List for voice actions for genie download#

By using an IP address, the cast device does not have to resolve the hostname. If you are not using SSL then setting an internal URL that contains the IP address of your server works around this issue. In this example, the say service creates a URL like (or if you are using SSL). ThatвЂ™s because your cast device ignores your local naming setup.

List for voice actions for genie download#

However, try as you may, your cast device wonвЂ™t download the media files from your ha machine. All your machines on your local network are able to access it as ha. LetвЂ™s say your Home Assistant instance is running on a machine made known locally as ha. They do not work with URLs that contain hostnames established by local naming means. The Google cast devices (Google Home, Chromecast, etc.) present the following problems: Ultimately, your option may be to serve files to local devices as rather than Google cast devices However, many media devices do not allow changing settings to accept self-signed certificates. If you could make the device accept your certificate, it would play the file. The tts service will send an URL to the media device, which will check the certificate, and reject it. This problem occurs when your Home Assistant instance is configured to be accessed through SSL, and you are using a self-signed certificate on your internal URL. The following sections describe some of the problems encountered with media devices. # Example configuration.yaml entry for Google Translate TTS service tts : - platform : google_translate cache : true cache_dir : /tmp/tts time_memory : 300 base_url : service_name : google_say