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 c8b6cd7ace feat(adr-115): ship 3 Lovelace dashboard YAMLs (single-room / multi-node / healthcare) 
Drop-in Lovelace dashboard YAMLs covering the three common ADR-115
deployment shapes. Paste into HA's raw config editor, rename the
`binary_sensor.ruview_<room>_*` entity IDs to match what HA
auto-discovered, done.

| File                                | Use case                          |
|-------------------------------------|-----------------------------------|
| 01-single-room-overview.yaml        | One node, full 21-entity surface  |
| 02-multi-node-grid.yaml             | 3+ nodes (whole-house)            |
| 03-healthcare-aal-view.yaml         | Care-giver dashboard, --privacy-mode-safe |

## Single-room overview

- Three top tiles: presence / sleeping / room active
- Glance card with HR / BR / motion / persons / RSSI
- Gauge for fall_risk_elevated with green<40<yellow<70<red
- Safety entities card (distress / no_movement / inactivity anomaly)
- 6h history graph of HR + BR
- 24h logbook of fall / bed_exit / multi_room events

## Multi-node grid

- Top markdown header
- 2-column grid of per-room presence tiles with navigation actions
  drilling into per-room dashboards
- Glance card showing per-room person counts
- 24h logbook of semantic events across the house

## Healthcare / AAL

- **Privacy-mode-compatible** — binds only to semantic primitives, no
  raw HR/BR/pose on the dashboard surface. Carer-app-friendly.
- Six tiles: sleeping / room-active / bathroom (top row) +
  distress / inactivity-anomaly / no-movement (bottom row)
- Gauge for fall_risk_elevated
- 24h logbook of safety-relevant events
- Last-presence-change timestamp card

## README + privacy-mode coverage

`examples/lovelace/README.md` documents how to rename auto-discovered
entity IDs (either via HA's entity-rename UI or via the NVS-only
node_friendly_name field per ADR §9.6) and explains why dashboard 3
remains useful under --privacy-mode (inferred states still publish,
biometric values don't).

All three files validate as well-formed YAML with `title:` + `cards:`
under PyYAML.

Refs #776, PR #778.

Co-Authored-By: claude-flow <ruv@ruv.net>
 		2026-05-23 15:04:39 -04:00
..
01-single-room-overview.yaml feat(adr-115): ship 3 Lovelace dashboard YAMLs (single-room / multi-node / healthcare) 2026-05-23 15:04:39 -04:00
02-multi-node-grid.yaml feat(adr-115): ship 3 Lovelace dashboard YAMLs (single-room / multi-node / healthcare) 2026-05-23 15:04:39 -04:00
03-healthcare-aal-view.yaml feat(adr-115): ship 3 Lovelace dashboard YAMLs (single-room / multi-node / healthcare) 2026-05-23 15:04:39 -04:00
README.md feat(adr-115): ship 3 Lovelace dashboard YAMLs (single-room / multi-node / healthcare) 2026-05-23 15:04:39 -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