I'm using one Nintendo Switch Pro Controller. But for some weird nintendo reason, its being shown as two seperate devices. Would be no problem, since --ros-args exists. The "fake" device is being listed as /dev/input/js0 or PDP Afterglow Wave Wireless Controller for Switch and it does not output any button inputs at all. The "correct" device (, which again is the same physical device) is shown as /dev/input/js1 "Lic2 Pro Controller" (and i verifed, that the inputs work correctly. But if i try:
~/ros2_ws$ ros2 run joy joy_node --ros-args -p dev:=/dev/input/js1
[INFO] [1761427577.234248382] [joy_node]: No haptic (rumble) available, skipping initialization
[INFO] [1761427577.234299168] [joy_node]: Opened joystick: PDP Afterglow Wave Wireless Controller for Switch. deadzone: 0.050000
^C[INFO] [1761428024.837689295] [rclcpp]: signal_handler(signum=2)
So basically its using js0 instead of the correct js1, even tho i told it to use js0, probabbly because it thinks it has higher priority or something.
And yea thats obviously a big problem, because now i cant use my switch controler for ros stuff anymore.
Proof:
I'm using one Nintendo Switch Pro Controller. But for some weird nintendo reason, its being shown as two seperate devices. Would be no problem, since --ros-args exists. The "fake" device is being listed as /dev/input/js0 or PDP Afterglow Wave Wireless Controller for Switch and it does not output any button inputs at all. The "correct" device (, which again is the same physical device) is shown as /dev/input/js1 "Lic2 Pro Controller" (and i verifed, that the inputs work correctly. But if i try:
So basically its using js0 instead of the correct js1, even tho i told it to use js0, probabbly because it thinks it has higher priority or something.
And yea thats obviously a big problem, because now i cant use my switch controler for ros stuff anymore.
Proof:
