← ClaudeAtlas

ha-addonlisted

Inspect, diagnose, and manage other Home Assistant add-ons via the Supervisor CLI. Use when asked to list/check/restart an add-on, read an add-on's logs, view its resource usage, or figure out why an add-on is failing, crashing, or unhealthy.
LayerTM/ClaudeInHA · ★ 0 · AI & Automation · score 70
Install: claude install-skill LayerTM/ClaudeInHA
Use the `ha` (Supervisor) CLI to inspect and manage sibling add-ons. This add-on has `hassio_api` access, so `ha addons ...` commands work with no extra auth. `$SUPERVISOR_TOKEN` is always in the environment for the API fallback. ## 1. Find the slug Add-ons are addressed by **slug** (e.g. `core_mosquitto`, `a0d7b954_nodered`), never the display name. ```bash ha addons # list installed add-ons: slug, name, version, state ``` Match the user's wording to a slug from that list. For structured filtering use the Supervisor API: ```bash curl -sS -H "Authorization: Bearer $SUPERVISOR_TOKEN" \ http://supervisor/addons | jq '.data.addons[] | {slug, name, state, version}' ``` ## 2. Inspect one add-on ```bash ha addons info <slug> # state, version, boot, options, url, ... ``` `state: started` = running, `stopped` = not running. The `options` block is the add-on's current configuration. ## 3. Read logs — the primary diagnostic ```bash ha addons logs <slug> # recent output ha addons logs <slug> | tail -50 # last lines ha addons logs <slug> | grep -iE 'error|warn|traceback|fail|exception' ``` Read the tail first to see the latest state, then grep for errors/stack traces to pin the failure. ## 4. Resource usage ```bash ha addons stats <slug> # CPU %, memory used/limit, network + disk I/O ``` Use when an add-on is slow, was OOM-killed, or is suspected of leaking. ## 5. Restart ```bash ha addons restart <slug> ``` Then confirm r