I’m trying to connect my Google voice assistant to my account via the Google Home app on my phone, but once I pass the login page and hit the button to authorize access it redirects to a 404 error on the Google domain. Not sure if there’s a different approach to connecting those, or if Google has changed something recently.
I’m on Android, with Firefox as my default browser (relevant because I can open the 404 page directly in the browser instead of the WebView in the Google Home app).
I’ve seen a small handful of similar errors online, and they seem quite recent.
After spending a fair bit of time with this, it looks like it is potentially a documentation issue. My troubleshooting steps, which eventually led to success, were as follows:
changed browser on phone to Chrome
result: this led to better error messages in the Google Home application and eliminated the 404 page
ensured my HAOS VM was visible outside of its own subnet
result: didn’t really affect anything, but it did show me that the basics were working. Leaving this here because it could be useful for someone else
double-checked that there was at least one supported sensor / entity exposed to Google Assistant
result: this was the sticking point. Initially, I had exposed a number of items, which showed in the expose tab under the assistants settings menu. However!! The items I had exposed were unsupported, and the placement of the warning badge over the Google Assistant logo made it look like it was just part of the logo! Once I added a supported item, the integration worked immediately.
So I feel like there’s an opportunity for an improvement to the documentation or a more prominent indication that an item isn’t supported when you’re adding it to the list of exposed entities. It’s obvious when you see them together, but it’s just an unfortunate confluence of design decisions that makes seeing the error challenging:
Bottom line: Google Home works far better with Chrome for the sign-in process, make sure your HA is exposed to the outside world, and pay careful attention to the information provided in the HA dashboard as it’s not always obvious you’re creating an unsupported condition.
Hopefully this helps someone searching for this same answer in the future!
Same thing happened to me (Android user with Firefox installed and Chrome disabled) but I used used slightly different steps to fix it.
I reinstalled Chrome on my phone, but I think it was still using Firefox for webviews. I used the “open in Firefox” option on the webview and then copied the page URL and pasted it into Chrome and signed in to my Nabu Casa account like normal. Chrome automatically opened the Google Home app and finished the setup.
