The call before was 10 minutes before. Did you identify the problem by now?
Tado support is really useless. They ask me for a bunch of photos of the thermostat. I really hate the attitude of this company. They treat their customers like they are idiots instead of communicating properly.
For now the blueprint is designed to hold a minimum temperature if scheduler is off. But if requested I would add a tweak option into the blueprint settings to turn climates off instead of lowering the temperature. I would add this to the v3 test version. I think itโs pretty stable now and so I can going to release it these days.
That would be amazing if you could add that feature please.
I absolutely love everything else about this blueprint, itโs exactly what Iโve been looking for, great job on it!
first thanks for your work. Really great blueprint. On your recent ones i got the problem, that my Thermostat stucks on minimum Temperature. I have no presense sensor only a schedule and a magnetic sensor. Schedule is set right (on) and the Windows is closed. On your older Versions (march 2023) it works fine and im still using it. Any ideas what causes this?
Yes itโs optional in order to use presence sensor only. But scheduled heating is only working in combination with at least one person. Maybe I should change this if no person is specified. Will add it to my fix list vor version 3.0.1. Thanks for your feedback!
@panhans Thanks for your work and integrating all our wishes.
Make it sense to integrate a external time scheduler (HA helper) that heats in this time also when im not at home. My sleeping room for example should not heat when im at home but between 21:00 and 22:00 and then go back to the minimal temp. i hope you understand what i mean, my english is bad ^^
You can use party mode or guest mode for this use case. Guest mode โsimulatesโ if someone is at home and party mode simply activates heating. Both can be set up by a timer.
How is presence measured? I have now switched to aqara motion sensors with a low occupancy timeout (with hardware hack down to 5 secs).
Now the motion sensors could detect several motions within a minute, but has it to register a constant 1 or 2 minutes of motion in order to trigger (therefore I have to set/extend the occupancy timeout)? In this case, a binary would be nice to control it.
Then I could count the number of motions (for example in a timeframe of 1-2 minutes) and switch on the binary and trigger the automation.
Yes, exactly it must hold the state for that duration. There are two options since a motion sensor is not the same as a presence sensor with mmwave:
I can add a second slider to have the option to lower the timings.
You can debounce the motion sensor as you said. The motion sensor is also a binary_sensor with device_class motion. If you define your template sensor based on your motion sensor just set the device_class to presence and you are good to go.
I have, this morning, Installed the full version 3 of the blueprint. Unfortunately calibration appears to have stopped working as it was in the beta (now removed).
The delta is beyond what is set in the automation of 0.5 degrees, even going as much as 1.5 degrees difference
Iโve tried a few things such as reloading the configurations even restarting HA and neither seem to have an effect.
Could you provide a trace log? For me it works as expected. The smaller the delta the more often the calibration is triggered. You can force the calibration trigger by setting the temperature in dev settings manually or simply hold the sensor in your hands.
Thank you! Some people in my household like to use the valves if they want to raise temperature, but itโs usually not need for the whole day, so this would be appreciated!
Nice! It would have been convenient for it to have a different file name so that we can save it and migrate the old automations, no? Not very experimented, so I might be wrong.