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

Anyone STILL having heart rate accuracy issues with their Fenix 6?

Former Member
Former Member

Hi all,

Super frustrated, but I am still having issues with my Fenix 6S and heart rate accuracy even with the 4.20 software update. I'm wondering if it's just me or what the deal is? I had a 5S Plus before this and had no issues doing the same activities so I really don't think it's user error. My heart rate hardly reads over 110 during really vigorous exercise when my heart rate is closer to 160+. I have tried wearing on the inside of my wrist, tried my other wrist with no luck. It consistently reads 80-110 bpm the whole time. I wouldn't have bothered to upgrade if I knew this was going to be an issue. I know that wearing a chest strap is the most accurate, but I don't like to have to wear it for all of my work outs and my old Fenix was totally fine as well as my apple watch before that. Any suggestions? 

  • The facts can always be ignored but the reality is much more real.

    Fact is my previous Polar watches and even Fitbit activity trackers had more responsive WHR. And the F6 is capable enough, I think the software algorithms mess WHR up.

    Last week right after an intense run I switched of my Polar strap and when walking home my F6 had my HR at around 65-70 for a full 15 minutes. Just not even close to my real HR after a run. Out of frustration I then switched of the F6 WHR sensor in the settings and after 30 seconds turned it back on. Within 10 seconds my HR was around 115 bpm and stayed there during the rest of my walk. Wrist placement was identical. There is just something very wrong with the Fenix sensor software I think.

  • Fact is my previous Polar watches and even Fitbit activity trackers had more responsive WHR. And the F6 is capable enough, I think the software algorithms mess WHR up.

    I've owned the Fitbit Surge, Amazfit Stratos, Fenin 5, Fenix 5+,  Forerunner 245 and Fenix 6 Pro. I've been tracking resting heart rate for several years.

    The Fitbit Surge was the best for me, it was deadly accurate tracking resting heart rate and 'OK' for activities (a strap isn't an option as you can't connect sensors)

    The Amazfit Stratos was awful, it was the only one that struggled to do resting at any sort of credible level - activity tracking was a non-starter. It was possible to connect a BT belt for activities.

    I count the F5 / F5+ as the same watch essentially - both were very accurate on resting HR tested parallel with a belt. I didn't have much luck with activity tracking unless i used a belt. 

    The Forerunner 245 did resting heart rate to belt accuracy - I didn't do any activities without a belt.

    The F6 Pro is very easily the worse of all the Garmin's I've owned - tested against a belt, even resting HR can be +/-5 from the HR belt.

    I find resting HR tracking incredible useful to track recovery or over-training - it's a metric I value highly - if accurate. 

    I may be unusual in that I don't care about activity accuracy as I always use a belt - but I care a lot about resting HR and that is supposed to be easy for any watch. The F6 Pro is worse than all previous Garmins (for me), it can be over 10% off.

  • There is just something very wrong with the Fenix sensor software I think.

    I agree that this must be a software issue rather than the environment / sensor placement issue. A few times when I tried to use WHR during a run, it would get stuck in a range that is clearly way too high for the effort level. Every time I was able to "reset" it by walking a little bit than resuming running. After resetting it would measure the HR correctly for awhile, but then eventually it might get stuck in the too high range again.

  • Could be a cadence lock?

  • Yes, although the measured values would generally be below my cadence. When I run easy my HR is rarely above 140-145. My cadence is generally around 165-170 when running easy. The WHR would typically get stuck in the upper 150s or low 160s - a bit lower than the actual cadence. But yes, it seems to not be able to fully filter out the cadence noise out of the useful sensor input. 

  • I also always use a chest strap during an activity, any activity, as it will always be better and I will always prefer the extra precision.  I also value the WHR for resting heart rate.  

    I also have no issues really at all with the WHR.  The accuracy is perfectly fine/decent for WHR vs the strap.  I get the odd moment where there is a spike, and about 6 months ago I did have some most consistent issues during an activity when I didn't happen to the strap but they were temporary and seem to have gone away (and then I use a strap anyway).  However, it's impossible to know who else is also having no issues as people like me are unlikely to bother posting here.  This thread only really attracts those who do believe they have an issue.

    The "I have an issue" and "I don't have an issue" debate is therefore pointless.  Only Garmin know how many watches have been sold, how many of those owners have expressed displeasure with the performance and whether that warrants whatever the cost is to them of fixing the watch.  The options seem clear; (1) raise the issue directly with Garmin and hope it is fixed, (2) live with it or (3) get rid of the watch.  I'll be keeping mine as it's completely fine.

  • The "I have an issue" and "I don't have an issue" debate is therefore pointless.

    I don't think anyone is having that debate? However when the same people have posting been in this thread for over a year trying to poo-poo anyone say they are having a problem or blaming the user, then it starts getting into gaslighting territory.

    I absolute accept resting works for you - it should do, it's the easiest thing for an optical HR sensor to do. That's why FOR ME it's so noticeable it's failing.

  • Just wondering what we are hoping to achieve from this thread.  It's been over a year and 115 pages of comments, and there is still some back and forth on who has an issue and who doesn't.  Feels like we are shouting into the abyss and it's just time to dump the F6 if it's not working for you.  It's not like there have been any clear trends or contributing factors that have been established?

  • I think what a big problem is, is that it got worse. At least for a lot people, so garmin changed something the bad way. I also use a chest strap for training where HR is my focus, intervalls or fast runs in general. But for easy days or "just4fun runs" keeping it easy i just used the WHR because it was good enough and there are not really big changes in HR for these runs. These runs which worked totally fine are now a total mess. There are 2 scenarios. 1) i totally destroy every pro athlete by running with a HR of round about  80, i mean i take it easy but not THIS easy.....  2) i am on the edge of a hear attack, because on an easy run i exceed my max HR.  and yes it is really this extreme for me, it just is data rubbish

  • It's all very well advocating 'dumping the f6' but some folks have spent a lot of money on this thing. And they'd quite like it to work. That's not a big ask.

    I guess 'we' are hoping that Garmin take another look at this rather than just move on the Fenix 7.

    We've seen Garmin do monitor these forums, Garmin reps. often post here. I'd be surprised if this sort of content isn't fed back to them.