Been observing some truely weird behaviour with the tts that has apparently changed overnight.
I use tts.google_cloud_say, set to a male german WaveNet voice. The required .json file is in the config directory, and everything was working fine last night.
This morning, I sent a voice message to my kids room, using the context menu in the media player card for his Google Home Mini, as usual, only to here the voice pronounce the german message in American English with a female voice.
I did some exploring and here’s what I noticed:
- Restarting HA didn’t change anything.
- Changing the parameters of the tts (pitch etc.) to force a refresh didn’t change anything
- Clearing tts cache didn’t help either
Next, I set up a test card with a click action of calling the tts.google_cloud_say service.
- If I use a Google Nest Hub as the target, everything works fine, the correct german voice is used.
- If I use a Sonos Roam as the target, I get the following error:
Error calling SonosMediaPlayerEntity.play_media on media_player.ecke: UPnP Error 714 received: Illegal MIME-Type from 192.168.86.33
Which makes me wonder if this is fallout from the Google/Sonos trouble.
However, using the context menu from a media player card in lovelace, even for non-Sonos devices, still defaults to the American English voice.
Any ideas what is going on here? Suggestions of how to get more clues?
1 post - 1 participant