Weird behaviour Ruunto Run + Polar Verity Sense
-
I’m using a Suunto Run paired with a Polar verity sense. On almost every run I get scattered spikes in hr that have nothing to do with reality. Happens every 5-10 minutes on average, but it’s random. These don’t look like the Suunto ohr cadence lock, they are much more instantaneous (one second 140, the next two 180, and then 140 again).
Another thing. maybe related, is that the fit file generated by Suunto contains “R-R intervals”, which are not really measured by the Verity Sense. It says that the R-R intervals are 5 seconds (yes, as in 12 bpm ;)). It’s not always the same value but it’s almost always around 5 sec. The only time it’s not 5 seconds is exactly the moment before a spike in measured hr, and then it’s ~10-15 sec (yes, longer when hr is higher!).
I’m really clueless as to what causes it. on one hand it seems like cadence lock, but on the other hand it has this weird relation with the bogus R-R. I wandered whether it might be some sort of connection failure and then maybe the watch tries to measure hr by itself.
Also, and even if the hr spikes are a problem with the Verity Sense, why does Suunto produce R-R intervals from the Verity Sense data? This is weird.
-
Just an update this is almost certainly an issue with Suunto.
I did a test to isolate the problem. I went on a run and set the Polar Verity sense on record mode, so it was both recording the run internally too it’s memory and broadcasting the data to the Suunto Run. The Suunto run recorded the data with the occasional spikes, but the Polar Verity Sense did not.
Again, to clarify, the HR data recorded by Suunto came from the Polar ohr. It’s just that Suunto added occasional HR spikes. -
@oni0n said in Weird behaviour Ruunto Run + Polar Verity Sense:
Again, to clarify, the HR data recorded by Suunto came from the Polar ohr. It’s just that Suunto added occasional HR spikes.
Weird. Unless it’s something closely related to Verity Sense, I would expect something similar on the H10 or Coros HRM as well, but that’s not the case afaic. Are u the same guy on r/Polarfitness?
-
@Hari-Seldon True, I moved here when I realized it’s probably an issue with the Suunto Run. A big difference between the H10 and Verity Sense / Coros HRM is that only the former provides R-R intervals. This fact surely affects how the watch interacts with the sensor since e.g. the watch knows that zonesense should not be available with the optical ones. I would guess something in how the watch treats them causes the spikes, and that this is somehow related to the bogus R-R data recorded by the watch. I don’t know whether or not this also happens with the Coros OHR sensor.
