Thanks for your help, really appreciate it. If the trace UI in home assistant were better…
Here is another trace, of another window that didn’t shaded either, even meeting all the conditions
I think I’m being too stupid right now 
I can’t find any attributes in the shutter entity. It is a Shelly Plus 2PM.
Have you looked via the developer toolbar?
“cover.ventana_2_2” looks good. But the trace is wrong. This refers to a change of position.
And “cover.ventana_2_4” still has the same problem. Have you deleted the helper entity and created a new one?
I’ve been searching for more than an hour now and can’t find any other error.
Actually yes. Can be the source of the problem? Or are you suggesting that I should do that?
I’m asking because I initially created the helper with the wrong name, and referenced it in the automation with the right name, then realized the mistake and deleted the old one and created it again with the right name
Hi @Herr.Vorragend,
It works like a charm. thanks.
1 Like
Thank you. I have already found the error.
1 Like
New Update
2025.06.07
- Added: Resident check for ventilation #216 (Thanks for the pull request, Astado)
- Added: Better description for shading_forecast_sensor (Thanks you, Eimeel)
- Fixed: Solve Issue with sun shading end if Tilt Position Control is enabled #216 (Thanks for the pull request, Astado)
- Fixed: Shades are being opened or closed even if they are already #219
- Fixed:
When the “End Sun Shading Immediately When Out Of Range” mode was activated, the shading of the cover was not canceled.
This was because the new waiting time was set to 0 seconds and CCA could not trigger itself in the same second via a helper.
- Updated: Extensive code refactoring
- Updated:
Automation mode changed to 'single' as a test, because otherwise new triggers in the delay would interfere with processing.
In the worst case, I will have to work with {{ state_attr('automation.cca_automation', 'current') > 0 }} as before to be able
to intercept the reciprocal triggers.
2 Likes
Please try version 2025.06.07.
This should solve the problem.
If not, please let me know.
1 Like
It works! Thank you.
1 Like
After a long time (and being totally happy with CCA) I updated from 2024.12.xx to 2025.05.07 and now I am facing an issue with one of my covers - the one which has a little exotic closing position: 44%.
In the evening it closes properly to position 44%, but doesn’t open in the morning.
Please find my configuration:
alias: Rollladen Wohnzimmer rechts (CCA)
description: ""
use_blueprint:
path: hvorragend/cover_control_automation.yaml
input:
blind: cover.rollladen_wohnzimmer_rechts_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: "08:00:00"
time_up_late_non_workday: "08:00:01"
time_down_early: "22:30:00"
time_down_late: "23:35:00"
time_down_late_non_workday: "23:35:00"
time_down_early_non_workday: "22:30:00"
drive_delay_random: 0
position_tolerance: 2
check_config: true
contact_cover_place: door
close_position: 44
sun_elevation_up: -3
sun_elevation_down: -3
workday_sensor: binary_sensor.workday_today
cover_status_helper: input_text.rollladen_wohnzimmer_rechts_eg_status
cover_status_options: cover_helper_enabled
shading_azimuth_start: 135
shading_azimuth_end: 190
shading_position: 44
shading_forecast_temp: 24.1
shading_weather_conditions:
- sunny
- partlycloudy
- clear
ventilate_position: 35
contact_sensor: binary_sensor.tuer_fenster_5
shading_brightness_sensor: sensor.helligkeit_2z_illuminance
shading_sun_brightness_start: 80000
shading_sun_brightness_end: 70000
shading_forecast_sensor: weather.home
lockout_tilted_options:
- lockout_tilted_closing
- lockout_tilted_shading_start
contact_delay_status: 1
workday_sensor_tomorrow: binary_sensor.workday_tomorrow
contact_window_tilted: binary_sensor.tuer_fenster_5
The content of the status_helper:
{"open":{"a":0,"t":1749358731},"close":{"a":1,"t":1749414601},"shading":{"a":0,"t":1745269267,"p":0,"q":0},"vpart":{"a":0,"t":0},"vfull":{"a":0,"t":1748982600},"manual":{"a":0,"t":1749358731},"v":5,"t":1749414601}
And the Trace
The attributes of the cover entity:
current_position: 44
device_class: shutter
friendly_name: Rollladen Wohnzimmer rechts EG
supported_features: 15
V2025.05.07 or V2025.06.07?
As I described in the posts above, there was a stupid bug. Then please update and get back to me, please.
Update:
Oh, I see in the trace that you have the May version. Then please update it.
Oh no. It’s something else with you. Your Close+Shading positions are identical. That was never allowed to happen. But it happened to work for a long time, but then caused other problems.
"close_position": 44,
"shading_position": 44,
ooops, well spotted. I overlooked for months …
Thanks a lot - will change it and see what happens tomorrow.
It seems that I have problems with the timely execution of the automation. Furthermore, the shutter was not closed at 19:30, although tomorrow is a school day and the corresponding binary sensor is active. A trace was not created, so the automation was not triggered at all.
Bonjour,
The solar elevation sensor is not taken into account. The shutters close from the closing time is reached without taking into account the elevation. I installed sun.sun activated the elevation sensor and I entered it in the automaton with a value of -2 degrees.
Hmm. That’s what you get when you want to optimize the code. 
I am currently experiencing this behavior myself. It’s definitely a bug. I’ll take a look at it.
1 Like
That may be the case. But it may not be.
However, I would need a little more information in order to answer this specifically. I wrote something about this in the second post of the thread.
