Could it be, that you forgot to define your sun sensor?
If you just want to use the azimuth/elevation of the sun, its not neccessary to enable the time based options for open and close! so try to disable them!
Hi, tanx for your answer!
I use the HA-includet sun-sensor (sun.sun) and i use a calender entity. That works without problems.
Or is there an another sun sensor i have to use?
no the included sun sensor should do the work 
Hi, I just noticed that there are a few similar issues on GitHub (#395, #398, #408ā¦)
If my traces and/or helper stats would be helpful for further analysis, please let me know.
For now, Iām waiting for the announced fixā¦
Since my English isnāt the best, unfortunately, and I have to read a lot of things twice to understand them, would it be easier for me if the whole thing were also available in German? Is it possible to translate the whole thing? Like a German version?
Also many thanks from my end. Very impressive!
Iāve automated some of the normal blinds and would like to extend my configurastion to velux roof windows with electrical motor and electrical blinds.
Here, it would be perfect to consider both, windows position and blind position (Blinds canāt be closed if window is fully open)
Iāve seen the bianry inputs to detect open / ventilating windows.But what I donāt understand: Is there any option to control the window position out of CCA?
There is one more constraint as the control unit (of the window) only allows to control window or blinds at the same time.
Consequently, a sequence might look like
- Sun Shading request detected ( e.g. based on #187)
- Move window to closed position
- wait until it is reached ( 1 Minute)
*Move blinds o shading position
Any experiences with such a setup?
The summer has arrived and my shading is not working anymore. Somehow east windows are working but south and west is not triggered. Trace analyzer shows temperature as and condition but they are configured as or.
This is the trace
And here is the config
alias: Rollo auĆen auto
description: ""
use_blueprint:
path: hvorragend/cover_control_automation.yaml
input:
blind: cover.rolladen_ausen
auto_options:
- auto_up_enabled
- auto_down_enabled
- auto_shading_enabled
- auto_ventilate_enabled
- auto_sun_enabled
ignore_after_manual_config: []
reset_override_config: reset_disabled
reset_override_time: "00:10:00"
cover_status_options: cover_helper_enabled
cover_status_helper: input_text.rolladen_aussen_helfer
drive_time: 25
ventilate_position: 20
shading_position: 25
time_up_early: "06:35:00"
time_up_early_non_workday: "08:00:00"
time_up_late_non_workday: "09:00:00"
sun_elevation_down: -3
sun_elevation_up: 9.8
contact_sensor: binary_sensor.kontakt_ausen
shading_azimuth_start: 120
shading_forecast_sensor: weather.ruesselsheim
shading_weather_conditions:
- sunny
- partlycloudy
- cloudy
- clear
- rainy
- exceptional
position_tolerance: 0
check_config: false
shading_forecast_type: weather_attributes
shading_min_temperatur1: 19
workday_sensor: binary_sensor.workday_sensor
shading_min_temperatur2: 19
shading_temperatur_sensor1: sensor.dwd_max_temp
contact_window_tilted: binary_sensor.kontakt_ausen
shading_conditions_start_and:
- cond_azimuth
- cond_elevation
- cond_forecast_weather
shading_conditions_start_or:
- cond_temp1
- cond_temp2
shading_conditions_end_or:
- cond_azimuth
- cond_elevation
shading_temperatur_sensor2: sensor.haydnstrasse_temperatur
Can someone help me please?
i got also a problem with the actual version and the sun shading part. None of covers go to sun shading position after the automations where triggered! All shading automations worked fine last year, and i didnāt change things in it, only the new versions of this blueprint! The CCA-Validator said, that all is fine! The trace analyser said that there are some values out of the range, but thats not true! The trace i uploaded here. Hopefully someone can help!
now i hang on the same bugsā¦
I donāt have a solution for your problem but I hit the same problem in the sense it worked fine last year but now no cover are going to shading position. I think this blue print got way to complicated and I just gave up on it. Instead, a few days ago I had GitHub Copilot look at my 6 configured cover automations and create much simpler versions on just the actually few features I used for each cover. And these just work for me now.
Glad to see that Iām not the only one. Looking back and forth to what I did wrong as no changes were applied to the settings, just keep updating and it also is not working. Looking forward to the āto be releasedā version being worked on to hopefully gain back shading before it really starts getting hot out there. 
actually i use the dev-version and yesterday it worked as it should 
Thatās good to hear.
Iāve made quite a few changes over the last few days. But I havenāt tested them thoroughly yet. Once thatās done, there will be a release.
I think it is a problem with the migration through different versions. I created a new one from scratch and now itās working for this cover.
after adding all conditions it stopped working again. I figured now out that the weather condition is the issue. If I remove the weather condition the shading is working.
I am using a standard dwd weather entity. Any idea?
the question is, what do you use from the weather entity?
Which version of the blueprint?
which configuration is working and which is not working?
Hi Mr.Herr.Vorragned,
I am testing the 2026.05.05 beta, because I do have also issues with the blueprint always shading.
I have added a github issue topic including all the logs and further details.
Maybe you can keep an eye on it. Also tried to start the blueprints from scratch with new settings, but did not work.
Where can I find the log book entries?
Regards!
Thanks fĆ¼r feedback. Version 2026.05.10 V2 Beta seems to work now much better!
1 Like