I think that was the intended point: 0.00001% of non-.xxx blocked, while 100% of
We ended up just opening up the windows to let the house warm up to a nice temperature. It's such a waste that the air conditioner keeps trying to cool the whole city to 20C, but dad pays the bills so that's his problem.
-- The Girls.
For some reason people tend to assume a proportional controller, and want to help it out doing its job.
People do this because they don't trust/understand the controller - especially understanding the amount of time it takes to respond to a setpoint change.
Back when A/C was simple, it would just run flat-out until it reached the setpoint, and then turn off until the hysteresis bound was crossed. But then they added inverters and the A/C might run an lower powers when it thought that might be a good thing: but sometimes gets it wrong. The solution was for the human to override it by setting a stupid setpoint so the stupid smart A/C might actually do what they want.
Adding extra layers of complexity to the thermostat may overcome the A/C controller limitations, but on the other hand might just make it so unpredictable that people want to override it more.
I thought it already was banned in the developed world.
Unique names do help in searching for issues relating to a particular release.
Over the shoulder supervision is more a need of the manager than the programming task.