01-14-2022 21:55
01-14-2022 21:55
I've been using Fitbit for years, and the Sense for two years. In the last few months, I have noticed that there is a huge discrepancy in the Dashboard between two screens: The "Food" screen that
shows "Cal in vs. out", and the 'Today" tab, which shows an overview of each tile on the dashboard. Here is an example. At 9:29 AM before I have even eating anything, the "Today" screen says, "Start Logging Your Food," and "635 calories left." (Currently I'm on the "Kinda Hard" plan with the calorie counter set at "Sedentary" so I earn more calories as I move around during the day.) At the exact same moment, when I click into the "Food" screen, it's showing I'm in the "Green" Zone with "0 calories in, and 571 calories out," and that I've "Reached My Goal for the Day."
Another example: An hour later, once I've eaten a breakfast of 231 calories, the "Today" screen says that I have "431calories left for the day," while the "Food" screen says that I am in the Red Zone, at "231 Calories Over for the Day." Basically it's telling me that I should not have eaten any calories.
This issue started after one of the software updates several months back, and it's very frustrating. Could someone help? Or is this a bug that the software engineers need to fix? Happy to send screen shots if helpful. Thank you
03-21-2022 06:05
03-21-2022 06:05
Mine is doing the same thing, the tile on the “today” page is saying a very different amount of calories left than on the “food” page. The number shown on the “today” page seems to be more accurate based on todays activity. This just started happening after doing an update. So frustrating. This is the one of the most important features on the Fitbit for me and it’s currently useless!
03-21-2022 18:58 - edited 03-21-2022 19:00
03-21-2022 18:58 - edited 03-21-2022 19:00
I am having the same issue! My watch says I burned 1700+ calories, but the cal in/out chart says 1100+ making it hard to track how many calories I have left and it says I'm over eating, but I'm not.
Looking at my previous logs, it looks like the issue started Saturday. (Tuesday and Wednesday my watch was dead, so ignore those days.)