RetroPie forum home
    • Recent
    • Tags
    • Popular
    • Home
    • Docs
    • Register
    • Login
    Please do not post a support request without first reading and following the advice in https://retropie.org.uk/forum/topic/3/read-this-first

    Multiple Bluetooth controllers of the same model (iPega PG-9021)

    Scheduled Pinned Locked Moved Help and Support
    bluetooth udev
    2 Posts 2 Posters 1.1k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • I
      inversechi
      last edited by

      I have two bluetooth iPega PG-9021 controllers which I have successfully managed to get one working by auto-creating the udev rule within the setup scripts. Which looks like this:

      SUBSYSTEM=="input", ATTRS{name}=="PG-9021", MODE="0666", ENV{ID_INPUT_JOYSTICK}="1"

      However when I connect the other one they seem to keep losing connectivity and it's pretty non-functional. How should this udev rule be setup to handle such? Do I need to add some unique ident e.g. the mac address? What does the last part mean? I'm new to the input system/drivers in linux ;)

      Any help or guidance explaining this would be much appreciated

      1 Reply Last reply Reply Quote 0
      • D
        dikdom
        last edited by dikdom

        Did you manage to solve this?
        My situation is kind the same. I have two controllers, though they are different type than this one.
        Both controllers report themselves as "Gamepad", fortunately with different addresses.
        So in the udev rule instead of specifying its name I used
        ATTRS{address}=="bt address"
        (interestingly with small letters when required: E8:A1:00:.... -> e8:a1:00:... you can check it with the udevadm info -a -n /dev/hidraw0 or hidraw1 command)
        This is where the good story ends.
        From this point the EmulationStation looses, because both of the controllers are recognized with the same name and somehow they got mixed up. Sadly the same happens in the games also.
        Any idea to tell Linux to propagate the BT client on different name than it reports itself?

        1 Reply Last reply Reply Quote 0
        • First post
          Last post

        Contributions to the project are always appreciated, so if you would like to support us with a donation you can do so here.

        Hosting provided by Mythic-Beasts. See the Hosting Information page for more information.