I’ve never found any solution to this so far. I tried to put the echo alone on wifi access point on router, and while it seemed it happens less often, it still did. I just keep telling myself it’s no big deal and when it happens (usually when I try to show off my “smart” home) I just fly into bout of seeing-red rage and on the whole find the entire process quite cathartic /s
I wonder does anyone that encounters this use some sort of ad-blocking? I’m using pi-hole and wonder whether alexa tries to send some spy info every now and then with the request, and times out since the address is unreachable. Not really willing to test this though, as even if it was the cause, I ain’t giving amazon any exceptions in pi-hole.
It’s not just you. I don’t run a spam blocker the way you do and also get this behavior or worse, it will say the device isn’t responding. A quick click in my phone’s HA app confirms the device is fine and it’s either an Alexa issue or a connection to Alexa from HA.
My internet is rock solid fiber and it still doesn’t matter.
At this point I’m considering looking into some voice control alternative, I literally only use alexa to tell her “device/group/scene/automation name” on/off or ask her what is the “room/outside thermometer” temperature, really very limited set of maybe 15 sentences I only ever ask her and then I get disproportionally irate when she mishears and googles some nonsense or even worse starts playing some music.
No idea if anything like that exists though, something like Voice Attack for games but for HA.
edit: maybe I should just get google home
Thought it was just me. Lately it has been really slow response from my Tasmota based devices. 5 -10 seconds after I ask Alexa to turn on/off something.
Ok, same Problem here. Every now and then alexa complains that the device is not reachable, even though it did respond in the very last moment.
I have a rather fast internet connection.
Same for me, too. Often I’ll tell Alexa to (for example) “turn living room lights off” and she’ll say it’s not responding but the lights turn off anyway.
Additionally, the Alexa phone app will tell me that pretty much every device she can see via Home Assistant is “unresponsive” even though Home Assistant itself is fine.
By the way I’m assuming everyone else is using Nabu Casa for the Alexa integration, as I didn’t think there was any other option - that’s the case, right?
And… finally… this is on a Pi 4 in case it’s a hardware challenge.
I’m on nabu casa yeah, afaik you can make custom skill and use alexa without nabu, but I haven’t tried that.
I recently ordered google home (which uses nabu casa too) and gonna try to set up exactly same as I set alexa to see if it exihibits the same behaviour before I point any fingers. I’ve also set up instance of Mycroft, but don’t have time to play with it.
I also get he all unresponsive in alexa app and then when I pull the page down they refresh and act as if nothing happened. As for hw, my HA + mqtt + zigbee2mqtt all run in 12 core 3.3GHz 48GB ram vm so I should hope it’s not hw related.
Last thought is I have several things set up as Script helper object in HA, which if exposed to alexa appear as scenes in the app, and those NEVER fail. They might take even 5 seconds to “happen” occasionally, but they never do what this whole thread is about. However I don’t think it’s feasible/possible to set up everything as script.
I’ve set up same devices and routines on the google home and it’s the same, down to the dashboard devices going “offline”. GH will actually say outright it cannot contact Nabu Casa Cloud.
As found out by another ha user from nabu casa support apparently it’s a known issue as they’re upgrading network infrastructure, see the github comment.
I am having this same issue… I finally after a year of planning and playing to get to know HA, I am migrating off SmartThings due to the CONSTANT outages and un reliable setup, to HA with a USB GoControl Zwave/Zigbee dongle running on an ESXi host with the VM having 12GB RAM/8vCPU/60GB HDD. Got all 35 switches moved over and the numerous ZigBee devices and other Wi-Fi RGB controllers and such integrated. When I use the dashboard, everything is stupid quick. But when I use Alexa/Google, they either time out, or waits 10 seconds or so to perform the action… 10 seconds is LONG when you want the light on NOW… I am super disappointed by this and having regrets…
I even shut down the other 6 servers running on this ESXi host and even migrated to another ESXi host and same issues… I dedicated one of the 8 NIC’s to just this VM and put a path in my network to prioritize all traffic and even moved a vlan to make it go direct to internet and thats it… still same issues.
Thanks @pergola.fabio I am aware of that one, I decided to avoid the challenges of managing all that myself by using Nabu Casa but the family’s acceptance of it ‘not working all the time’ is wearing thin so I am reconsidering my approach.
Do I need to disable the nabu casa cloud google 1st? Will I have to redo all routines in google app? Could you post some rough steps you took to make it work locally?
This has been getting worse and worse and it has been long enough to fix. Alexa now tells me dozens of times a day “…not responding”. It really is to the point of intolerable and I’ve moved getting off of Nabu Casa high on my list. Even HA itself is having Cloud timeout issues.
