Can no longer link Google Assistant

Configuration
81

Any update for this issue? Still not working for me.

82

@ngankl79 most of us got it fixed by latest Home Assistant updates.

If that is not your case then use what another user did (saw it on GitHub).

Create a new Google project from scratch.

I know it suxx, but it worked.

83

I just created a new google project from scratch and still got the same result where the [test]HA canā€™t be reachedā€¦ I added the description, the logo, the privacy docā€¦ Nothing helpsā€¦

84

If you follow the instructions of the Google Assistant integration step-by-step thoroughly it HAS to work.

85

I just found out there was a region rule on my cloudflare configuration that blocked the traffic from Google. Solved allowing it from there!

86

what is supposed to come up if we go to those pages? I am having problems trying to troubleshoot getting this setup.

87

I just found this solution today.
The solution doesnā€™t work immediately.
Is it possible that Google first checks the application before releasing it? I got the following answer.
_
project-id submitted for review
Version 1 of project-id has been submitted for review for Closed Beta by [email protected], and will be evaluated according to our guidelines.

This process can take up to 3 business days. You shall receive an email once the review is complete. Actions with specific complex features (Smart home setup, transactions including both physical and digital transactions, reservations, account linking, and banking) go through a more extensive set of verifications, which may take longer to complete. You can also track the status of your review in the Actions Console.

Thanks,

The Actions on Google Team
_
The description still doesnā€™t mention these points. I searched and searched until I found your solution.
Thank you

88

I have this same issue, but it seems a bit strange

I add my project to google home, i get to login to homeassistant, and then when it says linking ā€¦ i eventually get an error saying cannot reach.

I have tried filling in all developer options, does anyone have any other ideas?

89

did you create a draft version? You have to wait for approval!

90

Do you need to create a release?

It says release is active and review is not requested

91

I get error 404 when trying to synchronize. The description says that the trial version is not active. With the browser on the Google server error 407 wrong method. Iā€™m waiting for my approval.

92

If i look at the deployments

image
image1548Ɨ574 22.3 KB

i see its deployed

But i cannot link it, it fails saying it cannot reachā€¦

Iā€™ve even tried removing it and recreating it

Interestingly both old and new are showing :
textPayload: ā€œSYNC: Request ID 1033542564668582666 update devices failed: CANCELLEDā€

in the google console logs

94

No, unfortunately not.

95

Hello,

Two weeks ago I ran into the same problem:
Relinking my GoogleAssistant failed after unlinking (before it worked for 3 months without problems).
Problem occured after correct homeassistant login screen and message ā€œ[test] ā€¦ sucessfully y linkedā€ then I got error message ā€œcould not reach homeassistant [test]. Try again laterā€.

My domain with ssl-certificate was working properly,
also credentials at console.actions.google.com or console.cloud.google.com were correct.
Sync my devices in app or voice-command result in an error, too.
Neither clearĆ­ng app-cache or uninstalling App helped.
Nor using GoogleHome-App from another (not home) network.

I found MY SOLUTION here (last hint at the bottom of the page):
https://www.home-assistant.io/integrations/google_assistant/
"FAILED LINKING - COULD NOT UPDATE THE SETTING. PLEASE CHECK YOUR CONNECTION
If youā€™re having trouble linking your account, with the error message Could not update the setting. Please check your connection after logging into your Home Assistant instance, try setting expose_by_default: false then exposing a single simple device (light or switch preferably). It is also worth checking if any home ad blocker is disabled if you are having issues."

  1. Change configuration.yaml and expose only one entity.
  2. Restart Homeassistant
  3. In GoogleHomeApp Settings>Services>AddDevices: Link ā€œ[test] Homeassistantā€
  4. Only your exposed Entity is shown
  5. Change configuration.yaml and set expose_by_default to true.
  6. In GoogleHomeApp Settings>Services>AddDevices: Longpress on Link ā€œ[test] Homeassistantā€ then select search for new devices.
  7. All entities are shown again in GoogleHome.
# Example configuration.yaml entry with only one entity exposed.
google_assistant:
  project_id: YOUR_PROJECT_ID
  service_account: !include SERVICE_ACCOUNT.JSON
  report_state: true
  expose_by_default: false
  entity_config:
    light.YOUR-LIGHT_ENTITY_IN_HA:
	  name: "CUSTOM_NAME_FOR_GOOGLE_ASSISTANT"
	  expose: true
      room: "LIVING_ROOM"

# Example configuration.yaml entry with all entities exposed.
google_assistant:
  project_id: YOUR_PROJECT_ID
  service_account: !include SERVICE_ACCOUNT.JSON
  report_state: true
  expose_by_default: true
96

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.

97

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

98

Not Working in my case :cold_sweat:
Any other solution ?

99

Hi there,

I am currently trying to set up HA with Google HA. Iā€™ve got a domain and my HA instance is reachable from outside. Iā€™ve configured the Google part and configuration.yaml like in the official docs but I am not able to add the ā€œDeviceā€ in the Google Home app. There i get an error 404 on ā€¦/api/auth/authorize. Out of curiosity i checked /api/auth/token (wich also get a 404) and /api/google_assistant (which replys with "405: Method Not Allowed).

Now i found this thread and wanted to to add the Directory information in the google action. And the next problem was bornā€¦ I am not able to upload a Logo. Iā€™ve tried different image formats with diferent resolutions and different file sizes on differnt devices and on different networks.

This google assistant setup is driving me crazy, am i the only one who get this error?

100

Iā€™m also getting the ā€œCould not reachā€¦ā€ error when trying to re-connect to my HA instance. My GA integration stopped working in the last day or so, so I unlinked the account and am now unable to re-link it. Iā€™m using the manual GA setup, not nabu casa.
I tried the idea of exposing a single, simple entity, as suggested above, but it didnā€™t help.
???