07-26-2016 09:55
07-26-2016 09:55
Hello,
Recently, we are seeing 'Activity Logs List' records w/o the HR Zones. Such as;
{
"activeDuration": 2155000,
"activityLevel": [
{
"minutes": 0,
"name": "sedentary"
},
{
"minutes": 0,
"name": "lightly"
},
{
"minutes": 1,
"name": "fairly"
},
{
"minutes": 35,
"name": "very"
}
],
"activityName": "Elliptical",
"activityTypeId": 20047,
"calories": 267,
"caloriesLink": "https://api.fitbit.com/1/user/-/activities/calories/date/2016-07-22/2016-07-22/1min/time/8:21/8:57.json",
"duration": 2155000,
"heartRateLink": "https://api.fitbit.com/1/user/-/activities/heart/date/2016-07-22/2016-07-22/1sec/time/08:21:10/08:57:05.json",
"lastModified": "2016-07-22T07:55:21.000Z",
"logId": FILTERED,
"logType": "auto_detected",
"manualValuesSpecified": {
"calories": false,
"distance": false,
"steps": false
},
"startTime": "2016-07-22T08:21:10.000+02:00",
"steps": 3360,
"tcxLink": "https://api.fitbit.com/1/user/-/activities/FILTERED.tcx"
}
Can anyone tell me 'when' does HR Zones actually does becomes available? Or the screnario/state when it does? Such as the Device in use, "logType", Activity type, etc.
Thanks in advance!
Cheers!
Answered! Go to the Best Answer.
Best Answer07-28-2016 13:25
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.
07-28-2016 13:25
@Rapido thanks for calling this out here! This should be fixed now and the endpoint should behave normally moving forward. This was an issue on our end.
Apologies for the inconvenience!
Best Answer07-27-2016 05:05
07-27-2016 05:05
I'm hoping this is just a bug on Fitbit's end, but I also noticed it was no longer returning the heart rate fields.
Activities which I previously got from this list, and had HR information then, now don't include it when I get this endpoint.
Best Answer07-28-2016 13:25
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.
07-28-2016 13:25
@Rapido thanks for calling this out here! This should be fixed now and the endpoint should behave normally moving forward. This was an issue on our end.
Apologies for the inconvenience!
Best Answer