5.2.0 - Add central_mode to control all VTherm in one click

[jmcollin78]

Content

1. have global option to start and stop all VTherm automatically - have global option to start and stop all VTherm automatically #158
2. Details of log entry (cosmetic) - Details of log entry (cosmetic) #306 (thanks to HACS-bank)
3. Logbook warning for underlying switch on restart of HA questionable - Logbook warning for underlying switch on restart of HA questionable #307 (thanks to mleibe)

The #158 will allow you to control all VTherm in one click.

Enjoy !

---

This discussion was created from the release 5.2.0 - Add central_mode to control all VTherm in one click.

[MBRetrofit]

I would add a Note because this "Mode" has no any management syncronisation or algorithm as is just a switch and in the event of using electrical heaters, starting all at once could be tricky...

[jmcollin78]

ok but this configuration will not spread across time (or I don't understand it works).

[MBRetrofit]

So in over_climate the algo is different than in over_switch? Doesn't switch off spreading over time the climate's as Vtherm did in over_switch mode?
I did that with a primitive automation. and I have no more than 1,2KW/h with a 7KW electric heaters installed ( mainly because of my outside weather but the idea is to spread the power over time).

[jmcollin78]

So in over_climate the algo is different than in over_switch?

Yes. In over_switch, VTherm is doing the regulation based on power percentage. In over_climate the regulation is done by the underlying climate itself (and VTherm adds a self-regulation based on the target temperature increase if target is not reached)

Doesn't switch off spreading over time the climate's as Vtherm did in over_switch mode?

No. This makes no sense.

I did that with a primitive automation. and I have no more than 1,2KW/h with a 7KW electric heaters installed ( mainly because of my outside weather but the idea is to spread the power over time).

To spread the power over time you have the power management feature. Basically VTherm checks that a reserve of power is available before turning on a heater. That will do (or mitigate) the risk of overpowering.

[MBRetrofit]

Uff, I am not talking about overpowering. The overpowering routine is very nice and works flowless. Your regulation switch one by one the heaters from power percentage less then 50%.

I would like to have that for all house but every room with own temperature sensor not one sensor for all house.
Can you tell me where is the code for this:
''If several type entities are configured, the thermostat shifts the activations in order to minimize the number of switches active at a time t. This allows for better power distribution since each radiator will turn on in turn.''

[jmcollin78]

Hello @MBRetrofit,

It will be very difficult (not possible simply) to have a transversal optimisation between VTherm. There is nothing running which can take this feature and control the VTherm. The central configuration is not a VTherm but only an empty shell.

The code is located in the start_cycle method, called by BaseThermostat.async_control_heating here:

for under in self._underlyings:
            await under.start_cycle(
                self._hvac_mode,
                self._prop_algorithm.on_time_sec if self._prop_algorithm else None,
                self._prop_algorithm.off_time_sec if self._prop_algorithm else None,
                self._prop_algorithm.on_percent if self._prop_algorithm else None,
                force,
            )

The implementation of start_cycle is done in underlyings.py for the Class UnderlyingSwitch at line 176. It uses an initial_dely_sec which is calculated in ThermostatOverSwitch at line 103 of thermostat_switch.py file.

But you have only the control on the underlyings of the current thermostat, once again.

[MBRetrofit]

I would articulate more the On/Off time attributes and I would change the "price" with some any type of room priority's within the ''Recuit simulé algo.

Anyhow, I learn a lot from you, thank you!