moltbot-ha_skill

This skill helps you control Home Assistant devices, lights, scenes, and automations via the moltbot-ha CLI with configurable safety confirmations.
  • Python

2.5k

GitHub Stars

5

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill openclaw/skills --skill moltbot-ha

  • _meta.json296 B
  • CHANGELOG.md2.0 KB
  • config.example.toml1.6 KB
  • README.md9.5 KB
  • SKILL.md7.2 KB

Overview

This skill controls Home Assistant smart home devices using the moltbot-ha CLI. It provides discovery, state inspection, and action commands for lights, switches, covers, scenes, and automations with a configurable safety confirmation system. It is designed for scripted and agent-driven workflows with optional JSON output for integrations.

How this skill works

moltbot-ha talks to Home Assistant via its REST API using a long-lived access token (recommended stored in an environment variable). The CLI can list entities, read states, call services, and set entity attributes. A three-level safety system blocks or requires confirmation for critical actions and logs every write to an actions log for auditability.

When to use it

  • Discover devices and check sensor states before automations or reports
  • Turn devices on/off, set brightness, color temperature, or thermostat setpoints
  • Trigger scenes, automations, scripts, or custom service calls from scripts or agents
  • Control covers, locks, and alarms while enforcing safety confirmations
  • Integrate Home Assistant control into task runners, bots, or CI workflows

Best practices

  • Store the Home Assistant token in an environment variable (HA_TOKEN) rather than config files
  • Keep safety level at 3 for production to force confirmation on critical domains
  • Use allowed_entities or blocked_entities to limit automated access and reduce risk
  • Always present the user with the exact critical action and wait for explicit approval before retrying with --force
  • Use --json output for programmatic parsing and logging of results

Example use cases

  • Morning routine: turn on bedroom light, open blinds, set thermostat
  • Night mode: power off lights, activate goodnight scene, close all blinds
  • Agent-driven query: list lights and report available entities to a user
  • Safe critical action flow: ask user to confirm before opening a garage cover
  • Automation testing: call services or scripts with JSON payloads from CI

FAQ

Create a long-lived access token in your Home Assistant profile and set it as HA_TOKEN in your environment before using moltbot-ha.

What happens when a critical action is attempted?

The CLI returns a CriticalActionError and the agent must show the action to the user and request explicit confirmation before retrying with --force.

Can entities be permanently blocked?

Yes. Add entity IDs to blocked_entities in the config file. Blocked entities cannot be controlled even with --force.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational