Start->Stop By Timeout
Start->Stop by Timeout runs one action on the first trigger, keeps an active timer, optionally prolongs that timer on repeated triggers, and runs another action after the quiet period expires.
Build an active-while-events-continue workflow
Use this action when a detector, schedule, manual control, or Event Manager rule should turn something on once and turn it off only after activity stops. It is a good fit for recording bursts, alarm outputs, temporary high-sensitivity modes, and logical presence windows.
The most important design decision is whether repeated triggers should prolong the active period. Keep Enable prolongation enabled for motion, sound, or other bursty sources; disable it when the first trigger must define a fixed stop time.
Choose the start side
Set Start action to the action that should run only once at the beginning of the active window. Common choices are Action on Task, Action on component, Set task state, Play audio, or an action group.
Choose the stop side
Set Stop action to the matching action that restores the normal state after the timeout: stop recording, disable a relay, restore normal sensitivity, or stop an auxiliary process.
Set the quiet period
Use Delay (ms) as the required silence or inactivity period before the stop action runs. Avoid very small delays for noisy high-frequency rules.
Configuration parameters
| Parameter | Required | Description | Default |
|---|---|---|---|
Title | Yes | Display name of the action. Use a name that describes the active window, for example motion recording latch, siren timeout, or high sensitivity window. | None |
Start action | Yes | Action task executed immediately when the first trigger starts a new active cycle. | None |
Stop action | Yes | Action task executed when the active timer expires. | None |
Enable prolongation | Yes | When enabled, repeated triggers during the active cycle move the stop time forward. When disabled, the stop time is calculated only from the first trigger. | Enabled |
Delay (ms) | Yes | Timeout in milliseconds before Stop action runs after the last relevant trigger, or after the first trigger when prolongation is disabled. | 1000 |
Start once, then stop after silence
On the first trigger, the action runs Start action and creates an internal timer. Repeated triggers during the active period do not run the start side again. If prolongation is enabled, those repeated triggers only move the stop time forward.
When the timer expires, Stop action runs, the internal timer is cleared, and the next trigger can start a new cycle.
Start edge
The start action is executed once per active cycle, which prevents repeated start commands during one activity burst.
Prolongation
With prolongation enabled, each repeated trigger updates the stop time to the current time plus the configured delay.
Stop edge
The stop action runs after the active period expires and resets the cycle state.
Use active windows for bursts and temporary modes
Activity-controlled recording
Point Start action to a task or component start action, and Stop action to the matching stop action. With Enable prolongation on, motion or sound events keep the recorder active until no events arrive for Delay (ms).
Light, siren, or relay control
Use the first event to turn on an external output and automatically turn it off after a quiet period. This works well for local alarms, lighting, deterrent devices, and integrations exposed through actions.
Temporary high-sensitivity mode
Use Start action to apply a high-detail profile or start extra processing, then use Stop action to restore the normal profile after events stop.
Presence or session window
Maintain a logical active state while repeated events continue, for example person present, vehicle detected, operator connected, or door activity in progress.
Start once, stop later
Disable Enable prolongation when only the first trigger should start the activity and the stop action should run after the original timeout regardless of additional triggers.
Graceful shutdown after bursts
Keep Enable prolongation enabled for noisy detectors so downstream work does not start and stop repeatedly during one activity burst.
Paired action macro
Combine task lifecycle actions, component lifecycle actions, Set task state, Play audio, or Execute action group as the start and stop sides when the on/off parts need multiple side effects.
Operational notes
Start action runs once per cycle
Start action is executed only when there is no active timeout. Repeated triggers during the active period do not run it again.
Stop action clears the cycle
Stop action is executed when the timer expires. After it runs, the internal timer is cleared and the next trigger starts a new cycle.
Prolongation changes stop time
With Enable prolongation enabled, each repeated trigger moves the stop time to the current time plus Delay (ms).
Fixed timeout ignores repeated triggers
With Enable prolongation disabled, repeated triggers do not change the stop time. The stop action runs relative to the first trigger of the current cycle.
Stop uses the first trigger context
The stop action uses the execution context captured from the trigger that started the cycle. Later trigger events do not automatically replace that context.
Timeout checker frequency
The internal checker wakes periodically at roughly one tenth of the configured delay, with a minimum check interval of 10 ms. Avoid very small timeout values for high-frequency rules.
Targets must be valid actions
Both selected targets must be action tasks and must be running when called. If a selected action is removed or stopped, the start or stop side will not perform the expected operation.
Avoid trigger loops
Avoid wiring the start or stop side back to actions that immediately retrigger the same logic. Use cooldowns and specific Event Manager conditions to prevent loops.