Anyone expeirence abnormally high Stryd Lap power data after upgrading to 6.0 fw? I see the lap power shows in the 1000 to 2000 range while power should be around 230s.
And the common theme is - cycling. As Stryd note, if you use it as running power using their app it is not a problem. So yes, Garmin have something to fix, but for those using running power, the workaround appears to be to use the Stryd app.
As an aside, I'd be interested to know if this affects only 3rd party power meters and not the Garmin Vectors, or all power meters.
As others have pointed out: You may ignore Stryd here - this is an issue with most (all? all except Garmin's? we simply don't know yet) power meters connecting to F5+ units running 5.57 or above. Furthermore, if you simultaneously capture the ANT+ stream with e.g. a Garmin 520 and a F5+ running 6.00 the data captured by the 520 will be fine while the data captured by the f5+ running 6.00 will show spikes.
While it is technically possible, that the F5+ running 6.0 is correct and Garmin will push new firmwares to all units being able to capture power meter data, which will then all show the reported behavior, and all power meter suppliers have to adjust things on their end this clearly appears to be very unlikely. A more plausible theory is that a bug was introduced into the F5+ firmware and that once the powers to be at Garmin are aware of it things will be fixed. Occam's Razor.
A conspiracy theorist would of course suspect that Garmin introduced this to make all non-Garmin power meters look bad compared to Vector's. I don't buy into this.
Okay, at least Garmin Germany has acknowledged the problem and confirmed that they are working on it:
"Uns liegen Meldungen vor, die das Problem, das Sie beschreiben, zum Inhalt haben. Die entsprechenden Entwicklungsabteilungen in den USA wurden bereits über den Sachverhalt informiert. Die Kollegen dort überprüfen das Problem und arbeiten an einer Lösungsmöglichkeit. Bis es soweit ist, möchten wir Sie um etwas Geduld bitten."
It basically means that the development team is aware of the issue and is working on a fix.
What I had to do to get around first level support ("are you using third party power meters" - much like some people here in the forum) was:
1. Make clear, that the issue is not present with firmware 5.1 and that downgrading fixes the issue. 2. If possible, record the same activity with a different device - in my case a F735XT.
I suggest that everybody opens up cases - usually the people assigned to allocate resources to bug fixing are so far removed, that they tend to look at the number of cases associated to a specific bug, so complaining seems to be the only thing we can do to push priority up.
