Why are my sensors not triggering?

If your sensors are not triggering, please check the following steps.

Check Sensor Configurations

In Instance->Occupancy Sensors, verify that the sensors are still properly configured and targeting the correct groups or devices.   Ensure the behaviour has the tickbox ticked and you have selected your behaviour 

Ensure that the target is not in a scene that has been set as a disabled scene (unticked).  

Check that your controller is not in a profile that has the configurations disabled (ie, the fire alarm profile).  If the controller is in the fire alarm profile, take steps to change the profile (if the emergency has completed).

Check Trigger Maps

Examine trigger maps: Ensure the trigger maps for these sensors are correctly set up and pointing to the appropriate sequences for all profiles.  There should be a trigger map entry for each target for the profile you are in of type Sensor or Sensor and External Lighting Command

Check Sequences

Review sequences: Check that the sequences triggered by these sensors are still intact and configured correctly.  Check that there isn't any logic that could leave the lights in an unexpected state.  It is very easy to configure a sequence that does not function correctly (ie, you might configure a sequence that sends recall minimum at the warn time and then does not recall max when someone walks in the room, but does reset the time - at which point the sequence is running but has not returned full light to the target.

Simulate Occupied Triggers

Right click on a non functioning sensor and choose Simulate Occupied and see if the lights turn on.  This will create a sensor occupied message for the controller to process without using the occupancy sensor.  If your lights turn on, it is likely that your triggers and sequences are functioning.  You may then check in the monitor to see if you are getting occupied messages from your sensors.

If you check the monitor during this simulation, you should see the occupancy event Occupancy Sensor: OCCUPIED, and then trigger messages for the number of targets this sensor has, followed by a green line for the sequence trigger (and some lighting commands from the sequence if the sequence wasn't already running).  In this particular output, you can see that there is an override on G1 and G2 that may be responsible for why you are not seeing lighting commands on that group.  G5 has no such override and the sequence is started on G5 and sends the RECALL MAX.

Inspect network connectivity

If you are using targets to remote controllers, ensure that all controllers are communicating properly with each other.

Verify group assignments

Confirm that the lights/relays are still assigned to the correct groups that the sensors are targeting.  If on site, use the app to send commands to the group and verify that the lights still act.

Check for overrides

Look for any active overrides that might be preventing the sensors from controlling the lights.  Use the Simulate and watch the monitor to see if you see TRIGGER DENIED messages.  Overrides do not propagate through reboots so it is possible to clear overrides by rebooting the controller if this is not too much of a service interruption.

Analyse Dali Monitor

The monitor is a daunting prospect but it should give very good context as to what is happening.

If possible, examine the system logs around the time when the sensors should be triggering to see if there are any error messages or unexpected behaviours.  If you put OCCUPIED into the filter box at the top right, you will only see the occupied messages.

Contact Support

If these steps don't resolve the issue, it may be worth reaching out to zencontrol support with detailed information about the problem, including any error messages, logs, and the steps you've already taken to troubleshoot.

Remember to document any changes you make during troubleshooting, and be cautious about making significant changes on a live site without proper testing or backup.