#Generic thermostat in each room and actuators

1 messages · Page 1 of 1 (latest)

cloud sluice
#

Hello,
I'm wondering what is the best practice to manage generic thermostat helper when you have multiple rooms and a heather switch.

Context:

One temperature sensor for each room.
2 rooms have a tvr actuator
2 rooms don't have actuator
1 general thermostat switch

To avoid conflicts i tryied to add an input boolean helper to generate a "heat request" binary sensor that would activate the heather relay with an automation. Unfortunately the generic thermostat helper only manages real switches so I can't use the helper bolean with an automation that triggers it on when any generic thermostat is in heating mode.

What would be the best practice to manage this common situation?

Consider the generic thermostat works with the actuator but it should first check if the heater switch is on or off.

If I select the same real thermostat switch for each generic thermostat, I get a conflict.

Thank you

dim relic
#

Could you use a template switch in your generic climate control

tawdry mango
#

I am almost sure you can use the input_boolean as your heater value.

tawdry mango
#

I can share my setup if you find any inspiration here. I have 4 heating zones (with TRVs) and one main switch to enable flow of hot water in the apartment. My main valve is like your heater.

The way it is done is that the TRVs are in heat mode and when in this mode, they can be in heating or idle status. heating meaning "TRV valve is open*.

I then have a sensor that counts how many TRVs are in the heating state and if value is greater than 0, I turn on the main valve, else turn it off.

Now, you could replace the heating state with the input boolean. Boolean is managed by the switch and you can do the rest similar way I did.

sturdy rover
#

My setup incase someone finds it interesting: Standard UK home with a combi boiler. I have a Hive thermostat. 3 TRVs. I do not however bother with them and just stick them at 22C, the upper range for a temp I’d like in any room. I have temp sensors in basically every room (5 bed house) and have a template sensor which is set to the coldest temp. This coldest temp users all the “important” rooms: bedrooms, living room, kitchen. If the coldest temp is below a set threshold it triggers a Hive “boost” which basically cranks the boiler for an hour or the boost is cancelled. There’s other conditions to boosting: someone is home, the calendar is set to “daytime, you get the idea. Those centralised wall thermostats are useless, but using any random temp sensor to trigger heat works quite well for us. Hive is an odd system but I’m sure the idea could be adapted.

cloud sluice
cloud sluice
tawdry mango
#

hmm, then template switch is the right for you.

cloud sluice
cloud sluice
tawdry mango
#

you don't need much for template switch. You just need to encapsulate the toggle helper:

  1. Create a toggle helper, that will generate the input_boolean.xxx entity
  2. Create a template switch and for state add the: {{ states('input_boolean.xxx') }}, for turn_on action add the input boolean turn on command and for turn_off action add the input boolean off command.

This template switch should generate the switch.xxxxx entity and you use this for your heater

#

then in automations you can trigger or check the input_boolean.xxxx entity and do the rest

next osprey
cloud sluice
# tawdry mango you don't need much for template switch. You just need to encapsulate the toggle...

I was thinking about this solution but i might get it wrong. Why should be a difference with the actual behaviour if any generic thermostat is going to work on the same input boolean?
The logic should instead check if there's any other generic thermostat asking for heat before turning the warm request off (general thermostat).
I found that the new domain automation has something similar where you can set a certain automation to happen when *first, *last or *any device of a certain domain (or group) is changing state.
Shall this be a good way to go?