Speaking of updating, I see that already 3 people from here are creating PR’s separately with similar changes. Perhaps it would be more convenient to join forces and work together on 1 PR.
I prefer to see those changes in this one: Update google_assistant.markdown by new-kirte · Pull Request #22349 · home-assistant/home-assistant.io · GitHub
So if you have also created a PR, see if you can add something to this pull request.
Thnx,
./Klaas
This is great - but screenshots would have been very helpful. As I am not seeing a way to ‘add’ these items to my existing Google Project (Actions Console) - did you create over from scratch?
In the Google Actions Console, open your project and go to Deploy > Directory information. Fill out those fields.
Has anyone run into this more recently? I have the same exact issue and added all the directory information, but after going through integration setup docs, re-reading this thread over a dozen times, and validating external connectivity, I’m still hitting the same error.
I noticed that the account shows linked in Test Simulator Setting after the attempt despite the error (I can Unlink and another attempt will re-link).
I solved this without adding logos or the other info. I only used another device with a fresh instalation of Google Home and everything worked!
I did these and nothing changed. Did you have to wait some time to get the changes applied?
Unfortunately for me, tried every step here, but still not working.
Edit:
Just waited some more and @piereligio mentioned it should all work again, and it did! So don’t fix it if it’s broke, Google will fix it for you? 
Apparently yes ahaha
I’ve wasted a whole day behind nothing 
Also another instance that I didn’t touch got broken with Google and resumed working out of nowhere 🥲
Hahaha I could control myself to limit it to just 3 hours yesterday and a whole lot of frustration the rest of the day 
I was having the same issue with not being able to link Google Assistant<->Home Assistant. In my situation, I had to turn off the proxy setting in Cloudflare for my IP.
I am getting the same issue, unable to link google home and [test]HomeAssisstant with all the added new descriptions and logos etc.
Can connect using cloudflare to the portal and all is fine, only not able to use google home and link it to Home Assisstant
Hi I’m having what appears to be the same issue. My nest stopped working (thermostat). I had tried removing and completely redoing with the new process with no success. Is anyone else having this issue still?
Can’t link to homeassistant
Please contact homeassistant if the issue persists
Same issue here, first unlink [test] HA, but unable to re-link Google to HA. everything in this post has been done.
try to disable dyndns with ipv4 Google Assistant is not working anymore (Could not reach <app name>[test] please try again.) - #5 by sbeagle25
this was the solution for me
The solution did not solve my connectivity problem. Still same issue as per you have mentioned.
This solution did not solve my Google connectivity challenge. Interestingly was working well until I upgraded to Home Assistant 2022.9.7 and Supervisor 2022.09.1.
If you’re using duckdns, from yesterday there’s global problem with duckdns-google and integration is unreachable.
It is not a problem with duckdns. I have just the problem after uppgrade from 2022.9.6 to 2022.9.7.
On 2022.9.6 it works. Just upgrade to 2022.9.7 and it false.
Same issue here, and I’m not using duckdns but a private dedicated domain.
SAme issue for me, stopped working yesterday 1st October, maybe google can’t afford the leccy bill now to power it lol, Have added descriptions to action on google console and made no difference. DUCKDNS still works for me using chrome with standard and incogneto windows, two phones on different networks using HA app.