Stats
Actions
Tags
'%20stop-opacity%3D'0.16'%2F%3E%3Cstop%20offset%3D'1'%20stop-color%3D'rgb(200%2C90%2C60)'%20stop-opacity%3D'0.03'%2F%3E%3C%2FlinearGradient%3E%3C%2Fdefs%3E%3Crect%20width%3D'320'%20height%3D'200'%20fill%3D'url(%23g)'%2F%3E%3Ccircle%20cx%3D'250'%20cy%3D'56'%20r%3D'92'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.06'%2F%3E%3Ccircle%20cx%3D'64'%20cy%3D'172'%20r%3D'58'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.05'%2F%3E%3C%2Fsvg%3E)
From ha-nova
Provides fallback support for Home Assistant NOVA tasks not covered by dedicated skills, including blueprints, device config, HACS, Zigbee/Z-Wave, and helper families.
How this skill is triggered — by the user, by Claude, or both
Slash command
/ha-nova:fallbackThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Mandatory fallback for HA features without a dedicated skill. Three tiers:
Mandatory fallback for HA features without a dedicated skill. Three tiers:
All relay calls in this skill are experimental -- always follow the Safety section below.
Only needed when executing experimental relay calls (not for Roadmap/External guidance).
Verify relay CLI: ha-nova relay health
If this fails: ha-nova setup
For every Relay-Ready call in this skill:
ha-nova relay ws --data-file <payload-file> or ha-nova relay core --method <METHOD> --path <PATH> --body-file <payload-file>--out <result-file> for large responses-d as an optional tiny diagnostic path, not the canonical contract| Feature | Status | Skill |
|---|---|---|
| Automations CRUD | Covered | read / write |
| Scripts CRUD | Covered | read / write |
| Config Review | Covered | review |
| Helpers (9 storage + 10 config-entry) | Covered | helper |
| Entity Search | Covered | entity-discovery |
| Service Calls | Covered | service-call |
| Relay Setup | Covered | onboarding |
| Dashboard / Lovelace (storage lifecycle, cards, resources) | Covered | dashboard |
| Scenes (storage CRUD) | Covered | scene |
| History Queries | Covered | history |
| Logbook Queries | Covered | history |
| Statistics / Trend Queries | Covered | history |
| System Health / Repairs | Covered | health |
| Logs / diagnostics (why a specific automation/script/device/integration failed: traces, error/system logs, root cause) | Covered | diagnose |
| Media players (transport, volume, source, grouping, browsing, TTS announce) | Covered | media |
| Notifications (targets, mobile-app sends, persistent notifications) | Covered | notify |
| Actionable-notification callbacks (waiting for a button press) | Roadmap (needs event subscriptions) | -- |
| Cameras (snapshot, stream URL, record) | Covered | camera |
| MQTT (bounded topic listening, discovery/debug info, publish) | Covered | mqtt |
| Voice / Assist (utterance testing, pipelines, entity exposure, engine inventory) | Covered | assist |
| Persons / Zones / Tags | Covered | admin |
| User accounts (list, create, delete — with owner/system guards) | Covered | admin |
| YAML-only configuration (template/REST/command-line sensors, packages, themes) | Covered | yaml-config |
| Frontend themes | Covered | yaml-config |
| External data stores (InfluxDB long-term history, Prometheus, ...) | Covered | external-sources |
Weather forecasts (weather.get_forecasts) | Covered | service-call |
| Calendar Queries | Covered | calendar |
| To-do Lists (items + Local To-do lifecycle) | Covered | todo |
| Area / Floor CRUD | Covered | organize |
| Label CRUD / Rich label metadata | Covered | organize |
| Category CRUD / Entity category assignment | Covered | organize |
| Entity / Device metadata updates | Covered | organize |
| Blueprints | Relay-Ready | this skill |
| Energy (analysis + source/device config) | Covered | energy |
| Other Config-Entry Helpers | Relay-Ready | this skill |
| Statistics repair / Purge / Entity registry remove | Covered | maintenance |
| Device config-entry detach | Relay-Ready | this skill |
| Event Subscriptions | Roadmap Phase 1c | -- |
| Backups (status, create, inspect, delete) | Covered | backup |
| Updates (pending, release notes, install, skip) | Covered | updates |
| Apps / Supervisor | External | -- |
| HACS | External | -- |
| Zigbee / Z-Wave Config | External | -- (MQTT-level inspection of a Zigbee2MQTT setup: mqtt) |
1. Check Capability Map for user's request
2. If "Covered" -> STOP, use the listed skill instead
3. If "Relay-Ready":
a. FIRST: Search web using the provided Search query — understand current payload schema before any call
b. Show experimental relay call examples informed by search results
c. Preview full payload before any write — never guess fields
d. Execute only after user confirms that exact preview (see context skill → Active Preview Confirmation)
4. If "Roadmap":
a. Explain which phase and what blocks it
b. Search web for manual workaround or alternative approach
c. Suggest HA UI as interim solution
5. If "External":
a. Explain why it's outside HA NOVA scope
b. Search web for current best practice (how to do it directly in HA)
c. Point to HA UI path
Web search is mandatory for Relay-Ready writes. The relay call examples below cover common read patterns, but write payloads change across HA versions. Always verify the current schema via web search before constructing a write payload.
List and import automation/script blueprints from the community or custom URLs.
Search: home assistant blueprint import automation api 2026
Experimental relay calls (no skill guardrails):
ha-nova relay ws --data-file <payload-file>
Risks: Imported blueprints execute when instantiated. Review blueprint source before import.
Handle unsupported config-entry helper types that are not yet owned by ha-nova:helper.
Owned by ha-nova:helper now:
utility_meterderivativeintegrationmin_maxthresholdtodstatisticsgrouphistory_statstemplateStill handled here:
trendrandomfiltergeneric_thermostatswitch_as_xgeneric_hygrostatSearch: home assistant config entry flow helper trend random filter generic_thermostat api 2026
Supported types in this fallback section: trend, random, filter, generic_thermostat, switch_as_x, generic_hygrostat
Experimental relay calls (no skill guardrails):
# Start create/reconfigure flow
ha-nova relay core --method POST --path /api/config/config_entries/flow --body-file <payload-file>
# Submit create/reconfigure step
ha-nova relay core --method POST --path /api/config/config_entries/flow/{flow_id} --body-file <payload-file>
# Start options flow for update when supported
ha-nova relay core --method POST --path /api/config/config_entries/options/flow --body-file <payload-file>
# Submit options step
ha-nova relay core --method POST --path /api/config/config_entries/options/flow/{flow_id} --body-file <payload-file>
# Delete unsupported config-entry helper by entry_id
ha-nova relay core --method DELETE --path /api/config/config_entries/entry/{entry_id}
Risks: Multi-step flows are complex. Each step returns the next step's schema. Update support can be domain- and version-specific. Delete requires correct entry_id resolution first. Prefer HA UI for these.
Remove a config entry from a device (entity-registry removal is owned by ha-nova:maintenance).
Search: home assistant device registry remove config entry websocket api 2026
Experimental relay calls (no skill guardrails):
ha-nova relay ws --data-file <payload-file>
Risks: Device detach depends on integration support (supports_remove_device) and can sever the current device/config-entry relationship. Preview impact first.
Real-time event streams for state changes, automation triggers, and custom events.
Search: home assistant event subscription state_changed real time api 2026
Status: Coming in Phase 1c. Blocked by: No SSE streaming endpoint in Relay.
Workaround: Poll entity state periodically via GET /api/states/{entity_id}.
Supervisor API is separate from HA Core API. Requires different auth and endpoints.
Search: home assistant supervisor app add-on install manage api 2026
Alternative: HA UI: Settings > Apps. Or ha CLI on HA OS.
Third-party integration with no stable public API.
Search: home assistant hacs install custom integration repository 2026
Alternative: HACS sidebar panel in HA UI.
Device pairing is hardware-specific, requires direct coordinator access (ZHA, Z2M, Z-Wave JS).
Search: home assistant zigbee2mqtt zha device pairing configuration 2026
Alternative: HA UI: Settings > Devices & Services > [Zigbee/Z-Wave integration].
Experimental calls may fail with unfamiliar errors. Full relay/upstream error taxonomy: skills/ha-nova/relay-api.md → Error Handling. Fallback-specific rules:
400/VALIDATION_ERROR: payload schema wrong -- search web for current WS type schema404/NOT_FOUND: endpoint may not exist in this HA version -- check HA release notes502/UPSTREAM_* transport errors: verify state/config first (see relay-api.md → Timeout and Retry Guidance); retry once only when verification shows no change, then route to ha-nova:onboardingApply skills/ha-nova/output-rules.md to all user-facing output.
Every experimental call result names the tier (Relay-Ready / Roadmap / External), carries the EXPERIMENTAL marker where required, and summarizes verified outcomes only.
confirm:<token> verbatim; "yes" or any natural-language reply is invalid.ha-nova relay.ha-nova:fallback first — never probe unfamiliar write endpoints.Premise handling:
Rules for all experimental relay calls in this skill:
lovelace/config/save): MUST read full config, merge changes in memory, preview merged result, then write. There is no partial update endpoint — the entire config is replaced. After the write, read the document back and verify both the intended change and the survival of unrelated content (views, cards, sources) before reporting success.energy/save_prefs): omitted top-level keys are preserved, but each provided key replaces its entire list. To add one item, read the existing list first, append, then save back the full list. After the write, read the prefs back and verify the pre-existing list items survived alongside the new one.## Changes preview or revert. When a write may be hard to reverse, say so plainly and point to Home Assistant Backups (Settings > System > Backups) as the safety net before confirming.skills/ha-nova/SKILL.md → Claim-Evidence Binding)| Type | Behavior | Safe pattern | Examples |
|---|---|---|---|
| Full-document overwrite | Entire config replaced | Read → modify → save full document → read back and verify unrelated content survived | lovelace/config/save |
| Field-level list replace | Omitted keys preserved, provided keys fully replaced | Read existing list → append/modify → save full list → read back and verify pre-existing items survived | energy/save_prefs |
| Merge/patch | Only provided fields updated | Send only changed fields | config/area_registry/update, config/entity_registry/update |
| Delete | Irreversible for areas/zones/labels | Always search/related first, tokenized confirmation | config/area_registry/delete, config/label_registry/delete (entity removal → ha-nova:maintenance) |
No HA WS endpoint has optimistic locking (no ETags, no version numbers). Last writer wins silently.
lovelace/config/save with a guessed or partial payload — this overwrites the ENTIRE dashboard config, destroying all other views and cardsenergy/save_prefs with a single source — this replaces the entire energy_sources list, deleting all existing sourcesha-nova relay ws/ha-nova relay core for unfamiliar operationsnpx claudepluginhub markusleben/ha-nova --plugin ha-novaOperates Home Assistant through HA NOVA (App + Relay) with local OS-backed auth, including relay health checks, self-update, and build reporting.
Teaches Home Assistant automation patterns using native triggers, helpers, and conditions instead of Jinja2 templates. Covers safe refactoring, Blueprints, Zigbee automations, and dashboard cards.
Develops custom Home Assistant integrations including config flows, entities, platforms, manifest.json, and device registry. Prevents common errors in coordinators, async setup, and entity registration.