Software Update 2.43.8/.12 (2025 Q2)
-
@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.
-
@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.
-
@Dareo, I have the same problèm ! Every night, my watch switch Power off! Have you a tips ?
-
@Likarnik I recognized this behavior, too… never saw that before
-
@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 pullafter 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.
-
@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.
Suunto Race S / 9 Baro / Ambit 3 Peak / Observer
Polar H10 / Verity Sense / OH1
Stryd Duo / Wind -
@atoponce Thank you for sharing these details. Your findings aligned with mine. Raw data is not the problem which is a relief. What was changed in the latest firmware I guess is the way Suunto app and watch interpret the power data. When I use a 3rd party tool to analyse power data from Suunto’s Fit files, the average numbers tallied with Stryd’s and not the Suunto App’s and the watch’s.
-
@deltof Sorry @deltof but I can’t say that I do. I’m still waiting for this supposed “priority” hotfix that tech support told me about in the chat. Since the problems started 17 days ago my watch has frozen or completely shut off 5 times at night while sleeping. So it’s intermittent, not constant. Same with exercising. Sometimes it freezes up on me during a session and sometimes it doesn’t. I have no clue what triggers it. What I have found is that when it freezes up during exercise, it’s futile to do a soft reset because it will freeze up again shortly thereafter.
-
@atoponce said in Software Update 2.43.8/.12 (2025 Q2):
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.
FYI - today, 2.40.44
-
@sryke Wow, all those drops were failures? You didn’t stop during the run? If yes, then power is not usable with this bug.
In my case I see drops on the watch, but not in the app - strange. But I don’t trust the values after having the drops on the watch and reading experiences like yours… -
@sryke hm okay. Todays Run with Suunto RACE with 2.43.12 with no bugs.
-
Most drops are failures, I did compare it to the Stryd fit file data.
And you’re certain that this is really the Stryd pod power stream? Everytime I do not see any drops in the data is when I get an overall different wattage in the Suunto and Stryd files. My assumption is that the Race S sometimes does not read the stream from Stryd but uses its own wrist estimated power. Despite having a connection with the pod.
-
@sryke i dont have a stryd pod. Its suunto Measurement
-
@sryke said in Software Update 2.43.8/.12 (2025 Q2):
Most drops are failures, I did compare it to the Stryd fit file data.
And you’re certain that this is really the Stryd pod power stream? Everytime I do not see any drops in the data is when I get an overall different wattage in the Suunto and Stryd files. My assumption is that the Race S sometimes does not read the stream from Stryd but uses its own wrist estimated power. Despite having a connection with the pod.
@sryke this makes me curious about the comparing the power algorithm between Suunto and Stryd. I might do a test run without connecting both and see how they differ.
