I have added support for system-wide plugin installations in Linux for the upcoming 1.0 release. The plugin files can be installed system-wide to the /usr/lib/openrgb/plugins path, which allows them to be provided by distribution packages rather than manually downloading them.

I have created AUR packages for the following plugins and they have been picked up by the Chaotic AUR repository if you want binary builds.

• openrgb-plugin-e131-receiver-git
• openrgb-plugin-effects-git
• openrgb-plugin-hardware-sync-git
• openrgb-plugin-visual-map-git

I plan to update the rest of the plugins on https://gitlab.com/OpenRGBDevelopers and get them into the AUR as well before 1.0 releases. Until that happens, you will need to use the openrgb-git AUR package to utilize these new plugin packages. The current 0.9 release in the main repository does not support system-wide plugin installation.

Hi. OpenRGB detects my ENE DRAM correctly when run as Administrator. However, the DRAM is not detected when I launch the program without admin rights.

My OS: Windows 11 (this problem did not occur when I used Windows 10 a few weeks ago). Motherboard: Gigabyte B550 AORUS PRO AC ATX AM4 Motherboard Memory: G.Skill Trident Z RGB 16 GB (2 x 8 GB) DDR4-3600 CL18 Memory

Is there anything I can do so that OpenRGB detects my DRAM without admin rights?

I made a 3D printed, Arduino-powered desk fan based around a 120mm Corsair QL120 ARGB fan after seeing Noctua's desk fan. I wanted something similar but with RGB. It is based around CorsairLightingProtocol so it syncs with OpenRGB but also has a knob to adjust fan speed and LED brightness directly. I made a video showing it off but if you prefer to read about it, I have project documentation and files (code, assembly instructions, and 3D models) on GitLab here:

https://gitlab.com/CalcProgrammer1/OpenRGBDeskFan

The 3D models are also on Thingiverse:

https://www.thingiverse.com/thing:6655697

Hey all. I'm running OpenRGB Pipeline on Lenovo Legion 7 Gen 7 laptop. I have downloaded the 0.9 effects plugin and can run it successfully for effects. However if I run an effect through GIFPlayer the app just crashes after a random uptime. Typically in 5 minutes or sometimes less. I'm using gif files ~30kb for effects. Any idea on how to keep the app running?

after having some issues with my igpu (7800X3D), i decided to disable it in uefi. i'm running win10 (22h2, 19045.4651).

as for the description what i was seeing:

• i disabled the igpu in uefi
• reboot
• crash of OpenRGB upon starting up/scanning devices
• i deleted %appdata%/OpenRGB
• i ran the .exe as admin
• as soon as the scan went over the gpu (gigabyte gtx1080 ti aorus master) the programm CTD'd again
• disabling all detectors in OpenRGB.json allowed me to launch the app again
• in the settings i was able to reenable the mobo detection without issues and passed rescanning the devices
• in the settings reenabling all gigabyte device detections triggered the CTD upon rescanning again

at least it was able to log something to that point:

https://pastebin.com/fhnEddij

what i noticed in the logs is the following weird message: for some reason my mobo (an ASUS TUF GAMING X670E-PLUS WIFI) is being identified under gigabyte:

7325 |Debug: [Gigabyte RGB Fusion 2 SMBus] FAILED - 'TUF GAMING X670E-PLUS WIFI' was not found in the JSON list. Do NOT enable if this is a USB based board.

to me it seems that disabling the igpu somehow has messed up the enumeration of the devices/ids/slots, which led to the mobo being somehow wrongfully pushed up to the gpu slot, or something along the lines.

edit: before any questions arise, i'm running version 0.8, but upgrading to version 0.9 yielded no change in behaviour, which is why i downgraded again.

Besides the size difference, which one would you choose for OpenRGB on Arch Linux? Had a Keychron K8 Pro that I didn't get to work. Now it died, so have to replace it. Price wise they're 50 for the Alienware (new) and 75 for the Razer (open box, as new). Please help me decide. Thanks!

