Software Update 2.44.46 (2025 Q3)

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

JonasLarsson

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

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

I’ve done charge cycle, still 10 % per day.

JonasLarsson

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

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

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

I’ve done charge cycle, still 10 % per day.

Correction: 13 % battery drain last 10h.

Tieutieu

@orzechszek indeed, even if special zones for running are off, auto tag is still wrong.
Also I had not checked properly but my HR zones had been reseted after update

This activity was tagged has Vo2max (I was wearing chest strap) :

Miroslava

@Tieutieu i have no problem today i was run z2 slow run and tag is good aerobic

larrybbaker

@JonasLarsson I am not seeing the battery drain with the last update. I just recharged it today and will try and see if I can track it a little closer.

kriskus

@borgelkranz I wish we also had the Vertical watchface fixed: with color accents in the top part just like it was when the watch was initially released.

JonasLarsson

@larrybbaker

Thanks. It’s frustrating but I can handle it

orzechszek

@Tieutieu Thanks, I hope it will be covered.