External Heart Rate Monitor Issues with Version 20.16

Epix (Gen 2). Software Version 20.16. Paired with Coros Armband.

I had no issues on the version prior to 20.16. These issues started when 20.16 was installed.

I have an issue with the heart rate becoming fixed on a fixed value part way through the run. It works fine for a while (today, about 25 mins), then locks onto a particular heart rate (today it was 154) and it stays on that heart rate for the rest of the run. See below for the HR graph from Garmin Connect. On other days, it will lock onto a different HR value.

Any ideas if the just released 20.22 will fix this issue? My watch is basically worthless at the moment…

Also, is it possible to exclude the HR from this run in the metrics - this run looks like I did an hour V02 max workout…

  • My open case with Garmin says it’s only my coros heart rate monitor issues despite the issue occurring only after the change being the Garmin beta update. 

    since the open/secure change I’ve had countless issues with Bluetooth sensors from heart rate, Stryd, moxy, core body temperature but it’s all the third party sensors and not Garmin.

    at this point I’m trying on moving from Garmin, probably to a coros despite the overall lack of functionality coros had compared to Garmin 

  • Thanks for the info. I initially got the FR165 and FR265, but returned them after HR issues. Bought the Coros Pace and had zero issues, but did not like the small screen. I picked up the Epix Gen 2 with a deal and it worked great until the software update. If I have to buy new stuff, it wont be with Garmin. I will be going back to Coros with the Pace Pro. At the moment I have a useless brick on my wrist.

    The other frustrating thing is that the external HR monitor works perfectly with my Apple Watch. No issues at all.

  • Suunto Race S is another option... Currently I have both and both have their Pros and Cons...

  • I did a strength workout today with the 20.22 version and it worked fine. I have a couple of big workouts coming up - two fairly long runs - one will be an open run and the other a workout, so should get a good indication if this issue is fixed..

  • I completed the 2 big long runs (1 open, 1 workout) and the external HRM integration worked fine! If all goes well this week, then I will suggest upgrading to 20.22 as the answer!

  • 1 hour after I started my run session, had a race so started it early and my coros heart rate band stuck on 150bpm, connection to the Apple Watch at the same time fine… Garmin says it’s a coros issue. I’m 20.22, will report to Garmin again today

  • Interesting. I have suspected that there is something wrong with the HR readings with multiple activities. For example, I go out on a run, start the watch, then I realize that I have forgotten something, so I cancel the workout, get my stuff and start a new workout. The connectivity on that second activity does not seems to be as stable. I have not investigated this further recently though...

  • I spoke too soon. I went on a long run today (3/16/25) and after about 70 mins it locked onto a HR of 111 for the rest of the run. Everything was fine on my Apple Watch U1 for the entire run. I have a race coming up in 2 weeks and I need reliability, I am strongly considering relegating this watch to paper weight status and getting the Coros Pace Pro instead! Garmin should say on their website site that they do not support third party external heart rate sensors. Really annoying!