@atoponce Yeah, I wasn’t sure if CPS allowed for a speed criteria, and didn’t want to re-read the spec so I just linked it for you. CPS is often used with another protocol CSCS (Cycling Speed and Cadence Sensor), which obviously does report speed. When you finish an indoor cycling session, you can “edit the distance” for an indoor cycling ride. I never bother to do this, but if you use it to match what you’re seeing in an app, then you might get something you’d like, assuming it takes the “distance” and works out a speed graph over the session duration. Out of curiosity, what do you expect to learn from “speed” you can’t learn with power data? I don’t know of a “FTS” Functional Threshold Speed aspect like there is FTP to make power zones. Do you think you’d use it as an alternative way to determine TSS?

@2b2bff No question about it! I’ve also been programming since early 1990s and do that for living.

@reijervanrijsbergen I’m having the exact same issue. It’s further complicated by GNSS jamming. I’ve noticed that once the heart rate signal is lost, it doesn’t always recover, even when the watch is worn directly on my wrist rather than over a jacket. Coros HRM + Suunto Race S.

Also bit he bullet and did a factory reset. All works fine now, but it was a pain. Realized how much I customized the settings… let’s hope it’ll keep working stable now.

@frullewulle thank you Anybody else has used the latest SW 2.50.26 and not have issues with the laps being incorrect?

One year later this issue still exists. I did a 50K trail race today that consisted of 3 laps. The arrows were absolutely invisible behind several tracks from multiple laps. There were at least a couple of tricky 4 way trail junctions on the race course where the arrows would be helpful, if they were visible. I didn’t have time to take a picture of my watch because I was racing but here are fragments from the recorded activity: [image: 1771720463549-screenshot-2026-02-21-at-4.33.38-pm.png] [image: 1771720472616-screenshot-2026-02-21-at-4.34.05-pm.png] Please give this simple fix a priority!

@LUIS-RAZORMAX 70% after restart is normal. It is the baseline the Watch assumes until it gets different data. I found that it seems to matter how I wear my watch. If I wear it too tight, it won’t register any changes. Maybe because of the watch is held in a different spot? If I wear it more loose it works better and actually declines.

@geoffrey-reymond Bonjour, est ce que c’est arrivé juste après la mise à jour, que la batterie a diminué ? Jack

@2b2bff You’re right, it was enabled without me ever intentionally doing so… I’ll try. Thank you for now.

@mayakwyllie I can see it in the App - iOS…

@Egika already off the s+ for tunning exonomy, yeah the problem solved. So running 2coniny s+ really lap itself at 15:00 mins. Thanks guys

@Brad_Olwin Yup, you’re lucky. My point is just that if anyone hasn’t invested in Suunto yet, they should look at my experience as a warning. You’re better off looking for another brand.

I have a similar issue, looks like my watch lags behind 1 day with showing sleep data. It looks all good on the watch.

@flyinono this is a known regression in 2.50.26, it was reported and ack’ed by Suunto, you’re not alone, OHR stopping during the night which leads to no sleep and hrv data is a known issue.