Erm not sure I have the best logic for it, as my main concern was stopping it tagging DHW periods in the middle of the day when it was defrosting. There’s a potential that this could tag a DHW defrost against climate stats:
espaltherma_dhw_on:
friendly_name: "Altherma DHW On"
value_template: "{{ states('sensor.espaltherma_esbe_valve') == 'ON' and states('sensor.espaltherma_defrost_operation') != 'ON' }}"
I could probably check against the I/U operation mode on mine as it reports Heating, DHW, Stop, but can also report Heating + DHW which clouds things. Not sure if I/U is available for monoblocks as mine is a hydrosplit with indoor unit.
Also spotted another defrost where its using the cylinder… I wonder if its a quirk and its not valid as the flow temp drops down to 13C and needs backup heaters to recover, but if it was going through cylinder coil (which was supposed to be 34C at the time) you’d think it would maintain temperature despite defrosting.
I might go with:
value_template: "{{ states('sensor.espaltherma_iuoperation') == 'DHW') or (states('sensor.espaltherma_iuoperation') == 'Heating + DHW') and states('sensor.espaltherma_esbe_valve') == 'ON'))}}"```