Add Chroma Addressable RGB Controller support#61
Open
jooj211 wants to merge 1 commit into
Open
Conversation
This was referenced May 12, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Notes
OpenRazer added support for this device in openrazer/openrazer#1929 and tested none, static, breathing, spectrum, and wave effects. This patch ports the matching product ID and effect-path coverage used by Razer macOS' existing accessory UI.
Tests
I do not have the physical ARGB controller, so this is based on the upstream OpenRazer implementation and the existing Chroma HDK-compatible code path.