From bf3bce763c476eecac54b246e65568aad10523cf Mon Sep 17 00:00:00 2001 From: Pieter Hollander Date: Sat, 4 Jan 2025 21:08:15 +0100 Subject: [PATCH] Clarify watchdog information. --- opendtu-logger/DOCS.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/opendtu-logger/DOCS.md b/opendtu-logger/DOCS.md index 4513042..a37ae68 100644 --- a/opendtu-logger/DOCS.md +++ b/opendtu-logger/DOCS.md @@ -44,8 +44,8 @@ With the database initialised, we can now setup OpenDTU Logger. Add the [add-on - Optionally, if you don't want to use TimescaleDB, disable `timescaledb`. - It is recommended to leave the `log_level` set to `INFO`. - Valid options are `DEBUG`, `INFO`, `WARN` and `ERROR`. - -Save the configuration, go to the "Info" tab and start OpenDTU Logger. Make sure to enable the "Watchdog" on this page so OpenDTU Logger is automatically restarted when it crashes. By design, this may happen when the connection to the OpenDTU websocket is interrupted. +- Save the configuration, go to the "Info" tab and start OpenDTU Logger. +- Make sure to **enable** the "Watchdog" on the "Info" tab so OpenDTU Logger automatically restarts after connection interruptions. Check the "Log" page. If the setup is succesfull, it should contain a message stating: `OpenDTU Logger has been successfully initialised. Starting data recording...`. @@ -98,6 +98,8 @@ Using the aforementioned steps, you should now have a working OpenDTU Logger set - Error: `"level":"INFO","msg":"websocket: bad handshake"}` - Authentication is probably misconfigured. Ensure `opendtu_auth` is set to enabled and a valid `opendtu_username` and `opendtu_password` are set. +- OpenDTU Logger crashes and doesn't restart. + - This may happen when e.g. the connection to the OpenDTU websocket or database is interrupted. Restarts are handled by Home Assistant. Make sure that 'Watchdog' is enabled on the add-on info page. ## Feedback