You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello, the temperature values are not correct when the sensor's temperature is more than 32 degrees celcius (they are negative). I took a look (by decompiling) at the source code and here's what I found for the snippet that parses the temperature:
var temperatureRawValue =
((data.readUInt8(17) & 0b00000011) << 10) |
(data.readUInt8(16) << 2) |
((data.readUInt8(15) & 0b11000000) >> 6);
if (temperatureRawValue > 2047) {
// JavaScript way to convert an unsigned integer to a signed one (:
temperatureRawValue = temperatureRawValue - 4096;
}
temperature = temperatureRawValue / 16.0;
Beyond the latest version is it possible that you provide a patch for this for the version 0.16.1 (for example version 0.16.2)? Unfortunately I have various problems with the new APIs of version 1.0.1 and I would like to stick to 0.16.x for now but I'd really like this bug fixed.
Thanks a lot!
The text was updated successfully, but these errors were encountered:
Thanks for reporting that. Fix is already live in version 1.0.2 (need some time to appear on Maven) :)
We are not planning to update old SDK 0.16.1 for now :(
Hello, the temperature values are not correct when the sensor's temperature is more than 32 degrees celcius (they are negative). I took a look (by decompiling) at the source code and here's what I found for the snippet that parses the temperature:
This code is very strange and definitely doesn't have anything to do with your specs (https://github.com/Estimote/estimote-specs/blob/master/estimote-telemetry.js):
Beyond the latest version is it possible that you provide a patch for this for the version 0.16.1 (for example version 0.16.2)? Unfortunately I have various problems with the new APIs of version 1.0.1 and I would like to stick to 0.16.x for now but I'd really like this bug fixed.
Thanks a lot!
The text was updated successfully, but these errors were encountered: