It’s a little tricky but possible. The automation has to fire a custom event with all this data. On the other side it needs an template sensor that listen to this kind of event and stores the data in different attributes. I will check this.
1 Like
Just have a look in the latest changelog. If you’re missing information just give some feedback.
//EDIT: just added some more information to template sensor (last_calibration & last_temperature_change)
1 Like
Eco Temp is missing 
Eco and Comfort temperature is also available now.
1 Like
Hi,
im currently struggling a little bit with the configuration and understanding the ECO/ Comfort/ Away Functions.
I used before a mix of Integration and Automation, but I wasn’t happy with that because of the battery drain…
But in this combination it was possible for me to set a fixed away temp. This was used if nobody was at home (not linked to any schedule or so). Just plain nodody at home = Away temp ON.
When somebody is at home the eco temp was selected if nobody was in the room (presence detected). If presence was detected in the room, the comfort temp was applied.
Is this somehow possible? As im currently stuck of finding a good method to achieve this 
thanks in advance
Martin
Hi thank you for your feedback.
Currently the temperatures only switches between eco and comfort temperature. the away temperature is an offset subtracted from the comfort temperature. But your objection is justified: I will implement the away offset like you’d described if it’s set.
Nobody home → eco temp
Home but no presence detected → comfort temperature - away offset
Home and presence detected → real comfort temperature
Would this fits your needs?
hi,
hmm could be working yes, but how will then the schedule affect the behaviour?
Also wouldn’t it be better (maybe also easier) to change the name of Eco temp to away and use the eco temp for the room temp without presence?
In this setup the away temp will be then away from home and not “away from room”?
then also the scheduling would be quite easy as you can just schedule the comfort temp and otherwise the eco offset would be applied.
another question for understanding of the suggestion from you / in general.
currently it is necessary to use a schedule helper to “active” the away temp option and it is not possible to use the away temp just with the presence, isn’t it?
thanks, Martin
Same like the current implementation. Maybe it needs a switch for both cases.
The blueprint started with only two temperatures and this would be too much changes just for naming reasons. I also use the names in code and in the current state this monster has round about 2500 lines of code. So I will stay with comfort and eco and the away offset. Just to prevent unwanted reflection errors.
This would be part of the description of this modifier. In case of presence detection combined with persons no other combination make sense since it never can be activated if nobody is home.
Atm not, but with my local test version it is. 
1 Like
is there a way also to have “is_eco_temperature” and “force_max” attributes?
if you need a second tester, please let me know
is_comfort is boolean and is also the state of the template sensor. so if it is on comfort ist set and if it’s off eco is set.
force_max → yes, i will add this.
1 Like
No, need. Just checkout the latest version.
@stephanschleichstr13 if you update check your away temperature configuration again. I just changed the input variable. you need to set it again and enable it for scheduling.
1 Like
looks like its working 
Really great.
So now it is not needed for meta use any Schedule helper, as the automation is capable of doing some timings via the “Heating Schedule Adjustments”.
and I will get used to the ECO/ Away naming
1 Like
HI
i got some TRV801w (Salcar) thermostats. I can control them manualy without any automation. If i put them to your blueprint, nothing happens. I made a copy of a working automation from my AVM 301 and changed the entity but nothing happens.
The only thing i could figure out is the following error message in the trace timeline:
“Fehler: network error:(2008) command or value not support”
Any ideas?
Could you trigger the automation and share the trace log? (If you don’t know how you can do this just have a look in the first post of this thread.)
Your climate entity doesn’t support hvac mode heat. Just check your climate entity in dev tools and verify your hvac modes. Maybe it just supports auto then just set auto in blueprint settings.
is it possible to fix this protocoll error?
Logger: homeassistant.helpers.template
Quelle: helpers/template.py:2558
Erstmals aufgetreten: 10:30:00 (94 Vorkommnisse)
Zuletzt protokolliert: 18:10:00
Template variable error: 'dict object' has no attribute 'event' when rendering '{{ trigger.event.data.is_comfort }}'
Template variable warning: 'homeassistant.util.read_only_dict.ReadOnlyDict object' has no attribute 'last_calibration' when rendering '{{ iif(trigger.event.data.is_calibration,now(),this.attributes.last_calibration) }}'
and
Logger: homeassistant.helpers.binary_sensor
Quelle: helpers/trigger_template_entity.py:209
Erstmals aufgetreten: 10:30:00 (93 Vorkommnisse)
Zuletzt protokolliert: 18:10:00
Error rendering state template for binary_sensor.advanced_heating_control_wohnzimmer: UndefinedError: 'dict object' has no attribute 'event'
This is already fixed in the latest example. It’s also available in the initial post.
Im using the latest version of them - updated before i posted