Hi all, I got the Zwift ride, play and core last week and have been plagued with this since. I installed the latest firmware straight out the box. I did a factory spin down on Thursday evening (braking factor 0.92), which cured it, then did a race Friday and was pleased to see it wasn’t an issue at the start of the race, although came back 10 minutes into the race.
Has the theory that the auto calibration is causing it, rather than curing it, been explored?
that’s not good.
We don’t know if its auto-calibration causing it, or auto-calibration exposing it.
I’ve done quite a bit of testing isolating variables. Including Belt tension, Virtual shifting, chainring gear ratio, pedalling imbalance, flywheel balance, software, device, wireless interference, temperature.
There are two conditions that I have found tend to trigger it
Hard long low cadence climbing finishing with a large sprint and coasting downhill
A hard sprint at the end of a race and then exiting the game (it shows up next ride)
In both cases you need virtual shifting activated. Mechanical shifting des not trigger it.
My suspicion (as per the first forum posts that started to appear from Feb/March) is that under extreme conditions virtual shifting messes with auto-calibration and triggers an unresolvable miscalibration.
Unfortunately, we don’t know for sure. Only Wahoo will be able to understand how their firmware and algorithms work.
We also don’t know if other manufacturers are susceptible to the power offset, but we have no reports of ghost watts.
What we do know is that once the power offset is triggered it remains stored on the Wahoo KickR device and it is then present in all platforms (indieVelo, MyWhoosh, Wahoo app) even if you then use mechanical shifting
Apparently this is a Wahoo problem, but it should still be a priority for Zwift as well since it impacts the fairness of racing as well as the general accuracy of the user experience.
It seems like maybe there are tolerances within the virtual shifting processes that allow it to work fine in most situations but with gears/cogs on the extreme ends the calculations get off. The most recent firmware maybe expanded those tolerances a bit. But the free watt issue is not solved.
I tried the factory spindown. It’s impossible for me to do it directly from the Wahoo App (i tried tapping 10x many times but no access to the spindown process), but I can do it with the Wahoo Pro Spindown App (may be because I got a kickr Move which shouldn’t need any factory spindown?).
Anyway, the spindown works appently well but when I try on Zwift (with or without connecting the Zwift Play), the ghost watts remain.
I have tried a dozen time (before a race, after a race, with or without the ZP connected… actually in any possible configuration). The problem remain…
In case anyone is interested, I replicated the issue today. 8W differential between my Assiomas and my Core when going up the Grade. This was with the latest Kickr Core firmware upgrade. (1.5.36, released October).
I am also noticing higher Wahoo Kickr Core readings with virtual shifting compared to my Assioma pedals. Very similar to what you noticed – traditionally, the Core would be 2 watts lower on average on longer efforts, but now I am seeing the Core read ~8 watts higher than the pedals on sustained efforts.
I’ve done a factory spindown + restart, but it seems to still persist.
I’ve raised the issue with Wahoo. They asked me to run a test with the trainer in erg mode run from the Zwift app and another head unit recording a different PM. I ran this once but my second head unit did not record any power?! I came down with COVID, so I’ll try to run that test when I recover.
Not sure if any fixes were released, but I am pleased to report that I have gone from getting ghost watts every race (after spin down each time) to no issues for the last 3 weeks, very happy!