From fd7656a1d649d697f97b2c6da9033f57945f2771 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Andreas=20W=C3=A4scher?= Date: Wed, 9 Oct 2024 17:27:53 +0200 Subject: [PATCH] Update README.md --- README.md | 20 +++++++++++++++++++- 1 file changed, 19 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 4f0e111..34c83bd 100644 --- a/README.md +++ b/README.md @@ -8,6 +8,24 @@ The communication to the inverters is achieved with an [reverse-engineered](http The easiest way to use MaxPower is with docker. Use the files from [the dashboard sample](usage-with-docker-compose) to run a MaxPower container along with Prometheus and Grafana for a local dashboard stack which runs perfectly fine on a Raspberry Pi. +### Connection issues and regular restarts + +I found that the inverters turned inaccessible after ~24 hours of running MaxPower. Strangely enough, only restarting the MaxPower-container fixed it. I checked the code but could not find any leaks or possible connection issues. That's why I went with the crowbar tactic and added an additional docker container in my docker-compose.yml that restarts the MaxPower-container regularly. You might need it too: + +```yaml + restarter: + image: docker:cli + restart: unless-stopped + volumes: ["/var/run/docker.sock:/var/run/docker.sock"] + entrypoint: ["/bin/sh","-c"] + command: + - | + while true; do + echo "Restarting MaxPower ..." + docker restart maxpower # use the service name of the MaxPower container defined in your docker-compose.yml + sleep 3600 + done +``` --- -Solar panel icon created by Freepik - [Flaticon](https://www.flaticon.com/free-icons/solar-panel) \ No newline at end of file +Solar panel icon created by Freepik - [Flaticon](https://www.flaticon.com/free-icons/solar-panel)