Make the temperature preset persistent entities

[jmcollin78]

Changing a temperature preset should be simplier.

We could add some entities as domain number which can be changed easily in the VTherm and can be directly set into dabshboard.

Then we can remove the configuration presets which will simplify the configuration.
As a general way, keep configuration which change rarely into the configuration panel and add persistent configuration entities for each parameters which can be modified. Target temperature is the good example.

[jmcollin78]

Be careful to the migration: how to keep the configured values.

Should we remove the central configuration for preset temperature as well ? Or just init the values of the new entities with the central configuration values ? Then we lost the diffusion of changing a central configuration to all VTherm.

[gunmalmg]

This would be awesome 👏
I think your suggestion is really good. Create Presets as Entities under the VT Device.
For the "migration: how to keep the configured values" I think your suggestion is good : Fill the new preset entities with the preset values from the Configuration/central configuration - and then remove the presets from the Configuration.
From that on - we will change the presets in the UI by changing the preset-entities.
👍

[jmcollin78]

Thank you for your feedback, I was pretty sure, you will be interested 😉

[HACS-bank]

If it is easier during migration to leave the config in place, then perhaps the config values become "initial value" used until someone changed them.

This might allow newly defined VTherms to have a value before the user defines a UI for changing values, and covers the scenario where a VTherm exists without a UI.

[gunmalmg]

I'm really looking forward to this enhancement :-)

I'm planning a UI like this as i short list for all my climate entities on each floor(and one for the whole house). I have many climate entities and I need a place to get quick glance over them all. Its not usable to have to maneuver through many "room" cards for this.
In this way I can get a quick glance over the temperatures and preset-states of every entity.
And the ability to quickly change preset-mode on many entities.

And when you have made the preset-temperatures an alterable entity in the UI, I will be able to enhance my “card” with a “Hold-action” over the preset-mode buttons to let the user alter the preset temps right there.
That is a user-friendly UI :-) I think.
👍

[maia]

I'm planning a UI like this as i short list for all my climate entities on each floor(and one for the whole house). I have many climate entities and I need a place to get quick glance over them all. Its not usable to have to maneuver through many "room" cards for this. In this way I can get a quick glance over the temperatures and preset-states of every entity. And the ability to quickly change preset-mode on many entities.

Oh that's great, can you please share how you managed to create that UI? I was trying a super-compact layout as well but gave up. This here is what I managed using multiple-entity-row, but the icons did not change state depending on the selected preset, and that was rather unusable.

[jmcollin78]

@gunmalmg

I love your card and the compacity. Maybe an idea for a future UI card given out of the box by the VersatileThermostat UI Card. I will keep that in my TODO list, if you agree with that.

jmcollin78/versatile-thermostat-ui-card#27

[jmcollin78]

On the development of this feature itself, it is finally very complex and I'm running into race conditions:

1. temp entities should be initialized before VTherm climate (because VTherm need them),
2. but temp entities itself relies on VTherm configuration itself (to see if central configuration is used),
3. When central configuration is used, the Central VTherm should be initialized before all others.

So it is a nightmare to have all initialized depending on all configuration options. 😮‍💨