come on Zwift!!!
This is pretty fundamental!!! there is total silence with no fix in sight.
any updates from Zwift on this?
Any updates?
I recently found a bug with pairing Tickr as HR as well.
You can pair it, but it simply won’t show up when riding.
I haven’t been doing a LOT of Zwift rides in the past few weeks, but did one today.
The issue seems to be resolved here. I connected to the Rally pedals for power and Zwift remembered the Kickr as my “controllable”, and the pedals for cadence.
(Probably coincidental, but I did have a firmware update for my Kickr that I applied just prior to riding)
Apparently yesterday was just “luck”. On today’s ride I had to revert to the previous gymnastics of having the Kickr selected for power before I could select the Kickr for “controllable”
No resolution yet here
It has not worked for me since July @shooj when will this be resolved?
Seconding this, seems like communications have completely shut down for these bugs.
Are you able to do the workaround where you pair the trainer as power first and then as controllable and then swapping the power source to your power meter?
Or is this also now broken?
2 Likes
As of yesterday, this worked for my husband - he hadn’t used Zwift in weeks, so he was forced to do an app update before riding, so I’m guessing he was on the latest build (on iPad).
Same issue here. Discovered work around on my own. Also Garmin rally pedals go in and out and have some lag time. Really frustrating.
Its been months now with nothing coming out from Zwift regarding this problem, what is the real issue? I cannot imagine it would be this hard to fix something which has previously worked for years…
1 Like
Since Approx last May !!! ( with a brief “update” that prevented separate power/control)
on boot my Garmin V3 pedals show as power ( and cadence), but there is no controllable device, shown or selectable ( even if I wait for minutes)
I have to select my controllable kinetic for power, when it then magically appears as controllable AND power
Then I have to re-select my V3 power pedals in the power menu
All very much of a pain, especially with the apple TV remote !
When will this be fixed ?
1 Like
This has always been the case on Android so I’m guessing never!
agree “never”, but it used to work !
Much like investments, updates in zwift can improve as well as worsen things.
@Mike.W is there any update on this issue? I have just started using my Garmin Vector 3 pedals as the power source and am still seeing this issue (iPad, Zwift v1.18.1, Kickr Core trainer with 1.1.3 firmware). The only thing that works for me is the full pairing workaround you describe above; I have to do this every time I log into Zwift. Last winter this functionality was working fine!
2 Likes
@Thomas_Wright1, I can tell you work is being done to restore the ability to auto-pair mixed devices without having to go through all the steps I posted. Those changes will not be in the November or December releases, but it’s on our list.
A little background: There used to be the ability to have different power source and controllable trainer pair automatically. This was due to some test code that had been left in the app for some time. The test code caused an inconsistent experience among Zwifters on Mac and iOS (some had the behavior, others did not).
It was also “too much of a good thing”, because the behavior caused Zwift to pair to every device it could find (while on the Pairing Screen). This meant indoor events or training centers had issues with participants being unable to pair specific devices because one person might be paired to all of them.
For these reasons (inconsistent experience among users, pairing to everything) the behavior was removed.
However, the vocal feedback from the community has been heard, and we believe we can allow a “first-pairing” experience to properly set up and configure nearby hardware, then automatically pair to the saved (mixed) devices in subsequent sessions (with the ability to reset to “first pairing” if the environment changes). We are also including Windows and Android platforms so all users can benefit from these changes.
We’re working to make pairing simpler on the one hand, but recognize that some players need us to build a more sophisticated system for more complex training environments. It’s not a slam dunk, and we appreciate your patience.
1 Like
Thank you for the detailed explanation and timeline - that really helps. I look forward to seeing the fix in the new year.
I’d think having to go through the pairing screen every time at startup (instead of set-and-forget) would make this scenario more likely, not less.
For extra credit, consider an extra mode (only accessible via configuration files or whatever) that makes changing the paired HRM easy but hides the rest of the sensors by default.
Thanks for the explanation. Seriously, this makes sense and an understanding of the issue makes it much easier to be patient,
I would suggest that providing this detail early on would have saved a LOT of frustrated messages in this thread. All we could see was something that was working just fine (for us, in hindsight) had stopped working, and it appeared that, for months, nobody could find where they broke the code, or it was never important enough to deal with. I think most of us would have been much more patient with this understanding of the issue.
2 Likes