Related

Have you also found the OHR completely useless with 18.X/ 19.X/ 20.X?

6742038
9 months ago

Now that I have installed 18.22, the wrist measurement is no longer working. I did a suggested Garmin workout with warm-up today. Same left arm, same clothes, same track, same tightness as always. After 7 minutes I thought the watch had started to recognize my heart rate, but it just got stuck somewhere around 130 and the watch kept giving me "false heart rate alerts". After pausing the workout for a few seconds my correct heart rate of around 155 was recognized immediately. I then did a short test sprint, which was completely ignored by the watch.

Inb4 "use a chest-strap": It has worked perfectly for me so far. 

  • 0 2 months ago

    I'm not sure about this yet, but it seems OHR works fine during normal runs vs being inaccurate (too low in my case) during a workout or coach run. in my case this started  during the last couple of updates, now version: 20.32. 

  • 0 2 months ago in reply to 4377340

    For me it works fine for steady runs, and for bicycling. When running intervals, it can sometimes work well, other times not.

  • 0 26 days ago

    Thanks for your feedback.

    I recently tried out the new beta version 21 to give the OHR another chance with the latest firmware version. I also selected the daily suggestion "threshold running" and did not use the chests strap. At the beginning the heart rate was recognized instantly, but at the 10 minute mark, when I increased my pace from 6:30 min/km to 5:00 min/km, exactly the same error occurred as months and software versions before. The measured heart rate simply got stuck at around 140bpm. At this point, I am convinced that the watch is only spitting out fantasy values.

    On top of that, of course, they didn't miss the opportunity to slap the next buggy function onto the already buggy OHR. "The lactate threshold estimates are automatically applied after training with the heart rate." After training, my lactate threshold and max hr was raised to an absurd level and I couldn't opt out.

    It no longer feels like the watch is a benefit to my training when everything is wrong.

  • 0 26 days ago in reply to 6742038

    Do you have max HR set to update automatically?

  • 0 26 days ago in reply to ovekvam

    Yes, I had. I deactivated it and corrected it manually. I know it's a beta and will ideally be improved.

    I just don't understand these decisions to implement even more features that rely on the buggy ohr data. Can you remember the "invention" a few months ago that the OHR will no longer turn off if you use a chest strap? The justification was that the heart rate measurement would be more accurate. In reality, the measurements got worse, people were confused and there was an update shortly afterwards where you could disable the "feature". I just don't understand it.

  • 0 26 days ago in reply to 6742038

    Recently got a 255. Went for a run and my HR never went above 255 according to the watch. I doubt this is accurate, based on my effort and previous runs with other models and a chest strap, which didn't connect properly this time.

  • 0 26 days ago

    Yes, before 18.XX firmware OHR was pretty precise, i just installed 21.19 few days ago and looks like the OHR is working fine again, more fast and accurate taking the values, give a try, its a release candidate, its working flawless

  • 0 25 days ago in reply to Lewis

    Do you know, that this "release candidate" destroys LTHR detection, removes LTHR Test and not allows to reject wrong detected LTHR and max HR values? Read a beta forum, please. 

  • 0 25 days ago in reply to global_local

    But beta forum for which watch? There is no discussion going on in the 255 beta forum.

  • 0 25 days ago in reply to global_local

    i havent any issue with LTHR, i knew that now its not the LT Test, but i did some runs its auto updated and its stable, doesnt change in every run, so its working fine in my exp. and the LT has been detected good values