hi,
very strange behaviour … since yesterday all my HA exposed entities to alexa stopped working via voice command:
in Alexa app all HA devices show as “device is unresponsive”
I already tried to:
disable and re-enable (re-link to nabu casa account)
switch off an on the Alexa Integration in HA
even deleted one Test light from Alexa app, de-listed that also from HA Alexa exposed entities and freshly added that entity (caused Alexa app to happily detect this as new device) but still not working
might be some coincidence with an HA update I installed yesterday ? … not sure
my question now is HOW can I further debug and find the root cause why this dies not work anymore
Wow big help here. I’m working on moving my HA instance to another machine and logged in with a backup on that machine before I’m ready to fully put it into production. Pretty sure having two instances running threw something out of whack but this was the fix. Thank you
It just happened to me, I’m not sure if it is related to Supervisor or Core updates, I just did some updates and the devices stopped working with Alexa.
Nabu was showing as connected, but after a logout and login, it fixed the problem.
As extra information, now the devices are showing as recently added to Alexa, and all of them were removed from the Alexa groups.
Same thing here. It keeps happening, too. I’ll try (to remember reestablishing the Nabu Casa connection after every update. I also have three separate instances of Home Assistant and I’m not sure if that has its own side effects.
Has anyone successfully built a cloud connection using AWS? Maybe this problem can be handled in a lamba service…
I upgraded to 2024.9.2 and Alexa is down. As this thread noted, Nobu Casa states:
Your instance is not connected to Home Assistant Cloud
Remote address: Not available
Logging out and in to Home Assistant cloud on my instance shows that there is an SSL error and it can’t fetch the subscription. The Nobu Casa status page shows no issues.
I know this is an old topic but it saved me a lot of time. I changed devices that I’m running my HAOS on and running the new device on a different IP address. Before shutting down my original HA device I didn’t think to log out of Naba Casa. Once I got the new device up and running I logged into Naba Casa and all seemed ok except for all of my HA devices exposed to Alexa stopped working and had an error of device not responding. I double checked to make sure I was signed in to Nabu Casa in HA, removed the devices one by one from Alexa, removed then re-exposed them in HA and Alexa and the ones I removed were not returning in Alexa. Once I found this post and checked my logon in the Nabu Casa cloud page I found the instance was not connected to Home Assistant Cloud even though I was able to use the cloud based Home Assistant itself. Logged out of the Nabu Casa cloud, logged back in and every thing is working as it’s supposed to again. Thank you for posting this!
reestablishing the Nabu Casa connection after every update. I also have three separate instances of Home Assistant and I’m not sure if that has its own side effects.