RGB Underglow
RGB underglow is a feature used to control "strips" of RGB LEDs. Most of the time this is called underglow and creates a glow underneath the board using a ring of LEDs around the edge, hence the name. However, this can be extended to be used to control anything from a single LED to a long string of LEDs anywhere on the keyboard.
ZMK supports all the RGB LEDs supported by Zephyr. Here's the current list supported:
- WS2812-ish (WS2812B, WS2813, SK6812, or compatible)
- APA102
- LPD880x (LPD8803, LPD8806, or compatible)
Of the compatible types, the WS2812 LED family is by far the most popular type. Currently each of these types of LEDs are expected to be run using SPI with a couple of exceptions.
Here you can see the RGB underglow feature in action using WS2812 LEDs.
Enabling RGB Underglow
To enable RGB underglow on your board or shield, simply enable the CONFIG_ZMK_RGB_UNDERGLOW and X_STRIP configuration values in the .conf file of your user config directory as such:
If your board or shield does not have RGB underglow configured, refer to Adding RGB Underglow to a Board.
Configuring RGB Underglow
There are various Kconfig options used to configure the RGB underglow feature. These can all be set in the .conf file.
| Option | Description | Default |
|---|---|---|
CONFIG_ZMK_RGB_UNDERGLOW_EXT_POWER | Underglow toggling also controls external power | y |
CONFIG_ZMK_RGB_UNDERGLOW_HUE_STEP | Hue step in degrees of 360 used by RGB actions | 10 |
CONFIG_ZMK_RGB_UNDERGLOW_SAT_STEP | Saturation step in percent used by RGB actions | 10 |
CONFIG_ZMK_RGB_UNDERGLOW_BRT_STEP | Brightness step in percent used by RGB actions | 10 |
CONFIG_ZMK_RGB_UNDERGLOW_HUE_START | Default hue 0-359 in degrees | 0 |
CONFIG_ZMK_RGB_UNDERGLOW_SAT_START | Default saturation 0-100 in percent | 100 |
CONFIG_ZMK_RGB_UNDERGLOW_BRT_START | Default brightness 0-100 in percent | 100 |
CONFIG_ZMK_RGB_UNDERGLOW_SPD_START | Default effect speed 1-5 | 3 |
CONFIG_ZMK_RGB_UNDERGLOW_EFF_START | Default effect integer from the effect enum | 0 |
CONFIG_ZMK_RGB_UNDERGLOW_ON_START | Default on state | y |
Adding RGB Underglow to a Board
RGB underglow is always added to a board, not a shield. This is a consequence of needing to configure SPI to control the LEDs.
If you have a shield with RGB underglow, you must add a boards/ directory within your shield folder to define the RGB underglow individually for each board that supports the shield.
Inside the boards/ folder, you define a <board>.overlay for each different board.
For example, the Kyria shield has a boards/nice_nano.overlay file that defines the RGB underglow for the nice_nano board specifically.
The first step to adding support for underglow is to select you SPI output. With nRF52 boards, you can just use &spi1 and define the pins you want to use.
For other boards, you must select an SPI definition that has the MOSI pin as your data pin going to your LED strip.
Here's an example of an nRF52 SPI definition:
info
If you are configuring SPI for an nRF52840 (or other nRF52) based board, double check that you are using pins that aren't restricted to low frequency I/O. Ignoring these restrictions may result in poor wireless performance. You can find the list of low frequency I/O pins here.
Here's another example for a non-nRF52 board on spi1:
Once you have your led_strip properly defined you need to add it to the root devicetree node chosen element:
Finally you need to enable the CONFIG_ZMK_RGB_UNDERGLOW and X_STRIP configuration values in the .conf file of your board (or set a default in the Kconfig.defconfig):