Fitbit data inaccuracy in presence of multiple fitbit devices in vicinity

[aditya14641]

This is typically observed in my workplace where we have more than 100s of fitbit devices. I have developed the OAuth application that pulls data from fitbit using fitbit OAuth APIs. Sometimes, some of my co-workers get different data than that they see on fibit website and this data from fitbit OAuth API gets auto-corrected after OAuth calls are made sometime later.

I have noticed for past couple of months that the Fitbit OAuth APIs are sending inaccurate data intermittently and then the data auto-correction takes place.

Is this issue due to number of fitbits in vicinity?

This is repeating since past few months.

Please let me know solution if any.

I am using fitbit4j java library to make https calls

[aditya14641]

Is anyone else experiencing similar issue ?

[JeremiahFitbit]

The Fitbit API and Fitbit.com pull data from the exact same data storage. If you access both at the same time, they will have the exact same data.

[aditya14641]

Not sure what is happening but users are not getting same data fromOAuth as they can see on the website

[JeremiahFitbit]

Please provide examples of the page and the API request that differ.

[aditya14641]

API - timeseries API for steps

apiClientService.getClient().getTimeSeries(new LocalUserDetail(resourceCredentials.getLocalUserId()), FitbitUser.CURRENT_AUTHORIZED_USER, TRACKER_STEPS, LocalDate.now(), TimePeriod.SEVEN_DAYS);

Every night when this API is used for user to get past 7 days data it returns differenet data for yesterday and someother days at times

[JeremiahFitbit]

If you provide the actual HTTP request and responses, we can review them. Without this evidence, it's difficult for us to determine the issue. As this should contain user data, please email api at fitbit.com instead of posting it on the forum.

[aditya14641]

I cannot send the reuqests and responses. I rely on fitbit jar to generate that and get data for us.

However, I can send you our fitbit client id, client secret, userid of the user and his security tokens. It would be great if you can check at your side with all this information, why the data that we got for the user is incorrect.

Important! Our requests do not fail,just that they pull incorrect data sometimes in day. At other times in day, they pull correct data also.