Hi,
I made me a nice Voice Assistant ESP32 device that I can speak to, it does what I asked, and it replies by voice that it did it. YEEEEY!
I’m grateful to the people that made it possible.
There is one nagging problem though: When replying using Piper TTS, the device is passed an external https://MySpecialName.duckdns.org/api/tts_proxy/LongFileName.piper.mp3 link.
I want my TTS to be totally local, which it almost is, but the ESP32 Voice Assistant device is being pointed to the full external address of Home Assistant which is slow, goes through DNS, and defeats the purpose of having a local voice assistant.
I’m using an apache proxy server on another PC, configured to pass the certificates and point to my HAOS server.
So I’m hoping to find a way to use a local IP/hostname that my device can play the audio from.
I saw some complex workarounds that I didn’t fully understand and may not apply.
What can I do, please?
Hey, did you ever find a solution for ths?
There is another downside also, using https to play the response mp3 files create a lag compared to using http.
It was a long time ago, and I’m not really using it right now.
I think that setting “something” (https://yourhaosname:yourport) and NOT automatic in the “Local” URL in Settings/System/Networking worked but those two boxes (Internet, Local) behave very weird to me… like you can’t have both or something; maybe I just don’t get it.