Skip to content

Execution and Debounce

Arie J. Godschalk edited this page Nov 15, 2026 · 1 revision

Execution and debounce

Home > Execution and debounce

Contents: Choose a mode · Timing · Sequential · Compatibility · Limits

Debounce means limiting a burst of repeated requests. For example, several rapid sensor changes can produce one useful update rather than many.

Set Execution on the receiving This Flowcard started card.

Choose an execution mode

Homey option In everyday words
Default execution (none) Allow matching requests without debounce filtering.
Execute last one waiting (finish) At each interval, run the most recent waiting request; older waiting requests are skipped.
Execute at start (executestart) Run the first request immediately, then block further requests until the interval ends.
Execute at start ... finish with last one waiting (executestart_finish) Run the first immediately, then the latest waiting request at an interval boundary.
Sequential (sequential) Queue matching requests and allow each after the previous triggered Flow promise completes.

Homey's debounce labels include more explanatory words. The IDs above identify the options for advanced reference; you normally select their readable labels.

Debounce deliberately drops requests. Do not use it where every event must be preserved.

Timing and defaults

Debounce (ms) is in milliseconds. 1000 means one second. Missing or zero values use 1000 in the current implementation. Use a positive value.

The timer uses fixed intervals while there is activity. It does not restart the full waiting period after every new request.

For execute last one waiting, with 1000 ms:

0 ms: request A
200 ms: request B
800 ms: request C
about 1000 ms: run C

It does not wait until 1800 ms just because C arrived at 800 ms. This is an important difference from other tools also called debounce.

Sequential mode uses Flow completion rather than Debounce (ms).

Debounce state is shared by the app's saved name and trigger-size group. Multiple same-name receiving cards can interfere with predictable selection. Use one simple receiver for a first test.

Sequential is not a speaker-playback detector

The queue waits for the triggered Flow promise. A speaker action may finish as soon as it starts audio, before the sound ends.

For speech, a waiting Google Services condition can provide an estimated wait. Read its sound-before-speech guide and the original sequential speech example.

That is still not proof that a listener heard the announcement. Test with short, harmless messages and your actual destination.

Homey model and firmware differences

In 2023, community reports described Homey Pro 2023 resolving trigger execution differently from older Homeys, affecting returned values and sequential execution. The developer's follow-up said a firmware change was planned.

This manual does not infer that every current firmware still has that problem, or that it was fixed in an unspecified version. The source depends on Homey's trigger promises; a local source test cannot establish your firmware's behavior.

Run the small return test and sequential test on your Homey. If requests overlap or results arrive empty, include your model and firmware when asking for help.

Keep requests manageable

Queues and Return IDs live in app memory, not a durable job store. Restarting the app or editing receiving triggers during activity can disrupt pending work.

Waiting can hit Homey's action timeout. Historical advice mentions a 30-second limit; do not assume that exact limit applies to every current engine. Keep the first test short.

Avoid an uncontrolled loop that immediately starts itself again. Add a clear stopping condition, bound the number of requests, and test at a gentle rate before connecting real sensors.

Next steps

Clone this wiki locally