Dictation Dongle

For IT

IT approval pack for the Dictation Dongle. Applies to the production firmware. Last updated 21 November 2026.

The Dictation Dongle is a USB keyboard that types what its owner dictates on their iPhone. This page tells you exactly what it presents to a computer, what it can and cannot do, and how to allow it if your policies would otherwise stop it. We do not claim it will get past your controls: whether it is allowed is your decision, and asking you first is the route we tell our users to take.

Download IT approval pack (PDF, 1 page)

What it is

An app on the iPhone turns speech into text with Apple’s on-device speech recognition. Audio never leaves the phone. The app sends the finished text over an encrypted, bonded Bluetooth LE link to the dongle, a Seeed Studio XIAO ESP32-S3 board. The dongle types the text into whatever field has the cursor, at about 70 characters per second.

The computer needs no driver or software. It sees an ordinary keyboard.

What the computer sees

The production firmware presents exactly one USB device with one interface: a keyboard.

InterfaceOne HID interface: class 03, subclass 01 (boot), protocol 01 (keyboard). The device descriptor has class 0, so the class comes from the interface.
Nothing elseNo serial (CDC) port, mass storage, audio, vendor-defined or other interface.
Vendor ID0x2886 (decimal 10374)
Product ID0x0056 (decimal 86)
Manufacturer stringesp32-dictation-keyboard
Product stringDictation Keyboard
Serial numberUnique per unit: 12 upper-case hex digits taken from the chip’s factory-programmed ID (its base MAC address), for example 7CDFA1001234. It does not change when the dongle is replugged.

The VID and PID are the Seeed XIAO ESP32-S3 board’s own IDs, not a dedicated product ID. Any XIAO ESP32-S3 can enumerate with them, so an allow rule on VID and PID alone also admits other boards of that type. To approve only the units your staff actually own, pin the rule to each unit’s serial number, as the steps below show.

To check a unit yourself on a Mac: ioreg -p IOUSB -l -w0 | grep -B2 -A25 "Dictation Keyboard", or Apple menu → System Information → USB. On Linux: lsusb -v -d 2886:0056. On Windows, Device Manager shows one “HID Keyboard Device” and no Ports (COM & LPT) entry.

What it is not

It is not a mouse jiggler and not a macro or keystroke-injection device.

Threat model

What it cannot do

How a phone gets trusted

What remains

Allow-list steps

Most endpoint tools do not block a new keyboard by default. These steps are for estates that do. Test on one machine before rolling out, and read the IDs from a real unit first.

Windows: Group Policy (device installation restrictions)

This only matters if your estate blocks device installation, for example with “Prevent installation of devices not described by other policy settings” or a prevent rule by device setup class. Under Computer Configuration → Administrative Templates → System → Device Installation → Device Installation Restrictions:

  1. Enable Allow installation of devices that match any of these device IDs and add both device nodes the dongle creates, the USB device and the keyboard under it:
    USB\VID_2886&PID_0056
    HID\VID_2886&PID_0056
  2. Enable Apply layered order of evaluation for Allow and Prevent device installation policies across all device match criteria. Without it, every Prevent rule beats every Allow rule. With it, more specific rules win: device instance IDs > device IDs > device setup class > removable devices.
  3. To approve single units only, use Allow installation of devices that match any of these device instance IDs instead, with the unit’s USB instance ID, USB\VID_2886&PID_0056\<serial>, plus the instance ID of the keyboard node under it. Read both from Device Manager on a test machine: the device → Properties → Details → Device instance path, or run pnputil /enum-devices /ids.

Microsoft notes that a default-deny policy must also allow the USB hubs and controllers a keyboard connects through, or users can lose their keyboards and mice altogether. Check the exact hardware IDs of a unit in Device Manager (Details → Hardware Ids) before you deploy.

Windows: Intune

Set the same two policies with the DeviceInstallation policy CSP, as custom OMA-URI settings of type String:

