core: Unable to find token seed! Did https://translate.google.com change?

The problem

PR #42405 should have fixed issue #42255, but problem still occurs (sporadically?)

Many users seems to have the same issue: https://community.home-assistant.io/t/ha-117-unable-to-find-token-seed-did-https-translate-google-com-change/238237

Environment

Home Assistant Core release with the issue: 117.4
Last working Home Assistant Core release (if known):
Operating environment (OS/Container/Supervised/Core): HassOS 5.4
Integration causing this issue: Google TTS
Link to integration documentation on our website: https://rc.home-assistant.io/integrations/google_translate/

Problem-relevant `configuration.yaml`

tts:
  - platform: google_translate
    service_name: google_say
    cache: false

Traceback/Error logs

2020-11-06 12:18:55 WARNING (MainThread) [homeassistant.components.google_translate.tts] Unable to find token seed! Did https://translate.google.com change?
2020-11-06 12:18:55 ERROR (MainThread) [homeassistant.components.tts] Error on init TTS: No TTS from google_translate for ‘this is the second try’
2020-11-06 12:19:19 WARNING (MainThread) [homeassistant.components.google_translate.tts] Unable to find token seed! Did https://translate.google.com change?
2020-11-06 12:19:19 ERROR (MainThread) [homeassistant.components.tts] Error on init TTS: No TTS from google_translate for ‘this is the fifth try’
2020-11-06 12:19:41 WARNING (MainThread) [homeassistant.components.google_translate.tts] Unable to find token seed! Did https://translate.google.com change?
2020-11-06 12:19:41 ERROR (MainThread) [homeassistant.components.tts] Error on init TTS: No TTS from google_translate for ‘this is the seventh try’

So, the first, third, fourth and sixth message made it through and I was able to hear them, but not the ones mentioned in the log.

Additional information

About this issue

Original URL
State: closed
Created 4 years ago
Reactions: 15
Comments: 32 (6 by maintainers)

Most upvoted comments

There is no need to add “Still not fixed?” to your issue titles. It can be perceived as unfriendly, so I’ve removed it.

frenck on Nov 6, 2020

Hi everyone,

I’m the maintainer of gTTS-token. As stated, I hope to be able to spend some time this evening (GMT+1) investigating Google’s changes.

Feel free to discuss your own findings in https://github.com/Boudewijn26/gTTS-token/issues/20

Boudewijn26 on Nov 9, 2020

With v1.1.4 gTTS-token has now implemented a retry mechanism to deal with this issue. I hope that solves this issue.

Boudewijn26 on Nov 9, 2020

I also tested with 1.1.4. Same error msg as before. Its only working intermittently. I noticed that after the first non-working call for TTS, the second time seems to work. It then continues to work. But after its not used for a while, the problem comes back.

klingon888 on Nov 11, 2020

Thank you very much @Boudewijn26 and @hmmbob

devmaster-terian on Nov 9, 2020

@hmmbob If you would be so kind to take that up, it’d be greatly appreciated.

Boudewijn26 on Nov 9, 2020

same here :

ValueError: Unable to find token seed! Did https://translate.google.com change?

3 days back is still ok, I decide to choose a different API instead of using google. Does anyone have an idea? bing or IBM?

rthamrin on Nov 9, 2020