Hi everyone,
I’m starting to use this bleuprint. Do you have any good example to what can be done with Custom Action ?
can we send notification when temp is reduced because away mode or window open as example ?
Thanks
Could you share a trace log? I checked presence and scheduler away mode and both worked for me.
Thanks @panhans for this great piece of software.
I‘ve tried to use V5.0.rc1_2411011120
I‘ve imported the blueprint file advanced_heating_control_dev.yaml successfully. Semed to work for me in different configurations without problems.
But what todo/how to work with the file ahc_template_sensor.yaml ???
Sorry, but I am still learning HA
Regards Handfest
Hello, I have 10 thermostats and an Automation AHC v4.3.14 for each.
Spook keeps telling me that there is an error in the blueprint: This automation points to the following actions that Home Assistant is unaware of: tado.set_climate_temperature_offset
Is there really an error? I don’t use Tado and the entity really doesn’t exist.
Hello, just startet using our Blueprint.
It´s working fine for me.
Only question i have, is there a way i could use the default thermostat (Homematic IP TRV) to set the comfort temperature?
Greetings from austria
Before I look for the calibration error again, I would first install your new version. Will it remain so that I can delete the old one?
Thanks. It is actually working. Just the temperature did not change for a while and the TRV showed some other temperature, where ever it got that from.
Maybe one-shot update the external temperature when the automation reloads/HA restarts?
sure was on the road 
Not needed. It’s just a sensor that offers some variables and states of the automation.
Just search for “Spook” in this thread. In the next major release you won’t get this warning anymore. (You can ignore this.) Alternatively you can switch to the dev version of the next version.
You can enable “physical change / sync”. Be sure you setup entities for comfort and eco temperature. Note that this feature is some kind of experimental. (Don’t use it in combination with generic calibration or aggressive mode) In the next release it is more robust.
Yes, it will remain but if it goes stable the code is provided by another file. But the migration is quite simple: You just need to edit the automation blueprint path when it’s ready.
Did you enable aggressive mode over calibration?
Seems fine to me:
"is_away": true,
"temperature_comfort_of_entity": 21,
"temperature_comfort": 21,
"temperature_away": 20,
"target_temperature": 20
hmm, the thermostat had 21C - i will add now the “AHC Template Sensor v5” into the Dashboard
Edit: the Templte Sensor gives that error:
Logger: homeassistant.helpers.template
Quelle: helpers/template.py:2742
Erstmals aufgetreten: 12:30:26 (1 Vorkommnisse)
Zuletzt protokolliert: 12:30:26
Template variable warning: 'dict object' has no attribute 'id' when rendering '{{ trigger.id }}'
edit:
check this one { "trace": { "last_step": "action/2/default/4/if/condition/0", "run - Pastebin.com, here the trace values, but the thermostat has 22C
"temperature_comfort_of_entity": 21,
"temperature_eco_of_entity": 18,
"temperature_comfort": 21,
"temperature_away": 20,
"temperature_eco": 18,
"target_temperature": 21,
But in this case the away condition is false. (is_away: false)
are these values not the end values? are this whe values with them you work later (add calibration steps etc)?
Is this the thermostat temperature or the comfort temperature entity? Could you see in logbook what automation set this temperature? In the trace is nothing about 22°.
Try to change the thermostat temperature und execute the automation again. If the temperature is set to 22°C again, check the trace especially the set_temperature block. If 22°C was set just share this trace log, please.
22C is the setted temp on the thermostat comfort is 21C. yeah in the log is nothing thats why im struggeling
Is it normal that the Automation does not run when the comfort temp is reached? i setted 19C manuelly and run but he does not change the temp back to 2xC
the Logbook is emty, i will check it again later
Yes, the new code base works very conservatively and generally only reacts to the required triggers. You could consider implementing a strict mode that immediately corrects every change outside of the AHC automation.
1 Like
ah alright maybe this is the point
good to know i will check
@panhans ,
Thank you for this blueprint it’s very advanced:)
I use tado and I am happy with a tado app’s setting and do think like scheduling.
There is a way to use your blueprint just for presences, proximity and windows sensor settings? I am thinking about an on/off button or something in your blueprint like feature selector.
is this the new upcoming blueprint, or which one do you want to use in the future, i wanna change my system? HomeAssistant/blueprints/automation/panhans/advanced_heating_control.yaml at 664c3dcaf438279945524deb3f632d108321417a · panhans/HomeAssistant · GitHub
Edit:
Does the Temperatures not support comma?
Edit2: it looks like Commit 664c3dc, does break the template sensor creation (i changes the temp very high, so automation triggered but no entity was created)
Same question here - I am a little confused
I think my confusion started when exporting directly from the github instead of following the links in the Opening Post.
on your github, there are four versions.
For people, that import directly from the github page it is not very clear which is which. Maybe put some lines of description in the code? (I can somehow sort it out by the “last change”-date) … ah! I found Version on line 48 … so a little scrolling helps.
Found one more thing - mismatch of source url in code with actual source url. Dunno if this is important.
Until further notice I will go with the link in the opening post:
which points to: advanced_heating_control_dev.yaml (Dev version with new code base)
And advanced_heating_control.yaml will be the place for future major releases?
1 Like