Whenever we have an action using tts.cloud_say the speaker starts up but nothing is spoken.
Anyone know what could be the issue or how to debug it?
As far as I know there is no integration to restart for cloud tts?
Just noticed this in the logs.
The IP is wrong.
How could this be wrong all of the sudden?
Logger: homeassistant.components.cast.media_player
Source: components/cast/media_player.py:421
Integration: Google Cast (documentation, issues)
First occurred: 17 October 2026 at 21:48:12 (8 occurrences)
Last logged: 16:32:36
Failed to cast media http://172.30.32.1:8123/api/tts_proxy/z7IQpdiChxFQFcPWGqHaUA.mp3 from internal_url (http://172.30.32.1:8123). Please make sure the URL is: Reachable from the cast device and either a publicly resolvable hostname or an IP address
Failed to cast media http://172.30.32.1:8123/api/tts_proxy/aYr0BvokVBI2sQdPMmetmg.mp3 from internal_url (http://172.30.32.1:8123). Please make sure the URL is: Reachable from the cast device and either a publicly resolvable hostname or an IP address
Failed to cast media http://172.30.32.1:8123/api/tts_proxy/lA63z8nl1jgPwRNmmQ_HnQ.mp3 from internal_url (http://172.30.32.1:8123). Please make sure the URL is: Reachable from the cast device and either a publicly resolvable hostname or an IP address
Failed to cast media http://172.30.32.1:8123/api/tts_proxy/6LGBqVPqxG3P5pD9_XwhGQ.mp3 from internal_url (http://172.30.32.1:8123). Please make sure the URL is: Reachable from the cast device and either a publicly resolvable hostname or an IP address
Failed to cast media http://172.30.32.1:8123/api/tts_proxy/3T09iMt_4h0U22ah6tp5vQ.mp3 from internal_url (http://172.30.32.1:8123). Please make sure the URL is: Reachable from the cast device and either a publicly resolvable hostname or an IP address
Do you have Known Hosts configured in the Google Cast integration? And have you changed your port in Settings > System > Network > HTTP server?
I have not changed the port, it’s the default as in what used to be the default 8123.
Tried with known hosts but that did not help. Tried rebooting and that got it working again.
Very strange that it would make up its own internal IPs like that.
My internal IP has always been in the 192.168 range.