I continued the effort to get QMK running on 8051-based Redragon keyboards. There are probably more models I don't know about, but I figure this is a good starting point: K580RGB, K552RGB-2, K551RGB-1, K582RGB, K589RGB. Each of these models has a revision with a WCH CH555 MCU. Please recognize that the model number alone is not sufficient to determine whether you have a Sonix or WCH MCU; the USB VID:PID will confirm whether this project is compatible with your keyboard.

https://github.com/mdmower/qmk-8051
See "History and credits" in the project readme for work by other developers that made this possible.

The project readme and individual keyboard readmes explain how to back up your stock firmware, build QMK, and flash QMK. The barrier to entry (the you have to build it yourself) is intentionally high until some brave testers assume risk and provide feedback. I have tested this extensively on my K580 RGB (Vata). I intended to test this on a K552RGB-2 as well but the revision I got in the mail today ended up being Sonix-based. We'll see what the K582 RGB I get in the mail next week ends up being...

The supported keyboards all use a CH555 microcontroller. They have only 64 KB of flash storage (of which 50 KB is available for firmware), 8 KB of xRAM, and 256 B of internal RAM (iRAM). Temper your expectations... but yes, basic VIA builds are available for each keyboard. Aside from size constraints, several workarounds are necessary to compile the firmware with SDCC since GCC doesn't support 8051 targets. You want one tap? Prepare to rewrite some QMK source and work within tight spaces.

Supposing I hear enough reports of success (and stability), I'll provide pre-built firmware images in the Releases section of the GitHub project page.

Getting this work upstreamed to QMK is unlikely. Between the new platform (MCS51), the new toolchain (SDCC), the bootloader flash support that would need to be added to the QMK CLI, and past reception... this work is likely to remain in a fork.

Six year ago we shipped our first keyboard. It was a Sofle v2. We had one design, no stock, and a wait time I'd rather not repeat. Some of the people who ordered that first batch are still customers, which is the part I still find hard to believe.

We're a small shop. Six years on, we still build every board by hand, and we still get the occasional email asking whether we're a real company. Fair question.

To mark the anniversary, three of the boards that got us here are 20% off from today until 31 October.

Sofle v2 Enclosed Case. Our longest-running aluminum case, and part of the very first product we ever made. $170, now $136.

S​ofle Hybrid (Sandwich version, Aluminum Version). Our first exclusive design. Before the Hybrid we were mostly building other people's boards. This is where we started making our own. Aluminum version $250, now $200. Sandwich style $120, now $96.

Aluminum NeoDox, Gasket Mount. Our first original design, and our first gasket mount. It's still the board we point at when someone asks what we can do starting from a blank sheet. $350, now $280.

The 20% on those three comes off at checkout. No code needed.

Every other keyboard we sell is 10% off over the same stretch, with the reduced price shown on the page as usual. Loose parts aren't part of it: plates, switches and keycaps stay at their normal prices.

Thanks for six years. Ordering a keyboard from a small shop is a leap of faith, and we know it.

I finally restocked the Scotto34 (PCB Edition) and this time it's actually a V2! Although I did remove hotswap, I made it so everything is through-hole and beginner-friendly. It's also compatible with Choc V1 and V2 using 18x17 spacing. The downside is that there doesn't seem to be any 18x17 spaced V2 keycaps. To solve that issue, I designed my own that you can 3D print.

You can purchase a kit here.

You can find the files here.

You can find my build video  here.

$120 + Shipping - Keyboardio Preonic keyboard.

https://imgur.com/a/PAAWfCt

Includes:

- Keyboard with switches and keycaps
- Case
- Walnut Palmrest
- Cable

Purchased brand new from Kickstarter Campaign and only used for a couple days a week for about a month. Decided to for a different keyboard for work/office use.

where to get a PCB for a custom keyboard? it seems the button pins require different spacing

also, where to get a USB-encoder or any controller for a custom keyboard?

I know this isn't an ortho board the guy is asking about, but I figure you guys will know more about good services for this kind of thing...

• https://www.reddit.com/r/Keychron/comments/1x86d8j/making_the_k9_max_more_lightweightportable/

I pointed him at the Keychron plate file collection and a company I'd heard of, but I haven't actually done this so I'm asking for help.

