Replies: 3 comments 1 reply
-
"If you have money and time all is possible." More seriously, I see the idea. Having 12 VTherm my self I know tthat when you need to change something it is a little boring. If someone has the trick, it could be an interesting enhancement. |
Beta Was this translation helpful? Give feedback.
-
I could imagine one would have two integrations or one addon and one integration or something like that? One of these holds the "central" configuration data, the other integration all entities. Yes, this sounds complicated. Maybe we'll discover another integration that helps finding an easy solution. |
Beta Was this translation helpful? Give feedback.
-
I'm not comfortable with addon. What seems possible simply is to have a set a configuration into the configuration.yaml. This set of configuration can be transversal to all Vtherm instances and could be replace the UI configuration set by the user. But, you need a restart each time you change something in it (at least a restart of the integration), through the UI, you will see a value which will not be used. And this is very misleading for the user. So I see no simple and use friendly way to achieve that. Just wait if someone, who read this have a solution. |
Beta Was this translation helpful? Give feedback.
-
Is it technically possible to have a general configuration pane with all variables that are relevant for the entire home and don't change from one room to the other? E.g. external temp sensor, cycle duration, min/max temp allowed, regulation threshold, regulation min period, window sensor delay, temperature decrease threshold, max duration of open window, presence sensor, minimal activation delay, security delay,…
This would drastically reduce the number of options when configuring another climate entity.
Beta Was this translation helpful? Give feedback.
All reactions