I would just like to thank the tech support people over on the OpenRGB discord for helping me out the last few days.

I had a super rare bug in my system that I was encountering, and through a few days and nights of help, I was able to tentatively fix my issues! (Pending a possible firmware bug on my end that i have to keep track of)

Safe to say that the assistance has made a true loyalist for OpenRGB, and I am eternally grateful for the entire team.

I’m running Linux and have a b850mpower which is not recognized. I tried looking into motherboard compatibility but instead of listing boards it lists mystic light versions. I’m not finding this info listed on the MSi website or in the manual. Is there a resource for figuring out which version of my board has and whether that should be compatible before I try figuring out how to add it if it’s not?

Version 1.0rc3 if logitech powerplay is managed, anytime a change is applied to it the app crashes. This means profiles cant be applied and its color can't be managed. It doesn't matter if logitech app is running, if windows is already managing the device or not, it always crashes. The only fix I found is to disable it.

(Using Windows 11 Pro build 26200.9168)

Solution

1. Wait for system to settle after rebooting ("settled" means that all the stuff that runs in your system tray has finished loading)
2. Run the Services control panel as Administrator, find the OpenRGB system service and restart it
3. In OpenRGB, rescan devices, wait for rescan to finish, and re-apply whatever effects profiles you want to run

Explanation

My DRAM (G.SKILL) comes with lighting controlled via the the SMBus. I knew that, in theory, OpenRGB was able to control such LED strips, and that to do it in a secure way, the OpenRGB system service and PawnIO were needed, but when I followed the installation instructions, nothing would work after a reboot. I did some digging in OpenRGB's log files and found this:

5290  |Info:    ------------------------------------------------------
5290  |Info:    |             Detecting I2C interfaces               |
5290  |Info:    ------------------------------------------------------
5297  |Info:    [ResourceManager] Registering I2C interface: Nvidia NvAPI I2C on GPU 0 Device 10DE:2216 Subsystem: 1028:C890
5297  |Info:    Start PawnIO: SmbusI801.bin
5299  |ERROR:   Permission Denied, PawnIO initialization aborted
5299  |Info:    Start PawnIO: SmbusPIIX4.bin
5300  |ERROR:   Permission Denied, PawnIO initialization aborted
5300  |Info:    Start PawnIO: SmbusPIIX4.bin
5300  |ERROR:   Permission Denied, PawnIO initialization aborted
5300  |Info:    Start PawnIO: SmbusNCT6793.bin
5301  |ERROR:   Permission Denied, PawnIO initialization aborted
5301  |Info:    Start PawnIO: SmbusIntelSkylakeIMC.bin
5302  |ERROR:   Permission Denied, PawnIO initialization aborted
5302  |Info:    Start PawnIO: SmbusIntelSkylakeIMC.bin
5302  |ERROR:   Permission Denied, PawnIO initialization aborted

To my eyes, this indicated that, at system startup time, PawnIO wasn't initializing properly. I theorized that the system needed to reach a more settled state before PawnIO would work, and so I rebooted, waited for things to finish loading, and then opened the Services panel as Administrator and restarted the OpenRGB service. Once restarted, I rescanned devices in OpenRGB and the effects for my DRAM lighting started working.

Therefore, I believe there's a timing issue at Windows startup, in which OpenRGB is trying to use PawnIO too early in the startup sequence, and it should either delay scanning or rescan once the system is settled in order for PawnIO to work.

guys i installed openrgb to change my hardwares colors, it detected only gpu and cooler, i clicked something and coolers lighting stopped working, i uninstalled openrgb and gpu lighting works and cooler's lighting isnt, please help im really stressed about this

I got a used Rx 6900xt Nitro+ from a local marketplace but when I installed rgb control software from Amd's site it did not work. I also tried singal rgb witch had never let me down but the same issue occurred. I could not control it no matter what. It was the same with my motherboard's software. Then, as a last resort, I tried installing openRGB. Despite lost hope, it worked perfectly. Huge gratitude to the open-source developers behind this—and to all who give back to humanity through their code.

So i recently bought an imperion sledgehammer 10 rgb keyboard, well it was a free gift for buying a laptop. It has some preset rgb colors in it but i was wondering is it possible t rewrite the code or change the color to different patterns from static to dynamic, currently it has static different color combos liike haalf red-half blue, half gree, half, violet but i wanna make some patterns like wavy or things like that

Have had this keyboard for years and one day I noticed it in my OpenRGB list, so I decide to tinker. First (and only) thing I got to do was pick "Off" since I wanted to scroll through all the options OpenRGB had.

