Skip to content

Advanced Use Cases Dynamic Tracking Window

Jason Rhubottom edited this page May 7, 2026 · 2 revisions

Dynamic tracking window

Drive the start and end of the sun-tracking window from input_datetime helpers rather than fixed times. Useful when your schedule changes by season, day type, or occupancy.

set_automation_timing stores the entity reference, not the current time value, so the coordinator re-reads it on every cycle. Changing the helper later shifts the window automatically with no further automation needed.


Step 1: Create the helpers

In Settings β†’ Helpers β†’ Create Helper β†’ Date and/or time, add two helpers with Time only enabled:

Helper Name
input_datetime.acp_start ACP β€” Tracking window start
input_datetime.acp_end ACP β€” Tracking window end

Or declare them in configuration.yaml:

input_datetime:
  acp_start:
    name: ACP β€” Tracking window start
    has_time: true
  acp_end:
    name: ACP β€” Tracking window end
    has_time: true

Step 2: Wire the automation

automation:
  - alias: ACP β€” sync tracking window from helpers
    trigger:
      - platform: state
        entity_id:
          - input_datetime.acp_start
          - input_datetime.acp_end
    action:
      - service: adaptive_cover_pro.set_automation_timing
        target:
          entity_id: cover.your_cover   # or use area_id / device_id
        data:
          start_entity: input_datetime.acp_start
          end_entity: input_datetime.acp_end

Switching back to fixed times

To revert to a fixed time, call set_automation_timing with start_time instead of start_entity (and clear the entity reference by passing null):

service: adaptive_cover_pro.set_automation_timing
target:
  entity_id: cover.your_cover
data:
  start_time: "08:00:00"
  start_entity: null
  end_time: "20:00:00"
  end_entity: null

start_time and start_entity are mutually exclusive. Passing both in the same call raises a validation error.


Related pages

Clone this wiki locally