# Ha Deploy

> Validates, reloads, and verifies an existing Home Assistant deployment through its API. Use after overlay-owned configuration has been placed on the owning host. Container lifecycle and file deployment remain outside this skill.

- Skill: `larsboes/ha-deploy` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add larsboes/ha-deploy`
- Raw SKILL.md: https://api.skillmd.com/api/skills/larsboes/ha-deploy/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: DevOps & Infra
- Author: larsboes (https://skillmd.com/u/larsboes)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/larsboes/ha-deploy

---


# ha-deploy

This skill covers the safe API boundary after configuration is already present on the Home
Assistant host:

```sh
scripts/ha-deploy check
scripts/ha-deploy reload
scripts/ha-deploy verify
```

- `check` asks Home Assistant to validate its current configuration.
- `reload` applies reloadable YAML domains without restarting the service.
- `verify` requires Home Assistant to report `RUNNING` and summarizes automation states.

The retired SSH/git-pull deployment path is intentionally absent. Container changes go through
`tools/service-runner.sh`; overlay configuration placement belongs to the owning overlay.

Connection facts come from the active overlay. The token comes from the private secret mechanism
at runtime and is never printed. Confirm before `reload`, because it mutates the running instance.