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

Configuration
1

do we have a 117 bug, or, has google changed…

on my tts announcements I now see this in the logs:

Logger: homeassistant.components.automation.notify_espresso_ready
Source: components/google_translate/tts.py:126 
Integration: Automation (documentation, issues) 
First occurred: 7:38:56 AM (2 occurrences) 
Last logged: 7:38:56 AM

Notify Espresso ready: Error executing script. Unexpected error for call_service at pos 1: Unable to find token seed! Did https://translate.google.com change?
While executing automation automation.notify_espresso_ready
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 253, in _async_step
    await getattr(
  File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 463, in _async_call_service_step
    await self._async_run_long_action(service_task)
  File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 422, in _async_run_long_action
    long_task.result()
  File "/usr/src/homeassistant/homeassistant/core.py", line 1448, in async_call
    task.result()
  File "/usr/src/homeassistant/homeassistant/core.py", line 1483, in _execute_service
    await handler.job.target(service_call)
  File "/usr/src/homeassistant/homeassistant/components/script/__init__.py", line 215, in service_handler
    await script_entity.async_turn_on(
  File "/usr/src/homeassistant/homeassistant/components/script/__init__.py", line 320, in async_turn_on
    await coro
  File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 1010, in async_run
    await asyncio.shield(run.async_run())
  File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 245, in async_run
    await self._async_step(log_exceptions=False)
  File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 253, in _async_step
    await getattr(
  File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 460, in _async_call_service_step
    await service_task
  File "/usr/src/homeassistant/homeassistant/core.py", line 1448, in async_call
    task.result()
  File "/usr/src/homeassistant/homeassistant/core.py", line 1483, in _execute_service
    await handler.job.target(service_call)
  File "/usr/src/homeassistant/homeassistant/components/tts/__init__.py", line 168, in async_say_handle
    url = await tts.async_get_url(
  File "/usr/src/homeassistant/homeassistant/components/tts/__init__.py", line 341, in async_get_url
    filename = await self.async_get_tts_audio(
  File "/usr/src/homeassistant/homeassistant/components/tts/__init__.py", line 353, in async_get_tts_audio
    extension, data = await provider.async_get_tts_audio(message, language, options)
  File "/usr/src/homeassistant/homeassistant/components/google_translate/tts.py", line 126, in async_get_tts_audio
    part_token = await self.hass.async_add_executor_job(
  File "/usr/local/lib/python3.8/concurrent/futures/thread.py", line 57, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/usr/local/lib/python3.8/site-packages/gtts_token/gtts_token.py", line 28, in calculate_token
    seed = self._get_token_key()
  File "/usr/local/lib/python3.8/site-packages/gtts_token/gtts_token.py", line 58, in _get_token_key
    raise ValueError(
ValueError: Unable to find token seed! Did https://translate.google.com change?
2

Probably better to post issues with beta releases on Github or Discord.

3

sure, but I’ve learned the hard way to first check if it’s a user error :wink:
but here it is: https://github.com/home-assistant/core/issues/42255

4

:wink:
Capture

5

I see that from the GitHub issue that core now handles the error gracefully, but…
As a user, how do I fix this?
What do I need to do so it can “find token seed”?

6

I didn’t understand how to fix it… on github the issue is closed. But I have the problem also in 0.117.4 . Do you have the same problem?

1 Like
7

Yes, I have the same problem I mentioned in another thread. No answer yet. I also have no idea how to fix it. I used it to retrieve a template value, such as temperature or date. I had to quit. Several calls, almost half returned with an error.

8

Same problem also for me

9

Same problem here

10

Same problem here. Any fix?

11

I am chiming in here too, that I am also having this problem on 0.117.4.

12

Same problem here!

13

Same here, but only some messages sporadically produce that error:

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.

14

Same here,
I had to roll back to 0.117.1 for it to work.
Also getting lots of corruption when using iOs App

15

Hmmmm seems it’s an intermittent issue. Also occurring in 0.117.1?

16

Same here… seems to be intermittent. Same issue on NodeRed with error msg “get key failed from google” but it seems to still work intermittently.

17

Chiming in; also an intermittent problem for me but I am on HA 0.116.4 which is different than the rest of you.

18

This issue is being worked on. Please see following issue for updates:

19

Just ran into this for the first time today, and I’m on 0.118.4. The bug says it was to be fixed in 0.118.

I guess not.

To be fair, most of my TTS calls are the same, and are probably using cached values.

20

It was fixed, but it broke last night. The problem has already been reported.

1 Like