Cover Control Automation (CCA) - Intelligent Automation for Blinds, Awnings & Shutters | Calendar, Sun Shading, Force Functions

i played a little bit with the values, and i figured out with the configured day in march, the elevation values are high in summer and low in winter so in winter, when its gets dark early the cover will stay open longer and in summer, when it get dark later the day the cover will close earlier the day, because the values are higher! If i change the canfigured starting day to september the values in summer are low, and in winter they are high so both are nearby the real light! Was there a specific reason to use the day in march as reference?

1 Like

Good evening, I’d like to point out a problem that I’ve been detecting since I updated to the December version. It turns out that in the August 15 version, if I opened the window with the shutter down, it would be positioned in the ventilation position and if I manually raised the shutter to 100%, I could close and nothing happened. Now it happens that if I close the window, the shutter closes.
If I have the window open and the shutter closes because it’s time to close, example is night, if I close the window, the shutter will open again at 100%.
I don’t know if I made the idea.

PS: the text was written with Google Translate

Thank you Herr. I think the effect came from the bug fixed in today’s version 31/12. Ventilation now works well again. Now I have to check the new intros for dynamic opening. Happy New Year.

1 Like

Happy New Year, everyone!

I have a problem where my window closes from the ventilation position to fully open. According to the configuration, I think it should close, as the brightness is not yet right.

Furthermore, I don’t know what the trace from 4:30 a.m. (TUC+1) means?

Thank you.

For some reason, the traces are not downloaded completely in Firefox. Safari crashes when I try to download them. I downloaded them again with the Android CompanionApp.

Hi all!

I’ve been playing happily with this blueprint for a while and I have a bit of a challenge :slight_smile:

I use a condition to open the covers in the morning, the condition is that there is motion detected in the living room to open the covers.

So it works wonder during the work days because I wake up early and therefore motion is detected on the opening time.

However, let’s say that no motion is detected by the early open time, then when movement is detected nothing happens because it is a condition.

Is there any way around that other than creating another automation?

Hi there,

first of all, thank you. You created a great blueprint that I am using for some time now with excellent results.

Before that I was using some rather dump automation which triggered at a certain time which was defined in an entity. But for those times it is colder outside I had a boolean. When this boolean was true, the shutters closed only to a certain position to keep them from the windowsill, to prevent freezing.
Is something similar possible with the blueprint? I would like to define two levels of closing and have an entity decide which level to use. (I hope that was understandable gibberish).

Thanks in advance.

As far as I understand your setup I think it is similar to a window sensor. If you don’t use the ventilation position currently, you could use that entity to trigger partial ventilation. If it is off it will go to closed as normal.

Hi in the actual version (2026.01.02) is a bug with timebased closing with sun elevation. The closing time is set from 22:20 to 22:35 so the cover schould close latest at 22:35. In addition i set the closing sun elevation to -53. This value was reached at 22:51! With this elevation the cover was closed at 22:51 and not at 22:35! I have only 2 traces, one from 22:20 and one from 22:51 when the cover closed! Download trace automation.rollo_kueche_v_weihnachten 2026-01-07T21_20_00.411560+00_00.json | LimeWire

Hello, since the update to the version with the major changes, I’ve been having the following problem: The roller shutters are open, I open the door, and after closing it, the roller shutter moves to the closed position.

Example: The roller shutters were opened at 5:30 AM by an alarm automation. The helper variable for Wo_Links is still set to “close” and hasn’t been set to “open,” which is why the roller shutter moves to the closed position after the door closes. My question is, why was the helper variable set to “open” when the roller shutters were opened? Is this a bug?

The automation failed to execute at 5:30 a.m. when the roller shutters were raised.

i have a similar problem. Opening the cover manualy. After few minutes i open the door and 8 minutes later i closed the door. Than the cover closes, but it should stay open, because the reset time for manual override is set to 120 minutes!

Today the same.

Could it be that manual override didn’t change the status-helper. On both days i opened the cover manualy and the status of the cover didn’t change to manual = 1!

1 Like

Hello, same Here. Since update, roller shutter closing after Manual opening and Status helper Not updating Manual.

Chris

I can confirm that. I even have the problem myself. I’ll take a look at it. It probably came about when I enabled external position attributes or sensors.

1 Like

:rocket: CCA 2026.01.11 - Manual Position Trigger Fix

  • Fixed manual position detection trigger (#326): Replaced non-functional template trigger with separate state triggers for each position source (current_position, position, custom sensor). Manual position changes are now reliably detected within 60 seconds

See all changes from the last few weeks here:

To keep the code leaner, I removed a lot of information from the blueprint. For example, there are no longer any “Latest Changes” directly in the automation.

1 Like

i tested the new version and i got an error " Error in describing trigger: can’t access property “includes”, t is undefined". The status helper didn’t change! The trace is here

Oh, thanks for pointing that out. The logic was indeed inverted. I have updated the documentation and also added a few graphics for better visualization.

DYNAMIC_SUN_ELEVATION

—-

  1. Why March as a Reference?
    March 21st (Day 80.75) is almost universally used in astronomy and physics as the reference point for solar calculations because it marks the Spring Equinox (Vernal Equinox).
    Mathematically, this is the “cleanest” starting point for several reasons:
  • Zero Crossing: At the equinox, the sun crosses the celestial equator. In a sine wave, this corresponds to the point where the value is exactly 0.
  • Perfect Balance: It represents the exact midpoint between the two extremes—the Summer Solstice (maximum) and the Winter Solstice (minimum).
  • Symmetry: Using the equinox as the anchor ensures that the interpolation remains symmetrical throughout the year, providing the most accurate physical model of the Earth’s axial tilt.
1 Like

We’ve had this issue here quite a few times recently. It’s not a bug in the blueprint, but a display error in the Ha Trace Viewer. This is probably due to the legacy trigger notation.

But the bug should be fixed. It works great for me. Are you sure you didn’t update too early, i.e., before my post? I had made a fix shortly before the post. But the version number had already been incremented.

yep i updated befor your post, directly after your comment at github :smiling_face: I will update again and test it tomorrow :slight_smile:

Hi there,
I just came over this awesome blueprint! First of all big thanks.

I’m looking for a way to dynamically customize the position value of the covers. I would like to close the covers completely when the temperature is below 10° and go for 70% closed when the temperature is above 10°. Is there any solution for this? Did i miss anything?

Big thanks in advance.

1 Like

If you don’t need the ventilation position you could “mis-use” it. I do something similiar with my roof top windows and freeze protection. I created a binary sensor to track freezing and if it goes on, the rooftop windows go into ventilation position instead of completely closing.

1 Like

The status_helper changes the manual part now. But is it normal that the open state wouldn’t be set to 1 if i open the cover?
Example: manual open:
open = 0 → open = 0
close = 1 → close = 0
manual = 0 → manual = 1

I tested it with manual closing and here all status values are correct:

open = 1 → open = 0
close = 0 → close = 1
manual = 0 → manual = 1

Mhhh…very curious:
If i open the manual closed cover manual than the status helper is set correctly, i think!

open = 0 → open =1
close = 1 → close = 0
manual = 1 → manual = 0 ← is this 0 correct?