Update if anyone finds this thread later: I went with the Razer BlackWidow V3 and also got a Basilisk V3 to match it and they work very well with OpenRGB, I would definitely recommend them! I’m slightly annoyed by the green switches on the keyboard (sound and the feeling when typing) but that’s of course unrelated.

I am using Linux Arch (more specificaly, Garuda) and I wanted to use the effects plugin, but since the site and github only show versions for debian, I tried with the 3 (bulleyem bookworm and buster) by going into the settings > plugins and install the decompreesed file, but then nothing happened, it didn't add it. I also tried going into usr/share and making the directory openrgb/plugins and put it there, but it didn't work either. Has anyone had this problem and fixed it?

I've got a B550 GIGABYTE Aorus Elite AX V2 Motherboard. My OS is Ubuntu 22.04, OpenRGB is 0.9 installed from deb. lsusb output:

Bus 001 Device 004: ID 048d:5702 Integrated Technology Express, Inc. ITE Device

Looking at the Fusion 2 USB detector, it should be picked up by OpenRGB. Latest udev rules are installed and my mouse is picked up, but nothing else.

Description

The Corsair M65 ULTRA RGB wired has been added to the master branch with MR !2367 and I tried to switch the (fine) lights off. There are differences in behavior for the first and subsequent starts:

• start via ./openrgb after compiling and applying udev rules: colors of all three zones can be changed
  • I switched all colors to black and quit the program
• start via ./openrgb after reboot: colors freeze and can't be changed
  • this time I accidently left ckb-next-daemon running which might have interfered
  • unplugging the mouse seems to reset everything - the button to save the settings is disabled
