07-25-2018 16:29 - edited 07-25-2018 18:26
07-25-2018 16:29 - edited 07-25-2018 18:26
I'm building a clock face for the Versa. My formula for calculating Miles is
myMiles.text = (today.local.distance * 0.000621371).toFixed(2);
Seems pretty simple. But by the end of the first day I used it, miles on my clock face was about a half mile lower than what my phone app said the watch recorded (~5 miles vs 5.5). Using adjusted.distance gave me the correct number. Why would this be? I didn't make any adjustments.
08-13-2018 13:37
08-13-2018 13:37
There is two calculations done on our side: a "simpler" one on the watch, and we adjust the number once the data is on the server with different and more complex algorithms for things like distance and steps as examples.
12-10-2018 14:19
12-10-2018 14:19
What does this mean? I tried to create an app involving distance in MI on a clockface and the mileage was off by over a mile. The app on my phone showed 3.5 miles, the Versa itself showed 2.3 using the same conversion as the first poster. Is there an accurate way to display mileage on the watch itself?
12-11-2018 11:43 - edited 12-11-2018 11:44
12-11-2018 11:43 - edited 12-11-2018 11:44
Try using "adjusted' instead of "local", it should match the mobile app.
https://dev.fitbit.com/build/reference/device-api/user-activity/#interface-today