mirror of
https://github.com/ruvnet/RuView
synced 2026-07-31 18:51:42 +00:00
ruv
f5d787ccde
Per ADR-115 §9.4 (maintainer ACK on #776), v0.7.0 ships **3 starter blueprints**. This commit goes further: all **8** of the catalog proposed in §3.12.2 land as standalone YAML files under `examples/ha-blueprints/`, ready to import into HA. ## Blueprints 1. Notify on possible distress → possible_distress 2. Dim hallway when sleeping → someone_sleeping 3. Wake routine on bed exit → bed_exit (time-window-gated) 4. Alert on elderly inactivity → elderly_inactivity_anomaly (with optional escalation chain) 5. Meeting lights + presence mode → meeting_in_progress (activates a HA scene) 6. Bathroom fan while occupied → bathroom_occupied (privacy-mode-safe; zone-derived) 7. Escalate on fall-risk crossing → fall_risk_elevated (numeric_state trigger) 8. Auto-arm security when not active → group(room_active) + no_movement (composed; multi-room sense) Each blueprint: - Uses HA's blueprint schema (https://www.home-assistant.io/docs/blueprint/schema/) - Declares typed `selector:` for every input (entity-domain-constrained where applicable) - Carries a `source_url` for HACS-style re-import - Includes `mode: single` + `max_exceeded: silent` where appropriate so transient retriggers don't spam - Includes a `cooldown_minutes` / `confirm_minutes` / `ack_timeout_min` parameter where time-debouncing matters ## Validator (`scripts/validate-ha-blueprints.py`) Pure-Python validator that: - Registers no-op constructors for HA's `!input` and `!secret` YAML tags (PyYAML doesn't know them) - Asserts every file has a top-level `blueprint:` mapping with `name`/`description`/`domain` - Asserts `domain` is `automation` or `script` - Asserts at least one declared `input` - Asserts at least one of `trigger`/`action`/`sequence` is present Exits 0 only when all 8 validate. Local run: python scripts/validate-ha-blueprints.py All 8 HA Blueprints validate OK ## CI integration `.github/workflows/mqtt-integration.yml` gains a new `Validate HA Blueprints` step that runs the Python validator before the cargo test phases — fails the workflow on any malformed blueprint in a PR. ## Privacy-mode coverage table 5 of 8 blueprints are unconditionally privacy-mode-safe (no biometric dependency in the state derivation). The other 3 depend on inferred states that themselves derive from biometrics — the inferred state still publishes under `--privacy-mode` (per ADR §3.12.3) but the operator should audit the use case in regulated contexts. Full table in `examples/ha-blueprints/README.md`. Refs #776, PR #778. Co-Authored-By: claude-flow <ruv@ruv.net>
45 lines
1.3 KiB
YAML
45 lines
1.3 KiB
YAML
blueprint:
|
|
name: RuView — escalate on fall-risk score crossing
|
|
description: >
|
|
Send a notification when the fall_risk_elevated sensor crosses a
|
|
configurable threshold (default 70) — the resident's near-fall
|
|
frequency + gait-instability proxy has reached a level worth
|
|
investigating. Pairs with the longer-term ADR-079 P9 personalisation
|
|
flow once available. Part of the ADR-115 §3.12 starter blueprint set.
|
|
domain: automation
|
|
source_url: https://github.com/ruvnet/RuView/blob/main/examples/ha-blueprints/07-fall-risk-escalation.yaml
|
|
input:
|
|
fall_risk_entity:
|
|
name: Fall risk elevated sensor (0-100 score)
|
|
selector:
|
|
entity:
|
|
domain: sensor
|
|
notify_target:
|
|
name: Notification service
|
|
selector:
|
|
text: {}
|
|
threshold:
|
|
name: Crossing threshold
|
|
default: 70
|
|
selector:
|
|
number:
|
|
min: 30
|
|
max: 100
|
|
|
|
mode: single
|
|
max_exceeded: silent
|
|
|
|
trigger:
|
|
- platform: numeric_state
|
|
entity_id: !input fall_risk_entity
|
|
above: !input threshold
|
|
|
|
action:
|
|
- service: !input notify_target
|
|
data:
|
|
title: "⚠️ Fall-risk score elevated"
|
|
message: >
|
|
{{ trigger.to_state.attributes.friendly_name or trigger.entity_id }}
|
|
crossed {{ threshold }} (current value
|
|
{{ trigger.to_state.state }}). Consider a wellness check.
|