Voice assistant setup fails with 'announcement pipeline's file reader' / ffmpeg_proxy error #288
Comments
|
I hope I'm able to assist you or anyone else, I had the exact same problem with FFMPEG, the problem for me at least, was that home assistant sends the internal URL to the HAVPE, and this can be on any network not neccesarily the internal one The HAVPE appears to connect in the following steps:
For me as the HAVPE was on a separate network to the home assistant server, I needed to ensure the internal URL was resolvable on both networks, but in your case I would check the network reliability between these as you are using IP addresses (i assume on the same subnet). In my case (and I'm assuming others) I have home assistant running through an nginx proxy, that provides SSL through a wildcard certificate. To get this resolved I setup ADGuard, with a Domain Redirection filter, to serve up the externally resolvable address to the internal home assistant IP, then on top of this used a letsencrypt/nginx proxy so that the same https://myhomeassistantserver.com could resolve both to home assistant itself internally and when accessed via the already setup external nginx proxy. If someone from Nabu Casa reads this, is it possible to specify the home assistant URL that the HAVPE connects to as an advanced option for the ones that need this? |
I wanted to confirm that in the HA UI where one sets this "local network" URL, that you had the "Automatic" switch turned off? The reason I ask, is that in my case, the UI has this confusing wording for the "Automatic" switch:
I'm just not clear what "Use the configured network settings" means. I think it means if "Automatic" is turned Off, then HA will use the configured network settings in the box below it. However I talked with another user who said his configured URL didn't work for his HAVPE unless Automatic was set to On. Thanks. |
Thats correct, as that is the only way I can get the secure URL set that gets sent to the HAVPE
To see what URL (or other packets) are being sent you can install tcpdump using "Advanced SSH & Web Terminal" addon, i wrote my capture to a file and then opened it in wireshark, definitely recommend anyone doing this who is having network issues with this |
This appears to be my problem! HA in docker on a 172.x.x.x network cannot connect to the host 192.168.x.x IP. Need to figure out how I fix that... |
I have home assistant running in docker. The Voice PE is successfully added to HA as an ESPHome device, but when trying to set up the voice assistant part get the error " The voice assistant is unable to connect to Home Assistant". The link to documentation in the error points to the local network URL being incorrect, that is not the case here, the URL is valid, plain http and can be reached from the network the Voice PE is on. Logs indicate no connection issues, hower they do indicate issues with the FLAC file it (should?) get from HA during the setup:
Trying to query the same URL as the voice PE gives me a 200 response code but 0 byte body.
Since the documentation for voice PE all seems to assume you're running HAOS in some form pressed on and made sure to have the wyoming setup finished as well, thinking something could be missing there. So i have wyoming with piper, whisper and openwakeword set up. In Settings -> Voice Assistants I have a voice assistant set up using my local piper/whisper and that works fine when interacting with it through the web ui. Still, after that being set up I get the same error when trying to set up the voice PE. What am I missing here??
Error:
Voice Assistant config:
Device logs:
ESPHome debug logs:
The text was updated successfully, but these errors were encountered: