jeans/home-assistant.io
jeans/home-assistant.io
1
0
Fork 0
mirror of https://github.com/home-assistant/home-assistant.io.git synced 2025-07-17 06:16:50 +00:00
Code Issues Packages Projects Releases Wiki Activity

TTS: add examples how this integration is used (#31729)

Browse Source
This commit is contained in:
c0ffeeca7 2024-03-04 14:30:12 +01:00 committed by GitHub
parent d34f432e40
commit 7a5d5229b4
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 9 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
source/_integrations/tts.markdown
View File

@ -14,7 +14,7 @@ ha_platforms:
ha_integration_type: entity
---
Text-to-speech (TTS) enables Home Assistant to speak to you.
Text-to-speech (TTS) enables Home Assistant to speak to you. This is an internal integration that you cannot use directly. Rather, it is used by [other integrations](https://www.home-assistant.io/integrations/#text-to-speech). If you are using the Home Assistant voice assistant, [Assist](https://www.home-assistant.io/voice_control/), Assist is using TTS when replying to you. Another way to use TTS, is by using [TTS with Home Assistant Cloud](https://www.nabucasa.com/config/tts/).
{% include integrations/building_block_integration.md %}
@ -141,3 +141,11 @@ The Google cast devices (Google Home, Chromecast, etc.) present the following pr
- 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 an 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 SSL (e.g., `https://yourhost.example.org/...`) then you _must_ use the hostname in the certificate (e.g., `external_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.
### Related topics
- [List of integrations using the TTS integration](https://www.home-assistant.io/integrations/#text-to-speech)
- [TTS with Home Assistant Cloud](https://www.nabucasa.com/config/tts/)
- [Google Translate TTS](https://www.home-assistant.io/integrations/google_translate/)
- [Microsoft TTS](https://www.home-assistant.io/integrations/microsoft/)
- [Home Assistant Assist](https://www.home-assistant.io/voice_control/)