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

Hi Thorsten,

neither, actually. There is a third option built into CCA for exactly this scenario, and it fits the state model much better than both of yours: the Resident sensor.

Recommended setup

  • Use an input_boolean (e.g. “sleeping”) as the resident sensor. Turn it on in the evening, let your alarm automation turn it off.
  • In the resident section enable “Enable automatic opening when resident wakes up”. Leave “Allow opening the cover when resident is still present” off.
  • Set time_up_early to the earliest alarm time you can imagine, and time_up_late as a fallback for mornings without an alarm.

How it works: at the early opening time CCA switches its internal base state to “open” but does not move the cover, because the resident is still present. When the alarm turns the boolean off, the resident handler fires, checks your opening condition and opens the cover. Shading, ventilation and lockout keep working as usual. If the alarm rings before time_up_early, the cover stays closed. That is intentional, so just set the early time generously.

Why I would not use Force Open via a helper

Force is the highest priority in the cascade and overrides everything while the helper is on: no shading, no ventilation, no lockout, no evening close. So you need a second piece of logic to switch it off again. And when you switch it off, “Return to Target State After Force Disable” derives the target from the background state. If the scheduled opening time has not been reached yet, the background state is still “closed” and the cover drives back down. Force is meant for storm and emergency scenarios, not for a daily routine.

Why I would not call cover.open_cover directly

CCA sees that as a manual movement and sets Manual Override. What happens next depends on your “Automatic movements blocked during Manual Override” settings. If you block automatic closing there, your own wake-up call blocks the evening close until a reset. The “Manual movement inside the schedule window counts as the scheduled event” option helps, but only inside the opening window. Before that window CCA still thinks the cover never opened that morning.

If you really want the alarm to open the cover at any time, even at 4 am in winter, then that is a deliberate override of the schedule. In that case a direct cover.open_cover plus the schedule adoption option does less damage than Force, because nothing stays blocked. But I would rather set time_up_early early enough and stay with the resident approach.

@Herr.Vorragend : i have a short question: I have 2 autoamtions, one for shading and one for closing in the night. in the night automation i use the “Additional Condition For Closing The Cover”, in that case, the cover only should close if the temp will be below 10°. So far so good. The statushelper is set to close even if the cover wont move. But now i have the problem with the shading automation! If i open the door for ventilation and close it, the shading automation closes the cover immediatly! But why? The statushelper before and after the closing was identical (just teh timevalues changed) and looked like {“bas”:“cls”,“shd”:0,“pnd”:“non”,“win”:“cls”,“frc”:“non”,“res”:0,“man”:0,“ts”:{“opn”:1791352171,“cls”:1791403119,“shd”:1790778900,“due”:0,“arm”:0,“man”:1790324020},“v”:6,“t”:1791435463,“d”:1791435463}

In the shading automation only shading and ventilation is active! Any hints for that?