Files
ruvnet--RuView/examples/lovelace/01-single-room-overview.yaml
T
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

94 lines
3.0 KiB
YAML

# RuView — Single-room overview Lovelace dashboard
#
# Drop into a Home Assistant Lovelace view (raw config editor). Replace
# the `binary_sensor.ruview_bedroom_*` entity IDs with the entity IDs
# auto-generated by your RuView node (HA picks them up from MQTT
# discovery automatically — see `mosquitto_sub -t 'homeassistant/#'`
# to enumerate them).
#
# This view shows the full 21-entity RuView surface for one room:
# raw signals on the left (presence, HR, BR, motion, RSSI, fall risk
# score) and semantic primitives on the right (sleeping, distress,
# room active, no movement). Pose visualisation is a placeholder for
# the v0.7.1 picture-elements integration.
title: RuView — Bedroom
path: ruview-bedroom
icon: mdi:home-thermometer
cards:
- type: vertical-stack
cards:
- type: markdown
content: >
## Bedroom — RuView sensing
Status pulled live from MQTT auto-discovery. Tap any tile to
see the raw history graph.
- type: horizontal-stack
cards:
- type: tile
entity: binary_sensor.ruview_bedroom_presence
name: Presence
icon: mdi:motion-sensor
color: green
- type: tile
entity: binary_sensor.ruview_bedroom_someone_sleeping
name: Sleeping
icon: mdi:sleep
color: blue
- type: tile
entity: binary_sensor.ruview_bedroom_room_active
name: Room active
icon: mdi:home-account
color: amber
- type: glance
title: Raw vitals
entities:
- entity: sensor.ruview_bedroom_heart_rate
name: HR
- entity: sensor.ruview_bedroom_breathing_rate
name: BR
- entity: sensor.ruview_bedroom_motion_level
name: Motion
- entity: sensor.ruview_bedroom_person_count
name: Persons
- entity: sensor.ruview_bedroom_rssi
name: RSSI
- type: gauge
entity: sensor.ruview_bedroom_fall_risk_elevated
name: Fall risk score
min: 0
max: 100
severity:
green: 0
yellow: 40
red: 70
- type: entities
title: Safety
entities:
- entity: binary_sensor.ruview_bedroom_possible_distress
name: Possible distress
- entity: binary_sensor.ruview_bedroom_no_movement
name: No movement (safety)
- entity: binary_sensor.ruview_bedroom_elderly_inactivity_anomaly
name: Inactivity anomaly
- type: history-graph
title: Last 6h — Heart rate & breathing
hours_to_show: 6
refresh_interval: 60
entities:
- entity: sensor.ruview_bedroom_heart_rate
- entity: sensor.ruview_bedroom_breathing_rate
- type: logbook
title: Recent events
hours_to_show: 24
entities:
- event.ruview_bedroom_fall
- event.ruview_bedroom_bed_exit
- event.ruview_bedroom_multi_room_transition