The notify.google_assistant_sdk is broken here too.
Thanks for the workaround @tronikos.
Although it does not fully work for me.
Weird thing is that there’s nothing in the logs.
I don’t use nabu casa, but I’ve set up google assistant myself.
Maybe I’ll try to get some error logging on the google side tomorrow to see if I can catch something there.
This workaround worked for me the first time I used it but then on subsequent attempts with the same command it did not work. I tried the command listed above and the response was
So, I don’t think that is actually a workaround. It is just that the problem is very intermittent.
The issue has been fixed on the Google side.
We’re not the only ones who have noticed.
Question: Does IPv6 still need to be disabled to use Google Assistant SDK Broadcasts? Does it need to be disabled for global broadcast messages or just targeted broadcast messages? My goal is to provide room targeted broadcasts.
Before disabling IPv6 I was able to targeted broadcast to the original Google Home speakers and Google Nest Mini v2 speakers, but could not broadcast to the Nest Hub Display v2 speakers. After disabling IPv6, I’m still having problems with the Nest Hub Display v2. Now, I’m not quite sure IPv6 was the problem (or if I was unsuccessful at disabling it). Global broadcasts work.
I’ve also followed the SDK documentation enough to notice the IPv6 limitation was removed from the documentation, but I don’t know if this was intentional. Has something changed?
Confirmed the following: