Does anyone have a successful speech path to their Chromecast device?
This used to be hit and miss for me. The cure was usually to rerun Chromecast Integration (Beta) Discover again.
Lately there is nothing that gives me speech.
I like having the warnings of water leaks, front doorbell, intruder at night etc.
Pushover still sends me the important stuff but the speech in the driver fails as well and night time it the best time for voice.
Chromecast integration doesn't give you speech, Echo speaks would have done it. There is a depreciated version here...
Confused.
I use my Chromecast (Nest) speakers, of which I have many, all the time to speak from WebCore pistons.
Lately they have been, at best, intermittent.
Hmm, Maybe it's webcore. I only know of echo speaks being able to do that. If webcore has the ability you may want to post in the webcore group.
Right, but it would be webcore handling it. Without webcore you would need echo speaks.. @ogiewon Any thoughts?
I just send text to the speaker and it speaks.
I just sent a test to the one in the office from the device driver input and it works fine.
Seems to be a Group thing maybe.
I guess that's why it still says Beta. 
All I seem to be able to get is the bell, but no voice, and only when I first try to use the device. Pretty sure I used to be able to.... When I try sending another speak request nothing happens.
EDIT - Now it's working.... 
I'm using Chromecast Integration (Beta) and have been successfully sending messages to the speakers through WC with no issues for some considerable time. I've never had any issues.
I also have 'Chromecast Helper' from bptworld installed and running. Again, this was installed some years ago and I've just left it running. I'm not sure if this is helping or not to be honest. 
Is this a new issue or has it always been the case?
2 Likes
I used to use the Helper as well but I wasn't sure it was doing anything.
I did just discover that if you run Discover it created some, not all, duplicate devices. 
As my pistons point to the previous device they now stop working until I delete the old device and use the new duplicate.
Testing the code now.
Yup. The duplicates created by Chromecast Integration Discover threw the old devices out of WebCore but left them in the Devices list going nowhere.
I deleted the duplicates and added the new ones to WC, all good now.
3 Likes
I never had any luck keeping the beta Chromecast integration connected, so I bodged together a driver that sends voice notifications over to Node Red via http. The NR Chromecast integration has been much more reliable. I haven't used it in a while because the dog freaks out whenever the Google lady speaks.
3 Likes
Echo Speaks is only for Amazon Echo devices. Alexa TTS (my deprecated integration) is also only for Amazon Echo devices.
This thread is about Google Home devices, using Hubitat's built-in Chromecast integration (beta).
I did have an early integration that utilized the Google Assistant Relay to perform TTS on Google devices. Perhaps that is what you're remembering? That code has not been touched or supported for many years now. It also required an always on RPi to run the Relay server, IIRC.
Glad to see that the OP has solved this issue!
1 Like
I am really not paying attention and conflagrating chromecast with google... Holy hell I need more coffee these days.
2 Likes
