The trace shows the eco temp is set to 16°. Do you also could share the trace where the thermostat were set to 5°?
The thing is that the ECO is indeed set to 16, but the thermostat itself is only set to/left at 5 degrees. So it doesn’t change the temperature on the thermostat itself.
Even when I set it to e.g. 20 degrees and run the automation, it puts the thermostat to 5 degrees/off. This did always work well before.
Hi @panhans,
I really like your blueprint. It really saved me a lot of time. But I’m not sure if I understand the ‘winter mode’ function.
My challenge:
I have an air conditioning, which I use in the summer with cooling mode and in the winter in heating mode. The target comfort temperatur is different based on mode, ie Summer 75F vs. Winter 69F.
Thus, I created two automation, one for summer and one for winter for the same Air Conditioning.
My initial thought would be to use the ‘winter mode’ to toggle between those automation. (In one of the automation, the Invert Winter Mode Value is active, in the other not).
In my simplified assumption it would work as follows:
If Winter mode is on
Winter Automation active
Summer Automation inactive
and vice versa when Wintermode is off.
BUT: My observation is different. It seems that both automations are running.
My Winter automation sets the heating temperatur correctly to 69F. But the summer automation sets the Air Condition to ‘off’. The final status is ‘off’.
Am I misinterpreting the ‘Winter mode’ to toggle between them? If this is not the intended use case, for what use case is the ‘Winter Mode’?
Is there a different feature I missed, which would meet my use case?
Is this a bug of the ‘Winter Mode’ or is it a ‘missing feature’ to toggle between summer/winter needs?
Any advise would be highly appreciated.
(I’m using version 4.3.14)
You set a preset in custom action. May this did force the temperature to 5°C. Could you disable the automation. Set the temperature to 16°C and set the preset using the action/service in developer options?
Yes on means on. Navigate to your summer automation and enable invert winter mode value. This should do the trick.
Just have a look into your history. Select the time span and the climate entity. You also can have a look into your logbook.
Ok. I also looked through the logs, there is no change at 1 pm. Only when I got home was the target temperature raised to 22.
I think that the notification should also work, as the target temperature (even if it is the Eco temperature) should change, shouldn’t it?
Ah sorry, found the issue. The away temperature overrides the eco temperature from the adjustments. I will fix this soon.
Ah great 
I’m glad that it’s a bug after all and it’s not me:grin:Thank you
Yes, hard to find those kind of bugs since there is no possibility for automatic unit testing. I will push an update soon and after that I have to refactor the code to make in more readable and easier maintainable.
//I should looking forward to turn this into an integration.
Checked, and set the preset in de developer options through actions doesn’t put it back to 5 degrees. So it’s not that.
That custom action always has been there since I use it.
Could you reproduce that behavior? If yes, the trace log of the the run after the 5° were set would be great.
Came this issue after closing windows? Do your thermostats support some kind of window open detection natively? Some thermostats turn the temperature down automatically when they measure a temperature drop.
Tested and result:
Disabled Automation and removed the Custom Action (Preset to Permanent):
I set the Kitchen Temp to 20 degrees, Set Preset through Dev/Actions to permanent.
Waited a few minutes and temp stays at 20.
Run the Automation and immediately the temp is set to 5 degrees.
Trace: https://controlc.com/57c228af
No window detection natively, that requires wired sensors and we don’t have that.
Your outside temperature configuration turns the thermostat off. It seems the temperature sensor has a higher value than your threshold you’d defined.
Well, that could be it. Not that the temperature has the higher value, but it looks like the entity wasn’t working correctly anymore…(Netatmo), outside temperature wasn’t showing any value at all :-(. This should now be fixed, will monitor coming days. Will update you asap.
Just bought you another Ko-fi for all your effort. Thanks!!
1 Like
More testing on the proximity, do you have any hints?
I want to a shop on my way home, from work:
and I captured this when I got to the parking lot
When I left the shop
Range is set at 8000
Thanks @panhans for the quick response.
The ‘invert winter mode value’ is enabled in summer.
For some reasons, both automations are still running and firing an event, the summer/cooling one to turn it off, the winter/heating one to set the temperature at 69F. Below are some screenshots.
Please see the full trace here:
Heating: https://controlc.com/c364a467
Cooling: https://controlc.com/d481b15c
Any thoughts, why both automations run? Only the winter one should run, isn’t it?
Hi everyone,
I use the following configuration which works fine. The only problem with HVAC ‘Auto’ is that if the temperature difference is too small (~1.5°), the valve only opens 25%. Is there a way to ensure that it always opens 100%?
If I change the mode to ‘Heat’, it opens to 100%, but it does not stop when the target temperature is reached.
Regards
alias: 🔥 Advanced Heating Control - Kinderzimmer
description: ""
use_blueprint:
path: panhans/heating_control.yaml
input:
input_trvs:
- climate.kinderzimmer_thermostat
input_hvac_mode: auto
input_temperature_minimum_static: 18
input_presence_reaction_on_time:
hours: 0
minutes: 0
seconds: 0
input_presence_reaction_off_time:
hours: 0
minutes: 0
seconds: 0
input_windows:
- binary_sensor.kinderzimmer_fenstersensor_contact
input_windows_reaction_time_open:
hours: 0
minutes: 2
seconds: 30
input_windows_reaction_time_close:
hours: 0
minutes: 2
seconds: 30
input_mode_outside_temperature: sensor.kuche_thermometer_luft_temperature
input_mode_outside_temperature_threshold: 20
input_tweaks: []
input_temperature_comfort_static: 21.5
input_calibration_delta: 0.5
input_calibration_options: []
input_temperature_sensor: sensor.kinderzimmer_thermometer_temperature
input_time_based_temperature_change_valve_target:
- time: "06:00"
comfort: "19"
calibration: "on"
- time: "16:30"
comfort: "21.5"
calibration: "on"
- time: "21:00"
comfort: "19"
calibration: "on"
input_schedulers: []
input_presence_sensor: input_boolean.komfort_kinderzimmer
input_aggressive_mode_range: 0
input_aggressive_mode_offset: 0
HI
the only thing you can do is to use the aggressive mode!
1 Like
Hi tco95ttocs,
I tried that and didn’t really understand it.
Can you give me a tip on how to set this?
Example:
Actual temperature 20.5°
Target temperature 22.0°