Awakenings Count discrepancy

[FedericoArg]

Hello,

We have received several complaints from our users that we are importing the Awakenings Count incorrectly from Fitbit. After conducting our research we have determined that the Fitbit Web Report shows inconsistent information to the User. 

Could you explain why the "Times awakened" is different from the "Times awoken" values and what each means?

Also, could you detail us how to obtain the "Times Awakened" as the API only returns the "Times awoken"?

User: https://www.fitbit.com/user/2CJN73 

https://www.fitbit.com/sleep/2015/03/17 

API Values:

{

  "sleep-awakeningsCount": [

    {

      "dateTime": "2015-03-17",

      "value": "12"

    }

  ]

}

Regards,

Federico

[SunsetRunner]

Thank you for reporting this, I have forwarded it to the appropriate internal team.

[FedericoArg]

Any update about this issue?

[Michael]

@FedericoArg Any chance this is another case of you having multiple sleep sessions on the same day, and the graph you are looking at on the right is only for the "primary" sleep, but you are looking at the detail for a secondary sleep session?

[FedericoArg]

Hey Michael. Thanks for replying.

I have checked again one more time and I only have 1 sleep session showing up. The weird thing is that not even the Fitbit Dashboard is consistent with the awakenings. 

Also, I am concerned that no one from Fitbit has look into this issue or provided an explanation.

Federico

[SunsetRunner]

---

@FedericoArg wrote:

Any update about this issue?

---

We have pinged our team responsible for this again. Sorry for the inconvience, we hope to get an answer for you soon.

[SunsetRunner]

I'm still awaiting a response from the team but it appears to be a known issue with an open issue (internally). I don't know when it might be fixed.

Update: The team has acknowledged the issue and will work on a fix soon.