The boiler keeps defined flow temperature (knob, 1-6).
I have a HA switch, so i can “call for heat”.
I have a schedule for heating times for TRVs (currently using schedy).
i have heavy temp. differences depending on sun/no sun.
In first line i was curious about all this presence heating
The time needed to heat up a room is not always the same and i have no idea how i could automate this. Need some AI for it
At least if you’re not home you can use proximity for preheating. If you’re smart you can also build a template based presence sensor and use your sleep data or programmed alarm in the morning.
No, its not. This blueprint wont stop your thermostats. It just sets temperatures and toggles between mode heat and off if e.g. your window is open. That issue must be related to your integration or the performance of your thermostat.
I recently replaced the common v4 version with the refactored one since everything runs pretty stable to me. So now it’s - let’s say - in beta stage v2.
Furthermore I’ve added the Heating Schedule Adjustments aka Comfort Heating Plan. It survives reboots, reloads and doesn’t overwrite the adjustments you’ve made.
Atm you can adjust the comfort temperature and turn on/off calibration. You have to set this up with timestamps and weekdays (optional). Some more filters and adjustment possibilities are planed.
Happy testing and let me know if anything doesn’t work as expected. I want to release this version as final if everything runs well for you.
Reportingmore details on my issued with Danfoss Ally.
Seeing your logic – now I see my interpration of the events was wrong. You’re indeed not setting anything periodically. The thing is that Danfoss uses the -8000 (“-80.00°C”) as an undefined/unused value. So if the temperature does not get update by automation in due interval (180/30 minutes), e.g due to differences smaller than the delta, the TRV turns the feature off setting the externally set temperature to -8000. Then, the automation sees the difference larger than delta and sets it back in a few minutes.
When I set the delta to 0, the situation practically resolves (unless the precise temperature would hold for 180/30 minutes, which could borderline happen… but well good enough now).
The TRV documentation is almost fully available at ZigBee2MQTT, specifically here. Note the info on the need to be setting things periodically.
However, I still have the problem that only one of the two TRVs has the temperature set by the automation at all. I’ve reliably tested that it’s always the second of the two listed in the automation configuration.
Any idea what may be wrong there? Can I help you with any debug trace?
I will test these the next days again and give feedback. a special Service for the temp is not necessary
One question: can you set the hvac mode as a pulldown (currently he goes directly to mode “heat”), when this is manuell settable i can use your blueprint as air conditioner “heat/cool/dry” too, this would be great.
I just did an update for v4. Popp / Hive / Danfoss calibration gets triggered every 30 minutes (Maybe we make this adjustable) and when automation gets reloaded or after a home assistant restart.
I think traces wouldn’t help in some situations no more because I move much logic to jinja code. But it’s also easier for me to debug.
I just saw that I did a mistake in calibration logic for Danfoss/Popp/Hive. Just pull the new version and give it another try.
If it also won’t work for you I will provide some jinja code that can be pasted into the template editor.
First off all, the blueprint is great. I use it for several weeks or month and it works perfect till the last update.
I have the same issue when window is opened, the TRV mode switches from off the heat and reverse. Also the days in the heating plan won’t saved in quotes. If i use quotes, they’re gone after saving.