Suunto 2.50.26 – Q4 2025 Release Notes

[brechtvb]

@Bartek-W said in Suunto 2.50.26 – Q4 2025 Release Notes:

I was very impressed with the scope of this FW update, but less so when I discovered nothing much changed in a way my external HR sensors are handled

I have exactly the same feeling. Suunto ingores the gold in sports with external sensors. The sensors do the hard part (sensing biological or physical parameters) and make the information available digitally. It should be a no-brainer to put your effort in reading digital signals, that is the easy part in this.

E.g.: Suunto now improved the OHR, because it was bad, and it’s not easy.

But ignoring the open door of reading external sensors properly is plainly stupid.

[MarkusG]

@sky-runner Today I did a 7k comparison run (flat snowy forest) between my Race 1 and my Fenix 7X. After having read that much about distance issues I just wanted to check it

Well both watches auto-lapped within the same second. At the end both reported 7.33km. Of course this proves nothing, it could also be a one time fluke on my side now.
“Elevation” was 12m on the Fenix, 8m on the Race 1 (flat like I said )

[enriqueescoms]

On my wife’s Race S, everything related to synchronized workouts from TP is proving to be a problem. I’m going to have to downgrade it this afternoon. 🫤

[jjpaz]

@MarkusG My Race 2 is always showing 1%-2% less distance (and rythm, pace, power, ngp) in comparison to Vertical or the GPX files. That’s a bit weird in terms of accuracy.

[MarkusG]

@jjpaz Yes, but that was not the point in the post I answered to. There was the question if this new behavior also affects older models like the Race 1. In fact that issue that you and many other currently report holds me back from ordering an Vertical 2 (and the fact that the BLE issues haven’t been fixed as it seems).

[Stavrogin]

@MarkusG I am only saying this because I had massive issues with my Garmin Fenix 7x. There is a major issue with the altimeter and it can read wild numbers. Mine would jump wildly. Not saying that is the issue, but it is a known issue with gen 7 Fenix/epix devices. That is why the new ones have the ugly guard on the side of them.

TBH that is one of the reasons I was motivated to try Suunto back then

Red is the Fenix 7x
Green is Stryd Pod on the Fenix
Blue is a Coros Vertix

.

[Sportsfreund]

@jussim said in Suunto 2.50.26 – Q4 2025 Release Notes:

@Sportsfreund Ah, good then, I thought so too but for some reason I was having trouble activating it. I admit that I didn’t look into it thoroughly after failing with it.

I would like to have vo2max for rowing.

[Theo Lakerveld]

I’ve been testing the new algorithm for the optical HR sensor (SR1) a bit more. It feels subjectively more akin with my perceived exertion, also during two – 10 deg C runs and a XC ski activity. No more strange dips and spikes from the hr sensor. Testing together with my Polar OH1 during indoor cycling, it’s continuously within one beat from the belt.
So for now, I’m impressed and very happy with the improvement! Well done Suunto team!

[ChrisA]

@nicovoim ah… didn‘t think of this, thanks. Will see if it changes after two weeks

[atoponce]

It appears that this firmware release is still not sourcing pace and distance from the Stryd foot pod when paired when GPS is locked. It does use the pod however when doing treadmill runs.

[sustah]

said in Suunto 2.50.26 – Q4 2025 Release Notes:

@sustah sleep/HRV is not a watch but an iOS Suunto App problem, see this thread/post for a workaround.

https://forum.suunto.com/post/182982

I can confirm that this workaround solved my problem with sleep/hrv for only one night of sleep. Today in the morning once again my watch does not show any sleep/HRV data. In the app data is ok. After restarting the watch previous nights were shifted again.

Also my recovery seems to be trapped into 35-38% range since latest update. It jumped to 90% after 1:20 of indoor cycling yesterday (no idea why ), but then I did 10 minutes of strength workout and it dropped back to 36%. In the morning its even lower now on 35%.

[enriqueescoms]

Well, early this morning, the Race S updated itself (despite having automatic updates disabled).

So far, there’s a minor issue: one of the eight custom sport modes is missing (specifically MTB).

[HonzaS]

Thanks for big update!
I would appreciate better notifications from the phone. Right now, it’s only a preview. The option to display the full message would be good. Also, it could handle pictures too. But I understand — Suunto are sports testers not lifestyle watch.

[Marcus001]

Great update. Thanks.
Regarding turn-by-turn navigation, is it possible to use the turning points as waypoints so that you can also see when the next turn is coming up in the data field?

[Egika]

@atoponce said in Suunto 2.50.26 – Q4 2025 Release Notes:

It appears that this firmware release is still not sourcing pace and distance from the Stryd foot pod when paired when GPS is locked. It does use the pod however when doing treadmill runs.

I would have thought that this is exactly how it is and how it should be designed. Is there an indication that makes you think otherwise?

[Dimitrios Kanellopoulos]

@sky-runner that is strange. Can you please try to keep those in a separate post? So I can source them to the team.

I am suspecting the the previous try could have fluctuations

[jjpaz]

@Dimitrios-Kanellopoulos I opened a dedicated thread about thedistance discrepance topic: http://forum.suunto.com/topic/14375/race-2-gps-and-distance-accuracy-vs-previous-suunto-models/18?_=1768210465664

My Race2 is showing 1%-3% less distance than Vertical and RaceS in all activities.

Yesterday I did a crazy test: I recorded activities on a car ride with the Race2 and the Vertical 1 (I started a ‘Cycling’ activity). 25km out and 25km back. The difference between the two was no more than 100m, and around 100m with the Amazfit Zepp app on my phone.

However, when walking or running, the differences jump to 100-200m over 10km, even though the GPX files show similar positions and distances. Are there differences in the algorithms used to calculate distance and pace between the watches?

[Ars Vitae]

@sky-runner Ad. [1] - I reported to Suunto the same issue. As a exemple: On a well-known trail, over a distance of 16 km, I noticed a difference of more than 400 m between the predicted elevation and that recorded by the SV. (900m against 1360) However, this problem is not caused by the current update, but by previous ones.

[BRogers80]

@nicovoim
My ressources begin to work again. It seems a little bit different but after the update 5 days ago it is better now.

[sustah]

Ok, looks like my phone app updated from 3.7.0 -> 3.7.1 and it reset my sleep time to be 00:00 - 00:00 again. So I did workaround one more time and it looks like sleep/hrv is ok again… but doing this after every app update is not really optimal.