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 4 months ago in reply to Vizi
    Vizi said:
    These errors were not happening 8 months ago

    If you are talking about the post from @Leah P.then such errors existed 8 months ago, they still exist and will continue to exist. They are simply caused by the way the pulse is measured and not by software shortcomings, see for example the post from five years ago.

  • 0 4 months ago in reply to 4684381

    That is not true. While there are inherent OHR limitations, it is simply wrong to attribute every HR tracking inacurracy to OHR limitations, especially since it is very clear that in last 7 months HR has errrors that it did not have before (that affectes all Garmin watch models released in last 2 years).

    Regarding this particular error, I use watch for same workouts all the time (strength training) and never did have this problem until this year. The problem reflects in HR falling to very low 40 bpm) during workout and than spiking back to much higher number after some time. My resting heart rate is not that low, and never before 2024 did my watch have that problem. But after recent software updates it happens every so often. So, your assumption is not true in my case. If it was true, that would happen every workout in last 2 years. But no, it happened first time in last 6 months.

    So, yes, I know that this particular error happens and believe other people with such experience and I know that it is not due to OHR limitation but something that Garmin chanhed in HR algorithm. 

    Also, the post you linked as a proof that this error happened 5 years ago tells about completely different problem (HR not getting up for some time in some exercises, there is no spike down problem). But that is not what was reported here. Leah P reported sudden fall down of HR to 40s.

  • 0 4 months ago

    went for walking yesterday and my HR somtimes just went up for no reason. At the same time i was also wearing my huawei watch and my HR was perfect. Garmin can you fix this problem because this lasting at least a year already. You can see this on pictures below.

  • 0 4 months ago

    It has happened several times now that the watch delivers extremely incorrect measurements after an activity. I would guess a factor of 2 compared to the real heart rate. It doesn't always happen, but about every other time and the time of the error is also rather random, sometimes directly after the activity and sometimes 1-2 hours later. I have gotten into the habit of restarting the watch as soon as I notice the error. After restarting, the error has always disappeared. For me, this clearly indicates a software error and not a problem with the sensor.

    An example from yesterday evening after the run. I have a MaxHR of 175, which I have never actually achieved, and the watch tells me 2 hours after the run that my recovery time is being extended due to exertion. A look at my HR shows 202, which can't be right because I'm cooking right now, but it's not that strenuous. 60-80 would be my estimate of my current HR. Restarted the watch and it shows a HR of 72 again.

    I think these measurement errors started with a software update 6-8 months ago. I never had any problems with the HR before. I think I need to get into the habit of restarting the watch after every activity until Garmin fixes the error.

  • 0 4 months ago in reply to RoWe

    I have to add that I use a Polar heart rate monitor when I run. Thank goodness ;-)

  • 0 4 months ago

    This is from a 5,1 km run last week which has been done at a relatively constant pace and load.

    From the beginning to the end not even one of the whr-measurements has been near the reality.


    And here in relation to the cadence.

  • 0 4 months ago in reply to Woody

    I see 2 problems in the WHR:

    1. it's 20-30 bpm too low, which is a huge problem. It means it's maybe worth than just putting my hand over my chest. And useless.

    However I also notice that it does correspond "pretty well" to the external HRM, they move more or less parallel to each other.

    2. Even if I disregard that it's too low I still see lots of small flat line sections, that means the optical sensor lost a few seconds of reading.

  • 0 4 months ago in reply to flocsy🤠

    20-30 BPM consistently low is precise, but nowhere hear accurate, so basically useless, heck even 10 bpm low or high would be useless. Like I've said, I'm not seeing this on my 165 with 30.24 Sensor Firmware, but I'm also not a runner. For me it's been very precise and accurate indoor cycling. Hopefully this is a software/firmware fix, because all the training metrics are basically useless, even with a 10 BPM difference. You expect the WHR to miss the peaks and valleys on some harder exercises like Weight Lifting, Mountain Biking, Gravel, etc..., but not mess up a steady HR