| Parameter | Current design |
|---|---|
| Matter transport | Thread (requires a Thread border router in the home network) |
| Matter device type | Occupancy Sensor |
| Detection | Passive infrared, with pet-immunity configuration |
| Sensitivity | Adjustable per installation, so one SKU covers corridors and small rooms |
| Mounting | Wall and corner mounting; magnetic bracket option |
| Power | Battery — cell type confirmed at design freeze |
| Certification status | In development |
| Item | Detail |
|---|---|
| Device type | Occupancy Sensor |
| Core cluster | Occupancy Sensing — reports occupancy state to the ecosystem, with configurable reporting behaviour |
| Reporting behaviour | Holding time and reporting interval are the two settings that decide both responsiveness and battery life. Both are exposed as configurable values rather than fixed in firmware, because the right answer depends on where the sensor is installed. |
| Endpoints | Single functional endpoint plus the root node. |
| Transport certification | Thread, with inheritance checked from the radio module before design freeze — the same approach as on our contact sensor. |
Battery life claims are the least trustworthy number on most sensor datasheets, because they depend entirely on the duty cycle. Our approach is to state the assumptions instead of the headline:
| Variable | Why it dominates the estimate |
|---|---|
| Motion events per day | Each detection triggers a radio transmission. A corridor sensor in an office triggers orders of magnitude more often than a room sensor in a home. |
| Reporting interval and holding time | Longer intervals and holding times reduce radio activity substantially, at the cost of responsiveness in automations. |
| Thread network quality | A device far from a border router retransmits more, and each retransmission costs energy. |
| Temperature | Cell performance falls in cold environments, which matters for unheated spaces. |
| Item | Detail |
|---|---|
| MOQ | Sampling for design partners at low volume; production MOQ confirmed once the configuration is fixed. |
| Available now | Evaluation samples for design partners. |
| Expected availability | Production follows certification; a dated window is given in the quotation. |
| Customisable | Detection lens and range, pet-immunity threshold, sensitivity curve, enclosure and finish, mounting bracket, packaging and branding. |
| Certification ownership | Your Vendor ID or transferred to you, agreed before the project starts. |
Why contact sensors and PIR detectors are paired for intrusion detection, and what changes under Matter.
The companion sensor on the same Thread platform.
Deployment scenario decides sensitivity, holding time and battery expectations. Give us the scenario and we will size the configuration.