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

My intention is to open only the tilt. As Notes say open needs to be higher than close i set the cover position just to 2 and tilt to 50 for opening.

Even when I disable forcing down, the automation doesn’t do anything, although in automation list it reports it was launched “30 seconds ago” but nothing happened. I have absolutely no idea what is going on…

Eventhough thank you so much for your help :pray:t2:

Unfortunately I have to ask for help too. It works fine in my case except on one cover (its maybe this one because I use it diferently, but its the exact same type as the others.
My use case is this:
I bring the cover to 65% with CCA in the evening so the neighbors don’t see in the house. Then I open the cover again some hours later to go out with the dog and then I close it again, but with the hardware button to, 80%. It never closes to 100%. The cover does not open in the morning. It is also not closing in the evening if I moved it manually during the day.

Here are my traces:

Hi,

is it possible to put all my shutters in one automation (copy paste)? I have 20 shutters but I would like to have them all in one automation.
Kind regards
Michael

In the Helper-Section you can create a new Group containing all shutters.

1 Like

To be honest, I can’t really recommend it, as the shading function and ventilation are not very flexible. But yes, it works.

1 Like

I have a problem with a roller blind that is not moving as it should. I set up the automation again this morning in the same way as for the neighbouring window. It went up this morning. However, it didn’t go down again this evening.
These are Homematic components. The virtual channels of the window handle sensor, window contact and roller shutter are linked to realise the ventilation position and complete opening - this works. I don’t want to map this function via the automation. It is only about opening and closing the roller blind.

alias: Shuttercontrol - Bad_EG_F1
description: ''
use_blueprint:
  path: hvorragend/cover_control_automation.yaml
  input:
    blind: cover.bad_eg_f1_rollo
    auto_options:
      - auto_up_enabled
      - auto_down_enabled
      - auto_sun_enabled
      - auto_brightness_enabled
    time_up_early: '05:00:00'
    time_up_early_non_workday: '07:30:00'
    time_up_late: '07:30:00'
    default_brightness_sensor: sensor.ms_garagentur_illuminance
    brightness_up: 45
    brightness_down: 42
    workday_sensor: binary_sensor.workday_sensor
    shading_azimuth_start: 0
    shading_azimuth_end: 53
    shading_temperatur_sensor1: sensor.weatherman_sonnen_temperatur
    shading_min_temperatur1: 35
    shading_tilt_position: 50
    shading_cover_position: 20
    shading_waitingtime_start: 60
    shading_waitingtime_end: 300
    position_tolerance: 1
    open_position: 100
    cover_status_options: cover_helper_enabled
    cover_status_helper: input_text.shutter_status_bad_eg_f1

Status_Helper:

{"open":{"a":true,"t":1709276404},"close":{"a":false,"t":0},"ventilate":{"a":false,"t":0},"shading":{"a":false,"t":0},"locked":{"a":false,"t":0},"manual":{"a":false,"t":0},"v":3,"t":1709276404}

Trace:(trace automation.shuttercontrol_bad_eg_f1_2 2024-03-01T16_56_39.086450+00_00.json - Google Drive)

New update:

2024.03.01-01:
  - Roller blinds may only be closed once after Time_Down_Late. Previously, the entire day was checked.
2 Likes

I took a look at your trace. Your problem should also be solved with the latest update.

That’s a little more difficult.
I can’t do anything with the trace from February 29. Here you have manually moved the blind and changed the status of the helper.

In the trace from March 1, I can see that the Cover Status Helper apparently already says that the roller blind is open. Then, of course, it is not triggered again.
Either the status in the helper is wrong or you have sent me a trace that is too late.

Could you please show me the history of the Cover Status Helper from the two days?

Thank you for answering! I try to generate new traces. Gotta increase the number.

Here are the screenshots of the helper.

29/02 07:02:21: Automatic opening through CCA (100%). I didn’t move the cover manually in the evening before.
29/02 18:35:34: Automatic closing to 65% through CCA
29/02 21:24:53: Opening for going out with the dog (100%)
29/02 21:47:04: Manual Closing(means going to 20%, not fully closing!)
01/03 07:01:24: Manual opening because CCA didn’t work.



Quick edit: I disabled the lockout protection yesterday and it worked exactly in this pattern this morning. Does this bug belong to your GitHub issue regarding checking the ventilation position even when not necessary?

1 Like

But when I don with one shutters, can I take the yaml and copy and past (with a little entitty change for ventilaten for example) in one big yaml?

  1. You can duplicate automations in the GUI.
  2. You can copy&paste the lines in automations.yaml.

I faced the same problem a few weeks ago and have successively created the automations manually. And copied the values (brightness, sun, etc.) from my old automations.

Honest opinion? In the time you are now looking for a solution, you could have copied everything long ago. It takes less than half an hour.

2 Likes

I found that when I activate boolean to force closing, the automation gives commands to close and then immediately to open the blind, which stops the process. If it’s supposed to follow the schedule, it doesn’t give any commands.

Here I add screenshot of commands and traces

Traces

Unfortunately not.


You told me that the roller blind was closed by the automation system at 18:35:34. But I can’t see that in the screenshot. It says that the status is “open” and that it was probably triggered manually.


But regardless of this, I wonder how a blueprint is supposed to query this.

Your positions are configured as follows:

"open_position": 100,
"close_position": 65,
"ventilate_position": 85,

The blueprint also states the following under “Important Notes”:

- `open_position` should be higher than `close_position`
- `open_position` should be higher than `ventilate_position
- `close_position` should be lower than `ventilate_position

However, this does not really matter if you use the Cover Status Helper.

My main problem:

  • You let CCA close to 65%.
  • Then you manually close to 20% later.
  • How is CCA supposed to know what the status is?

Your desired privacy mode with 65% makes this much more difficult and I would do without it.

I also need the second trace.

Update: And you might want to deactivate further drives via auto_up_condition and auto_down_condition when overriding.

Thanks for your help again!

I tried different settings of the ventilation position, but it didn’t change the behavior. Since I don’t use the ventilation anyway I was thinking it doesn’t matter.

I get exact percentage values for all of my covers, so CCA can exactly know where my cover is atm. I thought it is setting the position on the base of these percentage values? Is it just time based?

I am afraid there is not second trace, another one is 30 minutes before this one.

Sorry, but there is nothing in the trace at 7:09:57pm.
What kind of actuators or relays do you have? Could it be that the
set_cover_tilt_position” leads to a reversal in your case?

Then please tell me what status CCA should assume at 20%?
65% is probably recognized without any problems.