Google TTS - broken with Google Home and Mini - works fine with normal ChromeCast devices

I don’t remember how I solved this but I’m currently using Google TTS through Chromecast Audio devices with Hass.io on RPi3 and the DuckDNS addon. I have a ASUS RT-AC66U router running Asuswrt-Merlin firmware. I can use https and get TTS notifications.

Duckdns with let’s encrypt ? Check if you have enabled nat loopback or nat hairpin on your router

Yes, this addon https://www.home-assistant.io/addons/duckdns/ .

@n0ir, If you read the title and/or previous messages, you will see that it’s already known to work with Chromecast. The problem is with Google Home devices.

No need to be snarky @aherbjornsen

My setup works with both my Chromecast Audio devices, Chromecast video devices and a Google Home Mini.

I assume it’s because my ASUS router have the possibility for the right settings, but apparently it’s possible.

@n0ir, No attempt at being snarky - but I’m not a mind reader. Your message, as it was written, did not bring anything new to the table. If you actually have TTS working through your Google Home Mini as well, that’s interesting, but you did not say so.

I cannot get that to work, even with my router configured for nat loopback and intercepting the DNS calls from my Home Mini to Google’s DNS. Could you check your relevant DNS settings and post them here?

How do you configure the base URL your HASS config?

@aherbjornsen We’re all on this forum to try and help each other the best we can. :S I’m terribly sorry my attempt to help you was not clear to you but the reason why I took the time to post a replay was to try and share that it obviously possible to use DuckDNS and have TTS notifications through Chromecast/Google Home devices.

I’ve finally got it working on my Home Mini.

Apart from having to add NAT loopback in the router, the format of the base_url has to be correct.

I initially had it set to:

base_url: https://<mydomain>:8123

That did not work. Then i removed the ‘https://’ part like this:

base_url: <mydomain>:8123

And suddenly it started working.

Well, seen I can’t get NAT loopback on my internet provider’s router, I just discovered (and implemented) an alternative solution that actually works even better with Google Home. It consists in using the Google Home broadcast function, via another hass.io add-on : https://community.home-assistant.io/t/community-hass-io-add-on-google-assistant-webserver-broadcast-messages-without-interrupting-music/37274/12

The only downback is that it broadcasts to all your google homes, so if you have several in your house you can’t direct your message to a specific device.

I’ve been having the same problem for a couple of days.
Do not transmit the tts (mp3) just make the beep.

1 Like

I have the opposite problem. My google TTS notifications work fine on my google home but not on my chromecast audios. No errors that I can see either.