Sleep Logs show '0 time asleep'

[KateFitbit]

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.

Please note I have merged several threads with this 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. 

[Flavio1110]

Same here... three days in a row already. 

[Wynlucky]

Same here tried to upload screen shot unable to 🤪....

[Hypapante]

Hi, I am fairly new to Fitbit (since Feb-2018) and it has worked well until this morning where I now have the same issue as a lot of you: my android recorded: 0 mins sleep, yet it had the graphs and recorded the time I fell asleep and woke up. I can see a lot of people have this issue but I can't see any answers. Does Fitbit not offer any solutions?

[claupcsilva]

Same here, a couple of minutes ago. 

[Janine18]

I'm having issues aswell, just set up my versa yesterday. Wore it to bed last night it recorded when I went to sleep and when I woke up however when I go into see it in more detail I can see first screen of sleep pattern but when I try to scroll through to see awake times the app crashes and I have to reopen the app (I have tried uninstalling and reinstalling the app but hasn't fixed the issue). It is showing me the graph of my sleep but saying 0 minutes asleep and 0 minutes awake. Would agree with other comments looks like a bug or a fault has happened

[Oygunn]

I have just the same problem to day. The sleeping tools has been a unstable th last week. Like showing the same day three times before it has settled. 

[ironmanjt]

Same here today for the first time. Based on the number of people this is happening to today something is up 

[Louiseeaster]

Same happened to me this morning. Very frustrating. 

[LuMo]

Add one to the club, first time it's happening (Charge 2)

[retsmit]

Same problem here

[LuciaT]

Same problem here. Can you let us know when the patch will be available?

[cjrb]

Hi,

Same thing here. It has recorded the sleep but shows 0 min in the log and the app crashes when you soon on the graph.

[Rebajay15]

Same here this morning also for the Charge 2. Over 7 hrs slept down on dashboard, though no awake minutes which is wrong.  Breakdown detail shows graphics on chart but no minutes or % stats displayed. 

[MMANV]

Hi, same problem. After receiving the rollover update from Android 7 to Oreo, the sleep time is saying '0' beside I can see the time I slept and stages, no total hours or percentage per stage. Same problem with my wife's device. 

Is fitbit app ready for Oreo? Maybe not fully. 

[ScubaShotz]

I get the same issue on iOS with Charge HR2. If you edit the sleep log and then save it again (you don’t have to actually change anything) then that brings the stats back. Obviously not ideal though and definitely a bug!

[Oygunn]

I haven't Oreo..

[Sunniva.96]

Unfortunately, this didn't work for me on my android phone. Edited the log, but still no stats.

[Dexterity]

Me and my BF are both having this issue today aswell.

[cjrb]

That worked well for me. I had to do it a couple of time, but now it's back.

Thanks a lot!

[Foodlady]

This happened to me this morning. Sleep tracker is my favorite part of the app. Showed me when I went to bed, when I woke up, total hours slept without accounting for wake up time. Then it recorded 0 minutes. Seems to be the same problem you all are having. Just a day later.