I'm having this issue as well and I've also reached out to them. They've stated that they're aware of the issue and working on it but it's going on day three of this issue (consecutively but I've been having the issue off and on for the past two months). I've also tried unpairing the two apps and repairing them and it's not working. This is the longest it has ever been an issue. This morning synced up to about 1k of my steps and then just stopped counting them. It's awesome.

Heartlight441 wrote: »

I was so proud of all my 'earned activity' only to watch it fall only to 500 calori s on mfp. My family is also using mfp and I know I did way more yesterday than some but it doesnt give me creditdue to this stupid issue.

so far your descriptions don't really help decide if you are actually having an issue - or the fact you may be misunderstanding what is happening even when it works right.

If you have your MFP Activity level set higher than sedentary, then it's already expecting you to be decently active.
If the calorie burn Fitbit reports to MFP matches that expectation - no adjustment up.
If certain times of the day it looks better - big adjustment, if other parts of day it's less - lower adjustment.

Hence the requirement to follow advice above about actually posting the numbers the math is done with.

Ya, need to deal with math to confirm if actually an issue you should be reporting along with everyone else.

Go to the details on the Fitbit calorie adjustment. Not the number of calories. But if 2 lines for adjustments there's one issue.

Hold that line on app to get details, or click on blue "i" on webpage to view them.
Screen shot or write down all the numbers/times you see there, along with description of course.
What Fitbit reported and when, what MFP estimated the day to be, what it was using as base.

500 is pretty good though adjustment though, that's more than barely show depending on what kind of steps.
Because again - the foundation - steps by themselves aren't calories - but the distance it represents and pace does.
So that's why you and someone with your exact stats with same steps could be different. Wrong distance being estimated because stride length setting is off, perhaps with both of you.

I have this issue too now, it's strange I hope it's fixed soon!

I've noticed several references to "making MFP sync" in the posts above.

Where is it mentioned that an option in the MFP app to make it sync includes syncing with Fitbit?

Unless it specifically says Sync with Fitbit or maybe Sync with other accounts - that's just syncing the app to the app server and then back to the account server where your info really resides.

Just curious and surprised I'd not caught that reference before. Not trying to take away from the obvious issues that many experience, but I'm beginning to wonder if false expectations are also playing bearing in this.
Like you sync the Fitbit app and get instant data from the device - but left to it's own schedule, it would be longer. Just wondering if more is being expected from the MFP app than actually occurs anyway.

Having the same issue - showed as 500 cal adjustment earlier, which is correct,but now showing as -79 and putting me in the red. Grrr!

@LauraUK2016 & @DoreenaV1975 : When this happens check the math that MFP is using to calculate your adjustment. (Go to the exercise page of the website and click on the little 'i' next to the Fitbit adjustment or go to the diary in the mobile app and touch the adjustment, then touch again.) You should see a screen like this:

If, however, you see two adjustments (website) and/or the MFP Calories Burned number has exercise calories included in it that you didn't log, then you've run into a bug that I think MFP needs to know about. The erroneous math screen looks like this (I never log exercise in MFP):

This bug has been, apparently randomly, hitting a lot of people. I seem to get it about once a week and it's driving me nuts. I have reported it to MFP and I think everyone else that gets hit with it should also report it, so they know that it is a pretty big problem. They do know about it. I believe this is the line about it on their help page (under Known Issues -> Integration Partners): "Bug: Some fitbit users are not seeing their steps syncing correctly and may also see multiple calorie adjustment lines when viewing your Diary on the website."

I just noticed the last week that it's trying to double enter some of my food logs, like in FitBit, I'll have two snack sections when there should only be one. I delete the one entry and then it looks OK again.

Interesting - I made a tech post for trouble on the effect of newer Fitbit daily burn not syncing over very often.

Response said my timezones were mismatched. Huh, never changed them.

I looked - both set to Central time - but one says GMT-5, other says GMT-6. MFP is incorrect during daylight savings time.

But Fitbit device and daily log show the correct time of activity.
MFP manually created workout synced over to the correct time.

So still not sure if that was totally true, or indeed true and almost forced synces work alright, but the auto-ones are effected by it.

Not sure what to change to correct their view of the log files on my account saying mismatched time zones.

Strange.

Wonder what happens for folks in AZ where they don't do DST?

I might be the guinea pig tonight and test changing MFP around.
I'll check back here in case you do it first.

I don't think they are correct though on assessment it was wrong. Because even the adjustment details time stamp is correctly matching what Fitbit was at that time.
I see none of the normal issues you'd get with mis-matched TZ's.

Shoot, only recent one was forgot who had their last 10 min calorie burn kinda of high - but it actually matched if MFP was doing 70 min left to day instead.

heybales wrote: »

Interesting - I made a tech post for trouble on the effect of newer Fitbit daily burn not syncing over very often.

Response said my timezones were mismatched. Huh, never changed them.

I looked - both set to Central time - but one says GMT-5, other says GMT-6. MFP is incorrect during daylight savings time.

But Fitbit device and daily log show the correct time of activity.
MFP manually created workout synced over to the correct time.

So still not sure if that was totally true, or indeed true and almost forced synces work alright, but the auto-ones are effected by it.

Not sure what to change to correct their view of the log files on my account saying mismatched time zones.

Strange.

Heybales this is interesting because as we were discussing in another thread, MFP doesn't seem to be doing an end of day true up for me, and you suspected it was off by an hour, even though I didn't change any settings.

Did you change your time zone (GMT-5 vs GMT-6) or just note the inconsistency? I just looked and mine is the same, one shows 5 and one shows 6.

I have been hit by the random double adjustment bug... earlier today it was giving me too many calories, now it is giving me too few...

This got me thinking about the phone aspect too, with the app. Which I don't use - but perhaps for others.

Phones get their time/date/timezone setting from the towers - unless you select manual override.
This started with the feature phones that had not so complete schedule changing ability.

So some operators at the DST change instead of just changing the time to be correct, would accomplish the same thing by changing the timezone, leaving the time alone.
Some smartphones hide the current settings, merely see the visual end result of the time. Have to uncheck auto-network time to see what it was using.

Well, it visually looks right, until you start scheduling appointments through an app with others in different timezone. Now the app is usually doing some math with timezones, and yours is wrong - so appointments show up wrong.
Or correctly set appointments alarm at wrong time based on current location.

Most carriers are good at running audits on their towers to confirm the change happened, and correctly. Then manually correct towers that are wrong.

Well - you hope they do it right. Because moving into that wrong tower and doing a sync .....

It would be interesting to catch if the apps on device are syncing at certain times when connected to towers giving the wrong info.

There is some very flaky interactions going on when that happens.
Like if you live near border of TZ and pickup towers and their settings on other side - which is usually attempted to be minimized, but still could happen in theory.
But apps trying to use phone setting info, their own hard set setting, talking to other accounts with their own method and settings.

I think I'd need another cup of coffee to work out which direction this would need to be with possible interactions.