Software Update 2.43.8 (2025 Q2)
-
@Tieutieu delayed slightly for S9PP, should come soon
Watch: Suunto Vertical Ti
Blog: isazi's home
-
@isazi What about Ocean? We haven’t had an update since December last year.
-
@marbjo Ocean is on a different schedule, it will also come, but I’d say don’t expect more than 2 updates per year for Ocean, while the other watches gets 4
-
I see on Joaquims vid that the altitude profile finally has colours matching the climb guidance, after being shown that way in the press release a year ago, if anyone can confirm?
Also would like to know if the bugs with track running are fixed, namely not being able to follow a structured interval session. I’d check but 9PP hasn’t got the update yet.
Lastly, would still like the gradient to make it into the native sports data field list in addition to all the other ones here. My Edge 500 did that after all.
Suunto Spartan Trainer Wrist HR / 9PP Refurb
-
@Francesco-Pagano said in Software Update 2.43.8 (2025 Q2):
Does anyone know if this bug was fixed?
Can someone please confirm if this manual interval issue has been fixed? I’m ready to buy a Suunto Race, but this problem is putting me off.
-
@The_77 yes climb info/graph is colored now. Pretty cool.
-
@Inge-Nallsson said in Software Update 2.43.8 (2025 Q2):
No. The old “Duration” value only reflects ‘un-paused’ time and with the new additions is equal to “Moving time” plus “Rest time”. “Total time” really means everything, paused or un-paused.
I really don’t like this. Personally I’d never ever pause my watch during an endurance event or even a training run because it is way too easy to forget to unpause it. The same applies to auto-pause that simply doesn’t work reliably on a steep terrain. Also, having pauses messes up.with some 3rd party services like Strava. Strava does change the way it interprets the data depending on whether there are pauses or not.
If Suunto wants to surface Rest time, that should not rely on pausing and unpausing. When a watch is paused, nothing else is recorded, including the distance. If I move during a rest, I think that should still count towards the distance.
-
@timecode said in Software Update 2.43.8 (2025 Q2):
climb info/graph is colored now. Pretty cool.
Now we need an ability to arbitrarily zoom and pan that graph. What you show in your screenshot looks great for a short 5-10km run, but it would be much less useful for a 100km race.
-
@sky-runner I agree, that would be very useful. You can still zoom “into” the section you’re actually on, but not the whole graph, true.
-
@sky-runner you have the choice to use either as far as I can tell. It isn’t either or just another option on custom data fields.
-
@sky-runner said in Software Update 2.43.8 (2025 Q2):
If Suunto wants to surface Rest time, that should not rely on pausing and unpausing. When a watch is paused, nothing else is recorded, including the distance. If I move during a rest, I think that should still count towards the distance
I understood the preceding paragraph about you never wanting to pause the watch during training or race, and that is a valid preference. But the quoted paragraph I simply can not wrap my head around. Rest and Moving time has nothing to do with Pausing (pressing the upper button on a Race or Race S). If you stand still, the time is logged as Rest. When you move, the Moving time bucket starts to fill again - with Distance as normal. All automatic.
I looked back at older runs I’ve made, and those where I had made an un-paused stop now show both Moving and Rest times. Those with watch pauses also have the Paused times logged and an additional Total time added to reflect this situation. It’s all very simple and logic if you think about it. ‘Unstopped’ runs, whether by watch pauses or physical body stillness, only show the normal Duration time.
Edit: Runs with “Moving time” now also show a “Moving pace” entry in the SA, in addition to the normal “Avg pace” for the whole time period. I think this is new…
-
I think there might be a bug connecting to Stryd pods. Or at least reporting the data.
Since updating this on my Race S, I have noticed a lot of power drops to 0 on my power data field, after which the 30s average slowly climbs back up. This has been happening frequently during a run. Interestingly, when I download the FIT data from the Suunto app for that run, all the data was recorded. The only zeroes I see in the data can be accounted for when stopping at intersections.
But while in full stride, either during an easy effort, or while executing a structured workout, about half the time when looking at my watch to make sure I’m targeting the correct run power, I notice it’s at 0 then climbs back up to what I’m actually doing in the run.
Can this be looked into? Is there any additional debugging data I can provide to help dig into this?
Thanks.
-
@atoponce I had the same with my run this evening although I don’t think as often as you. My Race S is set to always-on display during activity and about 5 times during the hour long run I noted the power value either 0 or clearly recently 0 (i.e. a very low number climbing back to normal). I use the 3-second avg power value as one of the main metrics on my primary display.
For reference, I use the Stryd with the air power sensor and I had a S+ workout and ZoneSense S+ app running. This is my absolutely normal setup and previous to the latest update I’ve had no issues.
As you say, @atoponce, the exported data seems fine - it’s only the watch display that seems to glitch.
-
@far-blue I too have the ZoneSense app installed and enabled during my runs. Since the new update, I’ve changed my data fields to show those new durations. This morning though was an easy run, so I wasn’t executing a S+ workout. I will be tomorrow morning though, so I’m not looking forward to seeing the zeroes while in the intervals.
