Hey, thanks for your feedback. The version of the blueprint is missing. It looks like you are using v4 atm. You should migrate your automation to v5 at first. Thanks!
Hi,
thanks for the great Blueprint.
I was using version 4 and have now switched to version 5. I have deleted all automations from V4, deleted the script and downloaded version 5 again.
Unfortunately, nothing is changed anymore. I have created a simple automation, a thermostat and no other sensors. But nothing happens.
What could be the reason for this?
I also entered additional sensors once, but it didn’t work there either.
Here is the TraceFile:
https://controlc.com/30aa5083
Thx Herbert
Thanks for your feedback. I don’t know what you want to achieve. If you just set a thermostat only the calibration will work.
The automation is designed to switch temperatures and modes based on people, schedules, presence, proximity, windows ect.
Without any of that entities no logic gets evaluated and executed.
At least you should add a schedule for example.
hi @panhans,
first of all thanks for the blueprint. I have switched to new version but i have problems with the Party Mode, when the timers or the booleans come on the thermostat not change to “heat” and it keeps its status to “off”.
Here you have the trace (https://controlc.com/d065ea8a) when the timer/boolean entity goes on:
mode: eco
automation: automation.aire_salon_calor_2
is_person_defined: true
is_anybody_home: true
is_proximity_defined: false
is_anybody_home_or_proximity: true
is_guest_mode: false
active_scheduler: schedule.festivos_aire
state_scheduler: false
state_presence_sensor: false
state_presence_scheduler: false
state_presence: false
state_proximity_arrived: false
state_proximity_way_home: false
is_force_max_temperature: false
active_party_entity: timer.precalentamiento
party_temp: null
is_away: false
state_window: false
is_aggressive_mode: false
is_frost_protection: false
is_liming_protection: false
state_outside_temp: true
entry_time: ''
hvac_mode: 'off'
temperature_comfort: 21.5
temperature_eco: 19
target_temperature: 21.5
set_max_temperature: false
last_trigger_id: temperature_change_party_on
calibration_trigger: false
change_trigger: false
warnings: false
In the v4 the Party mode runs without problems. is there any new condition to party mode?
Thanks in advance!
1 Like
Hi,
okay. I I thought it should work for now without any more, as I have problems with more sensors.
I have now added some sensors.
Shouldn’t it now be the case that when the external room sensor has reached the comfort temperature, the heating is turned down?
That doesn’t happen for me.
Here are the new trace: https://controlc.com/21d81b1f
Regards
Herbert
Hello, first of all I would like to thank you for the great work! Keep it up… I have been using the tool for a while, but what I miss, or perhaps haven’t found yet, is an option for an ECO switch! So if the valve is set to comfort, you can use this function to switch it to ECO (for example, using a switch). Basically like the party switch, only the other way around! Thanks and best wishes…
1 Like
Thanks for reporting. Indeed there was an issue. Just update the blueprint and have a test again.
@Markus1971a
You can set a party input boolean named like “Eco Mode 18”. If enabled the automation forces the TRVs to the desired temperature at the end of you boolean entity name.
@herbert1910
I will have a look into this. But for now changes only be done if there is a schedule, guest mode entity, presence sensor or proximity. If you don’t want any changes, you could setup a empty schedule or a guest mode entity that is always off. Never mind: Could you tell me the version you’re using?
//EDIT: if you want the thermostat to turn off when room temp is reached you have to enable Off If Above/Below Room Temperature. But keep in mind that every thermostat close the valve if this is the case. It’s implemented for A/Cs originally.
Hi,
i have a short question to the heating adjustment. Normaly i have a eco-temp of about 16. Its set with a sheduler during the night and the day. During the day i want to set it to 18. Is it enough to set it like this:
- time: “07:30”
eco: “18”
calibration: “on”
The question is now, will the automation, in form of the sheduler, set it back to 16 when its triggered again or is it neccessary to set it back to 16 in the evening with the heating adjustment?
1 Like
If in the meantime comfort is triggered and you’ve enabled reset temperature this should work.
But I would recommend to set it in the adjustments as well.
ok, yep comfort is triggered at 3 PM, so i will try both :)…
1 Like
Now works perfectly, thanks for the quick fix 
.
1 Like
@panhans I just notice that the link at the aggressive calibration info seems outdated (https://community.home-assistant.io/t/advanced-heating-control) - adding a “/” at the end should do the trick.
Also, I seem to struggly completely with the calibration options. Is there a guide on how to set this up?
I have basically 2 issues:
1 is for my burner, which I would like to be hotter (or colder) depending on the average temperature of multiple radiators (I have set up the avg temp correctly now and it is accepted as an input), but offset is always the max (i.e. temperature set is 23, avt temp is 22.4, generic calibration sets temperature to 28 with +5C° max).
For my other rooms, the thermostats have integrated temperature measurements (current temperature) but they don’t do a great job getting to the target temperature. Should I set the integrated current_temperature sensor as the Room temperature sensor? Generic calibration does not seem to work for me, then (either with this, or without a room temperature sensor set). If I set a true external sensor, calibration starts working).
I must have the concept wrong
Hey Guys,
im pretty new in the Blueprint and HA Game.
Do someone have problem with this blueprint using the tado x thermostates or am I just the stupid one? ^^
Hey Guys, @panhans
I use this great blueprint with my HomeaticIP TRVs and it works fine.
Sorry, but I don’t know, how I can get the current used blueprint version.
Can you document the current used version of the blueprint in the codesnippet?
snippets/ahc_template_sensor.yaml
So I can compare the server version (snippets/ahc_version_sensor.yaml) with the current version
and I can display an alert-icon, if it is diffrent.
could be but is there a way to not “hardcode” the temp and use instead a input_number?
This might be a stupid question, but do I need to set up multiple automations of this for the different seasons? To clarify, my house has heating and cooling (controlled through the same thermostat) but the modes are changed depending on the season:
- In the summer, the HVAC mode is set to “Cool” (to prevent the furnace from kicking in)
- In the winter, the HVAC mode is set to “Heat” (to prevent the AC from kicking in - it would damage the AC unit itself if the blower kicks in when filled with snow)
- In the fall/spring, the HVAC mode is typically set to “Heat/Cool” (or “Auto”) depending on the outdoor temperature
My largest concern is making sure the automation does not accidentally turn on the AC in the winter or heat in the summer.
Hi,
I just updated from 5.0.7 to version 5.0.9 after noticing an issue so I don’t know if this version has it fixed. I just went out of the house and came back after a while and almost all of my radiators were turned off. The thing is, both my wife and me are being set to all blueprints as persons so to my understanding while anyone of us is at home the TRVs should have remained turned on. In reality only the ones my wife was the only person set remained on while all the others were turned off only because of me leaving. I was looking for some changelog on the micro version but couldn’t find what was changed and if this got fixed in the meantime. Or is this still an issue maybe?