Repository navigation
Flow Triggers
Home · Conditions · Actions
Triggers are the When part of a Flow. For chronograph-specific triggers,
choose a name using the picker or name field; supported triggers also accept
* in the name field. See names and wildcards.
Browse the Triggers index for a dedicated page for every current trigger card.
- Every interval
- Lifecycle triggers
- Duration and step triggers
- Transition steps and tokens
- Other trigger tokens
Use Every interval to start a Flow repeatedly without creating a timer, stopwatch or additional Flow. Enter a fixed whole number and choose seconds, minutes, hours or days. The shortest interval is one second. For example, Every 5 minutes runs its Flow every five minutes.
Flows with equivalent intervals share a schedule, so a newly added Flow joins the existing schedule. Homey runs only enabled matching Flows. Intervals are measured from the schedule's start, not aligned to the clock.
The next deadline is saved across app and Homey restarts. If it has not passed, the remaining time is preserved. If it passed while the app was stopped, the trigger fires once after startup and begins a fresh interval; missed runs are not replayed. Timing is best-effort and may be delayed when Homey is busy.
| Card | Types | When it fires |
|---|---|---|
| … is started | Stopwatch, timer, transition | A new chronograph is started. Resuming a paused one does not trigger it. |
| … is paused | Stopwatch, timer, transition | The running chronograph is paused. |
| … is stopped | Stopwatch, timer, transition | It is explicitly stopped. |
| … is finished | Timer, transition | It reaches its target duration. |
Stopwatches do not finish automatically. A timer that finishes fires the finished trigger, not the explicit stop trigger.
Example — fan shutdown
- Start a timer named
Bathroom fanfor 10 minutes in one Flow. - In another Flow, use Timer is finished for
Bathroom fan. - Add your fan's Turn off action.
| Card | Meaning |
|---|---|
| Stopwatch reached a duration | Fires at a specified elapsed stopwatch duration. |
| Timer reached a remaining time | Fires when the specified time remains on the countdown. |
| Timer reached an elapsed duration | Fires when the specified time has elapsed since the timer started. |
| Transition reached a step | Fires at the start, intermediate steps, and the end of a transition. |
For a 10-minute timer, a 2-minute remaining trigger occurs around minute 8; a 2-minute elapsed trigger occurs around minute 2. Configure and save the enabled threshold Flow before starting the timer or stopwatch: the app attaches the saved thresholds when the chronograph starts. If you change a threshold, start a new chronograph to use the updated configuration.
Example — early warning: Use Timer reached a remaining time, name
Oven, time 2 minutes, followed by a notification action. Use a separate
Timer is finished Flow for the final notification.
The transition step trigger supplies name, elapsed seconds, the interpolated value, and first / last flags. It fires at the initial value, intermediate steps and final value. Use the value token in a device action that accepts the corresponding numeric range; check that your device uses the same scale before using it.
For example:
- Create a Flow triggered by Transition reached a step for
Living room dim. - Set a compatible light's dim level to the trigger's value token. Save and enable the Flow.
- In another Flow, start transition
Living room dim, from0to1, in10steps over5minutes.
The first and last flags can distinguish the endpoints. Very short transitions may use fewer steps than requested because step intervals are limited.
Lifecycle and threshold triggers provide the chronograph name and, where offered, a seconds token. Its meaning depends on the card: start cards report the target duration; elapsed/remaining threshold cards report their configured threshold. Timer pause and stop cards report remaining time. Inspect the token labels in Homey when building the Flow, as meanings differ by type and card.
Support development - If Chronograph is useful to you, you can support its
continued development through GitHub Sponsors,
Patreon,
PayPal, or
bunq.
Thank you!