<![CDATA[Routines not triggering anymore]]>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.

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 echo in my case) each time, so that functionality is not broken. It just doesn’t seem to trigger any “When <device> is pressed” routines anymore. Is this intentional?

]]>https://www.triggercmd.com/forum/topic/3361/routines-not-triggering-anymoreRSS for NodeWed, 10 Jun 2026 23:12:45 GMTTue, 09 Jun 2026 02:51:01 GMT60<![CDATA[Reply to Routines not triggering anymore on Wed, 10 Jun 2026 19:38:26 GMT]]>@Matthew-Mason, thank you for reporting this.

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.

It was intentional, but in hindsight it was the wrong way to fix it so I reverted the change. It should work now.

I'll find a better way to avoid the loop.

]]>https://www.triggercmd.com/forum/post/8906https://www.triggercmd.com/forum/post/8906Wed, 10 Jun 2026 19:38:26 GMT