health
Use when checking Home Assistant home status, repairs, system health, unavailable/unknown entities, low batteries, or component/config summaries through HA NOVA Relay.
markusleben · 已有静态检查记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add markusleben/ha-nova --skill health技能说明
name: health description: Use when checking Home Assistant home status, repairs, system health, unavailable/unknown entities, low batteries, or component/config summaries through HA NOVA Relay. license: MIT compatibility: Requires the ha-nova CLI (run 'ha-nova setup' first) and the HA NOVA Relay in Home Assistant (App, or standalone container on Container/Core).
HA NOVA Home Status
Scope
Read-only home status checks:
- repairs/deprecation issues
- integration entries that are not loaded
- config and loaded component summary
- unavailable/unknown entity summary
- low battery/SOC summary
- best-effort system health info
Not in scope:
- repair/fix/ignore actions
- statistics repair, purge, registry cleanup (
ha-nova:maintenance) - restart, reload, update, backup, or service calls
- YAML/filesystem diagnostics
- historical timelines (use
ha-nova:history) - root-causing one named item's concrete incident (
ha-nova:diagnose) — this skill reports what is wrong across the home right now, not why one thing failed - how long an entity has been unavailable, and whether it is a cleanup candidate (
ha-nova:maintenancelong-unavailable report)
Bootstrap (once per session)
Read and follow ../ha-nova/session-bootstrap.md.
Verify relay CLI: ha-nova relay health
If this fails: ha-nova setup
Read data.version from the health response.
Report Modes
Two independent dimensions; both are always visible at the top of every
report. Natural-language requests select them ("short/compact", "explained",
"full", "private", "shareable", "aggregate", localized); no CLI syntax.
Default: Explained + Private.
- Detail:
Compact(overall result + three highest-priority actions) ·Explained(default: all actionable findings, explanations, small-group details, summarized large groups) ·Full(every finding and group; selected large groups in bounded chunks). - Privacy:
Private·Shareable·Aggregate— semantics inavailability-analysis.md→ Privacy modes. When identities are hidden, say why and how to request private detail. Census participation never affects local report detail. A follow-up such as "show all entities in MQTT" requests that group's full detail in the ACTIVE privacy mode — a detail follow-up never switches modes; switching to private identities takes an explicit request naming the mode.
Relay Contract
Use file-based relay requests:
ha-nova relay core --method GET --path /api/config --out <result-file>ha-nova relay core --method GET --path /api/components --out <result-file>ha-nova relay core --method GET --path /api/states --out <result-file>ha-nova relay ws --data-file <payload-file> --out <result-file>ha-nova relay jq --file <result-file> --jq-file <filter-file>
For WS payloads:
- repairs:
{"type":"repairs/list_issues"} - integration entries:
{"type":"config_entries/get"} - entity registry:
{"type":"config/entity_registry/list"} - device registry:
{"type":"config/device_registry/list"} - area registry (optional, only when human-readable area names are shown):
{"type":"config/area_registry/list"} - system health:
{"message":{"type":"system_health/info"},"collect_events":{"until_type":"finish","max_events":100,"timeout_ms":10000}}
system_health/info is a finite event-response command. The Skill opts into generic Relay event collection through collect_events; the Relay only forwards the WS message and enforces until_type, max_events, and timeout_ms. A compatible relay returns data.events containing initial, zero or more update, and finish events. If the relay returns data: null, UNSUPPORTED_WS_TYPE, VALIDATION_ERROR, or another unsupported-event response, continue and say system-health details need a relay at the enforced floor — every supported relay has event collection, so this points at an outdated App.
Data Shapes
Envelope parsing follows skills/ha-nova/relay-api.md → Standard Envelope. Normalize each saved relay result separately before summarizing:
- REST
/api/config,/api/components,/api/states: use.data.body - WS
repairs/list_issues: use.data.issues - WS
config_entries/get: use.dataas an array - WS
config/entity_registry/list: use.dataas an array - WS
config/device_registry/list: use.dataas an array - WS
config/area_registry/list: use.dataas an array; use onlyarea_idandname - WS
system_health/info: use.data.eventsas an array; event kind is.type
Private detail uses explicit, minimal source fields — never more:
- state rows:
entity_id,state,last_changed,attributes.restored,attributes.friendly_name, structured battery/SOC metadata - entity registry:
entity_id,config_entry_id,device_id,platform,name,original_name,area_id - device registry:
id,name_by_user,name,area_id - config entries: existing state/domain fields plus
title, sanitized before display
Optional display metadata that is unavailable is marked unavailable; it never turns an otherwise complete result into a system failure.
Do not run one combined jq normalizer across config, components, states, repairs, integrations, and system health. Their envelopes differ. Normalize each source file into a small source-specific shape first, then combine those normalized summaries.
Before accepting a source, require ok:true, a 2xx REST data.status, and valid types for every required row field. If a shape differs, mark that source unavailable and continue. Do not show parser or jq errors; mention only the affected source in coverage.
Use --jq-file for non-trivial filters. Avoid complex inline jq, especially regex that must be shell-escaped. Prefer simple field equality and type checks over regex whenever Home Assistant attributes already provide structured data.
System Health event payloads are mixed-shape. For events from .data.events[]:
- read the event kind from
.type - before reading `.data