-
-
Notifications
You must be signed in to change notification settings - Fork 31.8k
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
Comments
Having the same problem with the basic code:
There is still no fix? I cant advance in many projects without a fix. |
There is no need to add "Still not fixed?" to your issue titles. It can be perceived as unfriendly, so I've removed it. |
This comment has been minimized.
This comment has been minimized.
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
|
same problem on 0.117.5 |
@frenck is the label google_assistant appropriate here? It's a completely different component and integration. |
google_translate documentation |
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? |
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 Boudewijn26/gTTS-token#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...
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.
|
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: if anything, please let us know how to aid in fixing this huge breaking change (somewhere).... |
0.117.5 Error on init TTS: No TTS from google_translate for 'Meddelande till León. |
The fix will be in 0.118.... |
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
Problem-relevant
configuration.yaml
Traceback/Error logs
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
The text was updated successfully, but these errors were encountered: