I think the issue might be with this component and not Google this time.
I tried using greghesp/assistant-relay with the same credentials, and it broadcasts without issues. In My Activity, the broadcast is coming from “Google Home” instead of “Google Assistant SDK”, but as far as I know, they use the same service calls and not the python library.
Have you tried uninstalling the add on and reauthenticating it?
No dice.
Everything was working fine for me earlier this week. It just stopped working all the sudden without me touching it. I run the docker image directly, not Hass.io, so I know nothing was changed.
Has this worked for anyone in the last week or so or dead for all again? It doesnt work for me right now, but really haven’t tried to troubleshoot either.
Weird. Everything should work. I even went as far as disabling/reenabling the Google Assistant API, resetting the OAUTH crediatials, and re-doing the authentication on port 5000. It registers OK, downloads the credentials file, and logs show messages going to it, but no broadcast comes out. Any other thoughts?
No go. Even deleted creds and re-authorized. My Google activity shows:
Said broadcast test
Got it.
Broadcasting now.
Here is the log from Portainer.
* Serving Flask app "hassio_gassistant" (lazy loading)
* Environment: production
WARNING: Do not use the development server in a production environment.
Use a production WSGI server instead.
* Debug mode: off
INFO:werkzeug: * Running on http://0.0.0.0:5000/ (Press CTRL+C to quit)
DEBUG:root:None
INFO:werkzeug:192.168.30.16 - - [15/Jul/2018 18:30:35] "GET /broadcast_message?message=test HTTP/1.1" 200 -
I’m not sure I am understanding this exactly. Does this replace the Google Assistant skill in the cloud component or does just provide the tts bridge to Assistant?
This lets you use broadcast to send notifications to google homes. The broadcast feature has a better tts engine (tends to sound more natural than the straight tts) and it also does not stop currently playing media so music for example fades down, the notification is delivered, and then the music comes back up. You can also send basic commands like ‘turn the kitchen lights off’ but this is a little redundant as you already have HA automations and google home voice control for that.
With this relay you are creating a notify service out of the broadcast feature, so you can use it like any other notify component within HA.
Just wondering, if the broadcast is still working for you, whether you are using the hass.io module ? Or is this your own container instalation/setup ?
Thanks @cogneato!! I was hoping that was the answer because that is exactly what I want, but I don’t want to replace the already perfectly functioning cloud component with something that seems to be having some growing pains.
Yes, this add on doesn’t replace any component in the ecosystem except the tts component.
All it does is create a standalone google assistant inside the add on, and that assistant accepts text-based queries… letting you broadcast text to all your google home devices using any type of automations that would send text notifications.
The quality is not only staggeringly better than the normal google tts in home assistant, but it will not cancel music that is playing on the google home.
If you do not have google home devices, than this add on won’t be of use to you. You won’t get any broadcasts.
Also, the google home you have must be using the same google account that you use to authenticate this add on.
Perfect. Exactly what I want. However, after uploading my Jon file and hitting Start, the button for grey for a sec, then red and the add on doesn’t start up. Nothing in the log in the add-on page, but will check home assistant log when I get home.