← Back to Skills Marketplace
eohmig

Home Assistant Backup

by eohmig · GitHub ↗ · v1.0.0 · MIT-0
cross-platform ⚠ suspicious
50
Downloads
0
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install home-assistant-backup
Description
Control Home Assistant smart home devices, run automations, and receive webhook events. Use when controlling lights, switches, climate, scenes, scripts, or a...
README (SKILL.md)

Home Assistant

Control your smart home via Home Assistant's REST API and webhooks.

Setup

Option 1: Config File (Recommended)

Create ~/.config/home-assistant/config.json:

{
  "url": "https://your-ha-instance.duckdns.org",
  "token": "your-long-lived-access-token"
}

Option 2: Environment Variables

export HA_URL="http://homeassistant.local:8123"
export HA_TOKEN="your-long-lived-access-token"

Getting a Long-Lived Access Token

  1. Open Home Assistant → Profile (bottom left)
  2. Scroll to "Long-Lived Access Tokens"
  3. Click "Create Token", name it (e.g., "Clawdbot")
  4. Copy the token immediately (shown only once)

Quick Reference

List Entities

curl -s -H "Authorization: Bearer $HA_TOKEN" "$HA_URL/api/states" | jq '.[].entity_id'

Get Entity State

curl -s -H "Authorization: Bearer $HA_TOKEN" "$HA_URL/api/states/light.living_room"

Control Devices

# Turn on
curl -X POST -H "Authorization: Bearer $HA_TOKEN" -H "Content-Type: application/json" \
  "$HA_URL/api/services/light/turn_on" -d '{"entity_id": "light.living_room"}'

# Turn off
curl -X POST -H "Authorization: Bearer $HA_TOKEN" -H "Content-Type: application/json" \
  "$HA_URL/api/services/light/turn_off" -d '{"entity_id": "light.living_room"}'

# Set brightness (0-255)
curl -X POST -H "Authorization: Bearer $HA_TOKEN" -H "Content-Type: application/json" \
  "$HA_URL/api/services/light/turn_on" -d '{"entity_id": "light.living_room", "brightness": 128}'

Run Scripts & Automations

# Trigger script
curl -X POST -H "Authorization: Bearer $HA_TOKEN" "$HA_URL/api/services/script/turn_on" \
  -H "Content-Type: application/json" -d '{"entity_id": "script.goodnight"}'

# Trigger automation
curl -X POST -H "Authorization: Bearer $HA_TOKEN" "$HA_URL/api/services/automation/trigger" \
  -H "Content-Type: application/json" -d '{"entity_id": "automation.motion_lights"}'

Activate Scenes

curl -X POST -H "Authorization: Bearer $HA_TOKEN" "$HA_URL/api/services/scene/turn_on" \
  -H "Content-Type: application/json" -d '{"entity_id": "scene.movie_night"}'

Common Services

Domain Service Example entity_id
light turn_on, turn_off, toggle light.kitchen
switch turn_on, turn_off, toggle switch.fan
climate set_temperature, set_hvac_mode climate.thermostat
cover open_cover, close_cover, stop_cover cover.garage
media_player play_media, media_pause, volume_set media_player.tv
scene turn_on scene.relax
script turn_on script.welcome_home
automation trigger, turn_on, turn_off automation.sunrise

Inbound Webhooks (HA → Clawdbot)

To receive events from Home Assistant automations:

1. Create HA Automation with Webhook Action

# In HA automation
action:
  - service: rest_command.notify_clawdbot
    data:
      event: motion_detected
      area: living_room

2. Define REST Command in HA

# configuration.yaml
rest_command:
  notify_clawdbot:
    url: "https://your-clawdbot-url/webhook/home-assistant"
    method: POST
    headers:
      Authorization: "Bearer {{ webhook_secret }}"
      Content-Type: "application/json"
    payload: '{"event": "{{ event }}", "area": "{{ area }}"}'

3. Handle in Clawdbot

Clawdbot receives the webhook and can notify you or take action based on the event.

CLI Wrapper

The scripts/ha.sh CLI provides easy access to all HA functions:

# Test connection
ha.sh info

# List entities
ha.sh list all          # all entities
ha.sh list lights       # just lights
ha.sh list switch       # just switches

# Search entities
ha.sh search kitchen    # find entities by name

# Get/set state
ha.sh state light.living_room
ha.sh states light.living_room   # full details with attributes
ha.sh on light.living_room
ha.sh on light.living_room 200   # with brightness (0-255)
ha.sh off light.living_room
ha.sh toggle switch.fan

# Scenes & scripts
ha.sh scene movie_night
ha.sh script goodnight

# Climate
ha.sh climate climate.thermostat 22

# Call any service
ha.sh call light turn_on '{"entity_id":"light.room","brightness":200}'

Troubleshooting

  • 401 Unauthorized: Token expired or invalid. Generate a new one.
  • Connection refused: Check HA_URL, ensure HA is running and accessible.
  • Entity not found: List entities to find the correct entity_id.

API Reference

For advanced usage, see references/api.md.

Usage Guidance
Install only if you are comfortable giving the agent authenticated control over Home Assistant. Use a dedicated least-privilege Home Assistant account if possible, protect the token file with restrictive permissions, avoid exposing tokens or webhook IDs, prefer HTTPS/WSS, and require explicit confirmation before actions involving locks, garage doors/covers, alarms, climate, scripts, automations, or generic service calls.
Capability Tags
requires-oauth-tokenrequires-sensitive-credentials
Capability Assessment
Purpose & Capability
The core purpose is coherent: controlling Home Assistant devices, scenes, scripts, automations, and querying state. The concern is breadth: it exposes generic service calls and automation/script execution that can affect physical devices such as covers, climate systems, and any configured Home Assistant service.
Instruction Scope
Activation and examples are broad, including 'any HA entity' and 'call any service,' without confirmation guidance for high-impact actions or warnings about chained automations and physical side effects.
Install Mechanism
No suspicious package installation was found. The skill declares curl and jq requirements and provides a shell wrapper, which matches its documented REST API approach.
Credentials
Network access to a Home Assistant instance and use of authenticated API calls are expected, but the authority is high-impact because successful commands can change a user's physical environment.
Persistence & Privilege
The setup recommends storing a long-lived Home Assistant access token in a local JSON config file, but does not document restrictive file permissions, token rotation, or the risks of exposing that credential.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install home-assistant-backup
  3. After installation, invoke the skill by name or use /home-assistant-backup
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
Initial release of home-assistant-backup skill. - Control Home Assistant smart home devices, automations, and scenes via REST API. - Supports inbound webhook triggers from Home Assistant automations. - Provides CLI wrapper (`scripts/ha.sh`) for easy command-line control. - Setup via config file or environment variables. - Includes troubleshooting tips and quick-reference API examples.
Metadata
Slug home-assistant-backup
Version 1.0.0
License MIT-0
All-time Installs 0
Active Installs 0
Total Versions 1
Frequently Asked Questions

What is Home Assistant Backup?

Control Home Assistant smart home devices, run automations, and receive webhook events. Use when controlling lights, switches, climate, scenes, scripts, or a... It is an AI Agent Skill for Claude Code / OpenClaw, with 50 downloads so far.

How do I install Home Assistant Backup?

Run "/install home-assistant-backup" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is Home Assistant Backup free?

Yes, Home Assistant Backup is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does Home Assistant Backup support?

Home Assistant Backup is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created Home Assistant Backup?

It is built and maintained by eohmig (@eohmig); the current version is v1.0.0.

💬 Comments