Software Update 2.43.8/.12 (2025 Q2)

isazi

@herlas power drops should be fixed in testing already, thanks everyone for reporting it

herlas

@isazi thanks, do you mean these power drops are more than a visualization issue on the watch and do contribute to lower avg wattage in laps and overall activity when comparing to Stryd app side?

isazi

@herlas I do not know, only heard there is a fix for that in latest testing firmware. Maybe it is just a visual bug

atoponce

@herlas Yes. Just this morning actually. I ran 3×9:15 at near-CP. Due to the frequent 0 drops on my watch, the lap table watch display on my Race S while in the run showed that I averaged 309, 309, and 308 W for those intervals. However, the data recorded in the FIT file shows the actual averages are 316, 316, and 315 W.

atoponce

@isazi If you need a beta tester, let me know.

Antoine

@isazi said in Software Update 2.43.8/.12 (2025 Q2):

@herlas I do not know, only heard there is a fix for that in latest testing firmware. Maybe it is just a visual bug

So a hotfix is coming ?

herlas

@atoponce what about Stryd side, what values ddi you get for those?

sryke

Another data point for issues with Stryd: Race S and Stryd since about the last software update (.12)

Stryd is connected as foot pod
Power field clearly underreports wattage
frequent power drop outs/zeros during a run
power in Stryd’s app looks very different (and in line with how values were before the update)

I did a mountain run yesterday, avg power for the ~40min uphill section: Stryd power 255 W, Race S reported power 214W. Can’t say this is due to the power drops, they don’t occur that often. Race S simply shows/logs a lower wattage throughout. As said before, this started at around the .12 software rollout.

atoponce

@herlas Screenshot from Stryd’s PowerCenter. 316, 316, 315 W.

atoponce

@herlas Also, I’ve tested my Stryd Duo with my old Suunto 9 Baro to eliminate variables and did not have any power drops on the display. The power reading on the watched remained 100% reliable during the run.

I haven’t yet tested my old Stryd wind foot pod with my Race S, again to eliminate variables, but knowing that there is a fix in beta, I don’t think I’ll bother. It seems like Suunto has identified the issue. Hopefully it comes out as a hotfix rather than the next quarterly update.

guy.s

I’m getting a problem with wayponts. Instead of showing up with the waypont name the watch is just displaying “Waypoint”. Changing the type of the waypont results in the watch showing the changed type as he waypont name , like “Parking”. The name is ok in the app, but the watch doesn’t show it.

Has anyone else seen this?

I don’t know whether it’s an app or watch problem.
Race 2.43.12, android app 5.3.7

Guy

babychai

@guy.s Yeah, i got this problem too on my SV.

Fenr1r

@guy.s Yup: noted here.

Hard to get custom names to “stick”. Entered, saved, synced … checked … repeated. Works worse with imported routes but still get reversions to default type names on SA-created routes. Usually midway through a multi-hour activity.

If there’s a guaranteed-success process/ritual known to Suunto, sharing would be appreciated.