Both my watch and the settings portion of my garmin profile are set to Eastern time (US & Canada) GMT -5 hrs. All of my uploads to garmin connect are always showing up as Central time thus an hour earlier. Device is a forerunner 410. Anyone else have an issue like this?
I have a similar issue. The chart of my sleep on the attached GC attached show the sleeping times correct as per my watch but the graph x-axis is an hour earlier (I am GMT +11).
The integration with MFP is always out for "remaining calories" by an amount equal to 1 hour of BMR as well. I have had that over multiple garmin devices. Both MFP and Garmin have an ability to set time zones but somewhere on does not factor in any summer time (neither ask the question in the settings)
Head & Shoulders icon - user settings - display settings.
Thanks for response.
yes they are both (GC and MFP) set correctly and on the same time zone (Sydney/Melb/Canberra). It appears the watch (FR235) must get the time from the internet connection via the mobile and upload activity detail with that. The "sleep" chart that was attached shows actual times falling asleep and awakening OK but on the x-axis an hour less as if it does not pick up summer time in however GC handles it and there is no option for summer time under GC settings. The Heart Rate chart is OK.
I am not clear about the MFP difference part though. It is also set on the same time zone but the equivalent of 1 hour "BMR" difference (coincidental?) in daily calorie deficit/surplus was there before summer time started and before and after using the negative correction transferred by Garmin. No big deal but I wouldn't mind knowing which was correct as they are otherwise calorie wise the same apart from the obvious food entry, nutrition in MFP etc. Both have the same net calorie goal and I think the issue may lie with MFP here.
Both my watch and the settings portion of my garmin profile are set to Eastern time (US & Canada) GMT -5 hrs. All of my uploads to garmin connect are always showing up as Central time thus an hour earlier. Device is a forerunner 410. Anyone else have an issue like this?
