homeassistant-assistControl Home Assistant smart home devices using the Assist (Conversation) API. Use this skill when the user wants to control smart home entities - lights, sw...
Install via ClawdBot CLI:
clawdbot install DevelopmentCats/homeassistant-assistControl smart home devices by passing natural language to Home Assistant's Assist (Conversation) API. Fire and forget — trust Assist to handle intent parsing, entity resolution, and execution.
Use this skill when the user wants to control or query any smart home device. If it's in Home Assistant, Assist can handle it.
Pass the user's request directly to Assist:
curl -s -X POST "$HASS_SERVER/api/conversation/process" \
-H "Authorization: Bearer $HASS_TOKEN" \
-H "Content-Type: application/json" \
-d '{"text": "USER REQUEST HERE", "language": "en"}'
Trust Assist. It handles:
Just relay what Assist says. The response.speech.plain.speech field contains the human-readable result.
"Turned on the light" → Success, tell the user"Sorry, I couldn't understand that" → Assist couldn't parse it"Sorry, there are multiple devices called X" → Ambiguous nameDon't over-interpret. If Assist says it worked, it worked. Trust the response.
Only if Assist returns an error (response_type: "error"), you can suggest HA-side improvements:
| Error | Suggestion |
|-------|------------|
| no_intent_match | "HA didn't recognize that command" |
| no_valid_targets | "Try checking the entity name in HA, or add an alias" |
| Multiple devices | "There may be duplicate names — consider adding unique aliases in HA" |
These are suggestions for improving HA config, not skill failures. The skill did its job — it passed the request to Assist.
Set environment variables in OpenClaw config:
{
"env": {
"HASS_SERVER": "https://your-homeassistant-url",
"HASS_TOKEN": "your-long-lived-access-token"
}
}
Generate a token: Home Assistant → Profile → Long-Lived Access Tokens → Create Token
POST /api/conversation/process
Note: Use /api/conversation/process, NOT /api/services/conversation/process.
{
"text": "turn on the kitchen lights",
"language": "en"
}
{
"response": {
"speech": {
"plain": {"speech": "Turned on the light"}
},
"response_type": "action_done",
"data": {
"success": [{"name": "Kitchen Light", "id": "light.kitchen"}],
"failed": []
}
}
}
Generated Mar 1, 2026
Homeowners can control lights, thermostats, and other devices via voice commands, such as 'turn off the bedroom lights' or 'set the thermostat to 72 degrees'. This enables hands-free operation, enhancing convenience and energy efficiency in daily routines.
Facility managers use the skill to adjust lighting, HVAC systems, and blinds across multiple rooms through natural language requests like 'dim the conference room lights' or 'open the office blinds'. It streamlines maintenance tasks and improves occupant comfort in commercial settings.
Caregivers or residents in assisted living facilities can control devices such as lights, fans, or media players with simple voice commands, like 'play relaxing music' or 'turn on the nightlight'. This supports accessibility and independence for individuals with mobility challenges.
Hotel guests can manage room amenities, such as adjusting lighting, temperature, or entertainment systems, by speaking commands like 'turn on the TV' or 'set the air conditioning to cool'. This enhances guest experience through personalized, automated control.
Store staff can optimize lighting and climate settings in different zones, using commands such as 'brighten the display area lights' or 'lower the temperature in the storage room'. This helps reduce operational costs and maintain a comfortable shopping environment.
Offer a monthly subscription that includes access to this skill along with premium support and advanced automation features. Revenue is generated through recurring fees from users who want reliable, hands-free control of their Home Assistant setups.
Provide paid consulting to businesses or individuals for setting up and customizing the skill with their Home Assistant environments. Revenue comes from one-time project fees or hourly rates for configuration, troubleshooting, and optimization services.
License the skill technology to smart device manufacturers, allowing them to embed it into their products for enhanced voice control capabilities. Revenue is generated through licensing fees per device sold or annual agreements with manufacturers.
💬 Integration Tip
Ensure HASS_SERVER and HASS_TOKEN environment variables are correctly set in OpenClaw config, and verify the endpoint uses /api/conversation/process to avoid common errors.
Control Sonos speakers (discover/status/play/volume/group).
Control Philips Hue lights/scenes via the OpenHue CLI.
Control Eight Sleep pods (status, temperature, alarms, schedules).
BluOS CLI (blu) for discovery, playback, grouping, and volume.
Control Home Assistant smart home devices, run automations, and receive webhook events. Use when controlling lights, switches, climate, scenes, scripts, or any HA entity. Supports bidirectional communication via REST API (outbound) and webhooks (inbound triggers from HA automations).
Use when integrating with Tesla's official Fleet API to read vehicle/energy device data or issue remote commands (e.g. start HVAC preconditioning, wake vehicle, charge controls). Covers onboarding (developer app registration, regions/base URLs), OAuth token flows (third-party + partner tokens, refresh rotation), required domain/public-key hosting, and using Tesla's official vehicle-command/tesla-http-proxy for signed vehicle commands.