home-assistant

Home Assistant Control

This skill enables Claude to interact with a Home Assistant instance via its REST API — querying device states, controlling smart home devices, reviewing history, and working with automations.

Slash Command

When invoked via /home-assistant, ensure authentication is set up (see below), then ask the user what they'd like to do — for example: check device status, control lights, adjust the thermostat, view history, or manage automations.

Setup & Authentication

Configuration lives in ~/.config/home-assistant/.env. On first use, check if this file exists:

cat ~/.config/home-assistant/.env 2>/dev/null || echo "NOT_FOUND"

If the file exists, source it to load HA_URL and HA_TOKEN:

source ~/.config/home-assistant/.env

If the file doesn't exist, walk the user through setup:

1. Explain what's needed: a Home Assistant URL and a Long-Lived Access Token
2. Ask for their HA URL (e.g., http://192.168.1.100:8123 or https://home.example.com)
3. Guide them to create a token: Go to their HA instance → Profile (bottom-left) → Security tab → scroll to "Long-Lived Access Tokens" → click "Create Token" → give it a name like "Claude" → copy the token
4. Create the config:

mkdir -p ~/.config/home-assistant
cat > ~/.config/home-assistant/.env << 'EOF'
HA_URL="http://your-ha-address:8123"
HA_TOKEN="your_token_here"
EOF
chmod 600 ~/.config/home-assistant/.env

Replace the placeholder values with what the user provides. The chmod 600 ensures only the user can read the token.

After sourcing, verify connectivity:

source ~/.config/home-assistant/.env
curl -s -H "Authorization: Bearer $HA_TOKEN" "$HA_URL/api/"

Expected response: {"message": "API running."}. If it fails, check the URL and token with the user.

Workflow

Follow this general approach for any Home Assistant task:

1. Discover what's available

Before trying to control or query specific devices, find out what entities exist. Run the discovery script to get a formatted overview: