Software Update 2.43.8/.12 (2025 Q2)

Max maxilifeguard

@gerasimos thanks, i ready did that, does not work. I ready sent it to the repair center

atoponce

I decided this morning to run with the Stryd SuuntoPlus app to see if the experience would be any better. Which got me thinking. I have a data field for power. If I’m using the Stryd SuuntoPlus app, is the power in that data field coming from Stryd, or is it Suunto’s running power?

What about pace and distance? When I pair the Stryd pods to my watch as foot pods, they’re the source of pace and distance, but if I use the Stryd SuuntoPlus app instead, are pace and distance coming from GPS instead?

sryke

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

Thanks to advise given here in the thread I was able to reinstall the previous firmware on my Race S.

All runs so far show the same wattage in the Race S fit file and the Stryd pod fit file.

However, the watch still shows these drop outs starting at about 10min into a run.

This is frustrating, I thought moving back to the previous firmware would have fixed my inconsistencies. Most runs were o.k. (with the exception of drop outs), here’s yesterday:

However, today I got disagreement between Race S reported wattage and Stryd wattage. Makes me wonder how many other runs were incorrect.

I’m considering to get a different watch now, this is annoying.

Ars Vitae

@Egika, @Pavlas isn’t alone with this experience. I can agree the similar SV behaviour in my case. Despite the risk of losing GPS signal from time to time, because the watch is regularly underwater (freestyle, crawl - to be specific) location accuracy in open water swimming about a year ago was correct. Something has changed for the worse, there are more people reporting this problem: https://forum.suunto.com/topic/13279/open-water-gps-drifting/15?_=1752690357701

atoponce

@sryke Are you comparing the power data in the Suunto FIT with the power data in the Stryd JSON pulled directly from the foot pod?

herlas

@atoponce correct, using Stryd via S+ is a separate Bluetooth connection, I’ve said it before many times, Stryd through S+ app creates more issues than it solves.

When Stryd is connected via S+ these conditions apply :

*Power from STRYD is displayed only on the S+ screen
*Power on regular screens comes from watch itself
*This breaks Stryd offline merge, Stryd didn’t create this S+ app it was Suunto, so Stryd hasn’t done any additional processing on their side to make offline sync work when workout is made with Stryd s+ app
*No pace, distance or cadence will come from STRYD,.
*Once S+ is connected, Stryd won’t be available as neither power meter or foot pod
*It creates fitfile with 2 power sources Suunto’s and Stryd’s

Bottom line, stay away from Stryd S+

Known workaround while Suunto fixes power drops and issues with power averages on manual laps is to go back to firmware 2.40.

sryke

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

@sryke Are you comparing the power data in the Suunto FIT with the power data in the Stryd JSON pulled directly from the foot pod?

Suunto FIT pulled from the app vs Stryd FIT pulled from the pod via Stryd powercenter.

I wonder if for some reason Race S records its own wrist based wattage instead of Stryd power. However, why just sometimes.

Likarnik

On my morning walk I got message for low battery, 5%. Now I checked and my battery is at 10%. Same thing happened a month ago when cycling, I got message for low battery but when I paused and checked battery level it was higher than it stated on message. Anyone else experienced similar behaviour?

runsgrun

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

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

@sryke Are you comparing the power data in the Suunto FIT with the power data in the Stryd JSON pulled directly from the foot pod?

Suunto FIT pulled from the app vs Stryd FIT pulled from the pod via Stryd powercenter.

I wonder if for some reason Race S records its own wrist based wattage instead of Stryd power. However, why just sometimes.

I suspect that as well, especially when the power readings dropped to zero many several occasions when I raised up my arm which my Race S was on.

I too contemplated reverting to the older firmware, but will just live with it for now, hoping the next update will fix the issue (soon).

runsgrun

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

On my morning walk I got message for low battery, 5%. Now I checked and my battery is at 10%. Same thing happened a month ago when cycling, I got message for low battery but when I paused and checked battery level it was higher than it stated on message. Anyone else experienced similar behaviour?

Not exactly what you encountered but this reminded me of my old Suunto Peak 9. After more than 2 years of use, the watch went dead at about 20% and gradually over weeks of charge cycles, it died at 50%. However, I didn’t feel like the overall battery life was significantly shorter. It just took twice as long to reach 50% from 100%. Seemed like the calibration went nuts. It was ok after I sent it in for servicing, I couldn’t recall the battery was replaced.

Theo Lakerveld

