System blacklists sensors if an unrelated code path is followed

[doctorames]

On the production unit, it was observed that

• when the temperature hit the absolute low (50.00), it then immediately thought that a sensor was in the weeds, even though it very clearly was not.
• it would then think that the remaining 2 sensors were also in disagreement, even though they very much were not, and reboot.
• I also see that the "temp has been out of range for 2 hours" alert also triggered the erroneous in-the-weeds behavior
• Ok, now that I'm going back over my texts, most of the weird behavior does not appear to have been precipitated by some other alert path. But those do exist.

[doctorames]