[Bug Report] incorrect LED mapping on HyperX Alloy origins core

Description of Bug

There is an incorrect LED mapping for the forward slash key (/) on the HyperX Alloy Origins Core keyboard. The control for this key in the OpenRGB interface is not correctly assigned.

Steps to Reproduce:

  1. Open OpenRGB and select the keyboard device.
  2. Locate the "LED" dropdown list.
  3. Select the entry named "Key: /" from the list (or click on the / key in the "LED View").
  4. Attempt to apply a direct color (e.g., solid red).
  5. Observe that the / key on the physical keyboard does not change color.
  6. Return to the "LEDs" dropdown list and find the "blank" entry that is located immediately above the "Key: /" entry.
  7. Select this blank entry and apply a different color (e.g., solid blue).
  8. Observe that the / key on the physical keyboard does change color correctly.

Actual Behavior:

  • When setting a color for the "Key: /" entry, the physical LED on the / key does not change.
  • When setting a color for the blank entry listed directly above "Key: /", the physical LED on the / key does change to the selected color.

Expected Behavior:

The "Key: /" entry in the dropdown list (and its corresponding key in the "LED View") should correctly control the LED of the physical / key. The blank entry should not exist or should not be the mapping for this key.

Attached Log

OpenRGB_20251028_023018.log

Operating System

Windows 11 25H2. OS build 26200.6901

OS - Windows

Hardware Configuration

HyperX Alloy Origins Core

The issue doesn't appear in 1.0rc1. This workaround (using the blank entry) seems to be a new development. For context, in older versions like 1.0rc1, there were no such "blank" entries in the LED list, making this key uncontrollable.

Thanks.