Google Home Mini - Error on init TTS: No TTS from google_translate

Configuration
4

same problem!

5

Try base_url with the port:

tts:
  # https://www.home-assistant.io/integrations/tts#base_url
  - platform: google_translate
    language: 'es'
    base_url: https://xxx.duckdns.org:8123
6

Hi @GTaylor, I am facing same TTS init problem now… did you find the solution? I will appreciate any suggestion.

7

Same for me

8

Anyone found a fix?

9

Tried the base url and didn’t work. Gave up and switched to reverso tts through HACS.

10

Thats is to bad… is there anyone who has an idee??

If have an synology with reverse proxy, and can’t get tts running on my nest mini. I can play a file from an internal link but this is abracadabra for me

1 Like
11

OK, so it’s not just me, good to know.

1 Like
12

I got same problem since yesterday, until then it worked fine … but I haven’t done any update or installation.
I tried with base_url without port, without base url (using internal) and with external as base url; with and without nginx proxy … same result always

13

Take a look here, for example. I posted a post there.

14

I see. I’ve just switched to Reverso TTS / tts on hacs, works perfectly

15

Can Reverso TTS read data from templates, such as temperature or time?

16

I’m testing now… wait a minute

17

yep, it works! :upside_down_face:

18

Thanks. I will decide if I will wait for the update until 13.12

19

Hello, version 0.118.5 fixed TTS for me

20

0.118.5 fixed for me as well. Here are the release notes including new Google TTS API component for the fix: https://www.home-assistant.io/blog/2020/11/18/release-118/#release-01185---december-5

1 Like
21

I’ve upgraded to 0.118.5, but I’m still getting failures. The log now says:

* Failed to cast media https://192.168.86.37:8123/api/tts_proxy/a94a8fe5ccb19ba61c4c0873d391e987982fbbd3_en_-_google_translate.mp3 from internal_url (https://192.168.86.37:8123). Please make sure the URL is: Reachable from the cast device and either a publicly resolvable hostname or an IP address

My failing automation looks like this:

- id: '1604104081390'
  alias: Test automation
  description: ''
  trigger:
  - platform: event
    event_type: ''
  condition: []
  action:
  - service: tts.google_translate_say
    data:
      message: test
      entity_id: media_player.office_speaker
  mode: single

The office speaker makes the “badoop” sound. when running the automation, but no audio plays. Is there some new configuration that is required after this fix?

22

add base_url to tts

23

Thanks, that helped.

To clarify for anyone else with the same issue: I have a public duckdns domain pointed to my HA with an SSL certificate. When I would visit the https://[ip address] URL (from my previous post) in the browser, Chrome would show a warning about no SSL, but I could step past that and get the mp3 file. If I went to the same URL but used http instead of https, the page wouldn’t load at all. If I went to the same URL, but substituted the base url with my duckdns url, I got the mp3 file with no warning.

So, I updated base_url (docs) to reference my duckdns domain (e.g. https://my-domain.duckdns.org:[my forwarded port]), restarted HA, and now it seems to be working.