Hi, I'm using a custom position with a boolean to achieve this, but if embedded in ACP, it could be great

a solution based on 'Advanced Use Cases Bedroom Sleep Mode'

Implement a presence-based, auto-recovering override for Adaptive Cover Pro by creating a template sensor that detects both room occupancy and high sun intensity. Configure this sensor as a "Custom Position Sensor" in the Adaptive Cover Pro UI with a set position and high priority, allowing the system to revert to automatic tracking when the sensor turns off.

template:
  - binary_sensor:
      - name: "Blind Presence Override"
        unique_id: blind_presence_override
        state: >
          {# Get the final target position ACP wants to set #}
          {%set target_pos =  state_attr("sensor.roller_shutter_switch_target_position", "raw_calculated_position")  | int(0) %}
          {% set occupied = is_state('binary_sensor.your_room_presence', 'on') %}
          
          {# Trigger if occupied AND the target is more open than your 20% limit #}
          {{ occupied and target_pos < 20 }}

Custom Position is the right built-in mechanism here, and your template approach is correct.

To wire it up: open the integration options for your cover and configure one of the four Custom Position slots with binary_sensor.blind_presence_override as the sensor and 20% as the position. When the sensor turns on, the pipeline handler fires at priority 77 and holds the cover at 20%. When it turns off, the handler steps aside and solar tracking resumes on the next update cycle.

Your current approach (set_cover_position + button.reset_manual_override) works, but Manual Override runs at priority 80, above custom positions. If something triggers another manual override while occupied, say opening the blind by hand, you'd need a separate reset. The custom position slot clears itself automatically, no cleanup needed.

One thing to skip: Minimum Mode acts as a floor, keeping the cover from going below the configured value while still allowing higher positions from solar. That's the inverse of what you want here.

The feature request makes sense intuitively, but the template pattern is already the intended way to handle it. A dedicated "occupied position" config option would just be a thin wrapper around what custom positions already do, so I'd rather keep the config surface small and point people to this pattern instead.

For the full reference, see Custom Position. The Bedroom Sleep Mode advanced use case uses the same pattern if you want another worked example.

❓ How to reset time_delta_too_small after sensor toggle?

Question

When using Adaptive Cover Pro with Custom Position slots with binary_sensor.blind_presence_override a binary_sensor (e.g. presence or override), I sometimes see:

Last Skipped Action: time_delta_too_small

This happens when the sensor toggles shortly after a previous cover movement.

Goal

I want the system to:

• React immediately when the sensor changes (ON → OFF or OFF → ON)
• Apply the new position without being blocked by the internal timing constraint

Ask

Is there a way to:

• Reset the internal timer when the sensor state changes?
• Force ACP to execute the next action immediately after a toggle?
• Or bypass time_delta_too_small for specific triggers (like presence)?

Alternative

If not possible, what is the recommended way to ensure reliable execution?

• Add delay?
• Debounce sensor?
• Use manual override/reset?

Thanks!

Good timing on this discussion. I just confirmed a bug that directly affects this use case. When a custom-position binary sensor toggles within delta_time minutes of a previous cover movement, the command is silently dropped by the time-delta gate in apply_position(). That is what causes the Last Skipped Action: time_delta_too_small you may see when presence flips on shortly after ACP has already moved the cover.

Tracked in issue #348 — fix is coming in the next release.

The fix I promised in May shipped in v2.19.0 (PR #349). If you're on anything from v2.19.0 onward, which covers the current stable v2.21.5, custom-position sensor edge-triggers now bypass the time-delta gate and apply immediately. You can verify it's working by checking the last_skipped_action sensor after toggling your presence sensor — it shouldn't show time_delta_too_small for that anymore.

For details, see the Custom Position wiki page.