admin
/admin
Use when managing Home Assistant people, zones, tags, user accounts, general settings (name, location, units, time zone), Labs features, and analytics sharing — creating a person, drawing a zone, adding a tag, or reviewing who has access — through HA NOVA Relay.
- Author
- markusleben ↗
- Repository
- ha-nova ↗
- Licence
- MIT
- Last repository change
- 27.10.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 27.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Use when managing Home Assistant people, zones, tags, user accounts, general settings (name, location, units, time zone), Labs features, and analytics sharing — creating a person, drawing a zone, adding a tag, or reviewing who has access — through HA NOVA Relay.
Original author description
Use when managing Home Assistant people, zones, tags, user accounts, general settings (name, location, units, time zone), Labs features, and analytics sharing — creating a person, drawing a zone, adding a tag, or reviewing who has access — through HA NOVA Relay.
How it works
- Scope
- Bootstrap (once per session)
- Relay Contract
- Flow
- User Safety (read before touching accounts)
- Error Handling
- Output Format
- Safety
- Guardrails
SKILL.md preview
---
name: admin
description: Use when managing Home Assistant people, zones, tags, user accounts, general settings (name, location, units, time zone), Labs features, and analytics sharing — creating a person, drawing a zone, adding a tag, or reviewing who has access — 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 Admin
## Scope
The people-and-places layer of Home Assistant:
- persons (and which device trackers follow them)
- zones (home, work, school — the geofences presence automations depend on)
- tags (NFC/QR tags)
- user accounts: list, edit (name, administrator, active), and the account lifecycle (create/delete) with hard guards
- Home Assistant's general settings (name, location, units, time zone, currency, language, URLs)
- Labs (experimental features) and analytics sharing
Not in scope: areas, floors, labels, categories (`ha-nova:organize`), automations that USE presence (`ha-nova:write`), or authentication providers and passwords — those stay in the Home Assistant UI on purpose.
## 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`
## Relay Contract
- `ha-nova relay ws --data-file <payload-file>` for every command here
- `--out <result-file>` for large listings
- account edits, general settings, Labs, and analytics: one WS item through `ha-nova plan raw --file <requests.json>`, then `ha-nova apply`
## Flow
1. **Persons**: WS `person/list` -> `person/create` / `person/update` / `person/delete`.
- a person links `device_trackers` (which follow them) and optionally a `user_id` (their login)
- update resends every mutable field (read first, or you drop their trackers), addressed by `person_id` — never put `id` in the body, Home Assistant rejects it. Zone and tag updates work the same way (`zone_id` / `tag_id`).
2. **Zones**: WS `zone/list` -> `zone/create` / `zone/update` / `zone/delete`.
- a zone is `name`, `latitude`, `longitude`, `radius` (metres), `icon`, `passive`
- **Zones are presence infrastructure.** Changing a radius or deleting a zone silently changes when every presence automation fires. Before any zone change, run WS `search/related` with `{"item_type":"entity","item_id":"zone.<id>"}` (there is no `zone` item type) and name the automations that depend on it — as an advisory, in the preview.
- the `home` zone is special: it comes from core config, not the zone registry. Changing home means changing the location in General settings (step 5) — say so instead of trying to delete it.
3. **Tags**: WS `tag/list` -> `tag/create` / `tag/update` / `tag/delete`. A tag's `tag_id` is what the NFC/QR tag physically carries; scanning fires an event automations listen for. Deleting a tag breaks those automations, not the sticker.
4. **Users**: WS `config/auth/list` shows accounts (`id`, `name`, `username`, `is_owner`, `is_active`, `system_generated`, `group_ids`).
- create payload: `{"type":"config/auth/create","name":"<display name>","group_ids":["system-users"],"local_only":false}` — `system-admin` in `group_ids` makes the account an administrator, so name that in the preview. The password is set in Settings → People, never here
- before any delete: WS `auth/current_user` returns the account this relay's token belongs to — that account is never deletable
- edit: `{"type":"config/auth/update","user_id":"<id>"}` plus requested fields: `name`, `is_active`, `local_only`, `group_ids` (`["system-admin"]` administrator, `["system-users"]` user). Any access field takes the one-time code; the CLI refuses it for the owner, a system account, and the relay's own account
5. **General settings**: `get_config` reads them; `config/core/detect` suggests location, units, and currency. Change with `config/core/update` plus requested fields: `location_name`, `latitude`, `longitude`, `elevation`, `radius`, `unit_system` (with `update_units` to convert entities), `time_zone`, `currency`, `country`, `language`, `internal_url`, `external_url`. Time zone and units take the one-time code: history and long-term statistics shift, and units can raise unit mismatches (`ha-nova:maintenance`). The location is the `home` zone: name presence automations (step 2's `search/related` on `zone.home`).
6. **Labs and analytics**: `labs/list` lists features; `labs/update` with `domain`, `preview_feature`, `enabled` takes the one-time code; a backup first runs through `ha-nova:backup`, never `create_backup`. `analytics` reads what is shared; `analytics/preferences` with `preferences` (only changed keys of `base`, `diagnostics`, `usage`, `statistics`, `snapshots`) is previewed.
7. Verify every write by re-reading the list (`get_config` for settings) — never from the command response alone.
## User Safety (read before touching accounts)
- **Never delete the owner** (`is_owner: true`). Home Assistant would be left without an administrator. Refuse and explain.
- **Never delete a `system_generated` account** — those belong to integrations, not people.
- **Never delete the account whose token this relay uses.** Identify it first with WS `auth/current_user`; if that call fails, do not delete any account.
- Deleting a user does not delete their person entry, their history, or their long-lived tokens' effects — say so.
## Error Handling
Full relay/upstream error taxonomy: `../ha-nova/relay-api.md` -> Error Handling. Admin specifics:
- `config/auth/*` requires owner/admin rights upstream: a permission error here means the Relay's upstream credential lacks HA admin (App: Supervisor credential; container: the host-side `HA_LLAT`), not that the command is wrong.
## Output Format
Apply `../ha-nova/output-rules.md`: plain words, HA names verbatim; unless asked or names clash, no ids, "entity", modes, Relay/HA URLs, snapshots, raw JSON. Previews, deletes, and results use the Cards defined there (`../ha-nova/output-cards.md`).
Render the Report shape (output-cards.md); person/zone/user inventories render the List Frame. For persons: name, device trackers, linked user. For zones: name, radius, and which automations depend on them. For users: name, whether they are owner/active/system-generated — never their tokens or credentials. State what was verified after the write.
## Safety
- Preview before write. The only exception is a call that `ha-nova call` itself executed as `tier: ordinary`; everything else waits for the user's confirmation of the shown preview. High-consequence actions (e.g. unlocking or opening a lock, opening a gate, garage, or entry door, disarming the alarm — also through a scene or script) and deletes or other destructive operations need the user's window click or phone tap, else their one-time code from HA NOVA; "yes" or any other reply is invalid.
- Confirmation binds to the displayed preview; any target, payload, endpoint, or scope change voids it (context skill → Active Preview Confirmation).
- Relay a plan's `say` in full, localized; never drop or shorten sentences.
- Anything before the preview ("do it", answers to questions) never confirms it; only a reply to the preview does.
- Never guess entity, service, or config IDs — resolve them or ask.
- Home Assistant is reached exclusively through the `ha-nova` CLI.
- Any HA write this skill does not cover: STOP, invoke `ha-nova:fallback` first; never probe unfamiliar write endpoints.
- Drafts follow `../ha-nova/smallest-solution.md`: the complete requested outcome in the simplest safe design, nothing speculative.
- `search/related` verdicts fail closed: verify `ok=true` and `data` is an object before projecting family keys (`../ha-nova/relay-api.md` → Parsing rule); a failed or unexecuted scan is inconclusive — never a no-consumer result.
- Zone and person deletes take the one-time code, and the preview must first name the automations that depend on them (`search/related`).
- User deletion is the strictest operation in HA NOVA: owner, system-generated, and the relay's own account are refused outright, and everything else needs the one-time code plus a plain statement of what is lost.
- Creating a user account grants durable system access, so it takes the one-time code too — not the ordinary create tier. The preview names the login name, whether the account is an administrator (`group_ids`), and that the password is set in the Home Assistant UI, never here.
- No delete here has a `revert`. Zones, persons, and tags are recreatable from their previewed fields — a tag keeps its physical `tag_id`, but other recreates mint new internal ids, so inbound references stay broken. A deleted user's password, tokens, and history are unrecoverable; the delete preview must say so.
- Offer a safety backup via `ha-nova:backup` before zone, person, and user deletes (not for tag deletes or routine updates).
## Guardrails
- One person, zone, tag, or user per operation.
- Never guess a `person_id`, `zone_id`, `tag_id`, or user `id`.
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · markusleben/ha-nova | 90 | MIT |
| yc-software/qm | 100 | MIT |
| evolvingagentslabs/evolving-agents | 100 | Apache-2.0 |
| grafana/skills | 100 | Apache-2.0 |
| devv-shayan/8x-hackathon | 100 | MIT |
Database snapshot: 13.11.2026 · package version 3395463e8697 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100scene
Use when listing, reading, creating, updating, or deleting Home Assistant storage scenes through HA NOVA Relay. For activating a scene, use ha-nova:service-call. - 100ha-nova
Questions about the user's Home Assistant — rooms, devices, modes, where something is used — go through ha-nova, not file search. Use for reviews and multi-step or multi-target Home Assistant work through HA NOVA (App + Relay; the demo house via `--server demo`), or when no… - 100home-assistant-best-practices
Selects Home Assistant automation, helper, device-control, and dashboard patterns. Use for HA configuration design, refactoring, or AppDaemon apps. - 100home-assistant
Control Home Assistant smart home devices, run automations, and receive webhook events. Use when controlling lights, switches, climate, scenes, scripts, or any HA entity. Supports bidirectional communication via REST API (outbound) and webhooks (inbound triggers from HA automations). - 100home-assistant
Home Assistant is an open-source home automation server that controls lights, sensors, thermostats and other smart devices locally, without a cloud account. Use when a user asks to install Home Assistant with Docker, edit configuration.yaml, write or debug a YAML automation,… - 100home-assistant
Use when automating a smart home with Home Assistant 2026.10 — configuration.yaml and automations.yaml, triggers/conditions/actions YAML, REST API /api/states and /api/services, WebSocket subscribe_events, long-lived access tokens, Docker container installs; also for…