v5.2.4 - pypowerwall proxy v0.17.0t100 (SolarOnly recovery fix)

What's New

pypowerwall proxy upgraded to 0.17.0t100 (was 0.16.2t97)

Since v5.2.0 the dashboard pinned jasonacox/pypowerwall:0.16.2t97, which contains a TEDAPI auto-recovery bug: after a fully-failed reconnect attempt, the SolarOnly fallback recovery thread stalls permanently and the proxy serves solar-only data until the container is restarted — the "no longer recovers from SolarOnly mode" symptom reported in #855. Fixed upstream in pypowerwall v0.16.4 (pypowerwall#367); this release carries the fix to the dashboard by pinning the latest image.

Notable changes carried in the new image (0.16.2 -> 0.17.0):

• fix: TEDAPI auto-recovery wedge — after a fully-failed reconnect attempt, the SolarOnly fallback recovery thread could stall permanently, leaving the proxy serving solar-only data until the container was restarted. Recovery now retries reliably (initial 60s interval, capped at 300s). (pypowerwall#366, fixed in pypowerwall#367, shipped in pypowerwall v0.16.4)
• feat(tedapi): lifetime energy accumulators merged into /api/meters/aggregates (pypowerwall#372, pypowerwall v0.16.5)
• feat(proxy): optional bearer-token auth mode for the proxy API (pypowerwall#359 by @Nexarian, pypowerwall v0.17.0)
• fix(tedapi): TEDAPIApiVersion is now comparable, and a Content-Type typo (octet-string -> octet-stream) was corrected (pypowerwall#363, pypowerwall#364 by @Nexarian)

Also in this release: weather411 v0.2.5

The weather411 fetch loop is hardened (merged after the previous tag): the configured TIMEOUT is now actually passed to the HTTP request, non-200 responses log the HTTP status code alongside OpenWeatherMap's error message, and exception handlers report the real underlying error (DNS failure, connection refused, TLS, JSON decode) on stderr — visible in docker logs even with DEBUG disabled. (PR #853, inspired by the debugging of #849)

Upgrading

No dashboard re-import is needed — run ./upgrade.sh and the stack is recreated with the new image. PW_TEDAPI_RECOVERY remains on by default (yes).

Full Changelog

v5.3.0...v5.2.4

---

Contributors

Thanks to the community members who made this release possible:

• @ViktorJp — reported the SolarOnly recovery failure on v5.2.3 (discussion #855)
• @dthorndyke — precise upstream report of the TEDAPI auto-recovery wedge (pypowerwall#366)
• @Nexarian — bearer auth mode and TEDAPI fixes carried in this image (pypowerwall #359, #363, #364)
• @anderep — weather411 timeout/error-reporting debugging that inspired PR #853 (discussion #849)