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

Data accuracy - Step count changed and calories changed

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

I just got my Ionic yesterday.  I was pretty excited to hit 10k steps today.

 

I hit 10k steps just a few mins ago, got the awesome graphic on the watch and after my watch synced it flashed the green circle for 10k on the app and then it reset my total step count to 2880! The phone, watch and browser dashboard all say 2880 steps now. 😞

 

I went for a run today and got 4,134 steps, so now my run detail page says "4,134 steps out of 2880 taken"

 

On the across the board my daily calories also went crazy, it used to say 2100 cal out and now it says 9425.

 

It there any way to fix this so I get my steps back and my correct calories? I use an Android Samsung S8

 

Capture2.PNGCapture.PNG

Best Answer
0 Votes
1 BEST ANSWER

Accepted Solutions

I spoke to fitbit support and was able to get this resolved.  

 

It turns out I accidentally logged a 40 hour run manually in Stava, this run was pulled in to Fitbit via the app connection and it made all the counts go out of wack.  The solution was to delete the manually logged run from both Stava and Fitbit and now my numbers are looking correct.

 

The support rep recommended not manually logging any activities outside of Fitbit and if you need to manually log something log it in Fitbit and let Fitbit push the activity to your outside applications.

View best answer in original post

Best Answer
0 Votes
2 REPLIES 2

Now every time the watch syncs it gets reset back to 2880.

I had 2886 and 2910 earlier and with each sync the step count is reset to 2880.

I tried restarting the Iconic a couple times but it still goes back to 2880.

 

It also says I have now burned over 10,000 calories today and I have 1440 active mins today. 1440 mins is 24 hours.

 

Please help me fix this, I have had this watch for less than 24 hours.

Best Answer
0 Votes

I spoke to fitbit support and was able to get this resolved.  

 

It turns out I accidentally logged a 40 hour run manually in Stava, this run was pulled in to Fitbit via the app connection and it made all the counts go out of wack.  The solution was to delete the manually logged run from both Stava and Fitbit and now my numbers are looking correct.

 

The support rep recommended not manually logging any activities outside of Fitbit and if you need to manually log something log it in Fitbit and let Fitbit push the activity to your outside applications.

Best Answer
0 Votes