Need help with CorsairLightingProtocol?
Click the “chat” button below for chat support from the developer who created it, or find similar developers for support.

About the developer

176 Stars 36 Forks Apache License 2.0 415 Commits 9 Opened issues


Control LEDs connected to an Arduino with iCUE, create an unofficial Corsair iCUE compatible Arduino LED controller.

Services available


Need anything else?

Contributors list

# 57,017
311 commits
# 80,163
1 commit
# 312,221
1 commit
# 23,274
1 commit

Corsair Lighting Protocol arduino-library-badge Test Status Average time to resolve an issue


This library can be used to integrate custom/unofficial RGB strips with iCUE. This is not an official corsair project.


  • Add support of Corsair DIY device protocol to Arduino.
  • Control LEDs with the Corsair iCUE software.
  • Support common LED chipsets. (e.g. WS2812B, WS2801)
  • Support FastLED.
  • Supported platform: Arduino AVR
  • Hardware Lighting mode.
  • Use multiple devices at the same time.
  • Repeat or scale LED channels to arbitrary size.

Supported Devices

  • Lighting Node PRO
  • Commander PRO
  • Lighting Node CORE
  • LS100 Smart Lighting Controller
  • LT100 Smart Lighting Towers


Getting started

This project is an Arduino library called "Corsair Lighting Protocol". It can be used to control Arduino boards with iCUE. This project provides example sketches for easy use with Arduino IDE.


The library is compatible with all boards using the MCU ATmega32U4. This includes Arduino Leonardo, SparkFun Pro Micro, Arduino Micro, and Adafruit 32u4 AVR Boards. It also supports the Arduino Uno and Arduino Mega, but this requires the HoodLoader2 bootloader, see this wiki for more details. It is not compatible with ATmega328 (Arduino Nano), STM8S103F3, teensy, ESP8266 and ESP32 see list of architecture/platform for a detailed description why they are not supported. In the rest of the documentation "Arduino" is used as a synonym for all supported boards regardless of the manufacturer.

When you have problems with a board not listed here, please open an Issue.

Install the libraries

To use this library you must install it with the Library-Manager. Open the Library-Manager in Arduino IDE via Tools->Manage Libraries... Search for "Corsair Lighting Protocol" and install the Corsair Lighting Protocol library. This library also requires the FastLED library. Search for "FastLED" in the Library-Manager and install the FastLED library.

Create a Lighting Node PRO

This guide will teach you how to create a Lighting Node PRO with an Arduino Leonardo compatible board. If you have an Arduino Uno or Mega, see the other guide.

  1. Open the example "LightingNodePRO", you can find it in Arduino IDE in the File menu->Examples->Corsair Lighting Protocol->LightingNodePRO. If you can't open the LightingNodePRO example the Corsair Lighting Protocol library is not installed correctly.

open example sketch 1. Install the CLP Boards. They can be installed by following the CLP Boards installation guide. After installation it should be possible to select the CLP Boards in the Arduino IDE as shown in the screenshot below. If your are using a Sparkfun Pro Micro also install the SparkFun Boards definition.

select CLP Board 1. Upload the "LightingNodePRO" sketch to your Arduino.

upload sketch 1. Do the wiring. For more information on how to wire the leds and how to set up the LEDs in the code see the links.

the wiring 1. Verify your device works as expected. Open the Windows settings->devices->Other devices. Somewhere in the list of devices, there should be a device called "Lighting Node PRO". 1. Now open iCUE there you should see the "Lighting Node PRO".

Use the Lighting Node PRO

iCUE RGB Strip example

In iCUE open the "Lighting Setup" tab of the Lighting Node PRO(LNP) and set for both Lighting Channels the device to "RGB Light Strip" and the amount to a tenth of the LEDs you have. iCUE groups the LEDs into groups of ten. So if you have 20 LEDs, set the amount to 2. Now you can create lighting effects in the "Lighting Channel #" tabs.


How it works

This library uses the USB HID interface of the ATmega32U4. After uploading a sketch with the library and selected CLP Boards, iCUE recognizes the Arduino as a Corsair device, because the CLP Boards use USB IDs of Corsair. In iCUE you can then select the device and set some lighting effects. iCUE sends these via the HID protocol to the Arduino. These commands are understood by the library and converted into lighting effects on the RGB strips connected to the Arduino. The FastLED library is used to control the LEDs.

Use of multiple devices

Each device has two unique IDs, that is, they should be unique. You must give each device a unique ID. There are two IDs that must be changed

Serial Number

The Serial Number can be set in the constructor of

as shown in the example.
const char mySerialNumber[] PROGMEM = "202B6949A967";
CorsairLightingProtocolHID cHID(&cLP, mySerialNumber);
The Serial Number MAY only consist of HEX characters (0-9 and A-F).

The DeviceID can be set with the

function of
void setup() {
    byte deviceId[4] = { 0x9A, 0xDA, 0xA7, 0x8E };



can be changed with the DeviceIDTool. Upload the DeviceIDTool sketch and then open the Serial monitor with baudrate 115200. The tool displays the current DeviceID, you can type in a new DeviceID that is saved on the Arduino. After that, you can upload another sketch.

Repeat or scale LED channels

You can repeat or scale LED channel controlled by iCUE onto physical LED strips. This is very useful if you have very long LED strips that are longer than 60/96/135 LEDs, which is the maximum number iCUE supports.

To repeat or scale a LED channel you must apply the

or the
function in the update hook of the FastLEDController. See the RepeatAndScale example for the complete code. Both functions take the FastLEDController pointer and the channel index as arguments. Additionally, the
function takes as an argument how often the LED channel should be repeated. For example, if you want to duplicate the channel you must pass
as argument. The
function takes as third argument the length of the physical LED strip to which it scales the channel using integer scaling. For example you have 144 physical LEDs on you strip and 60 on the LED channel. Then the third argument of the
function is

For both functions it's important, that the CRGB arrays have at least the length of the physical LED strip. This means if your LED channel from iCUE has 50 LEDs and you use the

function to control 100 physical LEDs you MUST declare the CRGB array at least with a length of 100.

Increase the Brightness of the LEDs

When using LS100 or LT100 iCUE only uses 50% of the LEDs brightness even if you set the brightness to max in the iCUE Device Settings. But there are good news, we can increase the brightness with the Arduino so we can use the full brightness of our LEDs. Add the

function to the
in the setup function as shown in the example. If there are multiple functions called in
should be the first. Only use this function with LS100 and LT100 devices!
ledController.onUpdateHook(0, []() {
    CLP::fixIcueBrightness(&ledController, 0);

Reverse direction of LED Strip

If you want to change the direction of the LEDs of the Strip without physically change the strip, the

function can be used. The reverse function must be called be for scaling.
ledController.onUpdateHook(0, []() {
    CLP::reverse(&ledController, 0);

Hardware Lighting mode

The Hardware Lighting mode can be configured in iCUE. It allows you the set lighting effects that will be active when iCUE is not running. This is the case when the PC is off, in sleep mode, booting or the user is logged out. So if you want to have lighing effects in all these situations, use the Hardware Lighting mode. If you don't want it, configure a static black color.


This project is licensed under the Apache 2.0 License.


This is a DO IT YOURSELF project, use at your own risk!


Related projects

We use cookies. If you continue to browse the site, you agree to the use of cookies. For more information on our use of cookies please see our Privacy Policy.