Repository navigation
Flow Actions
Home · Flows · Triggers · Actions
Use Simple (Sys) Log actions in a Flow's Then section. Card labels may be translated in Homey. Each card has its own reference:
| Card | Purpose |
|---|---|
| Add Something to the Log | Write a message to the log. |
| Add Something to the Simple Log | Write a message with optional group, severity and facility. |
| Add Something to the Timeline and the Log | Write a message to the log and Timeline. |
| Add Something to the Timeline and the Log (grouped) | Write to both with optional group, severity and facility. |
| Add Something to the Timeline | Post a Timeline notification without a log entry. |
| Get the (whole) log | Return the entire log as a token. |
| Clear log data older then (Days) | Remove older daily log files. |
| Clear the whole Log | Delete all log entries. |
The device action has its own Syslog client Flowcards index.
| Action | What it does |
|---|---|
| Add Something to the Log | Adds the message to the log. |
| Add Something to the Simple Log | Adds the message with an optional group, severity and facility. |
| Add Something to the Timeline and the Log | Adds the message to both the log and Homey's Timeline. |
| Add Something to the Timeline | Adds a Timeline notification without adding a log entry. |
| Add Something to the Syslog | Sends a message through a selected Syslog client device. |
The grouped Timeline-and-log action also includes optional group, severity and facility fields. The group is stored as the entry's App value. When Show group in Timeline is enabled in app settings, it is included in the Timeline message too.
The ungrouped actions only ask for a message. Use a grouped action when you need to filter by group, severity or category later. See the full severity-level list and category list.
Message fields accept text and Flow tokens. BLL-coded expressions are supported where the card indicates BLL support; BLL is not needed for ordinary text or tokens. The App/group fields on grouped actions also support BLL. See BLL coding for supported fields and examples.
| Action | What it does |
|---|---|
| Clear the whole Log | Removes all existing log entries. |
| Clear log data older than (Days) | Removes entries older than the supplied number of days. |
Clearing the log is destructive. The age-based action requires at least 1 day, including values supplied by tokens. Zero, negative values, and invalid numbers fail without deleting anything. Use Clear the whole Log to delete everything. After a full clear, the app writes a confirmation entry, so the log may immediately show one new row.
Get the (whole) Log returns a string in its Log token. Select one of these formats:
| Format | Token content |
|---|---|
| JSON | JSON text |
| JSON (base64) | JSON text encoded as Base64 |
| CSV | CSV text |
| CSV (base64) | CSV text encoded as Base64 |
| Excel (base64) | Excel workbook encoded as Base64 |
Base64 is an encoding for transporting data, not encryption. The action returns the complete log; it does not apply the current filters in the settings view. Use App settings to download a file directly.
When saving a Flow export with BLL, match the receiving file action to the selected format: pass plain CSV or JSON to Save Text, and use Save Base64 for a Base64 variant. The forum export discussion specifically recommends Save Text for CSV.
For example, use the JSON format when a later Flow card needs to inspect or transform the records. Use CSV or Excel (Base64) when passing the export to a service that expects file contents; decode Base64 before treating it as a file.
Use a scheduled Flow to save the complete log on a server with FTP Client setup. This adapts the developer's forum export example.
Warning: saving to an existing FTP filename replaces that file. Use an unused test name and protect the destination, because logs can contain private data.
- Configure an FTP Connection in FTP Client and verify that you can upload to the destination folder. Keep Better Logic Library running for the export.
- Add a scheduled trigger, for example once daily.
- Add Get the (whole) log and choose Excel (base64).
- Connect FTP Client's Save File from base64 after the export action. Pass the log-export action's Log output token into FTP Client's File field without encoding it again.
- Select the destination folder and enter
log.xlsxas the filename. - Run the Flow and download the saved file to verify that it opens as an Excel workbook.
To retain daily copies instead of replacing log.xlsx, use a varying filename,
such as log-{[ date("yyyy-MM-dd") ]}.xlsx. See
BLL's FTP filename examples.
Multiple exports on the same day still share that filename; include a time
or another distinguishing value when needed.
For CSV or JSON, choose CSV (base64) or JSON (base64) and use a .csv
or .json filename respectively. The export contains the whole log, including
entries in previous exports, rather than only new entries since the last run.
Protect exported values, restrict server access, and choose a retention policy
appropriate for your logs.
The Syslog client device adds the Add Something to the Syslog action. Select the client device, enter a message, and optionally set a group, severity and facility. The group is used as the Syslog application name for that message; if it is empty, the device's configured application name is used.
This action sends the message to the external destination configured on the device. The device's Log all Syslogs to the default Simple Log setting can save a local copy. See Syslog client for destination settings and automatic forwarding.
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!