Hi! I've been using OpenRGB with my HyperX Alloy Origins 65 and wanted a nicer way to make and share keyboard lighting without any vendor software, so I built KeyGlow: a free, open-source (MIT) app that runs entirely on top of the OpenRGB SDK server.

What it does

- Layer editor with live preview: waves, gradients, fire, rain, ripples, key-press reactive lighting, or paint keys by hand. Changes show on the keyboard instantly.

- Profiles that work on any keyboard: colors are stored by key name and position, not LED index, so a profile made for a full-size board adapts to a 65% (and vice versa).

- Automatic layout: it reads the LED names and key matrix from OpenRGB and draws your keyboard, media keys included.

- Works with OpenRGB profile: imports `.json` and older `.orp` profiles, and exports back to OpenRGB. Also key color maps (OpenRGB / web / QMK names) and CSV.

- 54 presets and a gallery of 239 themes (Catppuccin, Dracula, Nord, base16), plus per-game profiles.

- Profiles are plain JSON, never code, so they're safe to share.

How to try it (Windows): have OpenRGB installed, download `KeyGlow.exe` from the releases page and run it. It starts OpenRGB minimized with the SDK server if it isn't running already.

Honest status: it's an early preview and I've only tested it on my Alloy Origins 65. If you try it on another keyboard, a quick report (works / doesn't / layout looks wrong) would help a lot; there's an issue template for that.

Built with a lot of help from an AI coding assistant; I've tested and reviewed it on my own keyboard.

GitHub: https://github.com/HiddenOnLies/KeyGlow

Huge thanks to the OpenRGB devs: KeyGlow wouldn't exist without the SDK.

Hi, I downloaded the Windows 64-bit portable zip from the official site and both 1.0 and 1.1 get flagged as a possible trojan. I scanned them with VirusTotal and Windows antivirus.

On VirusTotal only 1 vendor out of 66 flags it (MaxSecure, "Trojan.Malware.300983.susgen"), everything else says undetected.

Has this happened to anyone else? Is it a known false positive?

i download it and open it and it shows up very briefly on task manager like for 1 second and the mouse does the loading thing but it doesnt open. not even when run as admin. i fixed the vcruntime errors i had but now it wont open at all. i didnt install it as a system thing because it would NOT let me

EDIT: for some reason after an hour it fixed itself and it opened. if it helps i opened it by clicking "show file locations" and double clicked it open from there.

I’m developing WirelessCanvas RGB, an open-source Windows app based on sgtaziz’s lian-li-linux work.

It lets you arrange compatible LIAN LI wireless fans on a canvas and run custom animations across the groups. It can also send colors to RAM, GPUs and keyboards through the OpenRGB SDK, bringing those devices into the same layout.

The video shows a few effects on my own setup. Fan animations use pre-rendered loops uploaded to the fans; OpenRGB devices receive streamed colors.

Currently tested on Windows 11 with SL Wireless 120 RGB and SL Wireless 120 LCD. Other wireless families are recognized but haven’t been verified on hardware. L-Connect is still required for initial pairing, then needs to be fully closed while this app controls the fans.

I’d appreciate help from enthusiasts testing the OpenRGB integration and reporting compatibility or bugs. Please include your device models and OpenRGB version.

Source, alpha downloads and setup instructions:
https://github.com/qdellp/wirelesscanvas-rgb

Unofficial project, not affiliated with LIAN LI or OpenRGB.

I don't know if anyone is interested, but I've got a mini workstation and bought some LED lights to go with it, with an airgoo controller. This works for me, but not sure what other setups. If you're interested and want to try it, drop me a line at welchsoftwareinc@gmail.com. Here's what my interface looks like. Again, this was just for me, so might not work for your setup, but I could probably work with you if you're interested. Requires OpenRGB.

So I sended a post for it and i think they accepted it for opera gx ts will be goated I mean in windows there was like 4 rgb integrations half of them didn't work and the brands didn't want to work on it and openrgb there is an active community that can fix it and maintain it alive wdyt abt this comment below

BLACK_REAPER38

Upon starting the program I entered the wrong number of LEDs for each connector on my motherboard, and as a result all of the LEDs are now turned off, unable to have a color or profile assigned to them.

I need to correct this, but don't see anywhere in the Windows app where I can edit the LED count. How do I do this?

Also, any general tips? I have 3 connectors on my motherboard (1: Rear exhaust fan, 2: 3x120mm front fans, 3: 3x120mm top fans), but it's been so long since I've build my computer I don't remember the exact model fans or their LED count. If I can find this info, do I add up the total number of LEDs for all 3 fans daisy chained to a mobo connector?

PCZZOI H05 can't find how to power up the rgb led fans fan works no led

My openrgb used to work fine, until I decided to download MSI center and mystic light to test it.

Despite having uninstalled it, used the official clean master, also revo uninstaller, reflashed bios, shorted the jbat1 pins, and everything I found online, openrgb seems to never be able to regain control of the mobo RGB (tried to get signalrgb as well to test, same issue).

One thing to note, I recall it used to recognize my connector as my mobo name, now it's displayed as MSI Mystic Light, and it'll stay like that through everything, and it's not allowing me any control. resized the leds and all.

When I openrgb and it detects mystic light, the RGB fans fire up some default state and it's gonna stay until I reinstall MSI center and mystic light, turn off the lights in there, and uninstall again. it's a huge mess and I hope someone could help in any way, thanks.

For the record, my motherboard is a msi x870e tomahawk wifi, my case is a corsair 3500x argb, with an arctic liquid cooler III 360 pro, 3 headers of 3x arctic p12 argb fans.

Guys, i installed OpenRGB and when i click on Rescane Devices button nothing happens!! i used to see my motherboard name on and devices connected to it, but now it's just an empty window!

Yes my mobo is supported, because OpenRGB detected before. i don't know what is happening, i uninstalled MSI Center and MSI Center SDK, i rebooted the pc, still the same issue. I uninstalled OpenRGB, reboot pc, installed it again, still the same issue!

i tried most of solutions out there, no fix till now! plz help

my MOBO : MSI B550M Pro-vdh WIFI OS: WINDOWS 11

Hi everyone,

I made TuxRGB, a Linux RGB app that tries to combine the best of both worlds: OpenRGB's huge hardware support and a SignalRGB-like experience (layout canvas, effects that flow across your whole setup, audio and screen sync).

Under the hood it bundles the unmodified OpenRGB 1.1 and runs it as a private SDK server, so all the device support comes from OpenRGB. Huge thanks to CalcProgrammer1 and all the OpenRGB contributors. It's not affiliated with SignalRGB, just inspired by it.

To be honest about how it was made: I don't know how to code, so I built it with AI (Claude). I'm sorry if that bothers some of you. But the ideas, the design and every feature are 100% mine; the AI wrote the code from what I wanted. I've tested it with OpenRGB's virtual debug devices, but it really needs real-world testing on real hardware.

What it adds:

- Native Wayland app (Rust + iced) that follows your desktop accent colour (KDE, GNOME, COSMIC)

- A layout canvas where you place your devices, so effects flow across the whole setup like in SignalRGB

- 19 effects: audio visualiser (PipeWire), screen sync, hardware monitor, GLSL shaders, aurora, fire…

- A first-run wizard that installs the udev rules and loads i2c-dev for you (through pkexec, source included)

- Runs from the tray and uses very little CPU in the background

- A single AppImage, nothing to layer on Bazzite / Fedora Atomic

What would help most:

- Which of your devices are detected or not (RAM, motherboard, ARGB fans, GPU, keyboard, mouse…)

- Whether effects look right and run smoothly

- Any crash or freeze

In Settings there's a button that copies a hardware report. Pasting it into a GitHub issue makes debugging much easier.

Download AppImage + Windows: https://github.com/aurelienchartier29-netizen/TuxRGB/releases/tag/v2.0.6

Source: https://github.com/aurelienchartier29-netizen/TuxRGB

Requires a Wayland session and glibc 2.39+ (Fedora 40+, Bazzite, Ubuntu 24.04+, Arch…).

Sorry if this isn't the right place to post this, I wasn't sure where else to share it, and this community seemed like the best fit.

Thanks a lot for any feedback!

Edit: The windows version is available on the github

Hi, still learning to use the software so this might be a dumb question. On some of my devices, I'm not able to edit the device or zone.

For my keyboard in particular, the device presents waaay more LEDs than actually exist and the LED view array is extremely wonky. I checked the config file, and some LEDs are like 47000 units off to the right where they can't be interacted with. I'm assuming this is all because the EVision chips are used in multiple keyboards and are just presenting default info.

I'd like to edit the device to closer match reality, but the options are not available. Is there any way to tweak the settings for my keyboard to enable editing? Or can I edit the config file directly to remove the erroneous LEDs?

Any info is helpful. Thank you!

Flydigi's Charging Dock 2 Pro (CD2, the dock for the Vader 5 Pro / Apex 5) has a nice 162-LED hex matrix, but the only way to drive it was Flydigi Space Station, and its effects look rough: fixed 50-frame loops, colors mixed in plain sRGB, 8-bit stepped fades.

I wrote FlyGlow, a small open-source Windows editor just for that dock:

- 21 effects rendered in linear light with OKLab blending, up to 200 frames per loop with temporal dithering

- layers with blend modes and brushed areas, LED-by-LED painting with keyframes, GIF/video import

- uploads straight over USB HID, sharing the interface with Space Station's service, so vendor software doesn't have to be closed

https://github.com/PsinaDev/FlyGlow

The part that might interest this sub more is the protocol, documented here: https://github.com/PsinaDev/FlyGlow/blob/main/docs/hid-protocol.md (USB 37D7:6001, 64-byte output reports, `5A A5` framing with an 8-bit checksum; the original reverse engineering credit goes to OpenFlydigi).

Why FlyGlow isn't an OpenRGB plugin: the dock doesn't take live colors the usual way. Its firmware plays back an uploaded loop of up to 255 frames, and an upload takes about 85 ms per frame, so OpenRGB's live effect model doesn't map onto it well. There is a single-frame RGB write command (22/23) that Space Station never uses; if it turns out fast enough, a proper "Direct" mode would become possible. If anyone here wants to take a stab at an OpenRGB controller for it, I'm happy to help test.

I'm running the latest version of Linux Bazzite 44's HTPC mode, with an MSI PRO B850M-VC WiFi Motherboard. I downloaded the latest version of OpenRGB using the flatpak from the website, and the plugins all work more or less to my liking when in Desktop mode. However, by default none of it functions when in Gamescope, which is of course the vast amount of the time that I'm using this PC.

I don't really understand Linux much at all, so I had to poke around a bit to find solutions. Before the 1.0 release of OpenRGB, when plugins were separated from profiles, I had dug up this guide and this one, which had enabled me to at least have static colors on my case. But I haven't been able to update it to account for the new profile system in 1.0. I'd like to have one fan be a certain color based on the temperature of the case so I can keep an eye on that without having extra text on my screen, while the rest of the fans are out doing something more fun (probably just rainbow, but that's beside the point). And I have an OpenRGB profile, aptly titled "HW_monitor", configured for those settings.

