hi i installed the latest version (5.0.rc2_2411042055). But today the same, aggressiv Offset is added to the target, but the calibration offset not!
comfort: 21,5
aggressiv: 2,5
roomtemp: 18,3
calibration offset: 21,5 - 18,3 = 3,2
target temp: 24
but the taget temp should be 27,2 (21,5+2,5+3,2)! For testing i set the calibration offset to 10.
Here is a trace from this morning: https://file.io/SpRpYGzrGWGs
Hope this helps
You have to enable this feature:
There is also a misunderstanding. Your values are fine as they are. If the absolute difference between your set temperature and your room temperature is outside the range defined by you, the offset defined by you is added or subtracted to the target temperature.
The generic calibration offset is for generic calibration only. You didn’t enable this. So this has no impact. The native calibration works automatically. You just can tune the amount of triggering with the delta and timeout.
The calibration is completely independent from the aggressive mode. Also the target temperature has no impact on the calibration. The native calibration sets the temperature / offset of certain number entities provided by your thermostats / integration.
If this is not the case, you can enable generic calibration so the value is added to the target temperature of your thermostats.
Calibration = Difference between the measured thermostat temperature and room temperature sensor.
Aggressive Mode = Forcing higher values (target temp +/- aggressive offset) if the measured temperature is way under / over the the target temperature (room temp - target temp </> aggressive range).
ah ok, little missunderstanding :D…if i activate the aggressive calibration, than the new target temp is lower than the old one, so instead of 24 its only 22 in the one room and in another ist 21,5 instead of 23! So thats nearly the same as without the aggressive mode! Im not sure if the aggressive calibration should generate a higher or lower target temp! https://file.io/Wi7P0bbSvM2D
Your room temperature is 18.3°C and your target temperature is 21.5°C.
Your aggresive mode range is 0.3°C
That means:
18.3 - 21.5 = -3.2
-3.2 < aggressive mode range (0.3)
So the aggressive offset will be added to your target temperature.
Target temp + aggressive offset = 21.5°C + 2.5°C = 24°C
24°C is your new target temperature.
You’ve enabled generic calibration. Now check the thermostat temperatures and the room temperature. The difference get’s added substracted to the target temperature depending on which temperature is higher / lower.
For example your first thermostat must measure 16°C instead of 18°C like your sensor. That’s why the difference (18-16 = 2) added to the new target temperature.
aggressive target temperature + calibration difference = 24°C - 2°C = 22°C
With every target / sensor change the target temperature will be evaluated and gets adjusted.
//EDIT: I’ve edited the thermostat temp value
These changes works thanks.
i have one open problem, why the thermostat goes to 0°C. It is always on 15C eco jumps to comfort 18C and than to 0, and than back to eco at 7 o’clock (no trace available)
Could you share at least your automation configuration in yaml code?
alias: Advanced Heating Control Schlafzimmer
description: ""
use_blueprint:
path: panhans/advanced_heating_control_dev.yaml
input:
input_trvs:
- climate.schlafzimmer_comet_dect
input_temperature_sensor: sensor.schlafzimmer_comet_dect_current_temperature
input_temperature_comfort_static: 18
input_temperature_eco_static: 15
input_temperature_comfort: input_number.advanced_heating_control_schlafzimmer_comfort_temperatur
input_temperature_eco: input_number.advanced_heating_control_schlafzimmer_minimum_temperatur
input_mode_party:
- input_boolean.advanced_heating_control_schlafzimmer_party_mode
input_persons:
- person.xxx
- person.xxx
input_people_entering_home_duration:
hours: 0
minutes: 2
seconds: 0
input_people_leaving_home_duration:
hours: 0
minutes: 5
seconds: 0
input_scheduler_selector: input_select.advanced_heating_control_scheduler
input_schedulers:
- schedule.advanced_heating_control_schlafzimmer_zeitplan
- schedule.advanced_heating_control_schlafzimmer_urlaub
- schedule.advanced_heating_control_schlafzimmer_homeoffice
input_reset_temperature: true
input_away_offset: 1
input_away_scheduler_mode: true
input_windows:
- binary_sensor.schlafzimmer_comet_dect_window_open
input_calibration_generic: false
input_calibration_key_word: external
input_mode_winter: input_boolean.heizperiode
input_mode_outside_temperature: sensor.penthouse_temperature_feels_like
input_mode_outside_temperature_threshold: 17
input_mode_room_temperature_threshold: 21
input_mode_guest: input_boolean.advanced_heating_control_wohnzimmer_guest_mode
Could you put binary_sensor.schlafzimmer_comet_dect_window_open and sensor.penthouse_temperature_feels_like into the history graph in combination with your thermostat?
//EDIT: sensor.schlafzimmer_comet_dect_current_temperature maybe, too.
Is your blueprint on version 5.0.rc2_2411042055? Had an issue with restoring temperature/scene after window gets closed. This should be fixed now. And it looks like your thermostat didn’t come back after airing.
it was 5.0.rc2_2411040928 Updated today to 5.0.rc2_2411042055
alright i will test it today, thanks 
Ok, thanks, when do you think comes the next release?
It’s done when it’s done. Some people here (including me) are already testing the next version (see. dev version in the first post).
The major issues are eliminated already, I think. For me it works very stable but I wait for the other testers if they are fine with their personal configuration.
i fully agree with the aggressive mode, but i thought that the calibration cames first!
And what happend if the calibration differennce will be 3 or 4? Than the new target temp will be 21 or 20, which is lower than he original target temp and lower than the comfort temp i try to get!
which is the first sensor and which is the second one? Normaly the temp in the room is lower than at the trv, so the first sensor should be the room sensor! So that the trv will open more to get the room warm!..
thats to high for me 
It doesn’t matter. It’s only addition and substraction.
When the radiator is cold the thermostat has the lowest temperature. After the valve opens a while it’s the warmest place. And with time both values gets equalized so the difference is in the perfect case 0°C.
Example:
TRoom = 18°C
Tthermostat = 20°C
Ttarget = 24°C
TTargetCalibrated = Ttarget - (TRoom - Tthermostat) = 24°C - (18°C - 20°C) = 26°C
After a while of heating:
TRoom = 20°C
Tthermostat = 22°C
Ttarget = 24°C
TTargetCalibrated = Ttarget - (TRoom - Tthermostat) = 24°C - (20°C - 22°C) = 26°C
And when the room temperature is nearly reached:
TRoom = 23.5°C
Tthermostat = 24°C
Ttarget = 24°C
TTargetCalibrated = Ttarget - (TRoom - Tthermostat) = 24°C - (23.5°C - 24°C) = 24.5°C
With every temperature change of target, sensor or temperature of the thermostat, the values gets renewed. So the target temperatures of your thermostats are only for that moment. In 10 minutes they can differ to the current temps.
had the same issue but after update it working fine
maybe you can add these to the 1first post as info?
Does your automation trigger when the presence detection is on? (see the timestamp in the automation overview)
Could you trigger your presence sensor for the duration you configured it in the automation/blueprint settings and share the trace log with me again? Your old one isn’t available anymore.
Sure thing here is a new trace log: https://controlc.com/32c0487e
It seems to definitely be triggering
I suspect the climate.set_temperature is for some reason not set.
Thanks in advance for the help.
