Replies: 3 comments 2 replies
This comment was marked as off-topic.
This comment was marked as off-topic.
|
Hello, I'm looking for a similar solution. I haven't found a native option to link the valve movement to a pump or boiler state yet. My heating system shuts down the pump during night mode or while preparing domestic hot water. In these periods it makes no sense for the TRVs to adjust or for the TPI algorithm to keep "learning," as there is no thermal energy being delivered to the radiators/underfloor heating. My main concerns are:
To make this feature truly versatile, I think we should have two different options/actions triggered by an external entity:
Allowing us to assign an entity (like binary_sensor.heating_pump or sensor.boiler_status) to these behaviors would be a game changer. That being said, I want to emphasize that Versatile Thermostat is doing an amazing job otherwise! |
I understand your point but there is a major issue: the boiler state is controlled by the position of the valve. So the valve needs to move before the central boiler will be activated. |
Uh oh!
There was an error while loading. Please reload this page.
Hi,
First, I want to thank the developpers for their work on this, it's a great tool that I've been using all this winter.
I'm not sure if this has benn already discussed, but I notice that even if the boiler is not sending hot water to the radiators (because the minimum number of nb_device_active_for_boiler has not been reached) the valves will action an move.
For example, if I enter the room and there is pressence detected, the target temperature of the room will adjust (as expected) but the valves will move also, even if the room temperature is still above target or if the nb_device_active_for_boiler is below threshold.
I think that optimizing the valve movement to only when there is need to actually heat the room, will save batteries in the valves, but also remove the anoying sound of the valves moving each time I enter a room XD.
Thanks!
All reactions