In the past, it used to be that the pairing screen that appears on startup would auto-confirm and move on once all previously used devices were paired (I don’t know the exact logic used). So once power, cadence, controllable, HR and perhaps controller were paired, I’d automatically be moved on to the home screen after a few seconds.
This no longer happens, and I’m instead stuck on the pairing screen until I click OK. Not the end of the world, but annoying when what I assume is intended behaviour stopped working.
It might have started happening after I used Zwift Play controllers for a while, but then stopped. In the beginning I assumed it was Zwift waiting for the controllers to connect, which I could see some logic in. But even after deleting knowndevices.xml - which I assume would be the relevant place to look - this behaviour persists.
Any other things I can try tweaking to get this behaviour back? Or has this simply changed?
I have almost the opposite issue where the pairing screen does the countdown and auto-confirm before my HRM (coospo) has properly connected. If I don’t stop the countdown and wait for the full connection, I have to manually go back to the pairing screen to complete that step.
Can we not just have a more robust pairing screen?
If we’ve accepted the connected sensors day after day, week after week, month after month… Zwift should be able to know this is what I want and it can move on.
ie: if I make no changes on the sensor screen after X number of launches, it should safely assume that’s what I want.
Would be great to have preferred devices remembered. If my wife starts riding while I am on the bike she steals my trainer every time. There doesn’t seem to be any way to fix it. If clicking on a pairing tile allowed me to tick a box that says “wait until this thing is available” or “don’t pair to this thing unless I say otherwise” that would be huge.
This killed my ride today. Trainer stolen by 2nd Zwift instance starting up, and then never repaired after being disconnected from the 2nd Zwift instance. Rebooting trainer didn’t help, it just went into the toilet and stayed there.
Never got around to re-installing Zwift (guess it wasn’t annoying enough to mess around with that). However the situation appears to have resolved itself recently - cannot confirm whether it was after an update, or as a result of something I did.
