Leonhard Hesse aa84eda871 feat: add expand_light_groups option (#1462) ... * feat: add expand_light_groups option Some light group entities act as a proxy that must receive a single combined `light.turn_on` call to function correctly — virtual mixers like <https://github.com/mion00/color-temperature-light-mixer> for instance, that blend a warm and a cold white channel into one entity. In such setups the individual member entities only expose `ColorMode.BRIGHTNESS`, so sending separate per-member commands bypasses the mixing logic. Setting `expand_light_groups: false` keeps the group entity in `self.lights` instead of expanding it to its members. Adaptation commands go to the group, and the interceptor no longer skips group entities for that switch. Default is `true` — no behaviour change for existing configurations. * tests: regression test for expand_light_groups=False _switches_with_lights was expanding the incoming entity_id globally, causing the switch to never be found when expand_light_groups=False * Resolve group targets consistently across adaptation paths * Discard delayed group events after target changes * Stabilize delayed group target regression test --------- Co-authored-by: Bas Nijholt <bas@nijho.lt>		2026-09-06 21:13:35 +02:00
..
brightness-modes.md	Migrate to markdown-code-runner's built-in include_section() (#1417)	2026-01-26 09:01:50 +01:00
manual-control.md	feat: add expand_light_groups option (#1462)	2026-09-06 21:13:35 +02:00
sleep-mode.md	Add documentation site with Zensical framework (#1385)	2026-01-12 23:39:57 +01:00