Cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Edit Sleep Log Fails Intermittently

Replies are disabled for this topic. Start a new one or visit our Help Center.

When I edit the sleep log using the Fitbit app on my iPhone, quite frequently the new time that I enter is not accepted and it reverts back to the old value. If I edit again then it will usually take the updated value the second time.

 

For example: I woke up at 7:00am, but forgot to press the button on my Fitbit One to stop the sleep interval. At 10:30am I realized my mistake, press the button on the Fitbit to stop the sleep interval, then on the iPhone app open the "Fitbit One" screen and tap "Sync Now". Then on the iPhone Fitbit app sleep screen I will open the sleep log for today, see that the Wake Time is 10:30am, select "Edit Log", tap the wake value, and change the hour and minute back to 7:00am, tap "Save" and within 1 or 2 seconds the wake time reverts back to 10:30am. So frustrating! I repeat the above a second time and the 7:00am wake time is accepted. 

 

This happens all the time! I think you should be able to repeat it in the Fitbit software lab!

This is one of many annoying little software bugs!

 

Best Answer
6 REPLIES 6

It's great to see you around @Mtnbikedad and weird to hear about the inconvenience you are having with your sleep log. I recommend double checking your alarms and also turn them off at the moment of feeling the buzz on the One. You can also check if your iOS Fitbit app is updated by following @MarreFitbit's instructions in the How do I update the Fitbit app for iOS? post. In the meantime, you can edit your sleep logs from a computer by doing the following:

 

1. Log in to your Dashboard and navigate to the sleep log page: http://www.fitbit.com/sleep/
2. Using the calendar date selector, choose the date with the sleep log that you would like to edit.
3. Hover your mouse over the sleep log in question.
4. To modify the start and stop times of your sleep log, click on the pen and note pad icon.

 

I hope this helps, let me know how it goes. Woman Happy

Alejandra | Community Moderator, Fitbit

If you like something I recommended, I encourage you to mark that reply as "Best Answer". 🙂

Best Answer
0 Votes

I've checked my alarms and I have always kept the Fitbit app updated to the latest version. I am still having the issue and my wife has a similar issue when she tries to update her sleep log using her iPhone. I am fairly certain that this is a bug in the iOS version of the Fitbit app.

 

I'm able to update the sleep log using the browser on my computer, by logging in to my Dashboard. However, that's not always convenient and the iOS app should be fixed so it works correctly.

Best Answer

 

I have the exact same problem on my iPhone.  I had an android before and it never had this issue, but the iphone app has issues.  It consistently doesn't work for me.  Any edits I want to save I have to repeat 3 times before it will save on my phone.  

 

I can edit on the web page - but that IS NOT CONVENIENT.  This needs to be fixed!  

Best Answer

Same issue. Had it on the Charge HR for months and, after it broke apart,  with its replacement Blaze. The app clearly is at fault and this annoying bug needs to be fixed. BTW, I keep all updated on an iOS platform. 

Best Answer

I have been using my Fitbit One since October 2013 and never had a problem syncing the Sleep Log until this morning. I have an iPhone and iPad and both are still in the 'Syncing' mode trying to sync the sleep log. Both devices have been updated yesterday.  I tried using the bluetooth and doggle on my computer and still it didn't work. Am I the only one experiencing this?

 

Best Answer
0 Votes

I've found a workaround, but not what I'd call a "solution". When I edit the Sleep Start and Sleep End times using the iOS app, I will wait about 15 to 20 seconds after I change the values until I click on "Save". If I wait to click Save, the newly set Sleep Start and Sleep End values seem to not revert to the original values.

 

Maybe the Fitbit software engineers can try this workaround and investigate the cause of the problem.

Best Answer
0 Votes