Repository navigation
Values and Returns
Home > Values and returned results
Contents: Types · Names · Sizes · Waiting · Return ID · Defaults
- Text contains words or other text, such as a room name.
- Number contains a numeric value, such as 42.
- Yes/No is a boolean: true or false. In a checkbox, checked means true.
Each size provides that many slots of each type. The 10-size starter can therefore send 30 values.
Optional values not supplied are filled with empty text, 0, or false. Larger receivers accepting smaller requests get those same defaults in the additional slots.
Triggername selects a name from the suggestions. Tag on the starter supplies a name as text, including a text tag from another card.
Use one, not both. If a selected name object is present, the implementation uses it before the alternative Tag field.
Names match exactly. demo-hello and Demo-hello are different, as are names with extra spaces. The app does not automatically turn similar names into the same event.
Save the receiving Flow to make its name available in suggestions. Selecting the suggestion stores the name correctly; typing without selecting it may not.
Use the same size on the starter and receiver for the simplest setup.
Overloadable → Use overloading lets a larger receiver accept a smaller request. For example, a 5-size receiver can accept a 1-size starter; its remaining values get defaults.
The opposite does not work: a 10-size starter is not routed to a 1-size receiver. The 1-size receiver has no Overloadable setting because there is no smaller active size.
For predictable debounce and returned results, start with one receiver per name and size. Reusing the same name in several receivers can start several Flows.
On a starter:
- Checked: the app waits for the triggered Flow promises, then returns any supplied results.
- Unchecked: it returns immediately with default results. Later Return cards cannot fill that already-completed request.
The current backend treats a missing value as waiting unless it is explicitly false. For return tests, explicitly select Yes/checked rather than leaving the option unset.
Waiting depends on Homey's completion behavior. It does not independently measure when a physical device finishes working.
Each starter request creates a Return ID, passed to matching receiving triggers. Connect that trigger's Return ID tag to the Return card's required Return ID argument.
Do not type a remembered number or use a device ID. This identifier belongs to this particular request and is not durable across app restarts.
A Return card supplies results but does not stop the receiving Flow. Place it at the end for a clear result. The waiting starter collects results after the triggered Flow promises complete.
If multiple Return cards run for one request, the first received result is kept. Avoid competing returns and use one clearly connected result path.
Every starter exposes Text 1 through 10, Number 1 through 10, and Yes/No 1 through 10 as output tags, regardless of its input size.
These are results sent back, not echoes of the values sent in. The larger output set lets even a small starter receive results from a larger Return card.
Without a matching Return card, or with Wait to Finish unchecked:
| Output | Default |
|---|---|
| Text 1 through 10 | Empty text |
| Number 1 through 10 | 0 |
| Yes/No 1 through 10 | false |
A successful Return card alone is not proof that the caller received its values. An expired, wrong, or non-waiting Return ID has no active waiting request to fill.
Support development - If Advanced Triggers is useful to you, you can support its
continued development through GitHub Sponsors,
Patreon,
PayPal, or
bunq.
Thank you!