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.