Console not pairing since update to 12.0.0

[thxomas]

I had a working setup on rpi3B with some issues, and after dist-upgrade (bad idea), I cannot connect anymore from the Grip/Order menu.

Joycontrol is indefinitely waiting for Switch to connect :

• hcidump shows request from the Switch, but after some exchanges, it terminates after passkey sent (HCI Auth Failure, Remote Terminated)
• I found that the Device Class is not properly set (even if the command returns correct in python, hciconfig shows 0x000000. Setting manually to 0x002508 is reset to 0x000000 when re-running joycontrol). That may explain the Authentication Failure.
• so now I have doubts about the bluez5 (don't know my previous version), but the SDP seems correctly set (Nintendo Wireless Gamepad with L2CAP+HIDP) However, the AuthenticationRequired=False may not be honoured, another possible explanation to the Auth Failure

[EDIT: unrelated issue fixed.]

I'm trying to fix this before being able to troubleshoot amiibo_writing again. :)

[thxomas]

Update : fixed Device Class setting by doing it AFTER hid.discoverable() in server.py

However, still no pairing from the switch, here is the end of hcidump :

> HCI Event: User Confirmation Request (0x33) plen 10
    bdaddr 94:58:CB:XX:XX:XX passkey 185519
< HCI Command: User Confirmation Request Negative Reply (0x01|0x002d) plen 6
    bdaddr 94:58:CB:XX:XX:XX
> HCI Event: Command Complete (0x0e) plen 10
    User Confirmation Request Negative Reply (0x01|0x002d) ncmd 1
    status 0x00 bdaddr 94:58:CB:XX:XX:XX
> HCI Event: Simple Pairing Complete (0x36) plen 7
    status 0x05 bdaddr 94:58:CB:XX:XX:XX
    Error: Authentication Failure
> HCI Event: Disconn Complete (0x05) plen 4
    status 0x00 handle 12 reason 0x13
    Reason: Remote User Terminated Connection

The rpi seems to reject the passkey although the AuthenticationRequired=False flag. So nothing happens at python level.
Investigating if this is a new default behaviour of the bluez version.

T

[thxomas]

OK, what's the practice on git ? Rename an issue or create a new one ?
I didn't notice the update to 12.0.0... 🤔 so this issue is merely caused by the console, not linux...

[thxomas]

Went a step further in the pairing process, by setting a bt-agent to accept the passkey.
Next step is failing after " Link Key Notification"

[thxomas]

If anyone interested : After gathering info from various projects, I managed to get the amiibo_writing branch work on raspberry pi 3, latest raspbian buster.
Amiibo read/write is not yet functional, but initial pairing works and then using reconnect gives a stable connection to the switch (I was able to launch BOTW from Home menu, load a save, and trigger amiibo reading, but was greeted by "Connect a controller that can read amiibos...").

Please be aware it is still manual, and not ready for easy sharing. Steps to reproduce :

• Change RPi BT MAC address to get in Nintendo OUI range : I just changed the first 3 byte of the original to 94:58:CB
  hcitool cmd 0x3f 0x001 0xbe 0x13 0x37 0xCB 0x58 0x94 (MAC bytes in reverse order
  or
  use the bdaddr tool
• Disable extra SDP Profiles by setting ExecStart command in systemd /lib/systemd/system/bluetooth.service to :
  ExecStart=/usr/lib/bluetooth/bluetoothd -C -P sap,input,avrcp
• Force default device class (I noticed bluez tends to set this value at unwanted times) in /etc/bluetooth/main.conf :
  Class = 0x002508
• Set default hostname in /etc/machine-info :
  PRETTY_HOSTNAME=Pro Controller
• Configure an Agent to negotiate pairing security : I used the test/simple-agent provided in bluez source, and slightly modified it to accept anything without blocking prompt. Launch it in the background.
  ./simple-agent &
• Modify server.py by swapping hid.discoverable() and set_class()

        # start advertising
        hid.discoverable()

        # set the device class to "Gamepad/joystick"
        await hid.set_class()

When this is done : try pairing..
sudo ./run-controller.py PRO_CONTROLLER
and go to Grip Screen, connection works ! However if you send 'a' command, the menu exits, but "ERROR - Connection lost"

Now if you reconnect with -r option, the connection keeps ON, until trying NFC read/write.

Of course, these steps should be in some way integrated to the project, but at least the POC is done.
Another drawback, is that the RPi is somewhat dedicated only to emulating a joycon, and trying any other BT service would break it..

Thanks to @Brikwerk from NXBT project for having found the missing information to reach this state

ref. Brikwerk/nxbt#18

I need amiibos back ! 💪
T.

[pokemon-bot]

I am trying your solution on my HP laptop with intel bluetooth on ubuntu and I followed your steps but I got stuck
this file is missing /etc/machine-info
and where do I get test/simple-agent ? and what is the modification I need to change ?

[thxomas]

I am trying your solution on my HP laptop with intel bluetooth on ubuntu and I followed your steps but I got stuck
this file is missing /etc/machine-info

This file is specific to the RPi I think. this is the way bluez gets the hostname for bluetooth. On Ubuntu, you may check /etc/bluetooth/main.conf for the Name setting (top of file, just before "Class")

and where do I get test/simple-agent ? and what is the modification I need to change ?

The file is an example found in the bluez source package. I attached my (dirty) modified version to this comment (rename .py or remove extension) Unlike joycontrol it runs on python2, you may need to apt install python-bluez

simple-agent.txt

Does the MAC Address change have an effect on the Intel chipset ?
Good luck
T.

[thxomas]

Run joycontrol, then, in another shell session, check your controller status by comparing to this :

/home/pi# bluetoothctl show

Controller 94:58:CB:96:BC:79 (public)           #MAC Address must be in Nintendo OUI range
        Name: Pro Controller                    #Name and Alias like a true controller
        Alias: Pro Controller
        Class: 0x00002508                       # Set by joycontrol
        Powered: yes
        Discoverable: yes
        Pairable: yes
        UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)   # Default profile (accepted by switch)
        UUID: Human Interface Device... (00001124-0000-1000-8000-00805f9b34fb)   # Gamepad profile set by joycontrol
        UUID: PnP Information           (00001200-0000-1000-8000-00805f9b34fb)   # Default profile (accepted by switch)
        UUID: Generic Access Profile    (00001800-0000-1000-8000-00805f9b34fb)   # Default profile (accepted by switch)
        Modalias: usb:v1D6Bp0246d0532
        Discovering: no

The simple-agent must be running detached, or in another session, it will auto accept pairing. Once paired, you don't need it to be running to reconnect with -r option.

T

[JaredEzz]

Thanks to @thxomas for providing steps to troubleshoot.

1. Change RPi BT MAC address to get in Nintendo OUI range
I installed the libbluetooth-dev & bdaddr tools to help with this, follow instructions here.
I'm using a raspberry pi 2 with a usb bluetooth connector, this was the info before the change:

Manufacturer:   Cambridge Silicon Radio (10)
Device address: 00:1A:7D:DA:71:13

and after the change:

Manufacturer:   Cambridge Silicon Radio (10)
Device address: 00:1A:7D:DA:71:13
New BD address: 94:58:CB:DA:71:13

Address changed - Reset device manually

2. Disable extra SDP Profiles
I changed ExecStart in /lib/systemd/system/bluetooth.service from
ExecStart=/usr/lib/bluetooth/bluetoothd --noplugin=input to
ExecStart=/usr/lib/bluetooth/bluetoothd -C -P sap,input,avrcp

3. Force default device class
I changed Class in /etc/bluetooth/main.conf (under the [General] section at the top) from
#Class = 0x000100 to
Class = 0x002508

4. Set default hostname in /etc/machine-info
I also did not find the machine-info file on my raspberry pi, could be because of the linux version, rpi version, etc.
I changed Name in /etc/bluetooth/main.conf from
Name = BlueZ to
Name = Pro Controller

5. Configure an Agent
I copied the contents of the prived simple-agent.txt into simple-agent on my rpi, made it executable and ran it, and got some missing packages errors. I installed the recommended package python-bluez, as well as python-gobject, python-dbus because of import errors, and I got the following error:

ERROR:dbus.proxies:Introspect error on :1.5:/org/bluez: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.AccessDenied: Rejected send message, 2 matched rules; type="method_call", sender=":1.39" (uid=1001 pid=1087 comm="/usr/bin/python ./simple-agent ") interface="org.freedesktop.DBus.Introspectable" member="Introspect" error name="(unset)" requested_reply="0" destination=":1.5" (uid=0 pid=280 comm="/usr/lib/bluetooth/bluetoothd --noplugin=input ")
Traceback (most recent call last):
  File "./simple-agent", line 161, in <module>
    manager.RegisterAgent(path, capability)
  File "/usr/lib/python2.7/dist-packages/dbus/proxies.py", line 70, in __call__
    return self._proxy_method(*args, **keywords)
  File "/usr/lib/python2.7/dist-packages/dbus/proxies.py", line 145, in __call__
    **keywords)
  File "/usr/lib/python2.7/dist-packages/dbus/connection.py", line 651, in call_blocking
    message, timeout)
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.AccessDenied: Rejected send message, 2 matched rules; type="method_call", sender=":1.39" (uid=1001 pid=1087 comm="/usr/bin/python ./simple-agent ") interface="org.bluez.AgentManager1" member="RegisterAgent" error name="(unset)" requested_reply="0" destination=":1.5" (uid=0 pid=280 comm="/usr/lib/bluetooth/bluetoothd --noplugin=input ")

Moving on to try the rest without the agent but wanted to post in case there's a simple fix for this error

[thxomas]

Try sudo or running the agent as root

[JaredEzz]

6. Modify server.py by swapping hid.discoverable() and set_class()
did this ^^ self-explanatory

FINAL
ran sudo ./run-controller.py PRO_CONTROLLER and it ran as expected. Paired, connected, then disconnected after a command or two.
Then ran the command with the -r flag and everything works as expected! Turns out I didn't need the agent. Thank you so much @thxomas

[thxomas]

For more insights if you want, find and install bluez-utils, to get tools liike btlon or btmgmt. They give good clues to the cause of problems (Switch not connecting at all, Authentication errors, etc...)

[JaredEzz]

I spoke too soon. It disconnected after a minute or so