Suunto Run HR - both native and with Monitor Bluetooth Connectivity
-
@friarmarenn I had the same experience with Suunto Run and Garmin HR 200. I tried for a week and it didn’t worked. Sold the HR 200 and bought the Suunto Smart Belt and it works but the Suunto Run still has some annoying bugs.
-
@Nelson-Diogo I have the same issue with the polar verity sense, and some other person here on this forum had this problem with the Coros sensor.
I emailed Suunto and after initially giving generic responses, they admitted that it’s an issue with the Suunto Run and said they’ll look into it. It was a couple of months ago. I think anyone getting these issues should mail them too. Maybe it’ll motivate their teem to focus on fixing core functionality bugs in updates, rather then the aesthetic gimmicks they are currently pushing in updates (ice too have, but imho making external hr sensors work is a bit more important).
-
Did you update 3.24.14?
-
@ADidier Yes! There’s some bug between Suunto Run and Suunto Chest Strap. I think it’s linked to the watch not being snug enough on your wrist. The connection to the chest strap drops and then the readings starts from the OHR giving results over 200bpm. I did 3 runs with the watch more snug in my wrist and the issue didn’t appeared.
I thought that the chest strap would free me from having to tight the watch but it seems not.
-
Update from my latest training. The Suunto Chest Strap looses connection and doesn’t sync afterwards event tough I wait 3 minutes for the rest HR. It happens mostly at the end of the training but can also happen in the middle.
-
@Nelson-Diogo I have seen this as well and filed a bug with Suunto. They are aware of the problem. When this happens again send your logs to Suunto and note the problem. You can DM me with the time and date your logs were sent, please note the time zone as well and provide your Suunto app email (username). I can make sure that the information gets to the right developers.
-
Apologies if this isn’t the right topic to be posting this issue but it is certainly pertinent to the use of external HR sensors with the Suunto Run.
Putting aside the issues i have had with the Coros armband which i have posted about in that specific topic i have also experienced issues when using a chest strap.
The HR graph normally looks absolutely fine as expected but i am usually given a different max heart rate in the run summary.
This example is from a run where i chucked in three sprints and as the graph shows my heart rate doesn’t go above 180 which is inline with what i expect for the effort. With a chest strap the Heart rate summary seems to always be different to the graph.
What’s odd is when using a chest strap, which works perfectly with my other watches, i get this max heart rate discrepancy and the synced data in Strava will show a mix of the correct max heart rate which is reflected in the Suunto produced graph or it will show what i’m sure is the incorrect max heart figure as produced in the Suunto app summary.
There seems to be something going on here with the relationship between watch and external sensors and how the data is all displayed within the app.
Is this something seen before on Suunto or unique to how they process the data? My experience with Suunto only extends to the use of the Suunto Run having used Garmin for years.
-
@ruNSuunto What I noticed is that those maximum HR values are coming from the OHR on the instances that the Bluetooth connection with the Chest Strap is lost. When using the Watch more tight I stopped seeing those high values even when the connection was dropped. You can correct the maximum HR in the app using the maximum detected by the chest strap but Suunto really needs to fix this connection issues.
-
Similar frustrating experience here.
After almost 5 years of respectable service, last Jan I decided to move away from my Apple Watch 6 (six!) and bought a Suunto Run, mainly for the price + dual-band GPS (hardware details below).After two months of daily use, I’ve to say:
- [1.] GPS accuracy: spot on;
- [2.] HR data: simply wrong and useless with or without external sensor;
- [3.] BT connectivity with iPhone: sub-par and frustrating;
- [4.] Assistance: just “did you try to uninstall the app?” Yeah, sure… -.-')
Regarding 2.: with the external sensor (never an issue with Apple Watch), random spikes here and there in any (literally) run. For example:
In addition, the very same run, with the following heart rate zone break down
…has been labeled as “VO2max”, and I did change my “HR and Intensity Zones” settings. Again, this mislabeling happened all the times. This is not acceptable.
Without the external monitor, the data are simply unreliable and from time to time, the hr simply jumps at 180bpm at stays there for minutes although the effort is low without any doubt.
Regarding 3.: I don’t even know where to start here.
GPS data? Fine on Strava, no way to sync it entirely and correctly on iPhone Fitness app.
HR data? Fine on Strava again, and again no way to sync it on iPhone Fitness app. Below an example of what I see…always…
To fix this, I also contacted Suunto’s assistance and, besides the uninstall-reinstall the app, no real solution or even idea of what’s going on.
My conclusions: I feel the hardware has potential and the price is clearly very competitive, BUT (big but) it seems to me that Suunto is holding it back software-wise and this is totally a shame.
Regards
–P
====================================
- iPhone 15 Pro (now iOS 26.3.1)
- Suunto Run (v 3.24.14)
- Polar OH1 HR sensor
====================================
-
Anche io con il Suunto Run e fascia cardio Polar H10 (ma anche senza) ho avuto un simile scherzo per quanto riguarda la misurazione HR.
In pratica mi segnava un HR Max di 165 BPM mentre sul grafico non si menziona minimamente. Spero in un veloce aggiornamento.
