Cover Control Automation (CCA) - Intelligent Automation for Blinds, Awnings & Shutters | Calendar, Sun Shading, Force Functions

Your question is a bit older. Have you already been able to solve it?

I would use the additional actions here. And you have to deactivate the execution of the actual commands in the blueprint: “Prevent ‘set_cover_position’ and ‘set_cover_tilt_position’”

I am pretty sure that a trace must exist for the triggers (close blind or detect/execute shading). I need these.

You can also increase the number of traces. See the second post above.

It is described as follows in the blueprint:

    Note:
      - However, after forcing a state, you must ensure that you move to the correct target position yourself. You are responsible for getting CCA back on track.
      - This cannot be performed in CCA and must therefore be done via a separate automation. Presumably in the same automation that sets the "Force"-boolean. It is sufficient, by the way, if a configured position is targeted. CCA then recognises the status.
      - Force is a final state that cannot be cancelled or resetted by CCA.

If you remove the automation from the rhythm, CCA no longer knows exactly what the status is afterwards. So you have to fix it yourself. There is currently no other way.

With all due respect, but how am I supposed to answer that from afar?

Please show me a trace of a trigger that didn’t work.

Do you perhaps use Cover Status Helper and have you copied this information? Then two CCA blueprints would share one helper. This will not work.

There are a few oddities here. Firstly, the fact that your helper is configured incorrectly has already been described.

This may not play a role, but you seem to live in Germany. So where do these extreme values come from?

sun_elevation_down: 56
sun_elevation_up: 229

But the biggest problem will be this:

shading_position: 0

This means that the shading position is identical to the close_position. This will not work. Please also note the information under “Position Tolerance”.

Please deactivate the option “Enable brightness control (in addition to daily opening and closing)”. This is active for you, but you have not configured a brightness sensor. It could be that the conditions are then always valid and therefore the earliest time is used.

This is a wrong trace. This refers to the detection of the target position. I need the triggering before that.

Then you should solve the problems with the hardware or integration beforehand. The blueprint must be able to rely on the circumstances. Sorry.

Just take a look at the fantastic blueprints from Blacky:

It looks perfect to me. That should be enough.

Please let us troubleshoot individually, otherwise I will lose the overview here in the thread.

Please write me a specific problem.
What did not happen at what time. And what should have happened.
Then please add the corresponding trace to the post. Maybe even the traces before and after. This plays a major role in shading.

Unfortunately, this will not be possible.
I have to rely on the “current_position” attribute in the cover entity. Sorry.

Have you also configured a Cover Status Helper?

Enable automatic sun protection / sunshade control (helper required)

Can you at least show me your CCA config?

hi,

Please excuse me if I’m asking a slightly daft question. I’ve been using FHEM since 2013 but only a few months in HA. Everything has worked so far, so I’ve never had to do any deeper troubleshooting.

What do you want to see from the trace menu if you want to see a ‘trace of triggering’?

???

How should the values for shading position and closing position be composed?

If shading is required, the external venetian blind should move to 0 percent (fully closed)

When the external venetian blind closes, it should move to 0 percent (completely closed)

When it fans out, it is always between 0/2 percent.

I have set the position tolerance to 4%.

According to azimuth, the venetian blinds now move correctly but they do not fan out, but remain at 0 position and 0 tilt angle.

Please search for the affected trigger at the top of the arrows. And then save the JSON (top right).

I look for triggers such as time, threshold reached and so on. Depending on the problem you have.


Hello!

The automation is working fine so far with the nightly closing, but now I started with setting up the sun protection, and unfurtunatly, it is not working as expected.

I am especially wondering why the helpers, that are set up as a text input, stay on unknown. This is my config:

alias: Rollosteuerung TV Links
description: ""
use_blueprint:
  path: hvorragend/cover_control_automation.yaml
  input:
    blind: cover.velux_external_cover_roller_shutter_3
    check_config: true
    auto_options:
      - auto_shading_enabled
    workday_sensor: binary_sensor.workday_sensor
    time_up_early: "06:00:00"
    time_up_early_non_workday: "07:00:00"
    time_up_late: "07:30:00"
    time_up_late_non_workday: "07:00:00"
    sun_elevation_up: 0
    sun_elevation_down: -5.8
    workday_sensor_tomorrow: binary_sensor.workday_sensor
    default_brightness_sensor: sensor.lichtsensor_terrasse_aussen_lichtsenor_terrasse_aussen_lux
    brightness_up: 5
    brightness_down: 10
    shading_brightness_sensor: sensor.lichtsensor_terrasse_aussen_lichtsenor_terrasse_aussen_lux
    shading_azimuth_start: 180
    shading_azimuth_end: 260
    shading_temperatur_sensor1: sensor.hg_wohnzimmer_temperatur
    shading_min_temperatur1: 23.5
    cover_status_helper: input_text.helper_tv_links
    cover_status_options: cover_helper_enabled

Does anybody of you have an idea what I am doing wrong? the temperatur is at 25°, azimuth at 227°, and sun elevation at 47° so I really wonder where the problem is coming from.

Thanks in advance,
Alex

The helper remains empty if you have never triggered automation. But I can’t imagine that. Or have you just created them?
Or the helper is configured incorrectly. Does it have a length of 254 characters?

You have only activated shadowing. Nothing more. Then these values don’t really matter. They’re probably still legacy, right?

sun_elevation_up: 0
sun_elevation_down: -5.8
brightness_up: 5
brightness_down: 10

Show me a trace of a triggering and I might be able to recognize what’s wrong with the helper.

Side note: You know that numerical triggers are only triggered when the threshold is exceeded, right?
Once it is above the temperature, there is no further trigger.

I set it up 2 days ago, for several shutters seperat automations, and some of them also close in the evening and open in the morning - and also there, the helper says unknown. I wonder wher I can adjust the length? I checked the helper but couldn’t find a setup.

Regarding these legacy things, I use that in winter, but deacivated it in summer.

I will send you a trace as soon as I have it, but somehow my feeling is that it is connected to the helper issue.