classic+ feature: day/night/solarized theme presets with schedule-based auto-switching #5

New issue

Open

opened 2026-07-12 22:31:21 -07:00 by pyr0ball · 0 comments

pyr0ball commented

2026-07-12 22:31:21 -07:00

Owner

Gap: UI currently has one fixed dark theme, no theme options, no time-based switching.

Ask (2026-07-12): multiple theme presets (day/night/solarized at minimum), with timing configurable from the Schedule page (page_schedule) so the display can auto-switch (e.g. lighter/day theme during daytime hours, darker/night theme after sunset) rather than requiring manual toggling.

Scope questions to resolve during design:

Theme switching mechanism: swap LVGL style properties (colors) at runtime vs. separate compiled pages — runtime style swap is almost certainly the right approach (no need for parallel widget trees).
Timing source: fixed clock-based schedule (needs the still-deferred live time: component, currently a static placeholder clock) vs. HA sun/sunset entity vs. simple user-set hour range.
Does this apply to classic (faithful Lennox replica — real device may or may not support this, check reference material) or classic+ only, or both?

Related: Dial and color theme refinement issue — if that ships first, its palette becomes one of these presets.

**Gap:** UI currently has one fixed dark theme, no theme options, no time-based switching. **Ask (2026-07-12):** multiple theme presets (day/night/solarized at minimum), with timing configurable from the Schedule page (`page_schedule`) so the display can auto-switch (e.g. lighter/day theme during daytime hours, darker/night theme after sunset) rather than requiring manual toggling. **Scope questions to resolve during design:** - Theme switching mechanism: swap LVGL style properties (colors) at runtime vs. separate compiled pages — runtime style swap is almost certainly the right approach (no need for parallel widget trees). - Timing source: fixed clock-based schedule (needs the still-deferred live `time:` component, currently a static placeholder clock) vs. HA sun/sunset entity vs. simple user-set hour range. - Does this apply to classic (faithful Lennox replica — real device may or may not support this, check reference material) or classic+ only, or both? Related: [[Dial and color theme refinement]] issue — if that ships first, its palette becomes one of these presets.

No labels

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: Circuit-Forge/firecrest#5

No description provided.