2022 Google Nest Minis TTS

Hi all,
Iā€™ve been using some rule scripts for a while to send announcements all around the house. However, during summer break, I turned them all off (using my ā€œVacationā€ switch). 7 weeks later, school is back and it was time to turn all the announcements back on. Well, they donā€™t work anymore. The rules run, the volume changes on the speaker, the sound file plays (like a chime), but the TTS never comes out of any of the speakers.

Using the ā€œSpeakā€ function with Google Nest Minis. Yes, I am aware of all the drama with Google Nest Minis and I spent a lot of time building a system that works.

Has anyone else had this problem this year (2022). They were all working in June but now donā€™t work in August. Google update that might cause it? Hubitat update? I just canā€™t seem to get the TTS to work.

I seem to be getting this error every time I use TTS, even in the device window.

su.litvak.chromecast.api.v2.ChromeCastException: Unable to load media on line 232 (method runQ)

Hmm... @gopher.ny ?

TTS is working fine here, the error you get is because of the chime (mp3) you are trying to play. To test, try to play text from the Chromecast device page using "Speak" option. Don't use play track in your script (for the moment - that error is being investigated).

1 Like

So, I had used the speak function alone in the device to test before and was still getting that error. Thatā€™s what finally led me to asking the group.

HOWEVER, I did figure it out. Two of my six speakers had gotten stuck in a loop. Possibly something to do with a file playback at some point. I had restarted my Hubitat, and that didnā€™t help anything. However, after going through all the logs, I noticed that those two speakers were constantly giving me that error. After removing those devices and reinstalling them, and updating my rules after the deinstall/reinstall, everything now works again. I am not exactly sure why the problem was affecting TTS and not file playback, and I donā€™t know why it was happening on all speakers. But, after reinstalling those two devices, all is well again.

2 Likes