From c985fddb6c8828d885bd2b3137048771eebb9b42 Mon Sep 17 00:00:00 2001 From: Bas Nijholt Date: Sun, 6 Sep 2026 09:27:30 -0700 Subject: [PATCH] Document shared turn-on policy limitations --- docs/advanced/manual-control.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/advanced/manual-control.md b/docs/advanced/manual-control.md index 9732a9e7..84dc5bf3 100644 --- a/docs/advanced/manual-control.md +++ b/docs/advanced/manual-control.md @@ -116,6 +116,8 @@ adaptive_lighting: When enabled, a light that turns on from `off` is only adapted if the state-change context exactly matches the most recent Home Assistant `light.turn_on` context recorded for that light. An unmatched turn-on is marked as manually controlled and left at its reported brightness and color. +Manual-control flags are shared by profiles controlling the same light. Use the same turn-on policy on those profiles; mixed policies can allow an earlier profile to adapt before another marks the light manually controlled. + This is the option to reach for when turning a light on with its local switch (or a native Lutron/Caséta scene) makes Adaptive Lighting override your brightness a moment later, forcing you to set it twice. Its advantage over simply disabling `detect_non_ha_changes` is that the two behaviors are decoupled: you can keep `detect_non_ha_changes: true` to catch manual dimming of lights that are *already on*, while leaving unmatched turn-ons untouched.