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

Wrist heart rate monitor WHR inaccurate

I am seeing same issue.  I'm posting a picture showing a Garmin 935 on one wrist, and a Garmin 945 on another wrist (excuse the makeshift armband, I can assure you the "tightness" is same on both). So, this is same person, skintone and setting...just a different 1 generation older Garmin model watch using OHR.  They are showing wildly different readings:  54 BPS (on 935, top) vs 147 BPS (on 945, bottom).  

Because the 945 OHR appears inaccurate it is compounding issues with the 945 that have changed and were supposed to be FEATUREs and a reason to buy it in the first place (I may not have all the Garmin marketing terminology correct here):

New Feature 1 - Exercise Load:  The new watch (and perhaps Garmin in general) seems to have shifted to using "Exercise Load" -- versus the old way of using Training Stress Score (TSS).  Since Exercise Load is based on EPOC and therefore, an extrapolation of Heart Rate using software modelling, none of that load for a given workout is accurate.   IMHO:  If you are going to switch to this EPOC methodology, you have to be very very sure the HR is accurate or be able to have a user setting to go back to TSS.

New Feature 2 - Fitness Training Progression:  Using EPOC from New Feature #1 cannot be showing fitness recovery vs fitness progression over time because EPOC is not accurate to begin with.  For example: The watch keeps claiming I'm doing "High Aerobic" workouts when in fact, I know I'm doing only a "Low Aerobic" workout (like a Recovery Spin).   I've been fighting with this watch for weeks trying to understand how I could not be in recovery by this point!!  Looks like I will ignore and use Training Peaks TSS ....

New Feature 3 - Abnormal Heart Rate Alarms:  I had an "Abnormal Heart Rate" alarm go off yesterday just watching a football game (well over 100, just sitting there, nothing exciting going on).  I was so alarmed I almost made a Heart Doctors appointment today until I found this thread!  

Old Feature - Heart Rate Zones (useless):  I recently completed a Triathlon and used the watch for Run Pacing and wanted to stay in Zone 2 as it was long course.  However, it kept telling me I was at or above Threshold (Zone 3->Zone 4).   I couldn't figure out why it was running so "High" as I did not feel I was exerting myself -- and forced myself to Walk many of the segments to stay in Zone 2 and be able to finish the race.  Therefore, it impacted my race time!!!!   Admittedly about 3/4 through the race I started to "just race by feel" and ignored the watch... but the watch is supposed to guide here.  Further,  psychologically, I was really getting down in the race thinking "What Am I doing wrong"  ... "Am I drinking enough and getting dehydrated and that is why heart rate is so high", "is it heat related", etc.....

Don't get me wrong:  I've been an avid fan of Garmin triathlon watches for many many years and have also owned since the Garmin Forerunner 910XT and always upgrade - I've never had any issues like this.  However, at this point, I'm thinking of going back to the 935 which I'm glad I had not time to sell yet.

Can anyone from Garmin help here?  The watch is clearly defective and should be fixed immediately either through software update or replacing these altogether.

  • I don’t find it better when I’m more active. Indeed - I find it much worse. 110 HR when it’s over 170 IRL? What’s up with that? So I made the band tighter and tried it in the inside of my wrist and whatnot. Nothing doing - the HR shown when doing a hard (level 5) workout is WRONG. I would be fine working with Garmin on solutions and I actually can help but the way things “work” now they don’t actually work. I did file a ticket at some point and the (clearly L1) tech suggested I record a workout with monitor and watch at the same time. Well, seriously? I can and I have but seriously? When I’m going on a hiking trip I don’t take a HR band. Why would I? Whatever. Seems there’s a hardware or firmware problem. Again, I’d be happy to help resolve this.

  • same issue here and I will be returning my 945

  • same issue here and I will be returning my 945

  • To test the sensor pace a finger over the sensor and check heart rate. If it is correct then the sensor is working.

    To get better results. Wear the watch further up the Wrist and Tighter.

  • My problem is cadence lock, it's a well known problem with watches where measured hr defaults to run cadence. My 935 and 735 suffered too. My problem now is that I wear a coospo hrm above my elbow which is 100% accurate but the watch keeps reverting to wrist hr and never reverts back. It must have a ant+ dropout but doesn't reconnect.

    In summary garmin watches are crap at running wrist hr but to compound that when I use an ant+ hrm it reverts back to the unreliable wrist hrm mid-run! Now I have to remember to turn wrist hr off before and back on after every run. Bloody useless! 

  • Garmin have always had problems reconnecting to sensors mid-acitvity. 

    A simple algorithm would stop hr being recorded if exactly the same as cadence. Easy to do. I'd prefer no hr measured to incorrect hr. It wrecks all my thresholds and training peaks analysis. My heart doesn't even go to 171bpm yet I keep getting it as a new threshold notification!