v1.2.3 – Boolean config persistence fix
Bugfix: Boolean Fields with True Defaults Now Save false Values Properly
- Fixed a critical bug where boolean configuration fields with default
truevalues (such astimer_action_turn_off_light,show_volume_buttons,haptic,volume_click_control, andshow_battery_percentage) would not persist explicitfalsevalues in the card editor. - Previously, setting these fields to
falsein the editor would appear correct in YAML, but upon reopening, the values reverted totrue(default). - The root cause was that the config cleaning logic deleted any value matching the default, incorrectly removing explicit
falsevalues for fields with a default oftrue. - Now, explicit
falsevalues are preserved, whiletruevalues are cleaned from the config (using the default). - The editor now accurately reflects and saves your intended settings for these fields.
Summary of Fix
- Explicit
falsevalues for affected boolean fields are retained and reflected in the editor. - Default
truevalues are omitted from the config for cleanliness. - Non-boolean fields and other behaviors remain unchanged.
For more details, see the merged PR: #6