Support request for Chicony RGB keyboard (VID: 04f2, PID: 011a) - Acer Predator Helios PH16-71
🖥️ Feature Request: Add support for Chicony RGB keyboard on Acer Predator Helios PH16-71
Summary
Requesting OpenRGB support for the built-in RGB keyboard of the Acer Predator Helios PH16-71. The keyboard uses a Chicony USB HID device with the following identifiers:
-
Vendor ID (VID):
04f2 -
Product ID (PID):
011a -
Device Name (from lsusb):
Chicony Electronics Co., Ltd USB-HID Gaming Keyboard (C)
The RGB lighting is fully functional in Windows using PredatorSense, but OpenRGB does not detect the device under Linux.
🔍 System Information
- Model: Acer Predator Helios PH16-71
- Keyboard: Chicony USB-HID Gaming Keyboard
- Dual Boot: Windows 11 + Parrot OS (HTB edition)
-
Linux Kernel: (insert output of
uname -rhere) - OpenRGB Version: 1.0 RC1 (built from source)
- Root access: Yes
🧪 What I’ve Tried
- Enabled modules:
i2c-dev,i2c-i801 - Ran OpenRGB as root
- Keyboard is detected with
lsusbandlsusb -vshows 4 HID interfaces - Tested USB write access via
hidapiPython scripts - Identified and replayed
Interrupt OUTpackets captured from PredatorSense - Replayed valid RGB color payloads (static red, green, etc.)
- Replayed
SET_REPORT,SET_IDLEandURB_FUNCTION_CONTROL_TRANSFER_EXpackets - Confirmed that even correct packet replay does not alter lighting
🧾 Additional Observations
- RGB lighting resets on boot to a default effect that is not selectable in PredatorSense
- Changing color via PredatorSense requires "Acer Lightning Service" to be running
- If the service is stopped, even PredatorSense can't change lighting
- This suggests vendor-specific HID initialization or locking mechanism
📎 Attached Files
-
USB capture log (from Wireshark/USBPcap on Windows):
chicony_rgb_log.pcapng- Contains sequences for static colors (green, red, orange, violet) and attempted wave effect
- chicony_rgb_log.pcapng
-
Full lsusb -v dump for the device:
lsusb_04f2_011a.txt
🙏 Request
Please consider investigating support for this keyboard model. I’m available to:
- Run additional captures
- Test early support builds
- Collect further debug data
Let me know if any additional information is required.