<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Routines not triggering anymore]]></title><description><![CDATA[<p dir="auto">Alexa routines that have a TriggerCMD device as their trigger seem to no longer fire when the TriggerCMD device is turned on from within Alexa.</p>
<p dir="auto">For example, I have a TriggerCMD device with voice name “Reset Volumes”, and an Alexa routine with the trigger “When Reset Volumes is pressed”. If I turn Reset Volumes on or off in the Alexa app, it used to trigger the routine. But now the routine will only fire if I trigger Reset Volumes from the TriggerCMD website or API. Turing Reset Volumes on or off in the Alexa app still runs the command (simply an <code>echo</code> in my case) each time, so that functionality is not broken. It just doesn’t seem to trigger any “When &lt;device&gt; is pressed” routines anymore. Is this intentional?</p>
]]></description><link>https://www.triggercmd.com/forum/topic/3361/routines-not-triggering-anymore</link><generator>RSS for Node</generator><lastBuildDate>Tue, 18 Aug 2026 01:41:53 GMT</lastBuildDate><atom:link href="https://www.triggercmd.com/forum/topic/3361.rss" rel="self" type="application/rss+xml"/><pubDate>Tue, 09 Jun 2026 02:51:01 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Routines not triggering anymore on Tue, 16 Jun 2026 02:34:46 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/forum/user/matthew-mason" aria-label="Profile: Matthew-Mason">@<bdi>Matthew-Mason</bdi></a>, it's a good use case that I should not disable, so I'm glad you caught it.</p>
]]></description><link>https://www.triggercmd.com/forum/post/8909</link><guid isPermaLink="true">https://www.triggercmd.com/forum/post/8909</guid><dc:creator><![CDATA[Russ]]></dc:creator><pubDate>Tue, 16 Jun 2026 02:34:46 GMT</pubDate></item><item><title><![CDATA[Reply to Routines not triggering anymore on Tue, 16 Jun 2026 02:27:59 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/forum/user/russ" aria-label="Profile: Russ">@<bdi>Russ</bdi></a>, thank you for such a quick response!</p>
<p dir="auto">That’s kind of what I suspected happened — fix one user’s edge case and it breaks another’s preferred behavior.</p>
<blockquote>
<p dir="auto">I disabled the Alexa smart home "doorbell" press when the trigger source was an Alexa Smart Home device trigger.</p>
</blockquote>
<p dir="auto">If you end up having to return to this behavior to avoid routines triggering themselves, I’m sure I can find a way to work around it. But I don’t know how many others are using TriggerCMD’s Alexa Smart Home device to trigger Alexa routines.</p>
]]></description><link>https://www.triggercmd.com/forum/post/8908</link><guid isPermaLink="true">https://www.triggercmd.com/forum/post/8908</guid><dc:creator><![CDATA[Matthew Mason]]></dc:creator><pubDate>Tue, 16 Jun 2026 02:27:59 GMT</pubDate></item><item><title><![CDATA[Reply to Routines not triggering anymore on Wed, 10 Jun 2026 19:38:26 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/forum/user/matthew-mason" aria-label="Profile: Matthew-Mason">@<bdi>Matthew-Mason</bdi></a>, thank you for reporting this.</p>
<p dir="auto">I was trying to avoid a loop that one user created, so I disabled the Alexa smart home "doorbell" press when the trigger source was an Alexa Smart Home device trigger.</p>
<p dir="auto">It was intentional, but in hindsight it was the wrong way to fix it so I reverted the change.  It should work now.</p>
<p dir="auto">I'll find a better way to avoid the loop.</p>
]]></description><link>https://www.triggercmd.com/forum/post/8906</link><guid isPermaLink="true">https://www.triggercmd.com/forum/post/8906</guid><dc:creator><![CDATA[Russ]]></dc:creator><pubDate>Wed, 10 Jun 2026 19:38:26 GMT</pubDate></item></channel></rss>