Hi guys, I wrote a small article on how to select the correct switches/keycaps for your next build here. Please have a look as it might help preventing you from buying incompatible products.

The stock YUNZII B75 PRO MAX firmware is QMK-based and has VIA compiled in,

but not the OpenRGB protocol — so OpenRGB fails to detect it with the usual

"Detection failed ... add OPENRGB_ENABLE = yes" message.

I ported the OpenRGB QMK protocol into YUNZII's own QMK source and built a

firmware that OpenRGB detects properly. Direct mode works, so per-key control

from music visualizers / ambient lighting is up and running.

Repo (prebuilt .bin + source + flashing/recovery guide):

https://github.com/ZerO970/yunzii-b75-pro-max-openrgb

Board: STM32F103, VID 0x28E9 / PID 0x31C8, 6x15 matrix, 85 LEDs (AW20216S),

stm32duino bootloader.

Notes / limitations:

- USB only (no OpenRGB over BT/2.4G).

- It's a VIA-free build — OpenRGB and VIA can't coexist (shared raw HID), so

the vendor configurator + module OTA aren't available on this firmware.

Keep your stock .bin as a backup; recovery is just ESC+plug-in to bootloader.

- Onboard hardware effect list is only partial in OpenRGB (vendor reordered

the effects); Direct mode — the main use case — is unaffected.

Credits to the OpenRGB QMK protocol (Kasper24's original PR and Domi2803's

newer-QMK port). Feedback / testers welcome, especially if you have a slightly

different B75 revision.

Hmx sprite v2 and guitar knobs

Anyone know how to fix this? issue only happens on the right side of R4. Tried flashing firmware and didnt fix the issue. Its an NK65.

also if this is the wrong place to post, let me know.

I love Auto Shift. I use it not just to type capitals, but to get dual use out of every key, including combos. I even use it to simulate mouse dragging.

But I can’t figure out how to get it to work with Leader key sequences. Is it possible?

My workaround has been using a double-tap where I would normally long-press.

For example, here are my Leader key sequences for é and É: (click here for my full Leader.c)

  else if (leader_sequence_two_keys(KC_E, KC_A)) { register_unicodemap(EACUTE); }
  else if (leader_sequence_three_keys(KC_E, KC_A, KC_A)) { register_unicodemap(EACUTECAP); }

For all accented letters, my pattern is base letter + diacritic: ea = é

I would like to be able to long-press the diacritic to get the capital variant: eA = É

But since I don’t know how Auto Shift sends the raw capital letter, I double tap the diacritic instead: eaa = É

This is less than ideal as I’m stuck with three key sequences for every capital letter. Two key sequences for both lower case and upper case would be preferable.

Is what I want possible, or is Leader unable to get input from Auto Shift?

Hi everyone,

I'm new to the keyboard scene. I got a Solfe RGB split keyboard which I spent a few days soldering. I finally got it up and running, and the key presses are being detected, but I can't get the RGB to work.

What's worse, the guide I was following suggested using an RGB keymap which got deleted a few months ago. Does anyone know how to enable the LEDs?

Here's the guide I was following: https://docs.beekeeb.com/build-guide/sofle-rgb-v2.1-soflekeyboard-build-log-guide-with-photos

And here's the keymap that got removed: https://github.com/qmk/qmk_firmware/tree/master/keyboards/sofle/keymaps/rgb_default

I'd really appreciate any suggestions. I tried doing things like defining RGB constants in the header.h file, but I'm way out of my depth here.

Edit: Success!!! Thanks for your help. It turns out I soldered the LEDs on the wrong way (the marking on the PCB was supposed to line up with DOUT, but I had it lined up with DIN).

Hello, I'm building a mini-keyboard and I created a very minimalistic AZERTY layout (build for Raspbian OS). Here's the design, what do you think ?

My travel setup is basically just a MacBook and a keeb with a trackball now.

The best part is not having to move my hand over to the trackpad all the time. It’s not the most compact setup, but it’s way more comfortable to work with

I’m still tweaking the layout and layers, but it already covers pretty much everything I need

I've been rocking this custom ortho keyboard for a few years, got custom PCBs made, programmed my own firmware and everything worked excellently. But now the last piece I had broke down (now I have toddlers and they threw it to the hard concrete floor by accident).

BUT I lost all my firmware code, my last PC got infected and lost everything, unfortunately I did not have a back up of my STM32 firmware.

Now life is too busy to go through that whole project again on my own, is there any way anyone recommends building this so that it's very easy and not time consuming?

