Outdoor cycling heart rate issues

I need some help. I did my first outdoor ride of the year a month ago after riding indoors for the winter. My heart rate monitor wouldn't exceed 100 bpm. I rode yesterday and my heart rate ranged from 160 to 170. So all is good. Well, today I rode again and my heart rate, again, wouldn't go over 100 bpm. I stopped and switched from bike outdoors to bike indoors and my heart rate was back to the 160-170 range. Has anyone experienced this or have a solution? I don't use a chest monitor, if that is what you're wondering and I'm up to date on all updates.  Further, this was not an issue last summer.  

  • When it works fine until a firmware update, then starts playing up its pretty likely to be the firmware update that caused the problem

    13.22 being the culprit? The Epix Pro updated to 13.22 on launch day so from my point of view I do not have any 'before' data but clearly I see the 'stuck too low issue'

    Its why Day 1 reviews from testers under NDA are useless in many ways.

  • Yeah its 13.22 for me thats the issue. And the sensor work fine outside of activities.
    The fact that its affecting both sensor models in the Pro and non-pro suggests that theres something odd going on.

  • What wrist HR firmware do you have? its 12.00.05 on my 51mm Pro with 13.22

  • Mines running the same as you on the old non-Pro

  • Here a short activity -commuting- recorded con the epix. You can see the massive drop on the heart rate.

  • So 11.28 which my Epix Pro shipped with had wrist HR 11.00.03 so it looks like a fairly clear indication 13.22 did do something to wrist HR coinciding with these new reports due the version jump

    FelipeSerra who just posted his HR trace above also sees a very similar instant where things dip for a while like my graph above and it gets stuck in a low HR state.

    @Garmin - Chris can you get some eyes on this?  UK level 1 support won't be able to handle this, we'll just get cut and paste 'solutions'. Very happy for you to access my profile if needed.

  • I just spoke to Garmin and let them know that I'm not the only one having this issue and I referenced your Epix Pro situation.  It was acknowledged that there is s problem and their teams are working on a fix.  They will email me when they have the problem resolved and have provided the update so I can inform others.  I was not given any sense of timing.  

  • I been using the nylon velcro band on my epix and new 245

    Abanen hook and loop on Amazon 

    Amazing watch band btw.

    The issue is the watch (I am guessing firmware as it ran better before ), it is not the fit .

    Been using epix for almost a year here. But updated last week to 13.22 to get load ratio n other new stuff.  Before I was on much earlier firmware. I usually don't update when everything working well, but since I skipped 4+ firmware updates I figure no point waiting. ( Since  for sure I will update this fall for hill score n new stuff )

    I only noticed this wrist heart rate after I bought 245 last week. So now  have a second watch to reference each other to  (using hrm pro plus and without )

    I am just very annoyed at how 245 is more accurate than epix.  The sapphire epix was bought brand new from best buy last year at full price !  While the 245 I only paid $86 last week  from Garmin refurbished ( it arrived same as new except in refurbished label. Pristine condition and battery life ! )

    I can't wait for next update and I may even install beta firmware when it comes out 

    I wear both watches now..one each wrist  so I can reference heart rate anytime lol 

  • Amazing watch band btw.

    I think I am using the same strap - its not a fit issue.

    Here is another section of my ride yesterday where the Epix Pro is completely out of whack - pay attention to the power graph. This hill sprint was from a standing start and its just WAY too low..in fact it only recovers AFTER my sprint finishes! (power drops to zero again). It's so blatently obvious something is up, the HRM Pro trace is from the purple line. Its too far off for it just to be the lag you see with optical. Something is up - it just gets stuck low with a gradual ramp.

  • Anyone has got feedback from garmin about this issue?

    thanks!