From bb9b92d7b3228969cb6e1c10f788b2fa0336399f Mon Sep 17 00:00:00 2001 From: Zemoj Date: Thu, 6 Feb 2025 12:56:01 -0800 Subject: [PATCH] Update troubleshooting.markdown (#37265) * Update troubleshooting.markdown Added media source fix for no TTS in YAML config. * Update troubleshooting.markdown streamlined media source text and added refence for default config. added local network header for more consistent style. --- source/voice_control/troubleshooting.markdown | 3 +++ 1 file changed, 3 insertions(+) diff --git a/source/voice_control/troubleshooting.markdown b/source/voice_control/troubleshooting.markdown index 7d316d56117..d87dbbf42ea 100644 --- a/source/voice_control/troubleshooting.markdown +++ b/source/voice_control/troubleshooting.markdown @@ -92,6 +92,7 @@ My voice assistant understands me and processes the command, but I don't get a v The voice response is generated in Home Assistant by one of our supported text-to-speech (or {% term TTS %}) engines. The voice assistant device then fetches the audio file from Home Assistant and plays it back. +### Local Network Settings For this fetching process to work, Home Assistant must communicate its own URL to the device. If you have a complex network setup, or if you changed this setting in the past, the URL communicated could be wrong. @@ -103,6 +104,8 @@ To fix the URL, follow these steps: - For most users, the **Automatic** option works and is recommended. ![Create alias for entity name](/images/assist/local_url.png) +### Missing Media Source +If you are using YAML configuration and do not have `default_config:` make sure `media_source:` is present. ## Tweaking the Assist audio configuration for your device