☀️ Cover Control Automation (CCA) - a comprehensive and highly configurable roller blind blueprint

so…
the normal part with sun shading works now.
But the part with ventilation didn’t work. there must be a problem with the statushelper. It didn’t change. Have 2 identical automations for 2 covers. One of them had the open-door-ventilation enabled. For the normal automation the statushelper changed as is should 5 times until now. The statushelper for the ventilation-automation just changed one time! At the begining of the shading.
So the only status i have is the following:


At this time the door was open. About 20min later the doors was closed. So normaly the statushelper should change again! but nothing happens!
here are “some” traces: https://file.io/7C5WqjgBE5x5

Edit: in addition to the post above from thorstenniemann.tn, i also had some errors with the none working automation! looks if there is a problem with the “vpart” in the status helper!

I don’t have any traces at hand right now because I’m on my cell phone, but my observation matches the previous posts.
There is something wrong with the ventilation setting.
It is being ventilated but the roller blind is moving towards it or remains open at 100% instead of the set value.

I don’t really understand…

I use Version : 2024.09.05

Why is the shading not carried out here?
https://file.io/98fHEoivCUSx

alias: Cover Control Spülenfenster
description: ""
use_blueprint:
  path: hvorragend/cover_control_automation.yaml
  input:
    blind: cover.rolladen_spulenfenster
    auto_options:
      - auto_up_enabled
      - auto_down_enabled
      - auto_brightness_enabled
      - auto_sun_enabled
      - auto_shading_enabled
    default_brightness_sensor: sensor.wetterstation_warema
    brightness_up: 20
    brightness_down: 10
    sun_elevation_down: -3
    sun_elevation_up: -0.5
    workday_sensor: binary_sensor.workday_sensor
    check_config: true
    cover_status_helper: input_text.cover_helper_spulenfenster
    cover_status_options: cover_helper_enabled
    time_down_early: "18:00:00"
    time_down_early_non_workday: "18:00:00"
    auto_up_condition: []
    auto_down_action: []
    time_up_late: "08:00:00"
    time_up_late_non_workday: "08:30:00"
    time_down_late_non_workday: "22:00:00"
    time_down_late: "22:00:00"
    brightness_time_duration: 120
    resident_sensor: input_boolean.schlafend
    shading_forecast_temp: 23
    shading_temperatur_sensor1: sensor.temperatur_kuche_temperature
    shading_min_temperatur1: 21
    shading_tilt_position: 90
    shading_azimuth_start: 65
    shading_azimuth_end: 165
    auto_shading_start_action: []
    shading_position: 20
    sun_time_duration: 60
    individual_config: []
    ignore_after_manual_config:
      - ignore_shading_after_manual
    shading_temperatur_sensor2: sensor.gw1000a_v1_7_6_temperature_1
    shading_min_temperatur2: 19
    shading_brightness_sensor: sensor.wetterstation_warema
    shading_elevation_min: 10
    reset_override_config: reset_timeout
    reset_override_time: []
    auto_shading_start_condition:
      - condition: state
        entity_id: sensor.season
        state: summer
    shading_weather_conditions:
      - sunny
      - partlycloudy
      - cloudy
      - clear
      - lightning-rainy
      - rainy
    reset_override_timeout: 30
    check_config_debuglevel: info
    drive_time: 60
    shading_forecast_type: weather_attributes
    shading_waitingtime_start: 30

I would be happy if someone could help me …

Greetings

Since the latest updates this automation is nog working anymore. I’ve checked if the following variables are deleted:

prevent_close_after_lockout
auto_lockout_protection_enabled
contact_sensor
contact_sensor_lockout
prevent_closing_by_resident
is_reset_time (replaces with is_reset_fixed_time)

I only have sun shading enabeld:

When I look at the logbook I can see it’s getting triggered by “time change”

This is my config:

alias: Cover Control Automation (CCA)
description: ""
use_blueprint:
  path: hvorragend/cover_control_automation.yaml
  input:
    blind: cover.screen
    time_control: time_control_disabled
    auto_global_condition: []
    auto_up_force: binary_sensor.is_it_raining
    default_brightness_sensor: sensor.gw2000a_solar_lux
    brightness_down: 25000
    brightness_up: 40000
    shading_azimuth_start: 140
    shading_azimuth_end: 310
    auto_options:
      - auto_shading_enabled
    cover_status_helper: input_text.cover_status_helper
    cover_status_options: cover_helper_enabled
    brightness_time_duration: 600
    sun_time_duration: 300
    shading_brightness_sensor: sensor.gw2000a_solar_lux
    shading_sun_brightness_start: 40000
    shading_elevation_min: 0
    shading_temperatur_sensor1: sensor.living_room_temperature
    shading_min_temperatur1: 21.5
    shading_temperatur_sensor2: sensor.gw2000a_outdoor_temperature
    shading_min_temperatur2: 16
    shading_position: 0
    check_config: true
    shading_forecast_type: daily
    shading_waitingtime_start: 600
    shading_waitingtime_end: 900
    shading_sun_brightness_end: 22500
    shading_forecast_temp: 18

I currently don’t have any traces available. Will add them when I have some useful ones.

