Rules connect Camera Server events to actions. A rule starts when an event node receives a matching event, then follows the connected action nodes.

Create your first rule

1. Open Rules and Sequences and switch to Rules.
2. Select New rule and give it a clear name.
3. Add an event node and choose the event that should start the rule. For a first test, use Capture started.
4. Add an action node, such as a sound or light preset.
5. Connect the event node's output to the action node's Start input.
6. Save the rule while it is disabled.
7. Test the source event and confirm that the action responds.
8. Enable the rule only after the complete event path works.

An enabled rule must have at least one event connected to an action with a Start edge. Saving an incomplete graph as a draft is allowed, but it cannot be enabled.

Add a stop event

To end an action when another event arrives, add a second event node and connect it to the action's Stop input. For example, connect Capture started to Start and Capture finished to Stop for a light or sound action.

Stop behavior depends on the action. It aborts a running sequence, turns off a light output, sets a GPIO pin low, or stops a sound. A sound node also supports a Pause connection.

Before enabling

• Run a target sequence directly before triggering it from a rule.
• Check that the referenced sequence, light group, light preset, GPIO node, or sound asset exists.
• Use a condition when the event should apply only to one zone, group, countdown value, or dataset.
• Keep the rule disabled while changing its graph.
• Watch the rule state and run log while testing.

See Rule graph concepts, Events and conditions, and Actions for the complete reference.