@stephanschleichstr13
Would you share the code of your card? I like it.
Even with the new code, these error messages appear in the TRV with the exclamation mark. Aqara E1. Here is the trace.
Hi
i’m still using AHC 4.3.14.
I use the calibration and aggressiv mode.
Could it be, that if the aggressiv mode is enabled, that the calibration didn’t work!
i got the following:
comfort: 21,5
external Sensor: 19,8
aggressiv: 2,5
So in this case the the differenz for the calibration is 1,7. This should be added to the target temp, in this case to the 21,5. This should result in 23,2. With the additional 2,5 for the aggressiv mode the target temp should be 25,7. In my automation the target temp is set to 24. So only the aggressiv mode take in place!
Should is change to the new AHC 5?
Do you want to toggle between presence and proximity dynamically?
Yes
Not for the moment. 
Yes, sorry. Actually, I had a dev branch. But that was confusing for some. Now all blueprints are in the main branch. The new version (v5) is
advanced_heating_control.yaml
and the dev version is
advanced_heating_control_dev.yaml.
A migration to the future stable version can then be easily achieved by editing the automation and adapting it to the path of the blueprint.
Disable your automation please. Bring your thermostat to a healthy condition and navigate to the service tab in the developer settings and try to call this command:
action: number.set_value
data:
value: 21.7
target:
entity_id: number.thermostat_kuche_og_external_temperature_input
If this produces the error please reset your thermostat again and try it again with 21.5 for the value if this also end in this error try an integer like 21, please.
Whats the aggressive range? And a trace log would be great. The logic of the aggressive mode is still the same in v5 just a little bit simplified for me but it’s also possible to modulate this feature on the calibration.
sry i forgot that. the range for aggressive is set to 0,3. …damn i forgot to store more traces…Which trace do you want?
Anyone where the temperature is set. You can force it by changing the temperature of a thermostat manually and then just trigger the automation. But keep in mind the reference temperature isn’t the external temperature in v4 but the local temperature of the thermostat except generic calibration is enabled. (Don’t ask me why I did that)
In v5 the external temperature is always taken if a sensor is set.
ah ok, that could be the problem, if the reference is the temperature of the trv!..so let me test some of them with the new v5!
i found a new bug, so the open bugs are:
- Template Sensor does not work. (dont create entity)
- Enable Room Temperature Threshold is off but does trigger/used
Edit: how i can do this for tests? “You could consider implementing a strict mode that immediately corrects every change outside of the AHC automation.”
Can’t confirm this. Everything works as expected. Could you double check the automation entity id? And are there errors when you check your configuration or after reloading your template entities?
Did your thermostats turn off? The temperature thresholds (outside and room) get evaluated in the same trigger logic.
the entity is right, but yes i have somethimes an ! in front of the yaml (but no errors)
Jep the Thermostat was Off, so in my oppinion this must something in the automation off feature, i setted the room threshold higher and it was triggerd to 15°C but the feature was off
Today i observed that the AHC is triggering the eco temp but it should be the comfort temp
Here is the trigger trace:
I’m still having an issue with the temp being set.
Here’s the trace: https://controlc.com/7ec44ecb
I’ve noticed something strange about my climate control, the state stays in off, even when it’s on.
There also doesn’t seem to be a Mode available in it.
I’m not sure if that might be related to the problem, the temp doesn’t seem to be set when the automation is triggered.
@stephanschleichstr13 @Mar1us @NoBadDays739
I had a similar issue this morning. I changed the execution logic a little bit. For me the temperature reset blocks upcoming changes when the comfort mode should kick in.
@stephanschleichstr13 Isn’t the file extension yaml missing in your filenames? Also the syntax highlighting doesn’t look like vsCode detected yaml code.
1 Like
Just search for spook in this thread. But if you update the blueprint this “issue” will be solved for you. 
Es gibt hier keinen Service Reiter??? oder meinst du Aktionen?
With the latest dev version for me the Window Detection only reverts to the original temperature when closing the window if Legacy Mode is enabled.
Neither with Legacy Mode on or off a scene is created when opening the window.
Reverting back to the original temperature does not work with Legacy Mode on or off if the Physical Temperature Change / Sync option is enabled.
1 Like
as i can say i got the same result with the aggressiv mode and the calibration in v5. In both it look like that only the aggressive value is added to the target temp and the calibration offset is missing! i have 2 traces from v4 and v5. I hope they are enough!!
https://file.io/yeJMmpS83YN3
Could it be, that the automation with v5 didn’t trigger with aggressiv mode, if the taget temp is reached?
roomtemp 21,6
comfort temp 21,5
aggressiv range 0,3
aggressive offset 1,5
So normaly the target temp should be 21,5 but it is still 23!!
target temp 23,5
Hi,
I have a setup with A/C to heat my warehouse. I have succesfully configured the heating to work to comfort temperature when alarm is disarmed using a helper for Presence Detection (i.e. when alarm is disarmed it means there is presence in the warehouse and comfort heating should be on).
Now in case the alarm is armed (meaning there is no presence) i would like a setup where the A/C’s are turned on ONLY when room temperature drops below a configured threshold. i.e. i would like the option “Off Instead Of Eco” to work but only when the current temperature is above the eco temperature (or other temperature setting using a helper). if current is below the eco/other temperature then we should enable heating with eco temperature.
Note that i did enable “
Off If Above/Below Room Temperature” but it does not work. The heating is still on when current temperature (as read from AC) is > than eco temperature. Not sure how to set target temperature otherwise if nobody is present (alarm is armed). I did configure the Presence Away Mode with 6 degrees offset but it also did not help
Is it possible?
Services / Actions yes. It got renaming with the last update.
@Rapha0000
Thanks for reporting. It’s fixed with the latest version.
@tco95ttocs
Also try the latest version. I can confirm aggressive mode didn’t work properly.
@kielczu
Off If Above/Below Room Temperature needs an external sensor in v4. With v5 it’s also possible with a climate only.