Software Update 2.44.46 (2025 Q3)
-
@Tieutieu I’d like to have both modes too. I used Garmin ClimbPro extensively when I owned a Garmin watch. But I can see that it may be difficult to make a consistent user experience because end of a climb may be either before or after a nearest waypoint.
Perhaps if a single climb mode looks distinctly different, it would be an OK experience to have that as an extra zoom level.
One other thing that I wanted to mention is that I don’t like how Suunto breaks the elevation profile into climb segments. It doesn’t actually break it into climbs and descents but segments based on category so you may end up, for example with a red segment followed by an orange segment, followed by another red segment, followed by a blue segment - all while the same climb continues uninterrupted and the actual grade is nearly the same. That unnecessary creates a lot of segments many of which are tiny, which makes the experience less than acceptable. It works OK for long and steep climbs and descents, but is frustrating on a rolling terrain.
For example I have just tried importing a route for UTMB Kodiak 100K race and that generated over 100 segments on the profile, many of which are tiny in length. Some may be so tiny that the watch skips them completely during an actual run. I wish it worked more like Garmin Climb Pro, which tracks complete end-to-end climbs or descents, but on on single climb you may see multiple colored segments that show you the grade. Another issue with Suunto’s implementation is that the color indicates cycling climb category rather than the grade, so it is quite possible for an orange segment to be steeper (e.g. 12%) than a red segment (e.g. 5%) if the orange segment is short but the red segment is long. For the same reason you can never see a long orange segment.
-
The problem with changing the GPX route during an activity while ascending or descending is still not fixed.
https://forum.suunto.com/topic/13165/serious-problems-with-navigation-with-gpx-routes/
-
@soisan You are correct.
The watch (or Suunto App) may refer all the zones for running; heart rate, pace and power (if a power meter used).
In my case, pace zones ware far out of range; 6’34/km went into VO2max, whereas my Z2 upper limit may be between 5’10~5’15 on flat. Changing it made my Z2 running “aerobic” as expected.
I am not sure if the software update made the change to “all zones referring mode”, or just the pace zones collapsed for some reason. -
Continuing from the above.
I noticed “unexpected VO2max” specific thread; https://forum.suunto.com/topic/13517/how-comes-this-run-is-classified-in-suunto-app-as-anaerobicIt seems that all the zones are not referred but the one specified for TSS may be.
Before the software update, it was TSS (hr). After the update it seems to be changed to TSS (pace) for running automatically. Many people (including me) didn’t touch/look at the pace zones which ware far off in fact. That makes easy run classified “VO2max”.It may be better to discuss (if necessary further) in the above thread about this one.
-
I was not able to navigate between my screendata when I am on the map screen. One press mid button didn’t work. I had to hold the button to navigate to my different pages…
Here a video
https://photos.app.goo.gl/EhgwJvERG5E1CRxq9 -
Not sure if it’s a bug but I don’t like how I have to choose my hrm even if it’s the only paired device.
If my HRM is on then I’d like the watch to default to it for all activities.
-
@pavel.samokha: I don’t know whether Suunto is actively monitoring this forum, thus the note here about a topic that is obviously not only affecting me, but others as well:
Bug in 2.44.46: Pool swim mode completely messed up
Please check this, as the bugs basically make the pool swim mode unusable. Thanks!
-
@borgelkranz I contacted support concerning my issues. They forwarded it to the dev team but did not yet receive any feedback. They advise me to roll back to the previous firmware and wait.
However I think I will simply wait for a fix. I just have my 7-day average and HRV range back after the factory reset that was forced on me with the latest firmware.
Maybe it helps if all those that face connection problems with sensors officially report their issues…
-
@borgelkranz Here no problems. Love my vertical.
-
@Mads-Hintz-Madsen said in Software Update 2.44.46 (2025 Q3):
In order to be able to use my H10 HRM again, I had to factory reset the Race and setup the watch from scratch (and now wait for the watch to re-learn my HRV range).
So the multiple sensor support needs some more love (i.e. testing and bug fixing), Suunto!
Did the factory reset resolve the issue for good? Or did you encounter the problem again?
-
@Sportsfreund I love my Race, too. But the new sensor support bugs me.
-
@borgelkranz said in Software Update 2.44.46 (2025 Q3):
@Mads-Hintz-Madsen said in Software Update 2.44.46 (2025 Q3):
In order to be able to use my H10 HRM again, I had to factory reset the Race and setup the watch from scratch (and now wait for the watch to re-learn my HRV range).
So the multiple sensor support needs some more love (i.e. testing and bug fixing), Suunto!
Did the factory reset resolve the issue for good? Or did you encounter the problem again?
The problem appeared when pairing a second cycling power meter to the watch. After the hard reset, I have only paired a single cycling power meter (and the H10) as I didn’t want to risk the same issue again.
So basically, I don’t know if the problem would appear again when pairing a second power meter. But given the many reported issues related to multiple sensors then I have decided not to use this feature but rather wait until the next firmware which hopefully will see some improvements regarding this (yes, I know. - I’m naive!).
-
@Stavrogin
The HRM is major bug for me on the Race 2 as well.I have two different chest straps that I have tried and connected (the Garmin HRM pro and the Wahoo trackr). I will verify the strap I was using is connected before workout in general connectivity settings. It lights up green, shows battery appears to be all good. Then in the exercise settings I again go into “HR Belt” to verify connection. Within the first few minutes of the run it’s very clear the chest strap is no longer connected. Both my runs were outdoors without any other devices nearby. My VO2 outdoor run today did not work, so then it defaulted to the wrist based HR which was all over the place during my warm up. Also no strap, thus there is no ZoneSense readings. I have verified these are working on my Garmin 965. If basic HR strap connectivity is an issue, or I can’t get good HR measurements on my sessions I will have to return the watch. I can’t wait another quarter. I did do a full reset of the watch today (as a basic restart didn’t resolve). I will only connect the HRM Pro, and we will see if that works. (FWIW I only had the trackr connected during my first run, so it wasn’t like I had multiple sensors at that time. I actually initially thought the sensor was the issue which prompted me to try the HRM pro)
-
@burrowsnp I am in the same boat as you. I wish things just worked.
Sleep tracking is like being in an abusive relationship. Total gaslighting from the watch. One night it will track correctly and make me think, “Oh, maybe this is going to work!” But then the next night it will track a 2 hour nap with zero HRV.
I know these things are not super science validated, but if they are advertised as metrics that help athletes they should just work.
Many of us as Suunto supporters make excuses for Suunto with statements like, “Sleep metrics on all watches are not accurate”. But it is supposed to work and not just for some people.
-
@Mads-Hintz-Madsen thanks for the info.
For the record this it what I did:
I first did a factory reset on the current firmware. This helped to remove the ghost sensor from the list of connected devices.
What remains is that I cannot pair my Fazua Ride 60 as a power meter any longer. It gets detected as speed sensor but the watch does not receive anything.
So I decided to downgrade to the previous firmware, so that I can use my power meter while I wait for a fix that will hopefully come.
-
@pavel.samokha with respect to sensors, as far as I can see I can’t set up an activity where it doesn’t search for all possible sensors.
For example I have two bike profiles, the generic for my dumpster bin commuter and one for my nice bike - which has a speed/cadence sensor.
Having added the S/C sensor again this update, the normal bike profile looks for it, and I can’t tell it not to, as before. Bug I suspect.
