ObstructionDetected Attribute within the Eve Cluster

[lboue]

For Eve MotionBlinds, ObstructionDetected attribute within the Eve Cluster

Boolean obstructionDetected 319422480 / AttributeId: 319422480 (0x00130a0010)

[jvmahon]

Have you considered using the ObstacleDetected bit (bit 5) within the Safety Status attribute 0x001A of the Window Covering cluster? That might let you get the information you need in a "standardized" way without having to add anything to Python Matter Server.

From Section 5.3.5.4 of the Matter Application Cluster Version 1.4.1 spec:

[lboue]

Have you considered using the ObstacleDetected bit (bit 5) within the Safety Status attribute 0x001A of the Window Covering cluster? That might let you get the information you need in a "standardized" way without having to add anything to Python Matter Server.

From Section 5.3.5.4 of the Matter Application Cluster Version 1.4.1 spec:

Yes, I noticed that. We can add the management of one or two alerts associated with the SafetyStatusBitmap bitmap.
But in principle, you should handle them all. It is mandatory in the specifications.
The only solution I have is to add one MatterDiscoverySchema per bit, i.e. 12 schemas. I don't think this is a very clean implementation. I haven't figured out how to manage this correctly in the Home Assistant integration.

[jvmahon]

The only solution I have is to add one MatterDiscoverySchema per bit, i.e. 12 schemas. I don't think this is a very clean implementation. I haven't figured out how to manage this correctly in the Home Assistant integration.

An option is to add the SafetyStatusBitmap as a new attribute of the window cover using the extra_state_attributes method. Probably not an ideal solution, but it gets you all the bits without having to add a dozen UI elements. I was going to use the estra_state_attributes with the Window Covering to add the targetPosition attribute; if you think adding the SafetyStatusBitmap as an attribute would be useful, reach me on Discord at "jvm" and I can do it at the same time.