10-17-2025 09:23
10-17-2025 09:23
Hey gang.
Unfortunately, it seems my Sense 2 has stopped calculating my sleep correctly. I've had it for 2 and a 1/2 years, so not a noob - but the sleep stages and sleep score are not recalculating when I try to edit sleep. One of the cool parts of the Fitbit is that you can go back in and edit sleep. I have historically used this edit sleep and delete sleep features and it worked pretty flawlessly most nights on recalibrating and recalculating. Now when I try to edit sleep, it just goes back to exactly the same bar of sleep stages, the same sleep score and nothing recalculates?
This only started in the last week to 2 weeks, if that helps locate the change, or update potentially on your side. Something you can roll back.maybe? If not, I have no idea what the issue would be, and appreciating your support. Thank You!
10-27-2025 10:27 - edited 10-27-2025 10:47
10-27-2025 10:27 - edited 10-27-2025 10:47
I have this exact issue with my PW4 and Pixel10. 2-3x a week my sleep "starts" on the sleep tracker at the time I took a pee break. It used to be easy to fix by editing the start time (in my case) to the actual start time of my sleep - I usually ask my wife what her watch says as a reference. Then it expands the sleep range and adds in the missing data. No longer!! It's empty space - it just adds the extra sleep time as if I had no awake time (never mind no REM/deep/light sleep). My score always remains the same too.
This is unacceptable and needs to be fixed ASAP as I never had an issue until the past couple of weeks (3x in the past week.) Hopefully this can be fixed soon.
10-27-2025 12:35
10-27-2025 12:35
10-27-2025
13:53
- last edited on
11-07-2025
08:27
by
AndreaFitbit
10-27-2025
13:53
- last edited on
11-07-2025
08:27
by
AndreaFitbit
Not just the Sense2. I have a Charge4 and it does the same thing. I use an iPhone.
---
Can’t see how to add a new comment, so am replying to one. I finally got hold of a live person! Wow! Only took 2 days and 100 clicks on non-helpful stuff!
anyway, I was told to set my watch to “sensitive” and give it a try for a couple nights. Odd recommendation because when people do this and have issues, they tell you to change it to “normal”. We will see what happens.
To get a live person, go to http://support.google.com/fitbit/gethelp?hl=en
Let us all know if it works!
10-31-2025 08:48 - edited 10-31-2025 08:50
10-31-2025 08:48 - edited 10-31-2025 08:50
Did it again today - infuriating!! I had 2 sleep stints (according to Fitbit), but I really only had one with a rollover and a small amount of awake time. It split my night almost equally into 2 - 3 hour and 25 minute stints. I tried to splice them together by deleting the 1st stint and then extending the "fell asleep" time to the time of the first (now deleted) stint. It did NOT fill in the activity of that 1st sleep period. Oh well, Fitbit now sucks. Instead of a high 80's to 90 score, I got a 75. I'm investigating alternate apps to analyze my sleep since this is now broken and they're not responding.
10-31-2025 13:21
10-31-2025 13:21
So, after getting a “live” person, I have an open “ticket”. What they told me to do (set watch to “sensitive” sleep mode, it still did not work and I’ve had the same issue, only it never tracked my “first” sleep period. I sent them an update yesterday with screen shots of the issue before and after I edited my sleep. I have not heard back. I also wrote a nasty review in the App Store, but no response there yet either.
If everyone having this issue would use the link I provided in an earlier post, and opened a ticket with this issue, (and wrote a nasty review in the App Store) maybe it would get their attention since complaining here gets no attention at all.
I’m waiting for a reply. Will update when, and if, I get a response from the “powers that be” at Fitbit.
11-02-2025 11:03
11-02-2025 11:03
Same problem here. Since mid October. Clearly, there's a problem with the app.
Fitbit/Google - Isn't it time that you geniuses fixed this problem?
11-02-2025 20:23
11-02-2025 20:23
Thank you @Heartlady214 for your diligence on everyone's behalf. Yes - that 'Sensitivity' suggestion is just asinine - if anything, it would just make the splits of sleep times worse! lol..
That said, I will endeavor to go the link you originally provided for Support through Google - and like you suggested, everyone of us should! Keep fighting for followup since you've started already and their original 'suggestion' did not work. Cheers!
11-06-2025 19:25
11-06-2025 19:25
The sleep app has been off the rails since the end of June. There was some negative press I read about how Fitbit counted too much resting time as sleep time. So basically Fitbit switched everything over to only sensitive mode. Normal mode is no different and no longer really exists even though it shows as an option. The Fitbit help desk folks are usually in India somewhere and most don't even know what we know.
It's so bad that now when I am up for maybe 30 minutes at the very most like last night it often shows up as and hour and 45 minutes of awake time and docked my sleep from 7 hours down to 5 hours 15 minutes. Insane! The sleep algorithm is BROKEN.
Fitbit NOW allows us to edit and adjust the times. In the past (I'm a 10 year Fitbit user) it would only give you credit if it was legit sleep or close to sleep like quiet and still time in bed. Now, however, for the past few weeks, it gives you whatever you ask for. So if I realize I've been screwed over by an hour and 15 minutes it let's me put it back during the edit. I guess it's their way of letting us fix what they broke. It counts in your weekly and monthly averages. But if you get weekly email charts from Fitbit like I do, it does not show up with the edits calculated in.
In the end it's all messed up. No moderators even bother to show up. Many threads on this same subject in other departments have been capped off from any new comments including mine back in July (Sense 2 threads). There was one announcement in the IOS threads how Fitbit has made sleep more accurate. But that was it. And again all they did was make sensitive mode mandatory.
Hoping they somehow fix this because it is truly broken.
The ONLY thing I can do to get even close to accurate is take my full sleep times and score and break it down into two different shorter sleeps rather than one long one. So deleting and editing is what I have to do. In that case it shows you a far more accurate rendering including awake and restless time which is far more accurate than what sensitive mode default view gives us. But you get no sleep stage breakdowns or sleep score.
I'm considering buying the Ring 4 just for sleep because it is rated better than anything else and probably keep my fitbit for other things including as a watch.
It's a shame what Google has done to Fitbit since taking over. Got rid of challenges, got rid of old sleep graph, made a new less user friendly app layout, now this new sleep settings change and more with very little improvements anywhere. And no moderators chiming in on any of this.
11-06-2025 20:51
11-06-2025 20:51
Thanks again @Heartlady214 for providing the Live Support link in your post above!!! I have now contacted them and spoke to someone. Insanely easy to do, btw!
I detailed the issue I raised here originally in the 1st post, copied these details into chat and got a live person to call me in the same 5 mins.
Basically, after reiterating what we're all going through, he came back and said they are aware of the issue - that engineering has been notified - and that they hope to have a fix in as part of their upcoming Nov 9th release. I'll of course, only believe that when I see it - but crossing fingers here. I have my doubts as I was told that if it isn't fixed by this Nov 9 update, that I should call back, give them the Case#, and would be escalated to a higher department. I hope that isn't just them kicking the can down the road, but we will see!
11-07-2025 06:20
11-07-2025 06:20
Same here. Nothing has improved with whatever update they did.
11-09-2025 09:40
11-09-2025 09:40
Yeah - I've got a Charge 5 running the Android app. I've chatted with Agents twice now, and just get the runaround with no admission that this is a new problem. I've been referred to Fitbit Help (https://support.google.com/fitbit/answer/14236402?hl=en&sjid=16004521064637540552-NA%23zippy=%2Chow-...) It states: "Note that for devices that receive sleep stages, if you extend your time asleep, you may notice gaps at the beginning or end of your sleep stages." Last agent told me that "...as the fitbit devices aren't medical devices can have those gaps." The last comment from Agent was "I don't know why you are experiencing those gaps only since this year.
It might be because a recently update and it will be fixed later on other update or as soon as possible." I'm not holding my breath!
11-10-2025 13:42
11-10-2025 13:42
I've been a Fitbitter for 12 years and many models. Having the same issue since I installed the latest firmware update. Can anyone else confirm that, or is it since a software update? Hoping software, since that's more fixable.
If I go back to sleep and then edit to add the additional time, it no longer recomputes the graph, sleep score, or metrics. It just says that I slept for exactly the time longer that I tell it, even if I've been up walking around, so that's definitely not accurate.
The only work-around is turning off Bluetooth so it doesn't sync until my final wakeup. Then, it calculates everything properly.
11-10-2025 13:44
11-10-2025 13:44
Samsung, so it's not an OS-centric problem. Is it since the firmware update for you, or a software update? I'm trying to pin that down
11-11-2025 06:39
11-11-2025 06:39
I am having the exact same issue. It's also been going on since sometime in October. I'm on a pixel 9 with the charge 6
11-11-2025 11:10
11-11-2025 11:10
Well, a couple of days late, but Fitbit just updated to 4.56. Hopefully this issue was addressed in the update.
Best Answer11-11-2025 19:23
11-11-2025 19:23
Just updated to Version 4.56 on one of our phones. Will know in a day (night) or so if the new version helps 🤞
Best Answer11-11-2025 19:46
11-11-2025 19:46
Skeptical but still hoping maybe they will fix it with the promised next update. Tech support really doesn't seem to ever help these kinds of issues. They really are no better than us here. And rather than promise a 11/9 update fix they should have at least mentioned rollouts don't happen all at once whenever they are released. They roll them out over time. I haven't seen anything yet. And no changes yet, I can still edit sleep times at will. I did notice my awake time last night was half of what it's been each night over the past few months. But no way to know for sure until several more days of sleep can be calculated. It was at least good to hear tech support say that this issue is known by engineers and being worked on. That's basically the best I've heard of so far on any of this, which this entire ordeal has been just really really bad on Fitbit's part. Why mess up sleep at all back in late June? Then when it all goes haywire why not have moderators say something here? Anything?
11-12-2025 09:59
11-12-2025 09:59
Sadly, ain't a dayum thing changed.
I am traveling for the next 3/4 days, but will take this up with them when I'm back. In the meantime, visit that link and yall can talk to someone yourself on the phone or chat, in minutes:
http://support.google.com/fitbit/gethelp?hl=en
11-13-2025 04:17
11-13-2025 04:17
I don't know how to post here but I'm so angry that this is happening. My Fitbit is useless for sleep. My cpap time is more accurate. Goodbye Fitbit if this doesn't get fixed soon.
11-13-2025 05:54
11-13-2025 05:54
I’m having the same problem with the Versa 3 watch on a IPhone 16Pro. I love Fitbit but since Google took over it’s becoming worthless.