Hi,
I would be able to specify the time delay, in seconds, before the PIR sensor changes to its unoccupied state after the last detection of occupancy.
There is a Matter attribute for that:
2.7.6.6. PIROccupiedToUnoccupiedDelay Attribute
This attribute SHALL specify the time delay, in seconds, before the PIR sensor changes to its unoccu
pied state after the last detection of occupancy in the sensed area.
Could you add the attribute PIROccupiedToUnoccupiedDelay for next firmware release?
Eve motion sensor implements it already
Matter 1.4.2 note
With the introduction of new sensor modalities in cluster revision 5, the indication for those modalities SHALL be done using feature bits. Indication of those new modalities is not feasible via the legacy attributes OccupancySensorType and OccupancySensorTypeBitmap. Servers SHALL set these attributes for backward compatibility with clients implementing a cluster revision <= 4 as described in OccupancySensorType and OccupancySensorTypeBitmap Attributes. Clients implementing a cluster revision >= 5 SHOULD use the server’s ClusterRevision attribute, and SHOULD ignore these legacy attributes.
With the same revision 5, the attribute HoldTime (along with the HoldTimeLimits) is used to determine the reporting when occupancy is no longer detected. This replaces the 9 legacy attributes PIROccupiedToUnoccupiedDelay through PhysicalContactUnoccupiedToOccupiedThreshold.
Servers MAY use the applicable attributes from this set of legacy attributes if and only if HoldTime is supported (see Attribute table and the corresponding explanation for details on conformance).
For the case of a server which supports none of the modalities supported in ClusterRevision <= 4 (i.e. none of PIR, US and PHY), specific mappings for the legacy attributes OccupancySensorType and OccupancySensorTypeBitmap are provided below, representing this sensor as a PIR sensor for best-effort backward compatibility. For this case, the legacy timing attributes linked to PIR (i.e. PIROccupiedToUnoccupiedDelay through PIRUnoccupiedToOccupiedThreshold) apply.
Regards
4 Likes
@ludovic_boue Hi there,
Thank you for bringing up the idea of adding the PIROccupiedToUnoccupiedDelay attribute to the Aqara Motion and Light Sensor P2. This feature could indeed offer more customization for users who want precise control over when the sensor updates its occupancy status. It’s great to hear that you’re considering how this could align with the existing functionalities and standards, such as those implemented by the Eve motion sensor.
Currently, the reference information I have doesn’t specifically mention the implementation of the PIROccupiedToUnoccupiedDelay attribute for the Aqara Motion and Light Sensor P2. However, I understand the importance of such a feature for enhancing user experience, and your suggestion seems like a valuable addition.
I appreciate your suggestion and would encourage you to share it with the Aqara development team. Community input like yours is crucial for driving improvements and innovation. Please feel free to continue the discussion and share any additional thoughts or insights you might have.
Warm regards,
1 Like
Hi. Thanks for the suggestion, I’ll pass it on for consideration.
2 Likes
Hi, thank you very much for your feedback and valuable suggestions. Indeed, this feature is already supported under the new Matter protocol, and we have developed support for it as soon as possible. We believe that our users will be able to see and use it in the App in the near future. We are always committed to providing users with the most comprehensive matter support. Thank you for your detailed suggestions!
4 Likes
Thanks, since the new firmware is already released and I asked in other threads without success, can you provide any insight on:
- Can the P2 motion sensor firmware be updated in SmartThings or Google Home? They support Matter OTAs but they don’t look for them in the DCL like Home Assistant.
- What are the new attributes added and supported values? I assume they’re the standard
CurrentSensitivityLevel and HoldTime.
Attributes for OccupancySensing:
2 Likes
Thanks, that confirms the HoldTime part.
I guess it also includes the BooleanStateConfiguration cluster for the sensitivity level configuration with CurrentSensitivityLevel, which is the other new feature of the firmware.
Edit: I’m trying to request SmartThings to add support for the new features and the firmware update for the Aqara P2 Motion Sensor. I’m sure Aqara can suggest it too since they’re WWST partners.
Yes BooleanStateConfiguration Cluster on Endpoint 1 too:
1 Like
