Deploy Home Assistant config changes via Ansible and verify they loaded in the live instance.
npx skills add https://github.com/DanielH2018/server --skill ha-deploy-danielh2018
Please help me install this Agent Skill. Skill: ha-deploy Source: https://github.com/DanielH2018/server/tree/main/.claude/skills/ha-deploy Command: npx skills add https://github.com/DanielH2018/server --skill ha-deploy-danielh2018
unknown. This Skill closes that gap by gating every deploy on live-state verification, not just playbook exit codes. ## Core Features & Use Cases - Validated deployment: Runs structural validation and Jinja macro tests before shipping config via the Ansible home-assistant tag to the k3s cluster. - Live load verification: Asserts every automation in files/automations/*.yaml exists and is not unavailable, and diffs referenced entities against the live instance to catch silent disappearances. - Targeted proof: Checks that an edited automation's last_triggered advances or an edited entity's last_updated postdates the container restart. - Use Case: After editing an automation YAML under ansible/roles/k8s/home-assistant/, deploy it and confirm the automation actually loaded and fired — catching the case where two vanished sensors left three features inert behind a green validation. ## Quick Start Deploy my Home Assistant config changes and verify the automations actually loaded in the live instance.High-intent search queries and answers about installing and using this skill.
Run ./scripts/deploy.sh --tags "home-assistant" from the repo root on the k3s control-plane host. The wrapper takes a deploy lock and ships the config as a ConfigMap with a rollout restart; exit 75 means the lock was busy and nothing deployed.
Run the probe script's verify-automations command, which checks every automation in files/automations/*.yaml exists in the live instance and is not unavailable. A non-zero exit lists the ids Home Assistant silently skipped due to schema errors.
Static validation resolves entity references against a snapshot file, so an entity that stopped existing in the live instance still reads as valid. Run verify-entities every deploy to diff the snapshot against live state and catch disappearances.
No. A new file must be added to the appropriate home_assistant_*_files list in the role's defaults/main.yml, because the ConfigMap only includes listed files. Unlisted files never reach /config and fail structural validation.
No. The "could not validate that the sqlite3 database was shutdown cleanly" message on boot is benign because WAL auto-recovers. Treat the deploy as failed only if the pod is not 1/1 Running or live verification probes fail.
L3DigitalNetAutomate Home Assistant integration publishing to HACS with GitHub Actions validation.
jackmcintyreInspect Home Assistant entity states and access log files for error tracing.
nampham2Run pytest suites, verify 100% coverage, and validate pre-commit hooks.
pascalandyManage dotfiles through the chezmoi source repository using standard commands.