Software Update 2.44.46 (2025 Q3)

Stefano M64

after the update every time I put the watch on the charger I get a “Map downloaded successfully” notification, even if I wasn’t downloading anything, why? it’s only me?
This happens in both Race and Race S

orzechszek

Hi,
Does anybody know why in such case when HR zones are set and properly visible in results:

training is still recognized as Vo2max?

Squirrel

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

training is still recognized as Vo2max?

https://forum.suunto.com/topic/13517/how-comes-this-run-is-classified-in-suunto-app-as-anaerobic

SamuelP

@Stefano-M64 happened to me also yesterday… I had 10% and left it “charging” and after 2 hours when I wanted to go out for a run it said “map downloaded successfully” and the charge was still at 10%, so it didn’t even charge the watch after removing the “map download” screen with the middle button it started to charge. That’s a bit weird. I also didn’t have any maps in the download queue.
I’m using a Vertical.

Sportsfreund

@VoiGAS not in my iOS app. There only I can see the other modes but without values.

On the other hand I thought you can set this value in the different activity modes in the setting.

VoiGAS

@Stefano-M64 Me too. I think already three times where I got this Maps downloaded message

Jan Suchánek

@Stefano-M64 Mee too. Race.

Chris_Dx

@Theo-Lakerveld Thanks for the information, I will try to do the same. Let see if I have the same good results.

soisan

@Squirrel I admire your patience with some members in this forum…

dombo

today I realized, that probably by update my global HR zones were altered. specifically 3-4 and 4-5 zone borders. on top of this my crank based power meter needed arm length (this info is set in the sensor and was not requested before. arm length is important only for pedal based power meters…)

Dareo

@isazi Can you be a little more specific? A general timeframe would be helpful. Thanks

Stefano M64

@SamuelP @VoiGAS @Jan-Suchánek OK, thanks!
so, it’s a bug caused by the new carger-less map download feature

isazi

@Dareo no I cannot, I only know it is coming soon

Inge Nallsson

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

To be noticed, guides created before update must be deleted and created again so it can work

I had hopes for this not to be the case, but alas… “Interval workouts” built before this FW update (Running tried) have no repetition counter, no 5 seconds beep before transition and no warning vibration/beep when not keeping the set target.

Ah well… I have time on my hands. But I do wish that the Suunto app had a ‘copy’ function within the workouts builder.

Tieutieu

@Inge-Nallsson more than « duplication of workouts », I’d like to be able to share with friends. But i guess ours needs could be fed at the same time.

suzzlo

After the firmware update, all my setting were reset to default values, so probably you have had same behaviour… for the ones having issues with ZS ring on riding… have you already check if the HR zones were correctly defined and activated? if not, default HR zones should be on place…

just in case it helps…

Inge Nallsson

@Dušan-Ković said in Software Update 2.44.46 (2025 Q3):

I just tried Zonesense intensity rings on a gravel ride. I think there is a bug

I can confirm this on my Race S during a Running session. Using a “Custom” sport mode; ZoneSense SuuntoPlus app not active and choosing “Exercise options” -> “Intensity zones” -> “ZoneSense” (without a target zone set).

Only the white arrow was visible (after the initial 10 minutes) without any coloured ring segments until some seconds of Anaerobic effort was detected (yellow segment became visible). After which the green segment also got activated - when my effort fell to that level.

I did not see any occasion where the yellow segment was highlighted when the arrow had fallen below that area.

On yesterday’s ‘Custom’ Trail Running session I had set a target zone (Aerobic) for ZoneSense and that worked perfectly, with a green segment visible from start and then the arrow popping up after 10 minutes.

Tieutieu

(For the record : Even if i didn’t lost any data/settings after update, I had to soft reset both my SV and SRs to make OHR work)

Inge Nallsson

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

for the ones having issues with ZS ring on riding… have you already check if the HR zones were correctly defined and activated?

I have recreated all my zones (HR/Pace/Power) so the initial missing ZS ring segments bug does not originate from that FW update wipeout.

Dušan Ković

@Dušan-Ković said in Software Update 2.44.46 (2025 Q3):

@isazi I just tried Zonesense intensity rings on a gravel ride. I think there is a bug.

first 9 minutes there was no rings, which was expected, as zonesense kicks in after about 10mins

after that only white arrow showed, there was no color rings.

at 25mins in activity I had a hill and I went onto an-aerobic zone, suddenly ZS zone 2 showed yellow

after the hill, it went back into ZS zone 1 and suddenly ring became green, so we have colors

during the ride I kept glancing into the rings and on multiple occasions white arrow went back to zone 1 but yellow ring (zone2) was highlighted

I am guessing that it is just buggy behaviour and devs should take a look at it more closely

I just had a 10km trail run. Zonesense was acting super weird. I had set intensity rings to zonesense, didn’t set target. I also had zonsense S+ app active and I had custom field for HR. I was running easy pace, something I would consider aerobic based on the feeling. During almost entire run, zonesense was showing me that I was at end of an-aerobic or end of VO2Max zones, but my HR was 130-140bpm. Zonsense rings and Zonesens S+ app were showing me the same. S+ app showing me something like 10% aerobic and rest was yellow or red.

BUT, when I ended activity and checked analysis I’ve got completely different zonesense data.

Unfortunately, I don’t have any picture of watch during running, but it was showing me completely wrong data. The data in the app is more in line how I felt, but during exercise, realtime data was not correct