Software Update 2.44.46 (2025 Q3)

timecode

@Brad_Olwin @Dušan-Ković I also have a weird issue with multiple sensors. I tried to connect one Coros HRM and one Wahoo Tickr (both full battery). When both are paired to the watch, and both on me, connected, the watch is still pulling HR from my wrist. When I go to the settings section where I can choose which sensor should be connected, and choose either one of the sensors, I get an error - couldn’t connect to the sensor. The connection only works after a very long fiddling around, or if I unpair one of the sensors. If only one is paired, then I have no issues. If both are paired, it’s very unstable and it doesn’t work properly. Then again if I want to pair the one which I previously unpaired it often ends up in an error - couldn’t pair. Something isn’t right.

Dušan Ković

@Brad_Olwin I know that, but you obviously didn’t watched my video properly.

first I have Polar H10 and it connects because I used it yesterday (last sensor used). I also go to to Exercise options > Sensor data just to show what is connected
I go back to main exercise screen and it doesn’t connect, not sure why, although exercise options show that it was connected. HR belt just blinks gray and it doesn’t show HR
I go back to exercise selection and start Trail Run again and it connects. We have HR displayed
I take off Polar H10, it is not powered while it is off the belt. And I show the sensor and sensor ID. In watch connections we see sensors with sensor IDs.
I turn on Verity Sense (VS), start trail run again, watch shows Polar H… 02674E3E connection which is H10, not VS, although H10 has been turned off. And we can see blinking heart symbol, without belt across it. Meaning watch is looking for wrist HR from watch sensor.
Again I go to Ex.Options, where we can see none of the sensors is connected, both are grayed out. When sensor is connected we have green Icon.
I tap on the Polar 910AA42E (Verity Sense) and connect it manually
when we go back to the exercise start screen we have green heart icon with belt, meaning Verity sense is connected, and it has some random HR value because it doesn’t read anything

That thing happens every time I switch sensors, I have to connect them manually

timecode

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

@Brad_Olwin @Dušan-Ković I also have a weird issue with multiple sensors. I tried to connect one Coros HRM and one Wahoo Tickr (both full battery). When both are paired to the watch, and both on me, connected, the watch is still pulling HR from my wrist. When I go to the settings section where I can choose which sensor should be connected, and choose either one of the sensors, I get an error - couldn’t connect to the sensor. The connection only works after a very long fiddling around, or if I unpair one of the sensors. If only one is paired, then I have no issues. If both are paired, it’s very unstable and it doesn’t work properly. Then again if I want to pair the one which I previously unpaired it often ends up in an error - couldn’t pair. Something isn’t right.

An another thing which I have noticed just now: I put both sensors away, then after 10 minutes I went (out of curiosity) to Settings, Connectivity, checked both sensors on my watch, they both showed 56%. 56% is the percentage of Coros HRM, but also Tickr showed 56% - but this one was not even connected. It’s a chest strap lying in my drawer. When I did put it back on my chest, it showed 100% battery. Again, something isn’t right.

Steffen1922

Hi, recently I bought a Race S and have since the update the issue that the watch can’t pair with my Wahoo Speedplay Powrlink Pedals. After the watch has found the pedals it is asking for the crank length. If I chose the right length it shows almost 1 min the saving process screen, but after that the setting isn’t saved. If I go into the cycling activity the watch is not pairing with the pedals. The Powermeter isn’t even listed in the connected sensor list. Anyone else here with the same problem?

I came from an Garmin Forerunner 745 and have to say, that I’m really disappointed with the userbility of the Race S for cyclists. Running functions are fine so far, but cycling support including indoor trainers needs a huge improvement.

Brad_Olwin

@Dušan-Ković If you put one sensor on so it is reading HR then select an exercise it connects as shown in your video. Start an exercise, short walk, etc. Then stop exercise and discard or save.

Put on the other sensor and select an exercise it should automatically connect. Start the exercise and record then stop and discard or save.

This should work. Be away form the unconnected sensor when you start the exercise.
You do not need to go to sensor data as you will see the icon for an external sensor connected

Dušan Ković

@Brad_Olwin That is exactly the problem that I am telling you, second exercise with different sensor won’t automatically connect. I already tried that. Even on different days. I have no idea why it is so hard for you to accept that something is maybe not working correctly. I am literally explaining the problems

borgelkranz

@Dušan-Ković since I own a Verity Sense, an H10, and a Smart Sensor as well, I did a quick test and can confirm what you describe.

Prior to this test I was only using different sensors in different activities and did not observe this. Usually I use H10 in the gym and on the rowing erg due to GymLink and dual BLE connection. The smart sensor for biking and running. Here the switching seems to work.

Another observation: in connected devices I have a nameless sensor that I cannot disconnect. Strange…

borgelkranz

My favorite watch face works again! Simplicity Analog finally has it’s accent color back. I am very happy!

duffman19

@Brad_Olwin We all agree this is how it should work, but you have several people here telling you it just doesn’t, at least not all the time.

I also just tested this. Started and completed an activity with the Verity Sense. It did connect correctly and instantly this time. Turned off the Verity Sense, put it away. Waited about 30 minutes. Put on the Suunto Smart Sensor, started a new activity, and… nothing. Only wrist-based OHR. I was able to go into the activity sensor menu and connect the Smart Sensor there, but it was not automatic.

This is the issue. Sensors do not always connect automatically from one activity to the next. Too often you need to dig into the menu to force a connection. Maybe the issue only occurs when recording the same activity type with different sensors as @borgelkranz suggested.

Brad_Olwin

@Dušan-Ković Got it and @duffman19 understand. I wonder if this is an issue with optical vs belt? I will ask about this. As I said using 3 different belts for months testing I never experienced this nor do I recall other testers having this problem. Might be worth forgetting both sensors then soft reboot and repair the sensors and see if this is still occurring. But I will get back to you. Wanted to make sure this was the issue as @Dušan-Ković video wasn’t entirely clear to me. Thanks!

Mads Hintz-Madsen

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

Another observation: in connected devices I have a nameless sensor that I cannot disconnect. Strange…

After pairing my 2nd cycling power meter to the Race, my Polar H10 HRM turned into a “nameless sensor” and my H10 could no longer connect.

And since the H10 configuration in the watch somehow got corrupted I could not delete the corrupted pairing from my watch. Also I couldn’t re-pair the H10 as the watch seemed to think that I have it paired already.

In order to be able to use my H10 HRM again, I had to factory reset the Race and setup the watch from scratch (and now wait for the watch to re-learn my HRV range).

So the multiple sensor support needs some more love (i.e. testing and bug fixing), Suunto!

borgelkranz

@Mads-Hintz-Madsen ok, that makes sense. My “unnamed sensor” probably is my stryd that suddenly disappeared from the connected devices. However I could pair it again, though the unnamed sensor remains.

frullewulle

Doess anybody has some sleep detection errors since the update?
I Have several nights where it misses 2 or 3 hours of sleep

Tieutieu

@frullewulle sleep tracking is still very good after update both for me (SRs) and my wife (beta update on S9pp)

orzechszek

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

@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

Base on your suggestion I’ve changed to TSS(hr), but It seems it still base my trainings on pace, because it assign as Vo2Max. It is not a bug?

Tieutieu

@orzechszek I had the same this morning : 1 hour trail running in Z1 but classified as Vo2max. I reported that through Sa beta program.
My 2 hours road cycling yesterday also in Z1 was properly classified as long aerobic.
Both with my SV and HR strap

Shrek3k

Very similar for me, running classification is currently very … creative, independently to the kind of TSS-zones I have chosen (TSS (hr) once again).
Biking is more relatable and related to the heart rate zones.

kriskus

And same here. No matter how I run, all this week’s runs were classified as VO2max. Even today’s very slow recovery run in Z1/Z2 (blue/green). I have the zones configured properly and use Polar H10 with a new battery. Even zone sense which normally works so-so for me showed 0 seconds in the VO2max zone.
I tried switching between rTSS and hrTSS, but it did not help.

matram

@kriskus for me setting the pace zones correctly fixed the problem. Although I use HR based zones it seems pace is now factored in.

orzechszek

It seems TSS is still forced for classification. I have advanced zones disabled for running and cycling but it still uses it.
In my opinion, there is so many data, so if somebody has default configuration for all sports based on HR and specific TSS is set as default (for example TSS(hr)), then pace zones should be simulated for that training base on HR. Similar behavior when TSS is used.