Sadly no. Just checked it right now and I think this wonât get fixed in near future. No developer had a look in the corresponding issue / pull request.
I only can provide an option for a sync using the dashboard. But atm itâs not possible to differ between a trigger of an automation or by the device itself.
that is sad. Having physical changes overruled wont be accepted by my wife
Any chance for a dirty workaround like:
check if the automation was triggered in the previous 3 seconds: if yes â likely change by the automation, if not: likely physical input? this wont be perfect, but might be enough to be acceptableâŠ
One other thing: Is it possible to have the window detection restore the previous temperature and not set the ECO/Comfort Temp?
@panhans, @Korbelix: maybe a workaround could be a delay! so if there was a manual change of the comfort temp, this should stay for a given time. Afterwards it will go back to the normal value in the automation!! Maybe its possible to use the party mode for that!!
I will open another issue in the ha github repo. @tco95ttocs the bad is theres is no way to differ between a change by an automation or the physical device. But atm the blueprint has no trigger based on the thermostats target temperature. So maybe there is a chance to do it that way.
Change temperature on thermostat
trigger the automation
check wether the temperature change coming from the thermostat matches to the eco/comfort temperature
a) If not â set the corresponding temperature entity in order to sync all thermostats used in the current automation
b) If yes â donât do anything
But this only works for automation with no temperature manipulation like generic calibration or aggressive mode since this would result in a recursive automation call and with every iteration the temperature would get higher or lower depending on the negative or positive offset of this features.
1.) Is it possible to assign window(s) to heater(s)? E.g. I do only want to pause heating in a single room (and not the entire house) if windows in this room are open.
2.) What is the main benefit over Better Thermostat integration? (e.g. multiple window detection. are there more?)
3.) What is the end result of this blueprint? a set of automations, helpers, scripts etc.? Will there be an single go-to UI to manage all these?
The aim of this blueprint is to bring an intelligent heating plan to your home with help of the onboard tools of home assistant. The core feature is heating/cooling based on people presence, schedules, presence sensors ect. without having any interaction with your thermostats anymore. (setup and forget)
Features like calibration, window open detection, aggressive mode, ect. are just extras.
This blueprint doesnât compete with better thermostat, but it can enhance every thermostat with dynamic heating plans.
At least just one automation. The complexity depends on your needs. For some features you need some helpers or existing sensors.
I would like to bring this to an integration but for now I donât have the resources to get involved into this.
Yes, itâs planed to store the entity states in a temp scene and restore it after the windows get closed.
Hi, thanks so much for this blueprint it is really great.
But I noticed a strange behavior. I am wondering if my understanding is wrong or it is a âbugâ.
I set up a âFrost Protection Temperatureâ. It seems my thermostat is set to this temperature when it is in eco for longer than the defined time, although I am at home.
My understanding of the âFrost Protection Temperatureâ feature is that it would only use this temperature if the person(s) are not home for the define duration. Independently of the eco or comfort schedule.
If my understanding is correct, then I would consider my observation a âbugâ.
What do you think? Thanks for the response in advance.
Hey, thanks for reporting. Youâre right I forgot to filter the persons wether they home or not. So if a room is longer in eco and the state of a person doesnât changed for a certain duration and forst protection duration is quiet short frost protection gets enabled. I will fix this soon!
There are some major changes under the hood. Feel free to report errors and bugs if you find some.
Nice weekend to everyone!
1) Before party starts or window gets open the automation takes a snapshot of the climate entities that gets restored after party ends or window gets closed. There is no fallback to comfort or eco temperature anymore but it is when scheduler (for example) changed during the party or window open duration.
First off, thanks a lot for this blueprint! Still getting used to working with them. Thatâs why i post this, just to make sure my âway of thinkingâ is correct.
For now i am only working with the eco and comfort temperatures and window sensors.
So, i have 6 rooms with smart TRVâs, and each room has sensors on their windows.
I have 3 floors, and two thermostats. one for the ground floor and one for the other 2 floors.
I have now created automations for each room, containing the TRVs and the window sensors. The work like a charm.
I was now thinking about the best way to actually control the termostats, should i include them in each room automation (and which automation is then going to âwinâ), or should i create an automation to control the thermostat outside AHC?
Just looking for your best practices and method you would set this up.
Another question, as you are about to release a new / updated version.
I was wondering if it would be possible to have a staggered away mode. Ie, after you leave the temperature is reduced by 1 degree. If you are away for longer than x it reduces the temperature by another 1 degree.
Any thoughts on such an approach?
@panhans Thank you for the blueprint! One question that I could not figure out after trying to search in this thread: is this possible to trigger the echo mode based on an input boolean? It works be nice to be able to determine the"night" or âsleepingâ time based not on schedules, but rather on an actual state whether household members are free factor in bed or not.
Hey @panhans, thanks for all the incredible work on this blueprint.
Iâve just configured it and am having trouble with the presence detection scheduler. After playing around with it a bit, Iâm unable to get presence detection to work alongside scheduling at all.
When I have set input_presence_sensor and input_schedulers, heating switches on at the scheduled times even if no presence is detected.
When I have set input_presence_sensor, input_schedulers and input_scheduler_presence, heating does not switch on at the scheduled times even if presence is detected.
@panhans Bump this Wish
Is it also possible to create a condition Check that must be true before you Trigger like the existing âcustom Actionâ Feature?