Software Update 2.44.46 (2025 Q3)

animalart

Hi !
On my end, I also have a bug regarding sleep. Even if I tighten my watch at the maximum so it does not move, I haven’t get a full night of sleep registered by the watch since the update. The first day it stopped in the middle of the night and since I didn’t get any night registered. It looks like the HR monitoring stops as the curves on the watch and on the app are stopped during the night. I had to move my watch on my wrist (and see the green light) to make the HR back again.

timecode

Yesterday I had an issue with connecting HR straps to the watch. I have paired 2 straps after the upgrade, one is a Wahoo chest strap and one Coros HRM. I went on an activity, a notification showed that the Coros HRM is connected, but on the watch I saw that it’s measuring from my wrist, not from the HRM. Tried multiple times, same result. I was then using just OHR. When I got home I tried to re-pair both straps and it was difficult - it took multiple attempts to get it done. Not sure if it’s just a “onetime issue”, but I’ll keep an eye on it.

Grundy82

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

@herlas understand that, and makes sense to only allow the stryd to be paired as a footpod, however on the previous software, when connecting the styrd as a footpod (as is still the case on the new software per your note), there is no longer the option to configure the auto calibration options on / off. I’m not sure why this has been removed as it allows the user to control whether the watch will use the stryd for pace & distance (auto calibration = off) or allow the watch to fuse GPS and styrd’s data for pace & distance (auto calibration = on). Any ideas why that has been removed and equally whether we can expect it to return?

@herlas any comment / update you can provide on the above please?

Peter Tönz

Since the Update to 2.44.46, the internal heartrate sensor is also broken. Without any activity, the heartrate value jumps between 255, 129 and 40 every seconds.

runomatic

@timecode Same issue here with my Coros HRM. I just thought they’ve changed the heartrate-icon, but after the run, the higher heartrate indicated, that the watch used HRM.

VoiGAS

For me Heartrate works over wrist and HR belt as well. Race S with Suunto Smart Sensor

timecode

@runomatic hm, I just tested the behaviour. The Coros HRM connects to the watch (there is the popup notification on the watch), icon shows OHR and Coros HRM is not connected at all - HR is coming from my wrist. I cycled through multiple activities (Trail running, Hiking, Open water swimming) just to see what happens and suddenly it connected. Then tried Running and again it didn’t connect twice, third time yes. So there is something off, until now it worked flawlessly.

runomatic

@timecode Ok, thanks. I’ll check this later.

EDIT/UPDATE: No more problems.

Peter Tönz

@Peter-Tönz After reading some others issues: I forced a reboot (long press upper right button) and the internal HR-value seems to work again!

atoponce

@sryke Can you explain the chart more? What’s the difference between the orange and blue-green lines? Is one Suunto power and the other Stryd? Or both Stryd, but different foot pods? Something else?

Jan Suchánek

I feel like my Suunto Race battery is draining faster after the update. Not drastically, but maybe twenty percent faster.

Cghinrg

@Jan-Suchánek i’ve noticed the same on myvertical. Have a lot of bugs too. This stupid update is ruining my watch. Where is a way to downgrade to the previous software?

Squirrel

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

@sryke Can you explain the chart more? What’s the difference between the orange and blue-green lines? Is one Suunto power and the other Stryd? Or both Stryd, but different foot pods? Something else?

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

Stryd fit file wattage (red) vs the Race S recorded fit file wattage.

The Lost Alien

@Jan-Suchánek Yes, I confirm that I recharged my Suunto Race yesterday, and it has now reached 88% in less than 24 hours. This didn’t happen before the latest update.

atoponce

@sryke @Squirrel Follow-up questions:

How are you getting the Suunto power data? From the FIT file out of the mobile app?
How are you getting the Stryd power data? From PowerCenter? If so, where is PowerCenter getting the data? Pushed from Suunto or manual sync from the Stryd foot pod?
What is your process for generating those charts? Looks like you’re using CanvasJS. I too am a JS developer and can attempt replicating your results with my own data if I know your process.

Alpha 156.42

In the Android app, the Aerobic, Anaerobic, and VO2max tags/status are displayed incorrectly.

SODIUM

@Alpha-156.42 The training plan might produce errors if the tags are inaccurate

The_77

@Alpha-156.42 these only work if your HR, pace & Power Zones are accurate in the watch - may be worth checking since apparently Pace Zones might be reset after the update?

Alpha 156.42

@The_77 Thank you so much! Your message really helped me. I chose TSS as ZoneSense, and that solved the issue.

sryke

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

@sryke @Squirrel Follow-up questions:

How are you getting the Suunto power data? From the FIT file out of the mobile app?

How are you getting the Stryd power data? From PowerCenter? If so, where is PowerCenter getting the data? Pushed from Suunto or manual sync from the Stryd foot pod?

What is your process for generating those charts? Looks like you’re using CanvasJS. I too am a JS developer and can attempt replicating your results with my own data if I know your process.

#1
Yes, mobile app. Or if you sync to intervals.icu you can get it there, too.
#2
Yes, Stryd PowerCenter.
Manual sync from pod.
#3
https://karaul.github.io/fitplotter/

Yesterday I unpaired and paired again the pod before my run. Race S logged and showed Stryd power data.

However, Race S would not end the run on the pod, e.g. the Stryd pod kept on logging. I only noticed 3 hours later when I wanted to sync the pod and couldn’t connect the Stryd app with the pod. I checked my watch (basically just checked the status of the pod) which closed the connection and made the pod visible again. First time I’ve seen this happening.