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

Created on 6 Nov 2020  Â·  32Comments  Â·  Source: home-assistant/core

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

google_translate

Most helpful comment

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

All 32 comments

Having the same problem with the basic code:

from gtts import gTTS
tts = gTTS('hello')
ValueError: Unable to find token seed! Did https://translate.google.com change?

There is still no fix? I cant advance in many projects without a fix.
Thank you.

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

I am also experiencing this issue on HA 0.116.4.

i am too in 116.4 since 4 days, but no always.

Same problem here HA 0.117.5. It worked till yesterday.

Same problem since HA 0.116.4 now on HA 0.117.5

Same on HA 0.117.5

same on ha 0.117.5

All cached strings works, but no new

This is from my logs

[homeassistant.components.google_translate.tts] Unable to find token seed! Did https://translate.google.com change? 2020-11-06 19:09:19 ERROR (MainThread) [homeassistant.components.tts] Error on init tts: No TTS from google_translate for 'Stäng Frysen' 2020-11-06 19:09:19 ERROR (MainThread) [homeassistant.components.http.view] Unable to serialize to JSON: Object of type HomeAssistantError is not JSON serializable {'error': HomeAssistantError("No TTS from google_translate for 'Stäng Frysen'")}

same problem on 0.117.5

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 is the label google_assistant appropriate here? It's a completely different component and integration.

I guess this is related to what is discussed in this thread: https://stackoverflow.com/questions/32053442/google-translate-tts-api-blocked

same issue, all bots were destroyed (((

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?

Unable to find token seed! Did https://translate.google.com change?
thank god. i'm not lonely

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?

how is it going

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

While we're on the subject, it appears to be working on my machine (which is a machine that hasn't seen gTTS-token before). It could be a change Google deployed, then rolled back or something they are gradually rolling out, which hasn't reached me yet.

Is it still broken for other people?

My experience...

  • Last friday I had same error
  • Sunday it worked again

Obviously I made no changes on configuration... :|

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

@Boudewijn26 Will you raise a PR to update google_translate here yourself, or would you like me to take care of that?

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

Thank you very much @Boudewijn26 and @hmmbob

@Boudewijn26 @frenck I just tested with 1.1.4. This issue is not resolved.

$ date
Tue 10 Nov 2020 08:43:42 AM EST

$ sudo docker exec home-assistant pip3 freeze | grep TTS
gTTS-token==1.1.4

### Automation triggered

$ tail home-assistant.log

2020-11-10 08:44:02 ERROR (Thread-33) [homeassistant.components.cast.media_player] Failed to cast media https://www.home-assistant.io/images/cast/splash.png. Please make sure the URL is: Reachable from the cast device and either a publicly resolvable hostname or an IP address
2020-11-10 08:44:04 WARNING (MainThread) [homeassistant.components.google_translate.tts] Unable to find token seed! Did https://translate.google.com change?
2020-11-10 08:44:04 ERROR (MainThread) [homeassistant.components.tts] Error on init TTS: No TTS from google_translate for 'There is someone at the door!'

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.

While I can't speak for home assistant google_translate, I'm currently investigating the changes made by Google to see if we can adapt to those (I've finally been able to get served the new version). You can follow along in this PR.

this issue is closed because the 'Unable to find token seed!' would be solved. However we now see constant:
Error on init TTS: No TTS from google_translate for issues. Wouldn't it be best to move that to a dedicated issue, where everyone can find it, and we are not breaking guidelines continuing on a closed topic?

if anything, please let us know how to aid in fixing this huge breaking change (somewhere)....

0.117.5
Logger: homeassistant.components.tts
Source: components/tts/__init__.py:172
Integration: Text-to-Speech (TTS) (documentation, issues)
First occurred: 16:00:03 (1 occurrences)
Last logged: 16:00:03

Error on init TTS: No TTS from google_translate for 'Meddelande till León.

The fix will be in 0.118....

Was this page helpful?
0 / 5 - 0 ratings