cca-assistant

Diagnose Cover Control Automation blueprint logic from helper JSON and YAML.

157|30|Updated Dec 23, 2023
One-click install
npx skills add https://github.com/hvorragend/ha-blueprints --skill cca-assistant
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cca-assistant
Source: https://github.com/hvorragend/ha-blueprints/tree/main/.claude/skills/cca-assistant
Command: npx skills add https://github.com/hvorragend/ha-blueprints --skill cca-assistant

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you quickly understand, correct, and validate the complex decision logic inside the Cover Control Automation (CCA) blueprint when behavior doesn’t match your expectations.

Core Features & Use Cases

  • Clarifies the full helper JSON model: Keeps track of base state, shading marker vs pending phases, window state, force/manual overrides, and retry timestamps.
  • Explains the effective-state priority cascade: Determines the correct outcome (lock, open, ventilate, close, shading) from competing inputs in the right order.
  • Guides safe YAML/trace debugging: Helps you spot common failure modes (missing “already-in-state” guards, stale helper vs live sensors, incorrect pending handling, timestamp issues) and interpret trace analyzer output.
  • Use Case: When your CCA automation repeatedly triggers wrong branches or shading retries abort unexpectedly, the skill helps you pinpoint which invariant or guard is being violated and what the correct branch conditions should be.

Quick Start

Ask the cca-assistant skill to analyze your CCA YAML change and trace results, then tell you exactly which invariant, helper field, or priority rule caused the unexpected branch behavior.

Frequently Asked Questions about cca-assistant

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

FAQPage Schema
How does the Cover Control Automation effective_state priority cascade work in Home Assistant?

The Cover Control Automation effective_state priority cascade determines the correct outcome—lock, open, ventilate, close, or shading—from competing inputs by evaluating helper JSON state, pending phases, and window state in strict priority order.

Why does my CCA blueprint automation repeatedly trigger the wrong branches?

Wrong branch triggering in CCA blueprint automation usually stems from missing already-in-state guards, stale helper JSON state versus live sensors, or incorrect pending phase handling that violates automation invariants and timestamp guard behavior.

How do I debug CCA trace output when shading retries abort unexpectedly?

Debugging CCA trace output when shading retries abort requires interpreting trace analyzer data to pinpoint which invariant, helper field, or priority rule is violated, checking retry timestamps and mutually exclusive pending phases.

What causes incorrect pending phase handling in Home Assistant cover control YAML?

Incorrect pending phase handling in cover control YAML happens when mutually exclusive pending phases overlap, base/window/override state separation is unclear, or trigger-variable limitations prevent proper helper JSON state updates.

Can I use cca-assistant to validate modifications to my CCA YAML logic?

Yes, cca-assistant validates modifications to CCA YAML logic by reasoning over helper JSON state and the effective_state priority cascade, ensuring technically consistent guidance on trigger branch selection and automation invariants.

What are common limitations when troubleshooting Cover Control Automation midnight reset logic?

Troubleshooting Cover Control Automation midnight reset logic faces limitations from timestamp guard behavior, trigger-variable constraints, and incorrect base/window/override separation that can cause unexpected branch selection or stale helper state.