Related
Options
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 over 5 years ago

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? 

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

    I suspect this is the cure for some people who are complaining that their WHR is not working - they aren't wearing it "correctly".

    Over the years people have complained about WHR and nine times out of ten they are wearing it over or next to their wrist bones rather than as the diagram shows.

    https://www8.garmin.com/manuals/webhelp/fenix66s6xpro/EN-US/GUID-F2E7E0A9-FB44-4297-BF4D-D0C31C400C45.html

    https://www8.garmin.com/manuals/webhelp/fenix66s6xpro/EN-US/GUID-08BC6CE7-EB8F-4392-9B7D-714B54D19499.html

    www.garmin.com/.../

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

    I am still waiting for a solution.  No fix or status here.  I have even tried to open the Garmin files myself to see what is being logged.  Unfortunately I have not been able to open the files. If the watch isn't logging the data is it a malfunction in the sensor or the bottom of the watch that is stopping the watch from working?  Is Garmin trying to postpone the inevitable?   the entire time I have a device that I paid a premium for that is not delivering what the marketing material said it would.  How long do we wait before we even get an update?  

  • 0 over 5 years ago in reply to Former Member
    Is Garmin trying to postpone the inevitable? 

    Which is what? 

  • +1 over 5 years ago

    Garmin knows the problem that the sensor brings too low values if one does not start an activity profile, but is nevertheless active. Then the sensor has difficulty registering values above ~ 110bpm. If an activity profile is started, the HF suddenly jumps up into the real area. The problem came into force after FW update in mid-September and has not yet been resolved. If you are affected by the same problem, it is best to contact :

    [email protected] .

    The problem is known there and will be investigated further.

    The ticket number for too low HR outside of an activity profile is:    PSC-87166.

    Whoever has exactly this problem should be added to this ticket.

  • 0 over 5 years ago in reply to tess

    Funny, I had an FR945 and now a F6Pro and both are WAY off when cycling outside of activity. Guess you never cycle?

    Last week I had to run a while to catch a train and my HR was 95 according to my F6, where it should have been 140+. Maybe you are very lucky, but I feel Garmin messed their firmware up last summer. Before firmware 2.50/2.64 the FR945 WHR was mostly fine.

    Garmin confirmed there is a problem with battery management procedures and recognition of activity in the Elevate3 sensor, so I’m not really only speaking for myself. I think Garmin should let us choose between 24h more accurate readings and losing battery life or the other way around. I would gladly lose some battery if my watch can function as expected.

  • 0 over 5 years ago in reply to Former Member

    Sure, that’s the standard respons, even for Garmin. But after wearing wearables for years I can safely say my F6Pro and FR945 are performing pathetic outside of activity. RHR is fine. Polar, Apple Watch, Fitbit: all much better at tracking your heartrate 24h a day. Frustrating thing is: the watch is capable enough, as starting an activity profile fixes the heartrate immediately (without changing wrist placement by the way) so it’s a firmware problem rather than hardware. Without starting activity’s for every home-work cycling ride I get around 300 intensity minutes a week, when using the bike ride activity that’s around 900. And then there’s the body battery and stress score that are completely messed up by this.

  • Former Member
    0 Former Member over 5 years ago

    I think it's a hardware failure

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

    Then the problem must lie in the low frequency sensing mode.

    ph.garmin.com/.../

  • 0 over 5 years ago in reply to JeremyBlck
    JeremyBlck said:
    Guess you never cycle?

    Usually 3-5 times a week. 

    JeremyBlck said:
    cycling outside of activity.

    Never saw the point of doing so.

    JeremyBlck said:
    Last week I had to run a while to catch a train and my HR was 95 according to my F6, where it should have been 140+.

    In similar situations both watches perform quite well for me.

    JeremyBlck said:
    Maybe you are very lucky

    That's a matter of perspective and implies that I'm part of a very few unaffected by some wide spread fault. Just because it's a forum topic doesn't prove that by any means. Many see you as very unlucky. 

    JeremyBlck said:
    Garmin confirmed there is a problem

    Where?  Please post your reference where everyone can read where Garmin publicly confirmed a problem.

  • 0 over 5 years ago

    I did a test today on my bike ride. I had the HRM Dual Strap connected to my Garmin Edge 830, and my Fenix 6x Sapphire using the optical HR both recording the same ride.
    I was out for just over 2 hrs. Average HR on the Edge (HR Strap) was 151, while the Average HR from the Fenix was 130.

    I loaded both fit files into the DCR Analyzer, and aside from the fact that the Fenix was almost always reading lower, the fenix was also all over the place with random hr spikes and drops, while the Edge was much more linear.