jlboygenius

POST /cloud/v1/deviceManaged/fatScale/getWeighData HTTP/1.1 accept: application/json tk: XrXvMIej5tLnkZER9**Am4g== accountid: 1***3 tz: America/New_York accept-language: en appversion: 3.0.20 Content-Type: application/json Content-Length: 425 Host: smartapi.vesync.com Connection: Keep-Alive Accept-Encoding: gzip User-Agent: okhttp/3.12.1 {"traceId":"1600269682529","method":"getWeighData","token":"XrXv****N6d1QllmAm4g==","accountID":"1**3","timeZone":"America/New_York","acceptLanguage":"en","appVersion":"3.0.20","phoneBrand":"SM-G973U1","phoneOS":"Android 10","startTime":0,"endTime":1600269683,"configModule":"WiFiBT_Scale_FatScalePlus_US","cid":"0L**WOQMU8kZT-0fGZMCwA1","pageSize":100,"order":"desc","index":0,"flag":1}HTTP/1.1 200...

Here's the device info for the scale. from /cloud/v2/deviceManaged/devices { "deviceRegion": "US", "isOwner": true, "deviceName": "Fitness Scale", "deviceImg": "https://image.vesync.com/defaultImages/ESF00__Series/icon_fitness_scale_160.png", "cid": "****1", "connectionType": "wifi+BT", "deviceType": "ESF00+", "type": "BT-Scale", "uuid": "24:****:E6", "configModule":...

Yes, the start dates are from when I logged the data, back in September. I'm using the packet capture app on my phone. I don't think vesync likes it, because...

convert the 1eb031:200254 to hex (A:B)... Add A+B/8192 in this case: 501 voltage works out to be 119

I wish I was the genius who figured it out, I found it in some other code. No idea why they do that.