Other HyperX headset support?

[SpnKO]

How difficult would it be to implement support for other headsets, and if not difficult, what is required from owners of other HyperX headsets? (I personally own a wireless Cloud 2)

[kondinskis]

Since I don't have access to Cloud 2 it would be hard for me to add support, but if you have the knowledge you can always capture the bytes sent/received on the official hyperx application on windows.

[SpnKO]

I would love to do whatever is necessary to get support, if there's perhaps a short guide on how to do this? (I'm assuming the data is similar to the cloud flight, so only a slight change is necessary).

[tottoszsolt]

I would help contribute too I have the ID's for the Cloud 2 Wireless from Linux

I tried changing the ID's on the cloud_flights files but I think that is not as easy.

[DaPutzy]

@tottoszsolt if you are still interested i would be willing to give you a hand?

[tottoszsolt]

Sure

[DaPutzy]

With this tool, could you run:

./hidapitester --vidpid 0951:1718 --open --read-input-forever

and capture all the events? i.e. Do an action and capture the corresponding output. Actions beeing:

• Mute
• UnMute
• VolumeUp
• VolumeDown
• PowerOn
• PowerOff

[michalis97500]

The tool mentioned here doesn't seem to select the correct interface (on windows). I managed to get some code working in Python for supporting HyperX Cloud II wireless although I am faced with the following issue, after writing to the device I get a reply from the headset (status, as a list) of which I can get the necessary information. However after that the device is unresponsive unless I open up NGenuity again. I don't know why it only replies to my first buffer only. I have attached some screenshots and any help is appreciated

[MrMangolo]

Hey, could you share your code regarding that and especially how you found out the HardwareID which you specified there?

Edit: Found out how to get the Vendor and Hardware ID.

Following that I've been trying around with this code:
https://github.com/Agustin-Jerusalinsky/hyperx-cloud-II-battery/blob/master/battery.py

Now im getting an error though.

Commenting out that line just gets stuck at reading the response..

[RadiantOblivion]

With this tool, could you run:

./hidapitester --vidpid 0951:1718 --open --read-input-forever

and capture all the events? i.e. Do an action and capture the corresponding output. Actions beeing:

* Mute

* UnMute

* VolumeUp

* VolumeDown

* PowerOn

* PowerOff

@DaPutzy I've attached a file of all recordings for each action for the HyperX Cloud II Wireless. Let me know if there's any other info I can provide. I'll leave the byte sniffer running to see if it will catch a battery percent report.

HID-OUTPUT-HYPERX-CLOUDII-WIRELESS.txt

[ISAndreiva]

I would help contribute too I have the ID's for the Cloud 2 Wireless from Linux I tried changing the ID's on the cloud_flights files but I think that is not as easy.

My Cloud II has a different ID:
Bus 001 Device 002: ID 03f0:018b HP, Inc HyperX Cloud II Wireless

[RadiantOblivion]

I would help contribute too I have the ID's for the Cloud 2 Wireless from Linux I tried changing the ID's on the cloud_flights files but I think that is not as easy.

My Cloud II has a different ID: Bus 001 Device 002: ID 03f0:018b HP, Inc HyperX Cloud II Wireless

HP acquired HyperX in 2021. Your headset must be manufactured after that acquisition date, ours would be before. There shouldn't be anything different other than the vendor ID/product ID. However, I would test the hidapitester mentioned above to make sure the byte readings are the same at the txt I submitted.

[tottoszsolt]

I would help contribute too I have the ID's for the Cloud 2 Wireless from Linux I tried changing the ID's on the cloud_flights files but I think that is not as easy.

My Cloud II has a different ID: Bus 001 Device 002: ID 03f0:018b HP, Inc HyperX Cloud II Wireless

HP acquired HyperX in 2021. Your headset must be manufactured after that acquisition date, ours would be before. There shouldn't be anything different other than the vendor ID/product ID. However, I would test the hidapitester mentioned above to make sure the byte readings are the same at the txt I submitted.

I will get my ID's and upload them here

[ISAndreiva]

I would help contribute too I have the ID's for the Cloud 2 Wireless from Linux I tried changing the ID's on the cloud_flights files but I think that is not as easy.

My Cloud II has a different ID: Bus 001 Device 002: ID 03f0:018b HP, Inc HyperX Cloud II Wireless

HP acquired HyperX in 2021. Your headset must be manufactured after that acquisition date, ours would be before. There shouldn't be anything different other than the vendor ID/product ID. However, I would test the hidapitester mentioned above to make sure the byte readings are the same at the txt I submitted.

I didn't think it'd change anything, just mentioning it for compatibility with both versions.
Either way I also tested the ids here HID-OUTPUT-HYPERX-CLOUDII-WIRELESS-HP-EDITION.txt.

[LennardKittner]

Using Wireshark, I was able to identify the specific packet required to be sent to the headset to obtain the battery level. Additionally, I learned how to properly interpret the response, which differs from that of the HyperX Cloud Flight.

Packet to get battery level:
[0x06, 0xff, 0xbb, 0x02, 0x0, 0x0, 0x0, 0x0]
The response has a length of eight and the last byte is the battery level.

Using this information I have implemented my own system tray application https://github.com/LennardKittner/HyperXCloudIIWireless.