Wrist power instead of Stryd?
-
Since the latest update I am really sure that my S9PP shows the power from the watch/wrist instead of the power from the Stryd sensor even when the sensor is shown as connected on the landing page of the workout. Maybe a bug came in here?
-
@jschmidt can you elaborate what makes you think so?
-
There are many points that make me think so: The power values are less responsive (they feel more like 10s than 3s), they are about 10W lower, I see drops (the value goes to zero and goes again up to its former level). I’m using Stryd for many years but never saw such reactions.
-
There is a known issue with the drops to 0w originally reported for the Race S but I think now also reported for the Race and the Vertical. I know what you mean regarding the 10s response time with the in-built power but I’ve not noticed this (or the 10w difference) on my Race S even though I am seeing the drops to 0w. I’ll pay more attention to power rate of update on my run tomorrow. There’s some confusion whether the issue is a display bug or a bluetooth problem or something else. I’ve tried to test whether it’s related to the environment but have not found any patterns. FYI, the original issue on the Race S was reported very quickly after the latest firmware update so the conversation about it is in that topic.
-
@far-blue Should not be a Bluetooth problem as it also happens with inbuild power
-
@jschmidt as others said, sounds like the known issue related to power drops to 0 that’s is there in the last couple of software updates… Validate power avg values between Suunto app vs Stryd app specially for structured workouts. If there’s a big difference in watts in the manual laps, this confirms the known issue.
-
Thank you guys for all your answers! I did a search on this forum before I made this post but it looks like I missed that this is a known issue. I’m wondering a bit why I didn’t notice this during all of my running sessions in the past. But anyway, maybe I began to watch at my wrist too often… Finally I resume that I have to wait for (one of the) next update to get out of this minor trouble.
