If this is your first visit, be sure to check out the FAQ. You must register before you can post. Your first post will be checked for appropriate content
(SPAM) - please allow a bit of time for that. After that, you'll be able to post at will!

Announcement

Collapse

No announcement yet.

TTS Issue with Google Home Mini when event is fired for the first time

TTS Issue with Google Home Mini when event is fired for the first time

April 21st, 2019, 01:24 PM

Firstly, thank you Spud for this wonderful plug-in.

I have been having a strange issue with this plugin and I am not sure what to make of it.
If I run an event that performs a TTS manually everything works well and the voice is played following the BEEP from the GH.
But when the event is fired, after a some time pases while GH wasn't in use I hear GH BEEP and no voice is heard. Then If I fire the event again or if it is triggered within a few minutes GH BEEPS and the voice is heard.

Comment

I too am having trouble with my GH mini. I just installed this plugin today. I didn't want to install the Apple service so I added manually. it appears in config. When I first pressed the Test button, I heard a ding, but no speech. I haven't been able to get any response from my GH mini since. Any troubleshooting steps I can take?

I just ordered 3 more minis with hopes of utilizing this plugin with them. I hope I can.

Much thanks!

Comment

I too am having trouble with my GH mini. I just installed this plugin today. I didn't want to install the Apple service so I added manually. it appears in config. When I first pressed the Test button, I heard a ding, but no speech. I haven't been able to get any response from my GH mini since. Any troubleshooting steps I can take?

I just ordered 3 more minis with hopes of utilizing this plugin with them. I hope I can.

Much thanks!

For me it works on second test within 5 minutes. As if the first ding wakes mini up.

Comment

I changed it for my post above, but it appears the contentId URL IP address is wrong. The plugin seems to be picking my VirtualBox network adapter's IP address instead of the physical adapter I'm actually using for network connectivity. Can this be manually set?

Thanks!

Edit: HS3 is running on the host and not from within VirtualBox

Edit2: Note that while they appear the same in my post above, the IP address used in the "/images/Chromecast/hs3.jpg" URL is correct. It's just the one to the .wav file is wrong.

Comment

Update on my issue. I can get TTS to work when I choose to use the Google voices instead of the system voice. I think I prefer my Ivona system voice and would prefer to use that if possible. I think I just need to figure out how to change that IP address that is being sent in the JSON. Any ideas on that? Thx!

Comment

banana, I noticed that when I switch from System to Google for voices, it doesn't work right away and I experience that strange delay you speak of. Once that first message comes through, the Test button seems to work immediately each time after...at least for me.

Comment

banana, I noticed that when I switch from System to Google for voices, it doesn't work right away and I experience that strange delay you speak of. Once that first message comes through, the Test button seems to work immediately each time after...at least for me.

I am on Linux so I don't know how to use ivonna voices. But yes after initial ding it starts talking right away for some period of time.

Sent from my Pixel XL using Tapatalk

Comment

banana, I just tested again with Google voices and I have experienced what you describe. After a period of inactivity, the Test button does not have an immediate effect. It is delayed. Then, after it finally responds, subsequent Test presses are acted upon immediately.

Comment

Update on my issue. I can get TTS to work when I choose to use the Google voices instead of the system voice. I think I prefer my Ivona system voice and would prefer to use that if possible. I think I just need to figure out how to change that IP address that is being sent in the JSON. Any ideas on that? Thx!

in Tools > Setup > Labs, you may need to set "Bind Server to IP Address" to the correct IP. Then restart the Chromecast plugin.

Comment

I can confirm the issue of my GH mini not responding in a timely fashion still exists in version .33. Sometimes it doesn't respond at all. Sometimes the status of my device shows as "Buffering" for quite a long time. I think it has to do with the plugin incorrectly targeting the wrong adapter IP address for certain things. For example, I have a speak event that first plays a .wav file. Speaker clients do this fine but GH mini will not. I see in the logs that the path to the .wav file I'm trying to play is wrong, just like when I try to use System voices. It is pointing to my VirtualBox Host-Only network adapter IP address, instead of the IP address of my host OS running HS3. Perhaps all of my problems are related to this. If the GH mini is trying to retrieve a file from an IP address that isn't responding, it must take a while to time out.