05-05-2017
15:03
- last edited on
09-09-2020
09:49
by
MatthewFitbit
05-05-2017
15:03
- last edited on
09-09-2020
09:49
by
MatthewFitbit
Dashboard shows calories left as one number then when I go to log food screen, the calories left is a different number. I have no deficit. This just started today after an update.
06-22-2017 23:02
06-22-2017 23:02
Been having the same issue for at least a month or two (possibly longer and I just didn't notice it).
How does a bug like this go unpatched for so long?
06-23-2017 01:21
06-23-2017 01:21
Ya I have to say am just extremely disappointed with the whole thing, no one "official" has actually responded to this thread.I can definitely say that my Charge 2 will be the last Fitbit product I buy.
06-23-2017 09:23 - edited 06-23-2017 09:26
06-23-2017 09:23 - edited 06-23-2017 09:26
OK, after doing some more research, I've figured out what's happening here. It's not a bug, it's a feature --just a really poorly labeled feature.
The "calories in / calories left" tile on the dashboard is showing you how many calories you have left based on your intake and the number of calories you've actually burned thus far in the day.
The widget in the food log which looks like a car tachometer, functions similar to a tachometer. It's showing you how you are doing relative to the time of day. The "calories left" is based on how many calories you "should" have consumed (or not consumed) by the current time of day, using some fancy math and historical analysis of your prior eating/exercise habits. In other words, it's a prediction.
If you look at the "tachometer" on the food log page, if the arrow is pointing to the left third, you're under budget, relative to the time of day. Middle third means you're "in the zone," and if it's pointing to the right third, you're over budget, aka "ahead of schedule" and need to slow down on the calorie intake to avoid ending up over budget for the day.
So the tachometer is actually kind of a useful idea if you keep a semi-consistent eating/exercise schedule (I don't). But the proper gauge of how many calories you have left in absolute terms is the dashboard tile.
Hope this helps someone else.
06-23-2017 10:31
06-23-2017 10:31
The calories remaining should equal on both screens which it did until the early May upgrade. .the problem is as you enter your food it's using the lower calorie number which is the incorrect # ..this causes you to eat way less if you want it to show on the app as on or under budget...only Android users are having this issue. .iPhone users the calories remaining on the tile and dashboard match...
06-23-2017 12:13
06-23-2017 12:13
I must admit myself and my better half did wonder if it was like you say, just a poorly implemented idea. However after Lisajay linked up her chat with the customer service rep am not so sure :(. Plus Baisdent says only Android users are haveing this problem. At the end of the day we don't know, I guess all we can do is read the tile that works and hope some one can help clear things up for us. But I think tbh your prob right it's just a really crappy way to implement it : /
08-16-2017 17:28
08-16-2017 17:28
Bumping this because it's still not fixed
08-17-2017 01:04
08-17-2017 01:04
Tbh I just stopped posting,eveyone either thinks its ment to do it.Or know Fitbit wont fix it sadly
08-28-2017 12:53
08-28-2017 12:53
I'm new to fitbit charge 2 always used the up24. Must admit I'm disappointed with this flaw and that is what it is. Come on fitbit it's not a good start!!
08-29-2017 09:02
08-29-2017 09:02
You're not the only one Debs, we've had a lot of problems so far. Tiles always moving about and re-appearing after being hidden. Trying to enter weights into the calorie tab and it refusing the numbers ( they keep swapping back to the original ones ) The heartrate tracker isn't tracking 100% of the time, it misses out hours worth of information.
Dissapointed in fitbit, customer service is brilliant but trying to get their tech department to get off their arses and we seem to get updates not actually doing anything or can't find any software patch notes.
I did dearly hope this was a bug but it seems to be either low priority or they're just calling it a 'feature' now.
Dissapointed, so much so I think my Alta2 and my partners Charge2 are the last Fitbit will see of us. Especially seeing as we've both gone through an extra leather strap a piece ( £60 ) in about 5 month period.
10-17-2017 10:14
10-17-2017 10:14
Thank you for this, I have the same problem and it's an essential part of weight loss knowing how many calories are left in my budget
03-06-2018 07:33
03-06-2018 07:33
Guess what?
It's STILL a problem!
Bump!
03-08-2018 06:51
03-08-2018 06:51
wow, thought this thread dead and buried because of the lack on interest from Fitbit! Thank you for the little bump there Kalvan!
Looks like this 'feature' is here to stay, because streamlining a UI that was fine is more important than getting the numbers clear that people want.
03-08-2018 18:38
03-08-2018 18:38
Right..all you get is the programmers are aware of the issue...how about"fix it" !! I was going to upgrade to the ionic but no way until this issue is addressed.. won't hold my breath, just my $.
03-09-2018 15:07
03-09-2018 15:07
I don't blame you.
I bought an Alta HR along with a leather strap accessory because the standard plastic 'sports' one keeps bringing both me and my partners arm out in a rash after a week of wearing it. The leather strap snapped at the join between the Fitbit and the clasp as it did on my partners too, so they were a waste.
Since then we've both bought second hand straps from Amazon and haven't had a moments trouble with them, even if they only cost £5 instead of the £35 to get an official one. Which advertises as 'leather' but fails to mention anywhere ( That I've noticed at least ) that it's faux, PU Leather.
03-31-2018 16:16
03-31-2018 16:16
still nothing Fit bit? this is driving me crazy too! I agree with the folks who say Fit bit won't get anymore $ from me. If nothing else a brief explanation about which is correct or if one is measuring real time and the other showing estimate for the rest of the day would be nice.
04-17-2018 08:22
04-17-2018 08:22
Still incorrect..a year ago (different phone but still android) my 2 screens matched on calories left. Now they do not. My co worker has an I -phone and her 2 screens match. Very frustrating
04-17-2018 11:34
04-17-2018 11:34
I know right!!! Seems like an easy fix that they continue to ignore 😠
Makes tracking food intake very frustrating... seems to me like a very important tool that they promote to get you to buy a Fitbit, then don't fix the bugs...
04-18-2018 05:03
04-18-2018 05:03
Yes I'm still getting the same erroneous numbers between screens on my Galaxy S7Edge even after reporting it and a few others have in this thread. It annoys me that we're not listened to in the simplest of things that could've just been slipped in a patch.
05-19-2018 15:15 - edited 05-19-2018 15:17
05-19-2018 15:15 - edited 05-19-2018 15:17
Also having this issue. The problem is it's actually incorrect math, full stop. So for example, my tile states:
1,130 cals in - 1,039 cals left.
Burn - 2,357 as of 5 PM
But the actual Food screen states:
1,130 cals in - 2,357 cals out
510 cals left in budget
That food tile is right. If it's 5 pm and I burn about 79 cals an hour. That means 553 for the rest of the day.
If I've presently burned 2,357, that means my total by midnight will be 2,910. A 1,000 cal deficit for me today would be eating a total of 1,910. If I've presently eaten 1,130, then 1,910 minus 1,130 is my cals left - 780.
So 510 is wrong, AND 1,039 is wrong. Over and under by about 250 cals each. THIS TOTALLY DEFEATS THE POINT OF USING A FITBIT FOR WEIGHT LOSS.
It makes the app useless!
06-16-2018 16:01
06-16-2018 16:01
Hi I think they are supposed to be different. Calories on the dash is an estimate if what you have left for the entire day and predicts how many calories you will burn to calculate this. Calories in the food widget are how many you have remaining on what you have burnt off at the particular point of time