I have automations trigger tts.google_translate_say with an entity ID of a speaker (or speaker group) and a message.
The .mp3 file is generated successfully in the tts folder, but my Google home devices make a sound like they’re about to say something (e.g. play the mp3 file from the tts folder) but it never actually plays now.
It just makes the noise like it’s about to then nothing.
Any advice is appreciated here.
Try adding base_url: http: //xxx.xxx.xxx.xxx:8123 to the tts: field in the configuration.yaml as per the documentation if you haven’t already.
Ah yep, just needed to set my internal URL in the configuration UI. Thanks for the reply, all good to go now! 
I’m guessing what broke it is renaming base_url field in the config: https://www.home-assistant.io/blog/2020/05/20/release-110/#internal--external-urls
Moving the value to the new place in the YML fixed it for me.
Hi Sir,
I’m also having issues with TTS. I added both my internal_url and external url (http://xxx.xxx.xxx:8123 and https://xxxx.duckdsn.org:8123) and finally added the base_url: http://xxx.xxx.xxx:8123 under tts in my configuration file. But when I try to play a notification that uses the tts, no voice is heard other than the bleep the Google Home Mini gives.
Did you do anything else?
EDIT: Hmm, so maybe this (in my case), was a matter of xx amount of reboots.
Finally both TTS and Cast started to work again with the below configuration:
#Connection URLS
external_url: https://xxxx.duckdns.org
internal_url: https://txxxx.duckdns.org:8123
Thanks
I’m now seeing this issue again although I have my internal address set, calling the service to all speakers doesn’t say anything, that’s odd…?