Chorus Pro (We-Vibe) not connecting: found and protocol matched but handshake fails #846
Description
Describe the bug
The We-Vibe Chorus Pro is not recognized by the device config — "Chorus Pro" is missing from the wevibe-chorus protocol's name list (which includes "Chorus", "skeena", "Sync 2", etc.). After manually adding "Chorus Pro" to the name list, the device is found and matched to wevibe-chorus, but the Bluetooth handshake never completes — the device stays in "trying to connect" state indefinitely and never appears in the Connected Devices panel.
Expected behavior
The Chorus Pro should connect successfully and be controllable via Intiface Central, as the original Chorus is listed as supported.
Actual behavior
Without the manual config edit: No viable protocols for hardware... ignoring.
After adding "Chorus Pro" to the name list: device is found and protocol is matched (Found protocol "wevibe-chorus"), but connection never completes. Log shows Device PeripheralId(...) currently trying to connect, ignoring new device event repeatedly. Device never appears in Connected Devices panel.
Additional context
Device config version: 4.179. Intiface Central version: 3.0.3+39. macOS Monterey 12.7.6.
Advertised services: 0000bb03-0000-1000-8000-00805f9b34fb, 00000203-0000-1000-8000-00805f9b34fb
Manufacturer data — company: 55809, data: [2, 41, 3, 3, 20, 0, 4, 1, 2, 5, 6, 56, 29, 178, 201, 181, 51]
The Chorus Pro may require a different connection handshake than the original Chorus. See also #424 (original Chorus issue, fixed in 6.2.0 — fix does not appear to cover the Pro variant).
Two requests: (1) add "Chorus Pro" to the wevibe-chorus name list in the official device config, and (2) investigate whether the Pro's handshake differs from the original.