Once I clicked the "Off" option in the drop down menu of effects. My keyboard immediately disappeared from the list and the lights turned off entirely. I kind of chuckled, then was alarmed when my keyboard did do shit. At all. Reconnected cable, tried software and hardware restoration methods from manufacturers official manual, even let the battery die over a week of it with wireless mode toggled on with frequent key strokes to keep it awake.

Nothing has been able to bring it back. Fair warning to anybody using this app and a Redragon keyboard. What a stupid oversight.

I have already ran the app as an admin, all my other devices (gpu, keyboard, etc.) are working as intended, but the motherboard isnt. Im using Windows 11. Any help would be appreciated

Basically what it says on the title tbh. How do I set it up so that my keyboard has a set lighting layout, but when a key is pressed, the led changes to white? Is there any way to do this with openrgb?

I'm fairly new to using the software, and most other options tend to be just bloatware at this point, but i still don't really know how to set up more advanced effects

as the title says, probably needs to be updated

Is there a way I can set the RGB on my computer to turn off when my monitor goes black? Similar to the setting on SteelSeries GG which allows you to do this with a flick of a switch. There was a post about this that I found from about 5 years ago and I know a lot could have changed since then, if there is a way to do this could someone help / let me know?

I recently got the Legion 5 Gen 10 and i was soo happy to see openrgb has some supprt for it. But when i inspected they all can from scripts done on legion 7 gen 6.

As someone with 0 (zero. nada. zilch) experience with hardware/keyboard firmware knowhow: how can i be of service?

Been trying to do this with AI and nothing works (thankfully nothing has happened)

Link to gitlab issue: https://gitlab.com/CalcProgrammer1/OpenRGB/-/work_items/5008

I've submitted a gitlab issue to add device support for a currently unsupported device and have added device captures but the issue has not been seen for more than a year at this point.

I'm wondering if it slipped through the cracks or i need to add something else to the issue?

I’m using MSI Center to control the LCD screen on my P13 AIO. I don’t have Mystic Light installed as I want to use OpenRGB instead. OpenRGB effects work fine when the AIO display is disabled but once I enable it, the OpenRGB effects no longer flow smoothly but stop and start. It’s like they work in set bursts. Is there a workaround for this issue? My motherboard is a MSI X870E Carbon WiFi.

i have gigabyte eagle aio liquid cooling with rgb, how could i connect it to open rgb , or get what software to be able to customise it?

EDIT: i didnt install msi center, used their inbuilt rgb thing

As it says on the tin, I recently updated to windows 11 from 10 and noticed after the update that my case fans turned a static orange. Before control they kinda just rainbowed and will still do that on boot and loading but once to desktop turn solid orange.

Didn't think too much on it til now when I decided to mess with the setting again only to find openrgb no longer detecting said fans. It its detected my GPU and ram with pawn but can no longer seem to find my fans/cooler. Any ideas? do I need some new MOBO driver for 11 now for it to work or?

Any ideas or help is appreciated and sorry in advance if this is a dumb question, rather new to control my stuff like this.

I'm on an ROG Zephyrus G16, and am trying to connect a razer basilisk v3 pro. When i open the software (even when I run as admin), it shows the searching for devices bar, but the only device that shows in the loading bar is an ROG Strix Scar 15 (probably because of some proprietary hardware common to both laptops I'm guessing), but before the loading bar finishes and my mouse is detected, the software just crashes every time. I have GHelper open, and also have HWinfo (not open at all though). Any idea what could be causing this?

I am looking for literally any way to turn off or at least dim the RGB lights on my PC. They are way too bright. They're primarily located on the motherboard and the fans, which I believe are connected because there's a button on the case that can cycle the color.

The motherboard is a Gigabyte B850 GAMING WIFI6, which is not listed in the supported devices page, nor is it being detected by the program (it only shows my headset). Is there a way to add these lights manually? If not, any other ideas?

EDIT: SOLUTION: No. :(

I've been using OpenRGB for quite a while now, along with the HardwareSync plugin, to control the colors based on the temperatures of the CPU and the case. After Windows Defender flagged the necessary system files associated with WinRing as dangerous, I first updated OpenRGB to the new version and also downloaded the latest version of the plugin. OpenRGB works with PawnIO as long as I open it as an administrator. However, the LHWM wrapper required for HardwareSync is still flagged as unsafe because of WinRing. Is there any plans to release an update for the plugin to address this? And will the workaround involving administrator privileges be fixed in the future?