Case study

Giving a vendor-unsupported keypad a native Linux workflow

Built a Linux driver and local React configuration app for the Huion Keydial Mini K20, remapping all 18 keys and its dial over Bluetooth or USB.

Stack
  • Python
  • Linux evdev/uinput
  • React
  • WebSocket

  1. Situation

    The K20 presented fixed keyboard input and had no useful Linux configuration path. Using it as a programmable creative-workflow controller required both an input-layer driver and a way to configure it without editing files by hand.

  2. Constraints

    The same path had to work over Bluetooth and USB, suppress the original keystrokes, preserve user-level security, update mappings without service restarts, and remain understandable to people who did not want to operate a driver from the terminal.

  3. Decision

    Grab the device through Linux evdev, emit chosen actions through uinput, run the driver as a user service, persist profiles as YAML, and expose the same behavior through a CLI, local HTTP/WebSocket API, and React/Vite interface.

  4. Tradeoff

    The result is Linux-specific and presently alpha software maintained by one person. Installation still requires one-time device-access and service setup, and command execution is constrained rather than delegated to an arbitrary shell.

  5. Outcome

    The public MIT-licensed implementation supports all 18 buttons and the dial, shortcuts, multi-step macros, application launch, profile switching, live input feedback, Bluetooth and USB operation, CLI control, and visual configuration.

  6. Retrospective

    Separating hardware input, action mapping, and configuration behind a local service made the driver usable from more than one interface. Broader hardware support and simpler packaging are still open.

Detail

Keydial Commander is public source under the MIT license. Its architecture keeps device access, action mapping, and presentation separate: the driver owns the hardware path, the local service owns profiles and live updates, and the CLI and web interface are two clients of the same capability.

Keydial Commander, from the keypad to its three interfaces.
Diagram as text

Parts

  • Keydial Mini K20: 18 keys and a dial
  • Hardware path
    • Linux evdev: grabs the device
    • Driver: runs as a user service
    • Linux uinput: emits the chosen actions
  • Local service: profiles (YAML) and live updates
  • Same behavior
    • CLI
    • Local API: HTTP/WebSocket
    • Web interface: React/Vite

Connections

  • Keydial Mini K20 Linux evdev (Bluetooth or USB)
  • Linux evdev Driver
  • Driver Linux uinput
  • Local service Driver (live updates)
  • CLI Local service
  • Local API Local service
  • Web interface Local service
Editing key 6 in Keydial Commander: the key is highlighted on the device drawing, and the side panel sets it to send the shortcut Left Ctrl + S, with a hold option and Test-fire, Clear and Save buttons.
Keydial Commander’s configuration app.

That boundary is what turns a one-off input hack into a maintainable tool. Linux is the supported platform, and packaging is still evolving.

Next case study: Turning one product’s knowledge into answers for product, QA, and developers

Get in touch All case studies