ruvnet--RuView

mirror of https://github.com/ruvnet/RuView synced 2026-06-09 10:13:17 +00:00

Files

T

rUv b12662a54d fix(mqtt): per-node HA devices use each node's own presence/motion (#872 ) (#918 )

The MQTT bridge fanned out one Home-Assistant device per node (#898) but
applied the *room-level aggregate* classification to every node — so in a
multi-node setup a node in an empty corner inherited another node's
"present", and `motion_level: "absent"` was mis-mapped to full motion
(the aggregate match fell through `Some(_) => 1.0`).

Each node in the sensing broadcast's `nodes` array already carries its own
`classification` (`motion_level`/`presence`/`confidence`, see
PerNodeFeatureInfo) and RSSI. Now each per-node snapshot reads that node's
own classification, deferring to the room aggregate only for fields a node
omits. Vitals (breathing/heart rate) and person count stay room-level.

Extracted the JSON→VitalsSnapshot mapping into a pure, testable function
(`vitals_snapshots_from_sensing_json`) and added 4 unit tests covering
per-node divergence, partial-field fallback, the no-nodes aggregate path,
and the absent→zero-motion fix.

Supersedes #899, which targeted the right bug but read non-existent fields
(`node["motion_level"]` / `node["status"]` instead of the nested
`node["classification"]` + `stale`).

Verified: builds with `--features mqtt`; new tests pass; full crate unit
suite 432 + 114 passed, 0 failed.

2026-06-02 19:26:01 +02:00

.cargo

fix(security): audit — fix RUSTSEC vulns, clippy warnings, dead code (#769 )

2026-05-23 05:36:13 -04:00

.claude-flow

chore(repo): rename rust-port/wifi-densepose-rs → v2/ (flatten to one level) (#427 )

2026-04-25 21:28:13 -04:00

crates

fix(mqtt): per-node HA devices use each node's own presence/motion (#872 ) (#918 )

2026-06-02 19:26:01 +02:00

data

chore(repo): rename rust-port/wifi-densepose-rs → v2/ (flatten to one level) (#427 )