• start via ./openrgb -v again: colors freeze
  • logs say mouse can be detected, nothing suspicious
  • back/forward buttons on the left side are now disabled until mouse get unplugged (most likely didn't notice the first time)
• start via ./openrgb -vv: mouse goes black (because thats my chosen color in the gui) and colors can be changed!
  • logs contain an error, as shown below
  • unplugging and restarting with ./openrgb -v lets colors freeze again

In summary:

• I'd like to be able to change colors (to black)
• I'd like to be able to persist chosen colors across reboots
• Mouse buttons shouldn't be disabled after starting ./openrgb

Logs

Logs for `./openrgb -vv`

[Corsair M65 RGB Ultra Wired] is enabled [ResourceManager] Calling detection progress callbacks. [Corsair CORSAIR M65 RGB ULTRA Gaming Mouse] GetAddress 12 - 00 02 - 00 9E 1B 00 00 00 00 00 [Corsair CORSAIR M65 RGB ULTRA Gaming Mouse] Setting write CMD to 08 for wired mode for PID 1B9E [Corsair CORSAIR M65 RGB ULTRA Gaming Mouse] Packet length set to 65 [Corsair CORSAIR M65 RGB ULTRA Gaming Mouse] Lighting Endpoint set to 01 [Corsair CORSAIR M65 RGB ULTRA Gaming Mouse] GetAddress 41 - 00 02 - 05 00 00 00 00 00 00 00 [Corsair CORSAIR M65 RGB ULTRA Gaming Mouse] An error occurred! Get Address 41 failed - 5 Unsupported [Corsair CORSAIR M65 RGB ULTRA Gaming Mouse] Creating a linear zone: Logo with 1 LEDs [Corsair CORSAIR M65 RGB ULTRA Gaming Mouse] Creating a linear zone: Scroll Wheel with 1 LEDs [Corsair CORSAIR M65 RGB ULTRA Gaming Mouse] Creating a linear zone: Indicator with 1 LEDs [Corsair M65 RGB Ultra Wired] Registering RGB controller

\ Versions OS: Debian 12 bookworm Kernel: x86_64 Linux 6.7.12+bpo-amd64 OpenRGB: commit 853f12e9c10d148fe4c71f6aed9c32af4dd3e32f

Hi,

Just wanted to point out that the chat bot on help.openrgb.org still has a link to the readonly reddit sub instead of here.

Hello, I just bought a new laptop it’s an Asus Zenbook Pro flip 15.

The install went very well with only a few minor issues that I was able to fix within a few minutes. Unfortunately, the one thing that’s been difficult to fix is I would like to be able to change the RGB colors of the keyboard.

I have tried all the fixes I could find online, I tried OpenRGB, supergfxctl, Asusctl, and several other fixes mentioned online.

When I run OpenRGB I get this error:

"One or more I2C/SMBus interfaces failed to initialize. RGB DRAM modules and some motherboards' onboard RGB lighting will not be available without I2C/SMBus. On Linux, this is usually because the i2c-dev module is not loaded. You must load the i2c-dev module along with the correct i2c driver for your motherboard. This is usually i2c-piix4 for AMD systems and i2c-i801 for Intel systems. See help.openrgb.org for additional troubleshooting steps if you keep seeing this message."

Unfortunately nothing I have tried has worked. It’s obviously not a huge issue but it’s the only thing that’s not working flawlessly. Any help would be greatly appreciated! Thank you!

Pastebin of my setup is attached.

So I'm guessing this has as much to do with a newer version of OpenRGB as the distro change, but I moved from Ubuntu 20.04 to Debian 12.

I've installed OpenRGB via the deb on the site. Running sudo openrgb -l -vv I get this at the end:

2: ASUS ROG STRIX B550-F GAMING Type: Motherboard Description: ASUS Aura USB Device Version: AULA3-AR42-0207 Location: HID: /dev/hidraw0 Serial: 9876543210 Modes: [Direct] Off Static Breathing Flashing 'Spectrum Cycle' Rainbow 'Chase Fade' Chase Zones: 'Aura Mainboard' 'Aura Addressable 1' LEDs: 'Aura Mainboard, LED 1' 'Aura Mainboard, LED 2' 'Aura Mainboard, LED 3' 'Aura Mainboard, RGB Header 1' 'Aura Mainboard, RGB Header 2'

But it no longer finds my fans via the standard ARGB controller. The RGB controller and on-board LEDS for the mobo work fine. I've tried every combination of switching "Zone", "LED", and "Mode" with no luck.

I do have an orp file that used to work if that helps? The strings output for anything ASUS are the same between the old one and a new one I made. So the devices exist in both, right? Here is an example:

ASUS Aura Motherboard ASUS Aura USB Device AULA3-AR42-0207 9876543210 HID: /dev/hidraw0 Aura Mainboard Aura Addressable 1 Aura Mainboard, LED 1 Aura Mainboard, LED 2 Aura Mainboard, LED 3 Aura Mainboard, LED 4 Aura Mainboard, LED 5 Aura Addressable 1, LED 1 Aura Addressable 1, LED 2 Aura Addressable 1, LED 3 Aura Addressable 1, LED 4 Aura Addressable 1, LED 5 Aura Addressable 1, LED 6 Aura Addressable 1, LED 7 Aura Addressable 1, LED 8 Aura Addressable 1, LED 9 Aura Addressable 1, LED 10 Aura Addressable 1, LED 11 Aura Addressable 1, LED 12 Aura Addressable 1, LED 13 Aura Addressable 1, LED 14 Aura Addressable 1, LED 15 Aura Addressable 1, LED 16 Aura Addressable 1, LED 17 Aura Addressable 1, LED 18 Aura Addressable 1, LED 19 Aura Addressable 1, LED 20 Aura Addressable 1, LED 21 Aura Addressable 1, LED 22 Aura Addressable 1, LED 23 Aura Addressable 1, LED 24 Aura Addressable 1, LED 25 Aura Addressable 1, LED 26 Aura Addressable 1, LED 27 Aura Addressable 1, LED 28 Aura Addressable 1, LED 29 Aura Addressable 1, LED 30 Aura Addressable 1, LED 31 Aura Addressable 1, LED 32 Aura Addressable 1, LED 33 Aura Addressable 1, LED 34 Aura Addressable 1, LED 35 Aura Addressable 1, LED 36 Aura Addressable 1, LED 37 Aura Addressable 1, LED 38 Aura Addressable 1, LED 39 Aura Addressable 1, LED 40 Aura Addressable 1, LED 41 Aura Addressable 1, LED 42

for context: I have an Asrock b450m/ac R2.0 MoBo (that seems to matter), and I'm running Nobara Linux. I was using OpenRGB to control some rgb fans and it was working fine, although I couldn't control the individual LEDs. Then suddenly (Can't think of anything I did that would've messed it up, other than maybe going from the 'effects' tab (from the plugin) to the default one, and clicking apply color, that's when it happened) it stopped recognizing my devices. I read online that I needed to run it as sudo, but when I do, I get this error Attempting to connect to local OpenRGB server. Connection attempt failed Local OpenRGB server unavailable. Running standalone. [i2c_smbus_linux] Failed to read i2c device PCI device ID QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root' terminate called after throwing an instance of 'std::bad_alloc' what(): std::bad_alloc Aborted From looking online it seemed to be the SMBus access problem mentioned in the OpenRGB Docs, and so I tried following these steps, but honestly I think I'm too new to really understand how to do it right. It felt like things kept going wrong during the patching of the kernel part, up until the last line, which simply didn't work.

As a Linux noob, I would super appreciate very noob friendly responses. Any help would be really appreciated.

Hi there, I’m building a new pc and my build is completely black without rgb lights. My question is, can I turn off the led strip on the 7800xt Nitro+ from Sapphire? I checked and it seems to be supported, can someone please confirm that I can turn off the led strip completely? I don’t know if it’s important or not but I’ll be using Linux on this new pc. Thanks!

I upgraded my PC recently, and did a clean install of windows 10. I'm now using an ASUS TUF Gaming Z690-Plus Wifi D4 motherboard with my old G Skill Trident Z RGB sticks that worked with OpenRGB before upgrading. So the issue is likely the motherboard. I just don't know why it's not reading the memory. I tried enabling the SPD Write option in the BIOS, but that didn't solve it. OpenRGB recognizes everything else that's plugged in, keyboard, mouse, even the RGB zones built into the motherboard. I don't have any other programs that would control RGB, and don't see any services running that would either.

Hello When I run openrgb -v I get the message of the title. I'm curious about why that's happening.

Full log

----------------------------------------------------- | Start device detection | ------------------------------------------------------ Initializing HID interfaces: Success ------------------------------------------------------ | Detecting I2C interfaces | ------------------------------------------------------ Registering I2C interface: /dev/i2c-3 Device 1002:73DF Subsystem: 1EAE:6601 [i2c_smbus_linux] Failed to read i2c device PCI device ID Registering I2C interface: /dev/i2c-10 Device 0000:0000 Subsystem: 0000:0000 Registering I2C interface: /dev/i2c-1 Device 1022:790B Subsystem: 1849:790B [i2c_smbus_linux] Failed to read i2c device PCI device ID Registering I2C interface: /dev/i2c-17 Device 0000:0000 Subsystem: 0000:0000 Registering I2C interface: /dev/i2c-8 Device 1002:73DF Subsystem: 1EAE:6601 Registering I2C interface: /dev/i2c-15 Device 1002:164E Subsystem: 1002:164E Registering I2C interface: /dev/i2c-6 Device 1002:73DF Subsystem: 1EAE:6601 Registering I2C interface: /dev/i2c-13 Device 1002:164E Subsystem: 1002:164E Registering I2C interface: /dev/i2c-4 Device 1002:73DF Subsystem: 1EAE:6601 [i2c_smbus_linux] Failed to read i2c device PCI device ID Registering I2C interface: /dev/i2c-11 Device 0000:0000 Subsystem: 0000:0000 Registering I2C interface: /dev/i2c-2 Device 1022:790B Subsystem: 1849:790B Registering I2C interface: /dev/i2c-0 Device 1022:790B Subsystem: 1849:790B [i2c_smbus_linux] Failed to read i2c device PCI device ID Registering I2C interface: /dev/i2c-18 Device 0000:0000 Subsystem: 0000:0000 [i2c_smbus_linux] Failed to read i2c device PCI device ID Registering I2C interface: /dev/i2c-9 Device 0000:0000 Subsystem: 0000:0000 [i2c_smbus_linux] Failed to read i2c device PCI device ID Registering I2C interface: /dev/i2c-16 Device 0000:0000 Subsystem: 0000:0000 Registering I2C interface: /dev/i2c-7 Device 1002:73DF Subsystem: 1EAE:6601 Registering I2C interface: /dev/i2c-14 Device 1002:164E Subsystem: 1002:164E Registering I2C interface: /dev/i2c-5 Device 1002:73DF Subsystem: 1EAE:6601 Registering I2C interface: /dev/i2c-12 Device 1002:164E Subsystem: 1002:164E ------------------------------------------------------ | Detecting I2C devices | ------------------------------------------------------ Loaded plugin OpenRGB E1.31 Receiver Plugin [ENE SMBus] Detection failed testing register A0. Expected 00, got FFFFFFFF. [ENE SMBus] Detection failed testing register A1. Expected 01, got FFFFFFFF. [ENE SMBus] Detection failed testing register A2. Expected 02, got FFFFFFFF. [ENE SMBus] Detection failed testing register A3. Expected 03, got FFFFFFFF. [ENE SMBus] Detection failed testing register A4. Expected 04, got FFFFFFFF. [ENE SMBus] Detection failed testing register A5. Expected 05, got FFFFFFFF. [ENE SMBus] Detection failed testing register A6. Expected 06, got FFFFFFFF. [ENE SMBus] Detection failed testing register A7. Expected 07, got FFFFFFFF. [ENE SMBus] Detection failed testing register A8. Expected 08, got FFFFFFFF. [ENE SMBus] Detection failed testing register A9. Expected 09, got FFFFFFFF. [ENE SMBus] Detection failed testing register AA. Expected 0A, got FFFFFFFF. [ENE SMBus] Detection failed testing register AB. Expected 0B, got FFFFFFFF. [ENE SMBus] Detection failed testing register AC. Expected 0C, got FFFFFFFF. [ENE SMBus] Detection failed testing register AD. Expected 0D, got FFFFFFFF. [ENE SMBus] Detection failed testing register AE. Expected 0E, got FFFFFFFF. [ENE SMBus] Detection failed testing register AF. Expected 0F, got FFFFFFFF. ------------------------------------------------------ | Detecting I2C PCI devices | ------------------------------------------------------

------------------------------------------------------ | Detecting HID devices | ------------------------------------------------------

Hello.

My ram was detected automatically.

My Motherboard was not and i get this error every time. The motherboard rgb is on even when PC is shut off. I assume because of this error?

I would like assistance with my motherboard and what values do i need to put into those fields. Or where do i find those values myselfe...

Thank you for any help.

!

Hi,

OpenRGB doesnt open when i try to start it. It loads for 2 seconds on my mouse, then absoluty nothing happens.

A few days before everything was working fine.

I tried deleting all files and redownloading several times.

I did try to run as admin.

I see no tasks on my task manager related to OpenRGB.

Help would be very appreciated! Thank you :)

Hi everyone, I'd like to understand if I can set up my RGB LEDs to change colors based on the CPU temperature. While searching, I found conflicting information on websites and communities, some stating it could cause damage while others claim it works fine. Can I do it without any risks?

I have an ASRock AB350 Gaming ITX motherboard with ASRRGBLED installed, which updated the firmware to manage the LEDs. However, I can't seem to find the version anywhere.

I've also installed OpenRGB (version 0.9), which can detect various devices with LEDs, including the motherboard itself, and I can successfully set the colors using both OpenRGB and ASRGBLED. I want to set up the motherboard's LED color based on CPU temperature. Googling, I found the Hardware sync plugin, which I installed successfully.

However, while setting up the "measurement," I noticed an exclamation point next to the motherboard, indicating it doesn't have "direct mode," and using an effect could damage the flash or controller. Googling, I found some users claiming to have damaged the motherboard, while others use OpenRGB without issues. Can anyone help me understand if I can use OpenRGB to set up temperature-based LED changes on the motherboard?

I have a logitech g733 and its listed as compatible device both in stable and experimental builds. I've tried both and my headset is still not recognized. Also tried with and without usb cable just in case and the issue persists.

My rear fan RGB stopped working when it was connected to a Corsair RGB hub. I originally had one RGB hub and one Corsair Commander Core. I bought a Corsair Commander Core XT over the weekend to replace the RGB hub and I installed it. It partly fixed it because my rear fan now lights up in white, but OpenRGB hasn't been able to detect the rear fan RGB yet. I haven't been able to control the fan RGB and change the color as a result. I did not connect the Commander Cores up to each other yet. The Commander Core XT has an optional 3 pin RGB C header and one USB 2.0 headers that I did not connect up. Should I try connecting either of those from the XT to the other Commander Core?

My health and mana bars in #lastepoch are now displayed in the real-world!

• Twitch
• Discord

Hello! Fedora 39, I've been stumped by this issue for a long time.

I have 4 DDR4 sets of 8 GB G.SKILL Trident Z RGB.

I tried the latest Flatpak, RPM as well as building the master branch for source, but every version can't find Trident Z in the "Supported Devices" section, and it doesn't show up under Devices.

I validated that the i2c modules were loaded, and the udev rules were put in place, both using the RPM and by running the script provided over at https://openrgb.org/udev.html

When running OpenRGB, in the terminal, I get:

[i2c_smbus_linux] Failed to read i2c device PCI device ID

even when running as sudo.

My motherboard is an AORUS X470 ULTRA GAMING (cringe name, I know), if it makes any difference for i2c support. As a side note, this motherboard has RGB, but it's not detected in OpenRGB. I think it should be supported, and I see it when running openrgb --list-devices -vv, but maybe the revision is wrong.

[Gigabyte RGB Fusion 2 SMBus] Success - Found 'X470 AORUS ULTRA GAMING-CF' in the JSON list [Gigabyte RGB Fusion 2 SMBus] Bus 02 is not a motherboard or the subvendor does not match the one for Gigabyte Technology Co., Ltd., skipping detection [Gigabyte RGB Fusion 2 SMBus] Bus 06 is not a motherboard or the subvendor does not match the one for Gigabyte Technology Co., Ltd., skipping detection [Gigabyte RGB Fusion 2 SMBus] no devices found [Gigabyte RGB Fusion 2 SMBus] detection end

Please let me know if further details are required.

TIA!

So...yeah. Just that. I have Linux Nobara (Fedora-based) and I was just testing a plugin (Open RGB Effects). I downloaded the Debian version, as I noticed it was a .so file...(maybe it would work, whaddayaknow). And so yeah, after loading the plugin, OpenRGB immediately crashed, and now it refuses to open. Error: ``` $ openrgb Attempting to connect to local OpenRGB server. Connection attempt failed Local OpenRGB server unavailable. Running standalone. [i2c_smbus_linux] Failed to read i2c device PCI device ID [i2c_smbus_linux] Failed to read i2c device PCI device ID [i2c_smbus_linux] Failed to read i2c device PCI device ID [i2c_smbus_linux] Failed to read i2c device PCI device ID [i2c_smbus_linux] Failed to read i2c device PCI device ID terminate called after throwing an instance of 'std::bad_alloc' what(): std::bad_alloc Aborted (core dumped)

```

Any ideas? Thanks!

EDIT: I figured this out. When I installed the newer version, it unselected nearly device to scan for. After re-enabling those, it worked.

Howdy!

I installed an experimental version, because my keyboard is not yet supported by the stable 0.9 build. However, when I switched versions, I lost the ability to see my motherboard. The webpage for the experimental builds makes it sound like it's the stable build plus unfinished/untested additions. But that seems not to be the case.

Is there something I'm missing? Or should I just take "experimental" at face value and not use it? Having my keyboard use its built in effects isn't the end of the world.

Motherboard

Gigabyte X6780E Aorus Master

showed 6 zones in the stable build:

• 2 aRGB

• • 1: Sapphire Nitro Radeon RX 7800 XT
• • 2: Arctic Liquid Freezer II 420

• 2 RGB: both unused

• 1 CPU RGB: unused

• motherboard Aorus logo

In the experimental build, my motherboard wasn't listed at all, and instead the Sapphire graphics card was listed by itself; but nothing could be changed on the graphics card (no zones or LEDs accessible, unlike the stable build where I could see them through the motherboard). All the Mode options were simply the ones that exist in the software the graphic card provided.

RGB controller

Razer Chroma ARGB controller

6 zones, all filled with Cooler Master fans

Keyboard

Corsair K70 TKL Champion

Thanks!

Greetings,

I recently started to using OpenRGB and I have encountered issues with my Razer Leviathan V2 X soundbar when I am using OpenRGB Effects Plugin. I'll try to sumarize the issue:

-I want to use SpectrumCycle effect, so all of my hardware are sychronized when cycling different colours -Everything works as expected, although for soundbar – the effect on soundbar's LEDs is excuted, but there are random "flickers" every 5-10 seconds, when all soundbar's LEDs are going off for fraction of second -I am using Windows 11 -I have OpenRGB v0.91

Any suggestions will be very helpful! Thank you in advance for any reply!

You can see example under the following link

alright so openrgb can indeed see my dz60 board and glorious o mouse. but only the moving effects work on the mouse not static. it used to work. for mydz60 when i toggle led and put it in direct mode i change the key lights it does not reflect.but it does reflect on the board if i change the mode on board itself. but even when i save and load profile the board goes back to being blank and it goes into a mode where whatever keys i press it lights up only then https://youtu.be/wZ1r9UUIBRE?si=6lMHFUYUpiI0ljHQ

So for a while now (years) I've been looking for a way to make custom RGB patterns (reactive patterns, hopefully) similar to what I could do on Razer Chroma back when I had one of their DREADFULLY clicky and loud keyboards. I've also tried Signal RGB, but it even though it did detect the keyboard, it could not interface with it.

Hi everyone, My keyboard started doing this a couple months ago where only the right side of it will light up on start up and I have to manually go to OpenRGB to load my profile every time I turn my PC on. When I load my profile manually the whole keyboard lights up so I know it is not an issue with the backlight (unless it is then fml). Sometimes only a small portion (like the picture) doesn't light up, and other times the whole left side doesn't light up, its completely random. I have re-installed OpenRGB already and my keyboard is the only piece of hardware that is having this issue. My PC and mouse load perfectly every time. If anyone could give me advice on how to get my whole keyboard to light up on start I would really appreciate it. Thank you!!!

edit: keyboard is an ASUS ROG Strix Flare is that helps!

Normally, if no plugin is touching my devices, I can just change their brightness using openrgb --brightness 50. But, if I enable any plugin (like Hardware Sync, or, what I have enabled right now, Effects), I can only change my brightness using the brightness slider inside of the plugin, and the CLI command does not work anymore.

Why do I need to change brightness with commands? Well, I'm using OpenRGB to control the lights on my laptop's keyboard and my mouse. That means my DE cannot stop the lights on my keyboard anymore when the screen dims and eventually turns off after a timer as well.

EDIT: I also cannot assign keybinds to decrease my keyboard's brightness anymore since OpenRGB seems to dominate over any other system brightness control when a plugin is in use

Am I missing something, or is this not implemented yet?

ok here is everything it detected:https://imgur.com/a/bwbqiMw it didnt detect thermaltake fans. i also have asrock xtx gpu and x670 steel legend mobo which both have rgb but only the steel legend was detected. the dz60 is my custom board which is fine it alr has custom firmware to work with openrgb. now the corsair commander core only changes the AIO Panel rgb (but not really it still goes back to its original hardware lighting setup from icue) and not the fans connected to it. it does not detect the fans at all all the fans have no light for corsair. thermaltake still keeps its profile from the TT rgb app and openrgb is not detecting it. and it wont detect the asrock taichi 7900xtx gpu. any ideas on whats going on?

and something weird is happening now. first of all when my pc is off my mobo light is blue and my keyboard is saved with the rgb profile. but when i boot up my keyboard does not work so i have to unplug it and plug it back in and then it turns blue too like the mobo. https://imgur.com/a/rOZj82M

My rear fan in my desktop PC used to be detected in OpenRGB until about a week ago after I installed some firmware updates for my Asus ROG Strix Z690-A motherboard. All of my 4 fans and my cooler are from Corsair, and three of the fans are plugged into one Corsair Commander Core. The Core is still being detected by OpenRGB, but the rear fan is not anymore. If I recall correctly it is managed by a Corsair RGB header. Additionally, My GSkill RGB RAM works but it is now being detected as a generic ENE DRAM. If I try to rescan devices nothing changes. What should I do?

Hi, I've got an Attack Shark K86 Keyboard, and I can't find it in the list of devices, so i'm wondering how to get it working with openRGB? I'd be grateful for any advice on this, I'm a complete newbie to RGB keyboards etc.

I have the latest stable version. I cannot get the program to actually change any LEDs off my MSI mobo. I also have Corsair RAM and that works just fine. I have 3 RGB fans and two strips all chained to a single ARGB header. The system of course starts with Rainbow but nothing I do changes anything, no matter how I resize the zone (I believe I have either 44 or 32 total LEDs.) Even in Mystic Light itself it doesn’t work! ORGB recognizes my MS board fine on USB; but no changes actually happen. I have a Z490A-PRO. Any help would be much appreciated; I’m one of the many that never want to open the bloated MSI center ever again.

Is there a way for ORGB to control the HW channels on devices (i.e. what transpires when ORGB does not run)?

Hi so I have a Thermaltake water cooler with ARGB leds. It does appear in Asus' Armoury Crate (Aura Sync tab), but not in OpenRGB.

Curiously, I also have a G502 mouse that is appearing in OpenRGB but not in Armoury Crate.

Btw, I mostly want my water cooler to be available in OpenRGB.

Hope you can help me solve this issue.

When I run open RGB my Mouse shows up but not my keyboard and I'm not familiar with how to read hexadecimal so using Wireshark does not help me to add a new keyboard to open RGB

I have a computer running Manjaro Linux with four RGB devices.

1. NZXT Fan and RGB Controller (Detected)
2. NZXT Fan and RGB Controller (Not Detected)
3. Ducky Shine 7 (Detected)
4. HyperX Pulsefire FPS Pro (Not Detected)

All of these devices are supported so I'm not sure why half of them aren't detected. Has anyone had any issues like this?

I recently did some upgrades to my PC. One of them was an MSI Pro B550M motherboard, which OpenRGB detects all the RGB/ARGB headers for. I have an ARGB fan controller/hub plugged into an ARGB header on the motherboard, but I can't get OpenRGB to affect it, not even Mystic Light. Does anybody know why?

Hi I'm looking at

!

and looking at products like: https://lian-li.com/product/uni-fan-tl/, https://lian-li.com/product/galahad-ii-lcd/ . However these products are not listed on OpenRGB devices list. Am I correct to assume, if I use https://lian-li.com/product/uni-hub-sl-controller/ (not sure about V2 or V2.5) to connect these fans and AIO - I can use OpenRGB without any issue?