home-assistant

Author and validate Home Assistant automation YAML with local scenario trace previews.

465|41|Updated Aug 4, 2026
One-click install
npx skills add https://github.com/autonomous-ai/openharness --skill home-assistant-autonomous-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: home-assistant
Source: https://github.com/autonomous-ai/openharness/tree/main/store/agents/home-assistant/skills/home-assistant
Command: npx skills add https://github.com/autonomous-ai/openharness --skill home-assistant-autonomous-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires yaml, and includes scripts (resource) components.

What problem does it solve? Writing Home Assistant automations by hand is error-prone: duplicate keys, missing IDs, malformed triggers, and unsupported semantics often surface only after deployment. This Skill validates automation YAML locally and previews how automations would behave under simulated events, without touching a live Home Assistant instance. ## Core Features & Use Cases - YAML Validation: Parses automations.yaml with strict YAML 1.2 rules, rejecting duplicate keys, unresolved tags, missing unique IDs, and malformed trigger/condition/action structures. - Local Scenario Simulation: Builds an interactive dashboard.html where you can edit entity states and events to trace whether an automation would fire, be blocked, or fall outside the modeled subset. - Honest Limit Reporting: Distinguishes local checks from real Home Assistant runtime validation and explicitly reports unsupported semantics (templates, durations, blueprints) instead of silently rewriting them. - Use Case: Draft a motion-activated lighting automation, run the builder to catch structural errors, then preview night vs. day scenarios in the dashboard before deploying to your live Home Assistant configuration. ## Quick Start Ask the assistant to validate the automations.yaml in this workspace and build the local preview dashboard so you can trace each automation's triggers and conditions.

Frequently Asked Questions about home-assistant

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I validate Home Assistant automations.yaml locally?

Run the build-automations.sh script, which parses automations.yaml with strict YAML 1.2 rules, checks for duplicate keys, unique IDs, aliases, and valid trigger/condition/action shapes, then writes a verdict and generates a dashboard.html preview.

How to test Home Assistant automation triggers without devices?

Use the generated dashboard.html scenario lab to edit event entities, previous and new states, and entity conditions, then run a local trace. It shows whether triggers match, conditions pass, and which actions would be requested, without calling any services.

Does this local checker support Home Assistant blueprints and templates?

No. The local model covers only simple state, numeric_state, and time triggers plus state and numeric_state conditions. Templates, durations, blueprints, and complex actions return 'not modeled' and must be validated in a real Home Assistant instance.

Why does my numeric_state trigger not fire in the preview?

Numeric triggers fire only on threshold crossing, meaning the value must move from outside the above/below range to inside it. An already-high sensor value does not trigger the automation, matching Home Assistant's crossing semantics.

Can this tool control my Home Assistant devices automatically?

No. The helper never contacts a Home Assistant instance or invokes services. It performs local YAML checks and scenario previews only; deployment requires using your real installation's configuration checks and automation traces.