Wrist Heart Rate bugged?

Welcome in the club. I have to bought Polar Verity Sense and started to use it on activities. HR readings is now totally different than wrist hr

Shame Garmin, shame

Hi guys, we have another soft version. Someone checked this bug?

Hi, I did exactly the same test with the Garmin chest strap HRM and my fenix 7x pro. The results of the fenix 7x are totally off, it is basically not usable at all. I think that all readings of the OHR sensor on the fenix are not reliable at all as I also have a Samsung galaxy watch 6 classic that was much more in line with the chest strap. I am on v17.23 now but have noticed this issue already few months ago and my watch is only 6 months old. IMO this is a much bigger problem then it appears as all other metrics like HRV, body battery, stress, sleep tracking etc. are affected by this OHR sensor issue. Basically all the metrics that the watch is calculating/outputting are wrong...so is there even a point to use the device in this state? Also is this just a software issue as we have been told by Garmin or actually there is a hardware problem?

I agree with you that Fenix 7 WHR data is quite poor. However I should point out and in your screenshot the two heart rates have different scales - that's why they look so much out of sync. Also, that is why I had to use Fit File Viewer to get my screenshot - that tool allows to sync scales. 

Furthermore, I don't think this is a problem with the sensor itself. When I bought Fenix 7X in 2022, initially it was surprisingly accurate and I had zero complaints. Then Garmin had "fixed" it at the end of 2022 which introduced a lot of inaccuracy such as the HR suddenly spiking and being stuck at high HR. Then Garmin further "fixed" it to make it being overly conservative and being stuck at low HR while the occasional high HR spikes haven't been fixed. It has become very unreliable in the 6 months or so, especially when used for activities with variable heart rate like trail running on steep terrain. But I believe all of that is caused by a heavy postprocessing in software. 

Seems to work (somehow). Now my sensor do not report those "naps" and seems to be reading properly.

Thank you for pointing out the scale difference and below is the graph generated with Fit File Viewer as per your recommendation, much appreciated! Still, about 70% of readings are off a lot. I truly hope that you are correct and this is just a software issue that as said it Garmin "fixed" but hopefully will actually fix it with the next update. I called Garmin and it appears that they are very well aware of this issue and are actively working on the fix. The question is how long all of us will have to wait to get back fully functioning watch again...

it's the same with the Forerunner series, off since end Q3/start Q4 2023. The moving average filter that seems to have been applied in later f/w updates only makes things worse. 

Interval training used to be possible, even with OHR: though not precise, it followed pace nearly instantly, now it's impossible and need to use chest wrap everytime for consistent readings.

Very old issue now, for a basic and so important feature on the watch !

---

I'm tracking since a long time now, but the fixes provided since approx 15.xx F7/E2 (and all models FRx55/x65, etc.) didn't correct the regression introduce in the past.

Hi All,

Have anyone solved the problem?