بنقرة واحدة
onboarding
Use when HA NOVA Relay requests fail due to onboarding, connectivity, or auth issues.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
القائمة
Use when HA NOVA Relay requests fail due to onboarding, connectivity, or auth issues.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | onboarding |
| description | Use when HA NOVA Relay requests fail due to onboarding, connectivity, or auth issues. |
| 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). |
Use when HA NOVA requests fail due to onboarding, connectivity, or auth issues. Diagnostics only. Do not use this skill for config writes or routine HA operations after readiness is restored.
If the ha-nova command itself is missing, the CLI is not installed — install it first from the latest GitHub release (https://github.com/markusleben/ha-nova/releases/latest carries the copy-paste install command per OS), then run ha-nova setup. Never bootstrap from the repo's main branch: released skills must install the reviewed, tagged release.
When the CLI exists, read and follow
../ha-nova/session-bootstrap.md before the first HA task.
Relay CLI command: ha-nova relay
If missing: ha-nova setup
401/403: relay auth token mismatch404: endpoint/path mismatch000: relay unreachableha_ws_connected=false: the reason can be passive or stale because health/REST reads do not open WS. Send WS {"type":"ping"}, then re-read health before diagnosing any auth, network, or never_connected value. Ping ok: true plus post-ping ha_ws_connected: true proves readiness. Otherwise classify the ping error and post-health reason: auth means upstream authentication was rejected (App: update/restart Relay; standalone: replace HA_LLAT); network means HA remains unreachable/restarting; never_connected alone never proves a bad HA_URL or network path. Older relays omit the reason — use the ping result or ha-nova doctor/ws on an older Relay proves LLAT is required: update the App; only standalone Container/Core should repair HA_LLATdesktop keyring locked / secure storage is present but locked during setup or pairing: the machine has a Secret Service that never gets unlocked (headless VM, autologin box, systemd user service). Do not ask the user to unlock it on every boot — use the explicit file backend instead: ha-nova setup --service <client>, or ha-nova pair --credential-store=fileha-nova setupha-nova relay healthha-nova doctorha-nova setup --service <client> — or standalone: ha-nova pair --credential-store=fileApply skills/ha-nova/output-rules.md to all user-facing output.
Return a short diagnostic report:
On success, keep the response to the status line only. Do not dump raw relay output.
Read-only skill: never issue mutating relay or service calls.
For write intent, hand off to the owning skill; unfamiliar writes go through ha-nova:fallback first.
Diagnostics only — this skill never modifies Home Assistant state, config, or relay settings.
Never ask the user to paste tokens or secrets in chat.
All communication with Home Assistant goes through ha-nova relay exclusively.
Use when the user wants Home Assistant operations through HA NOVA (App + Relay) with local OS-backed auth.
Use when checking Home Assistant home status, repairs, system health, unavailable/unknown entities, low batteries, or component/config summaries through HA NOVA Relay.
Use when checking pending Home Assistant updates (core, OS, Apps, integrations, device firmware), reading release notes, installing updates with safety gates, or skipping/unskipping update versions through HA NOVA Relay.
Use when managing Home Assistant people, zones, tags, and user accounts — creating a person, drawing a zone, adding a tag, or reviewing who has access — through HA NOVA Relay.
Use when working with Home Assistant's voice assistant — testing what Assist understands, inspecting or editing Assist pipelines, managing which entities are exposed to voice, and listing TTS/STT/wake-word engines — through HA NOVA Relay.
Use when checking Home Assistant backup status, creating a backup (including a safety backup before risky changes), inspecting backups, or deleting old backups through HA NOVA Relay.