Vote BLE Dropouts with Elite Justo 2 + Zwift Ride Smart Frame

[nenadjev]

Hi everyone,
I’m experiencing persistent Bluetooth dropouts between my Elite Justo 2 trainer (firmware v36) and Zwift when used with the Zwift Ride Smart Frame in virtual shifting mode.
Setup details:
• Zwift Ride Smart Frame + Zwift Cog
• Elite Justo 2 trainer (firmware v36)
• Windows 11 Pro (ThinkPad X13, Intel AX201 Bluetooth 5.1)
• Android 16 (Samsung Galaxy S25 Ultra, Zwift Companion)
• Tested both direct Bluetooth and Companion bridging
Issue:
• Initial pairing works perfectly
• During rides, Zwift intermittently loses connection to Justo 2
• Zwift Ride Handlebars and HRM stay connected without issue
• To restore functionality, I have to manually re-pair Justo 2 via the ‘Paired Devices’ screen
• Dropouts are less frequent with Companion bridging, but still occur

What I’ve tried:
• Uninstalled/reinstalled Bluetooth drivers
• Removed all paired devices from Windows
• Clean reinstall of Zwift (including Documents, Program Files, AppData)
• Reset Zwift game preferences (Zwift Support Guide)
• Ensured Justo 2 is not paired via Windows Bluetooth settings
• Verified admin privileges and system-level permissions,
• Disabled the internal Bluetooth adapter and tested with an external USB Bluetooth dongle with a USB extension cable to position the dongle closer to the trainer and away from potential interference sources.

etc…

Last winter, everything worked flawlessly with Justo 2 + standard bike, but I didn’t use the trainer from May to October, and the issue started after switching to Zwift Ride and updating to latest firmware

Zwift Tier 3 support confirmed a Windows-level GATT failure, but no clear root cause

I’ve also contacted Elite support, but unfortunately their response was limited to basic troubleshooting questions and didn’t offer any meaningful insight or escalation. At this point, I’m stuck between two support teams and still without a stable solution.

Has anyone else experienced similar BLE instability with Zwift Ride + Justo 2? Any insights, workarounds, or firmware rollback options would be greatly appreciated

Thanks in advance,
Ned