CORSAIR HS80 RGB Wireless Gaming Support

[VictorAseo]

Description

Could you please add this one? I'm experiencing constant issues with mic loopback every time I turn on my microphone. I'm unsure which device ID is the real one.

Headset Name

CORSAIR HS80 RGB Wireless Gaming

Device information

Detailed Device Information

``` Device Found VendorID: 0x1b1c ProductID: 0x0a6b path: /dev/hidraw5 serial_number: 16d64dc300050215 Manufacturer: Corsair Product: CORSAIR HS80 RGB Wireless Gaming Receiver Interface: 3 Usage-Page: 0xff40 Usageid: 0x6 Device Found VendorID: 0x1b1c ProductID: 0x0a6b path: /dev/hidraw5 serial_number: 16d64dc300050215 Manufacturer: Corsair Product: CORSAIR HS80 RGB Wireless Gaming Receiver Interface: 3 Usage-Page: 0xc Usageid: 0x1 Device Found VendorID: 0x1b1c ProductID: 0x0a6b path: /dev/hidraw5 serial_number: 16d64dc300050215 Manufacturer: Corsair Product: CORSAIR HS80 RGB Wireless Gaming Receiver Interface: 3 Usage-Page: 0xc Usageid: 0x1 Device Found VendorID: 0x1b1c ProductID: 0x0a6b path: /dev/hidraw5 serial_number: 16d64dc300050215 Manufacturer: Corsair Product: CORSAIR HS80 RGB Wireless Gaming Receiver Interface: 3 Usage-Page: 0xff42 Usageid: 0x1 Device Found VendorID: 0x1b1c ProductID: 0x0a6b path: /dev/hidraw5 serial_number: 16d64dc300050215 Manufacturer: Corsair Product: CORSAIR HS80 RGB Wireless Gaming Receiver Interface: 3 Usage-Page: 0xff42 Usageid: 0x2 Device Found VendorID: 0x1b1c ProductID: 0x0a6b path: /dev/hidraw5 serial_number: 16d64dc300050215 Manufacturer: Corsair Product: CORSAIR HS80 RGB Wireless Gaming Receiver Interface: 3 Usage-Page: 0xff58 Usageid: 0x1 Device Found VendorID: 0x1b1c ProductID: 0x0a6b path: /dev/hidraw6 serial_number: 16d64dc300050215 Manufacturer: Corsair Product: CORSAIR HS80 RGB Wireless Gaming Receiver Interface: 4 Usage-Page: 0xff41 Usageid: 0x2 Device Found VendorID: 0x1b1c ProductID: 0x0a6b path: /dev/hidraw6 serial_number: 16d64dc300050215 Manufacturer: Corsair Product: CORSAIR HS80 RGB Wireless Gaming Receiver Interface: 4 Usage-Page: 0xff41 Usageid: 0x1 ```

New Device Implementation Checklist

• [X] I acknowledge that implementing a new device requires direct access to the device and familiarity with capturing and analyzing its communications. I have access to the device and am willing to contribute by capturing necessary data and/or attempting implementation.
• [ ] I have already attempted to capture device communications using WireShark or similar tools and am including my findings (successful or not) with this issue to assist in implementation efforts.
• [ ] I am seeking guidance on how to begin this process and am willing to collaborate with the community to add support for this device. I understand where to find resources (refer to the WIKI).

[github-actions[bot]]

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.

[Sapd]

https://github.com/Sapd/HeadsetControl/issues/178

you should be able to control it with AlsaMixer or similar software