Stats
Actions
Tags
From homeassist
Validate, deploy, and verify Home Assistant configuration changes
How this command is triggered — by the user, by Claude, or both
Slash command
/homeassist:ha-deployThe summary Claude sees in its command listing — used to decide when to auto-load this command
# HA Deploy Workflow Safely deploy Home Assistant configuration changes with validation: ## Pre-deploy 1. **Check config** — `homeassist config check` - If invalid, stop and show the error. Do not proceed. 2. **Review changes** — show what files were modified (use git diff if in a repo) ## Deploy 3. **Reload components** — based on what changed: - Automations modified: `homeassist config reload automations` - Scripts modified: `homeassist config reload scripts` - Scenes modified: `homeassist config reload scenes` - Multiple: `homeassist config reload all` - If changes...
Safely deploy Home Assistant configuration changes with validation:
homeassist config check
homeassist config reload automationshomeassist config reload scriptshomeassist config reload sceneshomeassist config reload allhomeassist health — confirm still connectedhomeassist automations list --compact — check stateshomeassist entities get <entity_id> — confirm not "unavailable"homeassist services call pyscript.run_<feature>_testsIf verification fails:
npx claudepluginhub jsnyder/homeassist --plugin homeassist/ha-deployDeploys Home Assistant on Ubuntu servers using Docker with complementary services like MariaDB, MQTT, Zigbee2MQTT, Node-RED, Grafana, and Ollama. Also supports update, backup, restore, status, and logs.