Skip to content

v1.2.3 – Boolean config persistence fix

Choose a tag to compare

@eyalgal eyalgal released this 22 Sep 02:41
1844000

Bugfix: Boolean Fields with True Defaults Now Save false Values Properly

  • Fixed a critical bug where boolean configuration fields with default true values (such as timer_action_turn_off_light, show_volume_buttons, haptic, volume_click_control, and show_battery_percentage) would not persist explicit false values in the card editor.
  • Previously, setting these fields to false in the editor would appear correct in YAML, but upon reopening, the values reverted to true (default).
  • The root cause was that the config cleaning logic deleted any value matching the default, incorrectly removing explicit false values for fields with a default of true.
  • Now, explicit false values are preserved, while true values 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 false values for affected boolean fields are retained and reflected in the editor.
  • Default true values are omitted from the config for cleanliness.
  • Non-boolean fields and other behaviors remain unchanged.

For more details, see the merged PR: #6