18.20/19.18 HR bug still here

  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. 
  • There are NO changes in 18.26 relating to heart rate monitoring.

  • Well for me running without a strap never works on my FR965.

    Heart Rate measurement on the wrist looks so wrong on that device and did even get worse compared to the last months.

    My experience is that Heart Rate is just not going up during my running. Sometimes it stays at 110-115 bpm at full speed. 

    In connection with the really chaotic new Version of the connect app the last weeks have been really disapointing.

    Hope Garmin will fix those issues soon.

  • My watch was accurately monitoring my heart rate for a month or so but is now back to dropping to 0 during jogs. I would upload images but the site is not allowing me to at this time. The inaccurate heart rate is impacting so many other metrics (as everyone else has already pointed out).

  • 19.13 here and now everything works fine ! Thanks for the update!

  • I'm on SW19.13 and still do not see any significant improvements.

    Steady runs are somehow ok (except the first few minutes), for structured workouts it definitely isn't. 

    This is really disappointing as it used to work well with older SW (prior 17.xx). 

  • I know you don't like to hear this. Consider tightening by 1 hole. 

    It really works for me.

    I think 2 events were happening for my 265.

    I was losing a little weight so my wrist got smaller and I updated the firmware. I thought its the new firmware was the cause of HR bug.

    But I notice my watch was a little loose too when running so the HR measurement was probably less accurate. 

  • There's clearly a software issue when this many people are suddenly having the same problems with it. No idea why Garmin is refusing to even acknowledge there's an issue. My watch was working great for the first few months that I had it, and now the HR is wildly inaccurate throughout the duration of most activities, off by 50+ bpm at times. It is a problem. Period. What people want to know is what's being done to fix it and when we can expect a solution. If the answer is nothing and never then just say that, don't offer nonsense suggestions implying everyone collectively started wearing their watch incorrectly.

  • For me, it's a whole different experience. I'm still on firmware 18.27 and it's still very accurate. When I ride a bike, the difference is greater, but still within the acceptable limit. By the way, I use a heart rate monitor from Polar H10 for comparison.

  • wow 6 downvotes.

    I have confirmed and verified for my case that a loose watch can affect my heart rate data.

    The phenomenon is repeatable for me.

  • For me it does not make any difference how tight i am wearing the watch. Wearing it correctly as suggested by garmin gives the same results as wearing extremely loose or very tight.

    Maybe you got the downvotes because all these people with HR bug issues know that in their cases it is not a wearing, but a software issue.

    I.e. how is it explainable with a wearing issue that it always takes at least 10 minutes in my case to get an exact HR and before it is off by 20 to 50 BPM? Regardless of the activity-type, running, walking, rowing or cycling.