Since version 4.19 I have the following heart rate problem every other run. The watch always sits snugly and correctly on the wrist.
Anyone have similar problems?
Since version 4.19 I have the following heart rate problem every other run. The watch always sits snugly and correctly on the wrist.
Anyone have similar problems?
All,
I am locking this thread due to multiple abusive posts. We definitely understand the frustrations caused by this, but we will not tolerate attacks on other users or Garmin employees.
We are still working…
All,
Thank you so much for your patience as we've worked on improvements regarding erratic HR data (sudden drops/spikes) during for certain activity profiles. I deeply apologize for the understandable…
Yes. I’m also experiencing the same issue and would love to be contacted/included in the report in an effort to get this resolved.
Yes
Since firmware 16.x I have issues with spiking or excessive high heart rate. Up to 201 altough my max hr is 186.
Also the max hr auto detection is not working any longer. It comes up with values around…
Since a few days, I'm having this exact same issue. I'm including two graphs as an example.
In the first one, my HR shot up to 201 bpm. I had to stop the activity, take the watch off for a few…
Please see this section from The Heart Rate Sensor on My Garmin Watch Is Not Accurate:
Can you warm-up before you start your next few runs, and let me know if it continues to show a sudden jump?
I am familiar with this site. I already had a vivoactive 3 + 4 and a Venu 2. And with these watches I never had such problems. I will report tomorrow after my run
As you can see, after 4 kilometers of this run, the pulse jumped by a full 20 beats. It was a flat run at a steady pace.
This kind of jumps should not happen in the HR detection. Because of this, at any particular moment you just cannot make sure that the measurement has anything to do the actual HR or is it just a guess.
Basically, it makes the reliability of HR values zero all the time.
Instead, if the HR sensor detects anomalies, or environment when it does not have a chance to detect values with a high confidence, it should not guess, it should sign that the confidence level is low at that point, so all the other metrics calculation depending on that can be disabled.
Now, what we have is just a mess of a guesswork in 100% of the time. And a lots of garbage data in all consequent calculation (in stress, TR, RHR, all of them).
Did you try warming up before your most recent example? May I have permission to reach out via email so I can request a few pieces of information?
Yes you can contact me per E-Mail.
I will do 4 Runs this week. After that I can post all data.
We are still investigating. May I have permission to reach out so I can add you to our report?