core: Manual setup of Google assistant integration broken
The problem
After it was working for months Google assistant integration with homeassistant now seems to be broken. I also cannot re add homeassistant in google home because after logging in I get this message:
Iam running homeassistant on docker in a pi behind a reverse proxy. Iam still able to reach my homeasisstant instance with https from a external network so there doesn’t seem to be any connectivity issue.
What version of Home Assistant Core has the issue?
Home Assistant Core 2022.6.7
What was the last working version of Home Assistant Core?
Home Assistant Core 2022.6.7
What type of installation are you running?
Home Assistant Container
Integration causing the issue
Google assistant
Link to integration documentation on our website
https://www.home-assistant.io/integrations/google_assistant/
Diagnostics information
No logs available
Example YAML snippet
google_assistant:
project_id: foobar
service_account: !include service_account.json
report_state: true
expose_by_default: false
Anything in the logs that might be useful for us?
No logs available
Additional information
No response
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Reactions: 2
- Comments: 85 (19 by maintainers)
Alright, so I finally figured out the root of my issues. Leaving my resolution here in case it helps someone else:
I’m not entirely sure if this first step is necessary, but the first thing I did was disable the Cloud integration by removing it from my config, then restarting HA.
Once I did this, I went into Devices & Services and enabled the filter to show Disabled integrations. Lo-and-behold, my Google Assistant integration was sitting there in a disabled state. Once I enabled it, all of my issues went away and Google Assistant was able to connect.
No idea how it ended up disabled, but I suspect it has something to do with Nabu Casa and how it handles the Google Assistant integration. Either way, hopefully this helps someone else if they ever run into this issue.
I suspect there are several root causes here. In my case, on careful review of my Google Actions configuration I found a typo in my HA URL. After fixing that, account linking went swimmingly.
I discovered that this error I had seems to be a direct consequence of an error during HA restart caused by a very simple indentation fault (typo) in the configuration.yaml file.
For some reason, after updating HA to 7.x the Check Configuration no longer catches such syntax errors, which in turn allows HA to restart. But during restart, as soon as it hits the faulty part of the configuration.yaml it seems like the rest of the file is skipped, and as a result not only the mentioned Google integration failed to load, but several others as well, including custom dashboards etc.
+1 for the last couple months with each HA version - have tried completely removing/configuring from scratch the Google Home, app, service account (or no device sync), etc. per the manual setup instructions and this thread. Everything’s accessible externally with a valid certificate and CloudFlare proxy disabled; I get the expected “405: Method Not Allowed” on the raw fulfillment URL.
I’m using Nginx proxy manager for SSL -> non-SSL backend. Websockets + HTTP/2 are enabled, no custom configuration.
Same here, have spent several hours troubleshooting this without any significant progress.
Others have stated that adding a logo and some more information (privacy policy etc.) did the trick but I also tried all of that and nothing changed.
I even started from scratch and worked through the entire documentation again but same thing, fails with “Could not reach xyz”