You´ll have to do it same way, but using the chromecast channels for playing in the.
I do however fail to understand the need of this… I would say it would be better just tell your Google Home device to play what you like 
1 Like
I’d like to turn on the radio in the bathroom as soon as I enter 
Found a work around by hardcoding the stream URL into OH but I’m missing a STOP command (just pause is available, which isn’t what I’m looking for). Example
playStream(“chromecast:chromecast:1a878c7e0bad179784fd70253a8d80d9”,“http://wdr-wdr2-aachenundregion.icecast.wdr.de/wdr/wdr2/aachenundregion/mp3/128/stream.mp3”)
@Kim_Andersen what did you mean by “but using the chromecast channels for playing in the.”?
I dont think there is a STOP. You should use PAUSE. It was discussed in another thread I cant find right now. Pause will do the same.
Hmm… Seems like something went wrong in that sentence… I was suppose to write, you´ll have to use the channel for this (I think it´s the control channel).
When I use PAUSE instead of STOP with the playStream command, then it actually really pauses the stream. Meaning, when I return to the stream I listen to a delayed stream which means e.g. the news won’t be played at the right time, like 12:00h noon.
It would be much better if I could really use TTS with something like “hey google play radio energy” and “hey google stop”. will give it a try.
I agree, and I would suspect it should work. But I have not tried.
Regarding the STOP. I have found the thread for you too read… Read the whole thread 
Chromecast Binding - How to send STOPMOVETYPE
Just buy another Google Home and place it in the same room, then sent the command to that Home 
great idea, I’ll do that 
So I finally got a chance to try it with GoogleTTS English voice (googletts:enUSStandardB to be specific) and the same thing happens unfortunately. My Google Hub and Google Home Mini both “hang”, and I see the state going to offline:
2019-08-18 11:13:41.182 [hingStatusInfoChangedEvent] - ‘chromecast:chromecast:06c76ee5758f49d9bdd0b87cddddddd’ changed from ONLINE to OFFLINE (COMMUNICATION_ERROR): Waiting for response timed out
Wish I could somehow get some debug logging from my Home device
Hi Gert-Jan,
you have mentioned earlier that you do hear the “beep” after sending the say command.
Did you actually aquire an API key and configure the google TTS service as per: https://www.openhab.org/addons/voice/googletts/#google-cloud-text-to-speech?
VoiceRSS also needs an API key BTW.
Yes, I have a key for Google as well as a key for VoiceRSS
Hi @giejay,
I encountered similar issue (beep but no voice) when my OH server and Google Mini Home were on different subnets.
It seems that for TTS to work, both devices have to be on the same subnet and can see (ping) each other locally.
Thanks for the feedback! My openhab server is running on 192.168.2.15 and my GH on 192.168.2.110. That shouldn’t be a problem. However, I am running openhab in Docker… Maybe that causes issues? People here who have it working while running OH in Docker?
When using Docker make sure you configure the IP of your server in the Chromecast binding callbackUrl:
Without that configuration the binding would send an URL containing the unreachable Docker container IP to the Google Home.
1 Like
I should really start reading documentation That was it, I added the IP of my raspberry pi and everything works now! Thank you
1 Like
Sorry for the ugly question but, do the google api key need a billing account as I understand till now?
I think you need a billing account, but you wont be billed
1 Like
I would also like to use the Google voice instead of VoiceTTS, but the chance of beeing billed is to risky for me:
|Default voice(non-WaveNet)|0 to 4 million chars|$ 4,00/1million chars|
|WaveNet-voice|0 to 1 million chars|$ 16,00/1 million chars|
I use it more than a year and my bill is still 0$.
1 Like
Thanks, signed on. The Voice is really excellent!