Software Update 2.44.46 (2025 Q3)

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.

JonasLarsson

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

@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 ?]

Thanks for saying this. Was the same for me.

orzechszek

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

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

@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 ?]

Thanks for saying this. Was the same for me.

As I mention before, I had UNPINNED/OFF special zones for running/cycling and it still not properly auto-tag. Somehow it forces special pace zones, even it is disabled.

JonasLarsson

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

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

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

@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 ?]

Thanks for saying this. Was the same for me.

As I mention before, I had UNPINNED/OFF special zones for running/cycling and it still not properly auto-tag. Somehow it forces special pace zones, even it is disabled.

Excuse me, but what is auto-tag?

timecode

@JonasLarsson It’s when the app automatically tags your workouts based on exercise type - Aerobic, Anaerobic, Vo2Max etc.

JonasLarsson

@timecode Ah, I see. Thanks!

Tieutieu

@orzechszek Ok I have a running session tomorrow night, I’ll see if I have the same behavior.

sryke

I have reverted to 2.40.44, last firmware that worked without any issues for me on my Race S

As already mentioned here in this thread, the main issue is with Stryd connectivty.

Stryd connects with Race S for a run but Race S wattage is recorded in the Race S activity and shown on the watch. However, Stryd records the activty, too, and stores the data in the respective fit file
Sometimes the Race S does not send a stop-activty signal to the Stryd pod, it keeps recording.
I’ve tried two different Stryd pods, same behavior.
Then something new came up, I don’t really know, what happens: On and off the charger the watch makes this sound, when one puts it on the charger. Every 15 seconds or so. When on the charger it does not charge. Then it stopped and was quiet for a while. Then it started again. Then I gave up and reinstalled the old, old firmware.

VoiGAS

@valeR Suunto is using the TrainingPeaks metrics. It needs a little more attention, but then is useful for “professionell” use with training plans and everything.
If you have the zones right every TSS value is somehow right. I use Power TSS for intense runs, HR TSS for long, slow runs/walks. If you have a Power Meter you don’t need Run TSS in my opinion.
If you want it easy you can just always use HR TSS - thats the one that always works - also for Trailrunning

borgelkranz

@borgelkranz Turned out that the unnamed sensor was my Fazua Ride 60.

When entering the Sport mode, the Race showed a green overlay that told me that the Sensor is connected. But neither speed nor cadence were transmitted during the workout.

So I removed the Sensor and paired it again. Interestingly it now has a different name…

I am curious what happens when cycling home from work…

Edit:
Rode home. Race reported sensor as being connected but did not receive data. I am really unhappy with the way sensor support was changed. 🤬

ggrego

Hello since the last update my guides no longer indicate the steps but only the repetitions?

brechtvb

@Theo-Lakerveld @Chris_Dx

I also see serious battery drain since the update.

JonasLarsson

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

@Theo-Lakerveld @Chris_Dx

I also see serious battery drain since the update.

Same here. We need an update (or a new Vertical…)

Brad_Olwin

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

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

@Theo-Lakerveld @Chris_Dx

I also see serious battery drain since the update.

Same here. We need an update (or a new Vertical…)

My Vertical is not having battery drain, seems fine. Wait for a charge cycle, you can leave the GPS on to drain through a charge cycle faster.

Tieutieu

@JonasLarsson I had battery drain on my SV after update. After first charge cycle like every time after update, it’s back to normal, and even more : it drains slower than before.
l