Koenkk
`no_occupancy_since` for Aqara RTCGQ13LM
What happened?
This is an exact "clone" of the issue #11183 that was opened (and fixed) for the Philips Hue occupancy sensor.
Now the behaviour (that was originally present and later changed for the Philips Hue sensor) is being observed with the newly bought Aqara RTCGQ13LM high precision motion sensor (AKA lumi.motion.agl04).
Just like the fixed Philips Hue, the RTCGQ13LM sensor is capable of sending occupancy: false but the behaviour of the no_occupancy_since is not the same between these two sensors now. Aqara starts its "no occupancy" timer from the moment when occupancy: true has been sent out. The Philips sensor (correctly) starts counting from the moment when occupancy: false has been detected and transmitted.
We already discussed at length the reasoning behind it (found in the Philips issue #11183) and came to the conclusion that all motion sensors that are capable of transmitting occupancy: false (which actually are very few) should do what Philips Hue does now. This particular (high precision) Aqara sensor happens to be one of those capable sensors and should then be made consistent with Philips Hue in how the no_occupancy_since is calculated.
The frontend description for the no_occupancy_since setting also differs currently between the two sensors, so it needs to be updated for RTCGQ13LM if the behaviour is changed to match Philips Hue (if that's not handled automatically).
Zigbee2MQTT version
1.27.2 commit: 7dc48fb6
Adapter firmware version
20220103
Adapter
LAUNCHXL-CC1352P
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "Published by a pub.dev verified publisher"){kind=small}
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days