• Recent
  • Tags
  • Popular
  • Home
  • Docs
  • Register
  • Login
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

Where are bluetooth MAC addresses and other such configs stored?

Scheduled Pinned Locked Moved Help and Support
bluetoothwii u pro contr
5 Posts 2 Posters 1.0k 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.
  • B
    brimby
    last edited by brimby 22 Jun 2019, 18:03

    My WiiU controller always connected great until I updated RetroPie + kernel the other day. But now every time I boot up ES I have to go to Bluetooth settings and tell it to connect to all registered devices (while pressing buttons on my controller) to get it linked up. That's my main problem in case you have any tips for me, but I'm trying to solve this thing on my own, so I'm trying to purge my system of all trace of the controller to start fresh.

    I deleted all mentions of that controller in es_input.cfg and es_temporaryinput.cfg.

    I checked bluetooth.cfg (in configs/all) and the only thing it said was 'connect_mode="default"', so I left that there.

    Where are the other bluetooth options/configs stored? Like MAC addresses and security modes and udev rules all that?

    M 1 Reply Last reply 23 Jun 2019, 00:28 Reply Quote 0
    • M
      mitu Global Moderator @brimby
      last edited by 23 Jun 2019, 00:28

      @brimby The associations are stored in /var/lib/bluetooth, but you can use the Bluetooth menu from the RetroPie setup and 'forget' all registered controllers.

      1 Reply Last reply Reply Quote 0
      • B
        brimby
        last edited by 23 Jun 2019, 18:11

        @mitu Thank you! Do you happen to know which scripts are directly responsible for "keeping an eye out" for incoming bluetooth connections? I feel like maybe something got overwritten on mine when I updated. I only suggest this because, after I updated, my snes/retroarch.cfg got a bunch of overrides written in it that weren't there before. So I'm wondering if the same thing happened to one of the files responsible for bluetooth configuration. To reiterate, I can connect my WiiU controller fine if I manually go to bluetooth settings in the GUI and tell it to connect to all registered devices, but I used to be able to just turn on my controller and autoconnect, which I greatly miss being able to do. Thanks again.

        1 Reply Last reply Reply Quote 0
        • M
          mitu Global Moderator
          last edited by 23 Jun 2019, 18:16

          I don't think RetroPie has it's own handling of registered devices, it just relies on the OS (Linux) for the available/registered devices. You might be stumbling upon a bug in recent Linux kernels - see the 1st pinned topic in this category.
          Re-register the Wii U controller, without any special connection mode selected, and see if it re-connects automatically on power on.

          1 Reply Last reply Reply Quote 0
          • B
            brimby
            last edited by brimby 23 Jun 2019, 18:34

            @mitu I had already tried de/re-registering the controller multiple times to no avail. But I'm going to run that firmware downgrade mentioned in the sticky, and if it fixes things I'll post in the sticky about my experience so that people will know if it affects WiiU controllers too.

            1 Reply Last reply Reply Quote 0
            5 out of 5
            • First post
              5/5
              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.

              This community forum collects and processes your personal information.
              consent.not_received