Could you share the history graph of your binary_sensor.wohnzimmer_aktivitat? Also a trace log of the automation would be better for analysis your issue.
Hello everyone! I am loving day after day this automation 
I am experiencing though one issue. I created a timer with friendly name heat_boost23. I expected that, when activated, the heating was going to 23 celsius. But it does not: it pushes again the heating to the standard comfort temperature.
Am I adding the name of the timer wrongly?
1 Like
No problem, of course.
But you’d have to give me a little help. Where can I find the trace log?
In the Automation under Traces?
under Associated Log Entries: No log entries were found for this step.
Seperate the temperature with white space like Heat Boost 23. This should to the trick.
@clipse
It’s described in the initial post in the FAQ section. Doesn’t matter if there are steps or not since there are variables that give a hint. If the automation never got triggered you can execute it manually before downloading the trace log.
Lovely! Thank you!
1 Like
If you are not at home and have a heating plan and the absence is active, should you not heat up? For me, it does this from the point at which the heating time ends. Is that how it should be or have I forgotten to activate something?
I got everything up and running and it works great but I’m not smart enough to figure out how to get more heating schedules than away and comfort and eco. Could someone explain it a little more for me? Say I want the heat to be a little warmer after 5 on weekdays or something like that. I see it can be done but I don’t know how to accomplish it.
If you set up persons and you’re not at home but heating schedule is enabled, comfort doesn’t kicks in. If the schedule is off eco also will be set. If this is not the case for you just share an trace log to see what comfort heating triggers for you.
Just have a look into the heating adjustemts. There you can set timestamps where a another comfort or eco temperature can be set. You can make it more selectable for specific schedules or weekdays if you want, e.g.
- time: 17:00
comfort: 23
days:
- Mon
- Tue
- Wed
- Thu
- Fri
- time: 23:00
comfort: 21
days:
- Mon
- Tue
- Wed
- Thu
- Fri
The second entry is for resetting the comfort temperature.
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.