Yesterday it did not work.
This morning it was working.
Now it does not work.
Somehow it does not connect anymore to duckdns or someting else is happening.
The strage part is, when I open my browser or the home assistant app it connects normal with duckdns only the google speaker does not work.
Hi. I believe there is a global issue as currently I also cannot reach HA from google assistant (duckdns). HA devices are offline in google home app and their appear online for a short moments and then go offline right away. Might be something with google<->ha issue, as I can reach my home assitant from duckdns url
I am experiencing this issue for a couple weeks now.
I am NOT using duckdns, instead I have my own domain, setup using A records.
Google integration worked fine for two years and since a couple weeks it’s broken. I have to repeat my voice commands two or three times before google exexutes them succesfully.
Even when re-linking my account it needs multiple attempts before google can connect succesfully.
It’s very annoying.
Here are some logs from Google:
I cannot determine what’s wrong besides the fact that google encounters a Backend_Failure_URL_Timeout. (and that’s weird because i’m om a 1000Mbps Fiber connection and ping times never exceed 4 ms)
I’ve been seeing this recently as well. I am using DuckDNS, so have been thinking that was it. But commands, when executed, are often very slow to respond. I am starting to think that Google is changing things on their end that we are not aware of.
I’ve been fighting this when I was on DuckDNS and then on Cloudflare and I have found one issue and one manual solution. Anytime HA is rebooted I have to reauth the google assistant integeration and then I need to go into the Google home app and reconnect the Home Assistant linked service. The moment both are done it immediately works.
Also cloudflare has same issue
Same issue here. Tried both duckdns and cloudflare, same result. Nest speaker will fail once every couple of times.
Google logs are full with Backend_Failure_URL_Timeout.
Also enabled local fulfillment option but same result.
I am having this problem from time to time (still using duckdns). After difficult period in Oct it works most of the time, but sometimes devices go offline in Google Home for a couple of dozens of seconds.
At all times HA app connects flawlessly.
In Oct I noticed that although restarts do not help, the issue seems to become solved several days after pulling fresh image of container.
Coincidence? Maybe HA fails to reply promptly to Google?
Do you still experience the issue?
Still same issue here, gave up trying to solve it and I mostly just use Siri from my phone when its close by which always works and 10x faster.
A couple of months ago I never had any issues with google assistant either except being a little slow. Same here, never any issues with HA app at home or remotely.
Not using container config here, but normal restarts doesnt help anything. Cant wait for the native local voice control.
This started happening to me as of the 27th of december 2022 . Everytime I restart HAOS i need to reconnect Nabu Casa skill in the Home Assistant app on my phone. It’s really annoying.
I’ve had that problem ever since I’ve installed home assistant with google home and I finally managed to fix it.
I’ve migrated from freenom domain to paid registrar. I’ve thought that this won’t change anything (it’s just a domain) but since I use paid domain (.me in my case) google assistant is very reliable, and worked every time for a week.
I use cloudflared tunnels to expose my local instance to the world.
Has anyone found a solution to this issue? Every time I restart Home Assistant, it seems Google has disconnected.
Nope, I’ve been back and forth with nabu casa support for the past couple of months but the problem still persists. Everytime I try sync google entities it disconnects from google.
The only tyhing I havent tried is creating a new nabu casa account and using that to see if it fixes the problem.
this happened to me about a month ago and spent a day trying to fix with no joy but then the next day it was working fine.
Tonight the same error is occuring, open google home app on my phone and one minute it shows devices online, then they go offline and then after a few minutes they show as online again and then it repeats
I am able to use my duckdns url without a problem, I beleive it to be a google issue. will see how it is tomorrow
Also happening to me, starting yesterday. Was up for a while late last night and now is down again. Duckdns appears up and fine.
Edit: for anyone else that has ever had this happen - there is a reasonable chance (likely, but not confirmed) that this problem was caused by turning on the DoS firewall feature on my Asus router yesterday. There were all kinds of dropped packets to my HA server with this feature on that disappeared when I turned it back off and now Google Assistant is working again. When I looked in the Google project logs, it showed a bunch of timeout errors when I tried to use it while the DoS firewall was on.
I had the opposite happen. Since freenom is basically out, I bought a domain from xyz.com. I can get to my Home Assistant remotely but now I can’t seem to set up Google Assistant Or Alexa. I use Cloudflare and tried using option “everyone” in CF application
I’ve been having this exact same issue. Has anyone found a solution yet?
I used my own domain and used the Godaddy dns addon to update the domain dns, eliminating the need for duckdns and it’s been perfect since
So, we think the problem is with DuckDNS?
HERE IS A SOLUTION to the problem of Google Assistant’s intermittent inability to reach Home Assistant: I strongly recommend enabling local fulfillment for Google Assistant. This will substantially lower the fulfillment failure rates, especially if you are using DuckDNS for your remote HA access. As a bonus, the fulfillment latency will also decrease. The default configuration of the Google Assistant integration is cloud fulfillment - Google Assistant accessing HA via your dynamic DNS solution.
To check if you are using cloud or local fulfillment, check this link.
