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 updating with Autodetect off

mcalista

On 3 out of 4 recent rides, my recorded HR has spiked to the 240s in the first few minutes (before settling down), with a new maxHR notification at the end of the ride, and new HR zones being calculated, despite MaxHR Autodetect being turned off. My true maxHR is 184. The one time it didn't occur was on a very warm morning, and the HR didn't spike.

I'm not complaining about the HR spike itself - I know this is a common problem with many types of chest straps due to poor conductivity in cool conditions until the skin starts sweating.

My issue is that with Autodetect off, this should not result in my Edge 530 in a new maxHR and zones. I deliberately turn Autodetect off so as to ignore the measurement spikes.

I am running firmware 4.10, and using a Garmin HRM-Run chest strap.

  • 0

    I've had this problem since I bought my 830 months ago Garmin support has been frustrating blaming me, my HRM etc . I think they have finally sent the issue to the developers as a possible software bug . Please open a support ticket yourself in the hope Garmin will work on it . 

  • +1 in reply to DBD.2020

    I notice that beta 4.19 (just released) claims to address this issue. But Murphy's Law says that I'll now have trouble generating an HR spike to test this.

  • 0 in reply to mcalista

    You could manually set a low heart rate (130bpm), then go for a ride and see what happens if it still auto updates to a higher value (assuming you go higher than 130)