MuteMe · Setup & support
MuteMe Original and Mini HID reference
Use the documented USB identifiers, LED values and touch events when developing an integration for the listed Original and Mini hardware.
- Scope
- Original batches 001–009 / Mini
- Protocol
- Custom HID reports
Match the documented device
| Name | VID | PID |
|---|---|---|
| MuteMe Original (prototypes) | 0x16c0 | 0x27db |
| MuteMe Original (production) | 0x20a0 | 0x42da |
| MuteMe Mini (production) | 0x20a0 | 0x42db |
| MuteMe Original (Batch 009 and later) | 0x3603 | 0x0001 |
| MuteMe Mini USB C | 0x3603 | 0x0002 |
| MuteMe Mini USB A | 0x3603 | 0x0003 |
| MuteMe Mini (Generic) | 0x3603 | 0x0004 |
These identifiers identify a device family, not a safe firmware file. Match the physical model and batch before any firmware operation. MuteSync uses a different serial protocol; this table is not a MuteSync, Click or Signal protocol specification.
Set the LED color and effect
| Color | Value |
|---|---|
| Off | 0x00 |
| Red | 0x01 |
| Green | 0x02 |
| Yellow | 0x03 |
| Blue | 0x04 |
| Purple | 0x05 |
| Cyan | 0x06 |
| White | 0x07 |
| Effect | Add to the base color |
|---|---|
| Bright / steady | 0x00 |
| Dim | 0x10 |
| Fast pulse | 0x20 |
| Slow pulse | 0x30 |
For example, red 0x01 plus slow pulse 0x30 gives 0x31. These are values inside the custom report, not keyboard key codes or a complete operating-system write command. Report framing depends on the controller/API you use.
Read touch events
| Event | Value |
|---|---|
| Clear | 0x00 |
| Touching | 0x01 |
| End touch | 0x02 |
| Start touch | 0x04 |
The released legacy controller treats 0x01 or 0x04 as the start of a press. The newer Original and Mini controllers use 0x04 for start and 0x02 for end, ignoring idle/continuing values. Track press start and end separately for push-to-talk or push-to-mute behavior.
USB and firmware generations
The original hardware reference describes batches 001–003 as USB 1.1 and batches 004 onward as USB 2.0. Historical low-speed firmware variants were offered for particular connection problems; use a variant only when Support confirms it for your device. A faster USB revision is not a guarantee for every hub or cable.
Historical batch reference
| Generation | Batch | Details | Release |
|---|---|---|---|
| Gen 0 | Prototype | Handmade, 3D Printed, Various Configurations | Oct 2020 |
| Gen 0 | Batch 000 | Manufactured, MicroUSB, Pre-Production | Dec 2020 |
| Gen 1 | Batch 001 | Introduced USB-C / Better Illumination | Feb 2021 |
| Gen 1 | Batch 002 | Fixed USB Cable Support For High-End Cables | Apr 2021 |
| Gen 1 | Batch 003 | Fixed Issues with Internal LEDs, Sleep Modes | Jul 2021 |
| Gen 2 | Batch 004 | Better USB Module for Compatibility (USB 2.0) | Oct 2021 |
| Gen 2 | Batch 005 | Testing New Touch Sensor | Oct 2021 |
| Gen 3 | Batch 006 | Testing Software Touch Sensor (Faster) | Oct 2021 |
| Gen 3 | Batch 007 | Ultra-Fast Touch Response, Faster Device | Apr 2022 |
| Gen 3 | Batch 008 | No Change from Batch 007 | Mar 2023 |
| Gen 3 | Batch 009 | Increased Weight, Firmware Changes | Feb 2024 |
For an implementation question, email support@muteme.com with the device identifiers, batch, operating system and HID library.
We’re here to help
Still need a hand?
The best way to contact us is through the Support tab in the MuteMe app. Include your device, operating system, app version and what you have already tried.