Inaccurate Sleep data

[Jody222]

I have had the Pixel Watch 4 since its release. I have been a Fitbit Premium member (using the public preview) since that time as well. Since getting it, my sleep logging has been very consistent. Starting on 3/24, it shows me awake 90+% of the night .. and that is NOT correct. It has the right going-to-sleep and wake-up times, but the data is trash.

I have the SoundCore Sleep A20 and A30 sleep headphones, which I wear every night. They also monitor your sleep, and there has been no change in the numbers reported by them .. only the fitbit has tanked. The numbers reported by them are consistent with no major changes, as I had with fitbit starting on 3/24. (Not debating how accurate the headphones are, just that they are/have been consistent).

I have factory reset the watch, cleared the cache in the app, uninstalled/reinstalled the app, and even tried the sensitive vs. normal sleep logging settings, but nothing has made a difference.

I know that Google just announced the updated sleep-tracking algorithm, and I fear that it is the cause of my issues.

Is anyone else seeing worse sleep tracking since the upgrade?

*Note before it gets mentioned.. Nothing has changed. Same sleep environment, same watch band/tightness (though I have even tried tighter), same location on arm, and the same bedtime routine.

Moderator edit: formatting

Moderator Edit: Clarified subject

[eMonkey64]

Mine same. 

And I have a Polar Loop that has shown no significant change. 

[Jody222]

So todays amazing numbers are ..

5 minutes of light sleep
7hours 13 minutes of awake (in bed).

Amazing!

[RiekoC]

Hello @Jody222 , @eMonkey64 

I agree that the most recent sleep algorithm update seems to have issues. Like you, I'm not seeing the same sleep data ranges that I used to get only a week ago for me. 

Please submit this issue using the Feedback option in the Fitbit app:

• Tap your avatar in the upper right of the Today page in the Fitbit app
• Tap Feedback in the menu that opens
• Complete the prompt and submit

Although it's likely that you won't get a response, we've gotten confirmation that the team reviews every submitted feedback report and uses the information for issue investigation. 

[Jody222]

Thanks for the reply. I have already done that. I am putting it out in as many places as I can in hopes of getting it seen. As it stands, it's not worth having the watch [for sleep] .. and in fact, it's ruining my previous numbers and averages.

[Jody222]

So today's (4/4/26) amazing numbers are ..

19 minutes of light sleep 7hours 43 minutes of awake (in bed).

Of course, it also shows me awake DURING that 19 [staggered] minutes of sleep. Basically, it show me awake during the entire duration of my sleep, with a couple of random light sleep ticks, but also still awake.

[Jody222]

My sleep numbers for today (4/5/26) are:

5h 34m of awake
1h 22m of light sleep. No deep or REM.

Readiness score of 12.

[eMonkey64]

I've had terrible results everyday until last night. 

Fitbit 6hr 27m compared to Polar 7h 15m.

Maybe the issue us fixed - let's hope. 

[Jody222]

I hope you're right. I'll watch for a [hopeful] change in the next few days.

[AJE67]

The sleep algorithm is definitely not working for me - my recorded sleep data is so wrong it is not believable. Really degrading my experience of Fitbit which is a shame as I’ve worn one for more than 10 years. The Ai coach said that the new algorithm didn’t work for me, that it was frustrated by it and that I should consider using a different technology !?!

[Jody222]

I actually have a case open with FitBit. I had already done all the troubleshooting the Level 1 tech could do (reload app/factory reset watch, etc), so it was escalated to a higher team. Just waiting to hear back. Sent them several screenshots of before 3/24 and after .. so we'll see. 

[eMonkey64]

I started a case yesterday and they said should be better (fixed?) in new release of the App "67".

Its due before 17-April. 

[Jody222]

I started a case with them on the 4/7 and got an email today that they are aware of the issue and hope to have it resolved "soon". I didn't get a version or date as you did, but it does seem they know.

[Jody222]

So, I received Fitbit 4.67 on Monday April 13th, went to sleep, and the sleep data on the morning of the 14th was still TRASH. Guess 4.67 wasn't the solution they promised. 

[eMonkey64]

I still don't have 4.67 but they told me to get back to them if it didn't work. 

Very disappointing that this is going for so long. 

[Jody222]

the REALLY bad part is, I reported the 4.67 didn't fix my issue and this is the reply I got

---

Thanks for reaching out to the Fitbit Customer Care Team.

Following the team's response, it is recommended that you continue using the device. Please ensure that data is syncing to the application, as this will resolve the issue.

For your reference, your case number is <...>. If you need more help, you can contact us again and reference this case number, or reply to this email to reopen your case.

Regards,

Adriana

The Fitbit Customer Care Team

---

so basically, we are closing the ticket, but just keep wearing/waiting. The whole part about making sure the data is syncing is crap, too, because I have sent her MANY screenshots of sleep data from the app.

[Jody222]

so, I replied and complained that they were closing the ticket even though it's not resolved, and got this in return:

---

Hello Jody, 

Thanks for reaching out to the Fitbit Customer Care Team.

We understand you are experiencing this issue with the app, and we appreciate you providing screenshots. As this is a widespread problem, please be advised that our team is actively working on a resolution, and we ask for your patience until the app is updated. 

For further inquiries, please do not hesitate to contact us by phone or by replying to this email.

For your reference, your case number is <...>. If you need more help, you can contact us again and reference this case number, or reply to this email to reopen your case.

Regards,

Adriana

The Fitbit Customer Care Team

---

So, it's now classified as a "widespread problem".

[Cindy_lou]

I have to spend time deleting and reentering my data it's such a mess. Shows I'm awake in the night when I know I was sleeping.  

[Maffs]

I have a Fitbit Inspire 3 - I've had issues since Fitbit app update on 24 March.... sleep data records most of night spent awake, as little as a few minutes asleep, and most nights No REM or Deep Sleep times recorded..... very frustrating. This needs sorting.

[eMonkey64]

I've had quite different outcome.

I had 3 cases with Fitbit Support and they have decided to replace my Pixel 4 watch.

I don't think my device actually has a problem given that other users have exactly the same issue.

Each time it pushes the timeline out ...
a) Wait for next update ... update come, no difference
b)  Factory reset your device ... resets everything, takes time to work-out that there's no change
c)  Replace device - device sent ... still waiting for device to arrive but my expectation is that I'll go through the whole new-device process and the problem will still exist

Interestingly, sleep uses HRM. I was on treadmill recently for 30 minutes - during that workout the HRM decided I was at an extreme HR for 22 minutes. This models what happens at night - HRM decides I wake-up and stay awake the rest of the night. I had a chest HRM for the workout and I did not get to extreme HR at all during the workout. Something dramatically wrong with Pixel HRM.