Here's how bad the optical heart rate is on the FR265

There are a lot of posts on this forum of users experiencing erratic and/or unreliable heart rate readings from the optical heart rate sensor on the FR265. I am one of those users. I previously had a FR45 and do not recall any major HR inaccuracies from the OHR sensor on that watch. When I upgraded to the FR265 (or what I thought was an upgrade), I was shocked and puzzled that the heart rate reading was all over the place -- usually it was too low (based on what I know by feel) and often jumped up by 10, 15 or more beats from one reading to the next. The "solution," if you want to call it that, was to wear a chest strap. (FWIW, I tried multiple wrist positions and strap tightnesses with no improvement.) But again, I didn't seem have this issue with my FR45, at least not to this degree, so what is going on with the FR265?

I decided to conduct an experiment to see just how bad it is. I also have an Edge 830 that I use for cycling. So I brought my Edge 830 to the gym for a recent strength workout. I wore my chest strap and connected it to my Edge. My FR265 was on my wrist with the optical sensor reading my heart rate. I started activities on both devices simultaneously. After the workout, I downloaded the .csv data into Excel and plotted both sets of HR on the same chart.

Here are the results. The blue line is my heart rate as recorded by the Edge with a chest strap. The orange line is the FR265 with optical heart rate. The workout started with a casual 10-minute steady 7-MPH jog on the treadmill. The peaks that follow are my sets of lifts. 

Note the gap between the Edge and the FR265 -- especially during my treadmill warm-up. What is going on here?? The FR265 was jumping up and down randomly. I have no idea what that random spike is.

Here is my HR during some of the lift sets. Again, the FR265 HR was all over the place and the gap between the two is huge.

Some stats:

Greatest jump from previous reading: Edge: 6 BPM. FR265: 18 BPM. (How can my HR jump 18 BPM within one second? I had 13 readings where it jumped seven or more BPM within one second.)

Average difference between the two devices: 6.27 BPM

Greatest difference between the two devices: 38 BPM

Percentage of readings with more than 10 BPM difference: 20.1%

What this boils down to is that the OHR sensor on the FR265 cannot be trusted and is, in effect, worthless. The question therefore is what, if anything, Garmin is going to do anything about this. Considering the FR265 is no longer a "current model" on Garmin's website and has been superceded by the FR570 as the mid-tier running watch, I'd say the answer to that question is "nothing."

  • Along with the inaccuracies from your tests and others, I will also get a stuck HR after a run from time to time. I have a similar physical description as you. 

  • Hi  . Yes, I have heart rate switching on.  Which is why it was such a shock to see when I took a look at the 265 while i was on the trainer.  I saw my heart rate, on the 265, jump from 85 BPM to 125 BPM.  As soon as the watch connected to the external HRM, the heart rate jumped.

    I was shocked because I would not have expected such a significant jump if the optical heart rate sensor was working.  A few beats sure.  But not that dramatically.

    The 265 only seems to connect to the external HRM when the watch is engaged.  Meaning if I leave the watch untouched, put on the external HRM, start a workout, the 265 will not switch to the 265 unless I touch the watch and go to view my heart rate.  But then when the watch goes back to watch mode, the 265 drops the external ISM and relies on the optical sensor. 

    I think this explains why my intensity minutes have been so badly off.

  • I wonder if Garmin ever actually tests the changes, especially for the HR. Meaning do they have a number of folks (outside of Beta volunteers) that actively use the features as part of their daily routine, or is just folks in the basement theorizing about what might work? It's darn near impossible for me to believe the HR processing could get this screwed up if the processing is verified before release. And, just as impossible to believe a previous version that worked reasonably well isn't put back in play unless some developer's ego is saying we can fix this..(just give me another 3 or 4 generations of watches :\ ) I like the FR265 but it's turning me into a curmudgeon and a cynic.

  • My only hope is that Garmin did go back and fix the elevation issue with the FR745 way past the support date for the watch. Fingers crossed Garmin has enough data to fix the heart rate issue with the FR265.