you mixed up catty and imperial in description for mi scale 2

https://github.com/wiecosystem/Bluetooth/blob/master/doc/devices/huami.health.scale2.md#advertisement

Small correction:

• 8th and 10th off: metric
• 8th on: catty
• 10th on: imperial

You mixed up catty and imperial. I am not taking this backwards as I'm getting the correct info for weight/impedance stabilised.

Thanks a lot for this!

FYI your doc (along with some other projects) let me come up with this: https://github.com/foormea/esp32_mi_scale_2

[x11x]

Hi @foormea,
I'm trying to follow your work (helpful by the way, thanks).
You are counting bits starting from 1, with the least significant bit first?
So testing for "8th" bit corresponds to using the bitmask 1 << (16 - 8) = 0b100000000 against the 2 control bytes.
Testing for "10th" bit means using bitmask 1 << (16 - 10) = 0b1000000

Looking at your code https://github.com/foormea/esp32_mi_scale_2/blob/325ecb6f2c6b892c88ade0aeb8420deafc41761b/esp_sketch/esp_sketch.ino#L278-L286

if ((controlBytes & 0b100000000) == 0) strUnits = "jin"; means "if the 8th bit is off the unit is jin/catty"
if ((controlBytes & 0b1000000) == 0) strUnits = "lbs"; means "if the 10th bit is off the unit is lbs/imperial"

So it looks like you are doing the same thing as described in the document in this repo, just describing it differently? (except in this document the bits are counted starting from 0 instead of 1)

(x & mask) == 0 means the bits in the mask are "off" not "on", right? (just trying to make sure I understand).
Thanks

Hey @x11x, apologies for replying so late.

Yes, looks like I got really confused in my comment. You're totally right and my initial comment was plain wrong!