energy/home-assistant-addons
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Clarify watchdog information.

Browse source
This commit is contained in:
Pieter Hollander 2025-01-04 21:08:15 +01:00
parent d5fc9258cf
commit bf3bce763c
Signed by: pieter
SSH key fingerprint: SHA256:HbX+9cBXsop9SuvL+mELd29sK+7DehFfdVweFVDtMSg
1 changed files with 4 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
opendtu-logger/DOCS.md
View file

@ -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