Repository navigation
Troubleshooting
Home > Troubleshooting
Contents: Missing name · No receiver · Empty results · Overlap · Timeout · Unexpected filtering
Save the receiving Flow, reopen the sender's name field, and type the name again. Select the suggestion rather than leaving unselected text.
Check card sizes. A smaller starter only offers larger receivers when they have Use overloading enabled. Match sizes for the first test.
Confirm the fix: the sender can select the same saved name and the receiver creates your test notification.
Check exact spelling, capital letters, and spaces. Use only Triggername or the alternative Tag field, not both.
Confirm the receiver is saved and enabled, the execution path is connected, and the trigger size matches. Default execution avoids debounce intentionally skipping a test request.
An unknown name can finish without running a useful receiver. A green starter alone is not proof the expected Flow ran.
Confirm the fix: use the first test and look for its exact notification.
- Explicitly check Wait to Finish on the starter.
- Choose a Return card, not another starter.
- Drag the receiving trigger's Return ID into the Return card's required ID field.
- Fill in the result fields.
- Read the starter's output tags after it, not its original input fields.
- Use one Return path and keep the receiver short.
- Test normally after saving, then check model and firmware differences.
All starters expose 30 result tags. Unused results are empty text, 0, and false. They are not copies of input values.
Confirm the fix: the small return example produces Result ready. and 7.
The developer specifically recommended an explicit Wait to Finish choice in a 2026 return-value discussion.
Set Sequential on the receiving trigger. Begin with one receiver per name and size.
Check whether the receiver's actions finish before the physical operation does. A play-URL card may finish while the audio is still playing.
Test with a simple one-second delay and notifications before adding a speaker. If those still overlap, collect your Homey model, firmware, and app version; the queue depends on the Flow engine's trigger completion promises.
Confirm the improvement: short test requests run one receiving branch at a time. That still does not prove exact speaker timing.
Look for long delays, a receiver that starts itself without a stop condition, or another waiting action that never completes.
Remove those operations from the first test. Waiting can exceed Homey's action timeout. Unchecking Wait to Finish avoids waiting but also means you cannot collect later returned results.
Confirm the fix: the small receiver completes and the sender's next card runs promptly.
Do not restart the app in the middle of important work: queues and Return IDs are held in memory and can be interrupted.
Check the chosen option and unit. A missing or zero interval uses 1000 ms.
This implementation uses interval boundaries, not a timer reset after every request. Execute at start and execute last one waiting have different outcomes.
Start with one named receiver, Default execution for basic connectivity, then the three-request debounce test.
Confirm the result: the expected first or latest request runs at the interval boundary. Older requests being skipped is the purpose of debounce, not an error.
Include app version, Homey model and firmware, card sizes, execution choice, and whether you tested after saving or only in the editor. Redact private messages and names if you share a screenshot or Flow export.
Support development - If Advanced Triggers is useful to you, you can support its
continued development through GitHub Sponsors,
Patreon,
PayPal, or
bunq.
Thank you!