@alexsperlingz
No, should work like this. Away temp is set if you leave your home but comfort is set if your in range of 500m and moving towards your home.
//EDIT: Ah, I think. The proximity has no impact here because it only forces the comfort mode. Away temperature is based on comfort temperature.
So if your schedule is on in every case the away temperature is set. If the schedule is off the comfort temperature is set.
This also makes sense since proximity is implemented for some kind of pre heating. But I didn’t tested this case.
@Ohana_Means_family
Set your schedules in the schedule selector (not the schedule selector selector xD) like:
schedule.regular
schedule.night_shift
And if you only switch between those two you can simply add an input boolean as a selector. Off means regular - the first schedule in the list - on for night shift, the 2nd one.
You also can build a binary sensor based on a calendar or even/odd weeknumbers to toggle between them automatically.
Here you can see my schedules - one regular and one for holidays. The Urlaub entity is a binary sensor in this case that enables the Wohnbereich Urlaub Heizplan if its state is on.
Hi there - quite new to the scene here but very excited with what I’m seeing so far.
I have actually setup home assistant at home for improving my heating setup. Before I dive into setting up this blueprint I just wanted to make sure it can handle it for my need.
I currently have Nest thermostats in my home with two separate zone (upstairs and downstairs). Although this has been working fine, I’m looking to improve it by adding smart TVRs where effectively the TVRs would control as to whether the nest thermostat is on or off. I appreciate this would render the nest thermostat redundant. I currently have Nest thermostats and smart TVR showing up as entity under Thermostats/Climates (smart TRV are zigbee device configured via ZigbeetoMQTT).
Could you confirm this blueprint is intended for such scenarios? Apologies if this has been asked in the past. I have tried to search for ‘Nest’ in the trial but didn’t find any relevant hits.
So what about the some temperature trigger? One day that was really cold outside and the temperature drop a lot, I had to manually set to “comfort mode” (preset of the TRV) to start heating. Usually I have it in manual. I have set the comfort temperature at 22.5 and Eco at 19 but on 20.5 room temperature, no trigger.
Do you want to set a single target temperature for the hole heating zone or do you want heat every single room differently?
@fumantsu
I don’t really understand the problem. Can you explain how you configured the blueprint, i.e. what should happen in your eyes and what didn’t work for you? It would also be good if you could share your automation configuration in yaml here.
2 heating zone indeed. In each room, I have several rooms that have a temp sensor and smart TRV.
I want to set a single target temperature for each room differently based on the reading of the temp sensor. Main reason is upstairs i have 3 bedrooms and 1 office. I don’t want to heat up the bedrooms during the day but just the office.
Hope that clarifies and many thanks for your help!
Ok, just create one automation for each room. Stay with the static temperatures or set temperature entities. Set your TRVs (not the nest thermostats), schedules, presence sensors, windows/door sensors ect.
For enabling/disabling heating for all rooms, create a template sensor based on your nest thermostat like:
{{ states('climate.YOUR_NEST_THERMOSTAT') in ['auto','heat'] }}
And set this as your winter mode / on/off entity. Hope this helps. Let me know if you need further help.
@fumantsu
Ok, so you heat to comfort if your schedule is on or your presence entity is enabled.
But the problem is your room heats up to max 20.5° although the comfort mode is enabled and the target temperature is 22.5°C? So the radiator stays cold?
Not really, it doesn’t heat at all if the room temperature is low as 20.5. The schedule is usually to avoid working on night and presence is when someone is on a specific area of the room, so either this or that.
I have also upload an image of the presets (which are TRV internal presets), to clarify the “comfort mode enabled” you said.
I’m checking it. I have it in Auto because of two reasons:
a) System mode
Mode of this device, in the heat mode the TS0601 will remain continuously heating, i.e. it does not regulate to the desired temperature. If you want TRV to properly regulate the temperature you need to use mode auto instead setting the desired temperature.
b) if it is on auto the valve can be half open or 25% etc instead of full open.
Ok noted will try this and report if anything else needed. Just to be sure though. Under Thermostats / Climates, I select all the TRVs AND the Nest Thermostats. However, just to make sure we’re aligned, configuring the schedule for each room will automatically understand that if the TRV in room A requires some heat, then the relevant thermostat will kick in to make sure the boiler pumps hot water into the system?
As I said you can enable/disable all your automations with a binary template sensor based on the nest thermostat. But this isn’t needed.
I am right that your nest thermostat toggles your boiler? But your boiler isn’t integrated as a switch in home assistant, right?
The temperature of your Nest thermostat must be set automatically depending on your TRVs. However, this also means that you no longer have to / can control your Nest thermostat manually.
Indeed - the two nest thermostats toggles the boiler to feed hot water in the upstairs and downstairs pipes respectively. So effectively the downstairs Nest thermostats toggle the boilers for the downstairs area and the upstairs for the upstairs area.
Boiler is NOT integrated as a switch in HA indeed. I have integrated Nest through this integration Google Nest - Home Assistant
Yes that would make the Nest Thermostat as a switch for the boiler effectively and the temperature would be only set on the TRVs. Thinking out loud, we would need to have the nest thermostat switched on by setting a temp higher (e.g. 3 degrees) than what the thermostats reads whenever a TRVs is triggered and stopped (similarly by setting the TRVs at a lower temp that what the thermostat reads) whenever all TRVs are not asking for heating.
So i guess in my situation there’s two complications:
The nest acting as a switch on/off for the boiler instead of a thermostat
the mapping of the TRVs to the relevant nest (upstairs/downstairs)
This template switch should do the trick. Edit your TRVs in the climates array and your nest thermostat in the turn_on / turn_off action part.
What does it do?
It checks the states of your TRVs if any of them is in state heat or auto and the target temperature is higher than the local temperature the Nest climates target temperature is set to 30°C. (this should be the max temperature of your nest climate)
If no TRV hits the condition the hvac state is set to off.
- platform: template
switches:
heating_upstairs:
value_template: >
{% set climates = ['climate.TRV_UPSTAIRS_1',
'climate.TRV_UPSTAIRS_2',
'climate.TRV_UPSTAIRS_3'] %}
{% set heat = climates | expand | selectattr('state','in',['heat','auto']) | list | count > 0 %}
{% set result = namespace(r=none) %}
{% for climate in climates %}
{% if result.r == none %}
{% set result.r = state_attr(climate,'temperature') > state_attr(climate,'current_temperature') %}
{% else %}
{% set result.r = result.r or state_attr(climate,'temperature') > state_attr(climate,'current_temperature') %}
{% endif %}
{% endfor %}
{{ heat and result.r }}
turn_on:
action: climate.set_temperature
data:
hvac_mode: heat
temperature: 30 #max temperature
target:
entity_id: climate.NEST_UPSTAIRS #your nest thermostat
turn_off:
action: climate.set_hvac_mode
target:
entity_id: climate.NEST_UPSTAIRS #your nest thermostat
data:
hvac_mode: off
//EDIT: you also can convert this to an automation so this is easier to enable/disable.
Sure. Heating didn’t help. It was just heat without control. To test I set the comfort temp to 25 to try to trigger (which I didn’t saw from history to happen) and only one trace looks interesting (others are calibrating temperature).
The eco I set it further to 18 just to see in zigbee2mqtt if the temperatures there will change (which not beside current heating setpoint). Also input_boolean? where has to be set this and miss it?
As for the action, yes, it started to heat
