PS4 controller not showing up in Steam (Bluetooth)

Also bluetooth is not turning back on Gnome (bug)?

Where should I report this bug?

Bluetooth hardware details might be useful to start with

/usr/sbin/hwinfo --bluetooth
/usr/sbin/rfkill list

Can you elaborate on the problem you’re encountering?

1: hci0: Bluetooth
Soft blocked: no
Hard blocked: no

It should be able to be accessed via the Gnome 3 menu, that is the problem. It won’t enable from there it is a bug.
https://bugzilla.opensuse.org/show_bug.cgi?id=1172334

Upstream bugs…
https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/issues

This is the bug:
https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/issues/38

Hi
No issues seen here with a bluetooth dongle… disable/enable works fine.

@OP, what is your bluetooth hardware?

What command to show that?

The hwinfo command I gave you back in post #3.

Doesn’t show anything… Bug?

53: USB 00.2: 0000 Unclassified device
[Created at usb.122]
Unique ID: 2B3P.5usWtnvfTL2
Parent ID: FZIx.7qWCOCfUJwE
SysFS ID: /devices/pci0000:00/0000:00:12.0/usb8/8-2/8-2:1.2
SysFS BusID: 8-2:1.2
Hardware Class: unknown
Model: “Broadcom BCM20702A0 Bluetooth 4.0”
Hotplug: USB
Vendor: usb 0x0a5c “Broadcom Corp.”
Device: usb 0x21e8 “BCM20702A0 Bluetooth 4.0”
Revision: “1.12”
Serial ID: “5CF3706B57C1”
Driver: “btusb”
Driver Modules: “btusb”
Speed: 12 Mbps
Module Alias: “usb:v0A5Cp21E8d0112dcFFdsc01dp01icFFiscFFipFFin02”
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #69 (Hub)

Bluetooth if turning on and off right now so I closed that bug. Still there is a bug in steam-constroller where the controller when connected doesn’t show up in Steam.

https://bugzilla.opensuse.org/show_bug.cgi?id=1172335

Hi
Alas can’t help, only Xbox wireless controller here and need to fix that package as well to be python3 ready…

What about the output from dmesg when your trying to connect?

It is just udev rules how is that python 2?

Hi
That’s for an xbox wireless controller… one of the tools used is python2 and needs to be python3, it was just a comment…

So in your case, you think it’s a udev rule, so then what is the output from dmesg when you try to connect, what is the output if you think it’s a udev rule from the command udevadm monitor?

udevadm monitor logs:

https://paste.opensuse.org/15157362

Added the log to this bug report: https://bugzilla.opensuse.org/show_bug.cgi?id=1172335