Skill: Home Assistant Clawbridge

Owner: finalbillybong

Summary: Control Home Assistant devices via ClawBridge API. Use when users ask to turn lights on/off, check device states, or interact with any exposed Home Assistant entities. Handles entity discovery, state checks, and service calls with human approval flow.

Tags: latest:1.0.1

Version history:

v1.0.1 | 2026-02-12T18:47:01.935Z | user

• Expanded documentation for installation, configuration, and usage, including a new "What is ClawBridge?" overview.
• Generalized and clarified all endpoint, token, and webhook instructions (no hardcoded IPs or secrets).
• Added sections on security, audit, and the advantages of ClawBridge compared to direct Home Assistant API access.
• Updated process management instructions for starting and stopping notification scripts.
• Improved structure and explanations throughout; added a license section.

v1.0.0 | 2026-02-12T18:33:40.052Z | user

Initial release of home-assistant-clawbradge.

• Control and monitor Home Assistant devices via the ClawBridge API.
• Real-time device state notifications to Discord through Python script; instant, zero server-side cost.
• Human approval flow for device control actions.
• Includes configuration, entity filtering, monitoring, and command usage instructions.
• Provides example scripts and API calls for checking and controlling devices.

Archive index:

Archive v1.0.1: 2 files, 2041 bytes

Files: SKILL.md (3829b), _meta.json (144b)

File v1.0.1:SKILL.md

---

name: home-assistant description: Control Home Assistant devices via ClawBridge API. Use when users ask to turn lights on/off, check device states, or interact with any exposed Home Assistant entities. Handles entity discovery, state checks, and service calls with human approval flow.

Home Assistant Skill

Control Home Assistant devices through ClawBridge (air-gapped API proxy with human approval).

What is ClawBridge?

ClawBridge is an API gateway that sits between AI agents and Home Assistant:

• Token isolation: Your HA token never leaves ClawBridge
• Human approval: Service calls require explicit approval via web UI
• Read-only by default: AI can query sensors/state freely
• Audit trail: Logs every request for transparency

Configuration

• Base URL: http://YOUR_CLAWBRIDGE_IP:PORT (e.g., http://192.168.1.100:8100)
• API Key: Generate in ClawBridge web UI
• Discord Webhook: (Optional) For real-time notifications

Installation

1. Install ClawBridge as a Home Assistant add-on or standalone Docker container
2. Generate an API key in the ClawBridge web UI
3. Configure the Discord webhook (optional, for notifications)
4. Edit scripts/ha-discord.py to set your entity filters

Real-Time Notifications

Python → Discord Direct — zero AI cost, instant delivery.

Start Monitoring

python3 /path/to/skills/home-assistant/scripts/ha-discord.py &

Stop Monitoring

# Find the process and kill it
pgrep -f ha-discord.py
kill <PID>

Filter Entities

Edit scripts/ha-discord.py:

# Watch only these (empty = all)
WATCH_ENTITIES = ["light.office", "binary_sensor.front_door"]

# Ignore these
IGNORE_ENTITIES = ["sensor.cpu_temp"]

Device Control

Check Exposed Entities

curl -s "http://YOUR_CLAWBRIDGE_IP:PORT/api/states" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  | grep -o '"entity_id": "[^"]*"' | cut -d'"' -f4

Check Entity State

curl -s "http://YOUR_CLAWBRIDGE_IP:PORT/api/states/{entity_id}" \
  -H "Authorization: Bearer YOUR_API_KEY"

Control a Device

curl -s -X POST "http://YOUR_CLAWBRIDGE_IP:PORT/api/services/{domain}/{service}" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"entity_id": "{entity_id}"}'

Note: Service calls require human approval via ClawBridge web UI.

Quick Script

./skills/home-assistant/scripts/ha-control.sh state light.office
./skills/home-assistant/scripts/ha-control.sh on light.office
./skills/home-assistant/scripts/ha-control.sh off light.office

Notification Formats

| Domain | Message | |--------|---------| | light | 💡 {name} turned on/off | | switch | 🔌 {name} turned on/off | | binary_sensor (door) | 🚪 {name} opened/closed | | binary_sensor (motion) | 📡 {name} motion detected | | person | 👤 {name} is now {state} | | lock | 🔒 {name} locked/unlocked | | other | 🔔 {name} old → new |

Scripts

| Script | Purpose | |--------|---------| | ha-discord.py | Primary — WebSocket → Discord direct (zero cost) | | ha-monitor.py | WebSocket → file (for cron-based delivery) | | ha-control.sh | Quick CLI for on/off/state |

