Cover Control Automation is a comprehensive Home Assistant blueprint that automatically manages window coverings (roller shutters, blinds, awnings) based on time, sun position, weather conditions, and your preferences. It largely eliminates the need for manual adjustments.
Why CCA?
Most comprehensive cover automation blueprint available
Your automation YAML configuration (exported instance).
The exported trace (especially of failed runs).
Expected behavior vs Actual result.
Tip: Please do not summarize so many independent problems in one post. It makes support easier for me if we could focus on one possible error per post.
How to Use Traces Effectively
Traces allow you to inspect exactly what happened when an automation was run.
Increase Stored Traces (Optional)
To store more traces, add this to the automation YAML:
Use the arrow symbols to switch back and forth between the traces and search for the trigger (see trigger table) that should actually trigger something.
Please note that traces for the trigger “t_manual_x” are not relevant for debugging. Traces are only required in very rare cases. Then I would also point this out. These triggers are reactions to manual position changes or the attempt to recognize previous actions from the blueprint. If there are problems, then rarely with this trigger, but with the trigger directly before it.
Download the trace and make the file available in the thread via filehosters such as Pastebin.
Uploading the JSON File
Since the forum does not support uploading .json files directly, please use one of the following services to host your file and share the link in your post:
Copy the generated link and include it in your forum reply.
By providing the trace in this format, it’s much easier to identify bugs, unexpected behavior, or misconfigurations in your automation setup. Thank you!
Summary
Set up the CCA blueprint carefully with correct values and entity references.
Do not trigger it manually.
Keep the blueprint up to date.
Use Traces to debug and provide structured support requests.
The Cover Status Helper is the central control element in the latest version of the Cover Control Automation (CCA). It tracks the current state of the roller blinds.
Structure and Meaning of the Individual States
Each of these states is an object with at least two key values:
State
Description
a (active)
t (timestamp)
open
Cover is open or was last opened
0 / 1
Time the open occurred
close
Cover is closed or was last closed
0 / 1
Time the close occurred
shading
Cover is in shading mode
0 / 1
Time shading activated
shading.p
Shading detected, not yet started (Pending)
0 / 1
End of the waiting time (for trigger)
shading.q
End of shading detected, not yet started (Pending)
0 / 1
Time executed
vpart
Partly open for ventilation (window tilted)
0 / 1
Time activated
vfull
Fully open for maximum ventilation (lock-out protection)
0 / 1
Time intervention
manual
Manual operation detected (UI, switch, etc.)
0 / 1
Time intervention
v
Version of the status format
–
–
t
Timestamp of last global status change
–
Unix time
Cover Status Helper - State Overview
This table provides an overview of the different states used in the Cover Status Helper for Home Assistant Blueprints. Each row represents a specific scenario with corresponding binary values for each state variable.
Scenario Description
open
close
shading
vpart
vfull
Cover is open
1
0
0
0
0
Cover is closed
0
1
0
0
0
Shading active, then returns to open
1
0
1
0
0
Cover is still closed, then moves to shading instead of fully opening
0
1
1
0
0
Lockout protection active when closing
0
1
0
0
1
Window tilted – no lockout, cover moves to ventilation position instead of closing
Happy Release Day
Thanks again for all the work you put in.As a shift worker, I am very happy about the resident mode. But what I’m missing is an additional block that doesn’t open the blinds, for example during school holidays or weekends.
But you should be able to achive this by using the resident mode, shouldn’t you?
As it’s an input_boolean is just for this, you can create an automation and define however you want.
Or am I missing your point?
You’re right about resident mode. But I only have one presence detector in the bedroom and if it doesn’t recognize me or my wife, the shutters open. It is easier not to open the shutters on certain days. @Herr.Vorragend gave me the tip about the Additional Conditions For Opening The Cover and I’m going to test that now
I see. But still I would prefer to use this with resident mode. Create a new input_boolean and set to true on all days you don’t want the shutters to open.
Guess it’s easier than dealing with additional conditions.
I just started to use this blueprint but luck is not yet on my side.
in my application i want to use the blueprint just for shading in combination with screens i have installed in my home.
Regardless of what i try i cannot make this blueprint control my screens for shading alone.
I made sure to:
Configure a cover to control
selected the shading option (6) as only enabled option)
under the shading option i’ve set the:
start and end azimuth (65/220)
the start and end elevation (6/90)
i’ve set 0% as the setting to close the screen for shading (this is when my screens are fully closed)
i’m using the default weather forecast conditions and made sure the forecast entity exists
triggering the automation manually or wait for sun elevation and azimuth to become true, no dice.
Must be something obvious i am doing wrong but i cannot seem to find out what.
Btw: “fährt nach Sonnenauf- /untergangszeiten, aber nur innerhalb des Fensters (7-9 Uhr)” ist not completely right. It’s opening between 7-9 but closing 17-22.
Cover Control Automation (CCA)
Resources: GitHub Project | FAQ & Troubleshooting | Full Changelog | CCA Configuration Validator | CCA Trace Compare | CCA Trace Analyzer | Report Issues
PayPal Donation | 
What is CCA?
Why CCA?
Most comprehensive cover automation blueprint available
Key Features
Time & Schedule Control
Advanced Sun Shading
Cover Type Support
Ventilation Management
Manual Override Intelligence
Smart State Memory & Force Return
Extensive Customization
Configuration Validator
Documentation
Frequently Asked Questions: FAQ
Screenshots
]
if you find it helpful. Thank you!
Reply in this thread for community support
Report bugs on GitHub
Troubleshooting Questions
Tips for Creating Helpful Support Requests
Your automation YAML configuration (exported instance).
The exported trace (especially of failed runs).
Actual result.
How to Use Traces Effectively
Pastebin Example
Trigger overview
Cover Status Helper - Contents
