01-05-2016 05:00
01-05-2016 05:00
I purchased a Fitbit One yesterday, and immediately started feeling like it was very inaccurate. It was recording way too many steps and adding "floors climbed" when I hadn't climbed any floors. I decided to wait until the morning and see what I got when I woke up. I checked it when I woke, and it had reset to 0 steps. I put it on by clipping it to my belt when I got up, and in walking the 15 or so steps to my back door to let the dog out, it recorded 47 steps. I then took it off to do some research online, and I reset the device. When I went to put it back on, I checked it and it still said 47, and just the motion of picking it up off the table and clipping it to my belt jumped it to 90 steps. I reset it again, and then took about 8 more steps and it now reads 120.
I understand that this product is not going to be 100% accurate, but this type of inaccuracy is unacceptable to me. Do I have a defective product, or is this just the type of performance I should expect from my $100 Fitbit?
01-05-2016 06:15
01-05-2016 06:15
Hi @LP1435. No tracker, regardless of the make, will give you 100% accuracy. The industry's accepted margin of error is 5% and my experience with Fitbit One trackers is that they usually come well within 5%. But you're right, the wide error factor that you're experiencing with our One is not normal.
When you did the restart, did you get to see the Fitbit 6.60 on your One's display? If not, the restart was probably not successful. So I would plug it in the charging cable again and to a USB port on your computer and repeat the restart process two or three times if need be, holding the button down 15-20 seconds, until you do see the Fitbit logo followed by the firmware vesion number.
If your tracker needs a firmware update, please follow the instructions in the following link: How do I update my tracker?
Hope this helps. Please let us know how it goes.
TW
____________________________________________________________________________
(If this tip solved the problem for you, please mark this post solved, as this will be helpful to other users experiencing similar issues.)