Why ClawBridge?

The Problem with Standard HA AI Integration

• Long-lived tokens = full API access
• No approval workflow for destructive actions
• One prompt injection = uncontrolled home access

The ClawBridge Solution

• AI gets scoped API keys (not your HA token)
• Service calls queue for human approval
• Read operations pass through instantly
• Full audit trail of every request

API Reference

See references/clawbridge-api.md

License

MIT - Contributions welcome!

File v1.0.1:_meta.json

{ "ownerId": "kn7914ekxf0n1eb58r1nx410dx80y7hr", "slug": "home-assistant-clawbradge", "version": "1.0.1", "publishedAt": 1770922021935 }

Archive v1.0.0: 2 files, 1737 bytes

Files: SKILL.md (3093b), _meta.json (144b)

File v1.0.0:SKILL.md

---

name: home-assistant description: Control Home Assistant devices via ClawBridge API. Use when James asks to turn lights on/off, check device states, or interact with any exposed Home Assistant entities. Handles entity discovery, state checks, and service calls with human approval flow.

Home Assistant Skill

Control Home Assistant devices through ClawBridge (air-gapped API).

Configuration

• Base URL: http://192.168.0.238:8100
• API Key: cb_Z2_Kcoc5Efrztj58lk7SlpZISkwbYlkAkxYjLc_U6lY
• Discord Webhook: https://discord.com/api/webhooks/1471253559323656194/bGAVuOBcC66p7pyuUFN465lXOHdeScffN1ZyclDj1jb8kmgvocgBwd6J-F5W6qmNQymf

Real-Time Notifications (Primary Method)

Python → Discord Direct — zero AI cost, instant delivery.

Start Monitoring

python3 /root/.openclaw/workspace/skills/home-assistant/scripts/ha-discord.py &

Stop Monitoring

process kill sessionId={session_id}

Filter Entities

Edit scripts/ha-discord.py:

# Watch only these (empty = all)
WATCH_ENTITIES = ["light.office", "binary_sensor.front_door"]

# Ignore these
IGNORE_ENTITIES = ["sensor.cpu_temp"]

When James Asks to Monitor a New Device

1. Ask: What's the entity_id? What state to watch for?
2. Update WATCH_ENTITIES or IGNORE_ENTITIES in the script
3. Restart the monitor

Device Control

Check Exposed Entities

curl -s "http://192.168.0.238:8100/api/states" \
  -H "Authorization: Bearer cb_Z2_Kcoc5Efrztj58lk7SlpZISkwbYlkAkxYjLc_U6lY" \
  | grep -o '"entity_id": "[^"]*"' | cut -d'"' -f4

Check Entity State

curl -s "http://192.168.0.238:8100/api/states/{entity_id}" \
  -H "Authorization: Bearer cb_Z2_Kcoc5Efrztj58lk7SlpZISkwbYlkAkxYjLc_U6lY"

Control a Device

curl -s -X POST "http://192.168.0.238:8100/api/services/{domain}/{service}" \
  -H "Authorization: Bearer cb_Z2_Kcoc5Efrztj58lk7SlpZISkwbYlkAkxYjLc_U6lY" \
  -H "Content-Type: application/json" \
  -d '{"entity_id": "{entity_id}"}'

Note: Service calls require human approval via ClawBridge UI.

Quick Script

./skills/home-assistant/scripts/ha-control.sh state light.office
./skills/home-assistant/scripts/ha-control.sh on light.office
./skills/home-assistant/scripts/ha-control.sh off light.office

Notification Formats

| Domain | Message | |--------|---------| | light | 💡 {name} turned on/off | | switch | 🔌 {name} turned on/off | | binary_sensor (door) | 🚪 {name} opened/closed | | binary_sensor (motion) | 📡 {name} motion detected | | person | 👤 {name} is now {state} | | lock | 🔒 {name} locked/unlocked | | other | 🔔 {name} old → new |

Scripts

| Script | Purpose | |--------|---------| | ha-discord.py | Primary — WebSocket → Discord direct (zero cost) | | ha-monitor.py | WebSocket → file (for cron-based delivery) | | ha-control.sh | Quick CLI for on/off/state |

API Reference

See references/clawbridge-api.md

File v1.0.0:_meta.json

{ "ownerId": "kn7914ekxf0n1eb58r1nx410dx80y7hr", "slug": "home-assistant-clawbradge", "version": "1.0.0", "publishedAt": 1770921220052 }