Ok here's how I've set it up:

It hasn't been triggered yet but basically I'm hoping the conditions cover what I need. IAT needs to have been below 20.5 for 15 minutes. It will only run the automation if the DHW schedule is not active, and the current WCC values are my lower 'default' ones, which are 49 and 29.

Thus, this should avoid the automation continuously running if it has already been run and adjusted the values. The 'then do' values are 50 and 30 to bump it up a bit.

I then have a separate simple automation to turn the CH back on if it detects that it has been off for more than 1 minute.

I have just realised that there is an error in the above automation/yaml code which is that the Power DHW T5S is required to be off for 1 minute. What this actually means is that the state needs to change from on to off, so it won't run if Power DHW T5S is already off I think. Therefore, I have removed this part.

Posted by: @benson

↑

I have just realised that there is an error in the above automation/yaml code which is that the Power DHW T5S is required to be off for 1 minute. What this actually means is that the state needs to change from on to off, so it won't run if Power DHW T5S is already off I think. Therefore, I have removed this part.

Not sure I get this - the And if DHW Power is off seems clear enough, but more importantly, does this matter (DHW Power being off)? I'm pretty sure if all you are doing is setting the WCC endpoints than you can do that anytime, just as you could do the same thing manually.

There is also a bit of uncertainty which I think I have mentioned before about what Power DHW T5S really is. The DHW can be on, but not heating eg tank is already at temp, or it can be on and actively heating. There is also the transitional period, when the three port, two way valve has changed position, the circulating pump may be running, but the compressor hasn't started yet. Is that on or off? Again, if you don't need to know whether the DHW heating is active, then you don't need to deal with the ambiguity!    

@cathoderay I thought it's just the way home assistant works with the automations- if I include the 'for a certain time duration' field, it will mean that not only does that particular entity need to be off for that duration, but it must have also changed from on, to off. My IAT dropped to 20.4 earlier today and the WCC increase automation didn't run, and I realised it was probably this.

I can indeed run the auto adapt at any time, but if this interrupts a scheduled DHW schedule and turns DHW Power off I would need to use another automation to put DHW Power back on as well, but only during these scheduled times. It seemed easier just to avoid these schedule times for this reason. 

It has actually just worked as intended- around 15 minutes ago the IAT rose above 21 so it has set back to the WCC default values so all seems good thus far.

Posted by: @benson

↑

I can indeed run the auto adapt at any time, but if this interrupts a scheduled DHW schedule and turns DHW Power off I would need to use another automation to put DHW Power back on as well, but only during these scheduled times. It seemed easier just to avoid these schedule times for this reason. 

OK, that makes sense. 

Posted by: @benson

↑

It has actually just worked as intended actually- around 15 minutes ago the IAT rose above 21 so it has set back to the WCC default values so all seems good thus far.

That's good! Is this with the "turn CH back on" automation you mentioned earlier? If so, then another reason to run the WCC adjustments only when the space heating is on. But thinking back to what I have said recently, there is a contradiction in there. I do have a determine whether the DHW heating is on check in the code, but I have just said it doesn't matter whether it is on or not, because I don't have the unit gets turned off problem. Or maybe I did when the DHW heating was on, and that's why I added the check? It is quite a while ago now, and while the code is reasonably well documented, the underlying reason for a bit of code isn't always so well documented... I'll see if I can find any notes I made at the time.    

Posted by: @cathoderay

↑

That's good! Is this with the "turn CH back on" automation you mentioned earlier? If so, then another reason to run the WCC adjustments only when the space heating is on.

Yes that's right. It's a very simple one- if it has changed from on to off for a duration of 1 minute.

I did wonder about that bit in your code you mentioned as well. Anyway thanks for your suggestion that just turning on CH would reactivate the DHW schedules as well. That has solved a bit of a headache for me. My next plan is to try and make sure these automations don't interfere too much and are really only there to cater for exceptional conditions that might lead to more significant under and over shooting- not least as each time they run they interrupt a cycle by briefly turning the heat pump off.