Sense 2 is not recognising all of my sleep

[Seafish]

Since the new update, my sense 2 is not recognising all of my sleep. For instance I went to sleep at 10.30pm and woke at 7.30am. My sleep shows that I slept from 3.30am to 7.30am.

How do I fix this?

Moderator edit: clarified subject.

[ManuFitbit]

Hi @Seafish. Welcome to the forums. 

Thank you for sharing with me the information regarding this difficulty that you are experiencing with your Sense 2. Sorry to know the inconvenience.

It's best to have about an hour of complete stillness before your device will register that you're asleep. Keep in mind that there are some factors that may prevent your tracker from recording your sleep. Please make sure of the following:

• If you slept in a position that prevented your device from getting a consistent heart-rate reading or wore it too loosely. For best results, wear your device as described in this help article.
• If you slept for less than 1 hour for sleep patterns or less than 3 hours for sleep stages.
• If your device’s battery is critically low.

If you haven't done so already, please follow the steps listed here below: 

1. Complete a restart procedure.
1. Try adjusting the sleep sensitivity on the Fitbit app and check if you continue to have the same problem.

In addition, please wear your device on your non-dominant hand and monitor it for the next few days.

[SRG-JR]

Hi - has something changed with the Fitbit sleep tracking function? My Sense 2 has consistently recorded my sleep in the mid 80s since I started using it. All of a sudden my scores in the last 10 days are in the 70s and 60s. I sometimes have the problem described by Seafish but only once a month or so. Now, my device shows me sleeping all night but displays poor scores. Two nights ago it showed my score as 60 but said my Daily Readiness was a 70. This seems odd to me. Nothing has changed with my sleep habits and I don't feel like I'm sleeping poorly. But my tracker says I am. What's going on?

[LARoadKing]

I have the same issues even after doing all the resets and restarts!

[danab200]

I am experiencing the same thing.  Low sleep and non accurate awake times.

[LARoadKing]

I have repeatedly performed all this and still have no sleep score nor do I have accurate sleep tracking…very frustrating!!

[TheVinny]

Since others are experiencing this exact same issue at least it lets me know to stop trying to fix it as if something is wrong with my watches or just my app being faulty. 

It is pretty clear that somewhere, someone at Fitbit changed the default sleep setting to 'sensitive'. 

Here's the problem with doing that. When I am sleeping, I understand that I move some, even roll over a few times during the night etc. 

BUT I USUALLY DO NOT WAKE UP EVEN ONCE DURING THESE NATURAL SLEEP MOVEMENTS. 

But Fitbit, on sensitive mode, will count ALL movements as 'Awake Time'. It's there in print.

So, I am getting docked a ton of real sleep time because some genius decided it's better to make all sleep tracking done under sensitive mode now.

I am sure most users don't even realize it. But I did immediately. As have others here on this thread. 

The only Fitbit moderator here on this thread suggests being sure your setting is on normal and not on sensitive mode. But ALL readings are now based on sensitive. There is no difference now when going from normal to sensitive mode. ALL sleep times are recorded in sensitive mode now. And tightening your band does not make any difference. Nor does switching to a different device because I have tried all three of my Sense 2 trackers. It's entirely in the app. Which is why all of my older readings from 2016 all the way to 2025 have been changed by over a half hour per night for every year. They all reflect my times in sensitive mode which means all movements are counted as awake time. It should not be that way because I am still sleeping. Awake time is when I wake up and have constant movement, or get up in middle of night and walk to the bathroom or to get a snack to eat. Not when I am sleeping and rolling over. 

Would be awesome if we could have the option of normal or sensitive sleep mode made available once again just like it's been for the past nine years I've had Fitbits. Thanks.

[AFBSoul]

I noticed the same issue. So every morning I now have to edit my sleep to the correct times.

[LARoadKing]

Do you actually change the values or just open and save. I have tried everything and still don't have a sleep score.

[JaneSp]

How do you edit I tried it says I already have sleep scheduled in that time and it won't let me change anything. My particular problem is every day without fail I have to get up to give medication to my cat and then go back to bed. So yesterday my Fitbit said I slept for 20 hours. I don't know why I just got this thing and I'm trying to figure it out. Today it says I slept for 3 and 1/2 hours which is also not true. I don't know what I'm doing wrong but something and I can't edit the time.

[LARoadKing]

>From the Today screen, tap Sleep Duration. You should see your sleep stages
at this point. In the upper right corner of the screen, tap the ellipsis
(…). You should see a pop-up that contains the link to Edit Sleep. Tap Edit
Sleep and you should see controls to change start and stop times and dates.
As far as I know, that is all you can change.

Hope this answers your question.


Regards,
Kelly W. Brown

[TheVinny]

