No sleep score for three weeks on Versa 3

[LTP3]

Versa 3 stopped tracking sleep score about 3 weeks ago.  It was giving daily scores regularly, then nothing.  Tried updating and resetting but that did not work.  No change to watch position on hand or sleep positions from when it  was working.  I looked at other questions and responses and am doing everything they suggest but still no results

Moderator edit: edited title to clarity

[CrisVillaFitbit]

Hello, @LTP3 Welcome to the Fitbit Community.

Thanks for informing me about this situation with your Sleep Score on your Versa 3 and for the steps taken to solve this situation.

There are a few scenarios where you might see your sleep pattern (which shows your time asleep, restless, and awake) instead of sleep stages:

- 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 higher on your wrist (about 2-3 finger widths above your wrist bone). The band should feel secure but not too tight.
- If you used the Begin Sleep Now option in the Fitbit app (instead of simply wearing your device to bed). For more information on automatic sleep tracking, see this article.
- If you slept for less than 3 hours.
- If your device’s battery is critically low.

Taking this into consideration will help you getting your sleep score, for more information check this article.

[LTP3]

Thanks for the reply. I know all this information and have followed it but it has not worked after tries and several weeks. As additional information the device always records SpO2, RHR, HRV & skin temp. It has stopped recording breathing rate and sleep score.


Larry Porter
Sent from my iPhone

[RB0186]

I have the same problem with my Versa 3, also for about the last 2-3 weeks. I have also checked the above recommended actions with no change. It seems some investigation is required, not just send the standard reply.

[tbearcrazy369]

I agree! I have had the same issue for the same amount of time. This seems like a universal issue with the platform and not with our individual devices. 

[RB0186]

I think it started after the new app was released?  Maybe there was a software update about the time it started?

[Donuts53]

I too have the same problem like many many others since the last update. I am just still trying to talk to a human for some answers!!!! 

[Burr1]

I have had the same issue with my Versa 2 for the last 2 weeks. 

[RB0186]

I just checked my log & found that this started on 31st October. I want to contact a Fitbit person but cannot - no email, 24-hour chat not responsive, I don't use X or Tiktok.

[Podenco]

I am having the same issue, it also started on 31st of October. It would be nice if a moderator could respond.

[Donuts53]

Hi. We are all having the same problem since the last update. I believe this was intentional by Fitbit to get us all the buy new Google pixel smartwatches as Google has bought out Fitbit!! I am going to be calling my local media station and it will help me if I know the country everyone is from. I do believe this is a global problem with all Fitbit users! I will take it to my newspaper here in Canada!!
Thanks Donna

Sent from my iPhone

[RB0186]

I believe I have discovered why this is happening. I just found a table showing what we get with the free Fitbit App versus the Premium Fitbit App. The free one now only gives the Sleep Score, & the premium one gives Sleep details.  Therefore I am assuming that all of us are using the free app (I am).  I do not intend paying for the premium app because I I not not use 80% of the features.

[Donuts53]

Hi. I don’t think it’s that, as I don’t even get a sleep score, nothing. No heart rate, and now no hourly steps!! They did something in the last update!!

Sent from my iPhone

[frenz1]

I have also been having this issue with my versa 3. In the last week I haven't had a single sleep record properly and I haven't changed anything about the way I sleep. The last few nights I've even made sure to fall asleep on my back so the tracker isn't being moved around and it still isn't working.