From 18befc202e672c66bf17db489ba9e408b2a67f2d Mon Sep 17 00:00:00 2001 From: Dubh Ad Date: Tue, 6 Oct 2020 22:50:26 +0100 Subject: [PATCH] Clarity edit (#14588) Co-authored-by: Franck Nijhof --- source/_integrations/tts.markdown | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/source/_integrations/tts.markdown b/source/_integrations/tts.markdown index a8bdbbaf1be..9c679491bda 100644 --- a/source/_integrations/tts.markdown +++ b/source/_integrations/tts.markdown @@ -94,7 +94,9 @@ The Google cast devices (Google Home, Chromecast, etc.) present the following pr * They [reject self-signed certificates](#self-signed-certificates). -* They do not work with URLs that contain hostnames established by local naming means. Let's say your Home Assistant instance is running on a machine made known locally as `ha`. All your machines on your local network are able to access it as `ha`. However, try as you may, your cast device won't download the media files from your `ha` machine. That's because your cast device ignores your local naming setup. In this example, the `say` service creates a URL like `http://ha/path/to/media.mp3` (or `https://...` if you are using SSL). Setting a internal URL that contains the IP address of your server works around this issue. By using an IP address, the cast device does not have to resolve the hostname. +* They do not work with URLs that contain hostnames established by local naming means. Let's say your Home Assistant instance is running on a machine made known locally as `ha`. All your machines on your local network are able to access it as `ha`. However, try as you may, your cast device won't download the media files from your `ha` machine. That's because your cast device ignores your local naming setup. In this example, the `say` service creates a URL like `http://ha/path/to/media.mp3` (or `https://...` if you are using SSL). If you are _not_ using SSL then setting a internal URL that contains the IP address of your server works around this issue. By using an IP address, the cast device does not have to resolve the hostname. + +* If you are using an SSL (e.g., `https://yourhost.example.org/...`) then you _must_ use the hostname in the certificate (e.g., `base_url: https://yourhost.example.org`). You cannot use an IP address since the certificate won't be valid for the IP address, and the cast device will refuse the connection. ## Service say