Fenix 7 Pro is detecting HR from handlebars?

Some days ago I went for my bike ride. I have chest strap Garmin HTM-Tri and the Fenix 7Pro attached at the handlebars thought quad-lock. My screen was locked on maps so after first 7km of warming I looked at the my HR and it was 90bpm. After realizing that my chest strap was not transmitting. probably run out of battery.

First question, how is it possible watch were detecting HR from handlebar all my ride about 45km and it was 90-120bpm? And the second question, is there anyway I can correct that training, because all my statistics are messed up now.

Top Replies

  • detecting HR from handlebar

    Somehow this seems to add nicely to the option I developed from my various comparison tests.

    how much plausible data vs accurate HR data I've been…
  • F7 Pro with latest sensor was good after I had purchased it.

    Which software was on it when you purchased? Maybe there could be the explanation. Imho it is not the sensor itself (It was proven…

All Replies

  • Could you export the activity in the FIT file format (first export option in GC Web), and post the zipped file here? Perhaps it could reveal some clues.

    Otherwise, I am afraid the only practical way to correct the metrics, is doing a few new rides again.

  • Not sure how to post file here. But I made my homework and have opened FIT file in fitviewer and can see that HR was saved were. Also can see under device nr constantly 4375, 3865. I belive nr 4375 is Fenix 7 pro because there is software nr 2119.  Most concerning find is plausible data (a.k.a. HR increases/decreases with climbs/cadence/vibrations) and within a reasonable range based on effort....making me wonder how much plausible data vs accurate HR data I've been collecting if not using HR strap.

  • detecting HR from handlebar

    Somehow this seems to add nicely to the option I developed from my various comparison tests.

    how much plausible data vs accurate HR data I've been collecting if not using HR strap

    That's my question too...I think I found the answer to that at least for myself and made my decision for the time being.

    See e.g. here:

    https://forums.garmin.com/outdoor-recreation/outdoor-recreation/f/fenix-7-series/408780/wrist-heart-rate-still-broken#pifragment-1292=3

    If you want exact data nowadays I'd strongly recommend to use a strap AND switch off OHR while being on strap. Some versions ago there was almost no need for a HR strap if you were only interested in exact HR data except when you want to do a training with very rapid changing HRs which you wanted to record exactly. This is by principle of an OHR. Otherwise accuracy of OHR was really great...Alas no more.

  • Now I see, I`m on v21.19. I do agree some algorithm was probably running on watch itself trying to suggest my HR. I did saw strange behavior of HR sensor on Fenix watches before but F7 Pro with latest sensor was good after I had purchased it. Not sure now, how corrected my night data was all that time. Will try to update to last version and see. 

  • F7 Pro with latest sensor was good after I had purchased it.

    Which software was on it when you purchased? Maybe there could be the explanation. Imho it is not the sensor itself (It was proven - well - almost great with versions like 15.77) but the algorithm which tries to predict where nothing is to predict. Btw. I tested 22.06 in between against 15.77 too. No joy either. I think that's why so many people downgrade their systems nowadays. Never heard that to this extend 2 years ago.