Related

18.20/19.18 HR bug still here

afarnedi
9 months ago
  1. Hi, despite the information received from @Garminsierra that the bug was 'probably' fixed in 18.20, I have to say that today  I had a run after a couple of weeks of recovery after a flu and I was running with +30sec X minute slower than my normal pace and HR was around 140 BPM. All of a sudden, out of the blue, without changing my pace despite the very relaxed feeling, HR jumped at 185bpm, that's also exceeding my max HR possible for my age and my training level. I had to deactivate WHR and switching it on immediately after to get it working properly. After further 10 minutes same situation. Now, the thing is, i could also accept this and just don't care about that obvious bug, if not that all statistics are very much dependant by HR. I'm referring to vo2max, performance condition, rest hours, endurance score, suggested daily training etc etc...well Garmin, I'm sure you know that's probably the BIGGEST bug ever since here the whole reliability of the watch is under discussion. this is a sport Watch, probably the best out there, but if HR is not working properly, well, we're far from being an entry level watch. Furthermore, a friend of mine was running with a 69€ watch and HR was just perfect, consistent, stable and reliable. 
  • 0 9 months ago in reply to dacmic

    I only use the wrist measurement exclusively when walking. When I exercise I always have a heart rate strap. In my training I often have intervals, and additionally in temperatures around 0 degrees Celsius.

  • 0 9 months ago

    UPDATE: after the experience of my yesterday run I've decided to give a soft reset to the watch by pressing the light button for 5 seconds. Well, today's run went muuuch better; I didn't get any "out of the blue" HR peak and the graph seems much smoother than yesterday's one. you can see it here below. The drops are caused by traffic light stops and a fountain. I'm happy I've never exceeded 165 bpm; that's possible according to my feeling today. Therefore I'll keep an eye, obviously, on this for next runs and I'll keep everyone posted here.

    In conclusion, I strongly recommend a soft reset after updating to 18.20

  • 0 9 months ago

    I'm also experiencing wrist heart rate issues with the latest beta. In a beta forum post, I described my experience and questioned whether these problems are due to hardware limitations and whether it's realistically possible for Garmin to fix them with software updates alone. I'm skeptical about the effectiveness of such "fixes" if the root cause would be hardware-related: forums.garmin.com/.../

  • 0 9 months ago in reply to aykay.hnx

    did you try a soft reset of your watch? I did it and, after a disappointing first experience with beta 18.20, I had a second run with decent results and no strange behaviour of HR (no peaks or similar).

  • +1 9 months ago

    UPDATE2: 

    Hi all. Well, despite the initial optimism, this run went pretty much badly; I started for the first 20 minutes, and the hr was definitely below my standard hr for that pace; it was around 130 135 bpm, and I know myself pretty well to say it was way too low for the pace of 5 min/km, it should have been around 145 150 as a minimum. I've noticed during the run a few interruptions of the hr that confirmed something was wrong. I decided to stop the hr sensor and switch it on again, as in my first run with 18.20 and boom! The HR jumped at 240bpm, and it never decreased. Therefore, I've decided to switch it off and on again, but no way, the hr was moving from 230 to 240 bpm. Since I'm still alive and kicking it means it was a fake measurement. Therefore I switched it off until the end of the run to not destroy my running statistics. See the screenshot.
    The conclusion is we still have an open bug.

    Andrea

  • 0 9 months ago

    It is spectacularly bad during a workout. I just did an exercise ECG, at walking pace / slow jog, resting my hands on the treadmill bar and it still managed to get it completely wrong. Like, measuring 155 as 179. Warm environment. I mean, how does it get a cadence lock when my arm isn't moving?

    Given that I had a 12-lead ECG at the same time I think we can safely say that the 965 is measuring wrong. Not only that, my heart rhythm is normal, so it's not even that to blame. Snug on my wrist.

    Even my Fenix 6 wasn't this bad. @Garmin-Sierra, you're welcome to reach out via email and access my workout history. It's going to be pretty obvious which one it is, my max HR is 168 and this is recorded at 179.

  • 0 8 months ago

    Unfortunately I'm currently limited to walking only, but even there I'm seeing HR spikes with 18.20. For example, when I'm on a brisk flat walk, my HR would usually settle at around 95 (+/-2) bpm. Then all of a sudden the HR on the watch would increase to 100, 103, 106, 108 or even further to >110 bpm but when I immediately stop and manually check my carotis with stopwatch, I would still be at around 95 bpm. After a couple of seconds, the watch will drop to around 95 bpm, too.

    Needless to say, this bug needs to be solved rather sooner than later, because it undermines the reliability of the watch as a whole.