Describe the bug
Matter 1.5 Occupancy Sensing Cluster (Cluster ID: 0x0406) introduces new feature flags for modern sensing modalities including Radar, AmbientSensing, Vision and Other. However, the backward-compatibility enumeration OccupancySensorTypeEnum only contains four legacy options: PIR, Ultrasonic, PIRAndUltrasonic and PhysicalContact. This enum is also explicitly marked "SHALL NOT be extended" in the spec.
my millimeter-wave radar occupancy sensor uses radar-only detection hardware with no PIR module. Its FeatureMap only enables the Radar flag, yet there is no matching value in the existing enum. The backward compatibility fallback rules defined in Section 4.16.1 of the Matter Core Specification fail to provide a valid mapping for radar-only devices. This mismatch triggers errors in official Matter certification test tools and blocks full Matter 1.5 compliance. Additionally, Matter controllers/clients cannot identify radar, vision or ambient-sensing devices by reading the OccupancySensorType attribute.
Severity: Medium – causes functional limitations and backward compatibility gaps.
Steps to reproduce the behavior
- Prepare a radar-only occupancy sensor without PIR hardware (SONOFF millimeter-wave radar presence sensor).
- Implement the Occupancy Sensing Cluster based on Matter 1.5 specs (Doc 23-27350 Rev 1.5 & Doc 23-27349 Rev 1.5).
- Configure the device FeatureMap to enable only the Radar modality feature flag, without enabling PIR or ultrasonic related features.
- Attempt to match the device’s FeatureMap to a valid OccupancySensorTypeEnum value following the official backward compatibility mapping rules.
- Run the official Matter certification test suite to perform spec compliance verification.
- Observe test results: the tool throws a mapping mismatch error and halts the certification process.
Expected behavior
- The Matter 1.5 specification shall define valid OccupancySensorTypeEnum entries for newly added modalities: Radar, AmbientSensing, Vision and Other.
- Complete backward compatibility mapping logic shall be supplemented to assign a legal enum fallback value for devices with only new sensing modality flags in FeatureMap.
- Either remove the "SHALL NOT be extended" constraint on OccupancySensorTypeEnum, or introduce a new dedicated attribute to identify Matter 1.5 new sensor types.
- Radar and other new-type occupancy sensors shall pass all certification checks without mapping errors. Matter clients shall correctly recognize the underlying sensing technology via cluster attributes.
Log files
UI_Test_Run_2026_06_29_07_33_33.txt
PICS file
No response
Screenshots
No response
Environment
version:2.14+fall2025
sha:e20beac
Additional Information
No response
Describe the bug
Matter 1.5 Occupancy Sensing Cluster (Cluster ID: 0x0406) introduces new feature flags for modern sensing modalities including Radar, AmbientSensing, Vision and Other. However, the backward-compatibility enumeration OccupancySensorTypeEnum only contains four legacy options: PIR, Ultrasonic, PIRAndUltrasonic and PhysicalContact. This enum is also explicitly marked "SHALL NOT be extended" in the spec.
my millimeter-wave radar occupancy sensor uses radar-only detection hardware with no PIR module. Its FeatureMap only enables the Radar flag, yet there is no matching value in the existing enum. The backward compatibility fallback rules defined in Section 4.16.1 of the Matter Core Specification fail to provide a valid mapping for radar-only devices. This mismatch triggers errors in official Matter certification test tools and blocks full Matter 1.5 compliance. Additionally, Matter controllers/clients cannot identify radar, vision or ambient-sensing devices by reading the OccupancySensorType attribute.
Severity: Medium – causes functional limitations and backward compatibility gaps.
Steps to reproduce the behavior
Expected behavior
Log files
UI_Test_Run_2026_06_29_07_33_33.txt
PICS file
No response
Screenshots
No response
Environment
version:2.14+fall2025
sha:e20beac
Additional Information
No response