By default, if a sensor has not detected in 30 seconds, it will be marked as unoccupied. This is the state you will see in BACnet / MQTT etc for sensors as well as the value that will be used when calculating group occupancy states for the same services (ie, checking all sensors that target that group to see if any are occupied, in which case, the group is occupied).
In v2.2 and onwards, you can change this setting (it will affect all decisions of unoccupied for targets/individual sensors). First, you must enable Advanced settings.
Site Details->Settings, you must have enabled Advanced Control System Settings
Warning: Do not change other settings on this tab unless you are absolutely sure you know what you are doing!
You will then see the Advanced tab in the Control System view on the grid control. The Seconds to unoccupied field is available to change.
Setting the value very low (smaller than 10 seconds):
Occupancy sensors on our buses are generally set to report a maximum of 3-10 seconds in between. The more sensors are on the bus, the longer the report times will be. If you set the unoccupied time lower than the time they report, you could encounter issues where unoccupied is hit, despite the sensor detecting the whole time:
For example, you set it to 1 second and the sensor is set to update a maximum, every 3 seconds.
Sensor detects, status goes to occupied
1 second passes
Sensor is still detecting motion but cannot report for a further 2 seconds
Controller automatically sets the state to unoccupied (incorrect)
2 seconds passes as unoccupied
Sensor can send its next detection and does so.
Controller sets to occupied
Comments
0 comments
Article is closed for comments.