Thanks for that explanation. I think this was misreported at the time (or I just wasn't paying attention!).
In a way what you described is worse: a known bug that they decided not to fix.
I'm surprised that displaying the sensor value wouldn't be a standard feature.