Schedules supports custom attributes but they arenāt configureable using the UI atm. Itās possible to solve this with the custom schedule integration.
Keep in mind if youāre using the heating plan you default comfort entity will be set. So donāt use it in the adjustments.
@kitus
Could you try to disable physical change? Itās just a guess. What exactly is a.H. Jan and a.h. Pol? A tracelog of the moment when the temperature changes back would be helpful.
@Mar1us
You have to set the schedules you want to chose from in your configuration as well.
@thedju Sorry could you explain your problem again?
@david.jirovec Hey, yould you explain to me what exactly doesnāt work for you? Maybe itās better to open an issue in my github.Iām losing track a bit here.
Iām getting some bizarre swings in current temperature from a couple of my rooms, causing the heating to fire or not when the temperature is just fine. Hereās one of the charts showing current temperature jumping from 12°C to 25+°C then back to actual room temperature. The chart includes the room presence and the temperature device the room heating is measuring from (the reddish line).
It often does this for a while then settles down, sometimes not. Itās a Tado system and if I check the Tado app, the current temperatures match what Home Assistant is telling me and the offset in Tado seems quite large. Iām wondering if this is a calibration issue?
Does this work for heat/AC simultaneously, and if so how would I configure that?
I currently have a nest thermostat, which letās me set both heat/cool within a range. Heat will turn on when temp drops below 68, and AC will turn on when temp exceeds 78.
Itās not clear to me if this even allows for cooling. Can you confirm? If not, the title and this are confusing āroom based heating / based onā
I was wondering if there is a way to shut down rooms if they havenāt had any motion? or the best way to achieve something similar.
If everyone is down stairs most of the day or if its a weekend can I shutdown the heating in the office upstairs, but then if there is motion restart it?
Would it be possible to have an option to set the transmitted temperature setpoint for the liming protection?
I had the case where the setpoint of the thermostat was set back correctly after one minute (and it was reflected correctly in Home Assistant), but it seems like it was not transmitted to the actual TRV via Zigbee, so it stayed heating at maximum temperature.
OK apologies for the scattered approach. Will try to re-explain as best as I can
Hereās the equipment I have:
two nest thermostats one for each floor. The āDownstairsā thermostat controls flow of hot water into the whole system for the radiators on the ground floor of the house. The āUpstairsā theremostat controls the rad in the upstairs.
Smart thermostats (TRVZB)
Temp sensors (SNZB-02D)
For each room upstairs (4 rooms) I have installed a temp sensor and a smart TRV. At the moment, only the āUpstairs Nest Thermostatā controls whether hot water flows through the pipe and I would like to change this by having HomeAssistant controlling the flow to each radiator in each room independently. The āNest Upstairs Thermostatā would then become an on/off switch effectively and itās position becomes completely moot.
From our previous discussion, what i understood was that I need one automation using the blueprint for each room upstairs whereby the thermostats/climates is effectively the TRV of that room and where the room temperature sensors is effectively the SNZB-02D for the given room. I think for that part i can take the blueprint off the shelve. However, to make the boiler on/off switch whenever a TRV is on heat mode you kindly suggested the following code:
- 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
My question is quite basic⦠and apologies for this. Where do I insert that bloc. Do I append this at the yaml generated by the blueprint for each room I am setting up for?
Many many thanks again for all your precious time and help.
This is a fantastic Blueprint but I had a question as I wasnāt sure what my optimum way to set this up would be, but I really need to get away from my old simple node red config that I made. When I went to set this up to at least be similar to my current config I ran into a potential issue or maybe could be a suggestion if I just missed it.
I am using a HA Helper and taking the average of multiple temperature sensors in the room. This mostly due to size of the room and one sensor being close to where we are vs say one by the door. Is there a way to use a helper / or multiple sensors in the same room to create that average? Then make that room the target for specific period of time. Say if I used 70F as my target temp, after 9pm, it will run the HVAC until the sensors in that room avg to 70F. Just myself and wife so not super worried about other rooms being drastically different.
Currently I am looking to generally target 2 rooms. 6a-9pm Living Room and then 9p-6a Master Bedroom. I am using Node Red and then the Avg of each room and a time range to turn on/off.
I feel your blueprint will massively allow me to open this up and account for things like vacation / party modes but looking for suggestions on how I should set it up in my particular case to get started. If there is a RTFM section I missed feel free to kindly point me in that direction as well.
I should also mention I have and still reading though everything. I am seeing the Off If above/below temp which is most likely what I will need to start with but still wondering about the sensors if there is a way to group them / make rooms etc.
One more edit, I think I am on the right path but please let me know if there are better ways. Appears I need to make an automation for each (like I did with node red). So Set HVAC to Cool, Pick a sensor (for now Ill use the most central in the room), add a schedule, and then set comfort temp and the On/Off if above/below? And then from there I can start playing with the other settings, party mode / presenence etc. But also another question is since temps are super wild here, I do see the outside variance would I use that so summer it always stays cool and wont trigger heat and then if falls outside that then heat can be used it if it meets the req? At night we like a cooler room so even if the room drops to low 60s we are ok with that and wouldnt want heat on or should I just make that the trigger to turn on heat?
OK after a lot of stumbling and research I think I got it. Since in TX currently days are high enough to require Cooling so I set schedules, targeted the sensor in the room for each automation. I made one Heating Automation to see if I got it right, I used the additional Outside temperature threshold so when its low overnight it will turn on. So I think I got that right lol I am for sure interested to hear thoughts esp on use of combined temperature sensors.
Is there any way to make the manual temperature changes against schedule temporary? For example now schedule says 21, I change to 23, it stays 23 until next scheduled change. I would like something like: schedule says 21, I change to 23, but after one hour temperature is automatically changed back to 21.
Bug:
When the thermostat is switched off by the outside temperature sensor or weather entity, and the thermostats are set to go to a low temperature instead of off, this triggers the physical change detection and saves the low temperature as preset value.
I have a question regarding the calibration feature.
So far, I have enabled the generic calibration option with a 5 degree offset. So I think the blueprint didnāt calibrate anything. And I calibrated my thermostat myself by measuring the difference between the temperature of the thermostat and the temperature at a specific location. So, so far, I have had a fixed calibration.
But now I am thinking about using the calibration of the blueprint and I have a question regarding my setup:
Iām using 2 thermostats for a big living room
In this room I have 3 temperature sensors (2 motion sensors and 1 humidity+temperature sensor) and the 2 temperature sensors of the thermostats
I have grouped all 5 temperature sensors (3 dedicated + 2 from the thermostats) together for a āroom temperature sensor helperā
Iām using this helper / group for the automation as a room sensor
Now my question: Is it smart to have the temperature sensors of the thermostats inside the group? Or is the calibration error-prone because the thermostats are basically calibrating themselves to small part (1 of 5)?
I am new to HA and have just set up all my home automation devices.
I have Tado radiator thermostats that I want to control with this blueprint.
I configured some Aqara window sensors so that when the windows are open, the Tado thermostats turn off and turn back on when the windows are closed.
Turning them off with this blueprint works really well, but they stay off when the windows are closed again.
Features heating cooling based on people presence, multiple schedulers, presence sensor proximity aka geo fencing, away temperature offset, frost ⦠Iād recommend creating all of your heaters (and corresponding temp sensors) as generic thermostats . This will human benchmark allow you to use all of home assistants built in All dayā or āOnceā, means the heating will switch on at the first āonā setting you have programmed and then remain on until the last āoffā setting of the day. āBoostā or 1hrā switches the heating on for a one hour āboostā of heat. 'Advance
hi!
I wanted to ask if there is a holiday functionality?
Something i can set globally to āonā and a specific temperature will be set? kind of like the āwinter modeā but not offā¦
The away Mode seems like the closest but do i manually need to set the away modes on each device?
i use a shedule selector to set different schedules (normal, away, holiday), so try to use different shedules for different situations!
The active shedule in the shedule selector can also be set outside the automation!
For holidays i combined it with the calendar, if the calendar says āholidayā the selector is set to holiday otherwise it is set to ānormalā!