The only time I don't get a sleep score is if under 3 hours, or, if it is a really bad night, then it will just show me total time with the graph showing only awake and sleep with no score. My wife loves the scores I rely more on total sleep time. Which has been way off now for about a month. Frustrating. I did read somewhere you want to be sure heart rate tracking is on to get sleep scores along with the breakdown of Deep/REM/Awake etc.

[TheVinny]

Yes, as LA Roadking said, you can only edit sleep times through the ellipsis at the top right of the sleep page. BUT, it sounds like what you're trying to add is a new sleep time period altogether which comes from the bottom right tab on that same sleep page. If you try adding a new sleep time that overlaps with a current already established sleep time it will not let you and does say a message about "you cannot overlap sleep times". If that's the case then instead you should edit your current sleep times through the top right corner of the sleep page. You can also delete a sleep time from that same top corner and then add a new sleep time from the bottom righty corner tab once the old is deleted. In the end though, the numbers are still off because it appears everything is now based on sensitive sleep mode which counts all movements as awake time. I've been super loyal to Fitbit for nine years but definitely looked over Apple watches this past Amazon Prime Days sale. Hoping they get this put back where it's been. 

[389sixpack]

My Sense 2 hasn't properly recorded my sleep since ~ July 29th.  What changed?

[TheVinny]

It's all set to 'Sensitive Mode' now. Which is completely ridiculous. It basically means all movement time counts as awake time EVEN IF YOU ARE SOUND ASLEEP. Try switch to sensitive mode, all numbers stay like you see them now. Then go back to "normal Mode' and you can see nothing at all changes.

I've posted on this on another thread and not single Fitbit moderator reply.  Basically you lose about 40 minutes per night now.

[389sixpack]

Thanks. Basically all my REM and deep sleep are missing.

[LeftCoastBlue]

I have the same issue. My Sense 2 sleep preference is set to Normal, but it seems that the default is now Sensitive no matter what I do.

My Sense 2 is almost 3 years old, so I thought that some internal sensor was failing and giving me incorrect sleep results, but all of the other results, including my Premium features, seem reasonable.

Now I'm guessing that the cause of the problems with the Sense 2 is this week's impending release of the Pixel Watch 4. I've upgraded through about 6 different Fitbit devices, going back to the original Fitbit 1, but my continuing use of the Sense 2 is not a source of revenue for Google. Time for them to encourage me to move to their latest and greatest. 

Apologies for the cynical post, but that's life in America these days.

[JaneSp]

I do understand this all too well, being a cell phone user. I particularly
dislike Samsung for this practice. I will never in my life buy another
Samsung product, in fact. I have bought their Note Tablet, the big one,
when it first came out and they made tons of promises. I actually bought it
from a Samsung rep. One thing was they promised to upgrade it t the latest
Android version for a period of 4 years, I think it was. I bought this
thing the first day it was available in our Best Buy, so it was brand new
tech. About 6 months later, they released a new version and my promises
were all broken. Want new Android? Buy the new tablet. I have one of their
refrigerators and I have had nothing but problems with the ice maker in it
since it was brand new. They replaced it for free several times, Always the
same issue, never fixing the problem. The last time the tech, who had been
here multiple times and is from Korea, told me that if it breaks again, I
would be responsible for the costs of replacement. He was leaving, walking
down the stairs to go out, and he turned to me and said "It's a design
flaw. They do not care because Koreans do not use ice." And continued on
down the stairs like nothing had just happened.
I do not even want to talk about the issues with my Samsung not-so-smart
TV. Totally done with that company.
So far the watch is working pretty well once I reset the sleep settings. I
thought about the Pixel watch when I bought this one but it does not do the
one thing I really need, which is the ECG function. I do have a Pixel 8 Pro
so it would be nice to pair it with the watch for lots of reasons.

[TheVinny]

I think it's either a glitch with the app itself or some genius at Fitbit decided to make it mandatory. I lean towards the first because we still have both options available on the app. It's just that only sensitive mode is what's now showing up. I have three Sense 2 watches and all three show same exact thing. I even caved in and went with Premium hoping that would give me the option out of it and NOPE.  It's really a huge mistake on Fitbit's part. I rely on sleep as well as activity to help decide how much to pick it up or back off the next day. But the new sleep numbers are most times so far off it's not even worth paying attention to. For the first time I actually started looking at Apple Watches. Even with nine years of Fitbit data. I can't do the Pixel 4 because IT DOES NOT WORK WITH IPHONE. Just a train wreck whoever's responsible for no more Sense or Versa models to be released and Pixel watches do not work with any iPhone. And I thought Google buying Fitbit would be a good thing. 👎

[TheVinny]

How did you, "reset sleep settings", and make it work? Nothing works from my experience. You get all sleep data in sensitive mode which means all movement counted as awake time. Is just a mess-up on Fitbit's part. 

Our Samsung televisions have been pretty solid. Samsung Ice Makers awful.