kosmo886

So I am using my Wahoo to track routes that are loaded from ride with GPS then have it sync with Strava (I never enable Strava on a ride). I’ve been noticing an average MPH difference that posts on Stava relative to what my Wahoo says. I did the calculations and it’s because the moving time is different on Strava and the Wahoo. I have the Wahoo set to auto pause when stopped and will occasionally pause it if I stop quickly for some reason. The total time of the rides are always with a second or two between Strava and Wahoo. Why is this moving time difference happening when I thought I was literally just recording the ride on the Wahoo and sending that data to Strava?

drewguy

Strava seems to recalculate things - so I think it drops some time that it considers you not to be moving but the Wahoo does.

Iride01 

It's always the big unknown. Sometimes you can glean how a site comes up with certain data numbers by looking through their FAQ's or help topics.

Not every value you see on your device is logged in the file you transfer, so many values have to be derived from the data in the log file that was given to the site. Not necessarily what the device used to base that value on.

roadCruiser76

A similar thing happens with the data on my Garmin versus Strava. It seems that the biggest differences occur on routes where I stop frequently. Strava's algorithms don't seem to detect stops as quickly as the Garmin device does, so Strava will often show a longer moving time and hence a lower average speed than what the Garmin device shows. On rides where I only stop a few times the difference is much smaller.

dmanthree

I've noticed some significant differences between my Bolt and other tracking services. It seems that my Bolt loses contact with the satellites during heavy tree cover and doesn't count the distance. When I've checked it vs Strava or Ride With GPS it always comes up short on certain routes. Other rides, like along the coast with little or no tree cover, there's no difference. I wonder if Garmin is any better? Well, once they're back on line, I guess.

DrIsotope

Strava's got'n algorithm for everything. Going back say 2 years, it used to be waaayyyy worse. Not unusual to have rides with 3-4 minutes difference in moving times between the recording device and the final activity on Strava-- and that's with a speed sensor.

Even now, if the stopped time is say less than 30 seconds, I can figure it's gonna get rolled in and I'll have that 1.00 move ratio. I've used Strava with Garmin 500/520, a few Bryton units, a Hammerhead Karoo, and now an Elemnt Bolt. Strava uses their own math on all of 'em. If you're having GPS errors, a speed sensor is the best place to start.

Barry2 

Try adding a Wahoo Speed sensor.
The Bolt will even auto calibrate it for you.

Barry

dmanthree

I've had one for quite some time. While it seems to read the speed accurately, the distances are off. The speed sensor never loses contact with the Bolt, and has no bearing on distance, so it's nice to have a constant and accurate speed readout, but that's as far as it goes.