Camera Rules and Alerts
Use Kilo Lens camera motion readings in a rule to raise an operational alarm when movement appears in a selected area.
A Lens camera supplies a motion reading that Kilo's Rules Engine can use like other sensor readings. This makes a camera part of an operational workflow: movement at a selected entrance can cause a rule to raise an alarm for the team responsible for that site.
First connect the camera and configure its motion zone. You also need permission to create rules and alarm definitions.
How do I prepare the alarm definition for a camera alert?
In Alarm, create the definition that the rule will raise. For example, name it Entrance activity and write a message that identifies the area requiring attention. Configure recipients, channels, schedule, and suppression for the intended response. Follow Alarm Definitions for those settings.
How do I build a motion rule for a camera?
Open Rules engine and create a rule.
Configure Start with Sensor reading.
Select the camera in Device, then choose Camera motion in Sensor.
Add an Exclusive Gateway to distinguish detected movement from a false motion reading.
Set the outgoing condition for the motion branch to
vars.value == true.Connect that branch to Set Alarm and select the alarm definition you prepared.
Connect the action to End, and use a default route to End for the non-motion branch.
Save, build, and deploy the rule through the normal rule lifecycle.
vars.value is the value supplied by the selected sensor. For the camera's motion sensor it is a boolean: true means motion is detected. A false reading can mean no motion, but it is also sent when the camera goes offline; use Camera status to distinguish a quiet scene from a disconnected camera.
How do I test a camera alert before enabling notifications?
Use the rule's debugging tools with external actions mocked or skipped while checking the flow. Then test the actual camera by moving inside and outside its selected area. Enable intended delivery only after confirming the rule and alarm configuration.
The simple rule above raises an alarm on motion. It does not automatically resolve an existing incident when the next reading is false. Configure the appropriate clear behavior if that is required, and review trigger timing.
Manually resolving an incident does not change the camera's reading. A condition that continues to qualify can raise another alarm according to the configured trigger and suppression behavior.
How do I monitor a camera's connection?
Create a separate rule with Start → Sensor reading, select the camera, and choose Camera status. This reading is text rather than a boolean. A branch with vars.value == "offline" can raise a connection alarm so a missing feed receives attention. Test the recovery path as well as the offline path before enabling notifications.
Camera sensors are selected through the Sensor reading trigger. Readings can be repeated periodically even when their value has not changed; they are not only motion-start or motion-stop events. Combine conditions with the rule's timing settings and alarm suppression to avoid unwanted repeated notifications. Clearing an alarm needs an explicit clear action; neither a false reading nor a restored connection automatically clears an incident raised by the example rule.
Last updated