This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

MyFitnessPal Integration Errors

Former Member over 9 years ago

This started yesterday, some type of integration error with MyFitnessPal. Prior to yesterday (March 4th) things were fine. Here are the problems.

a) Garmin Connect is not reporting my correct calorie burn for the day to MyFitnessPal. When just synching, my Fenix 3 HR says that I have burned 2705 calories so far today (I ran 9 miles earlier) but after forcing a sync with MyFitnessPal it says that I have only burned 2105 calories for the day. Because I have "negative adjustments" turned on for MyFitnessPal, this forcing a subtraction of about 600 calories on MyFitnessPal which can't be correct. As of right now, MyFitnessPal says I have 689 calories remaining for the day, but Garmin Connect says I have 1362 remaining. Both Garmin Connect and MyFitnessPal have the same number - 2090 - as my base calories for the day.

b) MyFitnessPal is also overwriting my weight information for both days (March 4th, and March 5th). I have the Garmin Scale and use it every morning. It's been over a week since I have last logged weight in MyFitnessPal. The weight last entered into MyFitnessPal manually has now been overwritten as my weight on both March 4th and March 5th.

Have there been changes that are causing these problems? Anyone else having these problems?

Best,

Tim

0 Former Member over 9 years ago

MyFitnessPal integration -- Lots of Calorie problems -- Possible diagnosis/solution.

I've had periodic glitches with MyFitnessPal integration ever since I started using it.

Lately, it's gotten much much worse.

The calorie count for nearly every day this week is incorrect. Thursday reports /zero/ calories consumed, despite what's entered on MFP. There are errors on the "calories remaining" calculations as well - I have one day showing a 1500 overage when 1500 is the number of calories consumed, not calories beyond the daily limit.

This is very frustrating.

Silver lining - from watching all these errors, I have a theory, which, if right, may be of use to the web managers and programmers. (If they read this at all?)

I get the impression that the Garmin pages will cease to update a day's calorie count after the first time MFP data is read after midnight. Whatever's read that first time after midnight is treated as the 'final word' and any subsequent changes/corrections/additions on MFP are ignored.

For instance, I went back Saturday morning to add something I'd not put in on friday. MFP, of course, dutifully updated the calorie count. That update was never recorded on Garmin.

On thursday - when it reports no calories consumed - I believe there were those problems with Garmin talking to MFP. I suspect Garmin tried and failed to read MFP data sometime after midnight, got a "zero", and treated that as the final word on Thursday's calories from MFP. Subsequent reads ignored the actual data.

Suggestion --

When syncing with MFP, don't just pull the current day's data. Pull up the data for the last five days and update all those days as needed.

This will ensure that post-facto changes to MFP data are reflected in Garmin, as well as cover for days when there are Garmin/MFP synching problems, yet pulling only 5 values won't be too much of a strain on bandwidth.

Request - while you're fixing this, tweak the page so that when 'sync' is clicked, it updates the "Synced @" value. Right now, that value only updates when you refresh the page.