Software Update 2.44.46 (2025 Q3)

Sportsfreund

@SuperFlo75 My SV now also has the update. Everything worked without problems. All values have been retained.

Jugger

SV updated without any problem. Sportmodes and everything else are still there. I never had any problems with new firmware and hope it stays that way.

surfboomerang

Same for me. Update went smooth and all settings remained intact

SuperFlo75

Can someone explain why some of us use the settings, and some not?

Brad_Olwin

@SuperFlo75 Not clear, in testing I had HR, Pace and Power values lost but did not have a watch reset.

VoiGAS

@Jaakers Oh no! I was hoping that this update somehow helps . No automatic resume after the crash?

VoiGAS

@SuperFlo75 And also only parts are lost for some. I have my HR Zones and Sleep data - but the Power Zones are resetted

Dimitrios Kanellopoulos

@thanasis next time there won’t be a reset of the sport modes. Unfortunately this slipped through again.

Yeah I had the same and it does suck.

sky-runner

@pavel.samokha

I used the new software on a 7 hour mountain run yesterday. For the most part everything worked fine.

I liked the new climb guidance 2.0 feature, which is more useful than most people think because it now provides some of the functionality of Garmin’s Up Ahead feature in an indirect way - by turning the crown in the profile view we can see distances to up to 4 upcoming waypoints and also see the elevation profile leading to them. That’s brilliant! That however didn’t work 100% the way I expected due to the app issues, and I will make a separate comment or post about that.

However, what was really wrong is that the update removed my custom HR zones and replaced them, without letting me know, with some new zones which I assume are based on incorrectly detected Lactate Threshold, which was detected a few weeks back. Because of that my relatively low aerobic intensity run (I hiked a good part of it and the average HR was 122), shows in Suunto App as “Anaerobic - Hard”. Furthermore, because it was a 7 hour run and 30% of that was now matching Z3, the TSS went through the roof, and so as the Fatigue metric. Now all my training stats are messed up. Considering that I am in the final training block for an upcoming 100k race, this makes me quite upset.

In general the software should never apply new zones automatically without giving user a chance to verify. I never trusted Garmin’s ability to auto-detect max HR and HR zones and I don’t trust Suunto’s ability to correctly do that either.

Mads Hintz-Madsen

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

@Mads-Hintz-Madsen it’s funny, because before fw update I had to pair my powermeter when I changed bikes and when I paired my quarq (sram rival) powermeter it never asked me for my crank lenght and when I paired my assiomas I was asked for crank length. After update I paired my quark and it asked me for crank lenght, value was saved but when I paired assiomas, it asked me for crank lenght and value can not be saved

As I have updated in my original post about the Assioma power meter pedals and the new update, then the watch does in fact save the crank length to the pedals. I have confirmed that by checking with the Favero smartphone app (which can read the configuration stored in the pedals) that the crank length in the pedals has been changed by the Suunto watch. The reason for the confusion seems to be that Suunto watch does not display the actual configured crank length - it just always shows the default 170mm. It seems that the watch cannot or does not read the current crank length from the pedals. So this is not really an issue. Just confirm with the Favero app that the crank is correct. And then stop worrying

As you mentioned then there is another minor glitch which is that the Suunto watch asks us configure the crank length even when we try to pair non-pedal power meters such as e.g. crank-based power meters or power meter on smart trainers. Of course in such case, crank length configuration is not needed. But luckily this has no negative impact other than confusing the users

So in summary, I think that there is no real issues with the power meter pairing as far as I am aware. Only issue is the the user may get confused because he/she cannot cannot confirm that the crank length configuration for pedal-based power meters is correct and he/she is asked to configure crank length for power meter types where crank length does not impact power meter measurements.