Software Update 2.44.46 (2025 Q3)

matram

@kriskus for me setting the pace zones correctly fixed the problem. Although I use HR based zones it seems pace is now factored in.

orzechszek

It seems TSS is still forced for classification. I have advanced zones disabled for running and cycling but it still uses it.
In my opinion, there is so many data, so if somebody has default configuration for all sports based on HR and specific TSS is set as default (for example TSS(hr)), then pace zones should be simulated for that training base on HR. Similar behavior when TSS is used.

kriskus

And it also seems it got messed up after the latest update which forced a reset of the zones to default.

Alonzo

Hi everybody, I have an issue with ZoneSense: it stopped working on Race S after an update to 2.44. Perhaps something should be tweaked, but I don’t get where and what.

chest strap is repaired after the update
ZS Suunto+ doesn’t show anything
exercise options - Intensity zones switched to ZS: no “readout” triangle, just a green stripe on the left side (only if ZS target is set).
also updated heart rate zones just by changing max HR - no ZS
also no ZS data in the app after sync.

What do I miss? Or is it a bug?

Brad_Olwin

@Brad_Olwin @Dušan-Ković @duffman19 A tester has reported the bug with Suunto already.

The_77

@Tieutieu is this not conflating two different systems? The automatic run type assignment is based off the personal zones set for HR, Pace & Power, whilst TSS is based off whichever of those you choose (+ZS) to generate a TSS number.

For the record I redid my zones after the reset and had a long aerobic run counted properly and an anaerobic run counted properly too.

Mads Hintz-Madsen

@Alonzo said in Software Update 2.44.46 (2025 Q3):

Hi everybody, I have an issue with ZoneSense: it stopped working on Race S after an update to 2.44. Perhaps something should be tweaked, but I don’t get where and what.

Have you confirmed that your external HRM is actually used during your activity?

Some users have reported that they need to manually activate sensors when starting an activity if they have multiple sensor of the same type paired.

Alonzo

@Mads-Hintz-Madsen yes, HR data comes from repaired chest strap. Wrist OHR sensor is turned off actually.

Tieutieu

@The_77 not sure to understand what you mean. I have set my hr zones to « hr zones the same for all activities ».
So my Z1 run should be long aerobic

safari

@pavel.samokha
This update corrects the Turkish translation errors in the play menu that I mentioned earlier.

There’s also a weather unit option for wind speeds in meters per hour, kilometers per hour, or knots. In Türkiye, we use kilometers per hour.

The_77

@Tieutieu I meant setting pace & power zones too

Tieutieu

@The_77 ok got it. I only use HR zones, set the same for all sports.

Likarnik

@Tieutieu yeah me too, but this doesn’t mean suunto ignores them.

Tieutieu

@Likarnik yep I’ll check my power zones then.

Likarnik

@Tieutieu we should have options to ignore this, as a trail runner you probably don’t know power and pace zones. As I read this is set by 10k/threshold and if you do that, you are always in Z1 on trails

Tieutieu

@Likarnik I checked and « special zones for running » was pinned ON on both my SV and SRs. I un-pinned it, maybe it was the reason power zones were used to tagg my exercise (and indeed they are not set properly)
I’m sure it was unpinned before update. => for me that’s the option that exclude power zones from calculation of intensity
@The_77 thank you. Well I recommend to all of you to check if after update you are not in my case, with this option pinned ON.

I just asked 5 friends to check also.

[edit : my friend are all in the same situation => special zones for running was ON after update. Cycling remains to OFF. So definitively a « bug » after update, that will cause most off users to have wrong auto-tags. @Egika @isazi did I missed something elsewhere ? If not maybe you could report to Suunto ?]

dombo

@Mads-Hintz-Madsen the same issue with polar H10. and I have not paired second power meter… so I ended with ghost sensor in menu. luckily I’m able to re-pair after soft reset. hint is to swipe back from pairing screen and do not wait to see result of pairing, because then sensor is not connected in sport mode again.

the worst part is, that HR belt is randomly not connecting to sport mode even it worked in previous session few hours ago the same day. I don’t want to imagine myself standing on start line and my HR belt is simply not connected.

and because suunto took time to implement multisensor support (just few years) I bought hammerhead computer for my road cycling. now I wait third year to finish integration between suunto and hammerhead, so at least I can see correct HR zones…

valeR

Im really lost about these metrics now.

what TSS should be selected for running ? As per training peaks it should be tss but on this forum everyone goes for tss(HR) ?
what about trail running then ?
how do you set the power zones ? Is it any useful ?

All my friends having other watch brands do not enter these data manually, everything is calculated by the software itself. So why on earth do Suunto users have to do it without any knowledge on them ?

ninours

No longer works with Stryd or FC COROS, even though they are connected. If, for example, you accidentally disable STRYD (or FC Coros) during an activity where it was working normally, it is then impossible to reactivate it (ever again, as there is no check box). Not to mention the foam battery now on my Vertical. So I’ve reverted to the previous update while waiting for the issue to be fixed.

andrewjknox

Hey guys, couple of issues I’ve noticed since the upgrade (but first, great updates, lots of key improvements )

Been one crash/reboot after trying to start an activity (default walking activity)
One freeze trying to start a custom running activity so fell back to the default running activity
HR chest belt doesn’t connect while starting an activity (though the sensor pairs) so I used my arm strap instead (I’ve got two HR sensors paired now). Tried forgetting the sensor and repairing but didn’t work.