There is an issue with Hubitat TTS, Sonos Integration, and running hubitat with self-signed certs to enable and support https. Sonos speakers do not like self-signed certs and so far I have not seen away to add self-signed certs to Sonos speakers.
When ssl ui is turned off Hubitat TTS works with Sonos speakers. Is it possible to update Hubitat TTS and Sonos integration app to use a non SSL enabled port, but leaving the main / management UI as SSL / HTTPs?
You can apply signed certs to your hub. Then Sonos will see that cert. The built in cert is a 10yr cert and that is out-of-spec too.
There are, it seems to me, more reasons to use your own certs than to use the built-in. It has it's place but this perhaps isn't one of them.
I answer this way because your issue may not make it to the top of the development list as fast as you might like. I don't speak for Hubitat but there's always a time delay and you could deploy your own certs today.
I do run my own cert server and of course self sigened root ca cert. Which I then generate my device certs from. But again the root problem is the root cert is self-signed. I do not believe there is a way to have a known trusted CA like letsencrypt to sell / create a sub ca cert to be used with my own pki sever.
However, looking at the sonos error logs, it is not sending the sonos speaker to an FQDN HTTP URL, but just Hubitat's IP address URL. It is not using the configured host and and domain. So even if I had a real valid public cert assigned to hubitat, it wouldn't be used for the sonos integration.
Download the Hubitat app
