I too critically rely on heating. As system complexity increases with things like outside temperature sensors, I would much rather have visibility into their workings than not. In the middle of the night, that could be the difference between a quick ten minute diagnose and override, or waiting some hours for an emergency service call.
I had a similar failure with my hot water boiler, where an older solid state control failed such that when the circulator would kick on the burner would shut off. This allowed it to limp along heating, until a day when it was too cold out and I realized it wasn't keeping up.
re: libre software, my point isn't really about being able to audit the code, but rather about having a cross-device software-maintainer-maintained codebase that users choose to use.
FWIW another, probably better, way to mitigate this particular external temperature sensor failure mode would be a second larger control loop. When the indoor temperature is more than a few degrees below the setpoint (not as a result of a scheduled change), the furnace should be less-efficiently creating a larger amount of heat to get back up to the setpoint quicker. Which is funnily enough how people think most thermostats work when they ineffectively turn it up higher to get things warmer faster.
Individuals are of course welcome to hack together what they want using Arduinos or whatever.
Again I very deliberately do not have a smart thermostat or other network connections to my heating so no surveillance is going on. I do have network-connected temperature sensor but it’s purely passive.