When creating event-to-actions for license plate reads, you can specify additional conditions based on Sharp analytics to trigger an action. For example, you can specify that an action occur only when the plate number contains “123”, or the vehicle is traveling at a certain speed.
[PlateNumber] = "ABC123"
. To
know more about the operators and identifiers that can be used, see Elements used in event-to-action conditions for license plate reads.[PlateNumber]
."ABC123"
.[Speed] > 20 AND [Speed.unit] = "mph") OR ([Speed] > 50 AND [Speed.Unit] =
"km/h"
) the AND operator takes precedence.[PlateNumber] contains "123" AND !([PlateState] = "QC")
, any plate
reads with a plate number that contains the value "123" and a plate state other than
"QC" will trigger an action.Sharp analytics are not generated 100% of the time. An event-to-action might not be executed if the Sharp is not able to generate the analytic specified in the condition. For example, if the condition is [Speed] > 50 and the Sharp cannot produce a value for speed, Security Center will evaluate the condition as being false and the action will not be executed.
When the outputs of an LPR Processing Unit are used to control building access through event-to-actions in Security Center, rebooting the LPR Processing Unit causes the outputs to activate which could lead to the opening of the access point. This output behavior is not ideal for access control, but is required in order to power the in-vehicle computer on vehicle startup. Create an event-to-action in Security Center that will send a "Normal" state to the outputs following a "Unit Connected" event. The access points will still open, but will close shortly afterward.
To add a condition when creating an event-to-action for a license plate read: