Issues with pace/distance - Stryd integration
-
Hi!
I am using the Suunto Race S for several months now and had my first road races with it. During the races I got completely bamboozled by pace and distance, as the watch records more distance and for that shows a much higher pace. Also, when running intervals on a track, the watch records 1.200m instead of 1.000m. Is there any way to re-calibrate the watch?I also tried the Race S with the Stryd, but then, the distance measured is way too short (and with Suunto, I can’t add a manual calibration factor like with the Garmin)
Any tipps are appreciated. Thank you so much!
Another problem: regularly, notifications areu not sent to the watch. I need to restart the watch, so they get through again. Is that a common bug or something?
-
@yoora Came here looking for a solution to a similar question. I recently ran a race that is a short 5K (the actual distance is closer to 4.68 km). However, my watch reported that I ran 5.18 km, a full 0.5 km farther than the actual course length with a significantly faster average pace than I actually held.
When I navigate to Settings -> Connectivity -> Paired Devices -> Stryd X on my watch, it shows “SPEED & CADENCE, POWER”. I’m assuming these are the metrics the watch is sourcing from the pod. Does this mean that distance is coming from GPS?
This was a downtown race, but there is only one “tall” building that is 17 floors, the second tallest is 8 floor, and the rest are 4 floors or shorter. It was a clear sky, and the street is very wide. The watch has very good view of the sky. So I don’t think buildings would cause poor GPS signals.
I ran this race with other friends, and all their watches recorded 4.5-4.7 km. I’m the only outlier with 5.18 km. None of them have Suunto though, but as I understand it, I have multiband GPS, so it should not have been a problem anyway.
So what is sourcing pace and distance? The watch or the pod? Or is pace coming from the pod and distance from the watch?
-
I’ve been in contact with Stryd support on this issue since this 5K race. Every run I have done on my Suunto Race S is not using my Stryd pod for pace and distance.
Here is the data recorded by my Race S and here is the data recorded by Stryd. As you can see, both the pace and distance disagree:
- Suunto:
- Time: 20’31.0
- Pace: 06’20/mile
- Distance: 3.24 mi
- Stryd (only at the race segment):
- Time: 20’31.0 (14:37 - 35:08)
- Pace: 07’12/mile
- Distance: 2.85 mi
Checking in on the runs for Monday, Tuesday, and today, the watch distance and pace differs from Stryd’s distance and pace. I have Stryd Duo, which is two foot pods paired together for right/left balance metrics.
Things I’ve done to troubleshoot:
- Unpair the pods from the mobile app, then pair them again paying attention to which pod is paired first.
- Unpair the pod from my watch and pair again, confirming it uses the first pod that paired with the mobile app.
- Do a hard reset, restoring the watch to factory settings, updating to the latest firmware, and pairing the first pod again.
With the help of Stryd support, we are convinced that Suunto is ignoring the pace and distance from Stryd, although it’s correctly sourcing power from the pod.
Can anyone look at this, or is the Race S no longer the priority and we’re stuck with this regression bug?
- Suunto:
-
I know that footpods can have issues with calibration. Is it possible the distance measure is wrong because it’s derived from incorrectly calibrated footpod data?
I believe Suunto and Stryd both suggest performing some calibration runs on a track or similar straight/level terrain of known length. Have you tried this? Do you get accurate data in this case?
-
@Alex-Jurkiewicz Utnlike my previous Ambit3 Peak and 9 Baro, I don’t see anywhere in the Race S menu to calibrate it. I also don’t believe it’s necessary however, as Stryd is precise out of the box.
-
@atoponce said in Issues with pace/distance - Stryd integration:
Utnlike my previous Ambit3 Peak and 9 Baro, I don’t see anywhere in the Race S menu to calibrate it. I also don’t believe it’s necessary however, as Stryd is precise out of the box.
From what I read in the past in the forum, Stryd integration seems to be screwed up since Q3 update multiple BT sensors, if I remember correctly. Missing autocalibration option is a bug in the watch firmware, and the problem is, it needs to be disabled after initial pairing, and used only for manual calibration which is rarely or never needed for most users. So at this point it seems always enabled, as I understand, and I don’t know the implications of that, but is it possible that those implications are what you are seeing? Getting the actual speed/pace from whatever the watch provides, either GNSS based or accelerometer if indoors?
I was contemplating getting Stryd Duo myself for indoor track runs, so I can have an accurate pace and distance (don’t care much about power at this point), but the more I look into it, the weirder the Stryd itself seems, even without Suunto issues.
So there is now 4th generation pod? (Stryd 5.0) - Dec 2025
( 3rd gen (Next Generation Stryd) - late 2022 - Nov 2025
2nd gen (Wind Detection) - June 2019 to September 2022
1st gen - January 2018 to June 2019 )Possible issues that are not clear to me and if they apply to 5.0:
• Reading through Stryd site, I don’t see clearly stated battery life anywhere
• Battery level not available while charging, always shows 0%
• Stryd will switch itself off to save power when your cadence drops below 130 SPM for a few minutes, unless pod gets keep alive command from connected Stryd app
• Exercise can be started on the watch while only using single pod. When using Duo, exercise needs to be started in the Stryd app?
• Pods support only single channel BT connection, so if using the Stryd app, can’t connect to watch using BT? Consequently, without ANT+, can’t connect at all for DUO workout?For USD 300/600 pods, this looks entertaining. Maybe it’s just outdated info and/or my misunderstanding.
