Related

Power average zero after a ride?

9594373
5 days ago

I've had this happen twice this spring. I go on a bike ride and see that power meter is connected, the Edge shows power fine, but after the ride the Forerunner 955 says average power was zero and the power flatlines on zero for the entire ride. What is the most infuriating thing is that on both occasions I discarded the Edge ride and saved the Forerunner ride, because I didn't notice this.

I have Edge 830 so my watch has higher accuracy GPS and that's why I prefer saving the workout recorded by the watch.

Is this a known issue?

  • 0 5 days ago

    Also the exercise reports 0 active calories even though HR data is available. Everything indicates the power meter was connected, because without the power meter the watch would use solely HR for calory estimates and now it's ignoring HR. The fact that the Edge showed feasible power data throughout the exercise rules out the power meter as the culprit.

  • 0 4 days ago

    I've experienced problems where the power meter either disconnected during a ride, or it didn't connect properly in the first place.  I've had similar issues with a non-Garmin cadence sensor which suggests it is 955 flakiness.

    I use another Garmin device as a remote display that just picks up all the ANT+ sensors which is mounted on the stem of my bike with the power meter.  When I've had the connectivity problems the device on the stem has showed the power values whilst the 955 did not.  There is definitely an issue in my case, and it seems like in yours as well.

    I've also experienced problems where the power wasn't re-connected after re-starting an activity which had been paused using "Resume later".

    I now always make sure that in all the above cases the cadence sensor on that bike is connected, and also that the power meter on the other bike is registering values on the watch screen before I set off,  It is tedious and I obviously shouldn't have to do this, but it seems necessary.  I've not (yet) reported it to Garmin.  Maybe I had hoped this issue would go away.  I've not experienced it lately but this is likely because I don't allow it to happen rather than that the issue has been fixed.