Sudden offset in temperature reading
-
One of my aqara sensors suddenly stated that the temperature in the garage passed +650 degrees.. I checked, and it wasn't.
Both humidity and pressure is reading normal levels - i guess this must be a HW error?
Its not dead either, just severely offset:
-
strange indeed... seems like a hardware problem!
-
Took out the battery for a moment, and now its back.. Just a "senior moment" (well, 10 hours) i guess!
-
..and now its back at 655° again.. order a new one i guess..
-
If it's suppose to be around 65F° then it it could be a notation error. Mixing up decimal points and decimal comma
US notation 65.5 would result in 655 when the notation is not set to imperial. E.g. EU notation is 65,5.
Still doesn't explain why it changes all of the sudden though.
-
Hm! It wasn't that, but rather when it goes below 0° C! (cold in Norway)
I'll throw one of the others outside to see if the same happens, mabye its a flaw in the zigate plugin? -
Sounds like a signed value is being interpreted as an unsigned one, so the MSB is set when the temperature goes negative. I’d guess that a 16 bit value is scaled so that 32768 = 327.68 degrees. This would also be consistent with the UPnP standard representation of temperature being in units of 1/100 of a degree.
-
..And this is done in the plugin, i presume? Seems like all message handling is done there in zigbee?
I'll have a look at the code tomorrow.. -
If it’s as I think, then the fix is easy... if the value exceeds 327.67 then subtract it from that number.
5/9