TTS won't play on Sonos S1

[Whoarewe (Michael Knowles)]

Hi there,

Today’s project for me was to enable TTS because my wife keeps turning off a light switch I need to remain on. I’ve added the Google Translate TTS and it can play TTS files to my home cinema amp, but I want to send the TTS files to my Sonos S1 speakers (Play:1)

I’ve read that there may be some compatibility issues with the S1 speakers, but I don’t think I should be one of those from the looks of it.

There’s an error that comes up in the Sonos S1 app on my phone when I trigger a TTS from HA. This error says: “Unable to play ‘9e472f09082bb797429d07545c323836b7d175c0_en_-_tts.google_translate_en_co_uk.mp3’ - the connection to xxxxxx.duckdns.org:8123 was lost.” (where I’ve obfuscated my real home address to xxxxxx, clearly).

I run a split DNS at home so the URL listed is available both internally and externally, and it’s secured with a LetsEncrypt SSL certificate.

Any ideas on where i’m going wrong?

[PeteRage]

Post the complete error messsge.

[harry47 (Harry)]

As you’ll find in other topics, Sonos & LetsEncrypt & External URL don’t seem to mix:

Sonos will play at external dynamic Adress - no sound

I bought at ikea the SYMFONISK gen 2 speaker. Its connected with dhcp on the router. The android sonos app has “successfully” configured. Its connected with LAN, WLAN disabled. I can ping the device. The windows app also has recognized the speaker. HomeAssistant will try to play it with the EXTERN DYNAMIC IP Address "next_track_uri": "", "next_track_meta_data": "", "enqueued_transport_uri": "https://xxx.ddns.net/media/local/01%20Toccata%20an…

[harry47 (Harry)]

And this post actually mentions a fix that I’ve now adopted as well, redirecting the external URL back to an internal one:

Google TTS sending Sonos to external URL

You linked to my post from 2.5 years ago. Unfortunately HA and TTS has changed enough that my post doesn’t help now. I do have TTS and Sonos working. When TTS or even a media play command is sent to my Sonos it is sent my external URL. If I remember, Sonos requires HTTPS links in order to play anything sent to it. Sonos will not play HTTP or local network links. My HA is setup with SSL with a certificate signed by Let’s Encrypt. My internal and external URL are the same and I use a DNS redirect…

[Whoarewe (Michael Knowles)]

Just for completeness, I rebooted the Sonos the next day and it started working. The split DNS I mentioned should avoid any need for certificate-based failures as it resolves the same FQDN to the internal IP address when internal to the network. I’m also running NAT reflection on my firewall to do roughly the same thing so I think the error message was more of a misdirection than anything.