Related
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

18.20/19.18 HR bug still here

afarnedi
over 1 year 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 11 months ago in reply to Woody

    Ha, then they should up to processing power during activities. Because even if you do no activities, that watch still only last two days at best, whereas Garmin last a week minimum even with activities and using GPS.

  • +1 11 months ago

    All, 

    If you have not yet contacted Product Support directly, please 'vote UP' on this reply if you will allow me to add you to our internal report. I want to make sure everyone is added to the impact of what we've been tracking. I need permission because we may potentially email you, and will need to look at a couple of your activities if you have not already shared examples. 

    Thank you!

  • 0 11 months ago in reply to Garmin-Sierra

    Thanks, appreciate your efforts!

  • 0 10 months ago in reply to Garmin-Sierra

    I am still waiting for confirmation that this instance has been added to your bug report/internal tracking.

  • 0 10 months ago in reply to Garmin-Sierra

    I also experienced this twice last week. My hr according to the watch was over 200 (my real max is around 190) even though from what I did and how I felt I think it was about 150.

    I approve that you add me to the case, contact me by email.

  • 0 10 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 10 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 10 months ago in reply to RoWe

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

  • 0 10 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 10 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.