For me, the login into my HA works and then, after a while, the message comes: “Could not reach [test] myapp. please try again.”
I suspect my Nginx in. But everything else works. How can you use Google to see if everything in the project is correct?
When I trigger the sync in the integration, I see the error 404 in the service account of my project in the HomeGraph API. Because no account is connected.
Same problem, after freaking freenom crippled free domains I bought domain at cloud flare. Created new project in google console, and now my phone does not connect to home assistant via google home. Anybody has solution? I tried “solution above” from user from Spain , and it doesn’t work
I switched to my own domain yesterday/today and as part of this tried to resetup this integration.
Im stuck with Could not reach [test] myapp like the posts above and none of the alternative solutions are yet to help.
1 Like
Hello,
I had the same problem and posted my solution here:
Your solution still does not work after all , I even made 4 times new project step by step according the manual from HA, and still no positive result. I had previously account working on another domain, but after freenom did its thing, I had to buy domain at cloudflare and since then I’m having this issue. Everything is fine until I enter credentials to link HA with google home, then I get message “Could not reach [test] Homeassistant. Please try again later” in googles case later means never!
I have tried even uninstalling google home, clearing cash, trying on some other browser… and I run out of ideas
1 Like
I am also stuck with exactly the same issue. I’ve set up google home link as described in the tutorial, but then the last step after logging into Home Assistant when I get sent back to Google Home app, I get the “Could not reach [test] myapp. Please try again” - none of the solutions in this thread helped so far 
Problem solved. “ Manual setup (if you don’t have Home Assistant Cloud)” Google Assistant without Nabu Cloud works.
My problem was Duckdns related to my internet provider.
The ip4 address is just a nat address. This causes Google to try to access my HA via the ip4 address. I could try my luck, but then there was no response from Google.
The solution was incredibly simple. The ip4 on Duckdns was deleted and an automatic update was prevented.
It’s been running for 2 days without any problems. But now I have 2 new ones  My VPN WireGuard® is causing problems. The IP4 is gone and will probably have to display it again for the Fritzbox. And on Google I get:
Add capabilities
Seamless Setup Support local query
not selected.
But I’ll find that too. It doesn’t work, it doesn’t exist.
This has to work. do you get your login? Check your proxy and Google answers you. My solution is below.
I get my HA login page, and there when I enter credentials I am getting message could not reach [test] homeasssistant. Please try again.
I even switched off rule in cloud flare, now I am getting following message
But that’s good. You just have to adjust your yaml config
1 Like
how to adjust?
its already there
google_assistant:
project_id: zoki-somethingsomething
service_account: !include SERVICE_ACCOUNT.JSON
report_state: true
expose_by_default: false
I have managed to connect, but only when I exposed all entities to google home, now is such clutter…
A switch would have been enough☺️
diagnosis update 2 : Solution
issue with ip and dns resolution
yes duck dns , no ip like other services can help you to get access over internet but if you using ipv6 only then your google home app show error "could not reach [test] all
solution you need ipv4 as well to resolve ipv4 if you don’t have ipv4 like me here is solution for that as well
buy domain or if you have domain configure with cloud flare it will resolve your ipv4 queries and transfer to you on you over tunnel
before you setup cloud flare make sure you turned of reverse proxy like nginx and duck dns or no ip or what ever you are using
setup Cloudflare in home assistant
then google home and Alexa will work without any error
I got this working after trying a few more times. It may have been a cloudflared issue for me.