Hid Vid-1ea7 Amp-pid-0066 Amp-rev-0200 Amp-mi-00 2021 💫

Understanding the "HID VID-1EA7 AMP-PID-0066" Device Identity

If you are digging through your Windows Device Manager or looking at a system log and stumbled upon the string HID VID-1EA7 AMP-PID-0066&REV-0200&MI-00, you are looking at the specific DNA of a hardware peripheral.

While these alphanumeric codes look like gibberish, they provide a roadmap for your operating system to identify, communicate with, and find drivers for your hardware. Breaking Down the Hardware ID

Hardware IDs are hierarchical strings. Let’s dissect the one you have:

HID: Stands for Human Interface Device. This is a broad class of hardware that interacts directly with humans, such as keyboards, mice, game controllers, or drawing tablets.

VID-1EA7: This is the Vendor ID. The code 1EA7 is assigned to SHARKOON Technologies GmbH. Sharkoon is a well-known German manufacturer of PC components and peripherals, particularly popular in the gaming community.

PID-0066: This is the Product ID. In the Sharkoon ecosystem, 0066 typically identifies a specific model of gaming mouse or keyboard (often associated with the Sharkoon Drakonia series or similar optical gaming mice).

REV-0200: This indicates the Revision number of the hardware firmware (v2.0).

MI-00: This stands for Multiple Interface 00. It means the device is composite (it might have a mouse function, a keyboard function for macro keys, and lighting control all in one USB plug). Why is this appearing in your Device Manager?

Usually, users go looking for this ID for one of three reasons:

The "Unknown Device" Yellow Triangle: Windows knows something is plugged in but doesn't have the specific driver to make it work.

Ghosting/Lag: The device is working, but without the specific manufacturer software, you can't customize the DPI, RGB lighting, or macros.

Troubleshooting Crashes: A system log might have flagged this specific ID as the source of a driver conflict. How to Install the Correct Drivers

Since this ID points toward Sharkoon Technologies, the best way to resolve any issues is to go directly to the source.

Identify the Physical Product: Look at the bottom of your mouse or keyboard. Look for a model name like Drakonia, Skiller, or Light².

Visit the Sharkoon Support Page: Go to the official Sharkoon website and navigate to the "Download" or "Support" section. hid vid-1ea7 amp-pid-0066 amp-rev-0200 amp-mi-00

Search by Model: Enter your product name. Download the latest "Software" or "Driver" package for Windows.

Manual Update: If the installer doesn't work, go to Device Manager, right-click the device with the ID VID-1EA7, select Update Driver, and point it to the folder where you extracted the Sharkoon files. Common Issues and Fixes

Device Disconnecting: If you see this HID string appearing and disappearing in your logs, try disabling "USB Selective Suspend" in your Windows Power Options.

Driver Conflict: If you previously used Razer or Logitech software, their drivers can sometimes conflict with Sharkoon's "MI-00" (Multiple Interface) configuration. Uninstalling old peripheral software often solves the issue.

By identifying the VID 1EA7 as Sharkoon, you’ve done the hard part. Simply installing their specific configuration software should unlock the full features of your hardware and clear up any "Unknown Device" errors.

Are you experiencing a specific error message or malfunction with this device that I can help you troubleshoot further?

This is a specific USB identifier pairing:

VID = 1ea7 (Liangcheng (SHENZHEN) Electronics / sometimes associated with 2.4GHz wireless input devices)
PID = 0066
Revision (Rev) = 0200
MI (Interface Number) = 00

That combination likely corresponds to a wireless mouse/keyboard combo receiver or a generic HID input device (like a presenter, barcode scanner, or gamepad).

Below is useful content depending on your role.

6. For Developers: Parsing This String Correctly

If you encounter strings like this in user support tickets or logs:

import re
broken = "hid vid-1ea7 amp-pid-0066 amp-rev-0200 amp-mi-00"
# Step 1: replace 'amp-' with '&'
fixed = broken.replace("amp-", "&")
# Step 2: Normalize format
fixed = re.sub(r'(\bvid|pid|rev|mi)-', r'\1_', fixed, flags=re.I)
print(fixed)  # hid vid_1EA7&pid_0066&rev_0200&mi_00
# Step 3: Prepend HID\ and uppercase
hardware_id = "HID\\" + fixed[4:].upper()
print(hardware_id)  # HID\VID_1EA7&PID_0066&REV_0200&MI_00

This restores the valid Windows hardware ID.

What is `mi-00`?

The mi-00 stands for Interface 0 on a composite USB device. This device doesn't just do one thing—it has multiple logical functions running over a single USB cable.

Running lsusb -t showed this topology:

Bus 001 Device 004: ID 1ea7:0066 SHARKOON GmbH
└─ Interface 00 (MI-00): Human Interface Device (HID) – Controls
└─ Interface 01 (MI-01): Audio Control (volume, mute)
└─ Interface 02 (MI-02): Audio Streaming (microphone input)
└─ Interface 03 (MI-03): Audio Streaming (speaker output)

So, MI-00 is not audio—it's the control interface. It handles:

LED toggles (RGB modes on the ear cups)
Virtual surround sound enable/disable
Side-tone (mic monitoring) on/off

Known issues with this VID/PID combination:

Virtual 7.1 sound on MI-00 is just DSP reverb – not true surround.
On some motherboards (AMD B550 chipset), the headset will occasionally re-enumerate, shifting MI-00 to MI-03. A powered USB hub fixes this.
The rev 0200 firmware adds a 500ms delay before initializing the mic; don’t panic if arecord shows silence for half a second.

