In my last workout, it seems the actual Watts were fluctuating around~70 Watts while the target Watts was 48W. The resistance on the turbo felt more like 70W than 48W.
In this workout, I tried increasing the target to 70W, and this worked - both target and actual Watts settled in sync. I then took the target Watts back down to the plan of 48W:
This is an intermittent problem I’ve experienced for a while, and the latest workout is the first time I’ve managed to resolve it. However, I think it needs fixing.
Configuration & Set Up
Using Trainer Day app (v 8.5.0) on iPad (Air m2 running iOS26.1) or iPhone (15 running iOS26.1) - tried both and made no difference
Wahoo Kickr Move
Connection: Bluetooth
Workouts - all generated by Coach Jack (no changes or edits by me)
Do you happen to connect a garmin or wahoo cycling computer to your trainer at the same time or have it on in the same room? This move should be exactly like standard kickr which I have one and so do hundreds if not 1000 others and no one has reported anything like this in a few months. One thing to do is quickly click on slope and back to erg or up/down on the buttons below and it should fix it.
No Garmin or Wahoo cycling computer. The only things on are the Kickr and iPhone/iPad running the TrainerDay app.
We’ve only recently changed to the Kickr Move, previously we were using the Wahoo Kickr. I experienced this problem with the Wahoo Kickr and tried both the solutions above, neither of which worked. The activity below was such a workout:
The peak target Watts was 236W with an HR of 121 bpm and an rpm of 89. To put in context I’m an older female leisure cyclist weighing 48 kg with a 20 min FTP of 120, implying a power-to-weight ratio of 4.9 W/kg!!!
I know from experience that if everything is working OK then I would cease to be able to turn the pedals at such a power even if I apply my full body weight.
I was hoping the issue with disappear with the new Kickr Move, but it hasn’t.
Strange. So the other advice is make sure it is not connected to your phone directly in bluetooth settings and finally reinstall our app. It really should work just. fine.
