Skip to content

v1.0.13

Latest

Choose a tag to compare

@f17mkx f17mkx released this 23 May 07:55
  • 🐛 fix(v1.0.13) mode: temperature works 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 (a light.all member with mode: temperature inside light.main's manual_members also rendered brightness). Root cause: the host card's group-branch (everyday-light-card.ts ~line 1721) dispatched to <everyday-group-layout-expanded> without threading cfg.mode through, so the component's compact-slider mode + member-slider mode always defaulted to 'brightness' regardless of config.
  • 🔧 fix(v1.0.13) new defaultMode prop 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) now deletes the runtime mode-entry instead of writing 'brightness', so a configured defaultMode: temperature re-takes after the light is power-cycled (unless slider.persistent_mode: true keeps 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.