Heart Rate inaccurately low during almost all exercise

I notice that at rest and throughout the day and night my Instinct 2 Solar accurately and frequently monitors my HR, and I love the resolution and function of this. However, during all activities (the reason I bought the watch), my HR is consistently low, either half of what it really is or a solid 30-50 bpm down from my actual HR. 

My primary activities are backcountry skiing, stairclimber, trail hiking / running, and in general activities that involve sustained HR near or at my aerobic max. I will be traversing a steep up slope on skis and feel my heart hammering, take a timer measurement on my wrist and count 180 bpm, only to see my watch clocking in at 130 realtime. I have done this in multiple conditions, including while maintaining full cardio load, and coming to brief rest to measure. This dramatically alters my calculated loads for these activities on Connect and Strava, which defeats the purpose of monitoring vitals for technology informed training. 

I have gone through all of the garmin support articles and suggested fixes, I have even shaved my entire wrist to get a better fix on the sensor. I have experimented with every position, orientation, and tightness, and switched wrists.

The only thing that has worked inconsistently is letting my HR come all the way down to rest, and then ramping it back up again. From a signal processing standpoint, It's almost as if the HR sensor signal is aliasing until the HR frequency jumps under Nyquist. But this fix does not work consistently, maybe 30% of the time, and man does it kill a good workout. 

I have had an instinct 2 for several months now and this is becoming a deal breaker, and I may see myself go back to Apple as a result (watch ultra). I love almost everything about this watch, but I feel like, how can they not get this one core thing right? 

Has anyone else run in to this consistently? Does anyone from Garmin have any further suggestions other than the boilerplate support links? 

  • Former Member
    0 Former Member 9 months ago

    I have the same problem here, after upgrading from 15.07 to 15.08, the problem persists with 16.10

  • From my experience so far, all on 16.10, in the passive 24/7 HR monitoring, watch is good enough for sedentary life. The moment HR raises moderately it is a hit and miss and extremely unreliable above that. These are observations by simply glancing at the watch, without starting an activity and comparing to a HR strap or Fitbit.

    This trend has been noted by countless users on the forums, and appears to be an expected behaviour and a battery saving feature rather than a bug. Moral of the story is if you want reliable HR data, you MUST start recording an activity.

    HR has been mostly accurate once you start recording an activity with the biggest HR anomaly noted during a benchmark run where HR was 20+bpm lower than on the repeat. A few momentary dips in the HR on other activities have been noted but largely positive experience otherwise.

    These momentary drops in HR during recorded activities could be a bug as just about all reviews generally have the HR accurate, often perfectly matching the HR strap. Other part could be the known limitation of the wrist HR monitors. For me, it's HR strap cycling but do expect reasonably accurate HR data from the wrist while running.

  • From my experience so far, all on 16.10, in the passive 24/7 HR monitoring, watch is good enough for sedentary life. The moment HR raises moderately it is a hit and miss and extremely unreliable above that. These are observations by simply glancing at the watch, without starting an activity and comparing to a HR strap or Fitbit.

    This trend has been noted by countless users on the forums

    I know there are people who have problems with the optical sensor, but I do not know what percentage of the total number the "countless users" represent. However, it is definitely not the case how it works with me.

    I did some tests many times with several watches, but to be sure I just did it again right now with my I2, in case something has changed recently. I've put my HRM chest strap on, opened the Strava app to see the real-time reading from it, and in the same time I looked at my I2 display watching the HR.  I did not start any activity on the watch, and the strap was not connected to the watch! The values on both the watch, and from the strap were at 79 and 80 respectively when starting. I begun doing quick squats, and the HR value started rising immediately (within 5 seconds), going to 90 bpm, and then continuing far over 100 without any considerable differences between the two (I'd tell under 5 bpm most of the time).

    I can repeat the test on another day, record the data and post it here, though it won't help anyone having problems with the HR readings anyway. I am just posting this to deny that the watch is not designed to read high HR in non-activity mode. It is, and it does work (for some at least).

  • ... BTW. something else, of course, is the all-day HR graph, which does not show the life data from the HR sensor. It only shows the averages over 2 minute intervals. And there you won't see any short bursts of the high HR, of course. It in no way means, the sensor did not detect it.

  • I looked at my I2 display watching the HR.  I did not start any activity on the watch
    I can repeat the test on another day, record the data and post it here

    Thank you! Make sure that you read the HR from the watchface and do NOT call up the HR widget.

  • I know there are people who have problems with the optical sensor, but I do not know what percentage of the total number the "countless users" represent. However, it is definitely not the case how it works with me.

    There is several of us at least in this thread with an issue and if you search "HR low" you will find many more users over the years, across just about every watch model with unreliable HR data, both with recorded and passive modes. I didn't count, hence countless.

    It only shows the averages over 2 minute intervals.

    In this case (2nd set of screenshots), sensor did not detect it, full stop. Can see smoothed data (over 2,5,whatever minutes)  for the second half matches well but first half doesn't even remotely match the HR strap.

    Unreliable HR data

    I am just posting this to deny that the watch is not designed to read high HR in non-activity mode. It is, and it does work (for some at least).

    That is what this forum allows us to do, give feedback to Garmin on what is working and what is not. The fact there are algorithms calculating HR, means there is always room for improvement so HR can hopefully work well for everyone.

  • the all-day HR graph, which does not show the life data from the HR sensor. It only shows the averages over 2 minute intervals.

    How Does Heart Rate Data Display in Garmin Connect?

    ….“Garmin Connect averages out the heart rate values at 2-minute intervals while watches average out the heart rate values at 15-second intervals.“….

    https://support.garmin.com/en-US/?faq=dLag82HPPk0l4T2tRELSgA 

  • That is what this forum allows us to do, give feedback to Garmin on what is working and what is not.

    This forum is a uses-user forum. It's possible that a Garmin employee is reading here, but I wouldn't expect it.
    If you want to report problems to Garmin, you should contact Garmin Product Support.

  • There is several of us at least in this thread with an issue and if you search "HR low" you will find many more users over the years, across just about every watch model with unreliable HR data, both with recorded and passive modes. I didn't count, hence countless.

    Yes, there are several threads on the forums, but I see mostly the same people posting on them. And considering the millions of users who do not complain, I wonder whether the "countless" users represent 0.1 ppm, 1, 1%, 10% or more.

    Garmin Connect averages out the heart rate values at 2-minute intervals while watches average out the heart rate values at 15-second intervals.“

    This is actually an outdated information. The 2 minutes averages in GC are correct, and exactly what I wrote, but most of the recent models (including I2) no more sample each 15s. They now sample continuously. You can check it by looking under the watch. While still about a year ago the sensor only flashed each 15s, now it flickers continuously all the time, during the sleep mode including. And the displayed value also changes in real-time every second (if the HR changes). Weather the displayed value is a floating 15s average or not is a question, and it is quite possible, but the watch is still capable of detecting high HR even in non-activity mode.

    Make sure that you read the HR from the watchface and do NOT call up the HR widget.

    Makes little sense to watch the continuous real-time HR on the watchface, because the watchface updates ony once a minute, unless you wake it up with the wrist gesture, or by pressing a button. But if you wish I can do that, though I will have to wake it up each ~20s. 

  • They now sample continuously. You can check it by looking under the watch.

    Sounds a bit like Schrodinger’s cat. You’re not sure what’s actually happening until you look. But when you look you can’t be sure what was happening before you looked because the very act of looking changed things…or did it?