Software Update 2.43.8/.12 (2025 Q2)
-
@Miroslava
Yes, for me the Suunto Plus swimming exercises in its current functionality are a completely useless feature.After replacing the old algorithm with a new one, my watch (Suunto Vertical) became useless for swimming in the pool. It counted however it wanted and whatever it wanted. It divided the intervals randomly and underestimated the swimming distances.
In desperation, I sent the watch to Suunto service.
They performed “calibration and configuration” whatever that means and the watch started counting.
Currently, it counts very well in each of the 4 swimming styles.
Sometimes it is off by + - 25m when I swim, for example, 1000m continuously alternating the dynamic style (butterfly) and back the slow style (on the back).
Unfortunately, the algorithm stopped recognizing swimming styles correctly (front crawl, on the back).
Suunto Viper
Suunto HelO2
Suunto Ambit 3 PEAK
Suunto 9 Baro Titanium
Suunto Vertical -
@Artus-Diver again downgrade to 2.37.48 solved this issue
-
@Artus-Diver Thank you very much for the detailed description, I will try it tomorrow or Friday, I am curious how it will work. It is a basic thing so that the watch can calculate it correctly
-
@Miroslava How it will work is extremely individual. I bought the Race S November 30 2024. Updated the firmware to the then current of 2.37.48 from October 2 2024. That FW counted almost every lap in my swimming sessions (dropped a rare 25 metres here and there) but every style (freestyle, breast stroke, backstroke and butterfly) was logged as freestyle - that is, for me there was absolutely no style recognition.
Since then there have been FW updates with swimming algorithm changes which, for me, have gone from recognition of frestyle, breast stroke and backstroke but not butterfly (logged as freestyle) which had an almost perfect distance counting - like the 2.37.48 - but then over to FW changes which again dropped style recognition while retaining correct distance logging, until finally I now also experience an abundance of dropped laps unless just doing freestyle.
Other people have different experiences… It seems to be an almost impossible task to arrive at an algorithm that both counts laps correctly and discerns all the swimming styles for all of us with our individual stroke patterns.
Suunto Race S
-
@Inge-Nallsson thanks so we will see what will be
-
I agree, you’re right.
That’s why I’ve been trying to convince SUUNTO to return to the algorithm of learning individual swimming styles for a long time.
Unfortunately, without success
Suunto Viper
Suunto HelO2
Suunto Ambit 3 PEAK
Suunto 9 Baro Titanium
Suunto Vertical -
@Likarnik It is indeed a watch display error. I’ve looked at the FIT file in each case, and despite seeing dozens of drops to zero power on my watch while in stride, there are no corresponding drops to zero in the data. So it seems to be recorded correctly, just not displayed on the watch correctly.
-
@atoponce reported to Suunto, waiting for comment (but seems to be acknowledged)
-
@Artus-Diver I remember when you were writing this proposal, ideally, how could we support your proposal?
-
Having a nap while sleeping, again.
This is two nights ago…
Suunto Race S
-
@2b2bff are you sure that these are not different evenings/nights?
I have some similar ones, but first line is the night (from yesterday to today) and the second line is today today.
At least frim this picture your nap does not interfere with your night sleep -
Thank you very much @Miroslava for your support, it’s nice to hear.
Unfortunately I don’t know how to do it.Yes, I’ve been asking about it for some time now and unfortunately NOTHING.
Maybe guys: @pavel.samokha, @Egika, @Dimitrios-Kanellopoulos, @isazi, could help us because I’ve received a lot of technical support from them recently.
I think that if Suunto implemented a swimming style learning algorithm, this topic would be closed.
In addition, I also asks for heart rate zones specifically for swimming.
Note that if you do a maximum of 3 disciplines “running”, “cycling” and “swimming” there is no problem with heart rate zones.
However, if you do more than 3 disciplines, unfortunately you have to constantly change “Standard Zones” between other disciplines.
It is very inconvenient, irritating and time-consuming.
Apart from the above, it would be nice to have a “good !” tool for exercises with a board without using your hands, but after publishing Suunto Plus “Swim Drills” which don’t work, you can forget about it (…).
By the way.
I test the swimming algorithm every day and I have the impression that the current 4.43.12 is more sensitive?
Yesterday on a 4km swim it added +25m, today on a 4km swim it added +50m.
Of course it doesn’t happen often but on the 2.40.44 algorithm it wasn’t wrong at all.I also have the impression that the “segment time” summary is incorrect, I’m testing it.
Thank you @Miroslava for your cooperation.
-
@2b2bff how you set your sleeping times? I set mine earliest time 8pm and latest Wakeup at 8 am. I never had a nap in this time. Try it with other times.
-
@atoponce said in Software Update 2.43.8/.12 (2025 Q2):
@far-blue I decided to downgrade. I’ve got the Chicago Marathon coming up and I train by power. I don’t want to be second-guessing my power reading or babysitting the watch during my workouts.
Settings > General > About > scroll to bottom > hold bottom button a few seconds > secret menu appears > Select OTA pkg.
I had a few installed, and selected the .8 release.
The bug seems to have persisted despite the downgrade. On my run this morning, the power was dropping to zero every 45s - 1m. Every time I looked at my watch, it was either showing “0” watts or just climbing up from 0.
I don’t think this is a problem with my Stryd foot pods, but I do have my old Stryd wind version I can test, and I can also test my current Stryd Duo pods with my old Suunto 9 Baro to help eliminate variables.
However, because of the very frequent power drops, I decided to upgrade back to .12 so I can at least have the track calibration features when doing track work.
Hopefully we can figure this out, because this sucks and the timing for me could not have been worse.
Suunto Race S / 9 Baro / Ambit 3 Peak / Observer
Polar H10 / Verity Sense / OH1
Stryd Duo / Wind -
@Artus-Diver Hey a swimming guy like me …
Me also I dream to have some improvement for swimmers but in fact very very basic
these ones :
A GIANT big single information to see underwater when I swim with my foggy lenses and my impaired eyes still the distance I swim, then the time it is and then the duration …
If you think this is what you wish also do tell me -
My activities are recorded with swim style “Apnoe” but I swim just freestyle. Anyone else have the same strange swim style detection?
-
@atoponce and I train with power on my bike, just tested today. Avg and normalized power on watch are different than in SA (except NP data from SuuntoPlus app). You can’t pace a climb with this bug
-
@atoponce My thinking is that it might be related to the gps firmware update. If a separate device within the watch such as this has a firmware update I don’t know if a downgrade of the watch firmware would also downgrade this separate device. Same argument if the bluetooth is handled by a separate component of the watch.
-
I think there may also be a bug with the “Interval Workouts” you can program in the mobile app. I have used “Lap button press” under Duration for some steps in my workouts, and this worked well. In the new firmware pressing the lap button does not end an interval - it just records a new lap in the workout.
Is anyone else seeing this?
-
@far-blue I was wondering if it’s a Bluetooth patch that shipped with .12 but is absent in .8.
However, regarding GPS, I don’t use GPS for pacing—I use the Stryd pods. This is why I’m skeptical that it’s a problem with the pods as my pace never drops to zero but remains consistent the whole run. I guess it could be possible that when the pace disappears from the pods, the watch immediately switches to GPS so I don’t notice the drop. I wouldn’t know how to test this though.
I should mention that I use the 30s average for my power data field, so I have to wait a while for the average power to climb back up. I would probably be less annoyed by this bug if I set it to 10s or 3s average. But then I would be annoyed by the more frequent spiking. Double-edge sword. Heh.
