Mirko Laruina

Hi, I've recently bought this scale and I would like to help support it. I've just started analyzing the packets with Wireshark, but I would like to know what exactly...

# Frame sent by phone AFTER measurement ``` Frame no. 963 Value: ab2a0201 01aa1bb29f0212 02a019141e0213 d4d3 0xAB2A is the same for all the packets exchanged with the scale 0x0201 is...

# Frames sent by phone BEFORE measurement Before each measurement, the phone sends two packets. E.g. frame 954 and 956 in S2 btsnoop # First frame I think it setups...

I've reversed engineering (almost) all the protocol and I've added the support to openScale. I'm able to read the values from the scale and compute the various metrics quite like...

Here it is :smile: [openScale-debug.zip](https://github.com/oliexdev/openScale/files/7848835/openScale-debug.zip)

Just noticed I was setting the muscle mass wrong (kg instead of percentage as expected by openScale). Weight, BMI, water, muscle, body fat and body mass should be the same...

> It would still be nice to use the actually-measured impedance reading from the scale, though. Since this is what the scale actually measures. :D The actually-measured impedance is used...

@sebastian-387 oh okay, so it seems the scale is quite accurate and the implementation is working properly. Right now I'm writing the handling of the history. The scale sends all...

- Fixed height conversion (there were issues when set to inch) - Added support to historical measurements - Changed muscle formula. I was using the value under "muscle mass" in...

- The weight is now rounded, when sent to the scale, to the first decimal place to correctly show the UP/DOWN arrow on the scale. In openScale we still have...