Besides the layout, I'm looking for the keyboard to lay completely flat, be as thin as possible, use Kaihl Box Jades (or similar clickys) and to use DSA keycaps (which I still have, though all blanks). I'm currently making do with a cheap generic mechanical keyboard I found on Amazon.

I just received my Keebio Iris SE and seriously thought it was wireless. Not the worst thing in the world that it isn’t, but I was wondering if I would able to connect a universal keyboard dongle and if that would work?

Reddit filters didn't like my original post. I appreciate all the great feedback, so I'm giving it another try.

QMK Nexus is a firmware creation site I built, and I have been working out its rough edges over the last couple of months. It allows you to set up the layout, wiring, and mapping of your keyboard to ultimately create QMK firmware. I've added support for many features, such as OLED screens, encoders, and joysticks, that aren't supported by other QMK tools.

Please give it a try and let me know what you like, dislike, or what just doesn't work. I've successfully tested on all my ErgoDox keyboards (5 different models), but I lack the hardware to properly test many features. I'd love to hear feedback so I can keep improving this tool for the community.

https://qmknexus.tebay.dev

I'm using OSL so that the next key is from a layer, and to hold down the key to type multiple keys in a layer. Can I make it so OSL lasts a long time but has no delay for me to hold the key down?

Trying to land on my next split board and could use input from people who’ve used more than one of these.

My situation: big hands, need low-profile with light switches (20gf max ideally). Apple Magic Keyboard’s scissor switches are the gold standard for me, just wish it came split.

What I’ve gathered so far, correct me if wrong:

**MoErgo Go60** — great layout/build, but the trackpad seems to get consistently panned as barely usable.

**ZSA Voyager + Navigator** — solid reputation, but I’d be eating tariffs on top of price, and not sold on the trackball fitting my hand/RSI situation.

**Toucan2** — sounds like the best trackpad of the three (multi-touch, actually functional), but fewer keys and more layering, which seems rough as someone still learning ergo layouts.

This would be my starting board before eventually working toward something more heavy-duty and fully custom down the line for the RSI/SFN/cubital tunnel/TOS/tennis elbow combo (aka the Svalboard). Anyone made the jump between any of these three, or have thoughts on which pointing device is least likely to aggravate elbow/nerve issues?

Added some mx legend keycaps so I don’t have to play the guessing game anymore 😅

A few months back I built the Scotto2 for someone with quadriplegia that allowed them to play racing games using 2 large buttons. I figured something cool to do for a bit of a meme would be an entire number pad with giant buttons. The result is the ScottoBigum which I believe to be the largest in the world. Each button is scaled up 4 times and the entire thing weighs close to 2 pounds… oh and it’s also wireless with ZMK studio support so it doesn’t need to be strictly a number pad.

I have a full build video coming out tomorrow on my YouTube channel and as usual with all my handwired projects, all the files are available for free if you want to build this one yourself.

The only real trick I can think of is to flash the left side and right side with 2 different firmwares, and depending on which side is master you could have a qwerty layer, and when you plug the otherside in you could have a stenno layer.

Other than layout, is there anything else you can do ?

Hi everyone,

I was recently given a few Plaid PCB, which was out a few years ago (I missed the hype). One of them is almost fully working, and I wanted to finish it up. You can see the build docs and some images at this github repo if you are interested, but it is not necessarily relevant for my question.

However, the friend that gave me the PCBs did not have any bottom plates. I will ask one of the old revendors I found on internet whether they have some spare ones I could buy.

However, I was also thinking about finishing the keyboard with a case, as I have access to 3D printers and found some models online. So, I wanted to know whether I would need the bottom plate anyway, to make contact with the case or something? Or just the PCB + everything soldered on it would be sufficient?

I also asked on the r/MechanicalKeyboards, but figured some in here would maybe know as well

Thanks for reading

I’m losing my marbles.

I recently got a Keebmonkey Kb-16 and have been messing around with it, getting it set up through Vial.

I found a reddit post which is a fork from this github that shows some modifications to the firmware. I realized after some more dabbling that I was interested in modifying the number of Macros, Combos, and TapDances.

Now, i’m fairly sure I have the modifications to the config.h file figured out now, but I am very lost on why I can’t get it to compile with the qmk cli. I have followed this youtube video, but he only modifies the keymap.c file, not the config.h file. The oled display is also modified in the github file, so where does that fit into the qmk_firmware file tree?

Do I need to do something with the “asset” folder? What folder/ files from the github need to be transferred? Am I even using the right compilation process (QMK CLI through MacOS terminal) for a Vial-only firmware?

Any help is very much appreciated, it’s been two days of trying to wrap my head around this. Thanks!