HyperX Cloud 2 Wireless support

[noah56]

Description

I'm working on adding support for my headset, the HyperX Cloud 2, but I am running into some issues. I have used Wireshark to capture the packets being sent to my headset, and I believe I have found the byte that gets changed for mic monitoring (sidetone). On this headest, it is either on or off, no sliding scale. Anyway, when I try and send this data to my headset, I receive Failed to send data. Error: -1: ioctl (SFEATURE): Broken pipe. Any advice would be greatly appreciated. This is the data I am trying to send:

./headsetcontrol --dev -- --device 0x0951:0x1718 --send-feature " 0x06, 0x00, 0x02, 0x00, 0x9a, 0x00, 0x00, 0x68, 0x4a, 0x8e, 0x0a, 0x00, 0x00, 0x00, 0xbb, 0x19 0x01, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00"

Also, I captured a few hours of packet data from the headset as it ran from 100% battery down to 97%. I'm working through this now to see if I can find where battery data may be transmitted, but have not had any luck so far.

Headset Name

Hyperx Cloud 2 Wireless

Device information

Detailed Device Information

Device Found
 VendorID: 0x0951
ProductID: 0x1718
 path: /dev/hidraw0
 serial_number: 000000000001
 Manufacturer: Kingston
 Product:      HyperX Cloud II Wireless
 Interface:    3
 Usage-Page: 0xc Usageid: 0x1

Device Found
 VendorID: 0x0951
ProductID: 0x1718
 path: /dev/hidraw0
 serial_number: 000000000001
 Manufacturer: Kingston
 Product:      HyperX Cloud II Wireless
 Interface:    3
 Usage-Page: 0xc Usageid: 0x1

Device Found
 VendorID: 0x0951
ProductID: 0x1718
 path: /dev/hidraw0
 serial_number: 000000000001
 Manufacturer: Kingston
 Product:      HyperX Cloud II Wireless
 Interface:    3
 Usage-Page: 0xff13 Usageid: 0x1

[github-actions]

Hello 👋

Thank you for reaching out and expressing interest in having support for a new headset.
We appreciate your willingness to contribute to the project!

In order to create a implementation for a specific headset, we need to be able to reverse-engineer and test the implementation on that particular device.
Explicitly speaking, only people who actually own the headset, can implement that request.

👉 If you're interested in adding support for a specific headset, we recommend taking a look at our wiki to get started.

📝 If you encounter any problems while using WireShark, we would be more than happy to help. Simply post screenshots and data on your progress.