admin
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.
markusleben · 已有静态检查记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add markusleben/ha-nova --skill admin技能说明
name: admin description: 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. 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, and the account lifecycle (create/delete) with hard guards
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
Flow
- Persons: WS
person/list->person/create/person/update/person/delete.- a person links
device_trackers(which follow them) and optionally auser_id(their login) - update resends every mutable field (read first, or you drop their trackers), addressed by
person_id— never putidin the body, Home Assistant rejects it. Zone and tag updates work the same way (zone_id/tag_id).
- a person links
- 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/relatedwith{"item_type":"entity","item_id":"zone.<id>"}(there is nozoneitem type) and name the automations that depend on it — as an advisory, in the preview. - the
homezone is special: it comes from core config, not the zone registry. Changing home means changing the Home Assistant location (homeassistant.reload_core_configterritory) — say so instead of trying to delete it.
- a zone is
- Tags: WS
tag/list->tag/create/tag/update/tag/delete. A tag'stag_idis what the NFC/QR tag physically carries; scanning fires an event automations listen for. Deleting a tag breaks those automations, not the sticker. - Users: WS
config/auth/listshows accounts (id,name,username,is_owner,is_active,system_generated,group_ids).- listing and reviewing access is the safe, common case
config/auth/create/config/auth/deleteexist, and are the most dangerous writes in HA NOVA- create payload:
{"type":"config/auth/create","name":"<display name>","group_ids":["system-users"],"local_only":false}—system-adminingroup_idsmakes the account an administrator, so name that in the preview. The password is NOT set here: Home Assistant issues the credential separately, so tell the user to finish in Settings → People rather than offering to set one - before any delete: WS
auth/current_userreturns the account this relay's token belongs to — that account is never deletable
- Verify every write by re-reading the list — 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_generatedaccount — 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.
- Passwords and authentication providers are deliberately out of scope: send the user to the Home Assistant UI.
Error Handling
Full relay/upstream error taxonomy: skills/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-sideHA_LLAT), not that the command is wrong.- Deleting a zone that automations reference succeeds — Home Assistant does not stop you. The damage shows up later, which is exactly why the impact advisory runs before the write.
Output Format
Apply skills/ha-nova/output-rules.md to all user-facing output. Write previews, delete confirmations, and results render as the Cards defined there.
Render the Report shape (output-rules.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: nothing is saved until the user confirms the shown preview.
-
Confirmation binds to the displayed preview and expires on any change to target, payload, endpoint, or scope (context skill → Active Preview Confirmation).
-
Pre-preview phrases ("do it", "go ahead", "implement the plan") authorize drafting and preview only — never the write itself.
-
Delete and destructive operations require the typed confirmation code
confirm:<token>verbatim; "yes" or any natural-language reply is invalid. -
Never guess entity, service, or config IDs — resolve them or ask.
-
Home Assistant is reached exclusively through
ha-nova relay. -
For any HA write this skill does not cover, STOP and invoke
ha-nova:fallbackfirst — never probe unfamiliar write endpoints. -
Drafts follow `skills/h