As of this posting, there appears to be an issue with Zwift that is causing the rolldown calibration of a Hammer or Magnus to fail. This is not an issue with your Hammer or Magnus trainer. Zwift is hard at work to resolve this.
Until a fix has been completed, we recommend that a rolldown calibration be done using the Rouvy software (no subscription required). There are support articles on Zwift and Rouvy to walk you through this process on Rouvy.
It is completely fine to calibrate your trainer in Rouvy and then ride in Zwift because the calibration of the trainer is stored within the trainer; not the software.
Comments
1 comment
A quick note to share I just experienced the on-going problem with the Zwift calibration process with my CycleOps M2. It seemed to work the first time but as soon as I rode it was clear the trainer was not communicating the correct wattage to the Zwift app. When I attempted to re-calibarate I experienced all the same issues documented by so many other M2 owners (failed calibration, etc.).
I switched over the to Rouvy app and the calibration seemed to go OK. I will have need to test it more to confirm.
I understand the costs associated with creating a CycleOps app to perform this calibration process, and it would be in the best interest of Zwift and CycleOps to collaborate on the solution. From a few posts I saw from Zwift they seemed to spend more time explaining why it was not their fault instead of thinking about how they could contribute to a solution.
The M2 is a good product and I am hopeful you and the Swift team will figure this out.
Please sign in to leave a comment.