It seems like in a custom workout when you set the power targets as absolute wattage values instead of %FTP, the app translates this into %FTP and when doing the workout the translation back to absolute power it rounds of wrong. For example today I did a workout where I had set the target to 250W, but when doing the workout the target were set to 248W.
I’d say it’s a bug, but I suspect it’s a “feature” based on the internal data structure of the workouts. So a feature request is that the power targets can be expressed as both absolute values and %FTP, so we don’t get this annoying rounding error.
Yes I agree it’s more of a bug… I just tested it and can see it just in the saved workout when you re-open it, if it was 80.4% and you save and re-open it is 80%. I can’t remember why we did this. But fixing the rounding should be possible without a huge amount of work. Locking that fixed value is more work for sure but also something many users both want and expect. I will see if we can fix the rounding sooner than later and leave this a a request for fixed power values so even when you change your FTP they don’t change.
This bug is still persistent, the same rounding error is still here. Although not catastrophical, it’s a bit annoying when creating workouts that have very specific power targets. The workout today was as reported in november 2024, the power target when creating the workout was 250W, but when doing the workout the app “rounded” this to 248W. Is there any chance of this being addressed? Or some workaround? My workouts are planned with absolute power numbers, not as percentage of FTP.
We will be starting a major revamp of how this works soon. We plan to add running and distance based workouts so will address this at the same time.
The workaround for now is setting your ftp to something that rounds nicely. So if ftp was 248 or I believe 310, for example it would not round 248 incorrectly.