Upgrade "preset" temp modifications from UI

[mcornillon]

Hi @jmcollin78

Current situation :

• today, if I double tap on a preset, it retrieves the current target, and memorizes it for the preset
• it seems to only be stored in the UI, not in the VTherm configuration
• if a HA restart is performed, the "stored preset temp" is lost (see Preset temperature problems #39 )

Issue :

• it is easy to make an "undesired" double tap when on a mobile tactile interface, I would like to be able to change it to "long press" to avoid this (especially when kids or wife play with this)
• i would like that the new stored preset temp be fully applied to the VTherm & memorized beyond an HA restart

Future (desired) situation :

• default the action to "long press" instead of "double tap"
• (optional) in the UI configuration, give the user the ability to choose between "do nothing" / "double tap" / "long press"
• apply the new preset temp to the VTherm instance

Thanks ! :)

[jmcollin78]

Hello,

Preset temperatures are now independent entities in VTherm.

This temporary feature with is not persistent and should be removed in my opinion. It has been done before having the independent entities in VTherm. In your dashboard, you just have to expose you preset entities to be able to be able to change it.

Here is how I do personally:

[mcornillon]

OK, I agree with your explanation that now "preset temps" are independent, and so should be configured externally, as you did it personally, that's real fine for me : It is a good thing to setup another UI to modify them.

BUT it adds +1 point to my arguments : then, as they are now independent entities, they should not be modifiable at all by the vtherm ui card ? instead of replacing the "double tap" by "long press" as I suggested, you could add an option to simply "deactivate" this possibility ? so that we are sure that a user can ONLY modify the preset temps via the dedicated UI we setup elsewhere (as you did).

Am I wrong ? did I understand well you answer ? If no, don't hesitate to reply (in French if it helps, just running in English for the sake of the whole Github international audience :p)

[jmcollin78]

then, as they are now independent entities, they should not be modifiable at all by the vtherm ui card ?

Yes I will remove that. As I said it was a temporary solution while waiting for the new entities.

[mcornillon]

OK great, I did not get that you did it as a "temporary" solution, good to know you will remove it

[jmcollin78]

Let say it is now obsolete.