← Back to Skills Marketplace
814
Downloads
0
Stars
2
Active Installs
1
Versions
Install in OpenClaw
/install glitch-homeassistant
Description
Control and monitor Home Assistant smart devices using commands for lights, switches, covers, climate, scenes, and scripts via the HA API.
README (SKILL.md)
Home Assistant Skill
Control smart home devices via Home Assistant API.
Skill Metadata
- Name: homeassistant
- Type: OpenClaw Skill
- Purpose: Control lights, switches, covers, climate, scenes, scripts via HA API
Setup Commands
Prerequisites
- Home Assistant running on local network
- Long-Lived Access Token from HA Profile page
Configuration (One-Command)
# Run this to configure
ha-cli setup \x3CHA_URL> \x3CTOKEN>
# Example:
ha-cli setup 192.168.1.100 your_long_lived_token_here
Or set environment variables:
export HA_URL="http://homeassistant.local:8123"
export HA_TOKEN="your_token_here"
Usage Commands
Basic Control
# Turn on device (any type)
ha-cli on \x3Cdevice_name>
ha-cli \x3Cdevice_name> on
# Turn off device
ha-cli off \x3Cdevice_name>
ha-cli \x3Cdevice_name> off
Brightness & Color
# Set brightness (0-100)
ha-cli brightness \x3C0-100> \x3Cdevice_name>
ha-cli \x3Cdevice_name> brightness 75
# Set RGB color
ha-cli rgb #RRGGBB \x3Cdevice_name>
ha-cli rgb #FF5500 "Living Room"
Temperature
# Set temperature
ha-cli \x3Ctemperature> \x3Cthermostat_name>
ha-cli 22 thermostat
Scenes & Scripts
# Activate scene
ha-cli scene \x3Cscene_name>
ha-cli scene movie
# Run script
ha-cli script \x3Cscript_name>
ha-cli script morning
Status & Discovery
# Check HA status
ha-cli status
ha-cli info
# List all entities
ha-cli list
ha-cli list entities
# List by domain
ha-cli list light
ha-cli list switch
ha-cli list climate
Supported Device Types
| Domain | Commands | Examples |
|---|---|---|
| light | on, off, brightness, rgb | ha-cli on living room |
| switch | on, off | ha-cli off tv |
| cover | open, close, stop | ha-cli open blinds |
| climate | temperature, mode | ha-cli 22 thermostat |
| lock | lock, unlock | ha-cli lock front door |
| scene | activate | ha-cli scene movie |
| script | run | ha-cli script morning |
Entity Matching
- Case insensitive
- Partial name matching (bed → Bedroom Light)
- Fuzzy matching enabled
Error Handling
- Connection error: Shows HA URL and token setup instructions
- Entity not found: Shows similar entity suggestions
- Invalid command: Shows usage help
Related Skills
- openhue (Philips Hue)
- sonoscli (Sonos speakers)
- eightctl (Eight Sleep)
Files
homeassistant/
├── SKILL.md # This file
├── README.md # User documentation
├── ha-cli # Main CLI executable
├── ha # Bash wrapper
└── config.json # Saved configuration
Usage Guidance
This package is inconsistent: the docs instruct running a CLI (ha-cli) and storing a Home Assistant long‑lived token, but the actual bundle does not include the referenced executables or declare the env vars. Before installing or providing secrets, ask the publisher for the missing CLI or an install mechanism, verify the CLI binary comes from a trusted source (or inspect its source), and prefer using environment variables with limited-scope tokens. Treat the included config.json as potentially sensitive storage — set strict file permissions if you must use it. If unsure, use the official Home Assistant integrations or a well‑maintained client rather than this incomplete skill.
Capability Analysis
Type: OpenClaw Skill
Name: glitch-homeassistant
Version: 1.0.0
The skill's stated purpose of controlling Home Assistant is benign. However, the `SKILL.md` and `README.md` instruct the user to provide a Home Assistant Long-Lived Access Token, which is then explicitly stated to be stored in plain text within the `config.json` file. Storing a long-lived access token in an unencrypted, plain-text file represents a significant security vulnerability, as it makes the credential susceptible to compromise if the local system is breached. While there is no explicit evidence of malicious intent (e.g., exfiltration of the token) in the provided files, this insecure storage method constitutes a high-risk capability.
Capability Assessment
Purpose & Capability
The skill claims to control Home Assistant via a local CLI (ha-cli) and requires a HA URL and long‑lived token, but registry metadata lists no required env vars/credentials and no binaries. The declared package contents (README/SKILL.md) reference executables that are not actually present. That mismatch is disproportionate to the stated purpose.
Instruction Scope
Runtime instructions instruct the user/agent to run `ha-cli setup <HA_URL> <TOKEN>` or export HA_URL/HA_TOKEN and say credentials are saved to config.json. The instructions themselves are limited to HA operations (no unrelated file/system access), but they assume the presence of a CLI that is not included. The workflow also persists the token in plaintext config.json in the skill directory, which increases persistence of a sensitive secret.
Install Mechanism
There is no install specification (instruction-only), which is low risk by itself. However, SKILL.md/README enumerate binaries (ha-cli, ha) in the files list but those executables are not present in the bundle—an inconsistency that may indicate an incomplete package or mislabeling.
Credentials
The skill metadata declares no required environment variables or primary credential, yet the SKILL.md explicitly tells users to provide HA_URL and HA_TOKEN. That discrepancy is misleading: the skill will need those values to function, and the instructions advise storing the token in a plaintext config file. Requiring a long‑lived token is reasonable for Home Assistant control, but the package should declare that explicitly and document storage/permissions.
Persistence & Privilege
The skill does not request elevated platform privileges and is not always‑on. It does persist configuration (config.json) in the skill bundle directory per its docs; storing tokens there creates persistent local secrets but does not, in the package as provided, demonstrate unauthorized access to other skills or system settings.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install glitch-homeassistant - After installation, invoke the skill by name or use
/glitch-homeassistant - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
Initial release of glitch-homeassistant – Control Home Assistant from the command line.
- Supports controlling lights, switches, covers, climate, locks, scenes, and scripts via Home Assistant API
- Simple setup using one command or environment variables
- Flexible commands for on/off, brightness, color, temperature, scenes, scripts, and more
- Entity matching is case-insensitive, supports partial and fuzzy matches
- Helpful error messages for connection issues, missing entities, or invalid commands
- Includes `ha-cli` for all interactions and detailed usage examples
Metadata
Frequently Asked Questions
What is Homeassistant?
Control and monitor Home Assistant smart devices using commands for lights, switches, covers, climate, scenes, and scripts via the HA API. It is an AI Agent Skill for Claude Code / OpenClaw, with 814 downloads so far.
How do I install Homeassistant?
Run "/install glitch-homeassistant" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is Homeassistant free?
Yes, Homeassistant is completely free (open-source). You can download, install and use it at no cost.
Which platforms does Homeassistant support?
Homeassistant is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created Homeassistant?
It is built and maintained by Glitch (@chris6970barbarian-hue); the current version is v1.0.0.
More Skills