Garmin connect is definitely doing some post processing of the data which is causing all the errors.
Garmin connect is definitely doing some post processing of the data which is causing all the errors. I'm not certain if general activity tracking calories are based solely on HR + steps or HR + something else but whatever it is GC is messing it up.
That's what I'm leaning towards with my issue - I've noticed my watch is recording fairly accurate HR data. But when it syncs, the graphs don't match up AT ALL.
http://i.imgur.com/anCJ1yA.jpg <-- Watch HR
http://i.imgur.com/FPb32UW.jpg <-- Garmin Connect HR
So, it seems, the watch is sending the data but Connect is doing something weird with it?
Is that straight HR line in GC giving you a big active calorie calorie credit in the additional steps line?
I also have the calories discrepancy on some days between watch, widget, steps page, connect mobile, etc...
I sent information a few times to garmin and after a couple of back and forth I finally got confirmation that they are working on a fix:
"Thank you for contacting Garmin International. I am happy to continue assisting you today.
At this time, we have determined that the discrepancy in your calorie data between Garmin Connect Mobile and Garmin Connect on the computer, is an issue that we can recreate with accounts in-house. We have created a case regarding this issue that will be researched by the Garmin Connect Subject Matter Experts, and then be further researched by Garmin Connect engineers.
If we are in need of any additional information from you, or have any additional information to provide to you in the meantime, we will contact you via email. We appreciate your patience on this matter and hope this does not create any inconvenience to you. We will work hard to get this issue solved as quickly as possible. "
In the meanwhile, I found confirmed many times that the calories from the widget in the dashboard is correct and every once in a while an offset is created vs the full steps page, so for myfitnesspal I add a "quick calories" equal to the offset, just to help me eat correctly and I remove it at the end of the day. A little pain, but manageable.
The good news is that I have now 2 months of data proving the that the calories expenditure calculated by the 235 is really accurate, so the fundamentals are good, we just have to get the little bugs sorted out.