I just read the article. Good job beavers, and great story!

But it says nothing about dirty water. Just the image here does. Why was the water dirty, is there any info on that?

there are calculations and tables on exactly this, when a machine is to be replaced. Including production and shipment of a new one etc., some should be replaced. Look it up!

i think that was it, thank you! I must have enabled smart contrast which does that.

the classic cronjob workaround works great.

The command /usr/bin/openrgb --profile /home/user/.config/OpenRGB/test.orp runs fine, loads the test.orp setting i saved with openrgb-GUI. Until the keyboard goes back to default after 4 min or so.

Therefore i made a cronjob that does the same, just every 3 minutes: */3 * * * * /usr/bin/openrgb --profile /home/user/.config/OpenRGB/test.orp

correction: nevermind it does not work. Again. They keyboard just resets itself after like a minute, regardless. Don’t understand what is happening.

It works fine now. Uninstalled the openRGB flatplak from the kde neon app store (discover) and instead installed the .deb from the openrgb-website. Now it works with static dimmed LEDs. NICE!