Curious question. Anyone experienced their workout showing that almost half of it was spent coasting in an outdoor workout?
I’m not sure if this is a TR problem, COROS DURA problem or Power Meter (PRO-MX1) Problem. Support contacted, but curious if anyone else has run into this before as well.
yes, i have been having this problem for about 2 weeks. trainerroad marked me as coasting for more than 4 hrs on my 6 hour ride yesterday. my red light/green light function is also not working. i wrote to support this morning. i am glad to hear that i am not the only one. i am using a garmin.
I doubt if it’s a TR problem
do you use any other service (e.g., TrainingPeaks, Garmin Connect, etc.) If so, what does the other service show for the same ride?
Make sure your head unit / recording device is set to recharge 1 second intervals and NOT smart recording
Yeah I’m not sure. I also downloaded the fitfile from coros and uploaded it to garmin. Garmin synced over to TR and now I see a coasting time of 25 minutes, or around 12% which doesn’t seem too out of whack.
Something from Strava → TR was funny that was adjusted again with a push from the same fit file in garmin.
Only thing that jumps comes to mind here is I know different services and devices can count “0”s differently.
If you are stationary at a cafe stop for instance then then the device can either count those data points as “0” or “null”.
If its is set to count zeros then this would add to your coasing time.
I guess that raises another question. Does TR simply take all info from a provider as is or do they pull the raw data (such as fitfile) and apply their own pipeline against it.
i suspect the strava connection, too. the rides sent from zwift directly are normal. around the time the coasting issue popped up, strava also stopped synching with training peaks and i have been pulling the garmin data directly from the garmin head unit onto training peaks, where the information looks normal. i tried pulling the data from my head unit onto trainerroad, but i couldn’t figure out how to do it. i will try gamin connect.
Interesting its the same issue from a different device. What power meter are you using? I added a trainingpeaks sync to see if that can also push over. Being on coros i don’t really want to have to manually download/upload from coros to garmin to fix the issue.
I did test syncing another ride from coros → garmin → TR and it also alters the values. Sure seems like something thats being delivered from Strava is funky…
This case is a pretty marginal difference (15% to 14.6%) but it still indicates that something in the stream is producing different values.
i have a stages power meter.
Doing a bit more of a dive here. I pulled my data from the Strava API and it looks like my data is being downsample to distance, creating gaps in the data with respect to time.
That said, it does raise a question in how the interpolation between data points is calculated for the TR side. If the distance is used, then only a subset of time points are returned and some form of interpolation must be happening in the intermediate steps to produce a per-second value.
Perhaps this is the origin of the odd coasting values in how TR then interpolates these gaps?
I don’t know why Strava is returning as a down sample values (storage/efficiency?) but this might explain why data sync’d from other platforms returns the proper data as, in the garmin case, they are able to request the actual fit file from the provider.
One other tidbit is the TCX file pulled from garmin shows per-second values. checking my raw fitfile from COROS is also is stored at a per-second value. (last photo).
Based on what i see here, it looks like a problem with how Strava is delivering the data. Whether that is a problem from provider → strava or a problem from Strava → TR, something is creating funky values.
Just looked at my ride in TR from Saturday and something is definitely screwed up. The TSS for the 4.5+ hour ride is only showing 150. NP, AP, average speed are all a bit lower than what I see in Garmin connect, strava, and intervals.icu, but the TSS really has me scratching my head when is should be 250+ like all the other platforms. And TR shows over 2 hours of coasting when the other platforms are like 30 minutes. Everything feeds from Strava and TR is the only downstream system that is looking weird. That doesn’t mean the problem is just on the TR side, but something in the Strava to TR integration looks pretty broken.
Worth noting my ride was similar. It bumped my Tuesday interval session down slightly before the garmin sync, then post sync it retriggered to a recovery ride.
@CodyS This sounds very similar to a bug we’re investigating!
In the meantime, as you’ve mentioned a workaround would be to:
Download original ride file from source e.g Garmin, Wahoo, Coros etc
Delete ride in TR
Manually upload the original ride file
There isn’t a public bug tracker for these sorts of issues is there?
Nope
FWIW, my ride from tonight looks fine, so I’m assuming it’s fixed
