Added heating.circuits.N.operating.modes.cooling

[bekra00]

Added heating.circuits.N.operating.modes.cooling
to the PyViCareHeating Device and setup testing

[CFenner]

This can already be retrieved with getActiveMode(), not as a bool, but I think you get the idea. Do you still think we need a dedicated function for that?

[bekra00]

By getActiveMode(), I receive dhwAndHeatingCooling or heating, but not if in this moment it operates in cooling.

getActiveMode() -> heating.circuits.N.operating.modes.active
Shows current active operating mode on the device and provides command to change it.

getCoolingActive() -> heating.circuits.N.operating.modes.cooling
Shows whether the cooling operating mode is active now.

So it can be the case, that if the operation mode is set to dhwAndHeatingCooling, cooling is on or off. Therefore it does not provide the same information.

I want to use this value to open the zone valves.

[CFenner]

Ok, then would it make sense to expose heating as well?

[bekra00]

In general yes - not for my use case but it make sense

[lackas]

heating.circuits.N.operating.modes.cooling is device-dependent. Where cooling is a directly selectable mode it flips active: true, but where the operating mode is an umbrella (dhwAndHeatingCooling / heatingCooling) and the pump decides heating vs cooling itself, operating.modes.cooling.active stays false even while cooling runs. I verified this on a Vitocal 300-G (CU401B) doing natural cooling: the buffer dropped from 42 to 19 °C while that flag stayed false, so getCoolingActive() would report the opposite of reality there.

So this works for some setups but not all. Might be worth naming it after what it actually reads (the configured cooling mode) rather than "active", and documenting the scope. Background in #746.

[CFenner]

👍