From 5842625a21841632d4556c8897a8c44e5f5349f9 Mon Sep 17 00:00:00 2001 From: Jon Griffith <32052562+arretx@users.noreply.github.com> Date: Mon, 11 Mar 2019 14:58:19 -0700 Subject: [PATCH] Additional clarification (#8900) * 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. * :pencil2: Tweak --- source/_components/tts.markdown | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/source/_components/tts.markdown b/source/_components/tts.markdown index 3d4fceac5d4..5698f9a6b8f 100644 --- a/source/_components/tts.markdown +++ b/source/_components/tts.markdown @@ -63,6 +63,10 @@ tts: base_url: http://192.168.0.10:8123 ``` +

+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. +

+ ## {% 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.