It’s been next to useless for me over the past few days. I still need to follow the advice in cogneatos’s post though.
To be honest, I have no idea how to delete the /config/.storage/cloud file.
How cann I do?
1 Like
Start with whatever it is you use to edit your files, then use that to delete it. You’ll need to enable the viewing of hidden files. Or you can use the ssh web terminal
1 Like
I just followed the suggestions here to resolve, doesn’t seem to be much better unfortunately. It’s been pretty bad the last few months with the requested action occurring after the “Sorry [device name] isn’t responding”. Reviews of the Alexa skill seem to all be the same problem, going back to June 2021.
Using a YAML config filter I’ve only got 12 devices and 9 scripts exposed.
number of devices exposed wont make a difference, only for discovery. The speed of the response is the only thing that matters for “device isn’t responding”.
If your devices are polled, you’ll also have this issue.
1 Like
Everything that is responding is a Z-Wave+ device on a pure ZW+ network. They’re instantaneous in every other method used to control them. I’ve kind of just filed it under “the cloud sucks”.
I’ve been experiencing this more and more over the last 6 mos to where it’s a problem now as everyone in the house is getting frustrated having to repeat themselves. Steps I’ve tried:
Cleared out the Alexa skill, excluded all domains, deleted all devices in the alexa app, removed and re-added nabucasa cloud, factory reset all alexa speakers, and cleared the cloud file. None of this has improved it notably. It almost seems like nabucasa cloud is being rate limited to AWS. Note I do not have this issue nearly as much with the 2 google home devices I have.
1 Like
Same. It’s unusable at this point. I reached out to Nabu Case support and was told they hope to have new upgrades in place in the next few weeks to remedy this. However, my family is done with the frustration, and I just spun up my own AWS & Alexa app/skill to handle this myself.
Response I got from Nabu Casa support that I shared on another thread.
1 Like
The new relayer was deployed! This only took a few minutes, and happened earlier today. Now it’s time to see if it helps!
You don’t have to restart HA for your server to re-connect, or sign in or out of cloud, but you can. If you wait long enough it will just connect on its own or it has already happened.
Try out your Google and/or Alexa voice assistants and apps and see how it goes.
6 Likes
It’s working perfectly now. A very noticeable change. Thank you.
I can confirm that mine has been much more responsive in the last 7 days - I’d say over 98% of commands are completed first time now.
Great work Nabu Casa!
Oh my god, thank you!! This has been so frustrating the past couple of months after Alexa stopped seeing first some and then ALL of my devices that I had set up in Home Assistant. I followed pretty much all of your steps with just a couple of small changes - including here in case helpful to others:
-
I did not delete /config/.storage/cloud. Instead I went into Developer Tools and under Configuration Validation clicked the “Restart” link, which I’m guessing reset that file appropriately
-
I found I had to change the order of the last 3 items. I had to do these 3 steps several times in different orders until I got Alexa to actually properly see everything. This is the order that seemed to finally do the trick for me:
- Managed entities for Alexa within Home Assistant to expose the devices I wanted Alexa to see (while Alexa integration was still disabled).
- Re-added the Home Assistant skill to Alexa
- Reenabled Alexa within Home Assistant (I think I may have also clicked the “Sync Entities to Amazon” link after re-enabling Alexa)
And… at least for tonight, all is working! Hopefully it stays that way this time!
Abby
Hello sir!,
I solved the problem by doing these steps but after 10 minutes all my device states on alexa went back to “Server unresponsive again”,
Is there any other way to solve this?
Thank you, this got my system back in operation! I was able to shortcut it by deleting (renaming, really) /config/.storage.cloud and restarting HA. All the devices that Alexa said didn’t exist or didn’t respond or weren’t in my profile are now working as before.
This started when we had a power failure at home that was long enough for my UPS battery to go dead. My HA instance is running as a VM hosted on a Synology NAS. Apparently when it unceremoniously lost power, some files were corrupted. It took several days to finally delete the right things for both my Zigbee and Zwave dongles to begin working, only to discover that Alexa apparently could no longer control all these devices, even though they were detected and any changes to them would also be detected.
It has been a long week, but so far as I know, this is the last broken item from that event.
Thanks again for the guidance!
1 Like
Today my devices became unresponsive in Alexa.
Tried to re-add the skill, re-expose entities to Alexa - nothing helps. Also, in NabuCasa web account I see “device is disconnected from cloud”, although it is indeed connected and I can visit it by NabuCasa address. Also in HA itself it says “connected”.
Is there some hiccup on NabuCasa side?
Hi!
today my Home Assistant devices got unresponsive in Alexa too.
First, i thought it was the update to Home Assistant 2023.10.3, Supervisor 2023.10.0 and
Operating System 11.0. But in Homeassistant all devices are running normal and working with Assist.
Also I opened the Alexa App and there were none of my devices reachable.
So I thought this could be troubles within Alexa itself.
Normal restart of Homeassistant did not help anyway. But it wasn´t at least.
By the way - I use NabuCasa.
Solution:
Go to → Developer Tools
Select → Restart → Advanced option → and click “Reboot System - Restart the system running Home Assistant and all add-ons”.
After doing this all my devices in Alexa are reachable again and working as expected.
Hope, this helps others
2 Likes
I did that and killed a container running in port 80 and it started working for me again!
hoping someone has any other ideas here… I have been using the alexa integration for some time… but over the last week, all my devices went unresponsive… I rebooted the HA installation, I removed the devices and relinked my account but as soon as I add a device (expose) it shows it as unresponsive in Alexa app… I am at a loss…
This absolutely has to be a networking problem. For me, if my ISP connection drops, or I unplug a network cable anywhere on my network on the path from my HA which is running in docker, to my ISP, then this problem occurs. It’s as if the connection between HA and Alexa servers is lost and it’s never re-established, which is 100% a coding problem that exist in how HA is implementing this. Of course, a restart of HA solves this because it forces that network connection to be re-established. This is a major problem that has been plaguing me for nearly two years and it needs to be fixed.