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

Hello and welcome,

So you said that you waited until the trigger. So the automation has been running for about a day?

There can of course be many reasons for this.
With your configuration in YAML format I would already have an approach.

It would be better if you could send me a trace. See here: Troubleshooting automations - Home Assistant

We will manage that. I am convinced of that.

I don’t understand that.
So you open the blind again when you go to sleep?

In winter and autumn, I set my blinds to close when the sun reaches an elevation of -6°. I live in the south of France, and in summer, I prefer to sleep with the blinds open, but I’d like them to close at sunset so the sunlight doesn’t wake me. I understand that blinds can be set to close as the sun lowers, but I would like an settings to close them as the sun rises as well.

Two things I want to accomplish and looking for some advises how to do it the best:

  1. Stop Ventilation from closing the shutters when closing the window.

I use CCA ventilation function in my sleeping room with a window sensor. When I go to bed and put the window into tilt position its perfect that CCA is lifting the shutter to allow airflow. If its in the night e.g. getting too cold and I close the window its as well perfect that CCA is closing the shutter. But in the morning, when there is already some light outside I would prefere that the shutter stays at current position when I close the window. Is there an easy and prefered method to tell CCA when the end of Ventilation shout not move the shutter anymore? Moving the shutter outside of the ventilation position is not how I want solve it I want prevent extra shutter move just for this. I was thinking about manually manipulation the help, but the data seems rather cryptic to me.

  1. Prevent shutters from closing in the evening while light or TV is on

I do not have presence sensors in my household (and don’t want them). But I do not like when the shutters closing in the evening while I’m still awake and active. When I’m active there is typically a light on in the room or the TV is on. Can closing of a shutter put on hold as long a device (or helper) is switched on? There is no expectation to open the shutter again when the light is switched on again. My use case looks like: close the shutter on a daily basis at sun elevation -10 deg, but when a device is detected as ‘on’ delay closing until the device is ‘off’ or the latest time for closing is reached. By this the shutters are closed on time if I’m not at home and if I am at home they close later based on the status of a device I use to delay it. From what I see does current presence detection not allow this, not?

Hello, I would like to come back with my problem of condition to fill in to launch the automation. I defined a boolean which should launch the automation if it is OFF. This condition should only work for opening.Here is the code in my YAML for this part.

 auto_up_condition:
      - condition: state
        entity_id: input_boolean.rdc_occupe
        state: "off"

Obviously at the moment the boolean is OFF, it doesn’t work, the automation doesn’t trigger… And the shutter doesn’t close either. Do you have any idea why?

You can find a trace HERE

Not sure why the blueprint was not updated automatically, but I forced it.
It did not change anything. Since the current position is unknown (I am using the RFXCOM integration to manage my shutters) I am not sure if I can do something with CCA.
I will create an automation from scratch and simply use sun elevation + up / down commands. It should be enough.
Many thanks for taking time to analyse the logs and answer questions :+1:

@Herr.Vorragend It would be very useful if we can provide additional triggers to eg. closing, opening or activating sun shading. In this way we are more flexible for eg. the resident sensor.
With the HA 2024.10 Update we can provide a list of additional triggers and use them in the blueprint.
In the blueprint, it could be a additional section like “Additional Triggers”

1 Like

Sorry, but without knowing the current position of the blind in the form of the attribute (current_position), control via CCA is not possible. In general, this also limits the display in HA if you only know open/close.

Yes, I also read that a few weeks ago. But what’s the big difference between this and the Force features? It does the same thing.

So you go to bed before the sun goes down, do you?

Conditions are not triggers.

sorry i’m french maybe I didn’t express myself correctly…
Do you know why my condition doesn’t works ?

Hey!
Sorry for the late response. :slight_smile:

Here is a trace and my blueprintconfig: https://pastebin.com/raw/Lcv1U07t
Thanks for looking into it!

The force features are restricted to entities. I could create a new entity and set it with another automation to my needs but the automation wouldn’t still check the other conditions in the cca automation.
The additional triggers minds this gap. f.e.:

Sun shading has already took place
The cover were moved manually. No manual detection or reset was configured in blueprint.
Residents leave house
Actual action:
No further action is applied. The cover are still in the last manual position
New action:
An user trigger triggers and sun shading could start another time,

That caused me quite a headache. The trace only output strange things at the critical point. First of all: It’s definitely not due to your condition.
But I have an idea. But you may not like the answer.

What kind of hardware is your cover?
For example, the attribute “current_position” is missing.

And what is the result here in the developer tools? This was completely empty in the blueprint trace.

{{ expand('cover.volets_avant') | map(attribute='entity_id') | list }}

So something is wrong with your cover entity.

Can you perhaps show me the entire status output of the entity from the developer tools?

Unfortunately, this is a trace that only reacts to the position change (trigger: t_manual_). The correct trace with the appropriate trigger (t_open_) should be one step ahead.

Well, that also works without automation. It can also be done directly with template sensors.

But it is indeed…

… a good idea. It’s already on GitHub. The effort should not be great. Many thanks for the idea.

I have take an App: Sunsurveyor.

1 Like

I take this for my livingroom blinds.

Do you have enabled: Enabled generic automatic opening ?

Hello, whis Force Features can I close(close down and tilt down)my blinds at 21h? When the Sun goes down I have configured that my blind only tilt down because I have the blind a 30% open if the dog or the cat want to go to the Garden.
Nice day.

At this time I have make an other Automation a 21h to close the binds.