OMA-URI: ./Device/Vendor/MSFT/Policy/Config/DeviceInstallation/AllowInstallationOfMatchingDeviceIDs
Value:   <enabled/><data id="DeviceInstall_IDs_Allow_List" value="1&#xF000;USB\VID_2886&amp;PID_0056&#xF000;2&#xF000;HID\VID_2886&amp;PID_0056"/>

OMA-URI: ./Device/Vendor/MSFT/Policy/Config/DeviceInstallation/EnableInstallationPolicyLayering
Value:   <enabled/><data id="AllowDenyLayered" value="1"/>

&#xF000; separates the numbered entries and &amp; is an escaped &. Microsoft recommends the layered-order policy over “Prevent installation of devices not described by other policy settings”; if both are on, the layered order applies and the other is ignored. Applies to Windows 10 and 11 Pro, Enterprise and Education.

Microsoft Defender for Endpoint

Usually nothing to do. Defender device control on Windows only restricts portable devices, removable media, CD/DVDs and printers, and on macOS only removable media, Apple devices, portable devices and Bluetooth media. A USB keyboard is none of these.

CrowdStrike Falcon Device Control

Falcon’s USB classes are ANY, AUDIO_VIDEO, IMAGING, MASS_STORAGE, MOBILE, PRINTER and WIRELESS; there is no separate keyboard class. If the dongle shows as blocked in Device Control activity, add a FULL_ACCESS exception to the class the event reports, in the policy that applies to the user’s host group. Falcon writes vendor and product IDs in decimal, and its combined ID is <vendor ID>_<product ID>_<serial number>:

Vendor ID:   10374        (0x2886)
Product ID:  86           (0x0056)
Serial:      <the unit's 12 hex digits>
Combined ID: 10374_86_<serial>

Pinning the serial keeps the exception to that one unit. Falcon may also report the dongle as a newly seen USB device even when nothing blocks it.

macOS

Citrix and other virtual desktops

Keep the dongle plugged into the local machine or thin client and do not redirect it. It then types into the session like the local keyboard.

Ask before you plug it in

For people who want to use a Dictation Dongle on a work computer:

  1. Ask IT first. Many workplaces forbid unapproved USB devices, and plugging one in without asking can breach that policy even if nothing blocks it. Security tools may log a new keyboard and someone may ask what it is.
  2. Send them this page or the one-page PDF, with the email below. If you need it as a workplace adjustment, say so: many organisations have a process for assistive technology.
  3. Wait for a yes before you plug it in. If they need the serial number, you can read it on a personal Mac: Apple menu → System Information → USB → Dictation Keyboard.
  4. If they say no, that is their call. Do not try to work around it.

Template email to IT

Subject: Approval request: Dictation Dongle (USB keyboard)

Hi,

I would like to use a Dictation Dongle with my work computer, and I am asking for approval before I plug it in. [Optional: I am asking for it as a workplace adjustment because ...]

What it is: a small USB keyboard. I dictate on my iPhone, the phone turns my speech into text on the phone itself, and the text goes over an encrypted Bluetooth link to the dongle, which types it where my cursor is. Audio never leaves my phone.

What the computer sees: one USB HID keyboard (class 03/01/01) and nothing else, vendor ID 0x2886, product ID 0x0056, product name "Dictation Keyboard", serial number [serial, if known]. It has no storage and no network access, it accepts no commands from the computer, and it is not a mouse jiggler or macro device: it types only what I dictate.

The attached one-page IT approval pack has the full details, a threat model and allow-list steps for Windows (Group Policy and Intune), CrowdStrike and macOS.

Could you let me know whether I can use it, and whether you need anything else from me?

Thanks,
[Name]

Sources

Device facts come from the project’s firmware and README: USB identity in firmware/lib/dictation_core/src/usb_identity.h, USB and Bluetooth set-up in firmware/src/main.cpp, key tables in firmware/lib/dictation_core/src/keymap.cpp, Bluetooth firmware updates in firmware/src/ota_service.cpp. Allow-list steps were checked against vendor documentation on 21 November 2026:

Nothing here has been tested against your configuration. Vendor behaviour changes; check the current documentation for your version.