Repository navigation
Beyerdynamic MMX 230 #535
Description
Hello,
I would like to request support for the new Beyerdynamic MMX 230 wireless headset.
Here are the hardware identifiers from the Windows Device Manager (probably the Audio endpoint):
- Vendor ID (VID): 2E50
- Product ID (PID): 003A
Connection type: Wireless USB Dongle.
Currently, running headsetcontrol -b returns No supported device found.
Running ./headsetcontrol.exe --dev -- --list --device 2E50:003A returns completely blank (no output in terminal).
Important note: I wanted to provide Wireshark logs, but there is absolutely no official Beyerdynamic software for this headset yet. Windows uses a generic USB audio driver, and even the official Beyerdynamic Update Hub currently stops at the MMX 200 model and does not detect the MMX 230.
Therefore, there is no software polling the headset to generate USB traffic for me to sniff.
Could you guide me on how to find the correct HID endpoint IDs, or are there any standard Beyerdynamic commands I could try to fuzz via the dev menu?
Thank you!
Activity
github-actions commentedon Jun 29, 2026
Thank you for requesting support for a new headset!
To implement support for a specific headset, we need to reverse-engineer and test on that device. Only people who own the headset can implement support for it.
Want to help?
See ADDING_A_DEVICE.md for detailed instructions.
MorganWOODs3 commentedon Jun 29, 2026
Hello, thanks for the automated reply!
I am completely willing to implement support for this device myself and open a PR. However, I am stuck on step 2 (Wireshark capture).
As I mentioned in the description, there is no official companion software on PC for the MMX 230 yet (it doesn't even show up in the official Beyerdynamic Update Hub). Because of this, there is absolutely zero existing USB traffic to capture with Wireshark, as no software is polling the headset.
Since I have a background in software development and cybersecurity, I'm perfectly comfortable writing a custom fuzzer (e.g., in C# or Python) to blindly probe the HID endpoints and see how the headset reacts.
Before I start brute-forcing it, do you have any documented generic Beyerdynamic payloads (like standard battery polling byte sequences from the MMX 200 or others) that I should try injecting first? Any pointers on the expected payload structure would be a huge time saver!