energy/opendtu-logger
1
0
Fork 0
Code Issues Pull requests Projects Releases 11 Packages Wiki Activity Actions

Change wording of restart limitations for websocket disconnections.
All checks were successful
Build Docker image / build (push) Successful in 1m11s
Details
Build Golang packages / release (push) Has been skipped
Details

Browse source
This commit is contained in:
Pieter Hollander 2024-03-27 10:21:08 +01:00
parent 1c399f373a
commit a3079d1ac4
Signed by: pieter
SSH key fingerprint: SHA256:HbX+9cBXsop9SuvL+mELd29sK+7DehFfdVweFVDtMSg
1 changed files with 2 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
README.md
View file

@ -92,7 +92,7 @@ The `grafana` folder contains example dashboards which can be imported into exis
- `PV.json` is a dashboard which combines the visualisations of each table that I found to be most useful.
- `Zonnepanelen.json` is the same as `PV.json`, but in Dutch language.
## Known issues
## Known limitations
- The logger will currently log every event posted by OpenDTU to the websocket. Checks still need to be added to determine the uniqueness of an event. For more information, see also [this OpenDTU Github issue](https://github.com/tbnobody/OpenDTU/issues/1800).
- Upon restart of the OpenDTU, OpenDTU Logger will need to be restarted manually as well. Automatic reconnection logic is a work in progress. Using the `systemd` service file provides a workaround for this.
- Upon restart of the OpenDTU, the OpenDTU Logger binary will need to be restarted as well. Using the provided `compose.yml` files with Docker, or using the `systemd` service file when using the binary ensures this.