BLE Disconnect Error

Bugs and Support
1

This is a first for me, my hub has disconnected sporadically the past two rides and has never had this problem before. I recently got a new desktop so please advise if there’s any settings I should investigate. I’m concerned the hob is going to drop out during a race. I will attempt an ANT+ ride later today/tomorrow to see if the issue persists in a different protocol.

Relevant log:

[9:20:36] [BLE] Sending DEVICE - BLE DISCONNECT ERROR [ UUID: 244511008029508 ] Zwift Hub FB44
[9:20:36] INFO LEVEL: [ZwiftProtocol] Component on “Zwift Hub FB44” changed state from 3 to 0
[9:20:36] DEBUG LEVEL: [ZwiftHardware] Device Lost ID: 322693523
[9:20:36] Device List:
[9:20:36] ===========================================================================
[9:20:36] Cadence: Zwift Hub FB44 (0x133BE993) [BLE]
[9:20:36] Power: Zwift Hub FB44 (0x133BE993) [BLE]
[9:20:36] Shifter Input: Zwift Click E176 (0x1C56E790) [BLE]
[9:20:36] Heart Rate: Forerunner (0x14D4FF84) [BLE]
[9:20:36] ===========================================================================
[9:20:36] Device List:
[9:20:36] ===========================================================================
[9:20:36] Non-Selected: Zwift Hub FB44 (0x133BE993) [BLE]
[9:20:36] Shifter Input: Zwift Click E176 (0x1C56E790) [BLE]
[9:20:36] Heart Rate: Forerunner (0x14D4FF84) [BLE]
[9:20:36] ===========================================================================
[9:20:36] [ActionBarV2] ZCActionBar: UserAction has changed: teleport:pacers (children=false)
[9:20:36] [ActionBarV2] ZCActionBar: UserAction has changed: teleport:friends (children=false)
[9:20:36] [INFO] UDP host 34.209.156.251:3024 (secure)
[9:20:36] [INFO] Connecting to UDP server with relay id -2109620990…
[9:20:38] [BLE] Failed to retrieve GATT Services
[9:20:38] [BLE] Sending DEVICE - BLE DISCONNECT ERROR [ UUID: 244511008029508 ] Zwift Hub FB44
[9:20:38] DEBUG LEVEL: [ZwiftHardware] Device Lost ID: 322693523
[9:20:38] [BLE] Sending DEVICE - BLE DISCONNECT ERROR [ UUID: 244511008029508 ] Zwift Hub FB44
[9:20:38] DEBUG LEVEL: [ZwiftHardware] Device Lost ID: 322693523
[9:20:38] DEBUG LEVEL: [ZwiftHardware] Device Lost ID: 322693523
[9:20:38] DEBUG LEVEL: [ZwiftHardware] Device Lost ID: 322693523
[9:20:38] DEBUG LEVEL: [ZwiftHardware] Device Lost ID: 322693523
[9:20:38] DEBUG LEVEL: [ZwiftHardware] Device Lost ID: 322693523
[9:20:39] FPS 164.84, -549890, 10515, -471588
[9:20:40] [INFO] UDP host 18.236.113.35:3024 (secure)
[9:20:40] [INFO] Connecting to UDP server with relay id -2109620990…
[9:20:40] [BLE] Failed to retrieve GATT Services
[9:20:40] DEBUG LEVEL: [ZwiftHardware] Device Lost ID: 322693523
[9:20:40] DEBUG LEVEL: [ZwiftHardware] Device Lost ID: 322693523
[9:20:40] DEBUG LEVEL: [ZwiftHardware] Device Lost ID: 322693523
[9:20:40] DEBUG LEVEL: [ZwiftHardware] Device Lost ID: 322693523
[9:20:40] DEBUG LEVEL: [ZwiftHardware] Device Lost ID: 322693523
[9:20:40] DEBUG LEVEL: [ZwiftHardware] Device Lost ID: 322693523
[9:20:44] [Route] Hit checkpoint 31 out of 223 on route: " R.G.V."
[9:20:44] [BLE] “Zwift Hub FB44” firmware version: 5.2.2
[9:20:44] [ZwiftHardware] “Zwift Hub FB44” NECOD: 0
[9:20:44] “Zwift Hub FB44” hardware revision number: 1
[9:20:45] [NETWORK] DFU: ERROR: checking for dfu updates; no response
[9:20:45] [BLE] Sending DEVICE - BLE RECONNECT [ UUID: 244511008029508 ] Zwift Hub FB44
[9:20:45] INFO LEVEL: [ZwiftProtocol] Component on “Zwift Hub FB44” changed state from 0 to 1
[9:20:45] DEBUG LEVEL: [ZwiftHardware] Device Recovered ID: 322693523
[9:20:45] [BLE] Reconnected and selected “Zwift Hub FB44”.
[9:20:45] Device List:
[9:20:45] ===========================================================================
[9:20:45] Cadence: Zwift Hub FB44 (0x133BE993) [BLE]
[9:20:45] Controllable Trainer: Zwift Hub FB44 (0x133BE993) [BLE]
[9:20:45] Power: Zwift Hub FB44 (0x133BE993) [BLE]
[9:20:45] Shifter Input: Zwift Click E176 (0x1C56E790) [BLE]
[9:20:45] Heart Rate: Forerunner (0x14D4FF84) [BLE]
[9:20:45] ===========================================================================
[9:20:45] INFO LEVEL: [ZwiftProtocol] Component on “Zwift Hub FB44” changed state from 1 to 2
[9:20:45] INFO LEVEL: [ZwiftProtocol] Component on “Zwift Hub FB44” changed state from 2 to 3
[9:20:45] INFO LEVEL: [ZwiftProtocol] Comms established with Zwift Hub FB44.
[9:20:45] ERROR LEVEL: [ZwiftProtocol] “Zwift Hub FB44” decoding msg type 42 failed: wrong wire type

