After upgrading to Kickr Core FW v1.4.8 and Zwift 1.60.0 (since Saturday 2024-03-09) there seems to be an offset on the power reported from Kickr Core. It is most noticeable when attempting to supertuck. The wattage does not drop fully to zero, like it used to do (at least not for several seconds), but seems to have a baseline offset of around 27W. My 20min avg from Kickr Core was 271W compared to 254W from Stages. I have done a lot of DRs and it has always been the other way around (Stages reporting higher than Kickr) and Kickr used to drop to zero as expected.
From yesterdays race: zwiftpower analysis set_id 412921 (my messed up numbers caused Zwift to bump me to B for at least 90 days).
I was planning to do some testing today, but of course there is no repro. I did power cycle the Kicker Core after the race yesterday, but I am 98% sure I also power cycled it after updating the FW to v.1.4.8 on Saturday.
Today (Analysis set 413210 over at ZwiftPower if you want to have a closer look) it drops nicely to zero and the Stages power meter reports higher numbers):
Hi, I’ve also had the same issue but with my Kickr V6, at first I thought I had good legs, but after a couple of rides I could see that my power meter wasn’t matching up, the higher the power the bigger the discrepancy and like you said it seemed to take longer than usual for the power to go down to zero. I’ve gave up and went back to a certified reconditioned V5 and it matches within 1% with my power meter. I’ve emailed Wahoo but just get the usual checks and tests to perform. I’m thinking it could be a software issue?
I am not sure how that would produce the issue in the initial post (power not dropping to zero), but the Kickr Core is brand new (since November 2023) and as already stated the problem has not reproed since Sunday (raced yesterday and did several supertucks ;))
I only had this issue on two rides. Went away after I cut off power to the Kicker Core (full reboot). I have not seen it since. Not sure what happened.
I had this after riding up Epic KOM. I did a few reboots and got onto Wahoo who suggested I do a Factory Spin down. Its in a hidden menu on the Wahoo app because it can damage the trainer and should only be done if asked by Wahoo.
It happened after coasting from very high flywheel speeds, and I was able to replicate the issue in Wahoo app, Zwift, and IndieVelo. Neither did it matter if I use virtual shifting or manual shifting,
The issue mostly went away, but has occasionally reappeared after hard climbs. I’ve found that adding a little tension to the belt (usually on or two turns) stops the issue.
There are a few posts on this and I really think Wahoo need to address this. Especially if it is being caused by belt stretch.
For me it went away after a manual spindown + poweroff. Did not come again after that but I don’t trust it fully.
As you said next steps would have been factory spindown+belt and then wahoo support.
Thanks for sharing your experience, I hope wahoo is having a closer look at this.
