Data inconsistencies on API sleep list

[vlsantos]

I caught some many errors while comparing detailed data with summary and totals on https://api.fitbit.com/1.2/user/-/sleep/list.json

1- sleep.levels.summary.asleep.count always 0

example: all my set of data

2- sleep.levels.data.wake below 180 in the wrong place and other wake with the same date but different value in shortdata

Exempla1: start: 2018-08-01 03:09:00.000 end: 2018-08-01T09:10:00.000

3- sleep.levels.summary.asleep.minutes wrong sum (when comparing with sleep.levels.data and shortdata)

Example1: on start: 2018-07-06 00:49:30.000 end: 2018-07-06 07:25:30.000 expected: 82 actual: 79

Example2: on start: 2018-07-09 01:50:00.000 end: 2018-07-09 10:50:30.000 expected: 140 actual: 137

4- sleep.levels.summary.light.count wrong sum (when comparing with sleep.levels.data and shortdata)

Example1: on start: 2018-07-06 00:49:30.000 end: 2018-07-06 07:25:30.000 expected: 11 actual: 24

5- sleep.duration missing 30 seconds (when comparing with sleep.levels.data and shortdata)

Example1: on start: 2018-06-23 14:06:00.000 end: 2018-06-23 15:07:30.000 expected: 3690000 actual: 3660000

Example2: on start: 2018-07-07 01:05:00.000 end: 2018-07-07 09:07:30.000 expected: 28950000 actual: 28920000

Example3: on start: 2018-07-08 00:11:00.000 end: 2018-07-08 08:23:30.000 expected: 29550000 actual: 29520000

6- time in bed missing 1 minute (when comparing with sleep.levels.data and shortdata)

Example1: on start: 2018-07-11 03:11:30.000 end: 2018-07-11 10:23:00.000 expected: 432 actual: 431

Example2: on start: 2018-07-28 01:46:30.000 end: 2018-07-28 08:42:00.000 expected: 416 actual: 415

Example3: on start: 2018-07-30 12:41:30.000 end: 2018-07-30 16:08:00.000 expected: 207 actual: 206

7- sleep.levels.summary.asleep.count always 0 (when comparing with sleep.levels.data and shortdata)

example: all my set of data

[Gordon-C]

Hi @vlsantos

Would you please private message me your client ID and the user ID with the wrong data.  I'll check it out on our end.

Gordon

[vlsantos]

@Gordon-C@  done!

[Gordon-C]

Hi @vlsantos

My apologies for the delay in getting back to you.  It took me a while to research all of your questions.  #1 and #7 appear to be duplicates.  I've created a ticket to have this problem fixed.  #2 I'm still researching.  The others appear to be known issues.