Software Update 2.43.8/.12 (2025 Q2)

timecode

@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.

Audaxjoe

@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.

Inge Nallsson

@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…

John Himsworth

@Francesco-Pagano it doesn’t look like it, tested today on a race S after the update.

Laps do show in the suunto app, possible the problem is the phone app (I’m on android but seems to affect iOS too) rather than watch software but it’s not great either way.

atoponce

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.

far-blue

@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.

atoponce

@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.

nseslija

@atoponce I have the same issue with my bike power meter on Vertical…

isazi

Okay how many people are having power meter issues? Users with Stryd, all paired as power meter?

nseslija

@isazi My Assioma is paired like Power pod…

TrailEyes

Updated a couple of days ago and then just now got a prompt to update again for my Vertical. @pavel.samokha any insights? I assume this is a hotfix for something?

pavel.samokha

@TrailEyes yes, hotfix should come. 2.43.12 probably

dulko79

@pavel.samokha downloading 2.43.12 right now

Felix Felicis

@pavel.samokha
Any insights on when the update will be available for the 9pp?

VoiGAS

@pavel.samokha Hotfix just for Stryd? Then I can skip this one…

pavel.samokha

@Felix-Felicis it should be available for 9PP afaik. If it doesn’t this is weird, anyone can confirm this?

isazi

@VoiGAS nothing to do with Stryd

fv4500

@pavel.samokha not here for my 9PP, still on v2.40.44 as the most recent FW version available.

Francesco Pagano

No update for S9PP

Janne Leppamaki

Not available for S9PP