I’ve setup and been using the Google Assistant integration with Home Assistant for quite a while now. I had everything setup correctly including DNS, SSL certificate, etc.
I noticed earlier this evening that I couldn’t resync devices. At first I thought I had to just renew the Home Assistant project’s test in the Google Assistant Action Console. But I quickly discovered that not only couldn’t I resync, but I couldn’t control any of my previously synced devices either. Google Assistant couldn’t reach the Home Assistant integration.
Upon inspection of some logs I am certain that I am not even receiving any REST/HTTP traffic from Google at all upon voice commands.
Earlier today I had to reconfigure the Nest integration in Home Assistant. It appeared like Google rolled out some new privacy and permission controls for the SDM API. I wonder if this maybe also affected the Google Assistant integration in some way?
Does anybody else experience anything like this? Any recommendations? I tried (most) of the recommended steps on the Google Assistant integration wiki except for completely re-bootstrapping the integration. Time to upgrade to Nabu Casa?
I found some logs that might be useful. I went to the Action Console → Tests → Simulator and clicked the “Logs in Google Cloud” link. There I found an error log that’s been logging errors consistently since around ~5:30pm.
externalDebugString: "Failed to add authorization token to the HTTP header."
isSuccess: false
statusType: "EXECUTION_GAL_NOT_FOUND"
Googling for EXECUTION_GAL_NOT_FOUND didn’t yield anything helpful. The externalDebugString leads to some Home Assistant related posts, but none of them seem particularly helpful.
This has happened to me twice in the past two weeks. I had to re-link the Home Assistant integration each time. I also see the EXECUTION_GAL_NOT_FOUND error in the Google-side logs.
Thank you so much, this solved my issue!
For me aswell Google Assistant stopped working although it worked for months before and I didn’t change anything! Reconnecting my existing Account resolved the issue!
