Discrepancy in HR statistics between watch and app
-
@Tomi said in Discrepancy in HR statistics between watch and app:
Will try today to see if anything has changed.
No changes, identical results to what I previously posted. HR delayed roughly by one minute after 36 minute run.
-
@Tomi Thank you. I was able to bring this topic here to the support team’s attention. Hopefully, they’ll find the error soon.
One more note: Today I tried the Polar Verity Sense, but I couldn’t reproduce the issue in three activities (2x cycling, 1x walking).
-
Today I had several activities in a row (Suunto SmartSensor):
- Cycling
- Swimming
- Cycling
- Running
- Cycling
Noticeably, the problem only occurred while running. Cycling and swimming were no problem
-
Another day with multiple workouts (Polar H10):
- Walking (correct)
- Trailrunning (0:51 - deviation ~5 min)
- Hiking (1:40 - deviation ~15 min)
- Walking (correct)
Yesterday with the Polar Verity Sense:
- Walking (correct)
- Running (1:15 correct)
- Trailrunning (0:45 correct)
With the Polar Verity Sense it always seems to work. Whether the ZoneSense calculation has anything to do with it
-
After the latest update, I’ve also regularly noticed a strange discrepancy in the heart rate display on my watch.
Sometimes it freezes and only shows a much too high or low heart rate.
The graphs also show a delay or a completely unrealistic heart rate.
I’ve turned off zonence, but that doesn’t make any difference.
I have a Polar H10. -
@Jacobus said in Discrepancy in HR statistics between watch and app:
I’ve turned off zonence, but that doesn’t make any difference.
How do I turn off ZoneSense?
That also looks strange. What software are you using to display the data?
-
@Yves_ A bit unclear on my part, I turned off the zonesense app.
This is a screenshot of Intervals.icu, by the way. -
@Jacobus ah, okay
I meant this because of the ZoneSense calculation. This is the only obvious difference between the results from the Suunto SmartSensor or the Polar H10 to the Polar Verity Sense. The optical Sensor doesn’t have that.
Although I still don’t understand what is depicted with it
-
As of the latest (3.21.14) firmware update, the problem seems to be completely fixed for me
-
@Tomi That’s what I thought after the hotfix, but unfortunately it still goes wrong regularly… Zonesense still stops after an hour of training.
-