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

Create a 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.
4. Add an action node, then connect the event to it.
5. Save the rule and enable it after testing.

Available event types include:

• Trigger started.
• Countdown started, tick, aborted, or finished.
• Warmup started.
• Capture started, finished, or aborted.
• Dataset created or newly available.
• Transfer completed.

Conditions and timing

An event node can have conditions. Conditions compare an event field using equals, not equals, contains, greater than, or less than. For example, a countdown tick rule can run only when remaining equals 3, or a capture rule can match a particular camera zone.

Use the rule settings to control repeated events:

• Any (OR): start when any connected start event matches.
• All (AND): wait until every connected start event has matched.
• Debounce: ignore repeat fires during the configured time window.
• Delay: wait after the event before running the action.
• Stop when: abort a running sequence when another event occurs, optionally with its own conditions.

Actions

A rule can connect to these actions:

• Trigger a sequence: run one of the saved sequence workflows.
• Play a light preset: start a preset from a selected light group.
• Set a light color: broadcast a color and optional brightness to available light nodes.
• Run a light effect: play a transient effect with a frame count and framerate.
• Drive a GPIO pin: set a pin high or low, or pulse it for a duration.
• Play a sound: preview an uploaded MP3 or WAV file, then play it once or in a loop.

Rules can contain comment nodes for notes about wiring, event timing, or the reason for a condition. Keep rules focused: put a longer, reusable workflow in a sequence and leave the rule responsible for deciding when it starts.

Test before enabling

Run the target sequence directly first. Then trigger the source event under controlled conditions and watch the rule state and run log. Verify that the expected camera groups, lights, GPIO nodes, and sound assets respond before enabling the rule for an event.