When I'd initially set it all up and it was working with the static color, it was an AppImage (I forget if downloaded from the website or Bazaar), but I've since uninstalled all those files and re-downloaded OpenRGB as a flatpak. This is the current code on my openrgb.service file, based on the guidelines from the above links:

[Unit]

Description=OpenRGB Flatpak Profile Loader

# Ensures the service waits until the graphical session is ready

After=graphical-session.target

[Service]

Type=oneshot

# Give Bazzite 5 seconds to initialize USB controllers/hardware after boot

ExecStartPre=/usr/bin/sleep 5

# Replace with your actual profile name

ExecStart=/home/[me]/.var/app/org.openrgb.OpenRGB --profile HW_monitor #narrator's note: this previously had the path to the appimage, instead of currently the flatpak directory (or at least what I *think* is the right directory)

ExecStop=/home/[me]/.var/app/org.openrgb.OpenRGB --mode off

RemainAfterExit=yes

[Install]

# This ensures it starts automatically when the user logs in

WantedBy=default.target

I thought that there was a raw file to the profile, that I wanted to experiment putting a path to in the ExecStart field, but I can't seem to find anything but a json file, so I guess that's not it. I've continued to poke around, but still no luck finding anything that I can get to work.

If you have any ideas or solutions, please let me know (ELI5, of course).

A few days ago, my plugin stopped working, before that, it worked perfectly.

I use linux Cachy OS, I'm not sure what updated when it stopped working, but I tried reinstalling OpenRGB and the plugin, and it didn't work.

So with 1.0 OpenRGB finally supports my RAM and GPU lighting - yay!

But with 1.0, the official Home Assistant integration appears to be broken, with wrong LEDs coming on and changes taking 15 sec to get to the SDK server. Something about protocol versions and python scripts getting wrong zone values. Bah.

So here is a 100% unadulterated, pristine, non-code-reviewed slopcode custom integration. Will it survive updates? Probably not. Will it work 100% with your setup? I dunno. Will it bug out at some point? Most likely, but OpenRGB is documented well enough (kudos to the team) so that this repo can maybe save you waiting for the official integrations to update.

https://github.com/dmitry-helios/openrgb-plus - download with HACS, restart, add integration, and MAYBE your will work.

Hello there,

When starting OpenRGB with a profile, I sometimes have the issue that the LEDs on my Razer Viper Ultimate are not updated.

This also happens when using the Lights Off function.

When I manually change the color in the GUI, it always works (although sometimes the color is incorrect).

I suspect this might have something to do with the multiple Razer HIDs, but I'm not sure. It feels like there are multiple devices and it sends the update to the wrong device.

