Google Translate TTS pronounce urlencoded characters

[divanikus]

The problem

I'm trying to use Google Translate TTS in it's default configuration. It does work, but for some reason it pronounces messages like if they are urlencoded. For example, "Hello world!" is pronounced as "Hello percent twenty world" (which is "hello%20world" i believe)

Environment

• Home Assistant Core release with the issue: 0.113.2
• Last working Home Assistant Core release (if known): unknown
• Operating environment (OS/Container/Supervised/Core): hassio
• Integration causing this issue: google_translate
• Link to integration documentation on our website: https://www.home-assistant.io/integrations/google_translate/

Problem-relevant configuration.yaml

tts:
  - platform: google_translate

Additional information

Here's the rendered audio:
d3486ae9136e7856bc42212385ea797094475802_en_-_google_translate.zip

[SeanPM5]

Happens here as well after installing 0.113.2

There's a forum thread about this here so it seems to be a widespread issue.

[wolverinevn]

Same issue.

[Mariusthvdb]

Just to chime in here and put some weight on the issue, posted this in the community https://community.home-assistant.io/t/0-113-automations-scripts-and-even-more-performance/213387/383?u=mariusthvdb

Hope this can be fixed in 113.3 ;-)

[probot-home-assistant]

Hey there @awarecan, mind taking a look at this issue as its been labeled with an integration (google_translate) you are listed as a codeowner for? Thanks!
_{^{(message by CodeOwnersMention)}}

[hmmbob]

Another thread on the forum, issue seems widespread https://community.home-assistant.io/t/service-tts-google-translate-say-is-translating-spaces-to-20/214942

[dshokouhi]

I do not see this issue in my venv install, it seems most everyone here is on docker/hassOS?

[hmmbob]

Yes for me on Docker (HA Container).

[rogerjak]

Same issue here. HassOS 5, Core 113.2.

[p1ranha]

same here Hassio 0.113.2

[antoweb]

same here hassio 0.113.2

[McGiverGim]

Another with the problem in Hassio 0.113.2. I sent the same text to the phone and it's ok, only TTS is wrong.

[Mariusthvdb]

(how can we resize images here? sorry for the huge picture)

On

[AntiqS]

Same here, was running 0.113.0 half an hour ago, and after the upgrade to 0.113.2 getting %20

[blair287]

Same issue

[rpitera]

Same here, glad it's not just me. Home Assistant 0.113.2 - HassOS 4.11

[jjMustang]

Same issue here. Running in Docker on Ubuntu.

[jazbraz]

Same issue here.

[cpunella]

I confirm, same issue after upgrading to 0.113.2

[miniontechy]

same here after upgading to 0.113.2. putting single or double quotes around message doesn't make any difference.

my script:

speakarming:
alias: speak of alarm being activated
sequence:

• service: media_player.volume_set
  data:
  entity_id: media_player.kitchen_speaker
  volume_level: 0.5
• service: tts.google_say
  entity_id: media_player.kitchen_speaker
  data:
  message: "Engaging cameras. Alarm activating in 30 seconds."

[sermayoral]

Same here. Home Assistant Supervised 0.113.2 over RaspberryPiOS in a rpi4 4gb

[MechEng70]

Removed the spaces and it works. Doesn't sound too bad.

[antoweb]

For me removing space cause bad pronounce (Italian)

[jmijn]

You can use dashes now as a workaround. Seems like they are not pronounced (this-is-a-test).

Hopefully this gets fixed soon as my Google Home is going crazy :D

[orson1282]

Same here, 0.113.2 Running in Docker on Ubuntu.

I did notice the following tho, *automations like this one work fine.

trigger:
- platform: time_pattern
  seconds: "5"
- service: tts.google_say
      entity_id: media_player.living_room
      data:
        message: "This is a test."

But *scripts like this one say the "%20" for all the spaces.

- service: tts.google_say
      entity_id: media_player.living_room
      data:
        message: "This is a test."

Also if I run it via the developer tools > services and choose tts.google_say it also says the "%20" for all of the spaces in the message.

[hossamnagy]

Another related issue is the way numbers are pronounced. For the text "The -time-now-is-11-43" is pronounced as "The time now is one one four three " instead of "The time now is eleven forty three "

[KentuckyMC]

Same issue here

[sotima]

Same here
HA 0.113.2 HassOS 4.11;

And its not only the spaces but also german "umlauts" (ä, ö, ü, ß) !

[frenck]

I've been able to pin-point the exact reason why this happens. Looking into fixing it.

[frenck]

PRs are up, marked them for the 0.113.3 milestone. Sorry about this happening, it wasn't a direct cause of any change in the 0.113.2 release, but a sub-dependency of Home Assistant was the root cause (which made it less obvious to pin-point).

Fix and more permanent measures to prevent this again, have been put in place.

[hmmbob]

Thanks for your help, Frenck. As said, fix works in my set-up indeed.

[KentuckyMC]

Awesome work! Thanks for the quick fix.

[sotima]

Great work! Thank you very much for your super fast response! You guys are awesome! 🥇

[miniontechy]

Thanks Frenck & all the folk at Home Assistant.
LOVE your work!

[antoweb]

Hello, thanks for fast response. How to install 0.113.3 in hassio? I must wait new release?

[frenck]

@antoweb 0.113.3 isn't released yet, so that requires a bit of patience.

[antoweb]

@antoweb 0.113.3 isn't released yet, so that requires a bit of patience.

Sorry from hmmbob I understood that her had tried

[damiano75]

Same here
HA 0.113.2 HassOS 4.11;
And its not only the spaces but also german "umlauts" (ä, ö, ü, ß) !

AHAH very nice. In Italian language replace spaces with dash (-) is a working solution for now

yes, but try with "è" ...

[rpitera]

Thanks @frenck for resolving this so quickly. Though it hasn't affected normal HA operations, this has been an annoying bug nonetheless! LOL
It was entertaining though; I had an automation that announced the nightly forecast and tomorrow's forecast at sunset. It sounded like my Nest Home Hub was having a stroke.

[hmmbob]

@antoweb 0.113.3 isn't released yet, so that requires a bit of patience.

Sorry from hmmbob I understood that he had tried

I did partly - I pinned the yarl package to 1.4.2 and that worked.

[hmmbob]

Confirming that 0.113.3 fixed the issue for me.

[tubalainen]

Yep! Can confirm working (Swedish) with .3!

[cvb941]

0.113.3 fixed most of the issue.

However, using the Slovak (sk) language, typing práčka into the Text to speak window of the media Media Control Card results in percentages.

Interestingly, typing Práčka with capital P works just fine.

[sotima]

0.113.3 fixed most of the issue.

However, using the Slovak (sk) language, typing práčka into the Text to speak window of the media Media Control Card results in percentages.

Interestingly, typing Práčka with capital P works just fine.

Probably coming from your tts cache?! You should clear the cache (/config/tts/)

[sotima]

..still waiting for the update to show up in supervisor ....

[rpitera]

@sotima - Reload supervisor and you'll see it.

[sotima]

@rpitera: thank you showed up immediately aftter writing my post!

[sotima]

Confirmed: German umlauts also work again. My wife is pleased! ;-)

[antoweb]

Confirm Italian language work again also with spaces

[antoweb]

Confirmed: German umlauts also work again. My wife is pleased! ;-)

Lol

[MechEng70]

Thank you. Wife is happy too!!!

[xbmcnut]

This issue has reemerged for me in the last 24hrs under 0.114.4 and supervisor 242. It's been fine under 114.4 for weeks only the supervisor has been updating and now when I restart Home Assistant, I get a long screed of '%' messages.