In some circumstances, we are observing invalid values for sensor temperatures. For example, in this case my panel had been placed into Service Mode to override the pump schedule for 3 hours. This caused two spikes in air temp readings to 255F, one at the beginning and one at the end of the 3-hour run:
I have seen this before, maybe around updates or reboots, as well as readings dropping to zero. Got me to thinking that it might make sense to suppress improbable/impossible readings somewhere in the stack since missing points would be better at the app layer than wildly wrong values.
I can collect more data points if that would help, or maybe this is enough to go on.
In some circumstances, we are observing invalid values for sensor temperatures. For example, in this case my panel had been placed into Service Mode to override the pump schedule for 3 hours. This caused two spikes in air temp readings to 255F, one at the beginning and one at the end of the 3-hour run:
I have seen this before, maybe around updates or reboots, as well as readings dropping to zero. Got me to thinking that it might make sense to suppress improbable/impossible readings somewhere in the stack since missing points would be better at the app layer than wildly wrong values.
I can collect more data points if that would help, or maybe this is enough to go on.