Hello Team,
We are trying to get a deeper understanding on what the "minutesAwake" and "awakeDuration" data fields represents.
We are looking at the sample data below that has value for "minutesAwake" but 0 for "awakeDuration";
"body":{ "sleep":[ { "awakeCount":0, "awakeDuration":0, <=== "awakeningsCount":7, "dateOfSleep":"2016-02-27", "duration":31740000, "efficiency":98, "isMainSleep":true, "logId":10990988607, "minuteData":[ {REDACTED} ], "minutesAfterWakeup":0, "minutesAsleep":513, "minutesAwake":11, <=== "minutesToFallAsleep":5, "restlessCount":7, "restlessDuration":16, "startTime":"2016-02-26T21:46:47.000", "timeInBed":529 } ], "summary":{ "totalMinutesAsleep":513, "totalSleepRecords":1, "totalTimeInBed":529 } } }
The corresponding App record here;
In addition, can you confirm if the "mins awake" in the App record is taken from the "awakeDuration" and the frequency (times) from "awakeCount"?
I'll appreciate any information you can provide. Thanks!
Best,
Mark Salcedo
Answered! Go to the Best Answer.
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.
awakeDuration is the count of minutes in awake state and the value you should use.
minutesAwake is the value for an older algorithm that we no longer recommend using. Fitbit's own apps do not display it.
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.
Hi Jeremiah -- two questions
1 - the awakeDuration is no longer available, should we now revert to using minutesAwake?
2 - minutesAwake seems to be weirdly calculated -- in the "classic" view, it seems to actually be the combination of "restless" and "awake" time -- is this correct? In the "stages" view, what is this number generated from?
Best AnswerI'm wondering this answer to this as well. Any more information?
Best Answer