Optical HR accuracy

Hello world!

I know that e.g. DC Rainmaker quite rigorously tests the watches, comparing the optical sensor HR with a strap, and it turns out quite OK... but I never seem to have gotten trustworthy readings from optical HR myself. I don't think it's a defect of particular model or just my watch, as I tried multiple wrist optical HR watches and e.g. also Scosche Rhytm.

It will show a "generally" good HR, as in it will show 40 or 50 when I'm sitting (but also sometimes dipping to as low as 25; my actual HR at rest goes down to 40-42, but not 25...), generally show around 100 when commute biking, and during an easy run keep itself somewhere around 130.
But when I'm at the gym and do exercise / rest, then it will appear totally random - not budge above 80 when I'm jumping over a bench for a minute and am totally out of breath (and can verify after stopping with the fingers on my neck that my pulse is really high), then go up to 150 when I'm recovering (and the finger on my neck is maybe 80) and stay there for a few minutes... Or when I'm doing intervals, like 3min fast run / 2min rest it will go up to 160 during the first 2 intervals, but then e.g. during the third it will stay at 130, and only suddenly go to 170 at the end of the rest period (when the finger on my neck shows maybe 80).

The watch is fitting well on my wrist, it's not moving. I have shaved the hair from under the watch to see if maybe that was causing trouble. I have a very pale skin.

What are other people experiences?

  • I just had the same experience during a run, but I´ll recheck it againt a chest HRM the next days. Maybe my watch was moving around to much?

    The pattern I could see was that the heartrate was going up when I was slowing down to a much lower pace. E.g. running ca 5 min/km with 150-160 and then it was going up to 170 when the pace was around 7 min/km

  • This is generally a problem introduced with 4.10 and not fixed.   If you are running 3.0 or lower, you should not be having this problem.  I wear a Scosche armband for my HR, so I cannot test.  I'm just posting based on what I've read.

  • I, too, recently discovered an HR issue with the 4.10 update. My HR seems fine during everyday measuring, but when I went for a short run yesterday it never went higher than 118, when I know for sure my HR should've hit about 160-165.

    It worked fine prior to 4.10.

    Just updated to 4.20 this morning, will see if it's any better this evening.

  • Former Member
    0 Former Member over 5 years ago in reply to DCeremuga

    I have the same issue with 3.0...

  • Just upgraded to Fenix 6 pro from Fenix 3 with chest strap and the 3 runs so far have all recorded a HR that is around 25 to 35 bpm higher than the HR strap in non scientific comparison of what my usual run heart rate should be. I also tagged on a extra mile at the end of a run when I grabbed my old watch and HR strap and confirmed the Fenix 6 was showing a heart rate about 30 bpm higher than the strap connected to the Fenix 3..

  • So I tried power cycling (turn off/turn on) last night before I ran and then tightened (slightly uncomfortable, but not ridiculously tight) the watch after about a mile (and my heart rate fell back to something a bit more normal), and the run on the left below, seemed to have a heart rate somewhere around normal (125 ish). I was quite happy with this, as it was either a power on/off and/or a tightening of the strap (although it was tighter than I would like to wear it).

    This morning (right hand run), I ran again, with the watch tight, but with no power on/off and annoyingly, despite a slower pace, my heart rate was up to the 150+ mark i.e. too high again...

    Conclusions at the moment are some kind of software bug that necessitates a restart/power on/off of the watch to ensure the HR isn't reading high, combined with very tight strap...