Hi everyone,
I am currently developing a new app that should be ready for testing very soon: Sheets Log Dispatcher.
Have you ever tried to create structured logs or error logs in Homey Advanced Flows?
Some existing solutions store logs directly on Homey, which can use storage space and make the logs harder to access. Others rely on external servers or services. I also tried writing errors directly to Google Sheets myself, but my Flows quickly became huge and difficult to maintain. Using a variable was not reliable either, because the value could be overwritten by race conditions before the log entry was actually processed.
That is why I created this app.
Sheets Log Dispatcher receives log entries very quickly through a Flow card with predefined fields, stores them in an internal RAM queue, and then dispatches them one by one at a configurable interval.
The app itself does not write to Google Sheets and does not need access to your Google account. Instead, it triggers a Flow card with ready-to-use tags. You can then use the existing Google Sheets app in a separate Flow to write the log entries to your spreadsheet.
The app also includes an advanced retry helper. It allows you to retry a failed Flow action a defined number of times, with a configurable delay between retries. This can be useful when a device is only temporarily unavailable or when a condition is not ready yet. It works like a timed retry mechanism without creating a visible loop in the Flow editor.
Here are some example Flows to illustrate how the app works.
Example of a central logging flow that writes to different tabs of Google Sheet depending on the ‘type’ of the message:
Example of simple error logging:
Example of event logging:
Example of a ‘Retry’ flow:
This may allow your flow to continue to run if the device becomes available within the retrials.
Example of a log:
You can also use the ‘Full Text’ tag to write to the Timeline or any other place.
All fields and their order can be configured in the settings. Only the Type and Message are mandatory.
I’d be happy to hear your feedback, ideas, and suggestions before the first test version is released.
