Hey @Maztj,

Apologies for the delay but hanks for reaching out about this. You are correct in your observation as we are aware of some differences in calculations between custom zones and max HR.

Both are going to give us a unique lactic threshold heart rate for us to process the relative effort score from and this is causing some variables. We're investigating ways to make these more accurate between the two HR zone types, ultimately, they won't be exactly the same but we would like them to show more similar results.

We don't have an ETA when a better solution will be available but it is on our radar.
Until then, I would suggest using Max HR as you've done if the Relative Effort scores seem to be low.

Hello, 

I have exactly the same problem. 

I have the related efforts being ridiculously low (divided by 3-4 for exact same route at same speed/power).

It is now impossible to compare my fitness level to previous month/year. I would like a solution to switch back all my historical data since the change  to previous relative effort calculation.

Please can you advise a solution. I pay for strava for these functions (training follow up).

Thanks for your support

​@gcounet You have to revert your heart rate zones then to their former ranges and then you have to change the sport type of each old activity and revert that, that reevaluates the Relative Effort against the current zones.

I realise this is an old-ish thread, but glad I found it, as it addressed my observation that my relative effort scores had about halved (for similar workouts) after changing from max HR-based to Custom HR zones.  This was for activities with very similar proportions of time spent in each zone and very similar overall times.  I had only tweaked the zones by a few HR beats.  But the relative effort scores had about halved.

My theory is that it is do with Max HR value itself.  When HR zones are set using max HR, then the max HR exists as a set number and is used in whatever calculation Strava uses for relative effort.  In my case 170.  But when setting custom zones, there is no max HR set - (you can’t set the upper end of z5 to a maximum figure.)

If the algorithm for relative effort uses not just the % time in zones, but also max HR, perhaps as a denominator for part of the calculation, then it being a bigger number would cause the relative effort score to be much lower. (eg it wouldn't surprise me if the calculation uses the ‘default’ of 220 when using custom zones - because no max has actually been set.)

Anyhow, to fix the activities, I changed back to HR zones based on a max HR.  Then changed activity type on each of the affected activities over the last couple of weeks to a different type (I used ‘gravel’, but it doesn’t matter), and then back again to ‘ride’.  This caused the RE scores for those activities to be recalculated, back to similar values to what I’d expected based on prior activities.  And so the Fitness and Freshness graph, which had shown an odd declining trend, looks as I’d expect again, with consistently calculated data.

I’ve also now tweaked the max HR down a beat or two to get the strava calculated zones closer to my desired custom zones, which are within a beat or so, close enough...

I would encourage Strava to look at this - it feels like an oversight in the RE calculation algorithm, maybe due to what I’ve suggested.  Allowing users to also set a max HR value when in custom zones, would likely solve it.

I realise that is some senses this doesn’t matter - because the RE score in itself is just a number and it’s more the trend in it that’s important  But when I’ve got several years worth of data all calculated on the same basis, it would be preferable not to have a significant discontinuity in that trend!

Anyhow, I thought I’d post all this just in case it helped anyone else who was wondering why RE scores changed after moving to Custom HR zones, along with my work-arounds, as well as hoping Strava would address it.