We started with requesting the Cardio Load, but it looks like the Web API doesn't return the correct values. For a test device we see vo2Max range results on days that we didn't use the test device (for example May 10 and 11), we see a vo2Max range for the current day, while the Fitbit app shows that there is no cardio load (yet) for the current day (May 20), and we see wrong values, for example on May 18 we see a cardio load of 82 in the Fitbit app, but a 45 - 49 range via the API.
We are sure we retrieve the data from the correct Fitbit account, other data from this test account can be read properly from the API.
Is this a known issue? Do we need to provide more information? (showing the JSON result of the request doesn't work here, too many not permitted data items in the JSON like dates and ranges)
