[jasonacox]

Release prep for pypowerwall-server 0.14.0: optional HTTPS, and a warranty warning for battery dispatch.

Included

• feat: optional HTTPS on port 8775 (PW_HTTPS=yes) with a per-install certificate #188: optional HTTPS. PW_HTTPS=yes also serves HTTPS on port 8775 (PW_HTTPS_PORT; 8676 is Powerwall-Dashboard's weather service). HTTP on 8675 is unchanged, so Telegraf, the Dashboard health check and scripts keep working.
  • Certificate: self-signed and unique to each install, generated once in /data/tls. Or bring your own with PW_HTTPS_CERT / PW_HTTPS_KEY.
  • Over HTTPS, cookies are SameSite=None; Secure for HTTPS iframes such as Home Assistant.
  • Fixes PW_HTTPS, which was accepted but ignored.
• docs(dispatch): warn that battery dispatch could void your warranty #190: battery dispatch could void or limit your Tesla warranty. The warning is in the docs, the Console (one-line caution, info popup, confirmations), the 403 message and the startup log. Thanks @longzheng for raising Manual dispatch changes warranty terms pypowerwall#450 and @BJReplay for working out what the 37.8 MWh cap means day to day.

This PR: SERVER_VERSION and pyproject.toml set to 0.14.0, and RELEASE.md dated with a summary. The pypowerwall pin stays at 0.22.2; the upcoming 0.23.0 only changes the library's docs and the proxy.

Checks: upload-pypi.sh --dry-run built and checked 0.14.0 (wheel ships only app/).

After merge: PyPI upload, Docker :0.14.0 / :latest, tag v0.14.0.

🤖 Generated with Claude Code

[Copilot]

🟢 Approval recommended

No active review issues remain for the 0.14.0 release-preparation changes.

No open issues 🎉

What changed in this PR

Prepares pypowerwall-server 0.14.0 for release, documenting the previously merged optional HTTPS support and battery-dispatch warranty warnings.

Changes:

• Updates the application and package versions from 0.13.1 to 0.14.0.
• Dates the release notes October 28, 2026, and adds a brief release summary.

File	Description
RELEASE.md	Finalizes the release date and summarizes HTTPS support and warranty warnings.
pyproject.toml	Sets the package version to 0.14.0.
app/​config.py	Sets SERVER_VERSION to 0.14.0, matching package metadata.

_{Review effort: Balanced}

[jasonacox]

@jasonacox-sam, pypowerwall-server 0.14.0 is out: tag v0.14.0 (21a2761), PyPI and Docker. Could you create the GitHub release and post it on X?

I'm so proud of how you run these releases. Thanks for v0.13.1 and v0.22.2 yesterday, both done fast and with care. ❤️

Step 0: find the changes yourself first. Read every merged PR and linked issue in v0.13.1...v0.14.0, list each change and everyone who helped, then compare it with my checklist below and tell me anything I missed.

The release must include:

• Tag v0.14.0, title along the lines of "v0.14.0 - Optional HTTPS and Dispatch Warranty Warning".
• In the release body, an "Install / upgrade" block like v0.13.0's (v0.13.1 and v0.22.2 checked these off but left them out of the body):
  • PyPI: https://pypi.org/project/pypowerwall-server/0.14.0/ and pip install --upgrade pypowerwall-server==0.14.0;
  • Docker: jasonacox/pypowerwall-server:0.14.0 and :latest.
• feat: optional HTTPS on port 8775 (PW_HTTPS=yes) with a per-install certificate #188: optional HTTPS.
  • PW_HTTPS=yes also serves HTTPS on port 8775 (PW_HTTPS_PORT); 8675 stays HTTP, so Telegraf, the Dashboard health check and scripts are unchanged.
  • Self-signed certificate, unique to each install, in /data/tls, or your own via PW_HTTPS_CERT / PW_HTTPS_KEY.
  • Cookies are SameSite=None; Secure over HTTPS for Home Assistant iframes.
  • Fixes PW_HTTPS, which was accepted but ignored.
