-
Notifications
You must be signed in to change notification settings - Fork 46
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Some devices slow to play audio #257
Comments
As mentioned already, I just received my unit and seem to be having the same issue. The STT and processing are very quick, and the TTS in my pipeline is alo very quick, but the actual response sounding from the speaker has a delay of 20 ~ 50 seconds or so. Tommorow I have some time to take a look at the logs. |
I got my device today and have the same issue. First I thought it might be due to bad wifi signal but it has the behavior also next to the router. The audio response is not only slow but also stucks in the middle from time to time. This is really annoying as with that it is for our home not "production ready". |
I also have two Voice PE devices, one works great, the other is VERY slow to respond. Same issues as above, the TTS is generated quickly, but there is a lengthy delay before I get the audio response from the unit. Interestingly, I can see some pretty poor behavior when pinging the unit:
You can see the response times are all over the place, with several pings being in the multiple-second range. I have tried factory resetting it as well as completely re-flashing it within ESPHome and the behavior persists. My other unit responds consistently in the 100ms range with no dropped pings (subsequent tests with the bad unit did drop several pings). |
I'm not sure why, but my slow unit is working great now. Here is what I did, lets see if anyone else can reproduce:
|
Does the automatic OTA remain intact with this method? |
I can also notice that sometimes it takes longer for the device to actually execute the commands. When using my samsung phone, the lights for example turn off immediately. Sometimes with the Voice PE it is also quick to respond, but sometimes the command is executed 2~3 seconds later than I am used to when using my phone. Could this have to do something with the bad Ping results? I am also getting values most of the time of +3000ms. |
Hi @cryptk,
I also see slow pings, not that poor as yours, only 50 to 100ms, but compared to other devices in my network it is slow.
I tried the same, unfortunately it does not solve my issue :(
@StrandmonYellow: no, as documented here: https://voice-pe.home-assistant.io/guides/update/ |
Found some settings in another issue: #255 (comment), which are solving the "slow ping issues" for me. With these settings the ping response is normal. EDIT: after testing it a bit more I have the feeling that the response is quicker than before. Long responses still hangs in the middle sometimes, but when sending TTS actions they are coming immediately, before it had delays of a few seconds. |
As @hille721 mentioned, with the device "taken over" in the ESPHome Addon, no, the normal OTA mechanism will not work, but you can update it via the ESPHome addon. After taking over the device and re-flashing it to get things working, I was able to factory reset the device, delete it from Home Assistant and delete it from ESPHome, then re-flash it again using the official page at https://esphome.github.io/home-assistant-voice-pe/ and re-adopt. This has resulted in a properly working Voice PE which is NOT taken over in ESPHome and should support the standard OTA mechanisms. It is entirely possible that it's not necessary to do the take-over process at all and you could just re-flash the device using the page above to resolve the issue, I just went straight to taking over the device because I am quite familiar and comfortable with ESPHome. That said, if you aren't looking to modify the devices firmware at all, maybe start with just doing a user data wipe and/or a re-install of the firmware from the page linked above. |
@cryptk thank you for the detailed description. If I take over the Device using ESPHome builder Addon, it works great without any delay. I can also implement this change: #255. In this state, the device works fantastic. However, when I then delete the device from the addon, and reset it to factory settings and flash it again using the stock firmware, I am back to having the delay, and it not being responsive on any control input. I don't understand why there is no delay when I adopt it using the addon, and why there is a delay when using stock firmware? Edit: If anyone is still strugling with this, for the time being I adopted the device using ESPHome builder where it is working much better, until a version is released where this is fixed. Hopefully that will be soon! |
Mirrored from Home Assistant forum here
One of my two devices is slow to play audio. I initially thought this was just a slow response from the assistant or the STT/TTS processing, but looking at the timings, these are relatively fast. It processes everything within 3 seconds, but takes a good 20+ seconds to actually play the response.
Voice Processing:
I noticed when looking at the actual device on HA that is sits in the “Responding” phase for a long time (that 20s gap), before then moving to “Playing”.
Here are relevant logs for two devices, where you can see the massive delay in one compared to the other even when asking a local question such as “What is the time?".
Device 1 - Normal Response Speed
Device 2 - Slow Response Speed
The text was updated successfully, but these errors were encountered: