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

Blueprints Exchange
, ,
405

Did you try your config in the developer toolbar? With the code posted here: ☀️ Cover Control Automation (CCA) - a comprehensive and highly configurable roller blind blueprint - #361 by Herr.Vorragend

The trace is not meaningful. I don’t see that anything has been triggered.

You didn’t have to tell me the complete contents of Sun. Sorry, that’s not what I meant. A simple “yes” would have sufficed. :grinning:

But you still had to tell me whether the shading should be carried out between the times (see above).

I have no idea off the top of my head. I’ll have to look for it.

406

Oh, is that how you understand it? Then I probably translated it wrong.

No, it’s definitely triggered. My reference was only to using a schedule helper.

407

The only conditions i want to trigger shading are:

  • when the sun is up
  • when the sun is above a certain elevation (e.g. 3 degrees)
  • when the sun is at a certain azimuth (e.g between 65 and 220 degrees)
  • during sunny conditions (e.g. sunny, clear, party-cloudy)

No specifics with regards to time, or helpers that need to be on/off… just simple… sun is shining… lower screens :slight_smile:

408

I have added a brightness sensor and set the upper and lower value. Now the screen moves!
@Herr.Vorragend is the Brightness sensor a mandatory component for the shading logic to work? It says optional in the description…

409

Oh, that’s great that you told me that. Then I can narrow down the search. In any case, I’ll make it work without the sensor.

1 Like
410

Hello, I tried out your configuration on my system and the shading worked perfectly for me. Specifying the brightness sensor is optional. This was not necessary for me.

But I’ll ask again just to be on the safe side. Is the trigger activated between time_up_early (06:00:00) and time_down_late (22:00:00)? Then it should work perfectly.

Or could it be that your azimuth of 65 and elevation of 6 have been exceeded before 06:00? That would be the only possible explanation for me

I assume that you are from the Netherlands Not far from me And actually, azimuth>65 and elevation>6 should only be exceeded here after 06:00. Of course, you could set the time to 05:00 as a precaution. But somehow that’s strange.

411

Hi,
I have a quick question for my understanding: I created a helper switch that is enabled in case of rain to close a shutter once the rain kicks in. So far this works well. However after the rain is over and the helper switch turns off, can I somehow get the shutter open again but only if shading is not active? Do I need to have the opening part defined with the disabled switch to immediately open? In my case I would like to keep it close if shading condition is met but open it again once the rain is over and no shading is needed. Currently I am missing something because after the rain is over and the switch is off, the shutter remains closed. Just could not figure out what I need to put where exactly to run it like desired. I would appreciate any hint. Thanks!

412

Thank you for your help so far Herr.Vorragend, much appreciated!

Nevertheless i can not get this blueprint to work and it is driving me crazy.

The steps i take: (please check if i might be missing something)

  • I create a new automation based on your blueprint
  • Under “automation options” i:
  • disable option 1,2,3,4,5,6
  • enable option 7 (enable automatic shading)
  • early up time is set to 06:00
  • Late down time is set to 23:00
  • i make sure the sun sensor is set to sun.sun (i have checked all variables are present (e.g. elevation and azimuth)
  • I set the “shading postion” to 1%
  • I set the “shading azimuth start value” to 65
  • i set the “shading azimuth end value” to 300
  • i set the “shading elevation minimum value” to 6
  • i add “rainy” to the forecast conditions next the default ones (sunny, clear, partylcloud)

These are all the steps i currently take to configure the blueprint.
Am i missing something?

413

That all sounds absolutely right. Your config also worked for me.
But you didn’t originally configure the weather forecast here: ☀️ Cover Control Automation (CCA) - a comprehensive and highly configurable roller blind blueprint - #398 by snoekieboe

I am missing the forecast sensor in your sentences.

Please show me your config in YAML format again. Please just copy and paste the code. No screenshot, please.

414

I cant seem to find where to configure the forecast sensor exactly :slight_smile:

My config:

alias: TEST
description: ""
use_blueprint:
  path: hvorragend/cover_control_automation.yaml
  input:
    blind: cover.eetkamer_klein
    auto_options:
      - auto_shading_enabled
    default_sun_sensor: sun.sun
    shading_position: 1
    shading_azimuth_start: 65
    shading_azimuth_end: 300
    individual_config:
      - allow_shading_multiple_times
    shading_weather_conditions:
      - rainy
      - clear
      - partlycloudy
      - sunny
    shading_waitingtime_start: 60
    check_config: true
    time_down_early: "22:00:00"
    time_down_early_non_workday: "22:00:00"
    time_down_late: "23:00:00"
    time_down_late_non_workday: "23:00:00"
    time_up_early: "06:00:00"
    time_up_early_non_workday: "06:00:00"
    time_up_late: "12:00:00"
    time_up_late_non_workday: "12:00:00"
    shading_elevation_min: 10
415

That’s quite a lot of different individual solutions that you want to incorporate here. It’s difficult for me to keep track of everything. Has your original problem been solved where the blinds were not opened?

You’ll just have to try them out for yourself. Sorry.

416

Two lines above:

IMG_2179
IMG_21791179×1015 162 KB

But without this information, it will be ignored anyway. So that’s not our cause.

417

Aaah got it… it’s the name that is putting me on the wrong foot. I expected the “Forecast Temperature Sensor” to be used for the temperature slider underneath alone. But is also used for the forecasted conditions i understand?

And indeed, it does not make a difference. Screens are still not moving :slight_smile:

418

Sorry for not getting back about the other issue. This has been solved. The problem was that there was no percentage value existing. But I was able to find a solution.

As for the current one, I basically define a switch that turns on when it rains. I use that one to have the shutter of a wintergarden closed immediately to “protect” it from rain to keep the glass roof more dry and clean.
So far this works flawless and the shutter closes as described.
However, it will then not open again once the rain switch turns off again. So the question is, if I define the switch as a trigger to open the shutter when being turned of, is there a way to open the shutter again if the rain switch is off again and the shading condition does not apply.

419

I don’t understand why you can answer this directly. With HA triggers, a status change must always be carried out beforehand. And your elevation and azimuth have long since been exceeded this morning.

Unless you change the values via the developer toolbar. Make it smaller once and then set it higher again.

420

of course i have modified my azimuth values (65 to 350) to make sure they work as this time of day. What do you mean with “can’t answer directly”? what do you want me to answer directly?

421

Sorry i didnt see your answer, all working perfectly now, i just put 0% in tolérance position.

I have another question do u know if you will improve thé blueprint ( even if it is a very very nice one ) to keep thé covers closed in winter for example of thé température or weather is cold or rainy.

422

This is not possible with the blueprint either. With the force feature, something is only forced once and it stays that way. I don’t have an “Infinite State Machine” that monitors every feature and returns it cleanly.

The Blueprint cannot suddenly start up again after toggling the helper. I don’t know exactly what you want and when. Should it boot up during the day? And at night? That is simply far too special.

423

Why you can answer this directly. Not me.

424

What i imagine is for exemple i have another automation which active a boolean which tell it is a cold or very warm day for exemple. And so if it is cold or very warm day the covers stay closed.
It is just an idea liké this. I dont know if im clear with that.
But just know thé work made on this blueprint IS already amazing