Are there other alternatives to accomplish this other than using bjpierron’s device handler for the simulated alexa switch? For example could this be implemented using webcore or using IFTTT?
The key is that echo routines can only be triggered from a sensor. Not a switch.
The advantage of the bjpierron DTH Was that it created a virtual device that was both a switch and a sensor. Turning on the switch, which you could do from any smartthings automation, would make the sensor look like it opened. So then your echo routine would trigger because it saw a sensor open.
IFTTT is not going to add anything to help with this.
Webcore does have the option of activating a virtual sensor that doesn’t also have switch capability. So you can try that. But my understanding is that that has been showing the exact same glitch.
Beyond that, at least initially the same glitch was reported with physical smartthings Sensors, although I don’t know if that’s still true.
But if you want to try an alternative method, webcore with a virtual sensor that was not also a switch would probably be your best bet.
1 Like
My Simulated Alexa Switch has started working again! 
This is not the result of anything I did because it has been many days since I made any changes.
1 Like
It was only intermittently working due to the new, buggy Alexa skill for smartthings
I think I know what the issue is. The new Samsung ST app update, Android users in the US are able to create virtual switch via the app, but that’s only Android users not IPhone. Maybe that’s the issue, they removed the IDE capability and never fully gave everyone the option to create V-Switches thru the app
That fixed my problem. Thanks!
Just disabled and re-enabled the SmartThings skill on Alex app.