Proprietary device drivers, dedicated applications, and their ilk are the bane of the open-cording the “secret” USB transactions as they go over the wire, we’d have a chance
[Emir Mrkaljević]’s tool,
usb-rea mark -m lamp.pcapng.actions.json ” brightness then click it in the vendor app usb-rea mark lamp.pcapng.actions.json …repeat for values per setting capture stop report lamp.pcapng report.md scaffold lamp_driver.py dissector lamp.lua wireshark same protocol>
Usb-rea records all the USB traffic, timestamps it relative to your actions, and gives you a report, a driver, and a Wireshark protocol dissector out the back side. There is even an MCP file so that you can hand off the grunt work to the bots, possibly enabling this to work closed-loop?
Of course, you don’t want to reinvent the wheel, so it’s fun to see that there’s also a usb-rea lookup command to see if your VID:PID is already in the dataset. Most of the devices are CPU coolers, RGB controllers, and other blinged-out computer peripherals, but we imagine that it’s a lot more broadly applicable. We looked for our mouse on the list, but it’s sadly not there.
Usb-rea is not a silver bullet to bring back abandoned peripherals from the grave, because you still need to run the proprietary driver during the recording. But if you get ahead of the game and document the protocols before the manufacturers abandon them, you stand a chance. Get recording!


