02-02-2018 01:57
02-02-2018 01:57
We import fitbit steps, floors and sedentary time from the WEB API. Steps and floors appear to be fine, but we get 1440 for the total of sedentary minutes for the days that a user did not possess a fitbit yet. 1440 minutes is the same as 24 hours. That seems to be a bug.
See these graphs. This user received her new fitbit on 2017/12/25. We started importing data on 2017/11/27.
Answered! Go to the Best Answer.
02-12-2018 09:02
Fitbit Developers oversee the SDK and API forums. We're here to answer questions about Fitbit developer tools, assist with projects, and make sure your voice is heard by the development team.
02-12-2018 09:02
@dirkjanmdl, we checked our backend it seems like this is expected behavior.
The options for sedentary time before pairing are really either 0 or 1440, so 1440 is the current value. For the dates exported prior to pairing on 12/25, that 1440 value is accurate.
Best Answer02-08-2018 15:05
Fitbit Developers oversee the SDK and API forums. We're here to answer questions about Fitbit developer tools, assist with projects, and make sure your voice is heard by the development team.
02-08-2018 15:05
@dirkjanmdl what Fitbit devices your users are using?
Best Answer02-12-2018 09:02
Fitbit Developers oversee the SDK and API forums. We're here to answer questions about Fitbit developer tools, assist with projects, and make sure your voice is heard by the development team.
02-12-2018 09:02
@dirkjanmdl, we checked our backend it seems like this is expected behavior.
The options for sedentary time before pairing are really either 0 or 1440, so 1440 is the current value. For the dates exported prior to pairing on 12/25, that 1440 value is accurate.
Best Answer02-13-2018 00:15
02-13-2018 00:15
Thank you very much for answer. Wouldn't zero or nil make more sense? Why assume that the user sat all day? By the way, the device was a Charge 2.
Best Answer