Room control
Sensors for AV spaces: motion, presence, light and contact
Before selecting a sensor, define the information needed for the space’s AV use. Motion detection, presence indication, light classification and contact state are different data; one label should not stand for all of them.
Choose the data you need
| Reference | Documented data | What it does not establish |
|---|---|---|
| SONOFF SNZB-03P | PIR motion and dim/bright evaluation when motion is detected | No people count or numeric lux reading from that classification. |
| SONOFF SNZB-06P | 5.8GHz radar presence detection; functions depend on gateway | No identification of people; do not confuse it with SNZB-06P24. |
| SONOFF SNZB-04P | Open/closed state from transmitter and magnet proximity | No confirmation of a locked door or access-control authorization. |
Ambient light: category or measurement
The SNZB-03P product page describes dim/bright classification when motion is detected and identifies gateways for that function. Confirm which entity reaches your platform and when it updates before deciding how to use it. Do not convert those categories into a lux figure or a measurement of light on the screen.
If a decision needs a numeric value, select a sensor documenting that measurement, its unit and verification criteria. Projection legibility needs representative content and conditions; a bright label does not confirm it.
Presence and the detection environment
The SNZB-06P manual warns about moving objects, fans and detection through some nonmetallic materials. It also states that functions depend on the gateway and that some gateways present it as a motion sensor. An entity name alone is therefore insufficient to interpret the data.
For a later review, define representative situations: a seated person, a moving object and recovery after communication loss. Record expected detection, received data and freshness. The final choice depends on these checks in the intended location.
A proposed use without counting people or safety functions
For a noncritical proposal, the AV interface could display reported data and request operator confirmation before changing presentation mode. Missing updates should be indicated rather than presenting a remembered value as current. Do not infer precise occupancy, identity or how long people remain.
- Model and firmware → documented detection type.
- Gateway/integration → entity, meaning and updates.
- AV interface → freshness indication and operator decision.
What to share when reviewing options
Describe the information you need and where it would be used. Share space photos without people or private information, label photos or a preliminary diagram even if models and dimensions are missing. Images, audio or real occupancy data do not need to be collected for an initial inquiry.
This scope covers noncritical AV use. These sensors are not proposed for fire systems, evacuation, safety, locks, machinery or motorized movement.
Useful questions about sensor data
Are motion and presence the same?
No. Review the exact model’s documented technology and behavior. An integration may use a similar label for sensors with different capabilities.
Does a closed contact mean the door is secured?
No. It reports the detected relationship between the sensor and magnet. It does not establish a locked door or replace a safety or security system.
Can I inquire before selecting a sensor?
Yes. Start with the information needed and the AV decision it would support, then compare models, platforms and required checks.