☀️ Cover Control Automation (CCA) - a comprehensive and highly configurable roller blind blueprint

Blueprints Exchange
, ,
1731

I don’t need just any trace. This is about the trigger t_shading_end_pending_3. In other words, the end of a possible shading.

I need the traces for the trigger that should actually be executing something.

1732

New Update

(includes some shading fixes)

2025.05.02-02:
  - Fixed: A bug has been fixed that caused the shading to be recognized but not executed. But only if shading was only allowed to be executed once a day.

2025.05.02-01:
  - Fixed: Also take into account for shading that a door contact only needs to be tested when ventilation mode is switched on #197
  - Fixed: Removed protocol error that occurs during manual execution.
  - Added: Catching an incorrect weather configuration
  - Added: Ability to specify an existing sensor if it already provides daily maximum temperature forecast instead of weather entity #199
  - Added: Add hysteresis for temperature sensor based shading #189
1733

I see. Maybe I didn’t get the “tracer” concept in its entirety, and maybe I have a too optimistic hope of what the blueprint should do.

What I’m hoping for is the following. The moment temperatures and brightness reach a certain level, and the azimuth is also reached, the shading should start.
If brightness goes down again, shading should stop.

Currently the shades don’t go down at all during the day, and they now just went down for sunset. I added that Tracer (i guess) and I also added the one after that.

https://drive.google.com/drive/folders/1liZvgu0JG0Aw3MkU12C2GTYADEaWrOQN?usp=sharing

1734

Please update the blueprint.
Perhaps this will solve your problem. There was a bug with the shading. See the post above yours.

1735

Hi Herr.Vorragend,

first of all thanks a lot for your really great work. Would it be possible to have an additional antifreeze option like the shading option where the blinds do not close in the evening completely (80%) depending on the state of an outside temperature sensor or depending on the forecasted temperature?

This would help that the blinds do not freeze at the bottom position and can be opened in the morning when it really gets cold…

Best Marcus

1736

There is something similar that can be used for individual requirements.

IMG_7137
IMG_71371179×1875 266 KB

1737

Dear Herr.Vorragend,

after fiddling around for days now, I can’t identify, why my shutters don’t go to in to sun shading mode. To avoid any errors, I just used azimut and elevation for this function.
I opened the shutters today at 8:30, at this time, the shutters already were inside in azimut/elevation area. But the shutters remained opened.

Thanks in advance for having a look into it.
https://pastebin.com/u06VCXeM

1738

You have uploaded a trace for the trigger “t_close_4” here. It does not refer to the shading. I need the traces for the trigger that should actually execute something.

1739

Thank you so much for taking care of the issue.
Today the sun shading function worked well, but compared to yesterday, the shutters were opened before the azimut/elevation trigger kicked in:
https://pastebin.com/0cdFpjxP

1740

We are already in the process of discussing the problem via other channels. The resident sensor seems to play a role here. If relevant, an answer will follow here in the thread.

1 Like
1741

New Update (yesterday)

Many thanks to jpawlowski for the valuable pull requests. :+1:

2025.05.04:

* Added: Allow immediate ending of shading if the sun is out of the defined azimuth or elevation range.
* Added: Option to close cover instead of opening when shading ends (ideal for awnings)
* Updated: Note that the weather sensor specification is optional #198

Important note

I have completely revised the first two posts, added an FAQ, described the triggers, explained the contents of the Cover Status Helper, listed typical errors and described the best way to create a support request with traces here in the thread.

It just happens that the same questions are asked again and again. I will collect these and add them above.
CCA is very complex due to its versatility and can almost only be supported with traces. I would like to spare myself the constant questions about missing information, because unfortunately you lose sight of the context. A problem that is divided into four posts makes it really difficult for me.

Maybe it will work this way. I am quite confident. Have fun.

1 Like
1742

New Update

2025.05.07:
  - Fixed: Shading is now also recognized and temporarily stored in the helper if the resident sensor contains the value true. #131
  - Added: Tilt Reposition Feature (Thanks for the pull request, Astado) #196
  - Update: Better textual clarification of what the result of the additional condition should look like #204
  - Update: Only shade the cover when it is not in the shading position. Purely as a precautionary measure in case the target state and actual state do not match.

Many thanks for your pull request, Astado. :+1:

1 Like
1743

is this the fix for

and

1744

Yes, exactly. I was aware of that too.
I was also in contact with michi1215. He had sent me detailed traces so that I could fix it. I just didn’t go into it again in the thread. I hadn’t thought about it.

1 Like
1745

