[jasonacox]

Releases pypowerwall-server 0.16.0:

• MQTT / Home Assistant battery dispatch and resume (Add MQTT battery dispatch controls and Home Assistant inputs #184 by @longzheng). It's off by default and needs both MQTT_CONTROLS bit 32 and PW_BATTERY_DISPATCH=yes; resume works without the opt-in.
  • Home Assistant gets prepared power/duration inputs and Start/Resume buttons.
  • Automations can send an atomic command with confirm:true.
  • It uses only the gateway's live local v1r connection and shares the HTTP write lock.
  • Use at your own risk: battery dispatch could void or limit your Tesla Powerwall warranty.

MINOR bump: a new feature. Existing MQTT_CONTROLS masks are unchanged. Version bumped in app/config.py and pyproject.toml; [0.16.0] dated.

Checks

• 1366 tests pass with pypowerwall 0.25.0.
• upload-pypi.sh --dry-run: wheel and sdist for 0.16.0 built and checked.
• Add MQTT battery dispatch controls and Home Assistant inputs #184 on our 2x Powerwall 3 (v1r, read-only, MQTT to a test broker): every endpoint answers and Home Assistant discovery publishes. We don't run control writes in hardware checks, so dispatch itself is covered by tests, and by @BJReplay's earlier run on their system.

After merge: PyPI and Docker (upload.sh --prod -y), image smoke test, tag v0.16.0, then Sam's GitHub release.

🤖 Generated with Claude Code

[Copilot]

🟢 Approval recommended

No active review issues are reported for the 0.16.0 release metadata update.

No open issues 🎉

What changed in this PR

Prepares the 0.16.0 release for the previously added MQTT and Home Assistant battery dispatch feature. This PR updates release metadata only; it does not change control behavior.

Changes:

• Sets the package and server versions to 0.16.0.
• Dates the release notes and highlights battery dispatch’s default-disabled status and required configuration.

File	Description
RELEASE.md	Dates the 0.16.0 release and summarizes dispatch opt-in requirements.
pyproject.toml	Updates the package version to 0.16.0.
app/​config.py	Updates SERVER_VERSION to match the package version.

_{Review effort: Balanced}

[jasonacox]

@jasonacox-sam, pypowerwall-server 0.16.0 has shipped: it's on PyPI, the Docker image is pushed, and the tag is in place. I smoke-tested the published image on our PW3 (all endpoints answer, Console loads, container healthy). Could you create the GitHub release for tag v0.16.0 and then post the announcement on X?

Step 0: please go through every change since the last tag yourself first: v0.15.1...v0.16.0. Read each merged PR and its linked issues, list every change and everyone who helped, and tell me anything my checklist below misses.

The release must include (please confirm each item when you reply):

• Tag v0.16.0, title "v0.16.0 - MQTT battery dispatch"
• PyPI: https://pypi.org/project/pypowerwall-server/0.16.0/ and pip install --upgrade pypowerwall-server==0.16.0
• Docker image: jasonacox/pypowerwall-server:0.16.0 (amd64, arm64, arm/v7), with the Docker Hub link
• Changes: Add MQTT battery dispatch controls and Home Assistant inputs #184, MQTT / Home Assistant battery dispatch and resume.
  • It's off by default and needs both MQTT_CONTROLS bit 32 and PW_BATTERY_DISPATCH=yes; resume works without the opt-in.
  • Home Assistant gets prepared power/duration inputs and Start/Resume buttons.
  • Dispatch needs confirm:true and uses only the gateway's live local v1r connection.
  • Every Start and Resume in a burst of commands runs in the order sent.
  • A dispatch or resume is logged as acknowledged only when the gateway confirms that exact command.
• The warning, in bold: use at your own risk; battery dispatch could void or limit your Tesla Powerwall warranty (Manual dispatch changes warranty terms pypowerwall#450).
• Contributors:
  • @longzheng, who authored Add MQTT battery dispatch controls and Home Assistant inputs #184;
  • @BJReplay, for the early hardware test run of the branch;
  • @jasonacox, who finished it: merged main, added the opt-in and warranty warning, and fixed the two Copilot races and the acknowledgement check.
• Our test hardware described accurately: 2x Powerwall 3 + Backup Gateway 2, no expansion packs. The hardware check was read-only, so say that dispatch itself is covered by tests and @BJReplay's run.
• The X post link in your reply, not "going out next"

Thank you, Sam! I'm proud of you. ⚡

[jasonacox-sam]

@jasonacox — Done. Release is live: https://github.com/jasonacox/pypowerwall-server/releases/tag/v0.16.0

Step 0 — went through the full compare (v0.15.1...v0.16.0): exactly two commits — 85044ee (#184, longzheng) and 9f1879c (#204, your release prep). Your checklist covers everything; nothing missing.

Confirmed each item:

• Tag v0.16.0, title "v0.16.0 - MQTT battery dispatch"
• PyPI live: https://pypi.org/project/pypowerwall-server/0.16.0/
• Docker jasonacox/pypowerwall-server:0.16.0 — verified on Docker Hub with amd64, arm64, and arm/v7 images: https://hub.docker.com/r/jasonacox/pypowerwall-server
• Changes: Add MQTT battery dispatch controls and Home Assistant inputs #184 battery dispatch and resume — off by default (needs MQTT_CONTROLS bit 32 + PW_BATTERY_DISPATCH=yes; resume without the opt-in), HA power/duration inputs + Start/Resume buttons, confirm:true required, live local v1r only, ordered burst handling, gateway-confirmed acknowledgement logging — all in the release body
• Warranty warning in bold, referencing Manual dispatch changes warranty terms pypowerwall#450
• Contributors: @longzheng (authored Add MQTT battery dispatch controls and Home Assistant inputs #184), @BJReplay (early branch test + 0.16.0 image confirmation), @jasonacox (merged main, opt-in + warranty warning, Copilot races and acknowledgement check)
• Hardware described accurately: 2x Powerwall 3 + Backup Gateway 2, no expansion packs; noted our check was read-only smoke-testing and dispatch is covered by tests (1366, pypowerwall 0.25.0) + @BJReplay's live run
• X post: https://x.com/jasonacox_sam/status/2120395929341813202

— Sam 🔌