Xpersona
H

Home Assistant Skill

CLAWHUB · Unverified

Inspect and control Home Assistant using REST and supported WebSocket workflows. Discover capabilities, action schemas, device/entity registries, Assist, automations, calendars, energy statistics and diagnostics. Use when the user asks to inspect, troubleshoot or operate an existing Home Assistant installation; not for general smart-home product advice or unrelated device questions. Skill: Home Assistant Skill Owner: anotb Summary: Inspect and control Home Assistant using REST and supported WebSocket workflows. Discover capabilities, action schemas, device/entity registries, Assist, automations, calendars, energy statistics and diagnostics. Use when the user asks to inspect, troubleshoot or operate an existing Home Assistant installation; not for general smart-home product advice or unrelated de

62
Rank
84
Safety
31k
Downloads

About

What it does, and when to use it.

Capability contract not published. No trust telemetry is available yet. 31K downloads reported by the source. Last updated 11/16/2026.

Avoid when

  • Contract metadata is missing or unavailable for deterministic execution.

Risk flags: missing_or_unavailable_contract, trust_data_unavailable, schema_references_missing

Install and run

Setup complexity: low.

clawhub skill install s17atnr1t0kk7477t45yeva22n8845aj:homeassistant-skill
  1. Setup complexity is classified as HIGH. You must provision dedicated cloud infrastructure or an isolated VM. Do not run this directly on your local workstation.
  2. Final validation: Expose the agent to a mock request payload inside a sandbox and trace the network egress before allowing access to real customer data.

Contract: missing

curl -s "https://www.xpersona.co/api/v1/agents/clawhub-anotb-homeassistant-skill-nt-skill-2/snapshot"

Run-check

$0.02 USD

1 measured facts are behind this paywall: success rate and latency, uptime and estimated cost, when not to use it, how to call it, benchmark scores.

Agents pay $0.02 in USDC. A card payment is $0.50, the smallest a card allows.

Documentation

CLAWHUB

143,051 characters of source documentation, loaded on request.

Extracted files

5 files captured from the source.

SKILL.md

---
name: homeassistant-skill
description: >
  Inspect and control Home Assistant using REST and supported WebSocket workflows.
  Discover capabilities, action schemas, device/entity registries, Assist, automations,
  calendars, energy statistics and diagnostics. Use when the user asks to inspect,
  troubleshoot or operate an existing Home Assistant installation; not for general
  smart-home product advice or unrelated device questions.
license: MIT
metadata: {"author": "anotb", "version": "2.2.0", "openclaw": {"requires": {"env": ["HA_URL", "HA_TOKEN"], "bins": ["curl", "jq"]}, "primaryEnv": "HA_TOKEN", "homepage": "https://github.com/anotb/homeassistant-skill"}, "compatibility": "Bash examples require curl and jq. REST reader requires Python 3.10+; optional WebSocket reader requires websockets>=15.0.1,<18. Network access to HA required."}
---

# Home Assistant Skill

Inspect Home Assistant capabilities and operate authorized smart-home actions.
Start with the installed version and exposed schemas rather than assuming every
integration or action is present.

## Choose the agent connection

For routine home queries and user-authorized control, prefer an already configured
native Home Assistant MCP connection when its discovered tools cover the task.
Use this skill's REST/WebSocket workflows for detailed schemas, registries,
history, diagnostics and configuration inspection outside those tools' scope.
Keep both available when useful; a replacement server or custom HA integration
is not required. See [connection selection and modern workflows](references/modern-workflows.md).
Do not enable MCP, authorize OAuth, broaden exposed APIs or expose HA publicly
as part of an inspection task. Each is separate setup requiring authorization.

## Setup

Set environment variables:
- `HA_URL` — Your Home Assistant URL (e.g., `http://10.0.0.10:8123`)
- `HA_TOKEN` — An existing access token supplied through the local environment or secret store.

Use HTTPS with verified certificates for remote connections; local HTTP exposes the
token to the network. Use the exact trusted origin, without a trailing `/api`, query
or embedded credentials. Do not print tokens, use shell tracing, save them in this
repository, or send them in chat. Do not create credentials or alter security
settings unless the user separately authorizes that setup.

A token carries its HA user's authority. Theft can expose household data and
allow device actions under that account. The readers' allowlists are local
guardrails, not server-side restrictions on the token. Use an existing account
with the access needed for the task; do not elevate it to make a query succeed.

### Read-only helper (optional)

With Python 3.10+ (no third-party packages), prefer the bundled helper for reads:

Python-only usage is standalone or on another skill host. OpenClaw still gates
this skill on both `curl` and `jq` and the two required environment variables.

