berkus
/
wifi-densepose
mirror of https://github.com/ruvnet/wifi-densepose.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
wifi-densepose/examples/lovelace
History
rUv 249d6c327f
ADR-115: Home Assistant + Matter integration (#778) 
Closes ADR-115's MQTT track (HA-DISCO + HA-MIND + HA-FABRIC scaffolding).

Headline:
- 21 entity kinds per node (11 raw + 10 semantic primitives)
- MQTT auto-discovery with HA conventions
- Matter Bridge scaffolding (SDK wiring deferred to v0.7.1 per ADR §9.10)
- Privacy mode strips biometrics at the wire, semantic primitives keep working
- 420+ lib tests, mosquitto-backed integration tests, property-based fuzzing
- 8 starter HA Blueprints + 3 Lovelace dashboards shipped

Tracking issue: #776
 		2026-05-23 16:13:28 -04:00
..
01-single-room-overview.yaml ADR-115: Home Assistant + Matter integration (#778) 2026-05-23 16:13:28 -04:00
02-multi-node-grid.yaml ADR-115: Home Assistant + Matter integration (#778) 2026-05-23 16:13:28 -04:00
03-healthcare-aal-view.yaml ADR-115: Home Assistant + Matter integration (#778) 2026-05-23 16:13:28 -04:00
README.md ADR-115: Home Assistant + Matter integration (#778) 2026-05-23 16:13:28 -04:00

README.md

RuView Lovelace dashboards

Drop-in Lovelace dashboard YAMLs for three common deployment shapes. Paste the contents of any file into HA's Lovelace raw config editor (Settings → Dashboards → ⋮ → Edit dashboard → ⋮ → Raw config editor) and edit the binary_sensor.ruview_<room>_* entity IDs to match what HA auto-discovered from your RuView nodes.

# View When to use
1 Single-room overview One RuView node, full 21-entity surface
2 Multi-node grid 3+ RuView nodes (whole-house deploy)
3 Healthcare / AAL view Care-giver dashboard; privacy-mode-safe (no biometrics shown)

Renaming entities

RuView's MQTT auto-discovery generates entity IDs from the node's MAC address by default (binary_sensor.ruview_aabbccddeeff_presence). To get friendly names like binary_sensor.ruview_bedroom_presence, either:

  1. Rename in HA — open the entity, click the settings cog, change the entity ID. HA stores the rename in its own DB; the MQTT discovery topic stays the same.
  2. Set node_friendly_name in the sensing-server NVS config (per ADR-115 §9.6 maintainer-ACK'd decision: NVS-only, no ADR-039 packet change). HA picks the friendly name up at next discovery refresh.

Privacy-mode compatibility

The third dashboard is designed for healthcare / AAL deployments where --privacy-mode is set on the sensing-server. Under privacy mode:

  • HR / BR / pose entities never reach HA (discovery is suppressed).
  • Semantic primitives (someone_sleeping, possible_distress, etc.) continue to publish because they're inferred states server-side, not biometric values.

The healthcare dashboard binds only to semantic-primitive entities, so it remains useful — and HIPAA / GDPR-cleaner — under privacy mode.

Linked