HR Concerns - It is inconsistent

I've had multiple issues with the wrist HR acting inconsistently at times.  Sometimes the HR will jump up 20bpm for as long as 4 mins before settling back down.  Other times, the HR will remain too low by up to 30bpm before suddenly jumping up to the correct HR.  I always wear my watch on the same wrist at the same tightness.  Here is an example where my HR increased and decreased by about 15bpm suddenly for about 1 min even though my pace or effort has not changed.

Top Replies

All Replies

  • Using a chest strap for solving problems that appeared after updates is a workaround, not a solution. We are not advising "get another device" to users that have new issues with HRV or sleep/nap tracking.

    The solution is in addressing and fixing the HR algorithm issues caused by updates, same as to how Forerunner users have requested and finally got Garmin to recognize issue and take action in order to fix it. That is the option you seem to keep omitting, but in my eyes is the most important one. Holding them accountable isn’t about anger (as you for some reason interpreted), it’s about responsibility. 

  • finally got Garmin to recognize issue and take action in order to fix it. That is the option you seem to keep omitting

    Nah, I'm saying Garmin can work on figuring out how to better solve the signal to noise issue at the same time as people solve it for themselves by buying a cheap HR strap if the issue of completely accurate metrics is meaningful enough for them. 

    How long will you wait for someone else to implement the perfect solution whilst your training and recovery is compromised by bad data? 1 month, 1 year, 10 years?

    Log a case with Garmin. Provide some data and then fix your issue with a strap. Life's too short to get hung up on things that are solved with a $30 purchase (especially after you've laid down $1k on a watch).

  • Not waiting at all. Software bugs do not stop me from training. Simply pointing to actual solution of the obvious problem. 

  • I am wondering when there is the big jump in HR data if the previous data could be adjusted accordingly. That's assuming the end for run is the accurate section of data recording (I'm  on EPIX PRO 2 so same sensor). 

  • Hi

    I found this thread and comment

    ---

    https://forums.garmin.com/sports-fitness/running-multisport/f/forerunner-255-series/324326/erratic-wrist-based-heart-rate-bug-root-cause/1719498#1719498

    All, 

    We have a fix for this bug but are still conducting tests. I'm very sorry for the frustration, but appreciate your patience as we get closer to releasing the fix. 

    I will update this thread when it is available, and do not have a timeline at the moment.

  • It has the same HR sensor doesn't it? I wonder why they don't respond to this thread though?

  • Do you realize that using a strap isn't always an acceptable solution? I do have a strap, however I can't use it every day or on very long runs as it causes irritation, especially when I wear a hydration pack. Wearing a pack makes the strap move more against my skin.

    In most cases WHR is acceptable for me as long as it is reasonably accurate. But I definitely want to avoid those sudden high HR spikes that make it look like was running in Z5 because they distort other performance metrics. 

  • WHR Elevate 4 is shared accross FRxx5 and F7/E2

    Software for this sub-component is also the same WHR/BMX 15.1.1/15.01.01 (last Beta)

    I don't know if Sensor Hub is concerned but same situation with version 28.10

  • Garmin Beta update Sensor Hub, WHR/BMX, we will see and make a wish ...

    20240209 - System - Beta 16.16

    Version updates

    • System Update : 16.16 Beta (was 15.77)
    • BMX : 15.5.0 (was 14.0.6)
    • WHR : 15.05.00 (was 14.00.06)
    • Sensor Hub : 28.11 (was 27.18)

    ---

    16.16 beta / https://forums.garmin.com/beta-program/fenix-7-series/f/announcements/360083/beta-version-16-16---check-for-updates-only---non-pro-only ---Non-Pro ONLY !

  • I wanted to post a comparison between two long trail runs on the same terrain - one with Polar H10 chest HR sensor vs. another with the built-in optical HR sensor. I think this demonstrates really well that there is some sort of adaptive algorithm in the software for the WHR sensor which in some situations makes it quite wrong.

    Let's start with yesterday's run where I used the WHR. This graph shows both HR (red) and Power (purple), as well the the elevation.

    What is interesting about this is that the WHR sensor seemed to work reasonably well for as long as the high HR wasn't coupled with the high cadence. You can see that the HR went up 3 times while I mostly hiked steep uphills and ran everything else with easy to moderate effort. So it was completely fine for the first 2 and half hours of the run. Then around 2:15h there was a 12% uphill segment of the run that I forced myself to run. You can see that both HR and Power went up during that segment, which was correct.

    Then there was a short break around 2:30-2:40h, after which I started a long descent. What's interesting is that the watch seemingly remembered the coupling between the high running cadence and the high HR, so when I started running downhill the HR went back up, and mostly stayed there, and kept gradually increasing towards the run as the terrain became easier. I remember at the time noticing that it was definitely too high for the level of effort. I am fairly fit, and during that downhill I was definitely in zone 2 - below 140. I kept chatting to my friend the entire time. There is no way my HR was in 150-160 range. Actually, by the end of the run it kept going further up and exceeded 160, which is nonsense, because for me that is where my lactate threshold is - I have to put a very considerable effort to be there, which wasn't the case at all.

    For comparison, here is a run that I did just one week earlier on the same terrain. That time I was wearing a chest sensor - Polar H10. 

    You can see that at the end on the downhill my HR was mostly in 120-130 range while the estimated power output was around 200 Watts. For comparison, during my yesterday's run shown above, HR was in 145-155 range for the same 200 Watts output. 

    Another thing you can see how relatively even my HR in the second graph with chest HR sensor compared to fairly volatile HR in the first graph with the WHR sensor.