Hello there.

I have a yunzii YZ75 keyboard, and I wanted to try to make it work myself :D. There's some software for this keyboard to change RGB lighting on windows, but there is no such software on linux. I've spent the past few weeks capturing the communication between the keyboard on windows for rgb commands, but I think I need some guidance on what to do. I tried sending the bytecode here (attached at end of post), which is for example for setting the RGB to be white. The bytes are always the same for the colors, but I couldn't get it to work. For some reason it connects to three separate hidraw devices. I tried writing to all three (whichever they are), as bellow:

Vendor ID: 0x3151, Product ID: 0x4015, Manufacturer: ROYUAN, Product: Gaming Keyboard, Path: b'/dev/hidraw8'
Vendor ID: 0x3151, Product ID: 0x4015, Manufacturer: ROYUAN, Product: Gaming Keyboard, Path: b'/dev/hidraw9'
Vendor ID: 0x3151, Product ID: 0x4015, Manufacturer: ROYUAN, Product: Gaming Keyboard, Path: b'/dev/hidraw9'
Vendor ID: 0x3151, Product ID: 0x4015, Manufacturer: ROYUAN, Product: Gaming Keyboard, Path: b'/dev/hidraw9'
Vendor ID: 0x3151, Product ID: 0x4015, Manufacturer: ROYUAN, Product: Gaming Keyboard, Path: b'/dev/hidraw9'
Vendor ID: 0x3151, Product ID: 0x4015, Manufacturer: ROYUAN, Product: Gaming Keyboard, Path: b'/dev/hidraw9'
Vendor ID: 0x3151, Product ID: 0x4015, Manufacturer: ROYUAN, Product: Gaming Keyboard, Path: b'/dev/hidraw9'
Vendor ID: 0x3151, Product ID: 0x4015, Manufacturer: ROYUAN, Product: Gaming Keyboard, Path: b'/dev/hidraw10'

I'm really quite a bit lost. If possible could anyone provide me some input? I tried to go to discord but the link seems to be invalid!

I have been trying to figure out if i should get a better controller than the onboard controller on my ASRock motherboard.

The only problem is that it doesn't seem to support enough LEDs (or more than 5V/3A which is cutting it close) or direct mode.

I have been looking at the Razer Controller but the supported devices page and old Reddit posts seem to be torn on how good the support is in OpenRGB.

I mostly just need to get a working direct control since the direct control mode currently makes my ASRock motherboard unbootable (temporarily).

Any suggestions are welcome :)

I'm trying to get my mouse mat to connect but it just doesn't show up. Is it possible to add things that don't normally have a program to control them? It's just a button on the pad.

After I installed the software earlier today my mouse lost the ability to right click, middle click or side click. I disabled the device in the compatiblity section on my computer and functionality was restored, but if there's a fix I'd like to know.

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

[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?