-
Notifications
You must be signed in to change notification settings - Fork 14
Advanced Use Cases 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.
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: trueautomation:
- 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_endTo 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: nullstart_time and start_entity are mutually exclusive. Passing both in the same call raises a validation error.
-
Runtime Configuration Services: full
set_automation_timingfield reference - Configuration β Automation: tracking window and delta options UI
- Advanced Use Cases: all advanced use case recipes
π Home Β· β¨ Features Β· π° What's New
π Getting Started
- Installation
- Migrating from Custom Repository
- Migrating from Adaptive Cover
- First-Time Setup
- Cover Types
π§ Core Concepts
π Cover Types
βοΈ Configuration
- Sun Tracking
- Position
- Glare Zones
- Automation
- Custom Position
- Force Override
- Weather Safety
- Climate
- Blindspot
- Summary Screen
- Debug & Diagnostics
π Entities & Services
- Entities
- Proxy Cover Entity
- Position Verification
- My Position Support (Somfy RTS)
- Runtime Configuration Services
π οΈ Operations
π§ Advanced Use Cases
- Dynamic Temperature Thresholds
- Dynamic Tracking Window
- Bedroom Sleep Mode
- Handling Variable Cloud Cover
- Venetian Tilt-Only on Overcast Days
π¨ Dashboard
π§ͺ Testing & Simulation
π Reference
π©βπ» For Developers