I want to use shading when azimunth is between certain values, lux is above certain value and outside temp is above certain value. This was working perfectly. But at the moment I don’t know what the screen is doing anymore.

Same here :slightly_frowning_face:

exactly same here:

alias: Cover Control Markise
description: ""
use_blueprint:
  path: hvorragend/cover_control_automation.yaml
  input:
    blind: cover.markise
    auto_options:
      - auto_shading_enabled
    default_brightness_sensor: sensor.wetterstation_warema
    brightness_up: 20
    brightness_down: 10
    sun_elevation_down: -3
    sun_elevation_up: -0.5
    workday_sensor: binary_sensor.workday_sensor
    check_config: true
    cover_status_helper: input_text.cover_helper_markise
    cover_status_options: cover_helper_enabled
    auto_up_condition: []
    auto_down_action: []
    brightness_time_duration: 120
    shading_forecast_temp: 24
    shading_azimuth_start: 40
    shading_tilt_position: 0
    shading_azimuth_end: 250
    shading_position: 0
    shading_min_temperatur1: 19
    sun_time_duration: 60
    individual_config: []
    ignore_after_manual_config:
      - ignore_shading_after_manual
    shading_brightness_sensor: sensor.wetterstation_warema
    shading_min_temperatur2: 19
    reset_override_config: reset_timeout
    reset_override_time: "17:00:00"
    shading_forecast_type: weather_attributes
    shading_elevation_min: 12
    auto_down_condition: []
    auto_shading_end_condition: []
    auto_up_force: binary_sensor.regensensor_solar_water_leak
    auto_shading_start_condition:
      - condition: state
        entity_id: sensor.season
        state: summer
      - condition: state
        entity_id: binary_sensor.regensensor_solar_water_leak
        state: "off"
        for:
          hours: 0
          minutes: 0
          seconds: 0
    drive_time: 70
    reset_override_timeout: 60
    open_tilt_position: 100
    close_tilt_position: 0
    shading_waitingtime_start: 60
    shading_waitingtime_end: 60
    time_up_early: "19:00:00"
    time_up_early_non_workday: "19:00:00"
    time_up_late: "20:00:00"
    time_up_late_non_workday: "20:00:00"
    shading_weather_conditions: []
    auto_shading_end_action:
      - action: cover.open_cover
        metadata: {}
        data: {}
        target:
          device_id: bf53ef562020f767fa047aee6f101422
      - action: notify.notificationgroup
        metadata: {}
        data:
          message: Markise wurde wieder eingefahren.
    shading_temperatur_sensor1: sensor.gw1000a_v1_7_6_outdoor_temperature
    auto_shading_start_action:
      - action: notify.notificationgroup
        metadata: {}
        data:
          message: Markise wegen Hitze geöffnet

With this Update it works perfect again. :+1:t2:

1 Like

Nope, ventilation still not working. Ventilation moves blinds to full open instead to defined position.

After some monitoring today. It did respond on the solar lux. But it looks like the shading doesn’t use the shading_waitingtime_start and end. Here’s the trace of the screen opening when the lux was below threshold.

https://file.io/MryizS3Cn7cp

as a quick workaround for the guys who had probs with the ventilation, try to use the latest beta-Version, this works for me! Just download it from github and change in the automation.yaml the blueprintpaht from the automation to cover_control_automation_beta.yaml

Delete the helper you used in the beta test.

  • vent_partial is now called vpart
  • vent_full is now called vfull

This only affects the beta testers. I need space in the helper and had to shorten it.

Strange. Do you see more in the entire log?

Are you using shading or ventilation?
Can you show me your config?

1 Like

Can you at least show me your configuration?

ok will delete them later today…but its a little bit strange, i never changed/deleted the helper also when coming the first time from the public version to the beta version!..

Maybe because you went back to the beta version yourself in the meantime?

This is a trace that has only reacted to a previous position change (trigger “t_manual_1”).

I need traces for:

  • t_shading_start_pending (something has triggered a possible shading)
  • t_shading_start_execution (after the waiting time, the shading is actually triggered via a separate trigger. And, of course, it checks once again whether the conditions apply).

Dear user firebowl,
you take every opportunity to confirm that something isn’t working for you. That’s generally okay, because it sometimes allows me to deduce whether it’s a major error. But I would also like to help you.

You’ve already mentioned that you don’t currently have any traces to hand. That’s okay too. I can wait.

But your problem doesn’t necessarily have to be everyone’s problem. Of course, a bug could also be the cause. Then I would like to fix it. So traces again.

There’s just no other way.
Every configuration is individual. And everyone has different sensors. I’ll only get really smart if I get the correct logs/configs.

Let’s search together and then we’ll see.

3 Likes

Alternatively, you can simply rename the values.

Sorry for the late reply. Of course you’ll get a trace from me. I know that you are always happy to help with problems. I’m just on the road at the moment and won’t be able to get to my traces until tonight at the earliest.

First Trace https://file.io/JJvntRwHXNFq
In this case, activating the resident mode should lower the roller blind to the ventilation position because the window is open. However, the roller blind remains completely open. If the window is closed, the roller blind moves to the closed position. Until a few days ago, the roller blind moved to the defined ventilation position when the window was open.
I have the same behavior when closing in the evening after the time, but I only get a trace later.