i think there is a misstake in the blueprint.
in my opinion the comfort temp on Present should only work when the Scheduler is true right?
Currentlly the Comfort Temp is activ when iāam present but out of the scheduler.
Could you check if you running latest version? (at least 3.4.3)
I did some tests with scheduler and a person and for me heating turns off when scheduler is on and nobody is home and if scheduler is off and the person is home, too.
Could you check version again and provide a trace log if this happens with the latest one?
holiymoly, i updated a few days ago, ur fast. Iām was on 3.4.1 now on 3.4.4 and will check it.
Is there a way to get a notification in Homeassistant when ur updated your blueprint?
I tested these night, the minmal Temp was not triggered.
Could you provide at least a trace log? In my configuration everything is fine. (test and prod)
Click in this view the upper right button and download the json trace log. You can paste the content here, create a link and share it.
Youāre defined a presence sensor but no presence scheduler where presence should be active. Without a scheduler presence detection is always active. And in your case presence is detected so the comfort temperature will be set.
You can define a scheduler for presence detection where you can set the time when presence detection shall be active if you donāt want to use it all the time.
If you donāt want to use presence detection and schedulers only then simply remove the presence sensor from your configuration.
I think the automation is a little monster now and it needs some more documentation.
ahh okay, that makes sense, thank you.
I thought he use the default scheduler from top.
One more question maybe a feature, in my old Heating Blueprint the creator integrate an blocker helper which hold on the blueprint, when i wanna use the thermostat completlly manuell, make it sense to integrate these too what you think? alternative i can disable the blueprint in this time
With version v3 everything is more flexible and combinable. You can use schedulers only, you can use presence sensor only, also āperson is homeā only can trigger heating.
But you also can define your scheduler without a person and combine this with presence detection if this fits your case.
I personally use a scheduler in combination with persons and if scheduler is off Iād define a presence scheduler for evening and morning. So if someone stay awake or get up earlier heating will start dynamically.
Whats the use case for that feature? I can simply do it by adding a binary entity, but I also could add an option that blocks the automation if party timer / binary is active/on. So the automation can leave the blocking state automatically if party timer / boolean turns off.
//EDIT: Maybe a timer / boolean for a blocker entity is the most flexible option. I would trigger the automation a last time and after that it will gets blocked.
I think i need to play more with this blueprint to understand it better, its much more efficent as my old one.
My Case for that was for example when i has homeoffice but iām to lazy to set it up or when the current temp is on the current day to high and i wanna set it down for a while, but when im think about it, i can use the Party Timer for that too.
For home office you can use presence detection. Just define a scheduler when presence detection shall be enabled. Your presence sensor can be your computer or desklamp. If on ā heating turns on.
You also can enable reset comfort temperature when scheduler ends (maybe I have to add presence detection to that feature). So you can simply change the comfort temperature and it will reset automatically if scheduler turns off. And if you donāt want to manage it using UI try the experimental feature Physical Comfort Temperature Change. So you can change temp on your trv and it will set to your comfort temperature entity.
You can also start the party timer when changing temperature manually. There is an option for this.
But I think Physical Change doesnāt work as expected. I need to dive a little deeper into this. Itās not well documentated.
//EDIT: Yes, there is a bug with detecting physical change: Sun trigger does not generate context Ā· Issue #68047 Ā· home-assistant/core Ā· GitHub
So there is no way atm to differ between automation or physical.
Hi allā¦
Just sharing a little learning for any other newbies here!!
TL/DR - Check your Tolerance for heating cutoff on your thermostat
The blueprint is amazing and for the most part I am getting it to work. I have scheduled a window I want it to be at comfort setting and a window I want it to be at minimum.
I have used the āGeneric Thermostatā as my Thermostat for now. I will be having smart TRVās also, but may actually run these on separate automations so I can heat different rooms separately (we have a couple of lodgers so will only heat those rooms when they are home etc).
I have a Thermometer in the middle of the house and a smart Relay activating the boiler. If I turn the switch on and off (logically) the boiler turns on and off. The issue I had was when I setup the Generic Thermo, I did the minimum requirements. This seemed to work, except when I set the Comfort temp in the blueprint, the heating wouldnāt turn off. Took me a little while to realise that there is a Heat Tolerance level that you can adjust in the config of the Generic Thermo. By default this is 0.3ĀŗC.
So when I set a comfort temp of 19.2ĀŗC (in the blueprint) the heating continued to run past this. It never turned off because I have set the surrounding rooms to turn off their radiators at 20ĀŗC. So by the time the heat travels to the central thermometer it had dissipated and cooled downā¦meaning that it would never read the set 19.2Āŗ + 0.3Āŗ of the tolerance - 19.5Āŗ.
I made the adjustment to 0Āŗ for the tolerance and seems to work nicely now.
This would be the same for any Thermostat, boiler or TRV, you may have to dig a little to see if you have a tolerance for them. I did find that HA may not see all of these so you may have to use the original App to set that to get the behaviour you want in HA.
If you all know this, then sorry for wasting your timeā¦ but hoping it will save one or two newbies some time and effort.
Thank you for sharing your experiences.
So atm youāll heat all rooms to 20Ā°C and then the boiler is supposed to switch off?
Do you have any temperature sensors in your rooms? Maybe it makes sense to you creating a template temperature sensor instead of your physical central one that returns always the minimum temperature of all your rooms. In the end the generic thermostat turns off when every room is at least at 20Ā°C.
Thanks for the replyā¦ thats where I am heading. taking the steps to get there. I will eventually look to have window sensors come into play also. so if a window is open, then the temp of that room gets removed from the equation - donāt need to heat the neighbourhood!!!
@panhans I have one more problem, maybe im the problem ^^
my living room is on 22Ā°C but im was not @ home, so in my opinion the minimal temp should be 18Ā°C, can you see why?
If this is the trace log when no one is at home, there is something wrong with your detection of whether someone is at home.
Your scheduler is on and according to the log someone is at home.
Also check the time of your trace log. Donāt know if its the correct one. HA saves the last 4 logs. You can browse in trace view with the arrows next to the time stamp. Maybe you have to trigger it again without someone is home to produce the one you need.
Just check your history if person.martin really wasnāt away at the time.
Donāt want to hassle you and am very happy to play and learn. but wondering if you can shove me in the right direction. What I want to achieve is:
- 4 rooms with individual TRVās controlling the radiators in those rooms.
- some common areaās that for now Iāll treat as āequalā
so lets call it 5x zones. I want to take all 5 zones, look at the coldest zone and turn on the heating if itās below XX. Finding the lowest temp is fine, this can be achieved using a Min/Max or a Group helper. either will deliver the ācoldestā temp.
I know I can use this to feed the blueprint. BUTā¦ this is the big BUTā¦ I only want the inputs of the thermostats to be valid if the specific person for that room is home.
IE:
Room 1 - John
Room 2 - Peter
Room 3 - Paul
Room 4 - Jack
Common - Anyone
so if Peter and Paul are out, I donāt want their rooms in the mix, only Johns, Jackās and Common. I have presence detection working by their phones at the moment - not perfect but āgood enoughā for now. I will look to introduce presence detectors in the rooms over time.
If I can figure this out, I will then do the same with window sensors. If the window in Room 1 is open, then drop the temp out of the mix, regardless of presence.
In the short term, I am using the central sensor as my trigger to turn the boiler on and off, with each person added to that blueprint. that way if anyone is home the boiler will play nice according to the settings. I have then setup additional blueprints for each of the 4 rooms to control if the radiator un that room comes on or not. Obviously unless the boiler is on no heat will happen, but this is still a massive step forward from the traditional controls.
Hope this makes sense?? And ā¦ if itās too hard/unreasonable I fully accept thatā¦ but never know unless you ask!! Like I said I am happy to play/explore but any guidance would be amazing.