[New Device] Yenkee YKB 30 ODYSSEY

Name of device:

Yenkee YKB 30 ODYSSEY

Link to manufacturer's product page:

https://www.yenkee.eu/mechanical-rgb-keyboard/ykb-30-odyssey

Please select what type of device/interface the device uses:

DeviceTypeUSB

ID information:

ID 320f:5055 Telink ODYSSEY

Please attach screenshots of the device's official control application here:

YENKEE_ODYSSEY_2eoLAdQqIG

List of all modes:

zen_NqMU122QLu zen_On2xC1ENmd zen_lrhQLdavp9 zen_voopEG8W0N

Custom mode (static, per key colour):

YENKEE_ODYSSEY_L52jcNe8R5

All pre-defined modes have different settings (e.g. some support speed change, some can be set to go up or down):

YENKEE_ODYSSEY_rUQqZV7LzD

Please attach device captures here:

I was thus far unable to get Wireshark USB capture working on my Windows VM (KVM/QEMU) and have no bare metal install. USBPcap does run fine separate from Wireshark, but it makes it much harder to tell if I'm capturing what I supposed to be. Also, this method makes it impossible for me to capture plug in messages on Windows.

I'll look into it further, already spent a couple hours on it, I will update this issue when I have more information to share.

I was able to capture the packets on the Linux host while having the keyboard USB forwarded to my VM. This could have affected the capture in some way possibly, but it looks perfectly fine to my newbie eyes.

Custom mode

When you change the current brush colour in custom mode, it changes the colour of the devices outer ring, here are the relevant captures for that:

Outer ring

Switching effects

Changing options for an effect

Switching from first to last effect

Custom is set to all white here and the 2 effects that change based on live information from the OS are omitted (audio wave and shadow). Last effect selected is off.

all_modes_to_off-custom_all_white-no_system_info_modes.pcapng

Opening the software after replug

(quit software, unplug keyboard, plug it back in, begin capture, start software)

opening_the_software_after_replug.pcapng

Checklist for Step2

  • Name of device
  • A link to the vendors product page has been included
  • The transport bus has been identified and the appropriate label added to the issue.
  • The device ID's have been included for USB or PCI
  • Screenshots of the OEM Application are included
  • There is either, appropriate code examples linked or suitable device captures attached
Edited by Elly