My Versa 2 is tracking my calories too low

[Christina137]

HI I recently discovered my fitbit is showing very low calories count. After a several hours of digging and reading blogs here, I finally found out it was due to the app somehow changed my weight to 3kg!!! 

However, after I changed back to my normal weight, my calories count is still very low compared to when it was used to be. For example, 2 week ago i did a 5 hours hike on day, I remembered my total calories burned on that day was 3500cals, but it is now only showing 1900!!! I have then again checked all my other stats (age, sex, height and weight) and make sure all is correct. 

Anyone can help me fix this?

Moderator Edit: Clarified subject

[MarreFitbit · Accepted solution]

@Christina137 Thanks for stopping by in the Community Forums. Thanks for trying to troubleshoot the inconvenience with your Versa 2 before reaching out. I understand where your concern is coming from. 

While reading your post, I was wondering if the day you changed back your weight details to what was initially, was the same day you got the 1900 calories burned for your hike activity? Are the 1900 the total of calories burned for the day? If this describes your issue, please note that this an expected behavior. Since you changed the weight details after starting a day, your watch did a calculation based on what you previously had plus what you had now after editing your weight. 

Have you test your Versa 2 today? Is everything going fine now? Is it calculating your calories accurately?

Hope this clarifies your inquiry. 

[Christina137]

@MarreFitbit 

Hi, Thanks so much for the reply. 

Thanks for the reply. I did the hike on 14/08 and that day I burned 3500 cals. I believe at that time my Fitbit was functioning normal. I only changed my weight back today 10/09 (the drop in calories only happened yesterday), then I looked back the calories burned on 14/08 and it is now showing 1900cals and all the previous daily calories burned  also seems a lot lower than what it was used to be. 

So you think this is normal? going forward my calories count should be all correct then?

I am planning to do a test tomorrow since I didn't do any exercises today. I will report back if it corrects itself. 

 though it would be a shame not be able to reference back the old calories count 

(sorry for the repeated message, first time user, didnt realise i need use @  :))

[Christina137]

Hi, after a several days of testing, I can confirm the cause of the calories drop is just the glitch in body weight. It seems all is back on track. 

Though, it is a shame that I couldn't get the old calories count anymore. 

[OMAinFL]

I have a very similar problem. I have had my new Fitbit versa 2 since Thanksgiving. I’m very used to Fitbit as this is my fourth one. The first two weeks my calories were on track during my Boot Camp workouts. Then  last week they are only half of what they are supposed to be or what they normally are and I am working out just as hard. It’s very discouraging to see the great numbers up on the boards and then look at your watch and see that it’s not recording properly. I did call the telephone number and spoke to a man in Support!. He had me restart my watch and restart my phone. Tomorrow I will see if that works when I go back to Boot Camp. Any other suggestions from you would be welcomed. Thank you so much.

[Christina137]

@OMAinFL Please check your bodyweight, height and all other personal details are correct. For my case, I realised Fitbit changed my bodyweight to 3kg! that is why the calories counts were so low, because the calories are calculated based on those personal information. Once I changed to my actual weight, it is all fine now. I read many other people  from here found the same bug, hope yours can be resolved soon. 

[OMAinFL]

Thank you. I appreciate your feedback. I have not changed one thing nor have they changed anything on my app. It’s only three weeks old and the first two weeks it was doing fine. Just a little frustrated

Sent from Yahoo Mail for iPad

[Christina137]

@OMAinFL oh, I dont think it is because of you. it is a system bug, sometimes it just changed it by itself. I know very annoying!