Rules and sequences work together, but they solve different problems.

Sequence: what should happen

A sequence is a reusable workflow. It runs a list of steps in order and can coordinate cameras, lights, GPIO nodes, and timing. Use a sequence when you want to describe the actions themselves, such as warming up cameras, capturing several groups on a shared timeline, changing a camera setting between shots, running a timelapse, or playing a light and GPIO pattern.

Rule: when should it happen

A rule listens for a Camera Server event and starts an action when that event matches. The event can be a trigger, countdown, warmup, capture, dataset, or transfer event. A rule can run a sequence, play a light preset or effect, set a light color, drive GPIO, or play a sound.

Use conditions when an action should only run for a particular camera group, zone, dataset, countdown value, or other event field. You can also set a debounce window, add a delay before the action, and choose an event that stops a running sequence.

A practical way to build automation

1. Create or restore a sequence that performs the physical workflow.
2. Run the sequence manually and check the run log, timing, camera responses, and node outputs.
3. Create a rule for the event that should start it, then connect the event to the sequence action.
4. Add conditions if the rule applies only to one group, zone, countdown beat, or dataset state.
5. Enable the rule only after testing the complete event flow.

A sequence can be run directly from the Sequences page or started by one or more rules. A rule is not a replacement for a sequence: it is the event-to-action layer around it.