You can iterate through the logs with help of the arrow buttons on top of the graph view.
Does nobody have any ideas about my questions?
Would be helpful if you describe the use case. Atm the automation falles bac to the eco temperature in this case.
For this I have to add another selector.
See temperature adjustments / heating plan.
Just create a template sensor for this. And toggle between your schedules. If you need help, just let me know.
Ok, why? Also the use case would be interesting to me. Maybe there is already a solution.
Many thanks for your response.
The use case is that I want to have 2 different temperature modes when I’m at home.
An example:
If no one is at home, the temperature should be set to 18 degrees. In the evening, when the family watches TV, plays together or we eat dinner together, the temperature should be 21 degrees. The rest of the day, when someone is at home, the temperature should be 20 degrees. The idea is simply to save on heating costs. When I’m at home and cleaning the house I don’t need 21 degrees as an example.
That’s why I currently use the Eco and Comfort temperatures for the heating plan when I’m at home and need an additional temperature when I’m not at home.
Can you describe this in a little more detail?
That would be great. This gives more options for what can be set in the dashboard. The temperature range is currently set to 15 degrees, but it would be great if it went up to 18 degrees. I have currently changed it in the code myself.
The use case is the same as described in detail above.
If this is time based you can raise or lower the comfort temperature with help of the heating adjustments.
Maybe you share your ahc configuration first. Don’t know if you just trigger heating using persons or schedules, presence sensors, ect, too.
And here I’m again. I’m almost make it as I planned (which is good) with one exception. The night. I don’t want to work the TRV during the night so I create a schedule. Unfortunately it is been ignored.
Unfortunately I don’t have traces because… It is not the first thing in the morning 
I need to wake up to do it.
Below are more details:
Day Heating Mode: 06:00-23:00
input_boolean.living_room_heating is a boolean which change from automation and has a lot of “and” conditions
alias: "Living room: Heating control"
description: ""
triggers:
- trigger: state
entity_id:
- sensor.living_room_th_sensors_temperature
conditions: []
actions:
- if:
- condition: or
conditions:
- condition: and
conditions:
- condition: state
entity_id: person.katya
state: home
for:
hours: 0
minutes: 10
seconds: 0
- condition: state
entity_id: binary_sensor.working_on_the_office
state: "on"
for:
hours: 0
minutes: 5
seconds: 0
- condition: and
conditions:
- condition: state
entity_id: person.katya
state: home
for:
hours: 0
minutes: 10
seconds: 0
- condition: numeric_state
entity_id: sensor.living_room_th_sensors_temperature
above: input_number.living_room_eco_temperature
below: input_number.living_room_comfort_temperature
- condition: and
conditions:
- condition: state
entity_id: person.katya
state: home
for:
hours: 0
minutes: 10
seconds: 0
- condition: and
conditions:
- condition: state
entity_id: binary_sensor.sitting_on_the_dinning_table
state: "on"
for:
hours: 0
minutes: 5
seconds: 0
- condition: not
conditions:
- condition: state
entity_id: binary_sensor.sitting_on_the_dinning_table
state: "off"
for:
hours: 0
minutes: 10
seconds: 0
then:
- action: input_boolean.turn_on
target:
entity_id: input_boolean.living_room_heating
data: {}
else:
- action: input_boolean.turn_off
target:
entity_id:
- input_boolean.living_room_heating
data: {}
mode: single
and the automation for TRV itself
alias: "Living room: Advanced Heating Control"
description: ""
use_blueprint:
path: panhans/advanced_heating_control.yaml
input:
input_trvs:
- climate.living_room_radiator_right
input_hvac_mode: auto
input_temperature_sensor: sensor.living_room_th_sensors_temperature
input_persons: []
input_windows:
- binary_sensor.living_room_windows_sensor
input_mode_winter: binary_sensor.heating_winter_mode
input_startup_delay:
hours: 0
minutes: 0
seconds: 35
input_schedulers:
- schedule.day_heating_mode
input_temperature_comfort: input_number.living_room_comfort_temperature
input_temperature_eco: input_number.living_room_eco_temperature
input_presence_sensor: input_boolean.living_room_heating
input_presence_reaction_on_time:
hours: 0
minutes: 2
seconds: 0
input_presence_reaction_off_time:
hours: 0
minutes: 2
seconds: 0
input_mode_outside_temperature: sensor.outside_th_sensor_temperature
input_mode_outside_temperature_threshold: 9
also a screenshot from the input:
Hi @panhans,
me and my wife are away from home and I just received a notification from AHC automation indicating that confort temperature was set. This is unexpected. Could you help me figure out what made the automation act that way?
When that happened, I manually triggered the automation (target temperature did not change), to generate the trace log: { "trace": { "last_step": "action/3/default/8/then/0", "run_id": "b - Pastebin.com
I took a look at it and I can’t figure out why.
Many thanks!!!
"is_anybody_home": true
Seems somebody is home or at least wasn’t away for the set leaving duration. (15min) Also check the history graph of the persons.
Now, this is strange… nobody has been at home since early in the morning today. My wife left at 7am and I left around 9. And nobody has returned home. See below:
This is my current configuration:
and “we have guests” binary has been off for longer time
Did you do a restart of home assistant when nobody was home? (Update? Maybe you’d configured some kind of auto update?)
Not that I’m aware of, but even if I had one, if I now trigger the automation it still sets the target temperature = comfort temperature instead of eco. I assume it is an issue on my side, but I can’t pinpoint where it is.
Could you check the state of the persons and not the state of the home zone?
Ah, wait. Maybe I have an issue in my code. I will check this later this day. Do you have a clue when comfort kicked in?
yes, it is time based. That means I would have to set the schedule for Comfort for a full 24 hours and adjust the temperature via Heating Schedule Adjustments?
I didn’t configure much. I use the window option as well as the proximity option. The temperatures for Comfort and Eco are controlled via an input_number. Plus a schedule, but I’m now unsure whether I even need it?
I control the reduction for the night using the HA daytime sensor, which I have set as a window.
Hi again,
Yes, by all means!! 12:36pm today.
Thanks!
Hi,
Congratulations on this excellent blueprint, thank you!
I need the ‘window’ and ‘force max temperature’ features. So I’ve configured very little in my automation.
Automation configuration : https://controlc.com/373c84cf
I created an input_boolean helper to activate force max temperature. This triggers the automation, but no condition is validated at first step, so noting happens.
The automation trace : https://controlc.com/1b61a39e
I don’t understand why this isn’t working? Is force max temperature influenced by another parameter?
Thanks in advance for your help.
Hi again @panhans ,
just checked my logbook and saw that, for some reason, the automation got reloaded right when the temperature changed to comfort:
I did not do anything that may have triggered the automation. But even if I did, it would still have to have returned target temperature = eco.
Let me know if I can provide any addicional details!! I’m eager to discover what may have happened!
Schedules, person entities, proximity device, presence sensors ect. toggle the automation between eco and comfort temperature. (static or your entities)
With help of the adjustments you are able to set other value for the comfort or eco temperatures based on timestamps. (You can also provide another input number instead a number value)
So if you just use a simple schedule and want different comfort temperature over the day this is the way to go. 
Without any person/schedule/presence sensor ect. only window detection and calibration is allowed. I will see if I also could whitelist force max temperature for your needs.
Just reimport the blueprint. I did some changes here. Would be great if you report back if this fixes your issue.