09-09-2014 06:17 - edited 09-09-2014 08:19
09-09-2014 06:17 - edited 09-09-2014 08:19
My sleep efficiency is registering as 100%, 4 out of the past 7 nights...
Dashboard clearly shows my 10-14 awake periods, however the sleep efficiency is still 100%. This has just started happening. Any suggestions?
-Callahan-
Answered! Go to the Best Answer.
09-09-2014 06:36
09-09-2014 06:36
I noticed it started happening a few of days ago.
Go to the log / sleep area, click on EDIT, (like you were going to adjust the start/end time) and without changing anything click on "update". It will re-calculate the sleep efficiency.
09-09-2014 06:36
09-09-2014 06:36
I noticed it started happening a few of days ago.
Go to the log / sleep area, click on EDIT, (like you were going to adjust the start/end time) and without changing anything click on "update". It will re-calculate the sleep efficiency.
09-09-2014 07:52
09-09-2014 07:52
Thanks! This works, and I went back and fixed the last 6 days. The "awake" times are captured but not calculated.
09-09-2014 08:14
09-09-2014 08:14
Editing and saving works great but I have to do it EVERYDAY now?
Is there a better solution or maybe a fix from Fitbit?
This is a little annoying
09-09-2014 08:53
09-09-2014 08:53
That is the best fix short of Fitbit getting their act together. Two touch...edit, save! Beats deleting and re-entering. Thanks!
09-09-2014 09:46
09-09-2014 09:46
Thanks for that. I couldn't understand how I could wake so many times, and get 100% efficiency! Shame that it has to be done each day.
09-10-2014 05:30
09-10-2014 05:30
the more annoying little work arounds they make us do, the more customers they will lose especially sincew there are so many new and more sophisticated tracker competitors!
@Leonardo wrote:That is the best fix short of Fitbit getting their act together. Two touch...edit, save! Beats deleting and re-entering. Thanks!
09-10-2014 10:58
09-10-2014 10:58
Hi everyone:
I want to apologize for the inconvenience that this Sleep Log bug is causing you.This is a known issue that has been escalated to our engineering team. Please see Allison's update about this issue here. If you are seeking more information or updates about this concern, please visit that thread, which will be updated periodically as we receive more information about this.
I'm going to close this thread to new replies. Please refer to the main thread for ongoing discussion about this.