You’re having problems too? Did they started days ago or have they been going on for longer?
Hi, 2 or 3 days ago. Google home has no more answare. I tried to create and re-link a new test project but no luck.
It’s a known DuckDNS issue. There is discussion about it on a couple of threads.
Ok. I’m not crazy then. I’ve been reading about it and people have been using nginx instead of duckdns and it works. Like someone else already said, it’s a duckdns issue. We either wait it out or change the way we access HA, some people have purchased domains.
Today it works with duckdns.
Regards
1 Like
Good morning from Spain, there is not and never was a problem with Duckdns, neither certificates nor lets encrypt
The problem is in Google Cloud
I have tried:
– Change duckdns for godaddy, dynu etc, the problem still exists.
– Create a new project , renew credentials , the problem still exists .
– Remove IPV6 from homeassistant , remove my nginx proxy manager and do it with duckdns + letsencrypt plugins . the problem still exists
– remove 2FA from my homeassistant , the problem still exists
The solution?? : it was the most stupid and logical at the same time… google cloud allows us to create test projects… and they expire… we simply “must re-enable” it on google platform
I hope it helps a lot, it’s my first post and just thinking that it will save time for many people, gives me satisfaction, how beautiful it is HA! and what a war!
1 Like
After encountering a persistent problem, I eventually deduced its source. Surprisingly, it had nothing to do with either Google or my home assistant. Rather, it was a result of my ISP’s implementation of CG-NAT, which assigned me an IP address starting with 100. Due to my ISP’s proprietary DNS service, my home assistant was accessible from certain IP addresses but not from Google’s. Upon realizing this, I restarted my router several times until I obtained a different IP address not subject to CG-NAT, which now begins with 5.
fixed this problem on my router. I had country restrictions to allow only Australia. Took this off and it works fine. I put US and UK back on and restricted all others and it still works fine
1 Like
absolute legend, thnx.
hello,
we are the 05 october 2023 and the problem is back…
i use duckdns,
its just me or some have the problem back please?
I just got installed Google assistant on my HomeAssistant today.
It worked couples of hours and now got same issue as described in this thread.
Could not reach HomeAssistant Test from Google home anymore and cannot launch an update from Google assistant integration on HomeAssistant (got 404 error)
1 Like
Yes using duckdns also…
Voilà voilà…
dont think its a DuckDns problem because i succeed to relink my [test] APP but in Home APP android, my devices are connected, then 10 secondes after, disconnected, in loop…
Seems there is a problem on Google Servers side…
If you want to relink your [test] APP dont forget to delete the link of any Homeassistant shortcut on your smartphone home page, because it doesnt work if a shortcut of the app or a shortcut of HA in web browser is on the home screen.
I am also using DuckDns and getting the same connect, disconnect loop on the Home App and a Unable to sync devices with result code: 500, when resyncing in Home Assistant
this morning, i wake up, tell google to sync devices, it works again, i can control devices by voice, and change nothing…no relink app, not settings at all…seems back to normal…lets see…
Same here… sync google home worked, then launch from home assistant a synch google assistant and then lost the link.
Retried couple of hours after, sync devices from google Home, working again. This time I will not launch service sync Google from Homeassistant
Same issue! I feel in the past I would only be told it couldn’t reach the Test app after a HA update. Syncing my devices would fix it. Now (over the past month maybe) I have to resync every few hours and 70% of those sync time it claims they can’t reach the test app.
This time I will not launch service sync Google from Homeassistant
What do you mean by this?
I don’t understand why this tip isn’t included in every tutorial about this situation. Thank you!