Virtual thermostats and presets

I’ve set up multiple generic_thermostats and tried the “Better thermostat” and “dual thermostat”, and for some reason, all needs a predefined temperature value in YAML for presets like “comfort”, “away”, etc… If you don’t enter it, that preset won’t be available.

In my everyday, these preset temperatures can change through the year, and we simply adjust it to the value we want in the UI. If I then however need to restart HASS, they will be reset to whatever I entered in the configuration, which may be completely different than the current value.

Can someone please tell me that i misunderstood something here?

In my head, these integrations should - if anything - have a “preset_away_enable (true/false)” in the configuration, and a hard coded default value at first start. Then the values we adjust it to in the UI survives restarts after that.

This seems to be an old issue

It seems crazy to have to write automations to work around a seemingly minor thing to fix in the source code?

All preset temperature settings should survive restart right?