#First response to VoiceAssistant, after 10 mins of being IDLE, not played out

1 messages · Page 1 of 1 (latest)

fleet rose
#

Short description:
ESP32 voice assistant satelite is not able to play the response to the first command, after being IDLE for approx 10+ minutes. Responses to subsequent commands are played out normally.

Detailed description:
Using local VoiceAssistant setup:
Installation method: Home Assistant OS
Core: 2025.12.2
Supervisor: 2025.12.3
Operating System: 16.3
Frontend: 20251203.2
Using Local VoiceAssistant in English with
Conversation agent: Home Assistant
STT: faster-whisper
TTS: piper
Tried on ESP32 (no PSRAM), ESP32-S3 and ESP32-P4, both esp-idf and arduino frameworks. The ESP seams not to be the problem since tried to play the media on it after being IDLE for more then 10+ minutes and it works but the response to the first command is still not played out.
Enabled debug logs and no error is logged regarding Home Assistant.
TTS is also without error logs
I found the MP3 file in "\config\tts\2c73552970602ea3b6ba1dc88a40f2a15e78844c_en-gb_8cd8d30e6e_tts.piper.mp3" that contains the audio that should be played but when I go to DEBUG window in Voice Assistant I see in RAW view thet the URL is different "http://192.168.88.79:8123/api/tts_proxy/Q30iMZGwWZmERTcJDKSUNQ.mp3" and it is not working, I am unable to play that audio with the Play button.
On the other hand, after the first command, whose response fails, the subsequent commands response is played normall and for those responses I also finf MP3 files in ""\config\tts" folder and its URL also has a different name for the file but it works, I am able to play it from the Debug menu of Voice Assistant.

📎 home-assistant_2025-12-14T14-49-38.311Z.log 📎 VoiceAssistant-Debug.txt 📎 voiceassistant-esp32.yaml 📎 voiceassistant-esp32-p4.yaml 📎 voiceassistant-esp32-s3.yaml
proud basin
fleet rose
#

I believe my presentation of the issue shows that it is 100% not the ESPHome issue, the response is not played even when attempting from the DEBUG menu in the Home Assistant.
This issue needs someone who knows the code of the home Assistant

inner crest
#

Hey I recently jusy figured this out as well. It is a expiring stream token that is exchanged at the beginning of the pipeline. Home assistant then clears this after 5 minutes or so but then the pipeline will use the same expired token amd gey the error and you have to restart the pipeline.

#

The current work around is basically a script that restarts it without any activity after lile 4 and a half minutes to keep the token from expiring. There is a github issue about it. Im trying to boost this info so it hopefully gets some traction. In been there for a few months now I belive.