Open Fuyukiri opened 1 year ago
can i ask if you we're successful in fixing this problem? if not, what OS are you running? is this a virtual machine or a standard installation?
Same here. The configuration OP posted should be a standalone device but not virtual machine. I have issue with builtin BT as well. Here is my configuration:
$ hwinfo --short
cpu:
13th Gen Intel(R) Core(TM) i9-13900K, 1957 MHz
13th Gen Intel(R) Core(TM) i9-13900K, 2033 MHz
13th Gen Intel(R) Core(TM) i9-13900K, 1925 MHz
13th Gen Intel(R) Core(TM) i9-13900K, 3000 MHz
13th Gen Intel(R) Core(TM) i9-13900K, 2030 MHz
13th Gen Intel(R) Core(TM) i9-13900K, 3000 MHz
13th Gen Intel(R) Core(TM) i9-13900K, 2200 MHz
13th Gen Intel(R) Core(TM) i9-13900K, 1937 MHz
13th Gen Intel(R) Core(TM) i9-13900K, 1954 MHz
13th Gen Intel(R) Core(TM) i9-13900K, 3000 MHz
13th Gen Intel(R) Core(TM) i9-13900K, 2094 MHz
13th Gen Intel(R) Core(TM) i9-13900K, 3000 MHz
13th Gen Intel(R) Core(TM) i9-13900K, 2175 MHz
13th Gen Intel(R) Core(TM) i9-13900K, 3000 MHz
13th Gen Intel(R) Core(TM) i9-13900K, 2058 MHz
13th Gen Intel(R) Core(TM) i9-13900K, 3000 MHz
13th Gen Intel(R) Core(TM) i9-13900K, 1414 MHz
13th Gen Intel(R) Core(TM) i9-13900K, 3000 MHz
13th Gen Intel(R) Core(TM) i9-13900K, 1039 MHz
13th Gen Intel(R) Core(TM) i9-13900K, 3000 MHz
13th Gen Intel(R) Core(TM) i9-13900K, 3000 MHz
13th Gen Intel(R) Core(TM) i9-13900K, 3000 MHz
13th Gen Intel(R) Core(TM) i9-13900K, 3000 MHz
13th Gen Intel(R) Core(TM) i9-13900K, 3000 MHz
13th Gen Intel(R) Core(TM) i9-13900K, 3000 MHz
13th Gen Intel(R) Core(TM) i9-13900K, 3000 MHz
13th Gen Intel(R) Core(TM) i9-13900K, 3000 MHz
13th Gen Intel(R) Core(TM) i9-13900K, 3000 MHz
13th Gen Intel(R) Core(TM) i9-13900K, 3000 MHz
13th Gen Intel(R) Core(TM) i9-13900K, 3000 MHz
13th Gen Intel(R) Core(TM) i9-13900K, 3000 MHz
13th Gen Intel(R) Core(TM) i9-13900K, 3000 MHz
keyboard:
/dev/input/event5 SONiX USB DEVICE
/dev/input/event11 IM Networks Virtual HID
mouse:
/dev/input/event7 SONiX USB DEVICE
/dev/input/mice IM Networks Virtual HID
/dev/input/mice Logitech G502 SE HERO Gaming Mouse
monitor:
LG ELECTRONICS LG ULTRAGEAR+
ROG PG32UQX
graphics card:
nVidia VGA compatible controller
Intel Display controller
sound:
Intel Audio device
nVidia GA104 High Definition Audio Controller
storage:
Intel SATA controller
Samsung Electronics NVMe SSD Controller PM9A1/PM9A3/980PRO
Samsung Electronics NVMe SSD Controller SM981/PM981/PM983
ASMedia ASM1062 Serial ATA Controller
network:
wlan0 Intel Wi-Fi 6 AX210 160MHz
eth0 Intel Ethernet Controller I225-V
network interface:
eth0 Ethernet network interface
wlan0 WLAN network interface
lo Loopback network interface
disk:
/dev/nvme0n1 Samsung Electronics NVMe SSD Controller PM9A1/PM9A3/980PRO
/dev/nvme1n1 Samsung Electronics NVMe SSD Controller SM981/PM981/PM983
partition:
/dev/nvme0n1p1 Partition
/dev/nvme0n1p2 Partition
/dev/nvme0n1p3 Partition
usb controller:
Intel USB Controller
bios:
BIOS
bridge:
Intel PCI bridge
Intel ISA bridge
Intel PCI bridge
Intel PCI bridge
Intel Host bridge
Intel PCI bridge
Intel PCI bridge
Intel PCI bridge
Intel PCI bridge
hub:
Genesys Logic USB3.2 Hub
Genesys Logic Hub
Linux Foundation 2.0 root hub
Generic Virtual HUB
Genesys Logic Hub
Linux Foundation 3.0 root hub
Genesys Logic Hub
memory:
Main Memory
bluetooth:
Intel Bluetooth Device
unknown:
FPU
DMA controller
PIC
Keyboard controller
Intel System peripheral
Intel Communication controller
Intel Serial bus controller
Intel RAM memory
Intel SMBus
Serial controller
Micro Star International USB Audio
/dev/input/event4 Micro Star International MYSTIC LIGHT
/dev/input/event10 Logitech G502 SE HERO Gaming Mouse
My Usage:
$ sudo python3
Python 3.11.4 (main, Jun 7 2023, 10:13:09) [GCC 12.2.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import nxbt
>>> nx = nxbt.Nxbt()
>>> ci = nx.create_controller(nxbt.PRO_CONTROLLER)
>>> nx.wait_for_connection(ci)
(wait infinitely after last command) bluetoothctl:
$ sudo bluetoothctl
Agent registered
[bluetooth]# list
Controller F4:A4:75:3F:0C:22 Pro Controller [default]
[CHG] Device 74:84:69:65:6C:64 Connected: yes
[CHG] Device 74:84:69:65:6C:64 Connected: no
[CHG] Controller F4:A4:75:3F:0C:22 PairableTimeout: 0x00000000
[CHG] Controller F4:A4:75:3F:0C:22 DiscoverableTimeout: 0x000000b4
[CHG] Controller F4:A4:75:3F:0C:22 UUIDs: 00001200-0000-1000-8000-00805f9b34fb
[CHG] Controller F4:A4:75:3F:0C:22 UUIDs: 00001132-0000-1000-8000-00805f9b34fb
[CHG] Controller F4:A4:75:3F:0C:22 UUIDs: 0000112f-0000-1000-8000-00805f9b34fb
[CHG] Controller F4:A4:75:3F:0C:22 UUIDs: 00001104-0000-1000-8000-00805f9b34fb
[CHG] Controller F4:A4:75:3F:0C:22 UUIDs: 00001800-0000-1000-8000-00805f9b34fb
[CHG] Controller F4:A4:75:3F:0C:22 UUIDs: 00001133-0000-1000-8000-00805f9b34fb
[CHG] Controller F4:A4:75:3F:0C:22 UUIDs: 00001801-0000-1000-8000-00805f9b34fb
[CHG] Controller F4:A4:75:3F:0C:22 UUIDs: 00001106-0000-1000-8000-00805f9b34fb
[CHG] Controller F4:A4:75:3F:0C:22 UUIDs: 0000180a-0000-1000-8000-00805f9b34fb
[CHG] Controller F4:A4:75:3F:0C:22 UUIDs: 00005005-0000-1000-8000-0002ee000001
[CHG] Controller F4:A4:75:3F:0C:22 UUIDs: 00001124-0000-1000-8000-00805f9b34fb
[CHG] Controller F4:A4:75:3F:0C:22 UUIDs: 00001105-0000-1000-8000-00805f9b34fb
[CHG] Controller F4:A4:75:3F:0C:22 Class: 0x00002508
[CHG] Device 74:84:69:65:6C:64 Connected: yes
[CHG] Device 74:84:69:65:6C:64 Connected: no
[CHG] Device 74:84:69:65:6C:64 Connected: yes
[CHG] Device 74:84:69:65:6C:64 Connected: no
[DEL] Device 74:84:69:65:6C:64 Nintendo Switch
[NEW] Device 74:84:69:65:6C:64 Nintendo Switch
[CHG] Device 74:84:69:65:6C:64 Bonded: yes
[CHG] Device 74:84:69:65:6C:64 Connected: no
[CHG] Device 74:84:69:65:6C:64 Paired: yes
[CHG] Device 74:84:69:65:6C:64 Connected: yes
[CHG] Device 74:84:69:65:6C:64 Connected: no
[CHG] Device 74:84:69:65:6C:64 Connected: yes
[CHG] Device 74:84:69:65:6C:64 Connected: no
[DEL] Device 74:84:69:65:6C:64 Nintendo Switch
[NEW] Device 74:84:69:65:6C:64 Nintendo Switch
[CHG] Device 74:84:69:65:6C:64 Bonded: yes
[CHG] Device 74:84:69:65:6C:64 UUIDs: 0000110a-0000-1000-8000-00805f9b34fb
[CHG] Device 74:84:69:65:6C:64 UUIDs: 0000110e-0000-1000-8000-00805f9b34fb
[CHG] Device 74:84:69:65:6C:64 UUIDs: 00001800-0000-1000-8000-00805f9b34fb
[CHG] Device 74:84:69:65:6C:64 UUIDs: 00001801-0000-1000-8000-00805f9b34fb
[CHG] Device 74:84:69:65:6C:64 ServicesResolved: yes
[CHG] Device 74:84:69:65:6C:64 Paired: yes
[CHG] Device 74:84:69:65:6C:64 ServicesResolved: no
[CHG] Device 74:84:69:65:6C:64 Connected: no
[CHG] Device 74:84:69:65:6C:64 Connected: yes
[CHG] Device 74:84:69:65:6C:64 Connected: no
[CHG] Device 74:84:69:65:6C:64 Connected: yes
[CHG] Device 74:84:69:65:6C:64 Connected: no
[DEL] Device 74:84:69:65:6C:64 Nintendo Switch
[NEW] Device 74:84:69:65:6C:64 Nintendo Switch
[CHG] Device 74:84:69:65:6C:64 Bonded: yes
[CHG] Device 74:84:69:65:6C:64 Connected: no
[CHG] Device 74:84:69:65:6C:64 Paired: yes
[CHG] Device 74:84:69:65:6C:64 Connected: yes
[CHG] Device 74:84:69:65:6C:64 Connected: no
It does shows "Connected" on my switch once or twice but the device never appear in the controller list.
I can pass the demo but can't connect to switch anymore after 1s connection. In web UI, I can see that only in one second it shows connected, then it turns to yellow light and shows connecting.
System:
My gear:
Log:
I am guessing I need to use a usb bluetooth device instead of built-in bluetooth.
Also I am running nxbt in venv since the jinja dependency issue, not sure if this is related.