Update: If you’re seeing amp-mi-00 in your logs and nothing else, you might have a partial USB descriptor corruption. Try: VID = 1ea7 (Liangcheng (SHENZHEN) Electronics / sometimes

echo '1ea7 0066' | sudo tee /sys/bus/usb/drivers/usb/new_id

Then replug the device.

Would love to hear if anyone has decoded the full HID report set for MI-00—especially the command to disable the "beep" on mute toggle.

Hardware: SHARKOON Skiller SGH1 (Rev 0200)
Kernel tested: 6.1.52
Windows driver version: 2.1.0.8 (2023)

The hardware string hid vid-1ea7 amp-pid-0066 identifies the Sharkoon Mediatrack Edge Mini Keyboard

. This device is a compact, wireless multimedia keyboard designed for HTPCs (Home Theater PCs), smart TVs, and mobile setups. Sharkoon Mediatrack Edge Mini Keyboard Sharkoon Mediatrack Edge Mini Keyboard

is a specialized input solution for users who need full keyboard and mouse functionality in a handheld, remote-sized form factor. Design and Portability Ultra-Compact Form Factor

: Designed to be held with two hands, similar to a game controller, making it ideal for navigating media interfaces from a couch. Integrated Touchpad

: Includes a small built-in touchpad on the right side, allowing for mouse cursor control without needing a flat surface. Multimedia Keys

: Features dedicated buttons for volume control, playback, and home shortcuts, which are highly useful for streaming applications. Performance and Connectivity Plug-and-Play Compatibility : Identifies as a standard HID (Human Interface Device)

. It works seamlessly across Windows and most Linux distributions (like Fedora or Mint) without requiring proprietary drivers. Wireless Range

: Uses a 2.4 GHz USB nano-receiver, providing a stable connection for living room distances. Typing Experience

: While suitable for entering search terms or URLs, the small, membrane-style keys are not intended for long-form typing or office work. Technical Specifications Vendor ID (VID) (SHARKOON Technologies GmbH) Product ID (PID) : USB HID (via 2.4 GHz wireless dongle) Wifi Issues with all most recent releases of Linux

Audio: Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor HD Audio vendor: Dell driver: snd_hda_intel v: kernel bus-ID: 00:03. Fedora Discussion SHARKOON Technologies GmbH — USB Vendor 1EA7

How to Find Vendor ID and Product ID for Your USB Device - Acroname Inc Sending a report (e.g.

Step 4: Fix Interface 0 (MI-00) Failures

MI-00 is the main input interface. If it fails, the device may be stuck in a bootloader or firmware update mode. Try:

Hold the Start + Select + Home buttons for 5 seconds (many generic gamepads use this to reset).
Unplug, wait 30 sec, replug into a different USB port (preferably USB 2.0).
Use USB Device Tree Viewer → select the device → click “Restart device” (restarting the USB stack).

Linux

Works out of the box with hid-generic driver. Use evtest to see input events:

sudo evtest

Look for “1ea7:0066”. If not present, reload usbhid:

sudo modprobe -r usbhid && sudo modprobe usbhid

3. Where Would You See This String?

You are not supposed to see this in normal operation. However, you might encounter it in:

Windows Device Manager → Properties → Details → “Hardware Ids” or “Compatible Ids”
USB Device Tree Viewer or USBDeview
Linux → dmesg or lsusb -v
Driver installation logs (setupapi.dev.log)
OBS, JoyToKey, vJoy, or anti-cheat software logs (conflict detection)

If you see it under an “Unknown device” or with a yellow exclamation mark, the driver is missing or corrupted.

Summary

For the price point (usually around $50–$70 USD), the Fifine AM8 is arguably the best value microphone on the market. It punches above its weight class in audio quality and offers flexibility that competitors lack.

Pros:

Great sound rejection (blocks background noise).
USB and XLR connectivity.
Stylish RGB design.
Touch mute button.

Cons:

Included stand transmits desk noise.
Requires getting close to the mic (2–4 inches) for best sound.

It is highly unusual to encounter a string like hid vid-1ea7 amp-pid-0066 amp-rev-0200 amp-mi-00 as a natural keyword for an article. This string contains technical identifiers that appear to be a concatenation of USB device descriptors mixed with an amp; (HTML/XML entity for ampersand) artifact.

After analysis, this string likely originates from a USB device hardware ID — specifically VID_1EA7&PID_0066&REV_0200&MI_00 — that was corrupted when pasted from a system log, a website URL, or a browser’s developer console. The amp; fragments suggest the & symbols were HTML-encoded.

Let’s break down what this hardware ID means, why it appears, and how to resolve related driver or device recognition issues.

Observations & Quirks

Driver behavior: On Windows, the generic USB Audio 2.0 driver works, but the "SHARKOON Gaming Audio" driver is needed to expose MI-00’s HID reports for the LED button. On Linux, snd-usb-audio grabs MI-01–03, but MI-00 remains unclaimed unless you write a small HIDRAW utility.
Rev 0200 vs older firmware: I’ve seen older reports of rev 0100 on the same PID. Rev 0200 seems to fix a nasty bug where the microphone would enter a low-power state and never wake up after system suspend. Check your dmesg—if you see usb 1-2: reset full-speed USB device number 4 after resume, you have the fixed version.
Intercepting MI-00: Using usbhid-dump on the interface:
```
sudo usbhid-dump -m 1ea7:0066 -i 0
```
Sending a report (e.g., to toggle RGB) requires reverse engineering the HID report descriptor. So far, report ID 0x03 length 4 bytes seems to control lighting:
- 03 01 00 00 = Red
- 03 02 00 00 = Green
- 03 03 00 00 = Blue