Looks like you are using release 29, so in my opinion, no you cannot trust those readings. Other folks here, including myself, have seen this issue. From memory, I was thinking this issue and other issues had been fixed in a previous release of app and/or firmware, but now they have returned in release 29. Fix something, break something else. I am certain James is aware of the issue. By the way, very nice screenshots. You saved a least a thousand words :) – — Duane