That is definitely too much.
I’m already thinking about how I can rework this in the future. I want to make it a bit more flexible. I would like to offer different templates for cover actions that can then be changed as desired.
But the biggest problem is support. The additional code is not shown in the trace. And that could be a really big problem.
If you like, please record your request as a ticket on GitHub. Then it won’t get lost.
I am unsure how the manual control override works.
I have a rooftop window with an cover in it. When the window opens and the cover is closed, the cover opens 100%. I would like the blueprint to close it back to the ventilation percentage after this (with a wait of 2 minutes). Should I enable or disable the manual control settings?
Hm, overlooking the setting this might be the ‘allow ventilation even if the cover is in a higher position’ and setting. I think I can fix something with the additional actions for this.
Is there a way to set the seasons for the time or do I simply have to create a new automation for every four-year period?
The background to this is that the earliest time in winter was 5 pm. But now in spring it’s too early. Now I have to adjust all the times manually again.
I hope you know what I mean …
If you work with the elevation of the sun, you won’t have the problem.
The function for ignoring manual intervention has nothing to do with ventilation or returning to a previous state.
CCA can be configured so that the blueprint does nothing further in the event of manual human intervention. The person wins with their decision.
This can be reset via a timeout or at a fixed time. This prevents the blueprint from failing permanently.
This feature does not exist directly in CCA.
You can try it out with this. But then switch to a function configured in CCA. The only problem is that the window contact is then still open. This could put CCA out of rhythm.
I’m working with both time an sun…
You want the roller shutter to be lowered when it gets dark, don’t you? Then the time window and the height of the sun are sufficient. That works all year round.
That’s also the reason why I didn’t use fixed times like sunset and so on.
1 Like
I’ve been using the automation for days now, and it works wonderfully. Thanks!
The only issue is that the ventilation seems a bit sluggish. It takes about 5 seconds for the automation to raise or lower the roller shutters once the door is opened or closed.
In delay mode, I have everything set to 0 seconds. What could be causing this?
Sorry! Im so stupid 
Thank you
For sure, that is why I took it out. It was really just to see what happened.
I have given it a couple more days to see what it does but, there is no change it still opens at 8am and stays open. I think I am missing something in how the config works.
Is it because I am using the Time and Shading, and the shading starts before the drive up happens?
I just reread the option descriptions and noticed that for the late up time it does say that the cover will open by that time even if the values haven’t been reached:
The latest time at which the cover should be opened. If the required brightness or sun-elevation value has NOT yet been reached by this time, the cover will still be opened. (NOTE : If a resident has been defined and the resident is still asleep, then the cover will NOT be opened.)
So I am guessing that is what is happening? Do I need to move the shading azimuth to be after that time or should I be turning off the time option?
How can I tell you that if I don’t know your config? Or please show me a trace of when the blinds should have been closed.
Hey, I keep getting the below two errors and I can’t figure out what is going on. I have the helper set as follows. Any help is appreciated.
Error #1:
Logger: homeassistant.components.input_text
Source: components/input_text/init.py:275
integration: Input text (documentation, issues)
First occurred: 9:41:44 PM (1 occurrences)
Last logged: 9:41:44 PM
Invalid value: {“open”:{“a”:0,“t”:0},“close”:{“a”:0,“t”:0},“shading”:{“a”:0,“t”:0,“p”:0,“q”:0},“vpart”:{“a”:0,“t”:0},“vfull”:{“a”:0,“t”:0},“manual”:{“a”:0,“t”:0},“v”:5,“t”:1741228905} (length range 0 - 100)
Error #2:
Logger: blueprints.hvorragend.cover_control_automation
Source: components/system_log/init.py:331
First occurred: 9:41:45 PM (1 occurrences)
Last logged: 9:41:45 PM
Cover Control Automation (CCA): Config issue: Shading, ventilation and lockout protection require a cover status helper to be configured - automation.cover_automation_sun_rm_l
Helper:
On the one hand, the error message looks as if the helper is only 100 characters long. But in the screenshot you show me something else.
You could remove the contents of the helper. This will be refilled.
Otherwise show me a trace. Then I might see more.
I haven’t changed the config from the link I sent in the first message so if you have a look at that trace, it’ll be the same.
As I said in the second message I’m not sure that I can supply a trace as the time I’d expect it to run to mark the start of the shading there is no trace.
Looking back at the “Important configuration notes” it does say:
shading_azimuth_startshould be lower thanshading_azimuth_end
Which, because of where I live, it’s not and can’t be. I have:
Sun Shading Azimuth Start Value = 101 ← this is just before 8am
Sun Shading Azimuth End Value = 12 ← this is about 2pm
Would this impact the shading?
We’re talking about the fact that the roller blind doesn’t open in the morning. Not at the latest time. And not about the elevation/height of the sun either.
This has nothing to do with sun azimuth. This is required for sun protection. Not for opening.
I am quite sure that there will be traces for this. Perhaps not when reaching the threshold values for the sun elevation, because the comparison operator is (maybe) the wrong way round. But it could still be.
But there are definitely traces at the configured time.
Thank you for this great blueprint.
I have an understanding problem on the sun elevation settings.
I want the covers to open on weekdays on -3° sun elevation (dusk) but not before 6:35 o’clock.
Here are my settings:
alias: Rolldaden Fenster Wohnzimmer Automatik
description: ""
use_blueprint:
path: hvorragend/cover_control_automation.yaml
input:
time_up_early: "06:35:00"
workday_sensor: binary_sensor.workday_sensor
blind: cover.rolladen_fenster_vorhang
auto_options:
- auto_up_enabled
- auto_down_enabled
- auto_sun_enabled
cover_status_options: cover_helper_enabled
drive_time: 60
sun_elevation_up: -3.5
sun_elevation_down: -6
time_down_early: "18:00:00"
time_down_early_non_workday: "19:00:00"
time_down_late: "20:30:00"
sun_time_duration: 10
time_up_early_non_workday: "07:30:00"
time_up_late: "07:30:00"
time_down_late_non_workday: "21:00:00"
default_sun_sensor: sun.sun
cover_status_helper: input_text.cover_status_helper
lockout_tilted_options: []
For some reason that doesn’t work. Even though the sun elevation value has past the -3° already, the windows cover is staying closed.
What have I done wrong?
Thanks for the reply. I cleared the helper, but same result. Here is the trace.
It all looks great. I can’t recognise anything straight away. Just show me a trace at the right time and I’ll see what the problem is.
But you didn’t run the automation manually, did you?
And you didn’t change the sun_elevation even though the value had already been exceeded?
Or in other words: Have you already waited a day?