Re: Mismatched product ids for the ASUS ROG RAIKIRI PRO

[opinijm]

On Tuesday, May 19th, 2026 at 5:19 PM, Dmitry Torokhov <dmitry.torokhov@xxxxxxxxx> wrote:

> Hi Justin,
> 
> On Tue, May 19, 2026 at 01:37:59PM -0400, Justin Opini wrote:
> > Hey Dimity,
> >
> > I had a question on the product id,
> > { 0x0b05, 0x1abb, "ASUS ROG RAIKIRI PRO", 0, XTYPE_XBOXONE },
> >
> > This doesn’t match both my devices so I was wondering if somehow we
> > have similar named devices with need for different product ids or if
> > there was a mistake in the original commit?
> >
> > My relevant entries from lsusb are
> > Bus 001 Device 002: ID 0b05:1a3c ASUSTek Computer, Inc. ROG RAIKIRI PRO
> > Bus 001 Device 003: ID 0b05:1a3c ASUSTek Computer, Inc. ROG RAIKIRI PRO
> >
> > On my system I have ended up using this udev rule for quite some time
> > ACTION=="add", ATTRS{idVendor}=="0b05", ATTRS{idProduct}=="1a3c", GROUP="input", MODE="0660", TAG+="uaccess", TAG+="seat", RUN+="/bin/sh -c 'echo 0b05 1a3c > /sys/bus/usb/drivers/xpad/new_id'"
> 
> I am CC-ing Luke who added this VID/PID comboi to double check, but it
> looks like there are many variants of this controller using the same
> "ROG RAIKIRI PRO" name. For example
> https://github.com/atar-axis/xpadneo/issues/612 talks about
> 0x0b05/0x1abd.
> 

Ah i was thinking about this more. The device has 3 modes of connection, there is Bluetooth(on the Github tracker), and 2.4GHz via USB receiver(which is what I use) as well as USB directly to the device. Not use if this is enough to introduce variants, but I thought it was worth thinking out aloud. Maybe Luke could chime in on usage? In any case is a patch appropriate here to introduce variant?

> Thanks.
> 
> --
> Dmitry
>