- 🐛 fix(v1.0.13)
mode: temperatureworks on groups + nested groups: Stefan-Quote 2026-05-21: standalone single-light config[entity: light.hall_spot_1, mode: temperature]rendered the temperature slider correctly, but the equivalent config on a group entity ([entity: light.all, mode: temperature, group: { layout: compact }]) silently fell back to brightness. Same regression hit nested-group members (alight.allmember withmode: temperatureinsidelight.main'smanual_membersalso rendered brightness). Root cause: the host card's group-branch (everyday-light-card.ts~line 1721) dispatched to<everyday-group-layout-expanded>without threadingcfg.modethrough, so the component's compact-slider mode + member-slider mode always defaulted to'brightness'regardless of config. - 🔧 fix(v1.0.13) new
defaultModeprop on<everyday-group-layout-expanded>+ new_currentMode(id)resolver: precedence is_memberModes[id](user-driven picker choice) →defaultMode(host config) →'brightness'. The four slider-render and picker-indicator sites + cycle/toggle/auto-revert comparison sites now read via the helper so the configured mode is honored uniformly. Off→on auto-revert (line ~1027) nowdeletes the runtime mode-entry instead of writing'brightness', so a configureddefaultMode: temperaturere-takes after the light is power-cycled (unlessslider.persistent_mode: truekeeps the last-picked mode). - 🧪 test 172/172 pass unchanged - the fix touches the render-time resolution chain which is exercised by manual Stefan-verify on HA.
- 🔧 ops VERSION bump 1.0.12 → 1.0.13.
Build: clean. Tests: 172/172. Backwards compatible: cards without an explicit mode config keep their pre-fix behavior (brightness default + _memberModes picker overrides). Affected configs: any group-entity card with a top-level mode: temperature (or any non-brightness mode) - these previously rendered brightness; now render the configured mode on first paint.