Fitbit Sense 2 cutting off sleep

[L-Fra]

Good morning. Wondering if anyone else is having this problem. For the last several days (consecutively), and frequently for many weeks, the app has been cutting off anywhere from 1.5 to 3 hours of sleep from the beginning. For example, last night went to bed at 8:30 and right to sleep. Alarm went off at 5:30, checked the stats about 45 minutes later, and it had me going to bed at 2:30 am. When I tried to correct it to 8:30pm, it gave me the all-too-frequent message that I couldn’t correct it because there was already a record there (which didn’t show anywhere.) My Sense 2 is working well, so I’m assuming there is a problem with the app. Any thoughts/advice?

Moderator Edit: Clarified subject.

[DavidFitbit]

Hi @L-Fra Thanks for stopping by, I hope you're doing well.

Let me help you with the accuracy of sleep tracking on your Sense 2. Thanks for the troubleshooting steps you have already performed.

When you move too much during a period of your sleep session, it can make your device believe you are not sleeping.

Take a look at our help article What should I know about Fitbit sleep stages? below the section "What are some tips for getting a good night's sleep?" and see if those suggestions help you with this behavior.

If you find trouble while attempting to modify your sleep log, please ensure you are modifying such log as instructed in our help article How do I add, edit, or delete Fitbit data and activities? below the section "How do I edit or delete sleep logs in the Fitbit app?".

I hope this information will be helpful for you!

[Ga1ileo]

This a happened to me as well, but between 3.00am and 4.40am.  Sleep record showed me starting sleep at 4.40am and showed I was also asleep between 11.30pm and 3.00am.  If it was movement surely it would have shown sleep from 11.30pm with a period awake between 3.00am and 4.40am as one continuous record?  My heart rate during this missing period was normal and consistent with what I would expect if I was asleep (which I was).  I don’t believe this was down to movement.

[L-Fra]

Thanks for getting back to me. Being older, I do get up during the night, but often it's not until 3 hours later or more. When I go to bed, I typically fall asleep within 5 or 10 minutes, and very little movement after that. No alcohol, no caffeine, no sugar closer than 6 hours before bed time.

For example, a couple of nights ago, I went to bed shortly after 8pm, and fell asleep quickly. Woke up at 1145, went back to sleep about 6 minutes later. Didn't get up until 6am. When I checked my stats an hour or so later, it had me going to sleep at around 1145, with an accurate wakeup time, but when I tried to change the start time, got the message about not being able to add a log here, as one already exists for that time period (if it does, I sure can't see it anywhere). Seems to me to be an app problem, but I'm no expert.

The thing is that this has only been happening for about the last three months. Before that, if there was a time that needed to be altered (which didn't happen often,) all I had to do was open the app and change the time. Didn't see the "Can't save sleep. A sleep log already exists in this time period" message. 

---

Well, it's a consistent problem. Last night, went to sleep by 830, woke up early (530), and it cut off the first 90 minutes (with the usual "can't do this" when I tried to fix it). Even with the newest version of the ap. Seems a problem that won't be fixed.

[L-Fra]

As a follow-up to an earlier posting, the problem continues. Every night, from 1.5 t0 3 hours are cut off from the beginning of my sleep records. For example, last night went to bed at 830, woke up at 630, but the sleep record said I went to bed at 1100pm. Tried to correct it, but got the "there's already a log there," which is a bit frustrating, as it doesn't show anywhere. Deleted the log and tried to correct it with a new log, but no dice there either ("log already exists"). This is a new Sense 2, which is working fine, and this problem has been a plague with both my phone and my tablet (currently using the phone.) Everything else with the watch seems to work fine, and this was also a problem with my previous watch, so it seems this must be a problem with fitbit. Any suggestions?

[DavidFitbit]

Hi @L-Fra, thank you for the details provided.

When you try to modify your sleep start time, do you do it by just changing the start time? Could you please provide a screenshot of the message you receive while attempting to do it? I appréciate your time in this process.

Have you tried erasing the full log and setting fall asleep and wake up time all over again?

Thanks in advance for the screenshot.

[L-Fra]

Good afternoon and thanks for getting back to me about this issue.

I have tried to correct the problem by correcting and/or removing the start
time error, and about 90% of the time, I get the attached message. I have
also tried erasing the entire log and setting the times up again, and
again, 90% or more of the time, I get this message.

I’ve tried this with both my phone (with the newest app) and my tablet,
both the same result. It’s a bit frustrating.

[L-Fra]

No surprise. Today, cut off the first two hours again. Same response when I tried to correct it. I know it’s a minor thing, all things considered, but it does seem like something that could be fixed.