I’ve just reverted to FW 2.40.44 from 2.43.12.

Reasons:

Sleep tracking is underestimating
GPS drifting during OW swimming

The previous FW was performing better, according to my experience.

sryke

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

Known workaround while Suunto fixes power drops and issues with power averages on manual laps is to go back to firmware 2.40.

I’ve just gone back to firmware 2.40.44 on my Race S, still getting power drops.

atoponce

@herlas

correct, using Stryd via S+ is a separate Bluetooth connection

That’s what I noticed. I was just curious if the S+ app would be “sharing” its data to the watch, but it appears it’s all self-contained in its own walled garden.

I’ve said it before many times, Stryd through S+ app creates more issues than it solves.

I need to frequent the forums more. Heh.

Power from STRYD is displayed only on the S+ screen

Power on regular screens comes from watch itself

No pace, distance or cadence will come from STRYD.

Once S+ is connected, Stryd won’t be available as neither power meter or foot pod

It creates fit file with 2 power sources Suunto’s and Stryd’s

Perfect. Thanks!

This breaks Stryd offline merge, Stryd didn’t create this S+ app it was Suunto, so Stryd hasn’t done any additional processing on their side to make offline sync work when workout is made with Stryd s+ app

Yup. I sent in a support request to Stryd about merging the two runs in PowerCenter and Angus said it’s not possible and advised me to not use the S+ Stryd app.

Which surprised me, as I thought Stryd did the development. But you mentioned that Suunto did, so it’s even more curious that they didn’t develop the app to use the existing paired connection with the foot pods or share the data out of the S+ app to the watch. Shrug.

Bottom line, stay away from Stryd S+

Angus advise the same. Haha.

Known workaround while Suunto fixes power drops and issues with power averages on manual laps is to go back to firmware 2.40.

I’ll look into this. I’ve already downgraded to .8 and noticed the power drops remain, so I’m skeptical this is a fix. I suspect that the .12 firmware changed something that downgrading isn’t reverting. I’ll give it a go for tomorrow’s easy run and see how it goes.

Thanks for the confirmation and reply!

atoponce

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

Suunto FIT pulled from the app vs Stryd FIT pulled from the pod via Stryd powercenter.

If Suunto is syncing the data to Stryd, then I would expect them to be the same. IE, Stryd shouldn’t be manipulating the data Suunto syncs.

With that said, I don’t know how the offline sync interacts with the existing data. Does the data on the foot pod(s) overwrite the existing power data Suunto already synced over?

I wonder if for some reason Race S records its own wrist based wattage instead of Stryd power. However, why just sometimes.

I don’t think that’s the case if the pod(s) are connected to the watch via Bluetooth. The power data written to the storage on the watch should be coming from the pod(s), not the watch.

atoponce

@sryke This

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

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

Known workaround while Suunto fixes power drops and issues with power averages on manual laps is to go back to firmware 2.40.

I’ve just gone back to firmware 2.40.44 on my Race S, still getting power drops.

This is what I suspected. I’m going to give it a go for my next run and see how it behaves.

deltof

@Dareo, I have the same problèm ! Every night, my watch switch Power off! Have you a tips ?

SuperFlo75

@Likarnik I recognized this behavior, too… never saw that before

atoponce

@sryke I just plotted the power for my runs for M-F, including the Tue/Thu doubles. I’m grabbing the Suunto power data from the FIT file downloaded via the Suunto app. I’m grabbing the Stryd data from the JSON file on my Android phone using adb pull after doing an offline sync. That way, I’m getting the unadulterated Suunto and Stryd power data without any shenanigans in PowerCenter.

They all agree except Wednesday and Thursday AM. Wednesday disagrees, because I paired my Stryd pods with the Stryd S+ app, which means the power recorded to the watch was Suunto’s built-in running power, not Stryd’s.

Thursday AM disagrees in the 4th interval because I paused my watch at an intersection. As such, Stryd’s power data is shifted to the right of Suunto’s as Stryd ignores pauses. However, you can still see that the data would align.

Friday morning before my run, I downgraded the firmware on my Race S to 2.40.44 to test if the display would still drop power. It didn’t thankfully, so I think I’ll stick with this going forward.

atoponce

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

I’ve just gone back to firmware 2.40.44 on my Race S, still getting power drops.

I just ran with 2.40.44 and didn’t see any power drops on the display. I was getting it with 2.43.8 however. But 2.40.44 worked for me.