#33 - v0.13.0 — battery-low alert module (merged broadcasts, @mentions, cooldown) - MeshBot

Conversation 0 Commits 3 Files Changed 10

+471 -2

3 Commits

Author	SHA1	Message	Date
kamilkrzywda	fe8d2dbe0b	battery: merge multiple low-battery nodes into one broadcast per cycle CI / build + unit (pull_request) Successful in 1m0s Details Owner follow-up: 'if multiple ppl shows at once — merge messages to one'. check() now collects every qualifying node (at/below threshold and not within its per-node cooldown) and sends AT MOST ONE broadcast per cycle containing all of them, recording the alert timestamp for each after sending; nothing is sent when none qualify. Format: '⚠️ battery low: @!<hex> (<name>) <X>%[, @!<hex> (<name>) <Y>%]' — single-node case uses the same one-entry template. Cooldown semantics unchanged.	2026-09-25 12:51:25 +00:00
kamilkrzywda	d0b71e6e91	battery: low-battery alert module (v0.13.0) BatteryAlertModule + BatteryAlertService wired into app.module like the weather module. Every BATTERY_CHECK_INTERVAL_MS (default 60 s) the service scans the node state backing GET /api/nodes and broadcasts a single-packet '⚠️ @!<8-hex> battery low: <X>% (<name>)' alert for every node at or below BATTERY_ALERT_THRESHOLD percent (default 20, <= on purpose) not alerted within BATTERY_ALERT_COOLDOWN_MS (default 6 h, in-memory map — resets on restart). Sends ride the pinned send channel via MeshService.sendText like every other bot send.	2026-09-25 12:39:45 +00:00
kamilkrzywda	8ddd91d4b5	mesh: update node batteryLevel from live NODEINFO_APP packets battery_level was only populated during the initial sync; NodeInfo frames streamed as NODEINFO_APP (port 4) now refresh deviceMetrics in the node database so /api/nodes and downstream consumers see current values between syncs. decodeNodeInfo + PORT_NODEINFO_APP added to the codec, one branch in the existing packet-handling path.	2026-09-25 12:39:45 +00:00

Author

SHA1

Message

Date

kamilkrzywda

fe8d2dbe0b

battery: merge multiple low-battery nodes into one broadcast per cycle

CI / build + unit (pull_request) Successful in 1m0s

Details

Owner follow-up: 'if multiple ppl shows at once — merge messages to one'.
check() now collects every qualifying node (at/below threshold and not
within its per-node cooldown) and sends AT MOST ONE broadcast per cycle
containing all of them, recording the alert timestamp for each after
sending; nothing is sent when none qualify. Format: '⚠️ battery low:
@!<hex> (<name>) <X>%[, @!<hex> (<name>) <Y>%]' — single-node case uses
the same one-entry template. Cooldown semantics unchanged.

2026-09-25 12:51:25 +00:00

kamilkrzywda

d0b71e6e91

battery: low-battery alert module (v0.13.0)

BatteryAlertModule + BatteryAlertService wired into app.module like
the weather module. Every BATTERY_CHECK_INTERVAL_MS (default 60 s) the
service scans the node state backing GET /api/nodes and broadcasts a
single-packet '⚠️ @!<8-hex> battery low: <X>% (<name>)' alert for every
node at or below BATTERY_ALERT_THRESHOLD percent (default 20, <= on
purpose) not alerted within BATTERY_ALERT_COOLDOWN_MS (default 6 h,
in-memory map — resets on restart). Sends ride the pinned send channel
via MeshService.sendText like every other bot send.

2026-09-25 12:39:45 +00:00

kamilkrzywda

8ddd91d4b5

mesh: update node batteryLevel from live NODEINFO_APP packets

battery_level was only populated during the initial sync; NodeInfo
frames streamed as NODEINFO_APP (port 4) now refresh deviceMetrics in
the node database so /api/nodes and downstream consumers see current
values between syncs. decodeNodeInfo + PORT_NODEINFO_APP added to the
codec, one branch in the existing packet-handling path.

2026-09-25 12:39:45 +00:00

v0.13.0 — battery-low alert module (merged broadcasts, @mentions, cooldown) #33