chore(release): version packages

[frahlg]

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and publish to npm yourself or setup this action to publish automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to master, this PR will be updated.

Releases

ftw@2.3.0

Minor Changes

• 7ac7be9: The phone app can now notify you when a device goes quiet or the house draws more than the fuse allows. Same thresholds as before (ten minutes of silence, thirty seconds over the rating) so a blip is not a lock-screen.
• 54f0163: Sourceful Zap can again read PV and battery from devices it already talks to, as an opt-in under Settings → Devices. The default stays P1/HAN only. The driver never writes.
• 53ca4ae: Zaptec Go, Go 2 and Pro can be added as a cloud EV charger. The setup wizard and Settings → EV offer Zaptec next to Easee; the same email and password list chargers on the account and drive current, pause and resume through Zaptec Cloud. The integration is experimental until a live charger has been exercised.

Patch Changes

• 31742d7: Harden SI units and charging identities: SoC doors fold NaN/overflow instead of leaking percent or Inf, HA discovery slugs illegal driver names with a collision tag while leaving already-legal mixed-case ids unchanged, and synthetic history stores 0–1 SoC.
• bab685a: Modbus give-up recovery no longer reload-loops a missing driver file or a device that never answered, and a failed driver_init during that reload keeps the previous VM so default-mode still works.
• 33bd6ca: The weather location map loads again. OpenStreetMap's volunteer tiles now require a Referer, and the box was sending none.
• 983c7ab: A short Modbus network blip no longer leaves a battery or meter offline until the box is restarted. Drivers that skip a register after a few failed reads used to skip every register after a "no route to host" moment; the host now reloads that driver and resumes polling once the link is back.
• 5caddc1: The Plan chart reconstructs battery SoC from stored energy or battery power when a slot omits soc, instead of drawing a flat 0% line.
• db39491: The live stats strip and today's self-powered share stay honest when a meter or inverter is offline: no fake 0 W, and a day that already happened still shows its percentage.
• b1384b3: A meter that has stopped reporting no longer shows as 0 W balanced. Grid and house load go blank, and solar or battery that went quiet with it stay on the diagram as no data instead of vanishing.

---

Note

Low Risk
Version and changelog updates only; user-facing behavior is described in the changelog but not implemented in this PR’s diff.

Overview
Release housekeeping only: bumps ftw from 2.2.1 to 2.3.0 in package.json and package-lock.json, folds ten consumed Changesets into CHANGELOG.md, and deletes the corresponding .changeset/*.md files. No application/runtime code is modified in this diff.

What ships in 2.3.0 (as recorded in the new changelog section): three minor items—push notifications for quiet devices and fuse overload, opt-in Sourceful Zap PV/battery reads, and experimental Zaptec Cloud EV charging alongside Easee—and seven patch fixes around Modbus recovery/reload loops, stale-meter UI (no fake 0 W), Plan SoC reconstruction, OSM map Referer, SI/SoC math hardening, and related HA discovery slugging.

^{Reviewed by Cursor Bugbot for commit cf87b03. Bugbot is set up for automated code reviews on this repo. Configure here.}

[cursor]

Approved. Cursor Bugbot passed with no findings that need human review, and no reviewers were assigned.

  

_{Sent by Cursor Approval Agent: Pull Request Router and Approver}

[miravoss26]

Self-review pass (pr-steward). Mechanical `changesets` version-packages PR: consumes the four pending changesets into CHANGELOG.md 2.3.0 and bumps package.json/package-lock.json. No logic touched, no secrets, no new deps beyond the version string itself. Safe to merge from my read — a human still needs to hit merge (my own PR).

[miravoss26]

Mechanical release-train PR (changesets): removes 5 changeset files, bumps CHANGELOG/package.json/package-lock to 2.3.0. No logic changes, diff matches exactly what changeset version produces.

CI green, already approved. Safe to merge from my read.

[miravoss26]

Automated Changesets release — version/changelog bookkeeping only, no application source in the diff.

What it does: bumps ftw 2.2.1 → 2.3.0, folds 8 consumed .changeset/*.md notes into CHANGELOG.md (3 minor: offline/fuse push alerts, opt-in Sourceful Zap PV/battery read, experimental Zaptec cloud EV; 5 patch: SI/SoC hardening, OSM map Referer fix, Modbus blip recovery, stale-meter UI honesty). The behavior itself already shipped in the commits the changelog cites — this PR doesn't introduce it.

Security screen: no secrets, no new deps, no network/authz surface — pure metadata diff (package.json, package-lock.json, CHANGELOG.md, changeset deletions).

CI green, already approved. Safe to merge from my read — not on my auto-merge allowlist (repo isn't listed in POLICY.md), so leaving it for a human squash.