The ChromeCast integration pushes a URL of http://<hub IP>/tts/x.mp3. Requiring TLS on the hub causes all http:// URIs to redirect to https://. A valid cert for the hub's hostname doesn't cover the IP address, so TTS fails if TLS is enforced.
Solutions I see, neither under user control that I've found:
- Disable TLS enforcement for the TTS paths
- Enable setting the hostname used to build the TTS URIs
(Incidentally, I really don't like that you can read back the TLS private key from the web interface. That should be a write-only field.)