The firmware could see that the value was stuck at a constant, compare your outside temp to a local forecast, see that your internal temp continued to drop, or employ other strategies for determining bad sensor data. There's little incentive for Honeywell to add such functionality (cf the paradigm where you just call a professional who diagnoses your problem), but with libre software it might just scratch someone's itch at which point the functionality would be available to all. Libre software certainly isn't a panacea, but rather seemingly a necessary condition for embedded devices to not get stuck at whatever simplistic version of zip-source-control crapware they're shipped with.
By surveillance I'm referring to what would pass for "remote notifications" of system status (after the possible bad sensor was detected). The IoTrash solution would be to backhaul your system's data to a surveillance cloud, require you to sign up for email spam, install a bespoke app that would spam you with useless notifications, faux-consent to a ridiculous anti-privacy contract, etc. Whereas in the libre world, user-focused incentives are allowed to define functionality and that notification could be a simple single email.
Making the point in general, in order for complex software to not be some terrible black box, it needs to expose its internal state to users who want to see it. Libre software tends to do that (as many users are developers), while non-libre software tends to lock all that up and thus severely limits reliability xor complexity.