9 hours ago9 hr Hi All,I have a couple Alexa routines that are triggered buy a "fake" motion sensor associated with a state variable on the ISY. This has been working for years but just recently stopped. The device in the Alexa app indicates "Device is unresponsive". I found another thread (now closed) where other user(s) have had the same exact issue and it seems to be something on the Amazon side. There doesn't seem to be a solution other than spend hours on multiple support calls with Amazon and then hope it will be magically fixed. Even if I could get through to a real person for Amazon support, I'm not sure how I could explain what's going on? I'm sure they would suggest deleting all the routines, deleting all the devices, deleting the app, reboot, etc etc. I've already tried this with no success. The problem is obviously not wide-spread. Any suggestions on how to resolve this? Anyone else dealing the the same issue?
8 hours ago8 hr Author 1 hour ago, bgrubb1 said:I gave up and used "Virtual Buttons" Node Server in PG3XWish there was a free solution but I might have to give this a try.
5 hours ago5 hr 2 hours ago, DGG said:Wish there was a free solution but I might have to give this a try.looks like both virtual button plugins are free. Not sure what you're thinking costs anything. As for the Alexa problem -- yeah, that probably an Alexa issue as they (Amazon/Alexa/Echo team) really like to change code and ends up breaking things without letting people know. It's been a recurring theme here that things connected to/through the UD Portal to Alexa will randomly break then randomly work and it's nothing done by UD to disrupt the process...it's 100% random code changes via Amazon. I'm surprised people have been able to get support from Amazon to get things to work again. If I had anything that depended on Amazon's service it would have been removed long time ago.
Create an account or sign in to comment