Closed shresth45 closed 3 weeks ago
shresth45
commented
3 months ago My network is typically firewalled off to prevent WAN access. I allowed all traffic temporarily to triage the issue. There seems to be no impact based on it. The issue keeps occuring with unrestricted access as well. And the only way to restore the radar sensor is to reflash the EPL
EverythingSmartHome
commented
3 months ago Can you share the settings when this happens? Also, does things like the LED control work? Just no radar data?
shresth45
commented
3 months ago Do you mean settings as shown in HA? The buttons for LED and Reboot work as expected. But everything other than the Illuminance value is not updating.
shresth45
commented
3 months ago I see the only way to get this working again is to connect via USB and reflash the firmware. Over Wireless does not resolve the issue. And the issue reoccurs at least twice a day. No changes on the network side. This started occuring only after I installed latest update on ESPHome 2024.07, but now rolling back to the previous version is not resolving it either
jsk-sct
commented
3 months ago I had the same kind of problem (sensor stuck at minus Y-values for example and didn't recognize when I walked in front of it) but tried the solution in https://github.com/EverythingSmartHome/everything-presence-lite/issues/98#issuecomment-2209154036 It seems to be working the last 24h so maybe give it a try
MikeDembek
commented
3 months ago I'm seeing very similar behavior following the 1.0.7 update - I'm using imperial units but the values seem to be identical to @shresth45's:
This is with HA 2024.7.3 on an HA yellow, ESPHome 2024.7.2 on both HA and the device firmware.
EverythingSmartHome
commented
3 months ago No change in 1.0.7 to cause this but definitely a bug with those values, will look into it
shresth45
commented
3 months ago I had the same kind of problem (sensor stuck at minus Y-values for example and didn't recognize when I walked in front of it) but tried the solution in #98 (comment) It seems to be working the last 24h so maybe give it a try
@jsk-sct Does this fix work long term? I went on the route to downgrade the entire EPL release to 1.0.3 (before http_request was introduced) using the manual yaml method (working stable for 3 days now)
jsk-sct
commented
3 months ago I had the same kind of problem (sensor stuck at minus Y-values for example and didn't recognize when I walked in front of it) but tried the solution in #98 (comment) It seems to be working the last 24h so maybe give it a try
@jsk-sct Does this fix work long term? I went on the route to downgrade the entire EPL release to 1.0.3 (before http_request was introduced) using the manual yaml method (working stable for 3 days now)
Yeah, it has been working for a week now and hasn't frozen on minus-values one time. I upgraded to 1.0.7 and it didn't change anything. I have noticed that the EPL has become a little more sensitive since I upgraded the sensor to 2.0.4 but that could be because had to loosen it before I upgraded to 1.0.3.
tkadauke
commented
3 months ago Any workaround? I have a whole lot of EP1s around the house, and one by one they seem to be falling into over into this mode where nothing updates.
I managed to get one back to work for a few hours by disassembling it and restarting it a few times. Not sure exactly what fixed it, but it's broken again after ~5 hours.
alexdw369
commented
3 months ago I have a bunch as well, all with the same 1.0.7, and all but one was stuck with the exact values previously described. I tried updating mmWave sensor firmware to 2.0.4 on my one working EP Lite and on a non-working...the only change is that now ALL of my devices are stuck with stale values.
EverythingSmartHome
commented
3 months ago Would you mind verifying if 1.0.8 changed anything for you?
tkadauke
commented
3 months ago I just updated to 1.0.8, and still have the same issue. I haven't updated the mmWave firmware yet since the HKLRadarTool app keeps crashing as soon as I want to do anything with it.
Any suggestions what else I could try?
shresth45
commented
3 months ago Just updating to 1.0.8 does not fix it completely. Currently I see 2 cases where this issue is fixed (EPL is working at least?)
Thanks for the reply, unfortunately I won't be much help here ... I left town for a few days, so my access is going to be limited to what I can see in the HA front end since I won't have physical access to the EPLs. Before I left, the only thing I noticed was that after allowing HA to update device firmware to 1.0.8 on two of the EPLs, neither would connect to HA due to a mismatch in encryption keys or something. I can grab a screenshot of the logs when I get to my destination and can hop on my computer. Also (and this is probably a "me" problem), I'm not super sure what the workflow is supposed to look like when flashing firmware using the everythingsmarthome web utility, and then connecting to HA. Am I NOT supposed to allow adoption through the ESPHome Addon? Because when I do that, it'll want to re-install a different configuration and the firmware will get reverted back to 1.0.7. Otherwise, I'm not sure how to obtain the API encryption key that HA asks for when adding the new EPL as an integration. I'll grab a screenshot of the logs and get them to you as soon as I am able. Thanks again for working on this. Alex … On Sat, Aug 3, 2024, 01:45 Everything Smart Home @.***> wrote: Would you mind verifying if 1.0.8 changed anything for you? — Reply to this email directly, view it on GitHub <#120 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AFNCQWCFZUHPWR7PJBMNTYLZPSKBHAVCNFSM6AAAAABLETXVYKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENRWGY2DCOJTHE . You are receiving this because you are subscribed to this thread.Message ID: <EverythingSmartHome/everything-presence-lite/issues/120/2266641939@ github.com>
I faced this exact issue with EPL in earlier releases as well, so I avoid using the HA GUI altogether. Updating from the ESPHome Addon GUI (tab or webui port, however you access) works properly. In the addon GUI, so long your yaml is referencing the master branch it will pull in the latest EPL release
MikeDembek
commented
3 months ago I bumped to 1.0.8 yesterday, then had to re-push ESPHome firmware before the EPL would connect to HA again, but so far I'm seeing it work as expected running HA 2024.7.4 and ESPHome 2024.7.3.
biodrone
commented
2 months ago This has been happening to my office sensor for a week or so now (and not to my living room or bedroom EPL) but it's just started happening to a customer since I upgraded them to 1.0.8, which now means it's a problem I need to fix... Sensor screenshots are below, I seem to be the only person in this thread with all 3 targets exposed but 1 & 3 are stuck at those values. I also tried downgrading to 1.0.4 but the build fails, and anything older than that doesn't seem to resolve and just builds 1.0.8.
Oddly when I reboot or reset the mmWave sensor the values change and get stuck as per the second image, then upon rebooting the whole EPL they revert back to the first image.
Initial:
Post mmWave reboot/reset:
I'm remote from the customer site so it's not simple to go and update the mmWave firmware physically. I know that's the only thing I haven't yet tried, is there a way to do this remotely?
biodrone
commented
2 months ago Another bit of info I've just realised, all of the devices of mine that are having this issue are from the original batch of EPLs, I have 2 that are working fine and they're both from the newest batch... Not sure if that makes a difference but figured it was worth mentioning.
EverythingSmartHome
commented
3 weeks ago I believe this should be resolved now by updating the EPL firmware, and also ensuring that the mmWave firmware is on 2.04 by using the HLKRadarTool app on Android or iOS. Please let me know if still an issue
All radar sensor data just stops populating altogether in HA. In the Esphome logs too I cannot see the sensor data peing updated. Tried this on 2024.6.6, 2024.7.0 ESPhome. Works fine after a firmware flash, then stops after a few hours.