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-15 13:26:54 +00:00
Code Issues Packages Projects Releases Wiki Activity

Additional clarification (#8900)

Browse Source 
* Additional clarification

I was a bit confused about what the base url was supposed to be here and that setting it here was overriding the HTTP setting in configuration.yaml.  Often I see in the documentation that there are examples without explanation of why that was used as the example.  So for this one, I assumed that it was `asking` for the base_url that I had set, rather than allowing me to define a custom base url.

* ✏️ Tweak
This commit is contained in:
Jon Griffith 2019-03-11 14:58:19 -07:00 committed by Franck Nijhof
parent c94ba6327d
commit 5842625a21
1 changed files with 4 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
source/_components/tts.markdown
View File

@ -63,6 +63,10 @@ tts:
base_url: http://192.168.0.10:8123
```
<p class='note'>
In the above example, `base_url` is custom to this particular TTS platform configuration. It is not suggesting that you use the `base_url` that you have set for your core Home Assistant configuration. The reason you might need to do this is outlined in the next section.
</p>
## {% linkable_title When do you need to set `base_url` here? %}
The general answer is "whenever the global `base_url` set in [http component](/components/http/) is not adequate to allow the `say` service to run". The `say` service operates by generating a media file that contains the speech corresponding to the text passed to the service. Then the `say` service sends a message to the media device with a URL pointing to the file. The device fetches the media file at the URL and plays the media. Some combinations of a media device, network configuration and Home Assistant configuration can make it so that the device cannot fetch the media file.