Repository navigation
Examples
Home · Getting started · Flows
| What you want to do | Start here |
|---|---|
| Record a door opening | First door-event example |
| Add the current time to a message | Use BLL text below |
| Follow queued Advanced Triggers requests | Sequential logging below |
| Save a complete log to an FTP server | FTP archive walkthrough |
| Log from HomeyScript or another app | Flow logging scripts |
Install BLL and make your first log entry work first. In the Message field of a logging action, enter:
Door opened at {[date("HH:mm")]}.
Run the Flow and check the entry in app settings. It should contain the time when the action ran, rather than the expression. Use the door sensor's trigger for a real door-event Flow; running the action by hand only tests the message. See BLL coding for all supported fields.
Use Simple (Sys) Log to see which messages an Advanced Triggers Sequential receiver handles. This adapts the developer's community example to current cards.
Install Simple (Sys) Log and Advanced Triggers. You need Advanced Flow and a working log view. Use harmless test messages rather than private information.
- Create a receiving Advanced Flow. Add Advanced Triggers This Flowcard
started, choosing 1 text, 1 number, 1 yes/no. Enter and select the name
demo-queue, and set Execution to Sequential. Save the Flow. - Connect the receiver to Simple Log's
Add Something to the Simple Log action.
Insert the receiver's Text 1 token into Message and set App/group
to
Queue test. Leave severity and facility empty. - Make three manually started test branches or Flows, each with Advanced
Triggers Start Flowcard, again using 1 text, 1 number, 1 yes/no.
Select
demo-queueas Triggername, leave Tag empty, and set Wait to Finish off. Set Text 1 toA,B, andCrespectively. Save the Flows and connect error paths to a visible notification. - Run A, then B, then C normally, with a small gap so the requests actually
arrive in that order. In App settings, filter App by
Queue test. The receiver's log messages should be A, B and C in arrival order; the grid shows newest first, so read it from bottom to top.
Sequential waits for the receiving Flow's completion as reported by Homey's Flow engine. Engine and firmware behavior matters: test on your own Homey if requests overlap or appear out of order. This small test shows observed order; it does not by itself prove how overlapping requests are queued. Log timestamps show when the log action ran, not when a physical speaker finished playing. A speaker action may report completion while sound is still playing; these entries cannot prove the announcements finished in order.
Next: check a missing entry or explore the other Flow cards.
Support development - If Simple (Sys) Log is useful to you, you can support its
continued development through GitHub Sponsors,
Patreon,
PayPal, or
bunq.
Thank you!