Related
Options

Another example of the Low HR issue

Parmenion_45
9 months ago

HR was stuck at around 115bpm, only corrected once I went out to the controls view (pressing the top left button) and back to the activity. Hope they get a fix soon.

And here are 2 runs at my local park run, the one is where I saw it was low and went out and back for it to correct and the second one where I did not see it and it stayed low for the whole run. 

updated to the latest beta 18.12. not listening to music and not having any headphones connected and again I had to exit to the controls menu for it to correct. so still no improvement.

Updated to 19.4Beta and still the issue persist.  Watch recorded my HR lower than it actually was, then went lower still before correcting. No music or headphones or phone connected.

  • 0 9 months ago

    I have the same problem since the latest update. I have not yet tried to "shake up" the HRM by going to the controls view - but i will definitively try that !    The other option is to use a separate HRM band but that shouldn't be required.  If you decide to buy an additional hrm band please don't buy from Garmin. Garmin should not be rewarded for selling watches with faulty HRM.  Buy instead HRM band from Polar, Wahoo, or Scotsche! 

  • 0 9 months ago
    Parmenion_45 said:
    Hope they get a fix soon.

    Ha!

    Haahaha!

    Haaahhhahahhhhhaaaaa!

    This is a years long issue that gets worse and worse with every updates. Forums for all garmin watches are filled with this bug. Get an arm HR strap (Polar Verity Sense, or any others) as a simple solution - trust me, it will be never ever fixed in garmin watches. 

  • 0 8 months ago

    I've been having some weird things going on with the heart rate sensor too - today I started to jog very slowly and the HR kept raising to 154 (which in reality was way lower) and then suddenly, in few seconds it went back to the expected level, around 130. I noticed that when it showed the wrong HR, it also says that Power (W) was 381W and suddenly dropping to 81W, then coming back to 200W in mere moments. Maybe this has something to do with it, who knows :)

  • 0 8 months ago in reply to pxl

    Sad but possibly true!

    But today Garmin announced that they have put a lot of effort into the development of new watch faces with new functionalities and payed content.

    I just don't understand what kind of paying customers they expect in the future with not solving all current issues like wrong HR measurements!

  • 0 8 months ago in reply to Garmin Bug

    It is very annoying for sure 

    My watch functions perfect at firmware 15.76.(Heart rate and everything else!)

    But I am missing all the newer functions added since 15.76.

    I just can't update from a very stable version to unstable mess (latest firmware ) during marathon training blocks.

  • 0 8 months ago

    Same Here. around 120s for 4-5 km, short spike to 140, drops to 120s again for another 10km.  would be great to have ~120bpm but its a faulty measurement for shure

  • 0 8 months ago

    I sometimes (rarley) have same issue. Then I noticed, it depends on the position on the wrist. After moving around wrist or clean the sensor, the HR move to where it should be. Not sure if this is the SW related to "calibration to meet HR when sweat". But might be. (latest SW)

  • 0 6 months ago

    Had been going good for the last 2 weeks of running, heartrate monitoring seemed to be working fine regardless of if I where using headphones or listening to music until this Saturday's park run. I  was heading into my last 1km picking up the pace and my heart rate dropped  twice suddenly from around a 165 down to the 144's. 

    At least once in 2 weeks is an improvement.

    One key thing I did change was setup a running workout that I used for all my other outside runs that uses a heart rate zone intensity target. Wonder if that prevented the heart rate jumps?

  • 0 6 months ago in reply to 8400354

    I've noticed the same thing on my two last bike rides. Today, I was riding along a slight uphill at about 140 bpm, as expected, then it shoots to 167. It subsequently dropped gradually, down to 132, after I turned onto a steeper (8%) grade and started climbing. Sure, that makes sense!

  • 0 4 months ago

    19.4 beta and the issue is still there. Watch recorded my HR lower than it actually was, then went lower still before correcting. No music or headphones or phone connected.