Posts made by Matthew Mason

@Russ, thank you for such a quick response!

That’s kind of what I suspected happened — fix one user’s edge case and it breaks another’s preferred behavior.

I disabled the Alexa smart home "doorbell" press when the trigger source was an Alexa Smart Home device trigger.

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.

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?