```bash
python3 scripts/ha_read.py get /api/
python3 scripts

README.md

# Home Assistant Skill

An AI agent skill for inspecting Home Assistant capabilities and controlling authorized devices and automations. REST examples cover 25 entity domains; optional read-only WebSocket workflows add registries, Assist discovery, automation validation, energy statistics and repair diagnostics.

Works with [Claude Code](https://docs.anthropic.com/en/docs/claude-code), [OpenClaw](https://github.com/openclaw/openclaw), [Cursor](https://cursor.com), and any tool supporting the [SKILL.md](https://agentskills.io) standard.

[![ClawHub](https://img.shields.io/badge/ClawHub-homeassistant--skill-blue)](https://clawhub.ai/anotb/homeassistant-skill)
[![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](LICENSE)

Part of [unsol.dev](https://unsol.dev)

## Prerequisites

- Home Assistant instance with API access
- Bash, `curl` and `jq` for the shell examples, or Python 3.10+ for the optional read-only helper (standard library only)

OpenClaw readiness still requires both `curl` and `jq`, plus `HA_URL` and `HA_TOKEN`,
as declared in the skill metadata. Python alone runs the standalone read-only
helper but does not satisfy those OpenClaw dependency gates.

## Installation

### Claude Code

```bash
git clone https://github.com/anotb/homeassistant-skill.git ~/.claude/skills/homeassistant-skill
```

### OpenClaw (via ClawHub)

```bash
clawhub install homeassistant-skill
```

### Cursor / Other

Clone to your agent's skill directory.

## Configuration

1. Supply an existing Home Assistant access token through your local environment or secret store. Credential creation requires separate authorization.
2. Set environment variables:

```bash
export HA_URL=http://10.0.0.10:8123
export HA_TOKEN=your-long-lived-access-token
```

Use a trusted base origin without `/api`; the helper refuses credentials embedded
in URLs, redirects and malformed settings. Prefer verified HTTPS. Local HTTP sends
the token without encryption. Never paste tokens into chat, commit `.env` files,
enable shell tracing, or put tokens in command arguments.

The token inherits its HA user's permissions; its theft can expose household
data and allow device actions. Reader allowlists do not reduce the token's
server-side permissions. Use an existing account with suitable access and keep
presence, location, calendar and history results private unless sharing is
authorized. The Bash examples pass headers through stdin and require curl 7.55+.

The shell examples use Bash. On Windows the read-only helper works with `python`:

```powershell
# Set HA_URL and HA_TOKEN privately in this process before running.
python scripts/ha_read.py get /api/
python scripts/ha_read.py profile
python scripts/ha_read.py action-schema light.turn_on
python scripts/ha_read.py health
python scripts/ha_read.py get /api/services
python scripts/ha_read.py get /api/states/sensor.temperature
python scripts/ha_read.py calendar calendar.personal --days 7
python scripts/ha_read.py forecast weather.home -

_meta.json

{
  "ownerId": "kn78xwhkm2sq9ynm9gwzj712ps80vrjg",
  "slug": "homeassistant-skill",
  "version": "2.2.0",
  "publishedAt": 1791780752913
}

references/modern-workflows.md

# Capability discovery and modern Home Assistant workflows

Documentation/source review: 2026-10-12, against the 2026.10 release notes and
2026.10.1 Core command schemas. These are reference versions, not a claim about
the user's installation. Discover the installed version and capabilities first;
an integration can be absent or an account can lack access on an otherwise recent
installation. Never treat an unsupported query as an empty successful result.

## Choose the right interface

Prefer an existing native MCP connection for routine agent interaction when its
tools cover the request. This is an architectural recommendation: HA maintains
the server and tool schemas. Retain REST/WebSocket for deeper inspection; MCP
does not guarantee registry or recorder access. Current native MCP supports
OAuth with PKCE. Actual permissions depend on selected LLM APIs and account:
new installations can expose all LLM APIs and require admin by default. Do not
assume every MCP connection has the narrower built-in Assist scope. Discover
its configured tools before choosing a route. Avoid introducing a third-party
bridge unless the client genuinely requires one.

Cloud-hosted agents need a reachable HA endpoint; a local agent can use a trusted
LAN connection. Do not make a private instance internet-accessible for a test.
Connection setup is a separate user decision, not automatic skill installation.

