Migrating from Adaptive Cover
Users migrating from AdaptiveCover will need to recreate their configurations manually. See Setup below for configuration steps.
Adaptive Cover Pro migrates existing config entries automatically when you upgrade. The most recent rename pass (v3 → v4, included in the v3.x release line) cleans up some legacy option names. The migration runs on first load — no manual steps required.
| Old key (v3) | New key (v4) | Where |
|---|---|---|
group |
covers |
options |
set_azimuth |
azimuth |
options |
enable_min_position + enable_max_position
|
apply_limits_during_tracking_only |
options (merged with OR semantics) |
mode |
(removed — redundant mirror) | options |
sensor_type |
cover_type |
data |
The migration is idempotent and handles partial-migration cases (when a new key already exists, the old one is removed without overwriting). YAML scripts and blueprints that referenced the old keys continue working for one minor release through a deprecated-alias shim — update them at your convenience.
🏠 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