Skip to content

Troubleshooting

Arie J. Godschalk edited this page Nov 15, 2026 · 7 revisions

Troubleshooting

Home · Getting started · App settings

Contents

A Flow ran but I cannot see an entry

  • Confirm that the action writes to the log. Add Something to the Timeline only posts a Timeline notification; it does not create a log entry.
  • Check that the Flow is enabled and that the message contains the expected text or token values.
  • Clear the filters in the settings grid. A group is shown in the App column, not as a separate group column.
  • Use Refresh Log or enable Auto refresh if the view is not updating. Run the test again and confirm that its new row appears.

My trigger did not start

A log is generated reacts to new entries only. It does not replay entries that were already present when the Flow was created. Check that the trigger's group, severity and facility filters match the values used by the action. Leave optional filters empty while testing.

The group is missing from the Timeline

The group appears in the log's App column when the grouped action is used. To prefix it to the Timeline message, enable Show group in Timeline in app settings. This setting affects the grouped Timeline-and-log action.

A cleared log immediately shows an entry

After clearing, the app writes a confirmation entry. The existing entries are removed; the new row confirms the clear action.

The settings screen is a basic log view

The basic view uses the temporary backlog and does not display the full file-based log after migration. Install BLL if you need the full grid, filters and export settings; see App settings.

A BLL expression appears literally

BLL-coded fields need Better Logic Library to be installed and available. Check that the Flow or export field is marked * BLL supported. Without BLL, expressions are left unchanged; ordinary text and Flow tokens still work. See BLL coding for syntax and examples.

Automatic cleanup did not happen immediately

Automatic retention is checked once a day, shortly after the storage day changes, with a catch-up check at startup and when file storage becomes ready. Expired daily files can remain until the next check. Set Number of days to keep the log to a positive value, or leave it empty to turn automatic cleanup off. The manual cleanup Flow action still runs immediately and requires at least 1 day. It rejects 0 without deleting anything. To remove everything, use the separate Clear the whole Log action.

A Syslog client cannot send a message

Check that the destination hostname or IP address and port are correct, that the receiver is listening, and that both ends use the same TCP or UDP transport. Confirm that the receiver accepts the selected RFC 3164 or RFC 5424 message format. See Syslog client.

The Syslog server does not receive messages

Use the Homey's reachable LAN address and the configured port on the sending device. The current server implementation listens over TCP; selecting UDP in the device settings does not change its active transport. Ports below 1024 may fail because the app may not have permission to bind them; try a port such as 1514 and configure the sender to match. Also check that received messages have a recognizable Syslog header and hostname, and that Log all received Syslogs is enabled if you expect them to appear in the local log. See Syslog server for receiver configuration details. Send a fresh test message and confirm it appears.

Logs immediately after a restart are missing

Apps may need time to start. Add a short delay before the logging action in your startup Flow, run a controlled restart test, and increase it if needed. RogerSt's community example used 30 seconds; your Homey may need a different delay.

Clone this wiki locally