06-23-2016 11:26
06-23-2016 11:26
I've noticed my Surge is not tracking sleep accurately. It tracks only some of my sleep time and some nights it tracks nothing at all.
Yesterday, I restarted the device. After restarting, it logged too much sleep last night. It does, in fact, show a big block of time towards the end of my tracked sleep time last night where it shows I was restless / awake. Within that block of time, it shows a block of sleep time. It was on the charger during that time and I was in the shower. The "restless / awake time" prior to that and after being on the charger was actually awake time when it should not have been tracking sleep because I was up and walking around (and later, I was at work).
How can I get Surge to start tracking sleep properly again?
06-24-2016 06:22
06-24-2016 06:22
Update: It took awhile to update this morning, which is what I saw yesterday before it finally showed the sleep included time that I was not asleep (so it was not showing the sleep because it thought that sleep was still in progress). So if you look for sleep data before it thinks you wake up, there is none at all... it has to totally finish before it records anything apparently. So despite that it took awhile to show up, it is now there. It must have taken awhile after I woke up (yes, I did sync at least 3 times after waking up), but it does actually show sleep time that starts and ends at about the right times. I don't know why it worked last night, so not convinced it will work again tonight, but at least this is encouraging. I'm still open to ideas since I'm not sure if it is consistently working properly again or if it was a fluke.
06-27-2016 11:12
06-27-2016 11:12
It is doing better now, but still missing some sleep time. Aside from restarting again, does anyone have a suggestion as to how to get sleep tracked accurately?
08-04-2016 12:29
08-04-2016 12:29
Hi @midwesterner85 it is a pleasure to have you in the Fitbit community with us. I'm glad to hear the sleep is now more accurate. Thank you for performing a restart to troubleshoot this issue. Have you tried to change the sensitivity mode of your Surge? You can find this information in the settings of your device. It looks like this:
Hope this helps!