-
Notifications
You must be signed in to change notification settings - Fork 14
Configuration Summary Screen
The Configuration Summary gives you a plain-English view of everything you've configured for a cover, without having to click through each settings page.
- During initial setup: Shown automatically as the last step before the integration entry is created. Review your settings and click Submit to confirm.
- At any time: Open a cover's options (Settings β Devices & Services β Adaptive Cover Pro β Configure) and choose Configuration Summary from the menu.
The summary is organized into four sections:
Your Cover: the cover type, entity IDs being controlled, and physical dimensions (window height, shaded area distance, optional reveal depth and sill height for vertical blinds; awning length and angle for awnings; slat depth and spacing for tilt blinds).
How It Decides: a narrative explanation of every active rule in the order they are evaluated. Each bullet explains what triggers the rule and what the cover does:
- βοΈ Sun tracking: azimuth, field of view, and elevation limits
- π Timing: active window (start/end times) and sunset/end-time position
- π₯ Blind spot: angular range where an obstruction blocks the sun
- π Glare zones: named floor areas protected from direct sunlight (vertical blinds only)
- π‘οΈ Climate mode: temperature-based open/close strategy with entities and thresholds
- βοΈ Cloud suppression: skips sun tracking when lux, irradiance, or cloud coverage indicate no direct sun
- π Light sensors (informational): noted when configured but suppression is off
- β Manual override: pause duration, position threshold, and reset behavior
- πΆ Motion-based control: sensor count, timeout, and fallback position
- π§οΈ Weather safety: active weather conditions (wind speed, rain rate, binary sensors) and retract position
- π Force override: sensor count, target position, and the note that it overrides everything else
Only rules that are configured and active are shown. Unconfigured features are omitted.
Position Limits: a compact one-line summary of the default position, min/max range (with a note if the range only applies during sun tracking), minimum position change, minimum interval between moves, and any active flags (inverse state, interpolation).
Decision Priority: a single line showing all 10 pipeline handlers in priority order with β (active in your config) or β (not configured) for each:
β
Force(100) β β
Weather(90) β β
Manual(80) β βCustom(77) β βMotion(75) β β
Cloud(60)
β β
Climate(50) β βGlare(45) β β
Solar(40) β β
Default(0)
This answers the common question: "what overrides what?" The leftmost β handler that fires wins.
- Before saving a new cover: catch a misconfigured threshold or missing sensor before the cover goes live.
- After changing settings: confirm the change had the effect you expected.
- When troubleshooting: the priority chain shows at a glance which handlers are active and whether the right one would fire. For deeper per-turn diagnostics, see Step 1: Check the Decision Trace.
- Sharing your config: the summary is self-contained and human-readable, making it easy to share when asking for help.
π 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