Repository navigation
App Simple Sys Log
Supported apps · File server settings
Simple (Sys) Log supports BLL coding directly in selected Flow-card fields, as well as using BLL's file server for downloads. Install BLL alongside the logging app to evaluate expressions; ordinary text and Homey Flow tokens work without BLL.
You can use {[ ... ]} expressions directly in:
- Message fields on the app's logging and Timeline actions.
- App/group fields on the grouped logging and Timeline-and-log actions.
- Message and App/group fields on the Syslog client device action.
For example, put this in a supported Message field:
Door opened on {[date("dddd")]}.
BLL replaces the expression with the current weekday when the action runs. You do not need a separate BLL action to prepare this message.
The Excel, CSV and JSON export filename fields in app settings also support expressions. The App/group filter on the A log is generated trigger does not. If BLL is unavailable, expressions remain as literal text.
See the logging app's BLL coding guide for supported fields, examples and troubleshooting, and its Flow actions for the individual cards.
The community timer-report Flow also uses BLL as a text accumulator: loop over Chronograph timer names, append their running states to a BLL variable, then send that variable's tag to Simple (Sys) Log. See the step-by-step workflow. This passes already-built text to the log; it does not depend on the log app decoding BLL expressions.
The current topic documents complete-log exports as Excel, CSV and JSON from the mobile app, developer tools and Flows. The original file-server demonstration shows why BLL is involved: the logging app gives BLL file content and receives a temporary download URL.
- Install BLL and check its file-server settings.
- Open Simple (Sys) LOG and select the required export format.
- Download using the offered link while it is available.
- Open the saved file and verify its content.
See file server settings for the port, startup and availability controls. Protect download links and log contents: they may contain private information.
The historical demonstration mentions a 30-second link lifetime; do not treat that as the current default. Your BLL availability setting and the export/download mechanism determine the actual behavior. Do not open a router port simply to reproduce an old screenshot.
The FTP example uses the logging app's Get complete log as Excel (Base64) card and passes the result to FTP Client's Base64-saving action:
Historical Flow screenshot: the complete log's Excel Base64 output is passed to FTP Client.
Add a daily schedule and a unique filename for a rotating archive. See the FTP walkthrough. Base64 is a transport encoding, not encryption.
As an adaptation of the timer-report technique, use BLL's Execute Text (as Tag) before the log action:
Heating checked at {[ date("HH:mm") ]}: mean {[ number(math.mean([18, 20, 22]), 1) ]}
Pass the resulting text tag to Simple (Sys) Log. You can replace the sample readings with sensor tags and use the log app's group/severity fields to organize entries. This separate formatting step is optional for the BLL-supported Message fields listed above: they can evaluate the expression directly. Use the text-tag approach when you want to reuse the same formatted message in several actions.
Support development - If Better Logic Library is useful to you, you can support its
continued development through GitHub Sponsors,
Patreon,
PayPal, or
bunq.
Thank you!
