Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Closed
ZzetT opened this issue Nov 6, 2020 · 32 comments · Fixed by #43015
Closed

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

ZzetT opened this issue Nov 6, 2020 · 32 comments · Fixed by #43015

Comments

@ZzetT
Copy link
Contributor

ZzetT commented Nov 6, 2020

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

@Yorchbs
Copy link

Yorchbs commented Nov 6, 2020

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.

@frenck frenck changed the title Still not fixed? Unable to find token seed! Did https://translate.google.com change? Unable to find token seed! Did https://translate.google.com change? Nov 6, 2020
@frenck
Copy link
Member

frenck commented Nov 6, 2020

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

@probot-home-assistant

This comment has been minimized.

@rschuiling
Copy link

I am also experiencing this issue on HA 0.116.4.

@CineMAC-HA
Copy link

CineMAC-HA commented Nov 7, 2020

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

@antivirus68
Copy link

Same problem here HA 0.117.5. It worked till yesterday.

@hauserbauten
Copy link

Same problem since HA 0.116.4 now on HA 0.117.5

@maciekczwa
Copy link

Same on HA 0.117.5

@mkiryaha
Copy link

mkiryaha commented Nov 7, 2020

same on ha 0.117.5

@benganellison
Copy link

All cached strings works, but no new

@benganellison
Copy link

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'")}

@Ameglialuna
Copy link

same problem on 0.117.5

@edif30
Copy link
Contributor

edif30 commented Nov 8, 2020

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.

@probot-home-assistant
Copy link

google_translate documentation
google_translate source
(message by IssueLinks)

@benganellison
Copy link

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

@OleksijTkachenko
Copy link

same issue, all bots were destroyed (((

@rthamrin
Copy link

rthamrin commented 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?

@phudinhtruongk18
Copy link

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

@phudinhtruongk18
Copy link

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

@Boudewijn26
Copy link

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 Boudewijn26/gTTS-token#20

@Boudewijn26
Copy link

Boudewijn26 commented Nov 9, 2020

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?

@snakuzzo
Copy link

snakuzzo commented Nov 9, 2020

My experience...

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

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

@Boudewijn26
Copy link

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

@hmmbob
Copy link
Contributor

hmmbob commented Nov 9, 2020

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

@Boudewijn26
Copy link

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

@devmaster-terian
Copy link

Thank you very much @Boudewijn26 and @hmmbob

@edif30
Copy link
Contributor

edif30 commented Nov 10, 2020

@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!'

@klingon888
Copy link

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.

@Boudewijn26
Copy link

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.

@Mariusthvdb
Copy link
Contributor

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)....

@jazbraz
Copy link

jazbraz commented Nov 11, 2020

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.

@hmmbob
Copy link
Contributor

hmmbob commented Nov 11, 2020

The fix will be in 0.118....

@home-assistant home-assistant locked and limited conversation to collaborators Nov 11, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.