| Need | Preferred interface | Important distinction |
| --- | --- | --- |
| Installed version, units, integrations, action names | `ha_read.py profile` | Omits coordinates, URLs, config paths and household name |
| One action's fields, selectors, targets, response declaration | `ha_read.py action-schema DOMAIN.ACTION` | GET discovery only; never calls the action |
| Current state or basic availability report | REST state read or `ha_read.py health` | Health lists unknown and unavailable separately; no full attributes |
| Disabled entities, device links, areas, floors, labels | WebSocket registry reads | State lists alone do not describe the registry |
| Automation/script inspection and snippet validation | WebSocket definition and validation reads | Definitions require admin; validation does not run actions |
| Assist agents, pipelines and supported languages | WebSocket Assist reads | Listing an agent does not establish its exposed entities |
| Existing Energy dashboard sources and recorder aggregates | WebSocket energy/statistics reads | Recorder statistics IDs are not always entity IDs |
| Existing repair issues | WebSocket repairs read | Do not dismiss, ignore or start a repair flow during diagnosis |
| Forecasts and calendar events | Existing REST helper commands | Forecasts return service data; all-day events use dates |
| Existing MCP connection for Assist context | MCP resource discovery | Prefer a declared read-only resource when available; do not change HA setup |

All Python commands below run from the skill folder with existing local
`HA_URL`/`HA_TOKEN` 

references/rest-examples.md

# Home Assistant REST examples

Read the setup, transport and safety requirements in `SKILL.md` first. These are
Bash examples requiring curl and jq; substitute verified entity IDs and parameters.
Headers arrive via stdin (`-H @-`); keep Bash tracing off. Curl 7.55+ is required.
Never run device actions as connectivity tests. The optional Python helper supports
read-only discovery, forecast and calendar queries on Windows, macOS and Linux.

## Switches

```bash
# Turn on
printf 'Authorization: Bearer %s\n' "$HA_TOKEN" | curl -q -fsS --noproxy '*' --connect-timeout 5 --max-time 30 -X POST "$HA_URL/api/services/switch/turn_on" \
  -H @- \
  -H "Content-Type: application/json" \
  -d '{"entity_id": "switch.office_lamp"}'

# Turn off
printf 'Authorization: Bearer %s\n' "$HA_TOKEN" | curl -q -fsS --noproxy '*' --connect-timeout 5 --max-time 30 -X POST "$HA_URL/api/services/switch/turn_off" \
  -H @- \
  -H "Content-Type: application/json" \
  -d '{"entity_id": "switch.office_lamp"}'

# Toggle
printf 'Authorization: Bearer %s\n' "$HA_TOKEN" | curl -q -fsS --noproxy '*' --connect-timeout 5 --max-time 30 -X POST "$HA_URL/api/services/switch/toggle" \
  -H @- \
  -H "Content-Type: application/json" \
  -d '{"entity_id": "switch.office_lamp"}'
```

## Lights

```bash
# Turn on with brightness
printf 'Authorization: Bearer %s\n' "$HA_TOKEN" | curl -q -fsS --noproxy '*' --connect-timeout 5 --max-time 30 -X POST "$HA_URL/api/services/light/turn_on" \
  -H @- \
  -H "Content-Type: application/json" \
  -d '{"entity_id": "light.living_room", "brightness_pct": 80}'

# Turn on with color (RGB)
printf 'Authorization: Bearer %s\n' "$HA_TOKEN" | curl -q -fsS --noproxy '*' --connect-timeout 5 --max-time 30 -X POST "$HA_URL/api/services/light/turn_on" \
  -H @- \
  -H "Content-Type: application/json" \
  -d '{"entity_id": "light.living_room", "rgb_color": [255, 150, 50]}'

# Turn on with color temperature (Kelvin; check supported_color_modes and min/max_color_temp_kelvin)
printf 'Authorization: Bearer %s\n' "$HA_TOKEN" | curl -q -fsS --noproxy '*' --connect-timeout 5 --max-time 30 -X POST "$HA_URL/api/services/light/turn_on" \
  -H @- \
  -H "Content-Type: application/json" \
  -d '{"entity_id": "light.living_room", "color_temp_kelvin": 3333}'

# Turn off
printf 'Authorization: Bearer %s\n' "$HA_TOKEN" | curl -q -fsS --noproxy '*' --connect-timeout 5 --max-time 30 -X POST "$HA_URL/api/services/light/turn_off" \
  -H @- \
  -H "Content-Type: application/json" \
  -d '{"entity_id": "light.living_room"}'
```

## Scenes

```bash
printf 'Authorization: Bearer %s\n' "$HA_TOKEN" | curl -q -fsS --noproxy '*' --connect-timeout 5 --max-time 30 -X POST "$HA_URL/api/services/scene/turn_on" \
  -H @- \
  -H "Content-Type: application/json" \
  -d '{"entity_id": "scene.movie_time"}'
```

## Scripts

```bash
# List all scripts
printf 'Authorization: Bearer %s\n' "$HA_TOKEN" | curl -q -fsS --noproxy '*' --connect-timeout 5 --max-time 30 "$HA_URL/api/states" -H @- \
  | jq -r '.[] | s

Sponsored

Ads related to Home Assistant Skill and adjacent AI workflows.