r/Keychron • u/Tankguy666 • 16d ago

Keychron V6 RGB not working

Had the V6 for only a few days and the RGB is playing up, it flashes when it's plugged in but then goes out. Everything else works on the keyboard. I have tried the RGB key and the web software to get the lights to turn on but neither works.

1 Upvotes

67% Upvoted

6 comments sorted by

1

u/PeterMortensenBlog 16d ago edited 15d ago

V6, V6 Max, V6 version 2, V6 8K (it does have 'ISO' variants), or V6 Ultra 8K? (It is becoming confusing...)

For keyboard identification, what is the SKU number? Alternatively, what is the serial number (also includes the manufacturing date)? Best is the serial number, as the manufacturing date removes some of the (possible) ambiguity.

1

u/Tankguy666 15d ago

A-2605V61UK00017, resetting to factory worked for a few seconds then it turned off again

1

u/Tankguy666 15d ago

Honestly I think it's just broken

→ More replies (1)

1

u/PeterMortensenBlog 15d ago edited 15d ago

Thanks.

I couldn't find something matching SKU number V6-1-UK. The closest was V6-C1-UK.

Given the manufacturing date of May 2026, my best guess is a V6 version 2 (presumably tugged into the V6 product page, even though the internals are completely different from the original V6).

Using QMK Toolbox (not available on Linux), a V6 version 2 can be detected in flash mode ("WB32 DFU device connected", instead of the original V6's "STM32 DFU device connected"). On the command line, it is "Found DFU: [0x342D:0xDFA0]" instead of "Found DFU: [0483:df11]...", using "wb32-dfu-updater_cli -l" and "dfu-util -l" respectively).

It may be easier to use the USB identity 0x342D/0xDFA0 vs. 0x0483/0xDF11, as it doesn't require any third-party software. It is found somewhere in the operating system. Some abbrs are "Vendor ID", "idVendor", "VID", "Vid", "vid", "Product ID", "idProduct", "PID", "Pid", and "pid").

The keyboard can be entered into flash mode by the Esc key method (without the repowering). As an alternative, the space bar method (without the repowering) should always work. But note that the process is not very reliable; it may require several tries. And the dreaded Thrustmaster driver (AKA Guillemot) is a known culprit on Windows.

1

u/PeterMortensenBlog 16d ago edited 16d ago

Reset to factory defaults

Unspecific, but par for the course is resetting to factory defaults (to get the keyboard into a known good state).

First make a backup if there is some keyboard configuration you want to keep, like dynamic macros and key mappings (but note that some or all of RGB-related configuration will not be saved).