Hi. Thanks for the suggestion, but set_comfort also seems to be unavailable.
best regards
@panhans did you by any chance have time to look at these log files regarding the uptime error issue?
Hi @panhans
I hope the link is now ok: here the old trace
https://limewire.com/d/uXJY6#sMO5Nyq5Ds
Yesterday i tried to add a schedule with a 30 min Confort / unconfort
and now the automation trigert
but i dont know why all 3 dont triggerd on the same time ( but they have same Schedule)
Here is the trace from today
https://limewire.com/d/2DlZJ#JzZ9CCjvfL
I guess the problem is that (for the moment I dont have Precence sensor) and the automation dont trigger of on âScheduler card configurationâ See my link:
Do you have an option that he said please check / send the new confort value every 15/30min ?
I work with âScheduler card configurationâ because presence time change sometimes for some kids. Family want to check and configure that on dashboard
Edit:
Here also one more Trace
Here the Calibration is activated but I can t understand why he dont give the same setpoing for both
https://limewire.com/d/hu61s#9uJdVTxE9R
He calculate 24,5 and 25 but should ne the same because same automation âŠ
another
Can someone tell me, how I configure the automisation that it will only set to comfor, if the person is a home?
Background
My Wife is from time to time in home office and only if she is at home, her room should be heated up.
Poximity sesor is already configured with office and home zone.
Also a worktime 8-17 oâclock is configured. I was now assuming that the comfor temperature will only take parte if she is at home at the working time.
Thanks for your help
Is there a way to programmatically change the HVAC mode? I know I can set it via a separate automation but that would create a circular condition with the advanced heating blueprint.
Why? I have three schedules, a winter one, a âshoulderâ one and a summer one. In the case of shoulder, I could use âHeat/Coolâ but that results in the AC keeping to the target more accurately than I need, i.e. cooling when anything over target is actually ok at this time of year.
Thanks.
Iâve newly adopted the blueprint but Iâm having issues getting the automation to trigger and run successfully, even with a minimal configuration. My config is shown below, can you help?
id: '1762127531223'
alias: Home -đ„ Heating Control
description: ''
use_blueprint:
path: panhans/advanced_heating_control.yaml
input:
input_trvs:
- climate.central_heating
input_temperature_comfort_static: 20
input_temperature_eco_static: 19
input_frost_protection_temp: 6
input_adjustments: {}
The room temp is below the two nothing kicks in to bring the heat on. What am I overlooking?
EDIT> Iâve done a little more digging and the screenshots below show the trace elements from the nearest actual run.
The automation triggers as a result of a temperature difference.
It stops as a result of all 5 conditions being false
Hi @panhans
thank you for your answer. The uptime integration was not installed yet. I just added it and will check if it helps.
Thank you
Hi @panhans, did you checks the files ? because there would be only 1 week online
Hi all!
Iâve been using the blueprint for a couple years now and it works really great.
I wanted however to improve it with the presence detection.
The expected behavior is that I want the heating to be on, only if someone is in the room and turn to eco temperature if the room is empty.
However, it seems like it is not working, I have a presence sensor, but even when it goes to âoffâ then the heating stays to the scheduled temperature.
Am I doing something wrong?
Could you share your template block or better your blueprint configuration in yaml?
Could you set your thermostat to any temperature but not eco or comfort and run the automation action manually again? The tracelog of this run would be helpful. Sorry for my late reply.
@Esmax555
Your configuration is a little confusing to me. Could you explain to me what you want to archive and Iâll try to help with the configuration? I think itâs better to start from scratch. Maybe there are som misunderstandings.
Could you share your blueprint configuration and maybe a trace log of a manual run when the automation is not working as you expect it to.
You need an entity that toggles eco or comfort temperature, e.g. a person, schedule, binary sensor for presence or guest mode.
Could you share your blueprint configuration? And maybe a screenshot of the the history of the state of your presence sensor when you expect eco heating. Also try to trigger the automation at this point manually and feel free to share the trace log of this run.
Hi @panhans
here is the link of my Original post 
I have integrated several Scheduler cards into my dashboard to set different comfort temperatures according to different schedules (it was important that the family could directly change the setpoint or the schedule in the dashboard view using the Scheduler card).
Then I used this variable from the Scheduler card in the advanced-heating-control configuration as the comfort and eco temperature (since everything is managed by the Scheduler card planning anyway).
But the problem is that the automation doesnât seem to have a trigger to execute (probably because I donât have a presence sensor or a schedule in the automation).
So I randomly tested adding a schedule that changes status every 30 minutes to see if the automation would work,
and it doesâthe automation is triggered.
Here you can see the link showing the solution with the on/off schedule every 30 minutes:
I could open the party mode or maybe for switches. so you can add all your custom schedules there. If one schedule turns on comfort kicks in. In your custom schedules you can edit the target temperatures (comfort & eco).
Then leave everything else blank in the automation configuration especially the schedule section.
Would this fit your needs?
When working with a Time Schedule, there is no separate eco/confort temperature because the different time slots and temperature settings are defined directly in the Time Schedule card, as shown in the image below.
Itâs true that options like party or presence could also work if they are constantly activated by a bit, so the script might function in that scenario.
However, would it be possible to add a Time Schedule card option, for example under Scheduling? If enabled, the automation would know that the planning and temperature are managed by a Time Schedule card, and it could check every 15 minutes whether the comfort temperature has been updated.
In the screenshot above, âtestKIâ is only there to run the automation for 30 minutes. An option somewhere that would allow triggering the automation every 15 or 30 minutes to check if a new setpoint temperature exists would make it possible to remove this table.
Another possibility might be to add this option directly under Temperatures below: If Time Schedule Temperature is enabled, then it only needs to set the variable from the Time Schedule card, and the program knows it should check every XX minutes whether the temperature has changed.
The automation triggers automatically when the value of the eco or comfort entity changes. There is no need for time based triggers. You also can setup an input boolean as a fake presence sensor or guest mode and with your schedule you can toggle this input boolean and set your temperature entites as you like.
But as you can see on the trace automation donât triggers automatically after a new temps value, thats why i force with this 30min triggers
Yes at least you need a person, guest mode, presence sensor, proximity, ect. that toggles between comfort and eco.
If you donât set at least one option the automation only handles calibration and window detection.
As I said get rid of your TestKI schedule and set an input boolean for the presence sensor that toggles between comfort and eco with help of your time schedule that set the temperatures to the temperature entities.
I could also whitelist switches so youâre able to set your time schedules directly in the automation.
As i said before I dont need that toggles between comfort and eco. Ther is only âtemproomâ value in the âtime schedule cardâ
If I set a constant value of 1 for presence (since I donât need to switch), will the automation check every few minutes whether the comfort temperature has changed? (as i said befaore the eco temperature is not used)
Here I didnât understand. As I mentioned before, the goal is for the family to be able to change the schedules and temperatures directly in the dashboard without opening anything else like an automation.
From what I understood, it should rather be that the automation checks the comfort temperature from time to time (for people who donât need a switch eco/confort).
Of course, in addition to my time schedule, I use the party mode to set a slightly warmer temperature (overriding the temperature defined in the time schedule card).
In addtion i use also for exemple Winter Mode / Automation Toggle ⊠ousdide temp âŠ
sorry if it was not clear that i only use confort temp
Then just set an presence sensor / toggle that is always on.
No, but the set temperature change triggers the automation.
Just set a dummy entity that is always on as presense sensor and your comfort temperature entity and youâre good to go.
Hey @panhans thank you for your support!
Sure no problem, the Blueprint configuration looks as follows:
alias: "Wohnzimmer: Heizungssteuerung"
description: ""
use_blueprint:
path: panhans/advanced_heating_control.yaml
input:
input_trvs:
- climate.wohnzimmer_thermostat
- climate.buro_thermostat
input_temperature_eco_static: 18
input_temperature_comfort_static: 21
input_persons:
- person.person_a
- person.person_b
input_mode_guest: input_boolean.gastmodus
input_schedulers:
- schedule.wohnzimmer_heizplan
input_windows:
- binary_sensor.wohnzimmer_balkon_status
- binary_sensor.wohnzimmer_fenster_status
input_mode_winter: binary_sensor.heizperiode
input_mode_outside_temperature: sensor.heizschwelle
input_presence_sensor: binary_sensor.wohnzimmer_mmwave_occupancy
input_presence_reaction_off_time:
hours: 0
minutes: 15
seconds: 0
input_away_offset: 3
input_away_presence_mode: true
input_frost_protection_temp: 15
input_frost_protection_duration:
hours: 0
minutes: 0
seconds: 0
days: 3
input_presence_reaction_on_time:
hours: 0
minutes: 3
seconds: 0
input_away_scheduler_mode: false
input_physical_change: false
input_mode_outside_temperature_threshold: 18
input_scheduler_presence: schedule.wohnzimmer_heizplan
input_custom_action:
- alias: Deaktiviere Heizungssteuerung im Arbeitszimmer
if:
- condition: template
value_template: "{{ set_comfort }}"
alias: Wenn Wohnzimmer geheizt wird
then:
- action: input_boolean.turn_on
metadata: {}
data: {}
target:
entity_id: input_boolean.arbeitszimmer_heizungssteuerung_deaktiviert
else:
- action: input_boolean.turn_off
metadata: {}
data: {}
target:
entity_id: input_boolean.arbeitszimmer_heizungssteuerung_deaktiviert
The interresting bit is in input_custom_action:. I basically want to switch the input_boolean on when the comfort temperature is set and off if not. This is because the office thermostat is also controlled by another instance of the blueprint. And I do not want this instance take over the thermostat (and potentially turning it off) if the living room needs heating.
best regards
I sometimes have the problem that the heating thermostat keeps heating even though the desired temperature has already been reached. AHC then just doesnât turn the thermostat down any further; or maybe even shuts off completely. Does anyone else have this issue?
Also: Is there already a solution or a way to control the HomematicIP thermostats manually, or will that not/never be possible?