Hello @panhans any help with this?
Thanks 
Can I just confirm the logic here please
If the condition renders “true” does that prevent or allow calibration?
Thanks
@panhans Sorry to bother you with maybe a stupid question. I don’t understand how to use the holiday function. I would like to start add a button (input_boolean.heizung_schalter) and when this is pressed the Eco and Comfort temperatur is set to 16°C. When it’s pressed again, the temperature changes back to 19/21°C.
But if I press the button it will change to the temperature which are behind the helpers (input_number.temperatur_comfort_standard and input_number.temperatur_eco_standard).
After I got this to work I would like to add also another variant for sickdays/vacationa at home.
Could you maybe bring some light into my brain?
Thank you so much 
alias: Heizung_Esszimmer_v5
description: ""
use_blueprint:
path: panhans/advanced_heating_control.yaml
input:
input_trvs:
- climate.thermostat_esszimmer
input_temperature_sensor: sensor.temperatur_esszimmer_temperature
input_schedulers:
- schedule.arbeitswoche
- schedule.temperatur_urlaub
input_windows:
- binary_sensor.fenster_esszimmer_breit_contact
- binary_sensor.fenster_esszimmer_schmal_contact
- binary_sensor.tuer_wohnzimmer_einzel_contact
- binary_sensor.tuer_wohnzimmer_fluegel_contact
- binary_sensor.tuer_w_schmal_contact
input_temperature_comfort: input_number.temperatur_comfor_standard
input_scheduler_selector: input_boolean.heizung_schalter
input_temperature_eco: input_number.temperatur_eco_standard
input_adjustments:
- scheduler: Temperatur_EG
comfort: "21"
eco: "19"
- scheduler: Temperatur_Urlaub
comfort: "16"
eco: "16"
input_calibration_key_word: external
Hi,
i have the same Problem. I use the Aqara E1 theromsotats with room temperature sensors from Aquara and get the exclamation mark. If i deactivitate the room temperature sensors and use the internal thermometer everything works fine.
@panhans I am on 5.1.2. Is the fix integrated?
Have this on my list. Will implement this soon. I am little busy atm.
True means allow.
You can add multiple schedules and create a selector e.g. a Dropdown Menu Helper with the friendly names of your schedules to switching between them.
If you just want to have static temperature you can add an input boolean as a party entity with a name like Holiday Mode 16 to force your climates to 16°C. Let me know if you need further help.
Honestly I don’t know if I never fixed this since I don’t know what service call was the reason of this issue. Could you send me a screenshot of the attributes of the calibration number entity? (developer tools state section) Maybe I’d missed something I can implement like min and max values, step size, ect.
Okay, i saw that you wrote that its fixed…maybe it was something different.
I hope you mean this data
min: 0
max: 55
step: 1
mode: auto
unit_of_measurement: °C
icon: mdi:thermometer
friendly_name: Wohnzimmer/Thermostat External temperature input
Thanks. That helped. You can check out the latest version if you like. I’ve added step sitze an min/max check for the calibration values. Would be nice if you give some feedback if it works for you or if it ends in that issue again.
Thanks. That makes sense.
The external sensor calibration now seems to send only values rounded to the full degree, even though that option is turned off.
Guess that is related to the latest fix for the Aqara E1?
That value is definitely able to accept a 0.1 step on the thermostat side.
For now I think the exclamation mark just pops up randomly (or maybe when the temperature does not change for a while). There is an option to just disable those valve alerts though.
The step size is read out dynamically from its attribute. I don’t know if it depends on z2m/zha or custom quirk. Here you can see the step size for the calibration is 1 (at least for this implementation). Never mind if the attribute says 0.1 the step size is set to this value but if there is no step size provided it will fall back to 1.
Could you check the attributes of your calibration entity, especially its attributes?
Would be nice to know what exactly causes this issue.
Good to know. 
The attribute is indeed set to a step size of 1, even though it does accept 0.1 (and the temperature is shown with 0.1 resolution in z2mqtt).
I have set up an automation to update the external temperature at least every 60 minutes and enabled the valve alarm to check.
However it usually takes days or weeks for me for it to show up, and even more time for me to notice, since the thermostat behaviour does not change at all even with the alarm active.
Hi everyone,
I live in an apartment so I can only control TRV not the boiler. I want to avoid that during summer the automation continue to work. How can I achieve that?
Hi,
I’ve read back a few days as I’m struggling with setting up the presence detector to do anything useful atm. Is there some issue in general that you are working on, related to what @cediqqu has been saying?
I’ve set up the blueprint and after some weird issues (temp to max, randomly) that have been resolved by how the thermostats are configured (offset vs target), the temps are now doing what they should - for the most part.
The part with the presence detection gives me troubles… I have 2 proper SONOFF presence detectors in 2 different rooms, and they detect properly. They’re both on schedules, so that the bedroom actually goes into eco mode at night. But I’ve also tried to set it up that when during the presence schedule there is no presence detected for x seconds, it also goes into eco mode, but this just doesn’t ever trigger.
Also a question, it’s not possible to override the temperature of any thermostat manually? After just a few seconds or minutes at most it jumps back to the temp that has been set. It would be great if there was some way to keep a manual override persistent for a (at best defineable amount of) time…
Thanks!
-d
Take a look at the ‘On/Off Automation Options’.
You can use a weather entity or an outside temperature sensor to turn the automation on and off depending on the outside temperature.
Or you can switch it on and off by setting the ‘Winter Mode / Automation Toggle’ to a binary sensor, for example a switch helper entity.
Ah ok. So could this be fixed by forcing the calibration every X minutes? I’d implemented this for Danfoss/Popp/Hive because here the values gets deleted after a certain duration.
You can update the latest version but there is a BREAKING CHANGE with 5.1.7. The Fully Rounded Values Selector is gone and got replaced by a new one. So now you are able to override the auto mode for the step size.
Don’t know yet, I will keep testing it with an automation that triggers at least every 30 minutes or so.
However, like I said, I found the alarm coming up rather randomly in the past, so I just turned it off. There is no real explanation from Aqara about that alarm, and I also had the temperature not changing for like 8 hours without an alarm coming up (back when I did the updating with Node Red).
Cannot hurt to update the values once every x minutes if they don’t change anyways.
i tested it and the exclamation mark comes back very fast.
Atm i changed to generic calibration but i left the sensor to external. This works so far.
Thanks for the hint. So this will allow me ho stop to have the automation running but what about having also valves open at 100?%
Reason is that usually in spring/summer they use to have maintances (empty all the pipes change water ecc) and it’s better to have valves open to facilitate it.
Any hint?
The automation just changes the setpoint transmitted to the thermostat. Keeping the valve open would have to be done by the thermostat itself, for example by setting a high setpoint.