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

Garmin Connect HR Zone setting sanity checks too restrictive for bradycardic riders

hi,

I'm 65yo, I use Fenix 6, Edge 530 bike computer, HRM-PRO and an Android phone with Garmin Connect installed.  I've always thought that the numbers coming up in activities such as exercise load, aerobic/anaerobic etc were at times inaccurate or misleading.  Yesterday after riding for a solid 3 hours at 20KPH average on rail trail, I expected an exercise load of somewhere in the multiple hundreds, yet it was just 47.  I realised that my heart rate zones needed tweaking, so I created a spreadsheet and using default values based on a 60 BPM resting heart rate, I came up with values appropriate for someone like myself with bradycardia (very low resting heart rate).  For me, zone 1 should start at 59.  While that may sound too low, note that I have in the past had rides on my ebike taking it very easy, achieving an average heart rate of 57 over a 10KM round trip.  Uphills I achieved my max HR in the low 70s while rolling down hills hitting low 40s.  So I attempted to put these corrected HR zone parameters into Garmin Connect app, but it refused to accept.  I found that if I raised the zone 1 start up to 60, that it accepted.  So, I'm assuming from this that there is some sanity check that assumed that nobody has a zone 1 less than 60.  Wrong, please fix.  If I were stil in my teens, the correct zone 1 start for me would be 53, as my RHR then was 30.  I suggest accepting anything down to 50, or change the data rejection to a warning.

  • HR Zones are note really used for anything regarding the metrics calculation. They are there merely for the presentation of the data for the user. What is important for the metrics, are the values of the Resting HR, Max HR, and the detected Lactate Threshold HR. So make sure all of them are set properly, and preferably also use a HRM chest strap for more accurate HR, and to enable the correct LT detection. I usually also recommend to disable the auto-detection of the Max HR, once t is reliably set, and only recheck it about once a year.

    Otherwise, for changing the limit, you may want to suggest it also to Garmin, not only here on the user forum, where it is unlikely to reach the developers. You can do that at Share Ideas | Garmin