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? 

  • I contacted Garmin about low heart rate with cross country skiing when using OHR. They acknowledged the problem. I sent them all necessary data from my watch and those were sent to developers. Whenever you're having issues with OHR when doing some activity, you should contact Garmin. Nothing will happen if you only tell about it here. Just FYI if somebody does not know that yet.

  • Former Member
    0 Former Member over 5 years ago

    Went for a quick test run with the H10 vs 6X again. Had the 5X on my wrist but unbelievably forgot to hit record before I ran off. I will repeat tomorrow with all three, but for the moment this is the reading of the 6X and H10. The 6X just locked on to 150 and did not want to move at all. The big drops are where I paused the activity and started again to see if it would track HR whilst already elevated up to peak again.

  • Former Member
    0 Former Member over 5 years ago

    Yeah, this is really bad. I'm going to return tomorrow. Unfortunate. I really want to love this watch. Just not worth the hassle, especially at the $800 price point.

  • Former Member
    0 Former Member over 5 years ago

    Got a Fenix 6 Sapphire this week. Hiked up Scafell Pike yesterday and apparently my maximum heart rate was 110 bpm. This just doesn’t work, how is Garmin getting away with this? I will have to return it as not fit for purpose, especially when Garmin claim their wrist sensor is “cutting edge”, well apparently not, my Apple Watch never had this problem, nor did it think my heart rate was consistently in the 90s when resting on the sofa.

    Looks like this has been going on since October, so presumably this can’t be fixed in firmware. I think they should do a recall.

  • I think they should do a recall.

    unfortunately the watch works for a lot of people (works for me) but it doesn't for some.

    Probably is the situation with the majority of watches and brands out there.

    So a recall would be impossible and probably a fix either. 

  • Same here... Mostly fine when running (there were some exceptions) but very random throughout the day.

    This HR sensor is a failure and it's probably not going to be fixed by software.

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

    I have my F6x sapphire since october 2019. Since then i used it for hiking, walking and ski touring. My OHR was useless. Max hr was 120 (it should be 160), average 104 (it should around 150) so like I sad, useless. Now in spring I went out with my MTB and it looks like it is working pretty much OK. I have no idea whats the deal, but it seems to be working OK on a bike and nowhere else... go figure 

  • Former Member
    0 Former Member over 5 years ago

    Sorry if this has been covered before, but I have noticed (and I think read somewhere recently) that the heart rate calculation varies according to activity.

    I did a couple of experiments of Fenix 6 vs Polar Chest strap, where I did jumping jacks to get my heart rate up to 135 and then compared. When set to the hike activity, the Fenix barely changed ( went to about 90), however when set to run activity, it was spot on and matched the polar reading.

    I guess there are some rate of change filters in the hike mode that restrict the rate of change of heart rate, i.e the reading will move but very slowly. Either that or the readings are less frequent to conserve battery, however I didn't notice it capture any high heart rates during a 6 mile hike the other day.

    I can't find any documentation on this, can anyone point me to some?

    Perhaps a possible solution is to make a copy of the run activity, rename it to Hike HRM or something, and then change all the screens to the ones I want during a hike?

    I repeated the test a few times and the observations seem consistent.

  • Former Member
    0 Former Member over 5 years ago

    Hey Ya'll, after some testing, I just went ahead and copied the running activity, and for now, renamed them 'hiking' or whatever. Seems to be much better. The running activity HRM has been pretty good thus far. I recommend just copying the running activity and renaming it. I'm definitely leaning towards it being a software issue since it is better with some activities and piss poor with others (hiking). I bet Garmin can fix this.

  • I bet Garmin can fix this.

    I bet they won’t. Issue has been reported since last summer when it first appeared in the FR945 beta firmware. No fix since then and I really don’t care anymore. Garmin should just stop claiming they track 24/7 HR, because it only works reliable when you start an activity and the rest of the day it sucks. I will keep using my Fenix just for activities and for 24/7 tracking I will switch to a Fitbit Charge 4 for now. Not at all what I intended when I bought a 900 dollar watch only a few months ago, but when a 150 tracker just works 24/7 and my shiny watch won’t.. I’m through waiting for a fix that will/won’t come. I’ll bet they announce a Fenix 6 plus or 7 in a few months that will have a new HR sensor.