If you see amp;, the hardware ID is corrupted in the registry only if the string was manually entered — but hardware IDs are read from the device’s firmware, so the corruption is in your documentation, not the system.
echo 'SUBSYSTEM=="usb", ATTRSidVendor=="1ea7", ATTRSidProduct=="0066", MODE="0666", GROUP="plugdev"' | sudo tee /etc/udev/rules.d/50-hid-1ea7.rules sudo udevadm control --reload-rules sudo udevadm trigger
For evdev debugging:
sudo evtest
# Look for /dev/input/event* with this VID/PID
Sharkoon is a German manufacturer of PC peripherals. The PID 0066 corresponds to the:
Your original keyword:
hid vid-1ea7 amp-pid-0066 amp-rev-0200 amp-mi-00 hid vid-1ea7 amp-pid-0066 amp-rev-0200 amp-mi-00
This is not a valid hardware ID. It contains amp; — an HTML entity for &.
Correct ID should be:
HID\VID_1EA7&PID_0066&REV_0200&MI_00
Where did the corruption come from?
Fix: Replace every amp- with & and change dashes to underscores after VID, PID, etc.
If you’re building a custom audio controller or want to disable the obnoxious blinking LEDs without installing proprietary Windows software, MI-00 is your gateway. You can write a simple Python script using pyusb or hidapi to claim only that interface and send raw commands. If you see amp; , the hardware ID
"The device, identified by the Vendor ID (VID) 1EA7 and Product ID (PID) 0066, with a revision of 0200 and an interface identifier (MI) of 00, is designed to [briefly describe the device's function or purpose]. Detailed specifications and operational guidelines are provided below [or in the document]."