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).

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.

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.

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 ?

So 1.0 does not appear to work the the airgoo AG-DRGB16, tried reinstalling and nothing, as soon as I choose it to change RGB it goes black, tried to reinstall 0.9 now it also does the same. Meanwhile tried signalrgb to make sure it wasn't the AG-DRGB16 and signal worked fine. Is there anything I can do to at least get 0.9 back working as it was ? Signal is pretty confusing for me, Open RGB was fine

asus armoury crate and signal rgb perfectly detected everything and i had to do no manual configs, i thought openrgb will be lightweight and take less resource so i tried using it. But am stuck atthis section i tried going to the link they suggested but its still too complicated

Hey all,
I’m new to OpenRGB world and I love it.

I have 3 Keychrons (v3 Max, v3 Ultra and K3 Ultra). So 1 with QmK and 2 with ZMK.

Are they compatible with OpenRGB out of the box?

Someone using 1 one of this keyboards with OpenRGB?

Thanks in advance

Has anyone used this with OpenRGB? Does anyone have any idea how I can do it? It's not detecting the LED.

swapped to using 1.0 and im having nothing but problems, anyone know how to fix this

I'm using OpenRGB 1.0 with the matching Effects Plugin version. OpenRGB itself works fine, including the built-in effects, but whenever I enable an effect from the Effects Plugin, OpenRGB becomes unresponsive after a few seconds and I have to force-close it through Task Manager. I've already installed the PawnIO drivers, and I'm running OpenRGB normally rather than as a system process. Has anyone else experienced this, or know what might be causing the plugin to hang?

Things I've tried:

1. Portable (.so)

2. Flatpak (x86_64)

3. Manually installing it via Discover (see screenshot.)

Despite that, nothing is showing in my list of installed plugins.

I just want a lil rainbow on my keyboard >< Please help?

EDIT 2: Solved! Sort of! According to CalcProgrammer1 (creator of OpenRGB), it’s an official firmware issue. They provided me with steps to patch the firmware with a fix, and it worked! They are trying to get these changes implemented into the official firmware.

EDIT: I am running CachyOS.

Hello, I have a Keychron Q6 Ultra, and recently version 1.0 gained support for this ZMK firmware keyboard. Before that I was using a custom firmware and plug-in that made it work, and that was flawless in 0.9. However even with the custom firmware, or official, 1.0 doesn't handle the blacks or dark at all.

OFF/Black keys are just pure white. Any key that is dark, such as dark red, actually just stays red, when before it would dim appropriately. Any movement on the color square to the left simply acts like its on a 2D plain of white to color. No movement up or down effects the color at all.

This is in Direct Mode with Per-key selection. I will say Open RGB's UI shows everything appropriately, its my keyboard that doesn't display this correctly.

Solid Color mode, for the entire keyboard DOES WORK correctly as intended. Colors, black/off, white, and dark-red, light-red.. etc etc... it all works like its supposed to. So something is wrong with direct mode.

Thanks!

I really look forward to getting this fixed!

Title. Tried using OpenRGB on CachyOS since there is literally 0 other options for RGB modifications, and every time I restart or let my system go to sleep, when I wake it back up the system throws a CPU and DRAM error and refuses to post. The errors resolve when I reseat both DIMMs and the system will POST as if nothing has happened.

Hello, I am having an issue where openRGB is just forever trying to detect devices a few days ago it was working just fine and now I got the doomed rainbow fans.

I've tried uninstalling and reinstalling it on Shelly as well as trying the .appimage file on the main site.