09-26-2018
07:43
- last edited on
09-27-2018
06:24
by
AlejandraFitbit
09-26-2018
07:43
- last edited on
09-27-2018
06:24
by
AlejandraFitbit
I started wearing my Versa this past Friday and the sleep tracking is way off. Telling me I only slept for 38 minutes, or no sleep or a little over 1 hour when I am getting about 6 hours sleep.
Have tried resetting device, changed the start time to a minutes less as was recommended in a prior post, called customer support several times and still no resolution. Other then this, the Versa works well but seeing the other posts with the same sleep issue, I feel that there is something wrong with the product that needs to be addressed by Fitbit.
I would appreciate a remedy for this problem.
Disappointed.
Moderator edit: subject for clarity
09-27-2018 06:28
09-27-2018 06:28
It's great to see you around @frankrhomes.
I appreciate all the efforts in trying to fix this issue. Sleep stages are traditionally measured in a lab using an electroencephalogram to detect brain activity along with other systems to monitor eye and muscle activity. While this method is the gold standard for measuring sleep stages, your tracker can estimate the time spent in each stage in a more comfortable, convenient way.
For more information about this, I recommend checking the help article What should I know about sleep stages?, also I recommend editing your sleep information by following the instructions provide in the article How do I change my sleep history?.
Let me know if you need anything else.
09-27-2018 10:25
09-27-2018 10:25
I have the same problem. The sleep tracking is always far less than it should be.
Ive tried all the tips repeatedly without any change. The sleep tracking was one of the main reasons I bought this,
Disappointed in both the product and support.
09-27-2018 11:39
09-27-2018 11:39
09-29-2018 10:11
09-29-2018 10:11
Every response to this issue from Fitbit has been evasive. I suspect they know the Versa has a design flaw, and no solution will be forthcoming.
09-29-2018 10:27 - edited 09-29-2018 10:38
09-29-2018 10:27 - edited 09-29-2018 10:38
There is a 33 page thread on this in here that they eventually disabled instead of dealing with the issue. See Here..
09-29-2018 10:43
09-29-2018 10:43
09-29-2018 10:46
09-29-2018 10:46
I don't know about the Charge 2, but my Charge HR and my Blaze worked fine.
09-29-2018 11:04
09-29-2018 11:04