When i change the temp before i run the automation from 18 to 18,5 both autmations jumps to 30, beta and ref. (i think i was before to fast)
It looks like the ref does not set successfully the value to the thermostat, he still be on 30, the beta goes back later to 18.
1 Like
Ok, could you share the trace of the beta, too? Maybe there is something different when calling the services.
909734b6 - { "trace": { "last_step": "condition/0/conditions/4" - Beta
This trace ends in failed conditions. Just change the target temperature of the climate enitity directly, trigger the automation again and download the trace immediately.
I also pushed an update to the new version that makes the automation delayed for 10 seconds on automation reload and home assistant start.
Thanks for your help!
Could you enable ‘split service calls’ and give it another try? (Refactored Version)
1 Like
Perfect now it works, great Job
1 Like
Yes, the logic is quit a bit different now. If it works for you, I will drop the single service call. It seems many thermostats have problems with it. (mine included)
1 Like
i run the ref Version now in one room to test.
Did you already include the sync times for the Thermostats in this rev Version too or is there a other new logic or is these in beta state?
I dropped splitted service calls now. They are splitted per default.
Thank you. That will help very much!
Atm. it should operate like the version before. But maybe there was something wrong in the old version.
The sync times of your thermostat shall work since they are always 2 minutes after the scheduler kicks in. I would say you’re watching this with the new version and if the problem still occurs we will find a solution for this.
1 Like
i am testing new version.
Comfort Heating Plan (optional) i am writing but it is writing saved but it isnt saving
“”
- time: “07:00”
temp: “23” - time: “09:00”
temp: “21” - time: “17:00”
temp: “23” - time: “00:00”
temp: “15”
Comfort Heating Plan will dropped in future versions. I will replace it with something else… maybe something similar.
To your problem: Just delete “” and remove the 2 whitespaces at the start of every line. Just have a look in the example in the description next to your configuration.
thanks if you can add mutli plan ad schulder it can be usefull
if i select Generic Calibration temrature is making +1
Could you explain what you mean exactly?
Yes, that’s the correct behavior. The difference between thermostat and external sensor gets added to the target temperature.
Like this
1 Temp : 23
1 temp schulder
2 temp: 21
2 temp schulder
3 temp: 15
3 temp schulder
Hey, I tested v4 ref with aqara E1 in one Room. I had set up the external sensor via another automation because this works fine and looks better in the dashboard (instead of difficult offset calculation). After I run the blueprint I get an error:
Logger: homeassistant.components.automation.heizungssteuerung_kinderzimmer
Source: components/automation/init.py:618
Integration: Automatisierung (documentation, issues)
First occurred: 16:42:59 (5 occurrences)
Last logged: 16:45:19
Error rendering variables: AttributeError: ‘NoneType’ object has no attribute ‘lower’
I have tested It also with generic calibration. With It, the automation works as I can see. Maybe not really optional?
It’s still not implemented yet. I just want to get the current state to the new code base. But it would be helpful if you can share the trace log (see initial post for a how to) of the run of your automation that produces that error.
//EDIT: Thanks I can reproduce it. Will fix it soon. But has nothing to do with calibration of e1.
//EDIT: Error is fixed. It occured when no external sensor was set.
1 Like
Hi Panhans,
It’s running now so I’m sending you a trace of how it is and then another with me triggering it. Hope thats ok.
Thanks
The first trace ends in failed conditions. So the action was not called. Could you please link the initial post of your problem? Didn’t get everything together.