Bug with H10?
-
@Vincenzo said in Bug with H10?:
even when I’m exercising with the h10 on, the watch LED keeps flashing on my wrist
That’s right. The chest strap takes priority over the OHR, but if for any reason it stops working, the OHR takes over… hence the need for both to work simultaneously (feature available only for SR afaik)
-
@Hari-Seldon
Thanks for the answer.
So am I using hr from body sensor while the green led is flashing on my arm?Another question, do u know how to change the watchface for my interval training? I have created a running plan for the day but when I start the activity I can’t see my watch face with hr pace and Km.
-
@Vincenzo as mentioned before, yes Suunto Run will be reading the whole time from OHR but will take HR from belt as primary source, and to your second question, there’s no way to use our own screens when doing interval training, on a related note, Suunto will redesign that interval screen as today it’s not easy to read (small font and ui distribution issues)
SRS Ti
SRun (primarily road runner so testing SRun is a must ;))
A3P (drill mode for pool swimming 🤦🤷)
Galaxy Z Flip 3 / Galaxy S24+ -
@herlas said in Bug with H10?:
Suunto will redesign that interval screen as today it’s not easy to read (small font and ui distribution issues)
Glad to know!
-
@herlas thanks man, hope they will fix that interval training… so annoying
-
@herlas thanks for this, I got a new Suunto Run today and first run with it was an interval workout. As it is right now the screens are pretty much useless, so hopefully this will be addressed soon.
Related to the OHR notes above, I’ve seen some weird behaviour on this first run where I had a belt (Wahoo TRACKR HR) paired and connected. During the run I think the watch was displaying OHR readings for heart rate, (with the usual spike at the beginning that I often see with OHR sensors, it peaked at like 191 during the warm up when it should have been something more like 120-130), but the synced fit file appears to be the data from the belt, with no huge spike at the beginning
️
Will test some more tomorrow.
-
Having looked at the device_info fields in the fit file, I’m not sure now that it was recording from the belt at all as there is no mention of the Wahoo TRACKR there. Note that I’ve been using the belt for over a year with my Wahoo Rival watch and it’s always worked flawlessly. I checked before and at one point during the run yesterday and it showed as connected in sensor settings.
Sorry to hijack this thread but if feels like it could be somewhat related?
-
Hi @timefall,
after reading your posts, I ran a couple of tests with my H10. I’ve also set up Polar Beat to record session with H10 offline. Both heart rate recordings match, so at least on my end, everything seems fine. Tomorrow, I’ll put some black tape on the back of the Run and use the H10 again. In this way, I exclude everything that comes from the OHR.
I’m not saying you’re wrong, I’m just trying to understand where the problem lies… -
@Hari-Seldon good idea thank you, I might try the same with the tape today. I read on Reddit that I should see a different hr icon when a belt is connected (heart with little belt either side vs just heart for ohr) at the start of the run on the screen before hitting start, not sure if this also applies to the hr field icon during the run, will also check that.
-
@timefall said in Bug with H10?:
I should see a different hr icon when a belt is connected (heart with little belt either side vs just heart for ohr) at the start of the run on the screen before hitting start, not sure if this also applies to the hr field icon during the run, will also check that.
Yep!
Furthermore, if for any reason the belt disconnects, the heart icon changes to one with a line through it and starts blinking iirc -
@timefall said in Bug with H10?:
I might try the same with the tape today
must be thick enough to prevent light from passing through…
-
@timefall that’s it, normal
️ means only HR from watch -
Tested again today, icon was def the one with the belt before and during the run. I also completely removed the watch for a few minutes to make sure it wasn’t showing OHR data on screen, and it continued to give valid numbers so must have been the belt. Also I see that still the fit file has no record of the TRACKR belt in device_info, so I’ll just assume that Suunto doesn’t populate this in the fit file for whatever reason.
So maybe yesterday it was actually showing the belt data on screen, and the fact that the spike at the beginning showing on the watch but not post run activity/fit file is some other reason
