Problems with new voice assistant preview edition

[versed stratus]

Hey! Just got my new Voice assistant PE set up and managed to finally add it to homeassistant. It kinda works in the sense that if i say turn off the light in x room it works, but if i just say turn off the lights it won't, even tho it s assigned to that specific room.(the m5stack atom echo does it) more so after getting a command that doesn t work, it has to respond with "i couldn t understand that" but it just gets stuck in the Assist satellite Responding state with the blue leds circling and nothing happens. i m thinking there s a problem with outputing media. i have this in the error logs:

[18:38:12][E][speaker_media_player:326]: The announcement pipeline's file reader encountered an error.
[18:38:47][E][speaker_media_player.pipeline:112]: Media reader encountered an error: ESP_FAIL
[18:38:47][E][speaker_media_player:326]: The announcement pipeline's file reader encountered an error.
[18:38:47][E][audio_reader:142][ann_read]: Failed to fetch headers```



Any ideea what could cause this?

also i got this as well:

[18:34:42][D][voice_assistant:623]: Event Type: 5
[18:34:42][D][voice_assistant:666]: Intent started
[18:34:42][D][voice_assistant:623]: Event Type: 6
[18:34:42][D][voice_assistant:623]: Event Type: 7
[18:34:42][D][voice_assistant:718]: Response: "Turned on the light"
[18:34:42][D][voice_assistant:623]: Event Type: 8
[18:34:42][D][voice_assistant:740]: Response URL: "http://192.168.0.119:8123/api/tts_proxy/HqoVsW7g4VH3FD-MV-HuUw.flac"
[18:34:42][D][voice_assistant:477]: State changed from AWAITING_RESPONSE to STREAMING_RESPONSE
[18:34:42][D][voice_assistant:484]: Desired state set to STREAMING_RESPONSE
[18:34:42][D][voice_assistant:623]: Event Type: 2
[18:34:42][D][voice_assistant:763]: Assist Pipeline ended
[18:34:42][D][light:086]: 'voice_assistant_leds' Setting:
[18:34:42][D][light:074]:   Brightness: 66%
[18:34:42][D][light:160]:   Effect: 'Replying'
[18:34:42][D][media_player:083]: 'Media Player' - Setting
[18:34:42][D][media_player:090]:   Media URL: http://192.168.0.119:8123/api/tts_proxy/HqoVsW7g4VH3FD-MV-HuUw.flac
[18:34:42][D][media_player:096]:  Announcement: yes
[18:34:42][D][speaker_media_player:406]: State changed to ANNOUNCING``` it says the response was "turned on the light" but nothing played from the speaker

Also tried playing some media sounds i have stored and that does nothing as well

[18:56:17][D][media_player:083]: 'Media Player' - Setting
[18:56:17][D][media_player:087]:   Command: PLAY
[18:56:29][D][media_player:083]: 'Media Player' - Setting
[18:56:29][D][media_player:090]:   Media URL: http://192.168.0.119:8123/api/esphome/ffmpeg_proxy/7befc7aebcc9a0ee6543736a0f218325/sqEGH2TWKZ08Sm4gtUJMNg.flac
[18:56:29][D][speaker_media_player:406]: State changed to PLAYING
[18:56:29][D][speaker_media_player.pipeline:114]: Reading FLAC file type
[18:56:29][D][ring_buffer:034][med_read]: Created ring buffer with size 1000000
[18:56:34][D][speaker_media_player:406]: State changed to IDLE```

[tough egret]

is home assistant at the latest version?
is the VPE firmware at the latest version? (check the version in the device info in its device page)

in a recent update a basic command like "turn on the light" for something in the room it no longer responds with TTS. it just makes a noise to acknowledge.

if something is more updated than the other then might be some issues creeping in.

[versed stratus]

voice pe should be the latest i installed from https://esphome.github.io/home-assistant-voice-pe. i m updating home assistant as well now. turn on the light indeed doesn t do anything to require a response i noticed that

after an update turn on and turn off works. in the same room. if i try to turn it on in another room i get this in the logs: [19:16:27][D][media_player:083]: 'Media Player' - Setting
[19:16:27][D][media_player:090]: Media URL: http://192.168.0.119:8123/api/tts_proxy/gXwTlLOtGDKHC1uF7hf5Dw.flac
[19:16:27][D][media_player:096]: Announcement: yes
[19:16:27][D][speaker_media_player:406]: State changed to ANNOUNCING
[19:17:02][E][speaker_media_player.pipeline:112]: Media reader encountered an error: ESP_FAIL
[19:17:02][E][speaker_media_player:326]: The announcement pipeline's file reader encountered an error.
[19:17:02][E][audio_reader:142][ann_read]: Failed to fetch headers

and the device is stuck like this

[tough egret]

what are you using for TTS? piper? is that up to date?

can you show how your pipeline looks?

[versed stratus]

i ll update those again i m not sure when i did last time

[tough egret]

development for voice stuff in general is moving very quickly so updating is always best place to start

[versed stratus]

i ll come back in a bit after i manage to update the containers i have some problems with docker

[versed stratus]

Yep updated everthing did a restart on the vm and seems to work now thanks!