Hi Matthias,

In your first screenshot, real sensor 1 is zero, real sensor 2 is 24.5 and the virtual sensor is 12.3.
So the average is considering zero input.

I guess zero could only be achieved with faulty sensor or unplugged?
So in this instance, the virtual sensor would trigger the heater on and it’d be stuck on forever or until the heater broke.

I did this test myself, but figured I must have been doing something wrong, as I got the same result.

I think the average functionality is only good if both probes are fully functional, if you ever have an issue, it would boil your tank.

Do you agree?
Is there a way to handle this?

Ideally, if either of the probes registers zero then it should default to the working value.
That’s what I meant by “exclude zero input”.

Would it be possible to put an override using programming logic to detect zero on either probe and force the heater to stay off until the situation was resolved?

Am I misunderstanding something?

Many thanks,
Dave