Ignore 0% battery readings in low-battery alerting

A 0% batteryLevel is an invalid/no-data value (no battery wired or misconfigured node), not a genuinely critical battery, so it must not produce a "⚠️ battery low" alert. Add a non-positive guard to shouldAlert after the undefined check: 0 (and any non-positive) now skips, while 1-20 still alert and >20 still doesn't. Threshold/cooldown/ batching unchanged. Tests: 3 new specs in the check-threshold block (0% excluded from the batch, lone 0% sends nothing, 1% still alerts). 180 -> 183.
2026-10-06 08:02:37 +00:00
parent 84915fe314
commit 7ec97a06d2
4 changed files with 47 additions and 1 deletions
@@ -1,5 +1,9 @@
 # Changelog

+## v0.21.12 — 2026-10-06 08:01
+
+- Battery monitoring now ignores a 0% reading: a 0 (or any non-positive) `batteryLevel` is treated as an invalid/no-data value (node has no battery wired or is misconfigured) and no longer produces a "⚠️ battery low" alert, while genuinely-low readings (1–20%) still alert exactly as before. One-line guard added to `BatteryAlertService.shouldAlert` right after the `undefined` check. Tests: 3 new specs in the `check threshold` block — a 0% node is excluded from the batch (and a lone 0% sends nothing) while a 1% node still alerts.
+
 ## v0.21.11 — 2026-10-05 14:47

 - Migrated the opencode notifier to the v2 API routes: discovery is now `GET {api}{proxyPath}/api/session` (a `{ data, cursor }` envelope; sessions filtered by `location.directory`, most-recent `time.updated` wins) and send is now `POST {api}{proxyPath}/api/session/{sid}/prompt` with a `{text}` body, instead of the v1 `GET /session` + `POST /session/{id}/message` (`{parts:[{type:"text",text}]}`) routes. CodeNomad's per-workspace instance proxy was upgraded and now only serves opencode v2 `/api/*` — every v1 `/session/…` call 403s, which was breaking all notifications. v2 returns 2xx immediately (no longer holds the response until the turn finishes), so the 15 s read-timeout-as-delivered branch is kept only as a harmless safety net.