Xbox One S Bluetooth Controller Error when connecting
Pi Model: (B, B+, 2 B etc..): Raspberry Pi 3
RetroPie Version Used: (3.6, 3.8.1, 4.01 etc..): 4.02
Built From: (Pre made SD Image on RetroPie website, Berryboot, or on top of existing OS etc..): SD Image from Website
USB Devices connected: Logitech Wireless Keyboard dongle
Controller used: Xbox One S Bluetooth
Error messages received:
Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/dbus/connection.py", line 604, in msg_reply_handler
File "/home/pi/RetroPie-Setup/scriptmodules/supplementary/bluetooth/bluez-simple-agent", line 118, in pair_reply
File "/home/pi/RetroPie-Setup/scriptmodules/supplementary/bluetooth/bluez-simple-agent", line 38, in dev_connect
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
File "/usr/lib/python2.7/dist-packages/dbus/connection.py", line 651, in call_blocking
dbus.exceptions.DBusException: org.bluez.Error.NotAvailable: Operation currently not available
How to replicate the problem:
Open RetroPie Menu
Select "Register and Connect to Bluetooth Device"
Push sync button on Xbox One S Controller
Controller Discovered, Select controller
Receive aforementioned error
Also attempted option 2 "Keyboard Display"
Receive "An Error occurred connecting to the bluetooth device (creating device failed: org.bluez.Error.AlreadyExists:AlreadyExists)
I am happy to provide any model numbers or logs from the Pi or execute any tests recommended.
Doubt you will be able to pair it via the bluetooth gui. Does it work via cable?
You could try manually pairing via
bluetoothctl(you will need to google for tutorials using bluetoothctl) but I have no idea if it's compatible etc.
The Xbox One S controller does not work either wired or wireless.
I attempted to manually sync the controller from command line and was not able to succeed.
I work in software troubleshooting for a living so I think that there is something not contained in the drivers that is causing me pain.
I am willing to provide MAC addresses, Fiddler/Wireshark captures of anything needed.
Let me know what you need.I most likely can get it for you.
It was my understanding only certain models of this pad works, if at all.
Was a big thread about it on the original forum going back quite a while.
Trying to fiddle with this as well and it's a huge pain. From what I can tell it's got something to do with recognition software in the controller itself that required a Windows 10 register in the drivers of the device it's connected to. Which, of course, means that these shysters at Microsoft incorrectly labeled this controller as "Bluetooth".
Fack. Bought this thing to be my primary retropie controller because of its comfort. I have a few Pc games so it's not a complete loss but getting circular logic from the Bluetooth registry as you've shown above is not promising for future support.
@a7mag3ddon could you provide the link for this conversation if you know where it is? Spent about a half hour looking around the net for similar discussions and came up empty.
There's loads. Search Xbox One Pad retropie in your favourite search engine
This is specifically the Xbox One S controller. Not just an Xbox One controller.
The Xbox One S controller is supposedly Bluetooth instead of the wonky proprietary thing that requires an extra dongle.
I too bought one thinking I could use it as my primary RetroPie controller and it was pretty frustrating finding out it wouldn't connect.
Xbox one is also Bluetooth.
It's not. That's why the sell the extra Wireless Dongles for them to work Wirelessly with Windows 10.
"Another way to tell: On Bluetooth-supported controllers, the plastic around the Xbox button is part of the face of the controller. On controllers without Bluetooth, the plastic around the Xbox button is part of the top, where the bumpers are."
@igmothemagus here are some links that I think explain a little better what I think (along with these people) is going on.
Granted, I don't use proper linux on my PC so I haven't had the chance to test it properly. Of course, the damn thing works perfectly on Windows 10.
Seems to me like Microsoft intentionally held back functions of the bluetooth drivers of the controller itself so that integration with specificity only to their OS with the correct recognition coding is required. Scummy, anti-consumer and lying as well, tbh.
@igmothemagus this. Both controllers are not the same- the architecture of the new controller was moved to bluetooth because it was a simpler and faster band than the one they were apparently using for the original. There was a distinct attempt to brand this new controller as "Bluetooth", even at their E3 conference.
Of course, that didn't stop them from attempting to keep it as exclusive to their platform as they possibly could. The Linux kids are having all sorts of problems using it wireless via Bluetooth on their PC's. It's a mess.