Google Hub and Mini - "hey google" always result in error

Configuration Voice Assistant
1

I’ve spent 3 weeks reading and trying to figure out how I killed my Google Assistant devices in the process of setting up my first HA. The problem is that I’ve done a bunch of add-ons and integrations in a short period, and don’t know exactly which part made the google assistant stop working.

I’m too dumb to figure out how to debug voice assistant. All I can assume is that the voice component is not connecting to google cloud. Everything I call with “Hey Google” gets a response of “I dont know how to help with that, but here are web results”. It could be as simple as setting a timer, still wont work.

On the other hand, within the Google Home app, all devices show up (including entities from Nabu Casa domains)

Might be relevant:

  • DuckDNS is setup WITHOUT SSL (Have also tried with SSL, no difference)
  • using standard port 8123 on a reserved LAN IP
  • Tried factory resetting devices, rejoining home, etc without luck

If anyone can please point me in the direction to where I can debug this error, or which specific HA components may be interfering with Google Assistant, I’d greatly appreciate it!

2

I’m pretty sure you have to have SSL for Google Assistant to work. I found the easiest setup was DuckDNS and the NGINX Proxy Manager addon in Supervisor to handle SSL. And then port forward both 80 and 443 on your router (80 so that the proxy can redirect to 443).

3

So are you linking the Nabucasa App , or the manual integration? they are both different
If you use nabucasa, then your local instance doesnt mather, duckdns doesnt mather also

If you want local fullfillment witj nabucasa, then you NEED to run your local instance on HTTP

4

I’ll research the NGINX piece! Didn’t work with SSL alone

5

I’m linking the NC cloud

6

This doesn’t sound like a HA issue. Can you control the devices in the GH app?

7

Wow, I just update HA to the newest version (from second newest) and somehow this is working again, albeit the Google Hub takes like 6 seconds to reply which is odd.