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

Indoor (Non-GPS) Activities Uploading with Wrong Time Zone

Garmin Connect seems to be saving all my indoor activities (without GPS) with a start time an hour ahead of when they actually occurred and within the time zone labeled "GMT-6:00 Central Time (US & Canada)," but I live in the Mountain time zone. So if I do a 20-minute long activity, Connect will record the start time as being 40 minutes into the future.

All outdoor activities with GPS seem to record correctly. If I view the details of the completed activity on my watch, it shows the correct start time of the activity. I also have Mountain Time selected under the "Upload Time Zone" option the the Display Preference section of Account Settings in Garmin Connect. 

Anyone else run into this issue and/or have any recommendations on how to fix this?

  • I'm seeing the same thing. I'm in Central European Time, but indoor activities show South African Standard Time. Even though the time in both zones happens to be the same (at the moment), this is clearly a bug since CET is specifically set in my Connect preferences as the zone to use for non-GPS uploads.

    (looking at the time zones of my past activities, it seems this bug was introduced between the 16th and the 19th of July)

  • I reported this to Garmin and wrote about it here: https://forums.garmin.com/apps-software/mobile-apps-web/f/garmin-connect-web/172221/wrong-time-zone-on-the-garmin-connect-web-site

    I would suggest you contact Garmin and do the same so they have more reports of this issue.

  • Former Member
    0 Former Member over 5 years ago

    I've also reported this to Garmin. No solutions were offered and a ticket was created. Do they not follow the forums?

  • The issue is with your time zone setting with your Garmin Connect. If you change the time zone there to your current time zone, your indoor activities will record correctly. 

    https://connect.garmin.com/modern/settings

  • In my case that's definitely not the problem. My time zone is set correctly, and hasn't changed since.. ever. It's a bug in Connect that was introduced last July.

    My profile is set to Central European Time (GMT+01:00), but during summer time (which technically is CEST, GMT+02:00), indoor activities will show South African Standard Time. (which also happens to be GMT+02:00, but isn't quite correct)

    It appears they do some weird matching based on the offset instead of using the configured time zone.

  • My profile is set to Central European Time (GMT+01:00), but during summer time (which technically is CEST, GMT+02:00), indoor activities will show South African Standard Time.

    I am in CET too, so have just checked my summer indoors activities, and the TZ in the tooltip over the activity timestamd indeed shows GMT +2:00 (which is correct in summer), and the label "South Africa Standard Time", which is not correct, but I see no reason why I should be concerned about it. Unfortunatelly I am not quite sure about the true starting times of those activities, but from what I remember, I would tell they are recorded correctly.

  • As far as I can see on my own data, this issue happens only during the Daylight Saving Time (DST) period (in Europe also called Summer Time), and only on activities not using GPS. 

    In fact the time zone is matematically correct, it is just the time zone name that is wrong. I am in the Central European Time zone (CET), it is GMT+1 (in summer GMT+2). In summer, at indoor activities, the tooltip info over the time of the activity on its detailed page, shows the zone GMT+2 (perfectly correct) and the label South Africa Standard Time, which is wrong, but it matches perfectly with the CET+DST. I see absolutely no reason why I should be concerned about the wrong TZ label, since the TZ shift self is correct, and the time too.

    The reason why it happens is easy to understand, while at GPS activites, the time and TZ info come from the GPS satellites, in indoor activities it comes from the watch memory, and the watch likely just passes the time in the standard numeric format with only a numeric TZ shift. And the application then simply takes the first match for the numeric TZ in the numeric-to-name table.

    In other words - the conversion from TZ label to TZ shift is unambiguous, while the reverse conversion from TZ shift to TZ label, neded at indoor activities, is ambiguous, and the current system misses the data for solving the ambiguity.

    The proper solution would require the change of storing and transmitting the time values so, that it would include not only the numeric TZ shift, but also the TZ name or ID. That would have to be done at all existing watch models, and in the same time the system would have to be also backwards compatible. Looks like quite a lot of work for just a minor unimportant issue. There might be a quicker dirty solution by using the TZ setting from GC, but that would introduce a bunch of new problems, because many users are travelling, and would have to adjust the TZ setting in GC each time they move to a location in a different TZ. Another dirty possibility would be using the TZ name from the last GPS activity, but that would introduce again a number of new problems (i.e. you could have moved in between).

    That told, it would be certainly nice if it got fixed in the future, but if I were the project manager responsible for it, it would be pretty low on my priority list.

  • Did you ever manage to solve this?

    I have the same problem