My Charge 3 is my first fitbit, and since I got it yesterday, I've only had one night of sleep. However, whenever I opened the detail and then back out to the main sleep dashboard, my detail had duplicated itself. It does this every time I open the detail. I deleted the spare entries, but now I lost last night's entry. Is there an ETA on a fix? What's the best way to handle this?
Can you explain exactly what you mean by "my detail had duplicated itself". Where exactly do you see this? Is it registering that night's sleep for other nights? Or does it then show you slept twice as long for the same night?
Best AnswerFitbit app dashboard > Click to open the "Sleep" portion > Click on the individual detail for a night's sleep (or, I have just discovered, have my screen turn off on the main Sleep dashboard) > and, if clicking on the individual detail, click back
It is accepting it as the same day. Now that I have turned my screen on and off a few times while typing this, I am up to 1 day, 6 hours, and 40 minutes of sleep for today alone. However, if I try to delete one of the duplicate entries, it deletes all of the entries. Because I just got my fitbit, I don't know if the deletion thing is just for the log it is duplicating, or if it would somehow delete all sleep logs over a period of days.
I've never seen or heard of such thing happening. Does it happen again for today?
Something worth trying is to look at the sleep data on the fitbit.com dashboard - click 'Dashboard' near top right of this page. That generally accurately shows the data from the main database, even when there are phone app issues.
It seems like it would be an issue with the app, rather than with the tracker. Sometimes strange app problems can be fixed by deleting, then reinstalling, the app; be sure you remember your account and password as you would have to log back in again; that would not cause any data to be lost.
If the issue persists, it might help of you could post a screen shot showing the duplicated data.
Best AnswerI have the same issue and also using fitbit charge 3, android app.
Easy to repro:
1. go to sleep details (shows sleeps for this week)
2. select sleep from today (or any other day)
3. go back to sleep details per week
result:
sleep logs for that week are duplicated.
4. If i open sleep details for specific day again and go back to sleep details per week, my logs are now tripled.
Btw, they are duplicated just visually in that view. When i go back to my dashboard, and go to Sleep week overview again, there are no duplicates anymore unless i repeat repro steps
I have the same problem on my brand new Charge 3 with 2.83 Fitbit for Android app. When clicking on the sleep log, then going back, the sleep log is duplicating in the list view. I can tell the data is not duplicated by going to the previous page, then back to the sleep page: now I correctly only see 1 entry.
BTW, don't delete these duplicates because this will remove the actual data (there is only 1 data row for that night, trust me). Just navigate back to the previous page, then go back to this sleep page.
Anyways... Fitbit, please FIX!
I just got a fitbit versa and it does the same thing. At first I thought it was only happening with sync, when I synced the 2nd day I got duplicates, 2 entries for each day. When I synced the 3rd day I ended up with triplicates for each day. I tried deleting duplicates and lost all of the data 😞 But then after all the sleeps were deleted, the next day I had a new one and had same issue as everyone else, I went out of the app, went back in, and there were duplicate entries again. So frustrating, for the price we pay for this thing not to work. Is there an update that will fix it? I don't see any updates, but I'm still learning to use the fitbit watch and app.
After using my Charge 3 for a week, this bug didn't bother me as much. It isn't fixed, but what happens is the duplicates will all be after your first day's log. In other words, let's say you have 2 weeks worth of logs, you won't see the duplicates until after the 14th row.
Ok, not great, but at least this only bugged me for the first week or so...
BTW, do NOT delete any "duplicate" logs... because that is real data you want to keep.