[9:20:45] ERROR LEVEL: [ZwiftProtocol] “Zwift Hub FB44” decoding msg type 42 failed: missing required field

[9:20:46] ERROR LEVEL: [ZwiftProtocol] Zwift Hub FB44 Timeout for GET [object ID: 0] after 1 attempts
[9:20:46] ERROR LEVEL: [ZwiftProtocol] “Zwift Hub FB44” decoding msg type 42 failed: wrong wire type

[9:20:47] ERROR LEVEL: [ZwiftProtocol] Zwift Hub FB44 Timeout for GET [object ID: 0] after 2 attempts
[9:20:47] FPS 163.93, -551521, 10515, -477434
[9:20:48] ERROR LEVEL: [ZwiftProtocol] Zwift Hub FB44 ZP Sync queue didn’t receive response. {description: GET [object ID: 0], sendCount: 3}

2

You appear to be using the Click shifter, which means you cannot pair the trainer via ANT+ or the shifter will be disabled.

It’s not rare to find PCs with poorly performing Bluetooth adapters, which can typically be resolved by using a Bluetooth USB dongle on an extension cable. If you go that route, this video has advice:

3

I’ll be honest, I do have some doubts about it having poorly performing bluetooth as it already has an external antenna that’s at most 3 feet from my trainer. That said, I do have a wifi / bluetooth add-in card which also has an external antenna I can try out. Thanks.

It would be more useful if there were some way to analyze our log files to know what the issue actually is instead of playing hardware swap until it’s resolved.

4

There is! Upload logs to zwiftalizer.com

5

Fancy, thank you.

image
image1606×645 22.8 KB

Says 4 disconnects, which was the number I experienced.

6

I’ve done some repositioning of antennas, removed excess noise and obstructions, I have a group sprint training scheduled tonight which should give me an hour to test everything.

Thanks for the advice.

1 Like