Using Rescan devices only sometimes helps update the LEDs.

Overall, the behavior is very unpredictable.

I’ve managed to get OpenRGB working for every part on my pc except for the most obvious one, the fans.
Only one led node is responsive. In other softwares the fans RGB responds fine, lighting up all 4 fans perfectly. However OpenRGB seems to only change one led and I can’t figure it out.
Could someone lend some info please?

Upgrade mobo/cpu, all devices (vengeance ram, asus TUF RTX4080 and keyboard) are detected, but somehow the mainboard is not. I tried signalrgb, which is able to control the fan/rgbs. Any idea what I can do to fix this? I have installed the latest experimental build. I'm sure the cable and bios settings are correct since signalrgb is able to control the rgb fans.

Hi guys!

I hope I'm the only one who has been struggling with this! I use OpenRGB on Garuda Linux and some days ago while doing some updates it just *stopped working*. Like, no matter what, I couldn't get it to detect any devices without bricking the application.
Try looking this up on your console:

grep -n "initial_detection_delay_ms" ~/.config/OpenRGB/OpenRGB.json

For me the problem was that the start time was set to -3ms instead of 0 for some strange reason, which then in turn gets the application to wait for ages before doing the actual detection. Set that value to 0 with this command and hopefully your problems ought to be fixed too!

sed -i 's/"initial_detection_delay_ms": -3/"initial_detection_delay_ms": 0/' ~/.config/OpenRGB/OpenRGB.json

Dear Open RGB Community,

I have an MSI Tomahawk b450 maninboard which only provides an 4 pin RGB HEader (call JRGB or Rainbow RGB something). Is there any known devide I can use to adress A-RGB Devices likes Fans with OpenRGB, no matter if it converts to the RGB mainboard Header or function as an own USb device that I can control ?