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

I cannot access your trace. Have to log in there.

thx for implementing negativ values!
but in this case the cover will still close if the temp i set is below the forecast temp or?

I asked for the opposite!

the cover should close if the temp i set is above the forecast temp!

Is that possible? :slight_smile:

Thank you! Looks like I was running a super old version. This one worked right away. I also saw your note and did individual ones - not a cover group. Thanks again!

1 Like

Sorry,
I Change the rights. Hopefully it does work now

Another noob question. Is there a way to update the blueprint into existing automations or do you have to recreate each time there’s an update?

Same issue for me I would say.

Trace: trace automation.cca_2_beschattung_garten_schiessscharte_links 2024-04-06T06_30_00.143487+00_00.json

Yaml:

alias: CCA-2-Beschattung_Garten_Schiessscharte links
description: erstellt 22.02.24
use_blueprint:
  path: hvorragend/cover_control_automation.yaml
  input:
    shading_forecast_sensor: weather.openweathermap
    blind: cover.s25_eg_schiesssch2_li_garten_2024
    auto_options:
      - auto_shading_enabled
      - auto_up_enabled
      - auto_down_enabled
      - auto_sun_enabled
    time_control: time_control_input
    cover_status_options: cover_helper_enabled
    drive_time: 60
    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: 15
    time_down_late: "23:00:00"
    time_down_late_non_workday: "23:00:00"
    workday_sensor: binary_sensor.workday_sensor
    position_tolerance: 1
    shading_position: 20
    shading_azimuth_start: 30
    shading_azimuth_end: 140
    shading_temperatur_sensor1: sensor.openweathermap_temperature
    shading_min_temperatur1: 12
    shading_weather_conditions:
      - sunny
      - partlycloudy
      - clear
    check_config: true
    shading_forecast_temp: 21
    auto_global_condition:
      - condition: state
        entity_id: input_boolean.automatisierung_rollade_sonnenschutz
        state: "on"
    shading_elevation_min: 0
    brightness_down: 0
    sun_elevation_up: -1.5
    sun_elevation_down: -2.6
    cover_status_helper: input_text.rolladen_status_inputhelper_garten_schiessscharte_links

Just go into automations > blueprints and there are three dots at the CCA-blueprint. There you can execute a re-import and he will load the latest version from github and all automations are automatically updated.

1 Like

Hello,

I use the blueprint but i have some questions and kind new on home assistant.

I put a sensor for workday but on the non workday it will close at sun elevation or at time configured on the section.
The second question is if I close my cover at 70% for exemple it will close automatically after with the sun elevation ?

Thanks sorry my english is bad

No, I’m sorry, but that’s not possible with the normal means.

Then I can also undo the change, can’t I?

Sorry, but this is a trace for ending the shading (shading out trigger) and not for activating the shading (shading in trigger).

But I will take a closer look at the shading independently of this. Traces for this are difficult because I already have many conditions in a template trigger and there are no traces there yet.

1 Like

This is a trace from 07:30. That probably can’t be a shading trace, can it?

I feared already, that i downloaded not an appropriate trace, sorry! :frowning:

But i had certainly also the issue, that shading seamed to be a bit off like @Loi mentioned.

yesterday the lock-out prevention kicked in :slight_smile: which I was happy about.

But, after I closed the door the cover stayed open and didn’t close at all - 44% were expected (and configured).

Version: 2024.03.21-01

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_lockout_protection_enabled
    time_up_early: "07:00:00"
    time_up_early_non_workday: "07:45:00"
    time_up_late: "08:00:00"
    time_down_early: "22:30:00"
    time_down_late: "22:35:00"
    default_brightness_sensor: sensor.light_sensor_1_luminosity_value
    contact_sensor: binary_sensor.tuer_fenster_5
    drive_delay_random: 0
    position_tolerance: 2
    check_config: true
    contact_cover_place: door
    close_position: 44
    time_down_late_non_workday: "22:35:00"
    time_down_early_non_workday: "22:30:00"
    sun_elevation_up: -3
    sun_elevation_down: -3
    workday_sensor: binary_sensor.workday_sensor

Did I miss any configuration setting?

And yes, I am not at the latest version. but close to it

I think I have found the solution to my problem. I had not integrated a text helper on the roller blinds that shade. I did that today and now the shading works perfectly.

1 Like

yes i think so…
can i ask, why it’s not possible to implement the “opposite”? I mean shading is great, leds the temperatur outside the room in the summer. But in winter its also neccessary to let the temperatur in the room when its cold outside, mostly in the night :wink:

Thank you. Thank you. The hint has helped me.

New update:

2024.04.08-01:
  - Fixed: Make the shading work even without a helper
1 Like

By the way: If you want to check why the shading trigger is not triggered, you can copy the following lines into the developer tools under Template and adjust the parameters to the blueprint configuration.

Important: A status change is required. If necessary, briefly increase a value via the developer tools and then reduce it again.

The forecast conditions are checked later. There would then be a trace for this.

{% set default_sun_sensor =  "sun.sun" %}
{% set shading_sun_brightness_start = 20000 %}
{% set shading_azimuth_start = 55 %}
{% set shading_azimuth_end = 275 %}
{% set shading_elevation_min = 5 %}
{% set shading_temperatur_sensor1 = "sensor.innen_temperature_filtered" %}
{% set shading_min_temperatur1 = 20 %}
{% set shading_temperatur_sensor2 = "sensor.aussen_temperature_filtered" %}
{% set shading_min_temperatur2 = 18 %}
{% set shading_brightness_sensor = "sensor.lichtsensor_sueden_filter_moving_average" %}
    
{{
  default_sun_sensor != [] and
  state_attr(default_sun_sensor, 'azimuth') | float(default=shading_azimuth_start) > shading_azimuth_start and
  state_attr(default_sun_sensor, 'azimuth') | float(default=shading_azimuth_end) < shading_azimuth_end and
  state_attr(default_sun_sensor, 'elevation') | float(default=shading_elevation_min) > shading_elevation_min and
  (shading_brightness_sensor == [] or states(shading_brightness_sensor) | float(default=shading_sun_brightness_start) > shading_sun_brightness_start) and
  (shading_temperatur_sensor1 == [] or states(shading_temperatur_sensor1) | float(default=shading_min_temperatur1) > shading_min_temperatur1) and
  (shading_temperatur_sensor2 == [] or states(shading_temperatur_sensor2) | float(default=shading_min_temperatur2) > shading_min_temperatur2)
}}
3 Likes

What time did this happen?

Should the blinds have stayed open? Was it already evening?

A trace would also help me a lot here.

I don’t think it’s such a bad idea either.
But I would have to add a completely new status, another logic branch and new triggers. That can’t be combined with shading the sun. Because the comparisons are completely the other way round.

I also have to take into account the so-called “winter shading” for every status change. This has an effect on the entire blueprint.

Maybe I’ll have another idea at some point. But I can’t implement it in a hurry. Sorry.

But you are welcome to modify the blueprint. Anyone can create a fork.
And I would also welcome it if there were pull requests.

Hi,

can you please help me - what is “cover drive time” attribute good for? Is it a mandatory one? In my blueprint the default value is 90 seconds, but the cover drive time is much shorter for the one I’m trying to configure. Just asking before I test the blueprint.