Have a bowflex216 I can pair with the game but when I start it the avatar won’t move… I deleted the game from my pc( it was working there originally) I deleted from laptop (currently using it for the game) and reinstalled, updated the game and still nothing. On the cycling world all is normal. Can’t figure this out… need help
To confirm: this is the BTX 216 treadmill?
Can you post photos of your pairing screen in Zwift, as well as what you see when in the run?
OK, you’ve got it paired but the top left of the game screen is a hint: “Connection Failure.”
If you’ve EVER had ANY other device paired to your treadmill (phone app, whatever) it’s possible something is attempting to take over the connection. I would advise starting with that - remove device pairing on every other device and app you’ve got. (go so far as to shut other devices down completely)
I’d also advise trying ANT+ if it’s supported by the treadmill since you’re having issues with Bluetooth. Alternately, remove the ANT+ dongle from the device running Zwift and just use BLE. (off chance ANT+ is causing interference)
Also worth jumping into the thread Dean linked to.
Beyond that, I’m going to have to tap out and let someone with more experience diagnosing connection failures jump in.
The linked thread has all the answers. The date the treadmill was paired on seems to be the key.
I imagine uninstalling and reinstalling the app effectively means you lose any previous pairing history.
We have confirmed this bug and are investigating.
For all affected users, this may be an issue caused by multiple connections, as @Otto_Destruct called out. A common workaround for this is to disable bluetooth on any devices unnecessary for your Zwift activity and force close all apps that have connected to the treadmill.
Additionally, I’d like to recommend (safely) powering down and unplugging your treadmill to allow it to forget previous connections. Then, while on the Zwift pairing screen, (safely) plug in and power on your treadmill.
I will update with any further tips and news from the developers. Please continue to post or reach out if the provided workaround helps or not.