After updating my keyboard firmware, which cleared my custom QMK firmware, I did some research and found this project, providing OpenRGB support to the keyboard. I was successfully able to flash the custom firmware to the keyboard. However, once I installed OpenRGB it would not find the keyboard, even after I manually added it to the settings (see [this guide]( [GUIDE] How to install OpenRGB on FW16 - #3 by knfn )). Only after I launch OpenRGB using sudo, does the app find the keyboard. Though this workaround seems somewhat “unclean”, as all configuration is then only applied to the root user. Plus you generally shouldn’t start user apps as root.
Thus, I was wondering whether anybody has any ideas on how to mitigate this issue.
PS: I use Arch and am on Wayland (not sure if that could change anything, but the security protocols could somehow mess something up, even though I have all the udev rules correctly set up). Also, I saw that somebody fixed the exact same issue on the guide mentioned above, by uncommenting some specific lines in the udev rules to allow the user account to access the keyboard. I, for one, do not have these lines inside my udev rules and adding them does not seem to fix the issues.
PPS: I wasn’t sure whether I should first try to create an issue on the GitHub link posted above, or whether I should first look for support here. As it seems like a problem that should be solvable without needing to change the firmware, I thought I’d first look here.
