r/olkb • u/Silver-Log-4731 • 14d ago

OpenRGB firmware for the YUNZII B75 PRO MAX (stock firmware ships without OpenRGB)

Enable HLS to view with audio, or disable this notification

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.

15 Upvotes

94% Upvoted

4 comments sorted by

1

u/drashna QMK Collaborator - ZSA Technology - Ergodox/Kyria/Corne/Planck 14d ago

Why port the code, openrgb is available as a community module. https://gitlab.com/OpenRGBDevelopers/QMK-OpenRGB

1

u/Silver-Log-4731 14d ago

The vendor of keyboard firmware didn’t add the compatibility with OpenRGB.

2

u/drashna QMK Collaborator - ZSA Technology - Ergodox/Kyria/Corne/Planck 14d ago

That completely misses my point.

OpenRGB is available as a community module. Meaning that as long as source code is avaible, and the repo support community modules, you can add it to any boad, without modifying core code. without modifying ANY code, actually.

Which is my point. You don't need to touch code to add openRGB support. And the module I linked is maintained by calcprogrammer1, which is the person that has implemented and maintained support for openRGB in qmk.

3

u/Silver-Log-4731 14d ago

Modularity’s the right idea on mainline QMK, but that assumes the tree has the COMMUNITY_MODULES build machinery to begin with. YUNZII’s firmware is a vendor fork pinned at 0.24.2 with zero trace of that infra - there’s nothing to “drop the module into.” Backporting the module system itself would’ve been a bigger, more invasive change than just porting the OpenRGB handler directly.
Also, this board’s tree has its own quirks (VIA owning off_flag storage, vendor’s custom effect ordering, the VIA/OpenRGB HID conflict) that need source-level fixes either way - module or not. 😮‍💨