There is definitely something wrong with your helper.
CCA cannot read the content and therefore cannot determine the length.
Have you already waited for the next trigger after emptying the helper? If so, the helper should be refilled.
Please do not execute the automation manually. It only works with a trigger.
Not yet. Iâll give this a shot tomorrow. Thank you for the quick replies and great blueprint!
Hi. Thank you for your feedback.
Hereâs the tracefile from this morning
https://www.dropbox.com/s/gatfwr9fta538r9/trace%20automation.rolldaden_fenster_wohnzimmer%202025-03-07T05_35_00.389270%2B00_00.json?dl=0
Just a quick one before I go to work:
Do you still have a trace from 06:30?
The helper tells me that the roller blind was already open at this time today.
Hi,
thanks for your fast reply.
Unfortunately, I only have a trace from 6:35âŚ
Thanks for the hint to the status helper.
I think I made a mistake.
Iâm using your blueprint for three covers in total.
But I was using the same status helper on two different covers by mistake.
I have generated a new status helper for the cover in quesiton.
So letâs see if that helped.
Thank you again. 
Irrespective of this, your values for opening the blinds have not yet been reached.
The Sun Elevation was still at -4.5.
And the latest opening time had not yet been reached either.
So everything is actually correct.
I only read your whole answer after my last post.
Then we have the solution.
Dear Community
I would like to configure/enable automatic sun protection / sunshade control.
As this seems fairly the most complicated part in CCA (at least for me) could you please post some examples and hints how you have done it? What is absolutely essential and what is nice to have. Preferable I would like to see how you did it with Venetian blinds andHMIP actuators (HmIP-FBL)
Many Thanks in advance.
Thanks for this blueprint - really neat solution but I have one question - how does Sun Shading works?
Thank you so much. I couldnât figure out for months why I couldnât set the max length in the helper.
@Herr.Vorragend
You should consider adding this important information as a prerequisite to the Cover Status Helper information where it currently says " Attention: You will need to manually create a input_text entity with a length of 254 chars for this." It would help other users like @Freacly and me to create the helper as needed. Thanks! 
What do you mean exactly? As a prerequisite? Should I query this technically? Because itâs already in the text.
Many parameters for shading also execute a trigger. The blueprint then checks whether all conditions (regardless of the trigger) are valid.
Important information for numerical triggers in HA:
Once the threshold is exceeded, it is no longer triggered. Itâs already in the blueprint somewhere else. Iâll make it more present at some point.
So: It is only triggered when the value exceeds or falls below the threshold. After that, you have to wait for other triggers.
Start with the mandatory fields first.
On the other hand: What sensors do you have? Everyone has it configured differently because there are also different requirements.
Thanks for your answer. I have the following sensors:
Another question is, how do I configure shading when using âHomematic(IP) Local âSet cover combined positionââ in Additional Actions 
I mean you have to activate the advanced mode in your general user settings as mentioned here, before you are able set the max. length as shown here. Otherwise it does not provide the option to configure the max. length in the helper.
Itâs an important prerequisite that probably other users than @Freacly and me wonât know of.
Hope that makes it clearer to you. Thanks again!
Hello
I have a problem where the cover wonât close after venting. Hereâs my configuration.
alias: Cover Control Automation (CCA)
description: ââ
use_blueprint:
path: hvorragend/cover_control_automation.yaml
input:
blind: cover.rollladen_buro_rolladen_buro
auto_options:
- auto_down_enabled
- auto_brightness_enabled
- auto_sun_enabled
- auto_ventilate_enabled
- auto_up_enabled
cover_status_options: cover_helper_enabled
time_up_early_non_workday: â07:00:00â
time_up_late_non_workday: â08:30:00â
time_up_late: â07:30:00â
time_down_early: â16:30:00â
time_down_early_non_workday: â16:00:00â
workday_sensor: binary_sensor.workday_sensor
check_config: true
default_brightness_sensor: sensor.dammerung_kombinationssensor
brightness_down: 12
brightness_up: 10
contact_window_tilted: binary_sensor.fenstergriff_buro_gekippt
contact_window_opened: binary_sensor.fenstergriff_buro_offen
auto_ventilate_options:
- ventilation_delay_enabled
- ventilation_if_lower_enabled
- ventilation_after_shading_end
shading_brightness_sensor: sensor.hmip_slo_000d60c9a67869_beleuchtungsstarke
shading_sun_brightness_end: 9974
shading_sun_brightness_start: 13000
shading_temperatur_sensor1: sensor.wandthermostat_ez_hmip_wandthermostat_ez_temperatur
shading_elevation_min: 25
shading_min_temperatur1: 22
shading_temperatur_sensor2: sensor.wetterstation_garten_temperatur
shading_min_temperatur2: 25
shading_forecast_sensor: weather.forecast_home
drive_delay_fix: 3
drive_delay_random: 8
auto_shading_end_condition:
- condition: state
entity_id: binary_sensor.raspberrymatic_sv_beschattung_auto
state: âoffâ
ventilate_position: 30
ventilate_tilt_position: 30
lockout_tilted_options:
open_tilt_position: 100
close_tilt_position: 0
shading_position: 50
cover_status_helper: input_text.h_rollladenstatus_buro
ignore_after_manual_config:
- ignore_ventilation_after_manual
- ignore_closing_after_manual
individual_config:
drive_time: 143
Other way around: the blind opens and then doesnât close again until the end of the day.
Where it actually needs to stay closed (well shaded) until the sun has moved off the window at azimuth >= 101 or elevation >= 57, or something like that.
I canât find a trace that seems to trigger the shading, there is one run just after midnight with an ID of t_shading_reset, then the next call is the 6am âEarly On Workdaysâ, followed by the 8am âLate On Workdaysâ and at that point the blind is opened. The next thing that happens is the ât_shading_end_pending_5â when the sun hits the end point.
The best I can do is the 8am âLate On Workdaysâ trace. That seems to check for shading, decides that we arenât and then triggers the open: trace automation.curtains_person1_s_curtains 2025-03-12T19_00_00.138744+00_00.json - Google Drive
@Herr.Vorragend would say, please send me a trace 
Its a wild guess, your window contact sensor is a 3 way sensor? if yes, have you seen this?
It must be a binary two-way contact sensor. If a three-way sensor is available, it must be converted to a binary two-way sensor using a [template sensor](https://www.home-assistant.io/integrations/template/). See also the [following posts](https://community.home-assistant.io/t/cover-control-automation-cca-a-comprehensive-and-highly-configurable-roller-blind-blueprint/680539/593) in the forum.
**Important note:** Please do not enter the same sensor in both fields for the contact sensors. This does not work and leads to strange situations.
If iâm using the Force Down feature, how can I return back to normal operation. I donât want necessarily to return to the previous value but to a freshly calculated state.
What would be the best way to achieve this?
Alternatively I thought about using Manual Override instead of Force Down to achieve the same. Is there a way to trigger Manual Override reset from outside the automation?
I read and searched quite a bit through this huge thread, but didnât find an answer to my question. Sorry if it has been discussed before.
Hi all, maybe one can help
I have 3 roller blinds and it works perfect for months.
Now 1 Rollerblind goes up and down as expected.
The both others go only down in the evening but not up in the morning,
Deletion of scripts and new creation doesnât help.
Also a copy of the working one and change of the entities brings no solution.
No one an idea?