Corsair VOID Wireless V2 (0x2A08) detected but reported offline on Windows

[x1le1]

Description

Hi,

I tested HeadsetControl with my real Corsair VOID Wireless V2 headset on Windows 11.

The headset is detected correctly:

• Device: Corsair Wireless V2 Headset Device
• Product: CORSAIR VOID WIRELESS v2 Gaming Receiver
• Vendor ID: 0x1b1c
• Product ID: 0x2a08

However, the device is reported as offline and functionality does not work.

Output:

{
  "name": "HeadsetControl",
  "version": "continuous-43-ga16be48",
  "device_count": 1,
  "devices": [
    {
      "status": "partial",
      "device": "Corsair Wireless V2 Headset Device",
      "vendor": "Corsair",
      "product": "CORSAIR VOID WIRELESS v2 Gaming Receiver",
      "id_vendor": "0x1b1c",
      "id_product": "0x2a08",
      "capabilities": [
        "CAP_SIDETONE",
        "CAP_BATTERY_STATUS"
      ],
      "battery": {
        "status": "BATTERY_UNAVAILABLE",
        "level": -1
      },
      "errors": {
        "battery": "Device is offline or not responding"
      }
    }
  ]
}

Connection check:

headsetcontrol --connected
false

Sidetone also fails:

headsetcontrol -s 50

Found 1 supported device(s):
Corsair Wireless V2 Headset Device (CORSAIR VOID WIRELESS v2 Gaming Receiver) [0x1b1c:0x2a08]

Device is offline or not responding

The headset itself works normally in Windows and in Corsair iCUE.

I also checked the raw HID interfaces and found:

Interface 4 -> usage page 0xff42
Interface 3 -> usage page 0xff13

Since support for this headset was added in PR #492 by @Frank-py, maybe this is a protocol mismatch / firmware revision issue in initializeDevice() for corsair_void_v2w.hpp?

Thanks

Headset Name

Corsair VOID Wireless V2

On which OS does the problem happen?

Windows

Device information

Detailed Device Information

Device Found
 VendorID:  0x1b1c
 ProductID: 0x2a08
 Path: \\?\HID#VID_1B1C&PID_2A08&MI_04&Col01#8&23ed808a&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
 Serial: AD11C54501SVCA
 Manufacturer: Corsair
 Product: CORSAIR VOID WIRELESS v2 Gaming Receiver
 Interface: 4
 Usage-Page: 0xff42  Usage-ID: 0x0001

Device Found
 VendorID:  0x1b1c
 ProductID: 0x2a08
 Path: \\?\HID#VID_1B1C&PID_2A08&MI_04&Col02#8&23ed808a&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}
 Serial: AD11C54501SVCA
 Manufacturer: Corsair
 Product: CORSAIR VOID WIRELESS v2 Gaming Receiver
 Interface: 4
 Usage-Page: 0xff42  Usage-ID: 0x0002

Device Found
 VendorID:  0x1b1c
 ProductID: 0x2a08
 Path: \\?\HID#VID_1B1C&PID_2A08&MI_03&Col01#8&371d9cc8&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
 Serial: AD11C54501SVCA
 Manufacturer: Corsair
 Product: CORSAIR VOID WIRELESS v2 Gaming Receiver
 Interface: 3
 Usage-Page: 0x000c  Usage-ID: 0x0001

Device Found
 VendorID:  0x1b1c
 ProductID: 0x2a08
 Path: \\?\HID#VID_1B1C&PID_2A08&MI_03&Col02#8&371d9cc8&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}
 Serial: AD11C54501SVCA
 Manufacturer: Corsair
 Product: CORSAIR VOID WIRELESS v2 Gaming Receiver
 Interface: 3
 Usage-Page: 0xff13  Usage-ID: 0x0001

Device Found
 VendorID:  0x1b1c
 ProductID: 0x2a08
 Path: \\?\HID#VID_1B1C&PID_2A08&MI_03&Col03#8&371d9cc8&0&0002#{4d1e55b2-f16f-11cf-88cb-001111000030}
 Serial: AD11C54501SVCA
 Manufacturer: Corsair
 Product: CORSAIR VOID WIRELESS v2 Gaming Receiver
 Interface: 3
 Usage-Page: 0x000b  Usage-ID: 0x0005

[Frank-py]

Could you maybe post wireshark traffic so that we can pinpoint the issue. I use this daily and it works with no problems

[x1le1]

I captured USB traffic on Windows while reproducing the issue.

HeadsetControl does detect the headset as a supported device correctly:
Corsair Wireless V2 Headset Device (CORSAIR VOID WIRELESS v2 Gaming Receiver) [0x1b1c:0x2a08]

It also reports the expected capabilities (battery + sidetone), so device detection itself seems to work.

Steps I followed:

1. Started Wireshark capture on the USBPcap interface where the Corsair receiver appears
2. Applied this filter:
   usb.idVendor == 0x1b1c && usb.idProduct == 0x2a08
3. Ran these commands:

headsetcontrol --connected
headsetcontrol -b
headsetcontrol -s 50

Results:

--connected returns false

-b returns:
BATTERY_UNAVAILABLE / Device is offline or not responding

-s 50 returns:
Device is offline or not responding

What is interesting is that no USB traffic from HeadsetControl appears at all during these commands.
The only visible packet is the initial USB device descriptor enumeration packet.

This makes it look like HeadsetControl successfully detects the device, but does not actually communicate with it on my Windows setup.

I also checked the other USBPcap interfaces:

USBPcap1:
This is the only interface where the Corsair receiver appears.

USBPcap2:
No headset traffic at all.

USBPcap3:
No headset traffic, not even the initial enumeration packet.

Screenshot attached.
If needed, I can also provide the .pcapng capture file.