v5.1.2 - Proxy Docker Reliability Fixes
pyPowerwall Update
- Update pypowerwall proxy Docker image to
0.15.13t94.- Zombie process fix (PID 1): Installs a
SIGCHLDhandler inproxy/server.pyto reap terminated healthcheck child processes, and addstinito the Dockerfile as defense-in-depth. Without this fix, each 30-secondwgethealthcheck spawned by Docker'sHEALTHCHECKbecomes an unreaped<defunct>zombie that accumulates for the life of the container and can eventually exhaust the PID table. Affects any deployment where the container runs as PID 1 (the default). (pypowerwall PR #343) - Alpine → Debian-slim base switch: Switches all four Docker build platforms from
python:3.10-alpine(musl libc) topython:3.10-slim(Debian/glibc). Alpine's musl libc produces a TLS ClientHello fingerprint that Tesla rejects for token refresh requests after the initial access token expires (~8 hours), causing403 token expirederrors in long-running Docker deployments. This is the same root cause already fixed in tesla-history (v5.0.11). (pypowerwall PR #345)
- Zombie process fix (PID 1): Installs a
Also included since v5.1.0
v5.1.1 - Bug Fix Release
Bug Fix
- Fix
grafana.envshell error when anonymous access is enabled:GF_AUTH_ANONYMOUS_ORG_NAME="Main Org."was written without quotes, causingbashto interpretOrg.as a separate command whencompose-dash.shsources the file. The value is now quoted in bothanonymous-access.shandgrafana.env.sample.- Reported by @JonMurphy after upgrading to v5.1.0; fix identified by @mccahan.
String Voltage query fix
- Fix typo in String Voltage query:
A_Volatage→B2_Voltage(PR #799) — contributed by @holstein13.
Documentation
- Clarify v1r mode password prompt — the password comes from the QR sticker on the Powerwall 3 unit, not the Gateway. Updated both
setup.shand README.md to eliminate ambiguity for PW3 owners who also have a separate Gateway device.- Reported by @michalperth in Discussion #784.