OpenMouse Adds Open-Source Keyboard Customization for Logitech, Razer, Wooting, and SteelSeries in Beta

It recognized the keyboard. Then it stumbled.
OpenMouse's beta connected to a Wooting 80HE but failed to load its keymap or adjust settings.
Mark

So what actually happened here? OpenMouse started out as a mouse tool, right?

Mimi

Right. It's an open-source alternative to manufacturer config software. The new beta adds keyboards from Logitech, Razer, SteelSeries, and Wooting, announced on the project's Discord.

Mark

Does it work?

Luke

Barely, by the one test we have. A brief test with a Wooting 80HE connected fine but failed to load the right keymap and failed to adjust settings. That's a single board and a short test, so I wouldn't generalize to the other brands.

Mimi

And the feature list is the promising part. Adjustable actuation, rapid trigger, toggle key, mod tap, SOCD, DKS, plus RGB, layers, and profiles.

Luke

Careful, though. Those are planned features. The report says the set appears competitive, not that it's working.

Mark

What's missing?

Mimi

Key remapping. For a keyboard tool, that's a conspicuous hole.

Mark

And the Bridge app?

Mimi

It lets users make per-game profiles for compatible mice now. The same is expected for keyboards eventually.

Luke

"Eventually" is carrying a lot there. No date for leaving beta either, and Wuque Studio and Kochi Hummingbird 68 support is only described as in development.

Mark

One commenter said lighter tools should be the default.

Luke

That's an opinion, and the claim about a similar single-brand project was hedged by the commenter themselves. Nothing here shows OpenMouse is lighter than vendor software.

  • A Wooting 80HE connects instantly, but the app stumbles the moment it tries to load its keymap and apply settings.
  • Keyboard support from Logitech, Razer, SteelSeries, and Wooting has arrived in beta, while two more boards are reportedly in development.
  • Key remapping is still missing, a notable gap in a tool meant to replace first-party configuration software.
  • The developers are asking gamers to test the beta on real hardware, betting that community feedback will speed the route out of beta.
  • No release date has been set, and the planned rapid trigger, SOCD, and DKS features remain promises until the basics work.

Somewhere between a plugged-in keyboard that is recognized at once and a settings screen that will not quite obey, the open-source OpenMouse project is reaching for a corner of gaming hardware it has not yet mastered. Its developers, long known for mice, have opened a beta that speaks to keyboards from four major makers, a small step in a familiar story: community tools quietly trying to match the vendor software that ships in the box. The ambition is visible in the planned feature list, while the present reality is a tool that can see the hardware but cannot yet shape it.

In a brief hands-on test, OpenMouse recognized a Wooting 80HE keyboard as soon as it was plugged in, and then it faltered. It could not load the correct keymap or adjust the board's settings properly. That is the honest state of the project's newest beta, and it shows how far keyboard support has come and how far it still has to go.

OpenMouse is an open-source, community-driven alternative to the configuration software that gaming hardware makers ship with their products. It has long been known for handling many gaming mice. Its developers had hinted at keyboard work, and this beta, announced on the project's Discord, is the result. It adds support for keyboards from Logitech, Razer, SteelSeries, and Wooting, with early work reportedly underway for two more boards.

The planned list is ambitious, matching much of what proprietary tools offer, including Hall effect features such as rapid trigger, SOCD, and DKS. Layers, profiles, and robust RGB are also on the roadmap. But key remapping is absent for now, and per-game profiles for keyboards remain unconfirmed.

There is no timeline for leaving beta. The team is asking gamers to test the release, which makes community feedback on real hardware the likeliest path forward. The thing to watch is whether the keymap and settings problems get fixed, and whether remapping joins the list before the beta ends.

In a brief hands-on test, OpenMouse recognized a Wooting 80HE keyboard as soon as it was plugged in. Then it stumbled. The app could not load the correct keymap, and it could not adjust the board's settings properly. That is where the project's newest beta stands, and it is the clearest picture available of how far its keyboard support has come.

OpenMouse is an open-source, community-driven alternative to the configuration software that gaming hardware makers ship with their products. Until now it has been known for handling a wide range of gaming mice. Not long ago, its developers said they were working on keyboard customization too. The latest beta release is the result, and the news came through an announcement on the project's Discord server.

The beta adds support for a number of gaming keyboards from four manufacturers: Logitech, Razer, SteelSeries, and Wooting. Initial support also appears to be in development for two further boards, one from Wuque Studio and the Kochi Hummingbird 68.

Actual feature support is limited so far, and the implementation is clearly still a beta. The Wooting 80HE test showed the connection working but the more practical functions not yet doing their jobs.

The planned feature list is ambitious, though. It appears to match what most proprietary keyboard tools offer, including the features built around Hall effect switches: adjustable actuation, rapid trigger, toggle key, mod tap, SOCD, and DKS. Robust RGB customization is also planned, along with support for layers and profiles.

One notable gap is the ability to remap keys, which is absent for now.

The release also touches on per-game profiles. OpenMouse now lets users install a companion app called Bridge to create custom per-game profiles for compatible gaming mice. It appears the same functionality will eventually reach supported keyboards, though nothing firm has been stated.

There is no timeline for when keyboard support will leave beta. The development team has asked gamers to join the beta test, which suggests the fastest route to a working release is community feedback on real hardware.

A reader comment on the original report raised a related point. Chaitanya recalled a similar project, possibly called OpenLogi, that covers a single manufacturer, and argued that if such tools are lighter than first-party software, they should become the default for more users. That is one reader's view and an uncertain recollection, not something the report confirms.

For now, the thing to watch is whether the Wooting keymap and settings problems get fixed, and whether key remapping joins the feature list before the beta ends.

If these tools are lighter than first-party software, they should be the default for more users.
— Chaitanya, reader comment (paraphrased)
Contact Us FAQ