09-14-2023
04:21
- last edited on
09-14-2023
04:47
by
MarreFitbit
09-14-2023
04:21
- last edited on
09-14-2023
04:47
by
MarreFitbit
Hi I go to sleep about 10:30pm most nights but the sleep score says that I don’t fall asleep until close to Midnight. I’m pretty sure I fall asleep before midnight.
Is there some setting that I need to adjust?
Thanks
Steve
Moderator Edit: Clarified subject
09-14-2023 04:51
09-14-2023 04:51
Hello there, @SteveL1957. Thanks for stopping by in the Fitbit Community Forums and sharing the details about the inconvenience with your Charge 5. I understand how important it is to you to get your sleep data accurately.
As a first approached, I'd recommend to sync your Charge 5 to the app after waking up. This will help to make sure that all your data is sync properly.
Please note you can set your Fitbit device to track sleep in a sensitive mode. For information about how this setting works, see What's the difference between the normal and sensitive sleep setting?
To learn more about your time asleep in sleep stages, see What should I know about Fitbit sleep stages?
Edit or delete sleep logs in the Fitbit app. For instructions, see How do I add, edit, or delete Fitbit data and activities?
Was my post helpful? Give it a thumbs up to show your appreciation! Of course, if this was the answer you were looking for, don't forget to make it the Best Answer! Als...
09-14-2023 07:47
09-14-2023 07:47
Same here. Used to track ok, but the odd day I have been to bed about 11, woke up to visit the loo, then up about 6.30am, but it shows I only had two hours sleep. Another day only 3 hours sleep. Something has changed. Usually, it would count toilet visits as awake, then revert to sleep, not that I am awake.
09-14-2023 08:19
09-14-2023 08:19
Happens to me occasionally as well, and sometimes I get two sleep logs. I've found, as MarreFitbit notes, that editing the sleep log to reflect the time I actually went to bed solves the problem.
09-15-2023 00:29 - edited 09-15-2023 00:50
09-15-2023 00:29 - edited 09-15-2023 00:50
LOL. After writing my post yesterday, today I woke up to two sleep logs - one from last night (before midnight) for about an hour (with no detailed sleep data) and the other which started a 1 am this morning and resulted in a score in the 50s. So, I deleted the hour long sleep log and then edited the 1 am sleep log to start yesterday at 21h30 (when I actually went to bed) and it picked up an hour of deep sleep, which jacked the score up to 81.
Note: if deleting and editing sleep logs works for you, try doing the same for prior days, maybe even completely deleting a particular log - I found (by accident, really) that I could go back and delete, and then add, a sleep log which was either off or had no detailed sleep data, and it would provide the analysis the Premium subscription promises. I have no insight into why, but this fix does work for me (and I had tried every other possible option the mods suggest).
09-15-2023 18:16
09-15-2023 18:16
Umm why would you edit the sleep logs? That doesn’t sound right
also once I wake up and sync my Fitbit I get a sleep score and then I look and it is different a few minutes later. Example, today after I woke up and synced I saw. Sleep score of 80.then a few minutes later it changed to 75
This has happened a few times
strange
steve
09-15-2023 21:49
09-15-2023 21:49
When I know that I have been asleep / in bed for much longer than the device indicates, I edit the sleep log. So, in the example I cited, I had two sleep logs for the night in question - one for about an hour starting at 21h30 (but without a sleep score nor any sleep analysis, just time asleep) and the other for ~ 5 hours starting around 1 am (with a sleep score and full sleep analysis). So, I deleted the hour long sleep log, then edited the 5 hour log to start at 21h30.
I agree that this shouldn't happen, but it works for me, which is why I suggested it. If it doesn't work for you, no worries.
09-16-2023 13:52 - edited 09-16-2023 13:56
09-16-2023 13:52 - edited 09-16-2023 13:56
Hello @SteveL1957
We edit our sleep logs when our devices don't track properly. The data is there, just not correctly recorded. Most of the time, the device tracks fine. But when it doesn't, we correct the log by editing.
BTW, when you notice a change in your sleep score, consider double checking your sleep start and end time.
There are times when my Charge 5 thinks I'm sleeping when I'm sitting, having coffee, reading posts, or playing games on my Kindle - basically not moving around much. So, my Charge 5 will change my wake-up time to include my morning "quiet" time. Like @BezierNougat , I edit the sleep log to correct my wake-up time, which often changes my sleep score.
Rieko | N California USA MBG PE
09-18-2023 07:38 - edited 09-18-2023 07:38
09-18-2023 07:38 - edited 09-18-2023 07:38
In the past this worked, but I just tried to update a log from 9/12 where I went to bed at 9:28 pm, woke at 4:13am, fell back to sleep at 5:55am and got up at 7:26am. I got an error when I entered start time 9:28pm, end time 7:26am stating, "Sleep could not be logged. A sleep log already exists." This has been occurring lately almost every week, sometimes twice a week. I wish that Fitbit would fix it. I am getting inaccurate weekly reports, and I need to be able to print them out.
09-18-2023 07:54 - edited 09-18-2023 08:07
09-18-2023 07:54 - edited 09-18-2023 08:07
Yeah, I've gotten exactly the same message. Not knowing exactly what is happening with your device from your note: if you have two logs, delete one and then edit the other to start at 9:28 pm and end at 7:26 am. If you only have one log, delete that and start afresh, i.e., add a sleep log starting at 9:28 pm and ending at 7:26 am.
The other thing that could be happening is that when you try to edit the sleep start time, the time actually goes back a day (to the day before) - I didn't notice this the first time I tried to edit a log (frustrating!) - once I did, I realized that the device was trying to modify a log to cover some 30+ hours, which included the log from the day before (apparently that gives the device heartburn). So, to be specific, you need to make sure the log you want (either edited or added) is the only log covering a particular time period, so when you enter the start time, pay attention to the days (start and stop) as well as the times (start and stop).
As annoying as it is, I've pretty much given up on Fitbit fixing these issues, certainly on the C5, now that they are readying an October announcement for the C6 - at this point, I just accept it. But when it comes time for my next tracker (which seems will be within a month after the end of my warranty), it will be with another company.
09-18-2023 08:18
09-18-2023 08:18
09-18-2023 08:27 - edited 09-18-2023 08:29
09-18-2023 08:27 - edited 09-18-2023 08:29
Deleting the main entry is not a problem - you can add a new entry (the data is there).
The problem now is why is your attempt to add an entry blocked - double check to make sure that there are no other sleep logs (even ones without the analyzed data / a sleep score, i.e., just time time asleep) within the time frame (9/12 at 9:28 pm to 9/13 at 7:26 am). Once you are absolutely sure, then try adding a completely new log for that time, paying particular attention to the days, as well as the time - like I said, the first time I got the message about an existing log, I could not figure out why, until I realized that it the new/edited log was starting the day before (e.g., in your case, on 9/11). This morning, for example, I only got a log without the analyzed data, so I deleted that and then added a new log - for some reason, every time I go back to yesterday to add the start time, the device wants to go back to the previous night, so I had to adjust the start day (to yesterday) as well as adding the start time...
09-18-2023 10:10
09-18-2023 10:10
@BezierNougat I'm not sure why editing your sleep log would be acceptable to you as an answer for the C5 not tracking correctly. That's like saying, if you take a walk and the C5 doesn't count the correct steps, just add or subtract some to make it correct. Isn't this the reason we buy these things in the first place? Why do I want to keep track of my sleep myself just to see if the C5 got it right? Defeats the whole purpose of having one doesn't it? Just my opinion of course.
09-18-2023 10:22 - edited 09-18-2023 10:24
09-18-2023 10:22 - edited 09-18-2023 10:24
@6TJS6 see the last paragraph of my prior reply / post in this thread.
09-18-2023 15:46
09-18-2023 15:46
It just goes from "Sep 11" (Mon) to "Wed" (Sep 13), which is 9:13pm - 6:14am. No Sep 12.
09-18-2023 22:57 - edited 09-19-2023 03:39
09-18-2023 22:57 - edited 09-19-2023 03:39
@PayitFwd OK, that is 33 hours and 1 minute. I can only guess that this log is overlapping another sleep log, which would be why you are getting the message.
Assuming you actually went to bed a 9:13pm on Sep 11 and slept for 9 hours and 1 minute, then you need to edit SLEEP END to 6:14 on Sep 12, not Sep 13 - simply drag the date one day back. OTOH, if you actually went to bed a 9:14 on Sep 12, then edit SLEEP START from Sep 11 to Sep 12; again 9 hours and 1 minute - in this case, drag the date one day forward.
Here is a pic of my sleep edit screen: my SLEEP START is Mon 11 Sep at 22:13 and I was in bed for 8 hours and 49 minutes, until 07:02 on Sep 12. If I wanted to get the START to Sep 12, I would slide the date up one day (note, app wouldn't actually let me do this since then - for this sleep log - my SLEEP START would be after my SLEEP END...). If I wanted to change the SLEEP END date, I would first tap on the SLEEP END data (and it would turn blue) and then slide the day (but if, for example, I tried to change it to Sep 13, it would result in a sleep time of ~ 31 hours, it wouldn't actually allow me to do that, given that I already have a sleep log for the night starting Sep 12, and I would get the same message you did...).