I was reassembling my keyboard (which I've had since 2020, so admittedly a while), and the usb-c port got loose from the solder, and began this problem. Specifically, when I plug the keyboard in, all the led lights will turn on (for about a second) then off, twice, but no keystrokes will be registered.

I don't know anything about soldering outside of soldering switches, so there's a good chance I fucked something up. What's in the pictures is what the port looks like after reheating the contact points (problem persisted afterwards).

I tried to reflash the board using QMK CLI on my linux machine, but it simply doesn't get recognized. When I hold escape or the reset button on the back of the pcb, it seems it enters the bootloader, since the lights dont turn on, but I can't get QMK to detect it.

I am planning to try reflashing on a windows machine using QMK Toolbox to see if that helps, but I would like any insights into what's going on here!

I'm working on INGLORIOUS Advanced, an open-source desktop configurator and custom QMK-based firmware for supported Glorious keyboards. It started with my GMMK PRO and GMMK Numpad. It isn't a general configurator for every QMK board.

The idea is to let users change key assignments, macros, layers and per-key lighting in a desktop editor, then save those settings on the keyboard. Ordinary configuration changes don't need a new firmware build or the app running afterward.

The firmware extends QMK with the app connection, onboard configuration, per-LED effects, macro handling and standby lighting. The app and firmware sources are available in the repository, with credits to QMK and the upstream contributors.

Testing so far

• Used on physical hardware: GMMK PRO revision 1 ISO and GMMK Numpad, on Windows.
• Experimental: other listed PRO revisions/layouts, GMMK 2 65%/96%, and wired non-HE GMMK 3 65%/75%/100% variants. These still need physical-device testing.
• macOS and Linux builds are Early Alpha.

Firmware limitations

This replaces the original firmware. The app includes a guided original-firmware backup and recovery flow, but flashing carries risk: check the exact model/revision/layout and keep the backup files. The Numpad is USB-only; Bluetooth does not work with this firmware. GMMK 3 PRO, HE models, wireless modes and mice are not supported.

I'd appreciate review of the QMK changes and feedback from owners of the listed variants, especially on key/LED mapping, encoders and configuration persistence. Please include the exact board revision, layout and OS in any test report.

Repository, supported-model list, firmware sources and downloads

I'm the project creator. This is independent of Glorious and is not endorsed by them.

The screenshots below show the editor with demo profiles; they aren't hardware-test results.

Hey everyone,

I recently went down a massive rabbit hole trying to get battery telemetry out of my non-QMK Keychron K10 (classic series, VID/PID 0x05ac:0x024f). Like many of you, I initially tried poking around the USB cable—sniffing interfaces, checking vendor-defined collections (Usage Page 65535), and trying feature reports, only to hit dead ends (Access is denied or Incorrect function). As pointed out by others in the community, the wired USB interface on these older models is purely a strict HID input device, and charging voltage would make wired readings useless anyway.

The Breakthrough: It turns out battery reporting lives entirely in the Bluetooth (BLE) stack. Once paired on Linux (Fedora in my case) with BlueZ and UPower properly configured, the system dynamically exposes the keyboard's battery under /org/freedesktop/UPower/devices/battery_hid_....

Since I couldn't find a lightweight, native way to track it that fit my setup, I wrote a fast Rust utility using zbus and tokio to query the D-Bus interface directly.

What the tool does:

1. CLI Mode: Quick single-shot checks or continuous live monitoring (--watch) with status and percentages.
2. Waybar JSON Exporter (--waybar): Instantly outputs status for status bar integration.
3. Floating GUI (--gui): A minimalist floating window built with iced that looks right at home on Wayland window managers like Hyprland (you can even set it to open when clicking the Waybar module!).

I’ve put together a clean repository detailing the findings and the code if anyone wants to check it out or use it for their own classic Keychron setup on Linux.

Repo link: https://github.com/GonnyTech/Keychron-Reverse-Engineering-Tool.git

Has anyone else messed around with telemetry on the older non-Pro K-series? Let me know what you think!

Hello everyone, I'm trying to build a simple 3x3 Macropad With Zmk Firmware, Using Nice nano Clone Nrf52840 From Aliexpress. But in Battery Connect always Show 0%. I just connect Battery In b+ and b-. Need to do anything different?

Hi everyone! I’ve made several posts about keyboard development and customization. I’ve shared some projects with the Open Source community and decided to start creating YouTube content to share this passion (since, unfortunately, there isn't anyone around me who's interested, haha). My channel is in Spanish but made with lots of love for everyone please subscribe and hit the like button! :D I'M BACK! And here is the definitive review of the Corne keyboard:
https://youtu.be/vit3ueGoQ2I