Please add the rest of the info as asked.

@hjk321 said in Xbox One Controller won't connect the "official" way but WILL connect via bluetoothctl.:

So at first glance it might seem like a xpadneo issue, but it's actually not

It could be, if your controller has the latest firmware, but xpadneo's version is less than v0.9.2.
Update your RetroPie-Setup script, and then re-install xpadneo. Try pairing the controller again - either through the RetroPie menus or via bluetoothctl.

@mitu
Ok Thanks. Will have a go.

@cir-engineering I’m using six axis and custom hid Sony. Not sure if I need both, but it’s working. I don’t have the ps3 driver installed. Anyway, I started my pi and synced my ps3 controller via Bluetooth as usual, no issue. Turned the controller off by holding down the ps button (important because it will stay as blutooth with charging only) and plugged the usb cable in and the buttons were all messed up. Reconfigured with the usb cable and it was now working fine with usb. Unplugged and Resynced to Bluetooth, and still had no issue.
Try configuring it with the usb cable, make sure the controller is off when you plug it in to be sure your in usb mode.

@fahadshery
Also make sure that it's not a USB3 problem.
RF interference from the USB3 ports on a Raspberry Pi 4 can knock out the 2.4Ghz Wifi band and the Bluetooth randomly. It can work fine one day and not the next.
I would remove any USB3 cables (by putting them in the USB2 ports) and reboot.
I was even forced to use a small USB2 extension cord on my NESPi case just to keep the USB3 SATA adapter stable. (it makes the device work at USB2 speeds)

Better explained here:

It's not Pi specific, but the bad shielding on certain USB3 devices on a Pi can make it worse.

@folly Sounds like great progress! Ingenious work with the PSP battery.

I bet PS2 is decent for emulation, they are powerful enough in retro terms. PSP seems more fun - I like the handheld retro aspect.

I've got an XBox One and a decent laptop as well, I like modern and retro. There is some messing around to get games to work sometimes on Windows - I had trouble with Jurrasic World Evolution this week, took me a day to get it working (it didn't like booting up in anything other than 60hz 1080p). I'm playing Halo Infinite now as well - it is so good for a free game (only the multiplayer is free though).

Try installing the xpadneo driver from RetroPie-Setup (see here on how to install things in RetroPie) and try re-pairing the controller again via Bluetooth.

Dietpi on Orange Pi zero 2w.

Thanks, I'll try!

For my N30, SN30 and my P30 mod kit. I'll update this post when tried. And I'm writing this to find the topic tomorrow evening 😉

Edit: I needed to activate the flashing status.
Followed the rest of your steps though. Did not successfully and stably connect the N64 mod kit yet.

Edit: Best ways of working to connect 8bitdo modkit Bluetooth controller with Retropie on the Orange Pi Zero 2w, so far…

Do not install blueman-manager.
Do not connect via Bluetoothctl in the terminal.

Use Retropie Bluetooth menu to connect to the controller. Assure the /var/lib/bluetooth/MACADDRESS/ does not contain the controller device you wish to connect. Delete the controller file, and also from the cache folder, if any issues occur.

Hope this helps any future Dietpi users.

Reset your controller configuration and re-configure it again in EmulationStation.

@marine88 I use the Plugable 4.0 BT dongle, but run it on a short USB extension cable so I can get line of sight. I use this old docking station, but I expect another of good quality should work (if I were you I'd get a powered one so you can at least take power drain out of the equation): link

Basically, get that Plugable dongle as it's amazing and get a decent USB caddy!

@quicksilver
Oof, I really dropped the ball, sorry about that.

I'll gather much more detailed info and update my post later tonight. Sorry for being so vague.

@psyke83

Love this community. Thanks for a fast response @psyke83 & @mitu.

I ended up hacking your hack in sixaxis-helper.sh.
I basically disabled the whole restart and renaming section by commenting it out.

sixaxis_rename() { local bt_profile="/var/lib/bluetooth/${BLUETOOTH_MAC^^}/${SIXAXIS_MAC^^}/info" if [[ "$(grep -e "^Name=PLAYSTATION(R)3 Controller" -e "^Trusted=true" -c "$bt_profile" 2>/dev/null)" == "2" ]]; then echo "BlueZ <5.48 hack: renaming BT profile to make consistent with kernel module name" # systemctl stop bluetooth # sed 's/.*Name=PLAYSTATION(R)3 Controller.*/Name=Sony PLAYSTATION(R)3 Controller/' -i "$bt_profile" # systemctl start bluetooth exit 0 fi }

The controller paired then.
but like you stated I had to re-config the controller inputs (for BT vs USB).

Digging deeper I compared the two files under var/lib/bluetooth/${BLUETOOTH_MAC^^}/${SIXAXIS_MAC^^}/info for the On-board BT and the Dongle BT addresses.

The file for the on-board BT holds the changes to the renaming "Sony PLAYSTATION(R)3 Controller"
But for the BT dongle - on restart it must overwrite the file again with the old name "PLAYSTATION(R)3 Controller".

Anyway I have a fix that works for me.

Thanks for the info.

Had the same issue with the Xbox One S controller.

https://www.instructables.com/id/Fixed-Setup-for-Xbox-One-Bluetooth-Controller-With/

This fixed it for me, but I suggest that you keep it connected via USB and ditch bluetooth.

If you connect it back via USB cable (because you wanna charge it), once you're battery is charged, and you unplug it, you will have to remove it from devices and register it again... it's a pain in the butt.

I had that problem try remapping your controls in retro arch I had to hold the right trigger down for the control to work I retro arch till I re mapped.

Also try Installing the xpadneo drivers seems to work for me I then have to update the xpad drivers for wired my after glow wired controller to work

@mitu

Just deleting the ps3 drivers was enough to stop the notice and let me exit the menu without disconnecting the dualshock4. Thanks so much!

@mitu

Sorry, can you please explain me how i do this>?
warm reboot - normal reboot, cold reboot - shutdown then remove the power