Oh, now I know why the error has suddenly appeared and nobody has reported it in the last few months.
A few days ago, I wanted to prevent a roller blind from moving into the shade twice. As a result, I added a condition that now prevents CCA from executing this branch. So CCA continues and opens the blind. So the bug is not that old.
Thanks for the reply. Thuis is the friendly name for the entity Meteorologisk institutt (Met.no). It shows the following attributes:
temperature: 24.6
dew_point: 7.6
temperature_unit: °C
humidity: 34
cloud_coverage: 20.3
uv_index: 3.6
pressure: 1011.1
pressure_unit: hPa
wind_bearing: 142.1
wind_speed: 12.2
wind_speed_unit: km/h
visibility_unit: km
precipitation_unit: mm
attribution: >-
Weather forecast from met.no, delivered by the Norwegian Meteorological
Institute.
friendly_name: Forecast Thuis
supported_features: 3
I’ll start with enabling the forecast and check with openweathermap if needed.
2025.05.11:
- Fixed: Fixed bug that the cover can be opened again by the time-up-late-trigger despite existing shading.
I thought it was somehow strange that this was the reason and have just looked again.
It’s not because of the weather integration.
You have not set a value for “shading_forecast_temp”. And that’s why the comparison runs into an error.
{{ state_attr(shading_forecast_sensor, 'temperature') | float(default=shading_forecast_temp - 1) > shading_forecast_temp }}
For whatever reason the shading is not working anymore on my side.
Trace at 7.45 where conditions should have been fulfilled:
platform: template
value_template: >-
{{ states(shading_temperatur_sensor2) | float(default=shading_min_temperatur2)
shading_min_temperatur2 }}
enabled: ‘{{ is_shading_enabled and shading_temperatur_sensor2 != }}’
id: t_shading_start_pending_4
alias: CCA-2-Beschattung_Seite VDB_Bad
description: erstellt 22.02.24
use_blueprint:
path: hvorragend/cover_control_automation.yaml
input:
shading_forecast_sensor: weather.pirateweather
blind: cover.s25_og_bad_20
auto_options:
- auto_shading_enabled
- auto_up_enabled
- auto_down_enabled
- auto_sun_enabled
- auto_ventilate_enabled
time_control: time_control_input
cover_status_options: cover_helper_enabled
drive_time: 20
time_up_early: ‘07:00:00’
time_up_early_non_workday: ‘07:30:00’
time_up_late: ‘08:30:00’
time_up_late_non_workday: ‘08:30:00’
close_position: 20
time_down_late: ‘23:00:00’
time_down_late_non_workday: ‘23:00:00’
workday_sensor: binary_sensor.workday_sensor
position_tolerance: 5
shading_position: 30
shading_azimuth_start: 50
shading_azimuth_end: 230
shading_min_temperatur1: 0
shading_weather_conditions:
- sunny
- partlycloudy
- clear
check_config: true
auto_global_condition:
- condition: state
entity_id: input_boolean.automatisierung_rollade_standard_automodus
state: ‘on’
shading_elevation_min: 0
shading_forecast_temp: 19
sun_elevation_up: -1.5
sun_elevation_down: -2.6
cover_status_helper: input_text.rolladen_status_inputhelper_vdb_bad
individual_config:
- allow_shading_multiple_times
auto_shading_start_condition:
- condition: state
entity_id: input_boolean.automatisierung_rollade_sonnenschutz
state: ‘on’
ventilate_position: 50
ventilate_tilt_position: 35
auto_ventilate_force: input_boolean.automatisierung_rollade_ventilation
shading_sun_brightness_start: 0
shading_sun_brightness_end: 0
shading_min_temperatur2: 12
shading_waitingtime_start: 60
auto_shading_end_condition:
brightness_time_duration: 0
drive_delay_random: 0
open_tilt_position: 80
shading_temperatur_sensor2: sensor.pirateweather_temperature
shading_forecast_type: weather_attributes
ignore_after_manual_config:
- ignore_opening_after_manual
reset_override_config: reset_time
auto_shading_start_force: input_boolean.automatisierung_rollade_sonnenschutz_garten_seite_force
Hello!
it’s not possible to use irradiance instead of brightness, is it?
what happens when i need to override automatic shading? can i reset it?
example:
cover is closed because of azimuth settings, i need to open the shutter but after some time i’d like to set it in auto mode again. will it check if it should be open/closed according to azimuth & brightness parameters?
best regards
At this time, the temperature attribute of your weather entity was not 19 degrees C (value of shading_forecast_temp).
You can use all numeric sensors.
Yes, you can use the Force feature for this.
Please have a look at the second post of the thread. Especially the part with the numerical triggers. You will probably miss this later. Or you can bring CCA back to a suitable state yourself.
Danke @Herr.Vorragend
Screen 1:
Configuration:
ok, so i found this in the 2nd post:
in the blueprint “manuel override” section i can only find time related settings. is there also a possibility to reset manual override with a button/switch?
where would i enter the sensor + parameters?
or sould i just select the irradiance sensor as “Brightness Sensor For Sun Shading” and put W/m² parameters in the “Sun Shading Brightness Start/End” fields (which have lux as unit…)?
You have selected the following in your configuration:
Do not use a weather forecast, but the current weather attributes
The temperature attribute of your weather entity is then used. And this is not the maximum value, but the current temperature.
In addition, the sensor “shading_temperature_sensor2” (= “sensor.pirateweather_temperature” in your case) is also used.
However, this was also not above 19 degrees C at the time.
Have you already started with CCA and tried out a few things? Or are you just asking theoretically what is possible?
Please go through the input fields step by step and read the description. Then you might find something interesting.
The question is also what exactly you have in mind. You want to override the shading? Okay, of course that’s possible. And what should happen afterwards? Back to shading at the touch of a button? That is not possible. You’ll have to sort that out yourself.
As soon as you get CCA out of rhythm and leave the pseudo-state machine (force feature?), CCA can only continue with difficulty. You then have to move to a specific position in your own automation.
2025.05.12:
- Fixed: Multiple triggering of a detected shading has skipped the waiting time until execution
Is it possible to add a second cover for tilt?
I have by my blinds 1 entity for up and down(cover.raffstore_balkontur) and a second entity for tilt(cover.raffstore_balkontur_tilt)
It would be a great help to not make the room completely dark, but just keep the sun out while keeping the room bright.
That would really be the last thing missing from this otherwise perfect blueprint.
Hi Daniel,
Thank you very much for your support. I have already read your request. 
On the one hand, I also intend to make the actions completely dynamic: Allow individual actions such as homematicip_local.set_cover_combined_position · Issue #162 · hvorragend/ha-blueprints · GitHub
The only thing that bothers me is that I can no longer see anything in the trace. This seems to be a peculiarity of HA.
And what’s even worse is that errors can occur for the user. This in turn can lead to higher support.
Can’t you actually use the additional actions for this as well? You can use it to do your own things after each sequence.
That should work wonderfully, right?
2025.05.13
- Fixed: The nightly shading reset has changed the timestamp and therefore a new shading with active 'prevent_shading_multiple_times' can never be executed.
How work this?
Additional action wait this the nirmal 300 sec and the time till my cover close?
I was missing this value. I’m making progress now, screens are starting to behave like I want
Again, thank you so much for this, coffee coming your way!
I’m really sorry, but I don’t understand the question.
You don’t have to feel obliged to do anything. That’s important to me. It’s all voluntary here.
But it’s good to hear that you’re making progress.