RESOLVED: Sleep Log: 0 Time Asleep

[ErickFitbit]

Fitbit Update 04/18/2018: Hey everyone -- Our team has resolved this issue, which means you should be able to sync your sleep logs from last night and the app will display your actual hours slept as opposed to 0 time asleep.

Thanks for your patience as we worked to the get this resolved as quickly as possible. I will be closing this thread as the issue is resolved.

---

Fitbit Update 04/17/2018: We're aware of an issue where users who logged sleep may see their time asleep as 0 minutes.

We're working on getting this resolved as quickly as possible. In the meantime, we have a workaround:

Workaround:

• Manually edit your sleep log (hit the "edit" button at the top right of the app and change your start OR end time by 1 minute.
• Save the change
• This will recalculate your sleep and should resolve the issue.

I will have more information for you once this has been fully resolved. Thanks for your reports and continued patience as we work on a fix.

[leblek85]

Sorry if this has already been asked...
Ionic has been working perfectly fine for the past few weeks, but last night it recorded how long I was asleep (6hr 48min) which shows up on the dashboard, and I can view the detailed sleep cycle, but underneath the sleep cycle graph the Time Asleep says 0 minutes, and each sleep stage also says 0 minutes. I tried clicking on the sleep cycle graph for more detailed information about each sleep stage and each time I did this, the app crashed.

Has anyone had this before? I've restarted my phone twice now and it's still doing it. If I uninstall the app and reinstall, will I lose all my previous data? Sorry if that's a really dumb question, I'm not that tech savvy.

[jumpenguin]

Same here.  

[KAE53]

I have the same problem. Just updated to iOS 11.3. Is this a coincidence?

[leblek85]

I have a Samsung S8 and last update was done over a week ago.

[jumpenguin]

Mine is Samsong Note 8, and I actually updated to the latest today after noticing this issue, hopeing this update might fix the problem.

[Buffy_fitness]

I’m an iPhone user and mine is doing the same.  I’m going to reboot my watch.  Maybe it is the update.  

[jeandenys]

I'm having the same issue as well 

[Vastator]

I think this is a Fitbit server issue - I saw this same issue posted today across multiple Fitbit products. Good news is, nothing wrong with our devices and it's a big enough problem that I hope Fitbit will fix ASAP. Bad news, on the other hand, it might be  a big problem! 🙂

[Ogre123]

Same 

[limeric]

happened today only after 3 months of usage. Sleep schedule recorded but no analysis on sleep stages. graph is shown but no minutes are indicated (show 0m is all 4 sleep stages). pls advice how to resolve?

[Ksddrph]

Did you get this fixed and if so, how? My Fitbit shows what time i went to sleep and what time i woke up, but shows 0 time asleep

[leglalien]

Same here 😕

[inffy]

I had this happen today too. The way i got it fixed was to edit the times manually (changed the gone to sleep time with 1minute and the same for the wake up). Then I saved the "new" times and it did calculate the sleep stages after that

[inffy]

Change the times manually for example change them by 1 minute. This fixed it for me today

[leglalien]

Wow, this worked for me too 😄

[Ksddrph]

I'm not sure I understand. You changed your time in the app? Did you add a minute to your time you went to sleep, woke up, subtracted a minute? How did you manually change it

Sent from my iPhone

[leblek85]

Oh awesome! Thank you inffy, this worked for me as well 🙂

[inffy]

---

@Ksddrph wrote:
I'm not sure I understand. You changed your time in the app? Did you add a minute to your time you went to sleep, woke up, subtracted a minute? How did you manually change it

Sent from my iPhone

---

Click the sleep row where it shows the 0 amount -> then in the upper right corner there is a pen icon -> click it so it shows you the times. Change those times (like add a minute to both) and then save it.

[Anirt]

It registers more often than before. It helped turn off the fitpay / code lock on my Fitbit. But I still have some days with issues. Like today.