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.
1 Like
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.
I anyone has any advice ill be happy to try it.
1 Like
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.
2 Likes
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.
1 Like
Exactly the same behavior with alexa voice command for me since few week.
1 Like
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.
I opened an issue on github @ Frequent Nabu Cloud timeouts with both Alexa and Google Home HA Skills · Issue #298 · NabuCasa/hass-nabucasa · GitHub feel free to chime in with anything I forgot, please don’t spam the issue with Me too posts, upvote the issue instead, thanks!
edit: I also changed title to reflect it happens with google home too
2 Likes
Happens to me too, and now even more then a few months ago
1 Like
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.
2 Likes
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.
For the time being, now setup local google instead of nabucasa, now it’s instant
I mean , I setup this one now :
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?
?? All Steps are on that link, 2 posts above …
I used the nabucasa link for the auth, so no port forwarding is needed…
Thank you for this. Not only does it validate what I thought the issue was, but hopefully it will be fixed soon.
I also might look into setting up my own Alexa integration, but I’ve been trying to avoid this.
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.
1 Like
Here’s the response I got when I contacted Nabu Casa support a couple days ago. (Completely separate from seeing this thread)
"
Yes, this is a known issue and it is being worked on.
We are re-writing the relayer which handles the communication between your instance and Amazon/Google and this is expected to be a large improvement over the current implementation. There should be much less latency and CPU usage on the backend and should be up between now February.
After that is tested and deployed, we will then be adding region specific relayer instances which should further improve the situation.
We have simply gotten to a point where we have many more users than when the service began and the same old resources and we need to make changes.
Thanks for your patience!
"
2 Likes
Ok so the new relayer has been deployed! This happened within the last hour as I write this.
This deployment didn’t take long at all and you should not have to restart HA or sign out/in to cloud on your server, but you can if you want to.
Most likely your HA server has connected to it already.
Try out your Google and/or Alexa voice assistants, apps, and see how it goes. Working well here.
6 Likes
Great job, thnx for the feedback!!
1 Like