You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm experimenting with non-stop conversation on the standard esp32 and I noticed this feature: if the response text is generated longer than a certain time, then an error appears in the logs, and the entire logic of the device breaks down.
Several examples with piper:
Weak Intel processor in mini PC gives an error after a couple of sentences.
AMD 5900x stops working after 2000 characters.
Piper on the GPU has not yet caused errors.
I've also encountered the identical problem with cloud TTS.
If you look at the time in the logs, the error occurs 5 seconds after the start of the response mode
[05:09:55][D][voice_assistant:642]: Event Type: 8
[05:09:55][D][voice_assistant:720]: Response URL: "http://192.168.1.162:8123/api/tts_proxy/FhgG4XTYwqaqKyzIxmGtkQ.wav"
[05:09:55][D][voice_assistant:505]: State changed from AWAITING_RESPONSE to STREAMING_RESPONSE
[05:09:55][D][voice_assistant:512]: Desired state set to STREAMING_RESPONSE
[05:09:55][D][media_player:073]: 'esp32VA' - Setting
[05:09:55][D][media_player:080]: Media URL: http://192.168.1.162:8123/api/tts_proxy/FhgG4XTYwqaqKyzIxmGtkQ.wav
[05:09:55][D][media_player:086]: Announcement: yes
[05:09:55][D][speaker_media_player:420]: State changed to ANNOUNCING
[05:09:55][D][voice_assistant:642]: Event Type: 2
[05:09:55][D][voice_assistant:736]: Assist Pipeline ended
[05:10:00][D][esp-idf:000][ann_read]: W (3021499) HTTP_CLIENT: Connection timed out before data was ready!
[05:10:00][E][speaker_media_player.pipeline:112]: Media reader encountered an error: ESP_FAIL
I used to use a wyoming satellite and it doesn't have such a strict timeout.
And now please help with advice. How to realize the assistant reset after this error.
The speaker_media_player error has nothing to do with the on_error trigger, so the wakeword is not started
As there has been no activity on this issue for 30 days, I am marking it as stale. If you think this is a mistake, please comment below and I will remove the stale label.
I'm experimenting with non-stop conversation on the standard esp32 and I noticed this feature: if the response text is generated longer than a certain time, then an error appears in the logs, and the entire logic of the device breaks down.
Several examples with piper:
I've also encountered the identical problem with cloud TTS.
If you look at the time in the logs, the error occurs 5 seconds after the start of the response mode
I used to use a wyoming satellite and it doesn't have such a strict timeout.
And now please help with advice. How to realize the assistant reset after this error.
The speaker_media_player error has nothing to do with the
on_error
trigger, so the wakeword is not startedcode
p.s.
Hopefully in the future Assist will move to streaming responses to prevent situations like this from happening.
The text was updated successfully, but these errors were encountered: