Software Update 2.44.46 (2025 Q3)

Stefan Kersting

Have battery drain too on my SV. Charged sunday evening and have now (wed 10.37 am) 72 % left. Did a workout of 1 hour.

soisan

@Mattg576 You should just correct your power and pace zones. Check the pace and power zones diagrams of your activity in the app and compare them with your heart zones one. I bet they don’t match at all.

helgonet12

Does any one else facing that after the latest firmware the Zone sense do not work any more. On the previous firmware it worked for me everything. I have not change any thing. At the moment I’m using Race 2 but it does not work on vertical either.

brechtvb

@Stefan-Kerstin

Rebooted, charged 100% at 22:00 yesterday

No sport activity, always on (screensaver), hr monitoring on, sleep monitoring on

Currently at 90% after 21 hours

Stavrogin

I wrote a long post in the Race S area but have received zero replies. Usually if someone is having issues that others are not having they will at least say as much. I am going to copy and paste it here to see if I can get any help or suggestions. I made a couple edits to save time. Sorry it is so long.

TL;DR
Experiencing persistent heart rate sensor (HRM) connectivity issues, unreliable climb guidance, and problematic sleep tracking on Race S after recent software updates. Looking for confirmation from other users and troubleshooting advice.

I thought a lot about whether to write this or not. I have loved my Race S and it has done a great job 85% of the time. I am noticing little quirks that my COROS either does not have or cannot have due to the fact it does not have Ciimb Guidance.

Issues with having more than one HRM available to the watch.
Since updating to the new software version my Garmin HRM Pro +. It has been really bad at keeping connected.

If other Bluetooth devices (like a Garmin watch or my phone) are nearby, the Race S connects/disconnects from the HRM erratically, impacting Zone Sense reliability.

During a recent run, the HRM stayed “connected,” but produced a flat, incorrect HR trace for 28 minutes before suddenly recognizing Zone Sense.

The watch will randomly connect to HRMs even when not doing an activity.
Having multiple HRMs on the watch seems to swap mid-activity, causing further instability. Not sure if this is because I am using the HRM Pro +

Turn by Turn Guidance and Climb Guidance Issues:

Today during a hike with 2400 ft of climbing the climb guidance would not show were I was in the picture (it shades blue to show progress). The only way it would work is if I scrolled down to the second climb guidance screen and back. This happened over and over.

Also it announced the first climb, but it never showed up in the guidance. It was red in the graph, but…nothing.

As I approached the second peak I stopped short of the summit of the planned route by about 20-30 feet. There were a ton of people and I did not want to deal with it all so I started to head to the third peak. Because I did not “stay on the route” this cancelled any turn by turn navigation and climb guidance from there on out. It all disappeared.

There was cell signal so I stopped and did a replan of the rest of the route. This worked and the watch started working correctly. Shading in the climbs was also correct now. However about 30 minutes in I could not leave the navigation screen. It got stuck. I had to reload the route again to get it to go back to normal.

Sleep Tracking & Recovery Data

Sleep tracking is crucial for recovery metrics and HRV, but the Race S’s implementation is unreliable:

Initial sleep tracking only worked if worn in a non-standard way (inside right wrist after months of experimentation)

Recent “improvements” appear to have broken this function again, with frequent missed HRV readings.

When use competing platforms (Garmin, COROS, Whoop, Oura) I rarely have sleep tracking failures.

Are other people seeing little bugs like these?

Thoughts?

sky-runner

@Stavrogin I experienced some of these issues. I had issues with the watch refusing to connect to HRM twice even though both times I could go to the paired sensors and see the sensor responding and showing the battery level.

With the elevation profile not showing where you are, I saw that at least once with a previous software version, so I think that likely isn’t new. I think that might also be related to the blue navigation arrow not showing up on the map, which I have also observed several times.

With the issue where you turned around shortly before the peak, can you describe what the route was like. Was it a short out-and-back to the peak but otherwise continuing further on the original route? Even better, can you share the route and show where it lost you? In my experience, Suunto navigation doesn’t handle cases like that well. From my experience, it probably attempted to reverse the route and find you on the reversed path.

Stavrogin

@sky-runner

Is it about reloading a route when this happens during navigation? Didyou doing anything special to get HRM to connect continually

sky-runner

@Stavrogin Once HRM has connected it stays connected. I have never experienced flaky connections. But a few times I experienced HRM refusing to auto-connect in the beginning of an activity - the last time that was this morning. After a while I figured out there is a way to select a HRM in activity start screen options and connect to it manually.

loopylou72

@sky-runner thsnk you for this! I see it but it is really annoying - I do not want to have to select my HRM everytime I do an activiy when it used to just autoconnect.

isazi

@loopylou72 the watch automatically connects to the last sensor you used, exactly as before