Sauce browser plug-in, look at the last line:
that normalized power and IF match Garmin, TrainingPeaks, WKO5, etc.
Another race…strava and wahoo with some big differences…both apps set to include zeros, ftp’s are the same…
What device are you using?
Some are known for having sticky watts (cit. gplama. Bryton I’m sure of and wahoo too iirc and possibly wahoo app does not adjust for that.
HRmax and bodyweight is set to the same values in both apps too?
Wahoo Roam V2. Arent sticky watts a pedal based PM thing?
Max HR was 1 bpm different, weight was a few lbs different too because I forgot to change strava but that shouldnt make the power numbers that different.
It is. The activity file has all the data points from the ride. Strava and Wahoo are just interpreting the data differently.
Now that the “include zeros” is the same between apps, the results are much closer. My guess is any remaining differences are small differences in the algorithm use to calculate NP vs weighted average.
I’ll see similar things with distance and elevation between apps. Not worth worrying about - as long as you’re using the same app for training, it should be consistent. These days, I just use Strava as a “clearinghouse” to get data from one app to another (for whatever reason, TrainerRoad doesn’t natively speak to the Wahoo ecosystem).
That shouldn’t impact the .fit file - the “sticky watts” should be reflected in the data used by both apps.
Those two results are pretty similar now though.
My assumption for the remaining discrepancy is how the apps account for stationary time in the averaging calculations.
2 Likes