I’m experiencing a similar issue to @dastrix80. Often Alexa will say that the device is not responding. It is an intermittent problem. I can ask for the same device to be turned on several times, and sometimes it works immediately, other times will work only after several attempts. This affects all devices. I
Using the OpenHab app directly works as expected, as does asking Alexa for other information like the weather.
It may be coincidental, but after the restart of mongodb and the back end servers (openHAB Cloud: pool is draining/destroyed), the issue went away for a while, however it’s back now.
Overall I’d say this has been an issue since Early September.
@msexton187 - curious if you’re seeing the issue again?
I will add to this that I have now started experiencing the same. I would also add that it started once I updated to 4.2.1 a few days ago. I do not use Mongo DB though.
I just wanted to add to the thread that I am also seeing this problem in 4.3.0.M1 (and have been for several months on earlier versions as well) and can’t find a solution. I am not going to downgrade because this doesn’t break anything, it’s just annoying all of us (the family) that every time we ask Alexa to do something she responds that “the device is unresponsive” even though the action is usually carried out correctly.
I’m willing to help troubleshoot or provide logs if anyone can tell me what would be useful.
Same here- I’m still seeing this issue, happens several times on a given day seemingly at random. Happy to provide logs if needed, though it doesn’t appear to throw any errors locally.
Similar issues here, running 4.2.2-1 on a Pi 4B. Zwave devices unresponsive at 1st request but then seem to work at 2nd try, same with RFXTRX requests. Hit and miss. Kinda frustrating
I’ve been having this same problem as well. I’m on openHAB 4.1.2 docker container running in an x86-64 bit server. Lower version than most other people having the problem.
We use Alexa often to turn lights on or off. Sometimes it fails and Alexa says the hub the device is connected to is not responding. These days we get < 50% success rate. A lot of times it will succeed on the second attempt if it fails the first time. Sometimes I can try 3 or 4 times without success and have to get out my phone and change the lights in the app.
I believe my issue started around the August time frame of the other thread, and when the openHAB servers were rebooted and/or tinkered with I believe there was a few days of relief.
I’ve been on 4.1.2 since April in this configuration. I believe the Alexa stuff worked perfectly at that time and has only recently been an issue on the same time frame as what other people are seeing. I did not change or upgrade my openHAB version in that time frame which makes me think it must be an issue with openHAB cloud.
I’m happy to help debug if there are specific logs or anything that I could share.
Just wanted to briefly chime in to let you know that I also see this problem however it is much less frequent for me. Most of the time everything runs smoothly, sometimes I get the response that the device is not responding though it actually works and today I had the very rare case that Alexa was right when telling me that the device is not responding.
I was having Alexa fail to control my devices so frequently in the last month or so that I decided to try something today that seems to have resolved it. I decided to deploy a private version of the Openhab Alexa skill. That seemed to fix it.
This makes me think that there is a scaling problem ( maybe not enough lambdas allowed to run simultaneously ?) in the aws infra that is setup for the official Openhab Alexa skill.
One more thing, if you get it all working you’ll end up with a duplicate device for each device in your Alexa app. In addition, the new devices that you had Alexa discover from your private skill won’t work ( nothing will happen if you click on them) until you delete the old duplicate ones ( those will be obvious because they will be the ones that have a visual indicator of an issue) in the Alexa App. This means you’ll also have to reconfigure your Alexa groups and routines that were using the old device entries to use the newly discovered ones instead.
