Now it happened 3 times. My FR955 somehow showed much lower heart rate at the beginning of the bike ride. Each time I took the watch off the wrist, waited until the HR zeroed, put it back and it locked the HR immediately. Is there a cure for it?
Now it happened 3 times. My FR955 somehow showed much lower heart rate at the beginning of the bike ride. Each time I took the watch off the wrist, waited until the HR zeroed, put it back and it locked the HR immediately. Is there a cure for it?
An example of the ride when Garmin did not record the HR properly in the first half an hour. Then I took the watch off the wrist, put it back after a minute and it locked to the right one. The first 30…
Exact same issue running. Starts low and remains low and then jumps to the actual heart rate 10-20 mins in. Hasn't always been the case. I'm thinking it started with the 18.22 update.
Please stop suggesting chest straps, we are not here for that. Accuracy is not consistency. The watch is less accurate, no doubt, but its accuracy should be enough if it worked.
Interesting. You say you got my point and then directly proceed to elaborate on how another product is better than this product.
English is not my native language so maybe I unterstand consistency different.
I've got HR readings from my watch that looked like that:
and now I'm getting readings like that:
and so on.
There is a difference in consistence and accuracy and for me it is obvious that the readings are not consistent. You can call the non-consistent reading erratic, if that's more understandable. Again, no doubt that chest straps will deliver more accurate readings but that's not what the problem is. And I am not here discussing problems with my chest strap, it is working fine. Thankfully garmin does not update its firmware.
Please do not get my message personally. I was trying to suggest, that if we have purchased watches and bikes (not counting clothes) which total cost is much higher than chest strap, we should also understand limitations of OHR.
Back to your graphs. I see those spikes which bothers you.
Here you are mine from last Monday with chest strap
I have another workout that day with chest strap
and here from Saturday with just FR955 OHR
You obviously notice differences. Gray background is Speed / Pace
Am I blaming OHR / Chest strap? No. Should I consider those spikes as erratic readings? In my opinion No.
I was showing my second chart for another reason. About 4 min 30 sec from start of this run I am crossing multiple lane road. I can tell you that every time I have green light my HR raises. No I am not increasing my pace. I am not rushing forward to cross still on green when it turns to red. It just happens. It is like that always. Well since long time.
Shall I consider this as erratic reading?
And very last thing. We are looking at charts which are generated from raw data. Have you noticed "steps" on the second graph?
Hello,
Today, I conducted a test using my FR955 with software version 15.19 (exchanged through Garmin without performing any updates) and compared it with the EDGE 1040 and a chest strap.
The data are almost identical.
Previously, I had the Forerunner with version 18.22 and faced exactly the same issues as you have described. The first 10 minutes were either not counted at all, or the heart rate was completely incorrect.
It seems best to revert to version 15.19 or something slightly higher. I have a feeling that the problems started with version 17.xx.
What do you think?
Forerunner 955 with 15.19
Edge 1040 with HRM-Pro Plus Software: 8.8
No, I certainly won't make the mistake of updating my watch to version 18.xx again. I've been waiting for months for the issue to be resolved, and during that time, the heart rate data has been completely unreliable.
Now, I'm sticking with version 15.19 installed and will keep an eye on how things go.
Here you can see the nonsense readings the watch has been taking. (Just one example)
My way to my work for example with 18.15:
or here:
or here:
or here:
Version 17.26 also with problems:
Version 17.21
Version 17.18
Version 17.18
Version 16.17
Chat GPT: 
Looks like... I hope the will fix it.