I haven’t changed anything on the beta blueprint yet. So the error remains as before.
I already have some ideas for a solution. It’s just more complex than I thought.
There can really be many reasons for this.
Please upload a trace for the trigger “t_shading_1” here and I’ll take a look.
yep i know, that there were no changes, but i thought i reply again with the hint, that there is a “workaround” 
Ah okay. Now I understand.
Thank you.
Hello,
again, many many thanks @Herr.Vorragend for the amazing CCA blueprint. I was a tiny bit involved in Eimel’s predecessor
Unfortunately I have to bother with a shading problem as well, or more precisely I have a problem with shading of several covers.
today it was a very sunny and clear day, about 28°C. I expected shading to kick-in for my windows to the east in the morning, and for the ones to the south at noon.
But all covers stayed open.
Conditions for the shading are daily weather forecast, brightness, azimuth and elevation.
I provide the information for the automation for one of the east windows/covers.
The trace:
The configuration:
d: '1717248849774'
alias: Rollladen Küche (CCA)
description: ''
use_blueprint:
path: hvorragend/cover_control_automation.yaml
input:
blind: cover.rollladen_kuche_eg
auto_options:
- auto_up_enabled
- auto_down_enabled
- auto_sun_enabled
- auto_shading_enabled
- auto_ventilate_enabled
time_up_early: '07:00:00'
time_up_early_non_workday: '07:30:00'
time_up_late: '07:45:00'
time_down_early: '16:30:00'
time_down_late: '22:30:00'
drive_delay_random: 0
position_tolerance: 2
check_config: true
brightness_up: 30
brightness_down: 2
contact_sensor: binary_sensor.tuer_fenster_7z
time_down_late_non_workday: '22:30:00'
time_down_early_non_workday: '16:30:00'
sun_elevation_up: -3
sun_elevation_down: -3
workday_sensor: binary_sensor.workday_sensor
shading_position: 55
shading_azimuth_end: 125
shading_elevation_min: 12
shading_waitingtime_start: 120
shading_waitingtime_end: 240
shading_azimuth_start: 86
shading_elevation_max: 45
shading_weather_conditions:
- sunny
- partlycloudy
- clear
shading_forecast_sensor: weather.hattingen
shading_forecast_temp: 22.9
cover_status_helper: input_text.rollladen_kuche_eg_status
cover_status_options: cover_helper_enabled
drive_time: 22
check_config_debuglevel: error
ventilate_tilt_position: 50
ventilate_position: 60
shading_sun_brightness_start: 80000
shading_sun_brightness_end: 70000
shading_brightness_sensor: sensor.luminosity_1z_luminosity
trace:
stored_traces: 15
and APEX Chart of the data today
showing
- Temperature (outdoor)
- Azimuth
- Elevation
- Position of the cover (Küche)
- Brightness (Ost)
1 Like
I can’t access your file.
ouch - sorry.
I tried again – updated in the original post
At first, big THANKS for this blueprint. This is providing any option I was looking for.
Unfortunately I was not able to get it working. I started with an easy setup, which should open and close my cover based on time.
alias: Büro Cover Control Automation (CCA)
description: ""
use_blueprint:
path: hvorragend/cover_control_automation.yaml
input:
blind: cover.buro_rollladen
auto_options:
- auto_up_enabled
- auto_down_enabled
close_tilt_position: 0
open_tilt_position: 100
check_config: false
check_config_debuglevel: debug
time_control: time_control_input
time_up_early: "06:30:00"
time_up_early_non_workday: "07:30:00"
time_up_late_non_workday: "09:00:00"
I couldn’t find any entries in the log, although I set it to debugging. Does someone have an idea what I can check to get more information what might be wrong here?
It all looks quite good in principle.
But for some reason, your weather condition in the weather forecast array is set to null:
"forecast": [
{
"datetime": "2024-08-27T00:00:00Z",
"condition": null,
"wind_bearing": 114.86,
"wind_gust_speed": 24.1,
"uv_index": 5,
"precipitation_probability": null,
"temperature": 26,
"templow": 14,
"wind_speed": 11.1,
"precipitation": 0
},
And so the process stops and nothing else happens.
However, the weather conditions for the following days are fine:
{
"datetime": "2024-08-28T00:00:00Z",
"condition": "clear-night",
"wind_bearing": 138.75,
"wind_gust_speed": 27.8,
"uv_index": 5,
"precipitation_probability": null,
"temperature": 30,
"templow": 15,
"wind_speed": 14.8,
"precipitation": 0
},
{
"datetime": "2024-08-29T00:00:00Z",
"condition": "clear-night",
"wind_bearing": 241.12,
"wind_gust_speed": 29.6,
"uv_index": 4,
"precipitation_probability": null,
"temperature": 28,
"templow": 19,
"wind_speed": 16.7,
"precipitation": 0
},
You can also try this out yourself using the developer tools. Not that this is a recurring problem with your weather provider.
How did you test it? Did you run the blueprint manually? Because that doesn’t work.
Have you really waited a day?
The roller blind should have been raised by the automation system at 09:00.
I thought the automation would also be executed if it was later than 9 a.m., as it might be checked periodically. Then I’ll wait until tomorrow.
Is there a way to “debug” something before then?
Please try the newest beta updates. Thank you.
Thank you so much @Herr.Vorragend
there seems to be an issue with my (DWD) weather integration.
Until it’s fixed I will disable the weather condition in my config.
Thanks again!
is there a new link to the new beta?..
Strange. Not really.
The automation was triggered at sunset, but the cover was not closed.
From the trace I could see, that the automation ran only in the check_config tree and not in the “Check for closing cover” tree. That’s strange 
The “check config” branch is the default branch that is always executed if no other branches become valid.
Just show me your trace. Then maybe I can help.
1 Like
I forgot the beta suffix in the title. Has been fixed. But it was only cosmetic.
ah the link to the new beta branch changed, thats why i didn’t found it :)…