Hallo, ich habe mit der neuen Version ein Problem:
Zu frühe Entschattung nach automatischer Beschattung

Ablauf

  • 10.05.2025 11:36:20 (UTC) – Automatische Beschattung durch Sonnenstand, Temperatur und Helligkeit (Trigger: shading start)
    • Rollladen fährt korrekt auf Position 25 % (shading)
  • 10.05.2025 11:37:50 (UTC) – Frühe Entschattung durch Helligkeits-Trigger (t_open_4)
    • Bedingung: >100 Lux für 90 Sekunden
    • Ursache: Sensor sensor.wetterstation_helligkeit_sud war kurz zuvor unavailable, kam zurück mit >30.000 Lux → Triggerkette wurde neu gestartet

Feststellung

  • Der Rollladen war zum Zeitpunkt des zweiten Triggers bereits korrekt beschattet
  • Es fehlt eine Blockierbedingung, z. B.:
    • prevent_opening_after_shading_end
    • oder Prüfung is_cover_helper_shaded == false
  • Dadurch konnte eine direkte Entschattung wenige Sekunden nach der Beschattung erfolgen

Ziel der Rückfrage

  • Ist dieses Verhalten beabsichtigt?
  • Wenn ja: Welche Option wird empfohlen, um diese Logik zu verhindern?

Ich habe mir jetzt erstmal einen Template-Sensor geschrieben, der unavailable mit dem letzten Wert wegpuffert. Hoffe, das klappt. Aber vlt. denke ich auch mal wieder falsch :smiley:

1746

User Crandler also reported this error to me a few days ago. This is a bug. Fix coming soon.

The problem actually only occurs if shading is carried out between Time Up Early and Time Up Late. The next open trigger in this area then opens again.

1747

Because I was also surprised that no one has had this in the last few months: Are you sure it’s because of the latest version? Or could it be that the bug is already half a year old?

1748

You should always do that anyway.
Any automation will have problems with numerical triggers if the sensor goes offline.

Tip: Use HA filter, lowpass, outlier or median.

1749

Dear @Herr.Vorragend , many thanks for your work on this, absolutely fantastic!

I am trying to do shading only for some screens, based on weather conditions (sunny) but I get the following error thrown:

TypeError: unsupported operand type(s) for -: 'NoneType' and 'int'

Error in 'choose[14]' evaluation: In 'or' (item 4 of 6): In 'and' (item 3 of 3): In 'template' condition: TypeError: unsupported operand type(s) for -: 'NoneType' and 'int'
Error in 'choose[14]' evaluation: In 'or' (item 5 of 6): In 'and' (item 4 of 4): In 'template' condition: TypeError: unsupported operand type(s) for -: 'NoneType' and 'int'

I think this is coming from the template condition that calculates if enough time has passed since the last manual override.
The template somehow received None for is_cover_helper_manual_ts

Info:

Config:

alias: "[SCREEN] Slaapkamer N & D auto"
description: ""
use_blueprint:
  path: hvorragend/cover_control_automation.yaml
  input:
    blind: cover.brewery_hm_drbl4_01_screen_slaapkamer_n_d
    auto_options:
      - auto_shading_enabled
    drive_time: 30
    default_brightness_sensor: sensor.brewery_hm_ps_02_keuken_presence_sensor_illumination
    time_control: time_control_disabled
    sun_elevation_down: 55
    sun_elevation_up: 6
    brightness_up: 0
    cover_status_options: cover_helper_enabled
    cover_status_helper: input_text.ih_screenslaapkamer_n_d
    open_position: 0
    close_position: 100
    shading_forecast_sensor: weather.forecast_thuis
    shading_forecast_type: weather_attributes
    shading_weather_conditions:
      - sunny
      - partlycloudy
      - clear
    shading_elevation_min: 6
    shading_azimuth_start: 70
    shading_azimuth_end: 145
    shading_position: 100
    is_shading_end_immediate_by_sun_position: true

this is the value of the helper:

{"open":{"a":1,"t":1746880710},"close":{"a":0,"t":1746880624},"shading":{"a":0,"t":0,"p":0,"q":0},"vpart":{"a":0,"t":0},"vfull":{"a":0,"t":0},"manual":{"a":1,"t":1746880710},"v":5,"t":1746880710}

Trace:

Am I doing something completely wrong or did I hit a blueprint error?

Thanks in advance!

1750

What kind of weather entity is „weather.forecast_thuis“?

You deliberately refrain from using the forecast and access your weather entity in „shading_forecast_sensor“.

Is this your own weather station?
Could it be that it has no attributes for the temperature? Can you show me the attributes?