I/we are having issues with the iOS app not switching the Kickr trainer between ERG and SLOPE on my created workouts.
Thought it was me but I’ve checked and re-checked my workouts created and they’re correct to how I’ve always created them.
When switching from ERG to SLOPE it switches to SLOPE for a brief second then switches back into ERG mode.
It then randomly starts working 3/4 way through a session but whats supposed to be ERG switches to SLOPE… So the Kickr is switching, thats not a problem.
My wife is having the same issue with her (different) created workouts so its not a unique problem to me apparently. We’re both on iOS apps.
Is there something e should be doing that we aren’t due to an update? It worked perfectly up to the last couple of weeks.
This feature is super important for us as our coach sets structure mixed with max efforts in the same workout.
I can share with you the workout somehow if needed but not sure how…
We are both on version 3.7.3 connected to a Wahoo Kickr.
Would someone be able to help? I’ve a 1265mile ride I’m training for and need this feature working ideally as Im pretty close to the event… If possible… pretty please…
Hi Jbrown. Please try updating to the latest version 3.7.6. We encountered some issues with ble in version 3.7.3 as after we updated the library. For some users, this version has resolved the issues that emerged. If this doesn’t help, please let us know whether the switch to visual mode is happening, and please text your workout
I am on vacation but available to test this on Thursday. I have Kickr also but as Grigory said v 3.7.6 fixes a lot of bluetooth issues we had which seems to fix other problems.
Unfortunately using the updated app hasn’t changed anything.
It still blips to slope mode when asked then immediately goes back to ERG mode.
I can manually change it to Slopemodeo. The app interface either…
Thanks so much. We are growing quickly and one of the top priorities when we get a little bigger is to bring our current tester (he’s amazing) onboard full-time and this should reduce the chances of bugs like this appearing. Recently we had a few bugs that affected a handful of users including this one. This is stressful. but we are getting closer and closer to getting it all resolved.