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

Editing sleep does not update Sleep Score

Help! Editing sleep does not update score!!

(Charge 6, iOS App, device and phone updated and restarted). Editing sleep data changes everything EXCEPT Sleep Score which would be server side on Fitbit’s end.

All these issues with sleep tracking are pointing me to other more robust platforms. I sure hope you can get the Sleep Score not updating issue resolved quickly!

Thanks

 

Moderator edit: clarified subject.

Best Answer
17 REPLIES 17

I have the same problem, Pixel Watch 4, Android, app and device updated and restarted.

Editing my sleep does not update the sleep stage graph nor does it update the sleep score. 

Best Answer

I'm having the same issue.

Best Answer

Hello @WoodsyGuy , @yassie_j , @birdy42 

I suspect there's something going on with the Sleep algorithm in the Fitbit app. I also had edited one of my sleep logs earlier this week after my sleep was split into 2 logs. Usually, I will see an updated sleep score and sleep stages graph. However, the Fitbit app didn't show my updated sleep stages graph. It was missing sleep stages for the first part of my sleep. What's unusual is that I was able to see an updated sleep stages graph on my Pixel Watch 4, including the missing section. 

For now, please submit this issue using the Feedback option in the Fitbit app:

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

The feedback reports are received by the team for review. 

I will continue to monitor the forums and will report back if I see any updates to this issue. 

Rieko | N California USA MBG PE

Best Answer

I’m having the same issue.  I have been messaging Fitbit Support on X about it but they want me to erase my data and add it back which I don’t think will help since it’s clear from these posts I’m not the only one having problems so it’s not likely related to my device. Hopefully they will address this at some point it’s pretty frustrating.

Best Answer

Same issue for me, started happening about 10 days ago.

Impossible to re-calculate the score by adjusting sleep log...

Versa 4, Android app, OnePlus 12

Best Answer

@Imrewired   I tried deleting my sleep log for last night, then adding it back.  This DOES NOT work.  I got sleep patterns, not sleep stages.

Fitbit is aware of this issue, but I don't know when it will be fixed.

Laurie | Maryland
Sense 2, Luxe, Aria 2 | iOS | Mac OS

Take a look at the Fitbit help site for further assistance and information.

Best Answer

Just to clarify when I added it back manually I did not get sleep stages either.  But when I deleted two sleep sessions - both after midnight so on the same date - I was surprised that once I synced it automatically added one sleep session that covered both of those that were deleted and included sleep stages. I think that worked twice for me.  It may not work for you but regardless you shouldn’t have to go that route if it’s working properly.

---

I received a message from Fitbit support yesterday. They’ve begun rolling out version 4.55 of the Fitbit app which they believe may help address the issues with the sleep logs.

Best Answer

Hello @Imrewired 

Thanks for sharing that information that you got from Support. Please let us know when you receive this update and if it fixed the sleep log issue. 

If I find confirmation that this app update has the sleep log fix, I'll report back. 

Rieko | N California USA MBG PE

Best Answer

@Imrewired  @RiekoC   I downloaded v4.55 for iOS and it didn't fix the issue for me.  The sleep stages graph and Benchmark data didn't change.

Laurie | Maryland
Sense 2, Luxe, Aria 2 | iOS | Mac OS

Take a look at the Fitbit help site for further assistance and information.

Best Answer

I have installed v4.55.1 on Android and the issue still persists for me as well. 

Best Answer

I am also unable to edit sleep after the update.  I shared our experience with customer support on X.  The suggestion from the “team” was to offload the Fitbit app from iPhone storage and then reload it.  After doing that I attempted another sleep edit and still no success.  I reported that back and will provide an update if I hear anything.

Best Answer

It's definitely a server side issue, even downgrading to an older version of the app that used to work does not help work around the issue

Best Answer

Around Mid-October, editing sleep hours no longer updated the timeline or sleep score. Tried every fix such as restarting phone and Pixel 3 watch, clearing the cache, reinstalling the app. Nothing worked. Clearly, there's something wrong with the app.

Please fix the problem folks!

Best Answer

I have a Luxe and am having the same problem with editing sleep. Sleep-tracking is my sole reason for having Fitbit Premium, and I often edit my sleep time because — when the sleep timeline graph does not show at least a moment of “awake” time on each end of the graph — I know they’ve missed some of my sleep. I’ve done this for three and a half years, and my edits were always reflected on the graph as well as in the score. But starting in mid-October, neither of those measures changes. Yet I know the data is in there because, when I look at the heart rate graph for that night’s sleep period, it does include the time added by my edit.

Best Answer

I just received notice that Fitbit has a new update version 4.56 that is expected to fix what they referred to as a bug. They expect the version 4.56 rollout to be completed by Friday November 14.  I have not received the update or forced it so I can’t comment at this time but wanted to share this update.

Best Answer

I have updated to 4.56 and see no  improvement in the ability to edit sleep score.  I have had a Fitbit device since I preordered the 1st generation in 2007(?)  I have a small wrist and feel the Apple Watch is too large but I may give it a try at this point.  Any other suggestions?

Best Answer

For the record I did share my experience in my “DM string” with Fitbit support on X and received an immediate response that they are aware of the problem and are working on it so at least they are acknowledging the problem still exists after the latest update.  

Best Answer