Hello,
I've encountered some inconsistencies between the total sleep time displayed in the dashboard and the total sleep amount returned by the end /sleep endpoint. An example sample of the return (with minute data ommited):
{"sleep":[{"efficiency":90,"awakeCount":2,"minutesAsleep":454,"awakeDuration":2,"minutesAwake":50,"minuteData":[],"restlessDuration":48,"isMainSleep":true,"duration":30240000,"minutesToFallAsleep":0,"minutesAfterWakeup":0,"dateOfSleep":"2017-06-02","awakeningsCount":35,"restlessCount":33,"timeInBed":504,"logId":14830648278,"startTime":"2017-06-01T22:23:30.000","endTime":"2017-06-02T06:48:00.000"}],"summary":{"totalMinutesAsleep":454,"totalTimeInBed":504,"stages":{"deep":70,"wake":66,"light":197,"rem":72},"totalSleepRecords":1}}The dashboard:
As can be seen, there is a 15 minute difference from the "minutesAsleep" return and the "Time Asleep" reported on the dash board.
Any insight would be great
Answered! Go to the Best Answer.
Best Answer
Community Moderator Alumni are previous members of the Moderation Team, which ensures conversations are friendly, factual, and on-topic. Moderators are here to answer questions, escalate bugs, and make sure your voice is heard by the larger Fitbit team. Learn more
@dev_t Looks like you're using an old endpoint. See this post about changes to sleep endpoints.
Best Answer
Community Moderator Alumni are previous members of the Moderation Team, which ensures conversations are friendly, factual, and on-topic. Moderators are here to answer questions, escalate bugs, and make sure your voice is heard by the larger Fitbit team. Learn more
@dev_t Looks like you're using an old endpoint. See this post about changes to sleep endpoints.
Best Answer
Community Moderator Alumni are previous members of the Moderation Team, which ensures conversations are friendly, factual, and on-topic. Moderators are here to answer questions, escalate bugs, and make sure your voice is heard by the larger Fitbit team. Learn more