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

Configuration
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
21

Is anybody still having this problem ?
Base on https://github.com/home-assistant/core/issues/42911 it should be fixed but I am running 0.118.4 and still have this error.

22

See literally the post above yours to see it was somewhat fixed (through retry logic) but it broke again.

Issue at GitHub:

23

Broken for me too today
“Unable to find token seed! Did https://translate.google.com change?”

24

did you at least try to read the post above yours…

25

What he says ^.

Fixed in 0.119/1.0 with https://github.com/home-assistant/core/pull/43863, steps to get it to work now without waiting here

1 Like
26

Actually, 0.118.5 was just released and also includes this fix. So, no need to wait or run a custom_component if you upgrade to 0.118.5 when it becomes available!

1 Like
27

I just updated to 0.118.5 and google tts works very well again. :+1:

2 Likes
28

I still have this issue on 2021.1.5, but seems I am the only one?