I had also been seeing this issue. And while I was typing it is now resolved and I was able to relink in the Google Home app. Devices, device status, and device control is now restored.
I’ve been using this integration flawlessly for a couple years. I’m hoping it was just releated to duckdns. Last night I was seeing occasional moments where I could control my devices and then they would go offline. I tried the usual unlink and relink process in the Google Home app but it wouldn’t relink until just a moment ago. It would load the login page for Home Assistant so it seemed like things should be working.
Update: looks like devices are still intermittently offline. But I am able to control devices in the windows where the status isn’t offline.
Im sure the problem is at google. I can connect to my home assistant from outside by using my ducksdns url. All my content in home assistant can be used both on chrome und firefox browser. Where can the issue are on ducksdns in this case? This seems a problem by the communication betwen home assistant and google home app or something on the google action. I used another dns service and its the same. At the last step i builded a new action by using my outside url, but the same result. How can it now be duckdns yet?
This started happening yesterday, 10/01, on my setup using Duckdns + Nginx addon. The “Check for new devices” option in Google Home takes me to the HA credential page and allows me to successfully authenticate but I then receive the error “Something went wrong”.
Hello, same problem here (Italy)
My configuration has been good for a couple of years but yesterday I started to lose connection from google assistant.
I tried to
check again the configuration - was good
Start a new setting from scratch - Issue remains
Try to delete my domain from duckdns and reconfigure it. - nothing changes
Check my ssl certificate but it is still valid.
I am able to connect from HA app or browser, but sometimes I lose the connection for 10-30 seconds to
Sometimes, I try to “sync my devices” and 9 times on 10 it fails
Trying to connect to https://xxxxxxx.duckdns.org:8123/auth/authorize, I figure a page “access with home assistant local” and an error “Errore: Message format incorrect: required key not provided @ data[client_id]”
If i try to reconnect my test app from home app, it asks my HA user and pass but then it fails. (but… should’t use the token created on the google service account page?!)
I wasted a night on it and I hope that I don’t create a mess on my configuration (HA, router, SSL certificate, duckdns, and so on)
Same issue. Also using DuckDNS. Started Saturday morning (US time) and is ongoing? I tried several fixes, including removing the Google Assistant integration. Interestingly once I removed it I couldn’t find it again to reinstall, and restored an earlier backup to undo all my testing. Perhaps some disconnect with the integration and current version of HA?
@vanster I had the same issue with the with the google assistant instillation not be listed to reinstall. Found it odd but once i rebooted the instillation showed back up as if i never uninstalled it. It’s still not showing up in the list of integrations.
Can confirm with reasonable assurance that this issue is/was caused by DuckDNS, maybe some system at google flagging their DNS due to nameserver crashes.
After reconfiguring Google Assistant services to use my own(paid) domain using a paid DNS service, it works just fine.
@Appelflap is there an article you can direct us to so we can follow your steps here? Or some bullet points you’re able to share? I’m sure I could figure it out given enough time but since you’ve just fixed the issue for yourself would be grateful if you’re willing to share how you accomplished it. Thanks!
If the root problem is indeed because of Google not playing nicely with DuckDNS any longer (for whatever reason), then there are plenty of other dynamic DNS services out there. Your home router likely has a feature built into which you can use. In my case, I have had a personal domain for years which I can configure the DNS records for. In my case, I created a “homeassistant.domainxxx.com” CNAME record on my domain registrar’s DNS servers which points to the dynamic DNS record of whichever dynamic dns provider you setup. My Let’s Encrypt add-on is configured with the “homeassistant.domainxxx.com” CN (CommonName).
But you needn’t have your own domain name for this to work. For example, if you are using a Netgear router, you may setup “xxxx.mynetgear.com” as your home assistant URL. You would then remove the DuckDNS add on and separately configure the Let’s Encrypt add-on with this same name.
Yeah. chiming in here so i can follow this. I am also on duckdns and experiencing the same issue everyone else here is seemingly having. Looking forward to an answer when someone can find one. I am also digging around some myself.
