That’s why you need a 2nd sensor next to your thermostat.
Then i will try with aggressive mode and manual calibration. Currently i change it if its warm enough but still heating.
Hi @panhans,
I just wanted to get back to say that all Danfoss issues are now gone by me. After the update you mentioned there were still some small hiccups, but after some subsequent update they disappeared and now it’s all OK.
Now I’, going to buy you some coffee :-).
And I would suggest everybody who you helped should do the same – if a friend came to your house and debugged your heating, wouldn’t you at least buy them a coffee?
Thanks again, pal!
2 Likes
I would totally sign that. @panhans is taking care of every little problem or questions I have had. If its perfectly working or not (on my end it is), this project is totally worth it. I’ll also be refilling the coffee soon.
1 Like
edited: problem sat in front of screen 
1 Like
So after a lot of “try and error” and understanding at least a bit more i managed to fix the calibration issue (it seems so far). I had to modify the zha quirk for my thermostat.
I have _TZE200_h4cgnbzg and _TZE200_yw7cahqs devices and using this quirk (trv_saswell.py)
What i did you can read here (another user with a similar question for this device):
But after a few hours i already see the calibration and offset values finaly match and are in the range the device can handle. Not sure it’s the most elegant solution and not sure it has no side effects i don’t discovered yet 
At least i got sensible calibration / offset values between 0 and -2 now and no extremes like -20°C (instead of -2.0°C) anymore. Still not sure the device itself doesn’t mess it up with internal calibration functions. The AHC v4 blueprint seems to work fine so far. Fingers crossed 
1 Like
Advanced Heating Control v4 RC1 Hey, guys!
I will update the test version of v4 now. This is the first release candidate. But there are some breaking changes:
- this version supports the new proximity integration. You don’t need to select an entity for this. Just define some persons, select them in your proximity service and select the zone of your proximity service
- some tweaks and options got some new selectors in order to bring more structure in this mess of UI. I recommend to resetup your automations. At least you have to tick your tweaks and options again. Sorry for this!
Thank for your help, debugging and making this piece of blueprint reliable for everyone.
It feels like a fight against standards and faulty devices. But the main thing is that it works in the end and your apartments are warm and maybe you save a little money, too.
3 Likes
UI is much nicer/ understandable now.
Only for heating plan (i use scheduler) the optional options are not clear from the example.
I had to look twice to recognice the eco leaf icon with this lines arount on dark BG.
Maybe the little 2-leaf-plant is easier to spot.
1 Like
Thanks for the ideas. I will check this.
Heating Plan / Adjustments will get a little overhaul next:
- multiple day filter
- scheduler filter
- comfort temp setter
- eco temp setter
1 Like
can you add switch for extarnal boiler etc. i am using sonoff thermostats my rooms i have dry contact on my combi and i have sonoff trvbz on my radiators. i want to use which room needs head trigger dry contact switch and all rooms is get heat dry contact off
You want to turn on the switch if any of the automation starts heating? Is this correct?
yes but can we control this for all my rooms
Let me summarize:
- you need one AHC automation for every room
- each automation should toggle its own switch when heating is required
i am using your blue print for all room. i wantto cont dry concact open iff one room needs help and while closing chech other rooms state
e
You can realize it with the custom action like this. Don’t forget to replace the switch entity with yours. NOTE: this only make sense if you enabled off instead of eco. If you lower the temperature to eco temperature, you should evaluate the internal states of your thermostats. But this isn’t part of this blueprint.
if:
- condition: template
value_template: "{{ states('switch.boiler') != iif(is_heating,'on','off') }}"
then:
- service: switch.turn_{{ iif(is_heating,'on','off') }}
target:
entity_id: "switch.boiler"
Hi @panhans I am currently running v4_rc2 with Outside Temperature Sensor enabled however this feature doesn’t appear to be working.
Purely for testing purposes I have the Outside Temperature Threshold set to 5 - the current outside temperature is 5.9 C however heating is ON - I expected heat to be OFF.
[Trace]
But this doesnt take into account the other rooms in case of switching off.
Thanks for reporting. I will check this later.
@vajdum Yes, youre right. He needs for every room an input boolean that represents the heating state and then a 2nd automation that checks this entities or-wise.
@panhans Hi - Outside temperature has gone up to 6.4C (almost tropical and the heating is now being held off.
Is it possible there is some sort of delta built in that means the Outside temperature has to be a certain percentage above the Outside Temperature Threshold before it kicks in?
Outside temperature is now 6.8 C so I moved the Outside Temperature Threshold to 10 and the heating has come on. Whatever the reason for the earlier issue, the Blueprint does appear to be working as expected now.
1 Like
That’s very sweet. Thank you very much.
1 Like