Stryd vs race s
-
@Richard-McGlory there’s a lot of data coming from the pod: I imagine the volume exceeds what the watch can process and reliably deliver functionality.
Case in point: when I was having a go with a Garmin, I was using the watch to play cached Spotify music and track a run while connected to a chest strap and Stryd Duo, with the Stryd CIQ data field. The watch kept auto-pausing the workout, as it was losing connectivity to the Stryd, and it thought that meant speed = 0, so, logically pause. I opened a ticket with Stryd about it, and they said that the watch was out of resources.
I’d rather not have to come up with complex systems, but at the same time I prefer not having my run auto-pause due to resource saturation.
Question for you: when you sync the pod’s data to Stryd, does it overwrite the elevation plot? Mine does; I find it irksome.
-
@Ze-Stuart Thanks that puts things in to more perspective. The watches do have a lot memory though but if you are using maps and music then it will get eaten up quickly.
Yes, on merge the elevation plot gets overwritten and it is as you say it is irksome.
I also found that at times when the data is merged the pace drops to zero, but the data before the merge, pace has no drops. This happens occasionally.I have a Garmin 255, I will probably use that for workouts and see how it goes. I got the SR for trail running and ultras, I didn’t think about Stryd integration at the time.
-
@Richard-McGlory I’m going to open a ticket with Stryd’s support about it: I think they’re very focussed on their AW app (which to their credit is excellent), and Garmin, so another Suunto voice would be great!
-
@Ze-Stuart yeah, that sounds great.
Anyway hats off to the Suunto team for creating the S+ Stryd App otherwise I don’t think anything would have been created.
I would still like to see the option of getting all the data in the .fit file and I think the app shows that it is possible. They could even create a separate app to do it.That would probably take care of the elevation plot issue too.
-
@Richard-McGlory or if the data was left on the Styrd pod, so that one can still sync it after the run. I imagine there’s a flag that says ‘do not record this run’ that’s set by the CIQ field, AW app, and S+ app.
Seconded on them actually doing something, one has to start somewhere!
-
@Ze-Stuart - I have just come of AW to the Race S. I will follow the above. I used the PowerCentre training plans on the AW. I assume there is no automated way of syncing the workout from PowerCentre to Suunto and I would need to re-create as a S+ guide?
-
@kkalsi correct. I find it annoying, but, it gives me the opportunity to really understand the plan, which I value.
It’s not as bad as it seems: there aren’t that many templates for plans, so mostly you have to create them once, and then adjust the intervals and power bands.
-
@kkalsi Yes, unfortunately you are correct. This is, however, entirely in Stryd’s hands as Suunto has an available API and support for structured workouts that works brilliantly for training peaks, TAO and a number of other workout providers. Other than the well-documented lack of alerts when you go out of zone.
Before I switched to a running watch I used iSmoothRun on my iPhone and that could collect all the stryd metrics. But the only way to get them back into stryd was to sync to a garmin connect account and link that to stryd. Again, this is Stryd not being willing to open apis and integrate with more of the running ecosystem.
These days I do as the others have said and sync the stryd every few runs to enrich the run data. Honestly, though, as I don’t have Duo I’m not missing much - I don’t make much use of the additional data and it’s “stuck” inside Stryd power centre, not where I’d use it such as runalyze.
-
@Ze-Stuart Thank you.
-
@far-blue thanks. It is a shame as Stryd seem to be focused on the AW app as the priority
-
@kkalsi it is, but it gives them the most control, and is a huge market segment. Send them enough nice support tickets…
-
@Ze-Stuart agreed - nice tickets on the way !
-
@Richard-McGlory my elevation plot issue was resolved after a suggestion from their support: wash the pods. Turns out the air hole on the front was clogged.
-
@Ze-Stuart Thanks for that, I will give it a go. I take it out on the trails so probably the same issue.
-
@Richard-McGlory turns out I spoke too soon: a run on the same route a couple of days later and the missing elevation was back.
-
@Ze-Stuart check you haven’t caught a lace between the front of the clip and the pod - I’ve done that more than once.
-
I ditched my stryd after using it for years. It’s a bad company with a very bad service. They are always blaming the customer if the device is not working. I had so much trouble with that device regarding accuracy especially when changing shoes or with different watches that I finally ditched the very expensive subscription based device.
I hope they will fail with their anti customer service very hard.
In the meanwhile I am using power for after device analysis only. That’s great on any watch without any special device. Very accurate.
The GPS with the newest watches is so good that it outperforms the stryd pod by far.
My recommendation: Do not buy a stryd pod. If you still are using one: ditch it and feel free.From my running community:
The Stryd community likes to run the 400 m with a measuring wheel to check which is really 400 m long. According to Stryd, you should run exactly on the white line of the first and second lane with your left foot counterclockwise. Under a full moon and sober, of course
, and then after exactly 8 laps you will have run exactly 3248 meters. If it doesn’t work, then the track was built incorrectly or the measuring wheel is broken. 
-
@RightNow that’s a shame you’ve had bad experience with them: I only have good CS experience with them, they have yet to blame me for anything. Doesn’t everyone run with a trundle wheel…?
@far-blue no laces, interesting, though. I hadn’t thought of that.
@Richard-McGlory we ‘swapped the pods’: what was 1, is now 2, and the elevation profile is back. Key point: data from the pod overwrites data from the watch, every time, confirmed by their support. I imagine all that’s retained is the HR and GNSS track.