

I have reported all this to both Zwift and Garmin support, but not seeing a lot of action (both are as bad as each other in not actually reading the ticket, but I have manged to convice them of the issue).Īnyway - is anyone else having the same issue - I have found reports of it causing issues with Golden Cheetah during uploads due to the timestamp, but they did a workaround). If I use the FITfiletools corrupt time fixer the FIT files then upload (the tool makes the timestamps match).Oh and yes, my device has the right time set locally.
#Garmin connect sync goldencheetah manual#
It looks like this is what is stopping the automatic sync as well as the manual uploads working. You can then add a Power field column to the Basic data view, and copy and paste the Power2 data into it. The files are failing a GC check due to the “local-timestamp” being set to and the “timestamp” having the correct date (I think Garmin see the dates as too far apart). fit file from Garmin Connect and import it into Golden Cheetah, you can see the Power2 field under the Activity Details: Raw Data: Developer tab (look for the Developer view at the bottom of the GC screen.Recent Zwift FIT files will not even manually upload to Garmin Connect (GC).Aftersome investigating I found the following: I went through all the disconnect/reconnect options and still no joy. Modify curve hovering tooltip time format and Y value precision on the small plot.Automatic syncing has worked fine for me for ages, but recently it has failed.The user can still modify the parameters. Color bar have now default colors and zones definition.Add setting to change wall sections duration from 15 to 60 seconds.
#Garmin connect sync goldencheetah series#

Compute ride when setting is changed by the user. watches and cycling computers into programs like GoldenCheetah or Garmin Training Center that dont.
