Cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Time Asleep is not calculating correctly

ANSWERED
Replies are disabled for this topic. Start a new one or visit our Help Center.

Fitbit Update: 9/30

 

Hi everyone,

 

We're aware of an issue where your time asleep is being miscalculated. 

 

You might have noticed your sleep duration has increased and time awake/restless are being included in the time asleep calculation. In addition, some of you might have seen sleep duration had increased, but now it has changed back to the previous calculation. 

 

As mentioned, we're aware of all these sleep miscalculations and are working to identify a resolution as quickly as possible. 

 

Thanks for your patience. Once we have identified a fix or resolution, we will update these threads. 

Want to get more steps? Visit Get Moving in the Health & Wellness Discussion Forum.

Best Answer
1 BEST ANSWER

Accepted Solutions

Fitbit Update: 10/1

 

Hi everyone!

 

The bug we experienced with sleep calculations has now been resolved. You should all see your sleep duration will not include time awake/restless anymore. 

 

Thanks for your cooperation. We appreciate all your efforts in reporting this bug to us! 

Want to get more steps? Visit Get Moving in the Health & Wellness Discussion Forum.

View best answer in original post

Best Answer
35 REPLIES 35

All my sleep records were changed this morning!  Yesterday my sleep record was 5 hours 10 mins.  Today it becomes 8 hours 56 mins!  All my previous records were grossly boosted as well.  What happened ! 

 

I noticed that it reports only the dark blue sessions.  Now it seems to have included the light blue sessions.  Why this change?  It upset all my sleeping records !

 

Best Answer

It seems now short awakenings (for example 1 minute) are not counted in total awake time, while before every minute counted as restless went into the total awake time. So it's like we "slept more" and we will "sleep more". Maybe it's more accurate as it's now

Best Answer

Same thing happened to me - usually have between 90 and 270 minutes of restless/awake time every night averaging 3 - 5 hours sleep per night.  Now all  my records are showing total time in bed rather than time asleep.  This happened last week, but then corrected itself.  I'm using Flex2.  Husband is using ChargeHR and his records have altered too - although even before the change he was getting 7 - 8 hours per night, so not a lot of difference there.  The graphs on dashboard still show the sleep time rather than in bed time.  Probably a glitch with the software.

Best Answer

I was also flabbergasted today to see my sleep records, and simply cannot accept the current version!  For example, on Wednesday it showed just under 4 hrs sleep for the night before, now it says just under 6 hrs sleep for the same time.  Believe me, it cannot have been 6 hrs as I was feeling wrecked all day!  For Tuesday it now says 9hrs 15mins instead of 5.5 hrs - no way!


But I also have the FitBit app running on my computer (without a smartphone it's the only way to be able to force syncing when I want).  For today's sleep the app says 5 hrs 44 mins, vs the website saying 7 hrs 20 mins.  So the two bits of software do not even agree.

 

I rarely sleep well and the previous interpretation of sleep (over the 4+ years on Fitbit) made perfect sense to me.  Now the interpretations on the website version are simply unbelievable.

Best Answer

I've just had the same issue today, but it's displayed wrong in both the Dashboard view and in my Android app.

 

Something similar happened already a while ago, so hopefully it'll be fixed again soon.

Best Answer

All of the past recorded sleep hours have changed?!?!  The ENTIRE sleep history is now different, going back YEARS!!  It also isn’t accurate, as it is now counting “restless sleep” as actual sleep.  I don’t know what is going on, but this is very frustrating.

Best Answer

All of a sudden, last night, the time asleep changed. It is not subtracting restless time at all. 

Best Answer

Exactly!  What's the point in telling us the "time slept" is just the "time in-bed" less "time awake" (usually only a few minutes), by including all the "restless sleeping time" into "time slept" !  It is totally meaningless!

 

I do hope this can be rectified asap !!! 

Best Answer

The same thing happened to mine.  It changed all the previously recorded sleep as well.  I track on sensitive and rely on looking at the changes -/+ in sleep more than the actual time I was in bed.

Best Answer

Same things happened to me today as well.  Following this thread in case there is a fix that becomes available.  It changed all my prior records as well.

Best Answer

Same and it’s awful. When it gives you the time you went to bed and the time you woke up you can calculate the difference yourself. I don’t want to know the time between when I went to bed and when I woke up, I want to know how much of it I was actually sleeping well. Bring back the actually helpful relevant info!! 

Best Answer

FitBit seems to have recently changed the algorithm they use for determining sleep stages. I used to consistently get 50-60 awake minutes every night. Now I’m seeing 15-30 minutes. Wondering if I had changed or the app had, I looked back at my data from months ago - it now also says that I was awake for 15-30 minutes, so they retroactively changed past days too. Is this something others are seeing?

Best Answer

I'm seeing the same thing today. How can we notify Fitbit of this issue?

Best Answer
0 Votes

I watched in confusion and horror this morning as my Alta synced and changed every sleep value in my log!! It’s incredibly frustrating - I haven’t updated anything on my phone, app, or Fitbit, so why the sudden change?!?! For those of us with sleep issues who rely on this data to help, this is a step backwards and it makes me feel like my Fitbit is useless now. I basically get to wake up every morning and see the number of hours of sleep i SHOULD have gotten taunting me on the screen, instead of understanding the amount of time I was actually able to sleep.... sounds like a great start to the day!!

Best Answer

I’ve noticed my sleep log entry shows I’ve had much more sleep than what’s tracked on the sleep graph. See below both photos of today’s sleep- one showing I slept for 8hrs 9mins, the other 7hrs 40mins.

 

This is frustrating because for a while now I’ve been trying to improve my average hours of sleep per week. But it turns out the graph I was checking was out by a lot!! Please can you advise how to fix this? Or when this will be fixed?

 

F5DE2346-9A4B-4D47-88F9-F3BDD7F5C0ED.png

FF27449A-4553-434C-A6DC-16034AE3E322.png

Best Answer

 Hi I have a Fitbit flex. Ever since the last iOS update, the sleep tracking math is off. It gets the time I go to bed and the time I get up correct, but either the time asleep or the time restless/awake is wrong. From my own analysis, I think it is the time asleep number that is the incorrect one. 

 

I’ll give you an example. Last night I had a bad headache so I went to bed at 7PM. I got up this morning at 8:30AM. This means that my time in bed was 13.5 hours.  The Fitbit got this right. The app says I was restless/awake for 4.5 hours and I believe this is also correct. Before the app update, the time listed under “time asleep” would’ve been 9 hours.  Yet today it inexplicably lists 12.75 hours. The math doesn’t match.

 

Sure I can do the math myself. I can subtract the 4.5 from the 13.5. But since this is only started since the app update, I thought you’d wanna know this was a problem so you can fix it with the next update.

 

Thank you for your help.

 

I have iOS 12.3.1 on my iPhone. 

 

Moderator edit: updated subject for clarity

Best Answer

I am having the same issue! Aggravating!

Best Answer

Same problem here, as well.

Best Answer

My sleep totals are also incorrect but the sleep time displayed in the graph is correct. My profile is set to sensitive which seemed to match my actual sleep and it did not include the restless time in sleep totals. Now it appears that total time in bed is what is being reported.

It looks like Fitbit has yet another bug in their latest update.

Best Answer