Suunto 2.50.26 – Q4 2025 Release Notes

elis001

Serious bug not being able to see manual laps in the app from activities after the last update. Still able to see them in my race s after the sessions but not in the app. Hope they solve this quick since it’s a very important function.

mich heller

@elis001 it’s a bug in Suunto App. it’s fixed in version 3.7.1 (at least on iOS)

hatori_hanzo

Sorry for this question, maybe it was already addressed. If I am understanding this correctly, ZoneSense is now turned on by default in every sport mode and it gathers data as before. But you can only see that data in app after the activity is done and saved. And it does that even if it’s not turned on in SuuntoPlus section.
But if you turn ZoneSense on in SuuntoPlus, you can view data live on separate screen, and data is also gathered. And it’s basically the same as before the latest q4 update.
So that means that if you do not turn ZoneSense on, it still gathers data that you can view after your activity, but you get two Suunto Plus slots. And the trade-off is that you can’t view ZoneSense data live during activity.
I hope this makes sense

Squirrel

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

And the trade-off is that you can’t view ZoneSense data live during activity

You can if you choose Exercise options > Intensity zones > ZoneSense

Sportsfreund

@Squirrel but this is not the same like afterwards in the app.

Squirrel

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

but this is not the same like afterwards in the ap

Neither is ZoneSense S+ app, but nobody suggested that in the first place.

Freezer

@hatori_hanzo - you can also (besides the Intensity zones ring) natively view the ZoneSense data in three time fields: ZS Aerobic/an-aerobic/vo2max that you can add to a custom sport profile.

Zdeněk Hruška

Is external sensor connectivity working properly for everyone?

I’m having an issue with Stryd 5.0. For some reason, after a while the sensor pairing breaks. The sensor shows as connected and everything looks fine, but data like power and pace are taken from the watch, not from the sensor.

After re-pairing, power is taken from the sensor again (at least based on my testing), but PACE is still taken from the watch, even though pace and cadence are enabled for the sensor. Why is that?

Another issue: the auto-calibration button is only visible during the pairing process. If I later go to paired devices, I can see battery status etc., but there is no option to adjust auto-calibration. I don’t necessarily need it, but I assume this is not intended behavior.

Could you please fix the sensor handling so that the values marked as coming from the sensor are actually taken from the sensor and not from the watch? Right now it’s really messy.

Thank you.

hatori_hanzo

@Freezer I haven’t thought about that, great idea, thanks
Thanks everyone, it makes more sense now.

Dimitrios Kanellopoulos

@Zdeněk-Hruška yes have reports of stryd 5 . Working onthis

DrSilverthorn

@Zdeněk-Hruška There is similar behavior withy verity sense - the sensor shows as being connected, but there is no heart rate data.

thanasis

@Dimitrios-Kanellopoulos coming back to the battery drain issue.
This is the second full charge cycle I am running (so not yet a full 2 cycle calibration) .

It seems the drain is there in my case - although I shall wait for the second cycle iteration. Unless I have faulty device (which is something I need to assess btw), I get 5% drain on activity without GPS (Indoor Tennis for instance) with a HR belt connected and like 5% on a 1hour run with GPS and HR Belt . This is exceptionally high compared to where it was like 6 months ago (with previous firmwares) . Resetting the device after the activity seems to stabilize the drain percentage to another 5% for the rest of the day if worn on the wrist.

I will continue reporting on that

Dimitrios Kanellopoulos

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

although I shall wait for the second cycle iteration

why would you need to wait ?

Its I think very difficult to conduct the test you are doing with so close buckets. Meaning is its 5.2% to 4,4% ? etc.

Also I see you are trying to test battery life with so small activites that eventually have the overhead of ie connecting to sensors etc.

Not really sure why you have to bother so much to be honest and without being disrespectful but I have the strong feeling that:

Either your v1 is getting old ?
Either we are all ghosted by battery life issues.

I could say easily: Continue the tests , but on a personal note, I ll say just let it rest man and enjoy your trainings.

NOTE: we did have a battery “kinda” drain but that was on time mode it was minor and it was on first connect of the sensor. This is how the whole story began I think, or am I wrong?

Also if there is a really battery life issue we will kinda find out sooner or later.

thanasis

@Dimitrios-Kanellopoulos thanks . Indeed . I need to forget about it