- fix(proxy):
PW_HTTPS=yesstarts again in Docker — images since v0.15.0 left out the bundledlocalhost.pem, so HTTPS failed to start. The proxy now ships with an HTTPS-aware health check, and newPW_HTTPS_CERT/PW_HTTPS_KEYlet you use your own certificate, as in pypowerwall-server. The shared bundled certificate stays the default (nothing breaks on upgrade) and now logs a warning. The README shows how to make your own. Proxy t110. (#449) - docs(v1r): battery dispatch now boldly warns that it could void or limit your Tesla Powerwall warranty. The Powerwall warranty quoted in #450 gives unlimited cycles only for solar self-consumption, time-based control and backup; any other use is limited to 37.8 MWh of total energy throughput. The warning was added to the README and API.md warnings, the
dispatch_battery_power()docstrings, and the WARNING logged for each accepted dispatch. (#451, closes #450) - Library version bumped to
0.23.0
Proxy t110 validated on 2x Powerwall 3 + Backup Gateway 2 (no expansion packs).
Install / upgrade:
- PyPI: https://pypi.org/project/pypowerwall/0.23.0/ —
pip install --upgrade pypowerwall==0.23.0 - Proxy Docker image:
jasonacox/pypowerwall:0.23.0t110(alsolatest)
Contributors
Thanks to the community members who made this release possible:
- @longzheng — raised #450 the moment he found the warranty implication, protecting everyone who uses dispatch — on top of building local battery dispatch itself (#440)
- @BJReplay — worked out what the 37.8 MWh cap means day to day: about 10.4 kWh every day for 10 years
- @jasonacox — the proxy HTTPS fix (#449), the warranty warning (#451) and release chores (#452, #453)
Spot a bug or have a Powerwall feature you'd love to see? Issues and pull requests are always welcome — this project is built by its community. 🌟
Full changelog: v0.22.2...v0.23.0