I did those and nothing changed. Did you have to wait some time to get the changes applied?
I started having this problem last week.
Before that it worked flawlessly for me and I haven’t set up those configurations before so i’m pretty sure it’s not that.
I added those anyway and haven’t had any luck.
Did someone find a solution?
Not yet. I’ve tried a whole lot of things (as also mentioned here Could not reach Home Assistant during linking with Google Assistant) but no luck unfortunately so far.
+1, same here. I am currently moving all my stuff to Home Assistant and did a PoC of this a couple of weeks ago, worked like a charm back then.
I did see the other post mentioning that you have to provide a bunch of info for the app now but regardless, no success.
For me Google Assistant linking to Home Assistant also stops working. The story is that I have used Google Assistant in my HA for about 2 years without bigger problems. In case of bigger trouble I have simply unlink and link my integration in Google Home app (it happens maybe 2-3 times), but it always starts working again, until… Two weeks ago I have had problem with syncing devices, so I have decided to make quick unlink/link and since then I cannot make it work again.
My [test] app is properly listed, it starts linking properly - splash screen “Link an account to control app on any device” appears, but after “Continue” it ends always with “Could not reach [test] app. Please try again” (linking done from external network). I have made dozens of tries with different configurations of my Google Action and Home Assistant configuration file. Unfortunately no success…
My configuration:
- Home Assistant Core 2022.6.7
- Home Assistant Supervisor 2022.05.3
- Home Assistant OS 8.2
- configuration.yaml (current version, cropped to minimum - previously I have used expose_by_default: true and disabling entities using entity_config:):
google_assistant:
project_id: xxx
service_account: !include xxx.json
report_state: true
exposed_domains:
- switch
- Google Actions:
- Google Console:
- NGINX - standard configuration with section http: added to configuration.yaml:
http:
use_x_forwarded_for: true
trusted_proxies:
- 172.30.33.0/24
- DuckDNS - also standard configuration
HA is accessible from outside as well as from local network.
I will appreciate any help with this problem.
edit 05.07.2022:
Today as every day I have made a try to link account and… it passed (from local network)! I do not know how it is happened because yesterday with exactly the same configuration did not work. Yesterday evening I have made one additional step - configuration (only mandatory fields and adding users for testing) of OAuth consent screen here: Google Cloud Platform . I do not know if it helped, but I am planning to not touch anything again 
I tried today (02/10/2022), no luck.
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!
2 Likes
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à…