From a3079d1ac49c33b436352f74d9f957850d0c2490 Mon Sep 17 00:00:00 2001 From: Pieter Hollander Date: Wed, 27 Mar 2024 10:21:08 +0100 Subject: [PATCH] Change wording of restart limitations for websocket disconnections. --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index af89438..88bea7d 100644 --- a/README.md +++ b/README.md @@ -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.