I have been using Fitbit with My Fitness Pal for several months with no problems. I only log food on My Fitness Pal and only track steps on Fitbit, but normally the Fitbit tracker accurately shows the data for the food that I have entered into My Fitness Pal. All of a sudden, Fitbit is showing crazy calories. For instance so far today, the food that i have eaten and entered into My Fitness Pal add up to about 1050 calories. Fitbit is showing 4800 calories. Earlier when I had listed about 500 calories, Fitbit was showing over 3000 calories. It keeps telling me that i am over my calorie budget. Any ideas of how to correct this?
The food entered in My Fitness Pal is showing up correctly in My Fitness Pal.
Thank you
I'm having the same problem with the sync to MFP. So far, the dashboard says I've eaten 20,038 calories today, while MFP has me at 1,565 calories.
Apparently I didn't account for eating an extra four pounds of lard somewhere... ![]()
Hopefully this will be corrected soon; earlier syncs today went just fine.
(And it would be nice if Fitbit was syncing with Weight Watchers correctly, but I'm not holding my breath on that one.)
Same problem here, with fitbit and MyFitnesspal. Fitbit had about 30 fictional entries in total, distributed among the meal categories. I deleted all of the inaccurate ones, and now the food "more details" page looks less discouraging, but the dashboard has some trouble knowing which number is larger.
Thank goodness for this community to share our issues on. it helped me calm down a bit!
Best AnswerOMG!! fitbit says I ate 3300 calories more than I did - multiple snacks, dinners and lunches -
My dietician is going to think I had a massive binge! I am currently on a Very Low Cal Diet - this does not go unoticed - hopefully it can be fixed?
Best Answer
Best AnswerThis issue just happened to pop up the same day that I did the most recent app update for Fitbit, so that's crazy, isn't it?
Best Answer
Nbrim, thank you for the information.
I wonder if it is MyFitness Pal or FitBit that is the problem. The problem for me started on October 21st (Wednesday), and on that day my phone updated FitBit to version 2.15.
Best Answer