Configuration Force Override

Force Override

As of v2.28.0-beta.7, Force Override is no longer a separate config step. Its functionality has been merged into Custom Positions — any slot set to priority 100 carries the same safety semantics. Existing configurations migrate automatically. See Custom Position → Safety Priority for full documentation.

---

What changed

The standalone Force Override step has been removed from the config flow. Its behaviour — a sensor-triggered override that fires outside the schedule window and bypasses all send gates — is now expressed as a Custom Position slot at priority 100.

Nothing breaks on upgrade. The v3.2 minor migration copies your force_override_sensors, force_override_position, and force_override_min_mode settings into Custom Position slot 5 at priority 100 automatically. If you downgrade, the legacy keys are still present and the old Force Override handler resumes operation.

Migration guide

1. After upgrading to v2.28.0-beta.7 or later, open your cover's options → Custom Positions.
2. Slot 5 should contain your previous trigger sensor and target position at priority 100.
3. The safety semantics are identical: the slot fires outside the time window, bypasses delta gates, and forces an immediate return to the calculated position on release.

service: set_force_override

The adaptive_cover_pro.set_force_override service is deprecated as of v2.28.0-beta.7 and will be removed in a future release. It currently works as a shim that writes Custom Position slot 5 at safety priority and logs a deprecation warning. Replace calls with adaptive_cover_pro.set_custom_position targeting slot 5.

Full documentation

→ Custom Position — Safety Priority