-
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
Poor WiFi, drops outs, time outs, turning on LED in HA takes 15-60 seconds. #255
Comments
copying the yaml from here (home-assistant-voice.yaml) and then adding the below the device pings all the time and is near instant when doing things, like turning the LED on or changing the wake word.
|
Does your WiFi access point report the connected rates & connection sensitivity for the device? Or can you visit the built-in HTTP on the device, and see what it reports as it's connected WiFi reception? Or is that visible in HA at all? |
I had a similar experience with mine - it would process voice commands quite quickly (regardless of HA Cloud or local agents). At first I thought it was the text-to-speech (since it would then sit a while before speaking a response) - but then I noticed that simply toggling the LED light ring would take a while and sometimes not even work. I also have a Unifi AP and also have tons of ESPHome devices that work just fine. I added the snippet from above and things seemed to be much better. |
I can post info from the original firmware and with changes. I'll see if I can get it done today (as I'm sure after the holiday break there are gonna be more people with these devices) |
With wifi tweaks in ESP yaml OG from chrome flasher (issue was still happening at this point) whats strange is that at first it was having the same issue on the OG firmware from the chrome web browser flasher, after clicking "reset device" to try and get some cleaner logs it pings/behaves fine. OG from chrome flasher (issue no longer happening) |
Same issue here. When turning on or off the LED ring for example, it takes 10+ seconds for the unit to respond with actually turning on the LED. |
I'm experiencing a similar issue with my Voice PE. I have tested both firmware version 24.10.15 and the latest manually installed version (Firmware: 25.1.0 (ESPHome 2024.12.2)) from the official site . The problem arises during audio playback. The playback stops after about 30-40 seconds with a brief hiccup, displaying the error message "The media pipeline's file reader encountered an error." in the ESP console. I have tested multiple sources, including Music Assistant, external MP3 files, and TTS, and all function correctly with other media players on my network. However, with TTS, long responses do not play at all, while shorter ones work perfectly. The Voice PE responds quickly on my end. Here are two examples of playback failures: Music Assistant & External MP3 File : Stops after a few seconds.
TTS (Text-to-Speech) : Long TTS responses do not play fully or at all.
For reference regarding connection quality, I have observed good Wi-Fi performance (-49 dB) and minimal ping issues:
Thank you for your assistance! |
Are these things picked up? I don't see much activity regarding this or any other open tickets I must say |
Not sure what you would need for this one. I've got a Unfi AP, with a mix of ESP32 and ESP8266 devices that ping perfectly, tho they are all setup from ESPhome yaml files i have created (i think i turned off powersave on the wifi)
ping 192.168.1.165 -c 10
PING 192.168.1.165 (192.168.1.165) 56(84) bytes of data.
64 bytes from 192.168.1.165: icmp_seq=1 ttl=64 time=16984 ms
64 bytes from 192.168.1.165: icmp_seq=2 ttl=64 time=15927 ms
64 bytes from 192.168.1.165: icmp_seq=3 ttl=64 time=14903 ms
64 bytes from 192.168.1.165: icmp_seq=4 ttl=64 time=13879 ms
64 bytes from 192.168.1.165: icmp_seq=5 ttl=64 time=12855 ms
64 bytes from 192.168.1.165: icmp_seq=6 ttl=64 time=11831 ms
64 bytes from 192.168.1.165: icmp_seq=7 ttl=64 time=10807 ms
64 bytes from 192.168.1.165: icmp_seq=8 ttl=64 time=9783 ms
64 bytes from 192.168.1.165: icmp_seq=9 ttl=64 time=8759 ms
--- 192.168.1.165 ping statistics ---
10 packets transmitted, 9 received, 10% packet loss, time 9249ms
rtt min/avg/max/mdev = 8758.945/12858.740/16984.322/2649.692 ms, pipe 10
If i play with the volume up/down on the device it pings all the time i'm doing that.
The text was updated successfully, but these errors were encountered: