Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

HR Zones Bug

snochick

I've noticed since the 18.22 roll out that that there's a bug with the HR zones. My watch pushed up my max heart rate recently due to the auto detect function (I've now turned this off) and I felt it was a little too high so have lowered the max HR by a few beats. However despite the watch saying that my max HR has changed this doesn't seem to translate to the actual zones when I am doing a cycling activity. I have a training session to stay 30 mins in zone 3 and have noticed when I hit this zone its too high than it should be for my max HR and the calculation hasn't translated to the actual cycling activity (it hasn't dropped back down after I changed the max HR).

Anyone else having this issue?

  • 0

    Yes, it is a know bug: when the watch updates your Max HR, if you have your zones as a % of Max HR, you have to go reset your HR zones so that the normal % are reapplied.

    The Max HR auto-detection works much better now than in the past, but is not fool proof. You can get a higher or lower new Max HR than you recent activity peak HR. The algorithm filters out HR data that it deems not qualified. Also, you can get a new cycling Max HR after a run.

    If your newly detected Max HR is adding/substracting more than 5bpm, I recommend you perform new LTHR test using the watch built-in test since Max HR influences the detection of LTHR.

  • 0 in reply to Etupes25

    That's really good to know. I've reset the zones, have lowered my max HR a little and turned off the auto update for now. It jumped from 186 to 191 which I just thought was nuts. I normally cycleon the wattbike so will see if there is a LTHR test I can do when I'm feeling brave!!