-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
All motion detection from any Third Reality device doesn't update expose after update to v1.37.1-1 #22575
Comments
I have the same problem with a DIY device. All properties work - only occupancy remains on motion in inactive (or null) state. |
Can confirm this issue on all my Third Reality Multi-Function Nightlights (3RSNL02043Z). Lux and light controls work, but motion sensing no longer works. Reverting to 1.37.0 gets motion sensing reporting again. |
I'm observing the same! |
I'm noticing something similar with Aqara P1 motion. In my case, the issue is caused by the fact that the illuminance_lux entity is updated after the motion entity resulting in my automation to not work properly.
in the z2m logs panel I see:
In both cases I have good values, however when my automation runs I notice that motion entity triggers from 'off' to 'on' and the illuminance_lux entity has the old value (not the one as we see from the above logs. I did a fix where I have a new trigger based on illuminance_lux entity with a delay of 1sec to catch this use-case; however will be nice if the entities are updated accordingly. I'm not 100% sure, but I think this issue started with version 1.36.1 |
Same here. Also the door sensor stopped working at the same time |
Same here for my devices. No motion reporting on 1.37.1, everything else appears to work. |
Regarding the third reality devices, could you provide the debug log when motion should be detected? See this on how to enable debug logging. |
I think this is what you need. Let me know if you need something else, or a more specific log line. |
This is something different, can you:
|
Got it. So I think this is actually what you need :-P
Guessing |
I think this has already been fixed in Koenkk/zigbee-herdsman-converters#7521, can you check with the latest dev branch? |
+1 on this for a Third Reality 3RSNL02043Z. I thought I had misconfigured it. Trying to sort out how to switch to edge to test. |
Dev branch works, at least for my Third Reality 3RSNL02043Z. |
Sounds like we have a verification that it's fixed in the dev branch. When can we expect the fix to be released? Or do we need more individuals to test? |
Next release is on Saturday! |
What happened?
After update to v1.37.1-1, no Third Reality device is updating motion detection expose.
What did you expect to happen?
Motion detection normally works.
How to reproduce it (minimal and precise)
Update to v1.37.1-1 (doesn't work)
Revert to previous release (works again)
Zigbee2MQTT version
v1.37.1-1
Adapter firmware version
latest
Adapter
Sonoff P 3.0
Setup
Home Assistant Add-on
Debug log
No response
The text was updated successfully, but these errors were encountered: