SOLVED (again): My Google TTS went out yesterday without warning?

I have this set up in the configuration:

  - platform: google_translate
    language: 'da'
    base_url: !secret tts-public-url

It has worked for quite a while, and then yesterday it stopped.
Has anybody else had problems?
I can’t figure out what is wrong, as I haven’t changed the firewall, and nothing is modified in the config, I don’t see what is wrong.
If I go and push a text to a speaker, it gives the usual ploink from Google when it receives sound, and then it usually playes the words, but not anymore.
It still playes the sounds we have for different signals.

I do have the same kind of problem when my DNS provider is down and HA is not accesible anymore

1 Like

The problem is, you’re using DuckDNS and they had yet another outage (I’d guess).

The “answer” is to run a proxy server and handle the SSL there. Then you can use http://192.168.2.55:8123 internally, and https://myname.duckdns.org externally.

1 Like

@Tinkerer good guess, but wrong :slight_smile: I have my own domain and a static IP.
My DNS provider, hmmm, that’s a big hosting company, and I can resolve my static IP without issues, but I guess they could have a problem in Google, just seems odd that it has been so for two days.

Hi @Tinkerer
Thankyou for the chat on discord yesterday, I got it fixed, I have the nabucasa url under

http:
  base_url: !secret nabucasa

So I removed the one under tts: and let it use that, and it worked. So for some reason, the url in tts pointing directly to me was not working any more, weird.

And then it went out again after going to 0.110.0, geez this is friustrating.

I do now have the same situation. Upgraded to 0.110.2 and had to remove “base_url”. How to make Google TTS work again?

Put back the base_url in the tts settings, that will make it work again, sigh… (the sigh is not for you @FaserF! :wink: )

1 Like