Repository navigation
Flow Triggers Log_generated
Start a Flow when a new log entry is generated. Existing entries are not replayed.
App/group, Severity, and Facility are optional exact-match filters. Leave each empty to accept any value. Group matching is case-sensitive. Severity and facility match a single value, not a threshold. See levels and categories.
| Token | Meaning |
|---|---|
| Log | Message text |
| Group | Group text, or empty |
| Severity / Severity ID | Severity name and number |
| Facility / Facility ID | Facility name and number |
| Hostname | Hostname, or empty |
| Timestamp | Unix time in milliseconds |
| Source |
log, syslogclient, or syslogserver for the usual sources |
Missing metadata produces an empty name and ID -1. The current name mapping covers only some facility IDs, so a facility name can be empty even when its ID is present. Numeric zero received from Syslog is treated as missing by this trigger; test such rules carefully.
- Make a Flow with this trigger, App/group
Entry, Severity Warning, and Facility blank. - Add a Homey notification action. Insert this trigger's Log token into its message.
- In a separate test Flow, use Add Something to the Simple Log with Message
Door test, groupEntryand Severity Warning. - Run the test Flow. The second Flow should start and the notification should contain
Door test.
Avoid writing an unfiltered log message from this trigger back to the log: it can trigger itself repeatedly.
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!