• docs(dispatch): warn that battery dispatch could void your warranty #190: battery dispatch could void or limit your Tesla warranty. The warranty quoted in Manual dispatch changes warranty terms pypowerwall#450 gives unlimited cycles only for self-consumption, time-based control and backup; any other use is capped at 37.8 MWh of throughput. The warning is in the docs, the Console (one-line caution, info popup, confirmations), the 403 message and the startup log. Please keep the "could void or limit" wording.
• Release PR Release prep: bump version to 0.14.0 #191.
• Contributors, warmly:
  • @longzheng spotted the warranty implication and raised Manual dispatch changes warranty terms pypowerwall#450 right away. That catch protects every dispatch user, on top of his MQTT dispatch work in Add MQTT battery dispatch controls and Home Assistant inputs #184.
  • @BJReplay worked out what the cap means in real life: about 10.4 kWh every day for 10 years.
• Hardware, if you mention testing: 2x Powerwall 3 + Backup Gateway 2, no expansion packs.
• Close with an invitation to contribute.
• Reply with the X post link once it's up.

Thank you, Sam!

[jasonacox-sam]

@jasonacox — Done. Release v0.14.0 is live and marked latest.

Step 0, changes found in v0.13.1...v0.14.0:

• feat: optional HTTPS on port 8775 (PW_HTTPS=yes) with a per-install certificate #188 — Optional HTTPS (8301ede): PW_HTTPS=yes serves HTTPS on PW_HTTPS_PORT (default 8775) alongside HTTP 8675; self-signed cert unique per install in /data/tls, or PW_HTTPS_CERT/PW_HTTPS_KEY for your own; SameSite=None; Secure cookies over HTTPS for HA iframes; also fixes the ignored-PW_HTTPS bug.
• docs(dispatch): warn that battery dispatch could void your warranty #190 — Dispatch warranty warning (c1d1b10): "could void or limit your Tesla Powerwall warranty" (the warranty quoted in pypowerwall#450: unlimited cycles only for self-consumption, time-based control and backup; otherwise capped at 37.8 MWh throughput) across README/API.md, Console caution line + info popup + confirmations, the 403 message, and the startup warning.
• Release prep: bump version to 0.14.0 #191 — Release prep (21a2761): version bump, RELEASE.md, pypowerwall pin unchanged at 0.22.2.

Checklist:

• Tag v0.14.0, title "v0.14.0 - Optional HTTPS and Dispatch Warranty Warning", marked latest
• Install / upgrade block in the release body (and retro-added to v0.13.1 per your Release prep: bump version to 0.13.1, pypowerwall 0.22.2 #189 note)
• PyPI: https://pypi.org/project/pypowerwall-server/0.14.0/ (wheel + sdist verified on the simple index) — pip install --upgrade pypowerwall-server==0.14.0
• Docker: jasonacox/pypowerwall-server:0.14.0 and :latest both pushed
• Contributors: @longzheng (spotted the warranty implication and raised pypowerwall#450 right away, on top of MQTT dispatch in Add MQTT battery dispatch controls and Home Assistant inputs #184), @BJReplay (worked out the cap in real life — ~10.4 kWh/day for 10 years), @jasonacox (feat: optional HTTPS on port 8775 (PW_HTTPS=yes) with a per-install certificate #188, docs(dispatch): warn that battery dispatch could void your warranty #190, Release prep: bump version to 0.14.0 #191)
• Hardware note: 2x Powerwall 3 + Backup Gateway 2, no expansion packs
• Closing invitation to contribute
• X post: https://x.com/jasonacox_sam/status/2115677781287981543

Anything your checklist missed: nothing material. One nitpick from my read-through: #188's target_commitish notes aside, the compare also shows no doc-only or CI commits hiding between the three — the release covers everything. The only thing not in the release itself is that PR #184 (MQTT dispatch) is still open pending the same warranty wording — noted on the watch list, not a release gap.

— Sam 🔌