Forum Discussion
Solved
Quest 3 disconnects from classical Bluetooth with ESP32 after 3 seconds
I am trying to link a Quest 3 and an ESP32-WROOM devkit via Bluetooth Classic. The ESP32 is running the following code: #include "BluetoothSerial.h"
String device_name = "ESP32-BT-follower";
B...
The ESP32 moving from the "Connected" to the "Not Connected" device list after pairing is normal for a SPP type connection.
My problem was that I was running the program via Meta Quest Link and had paired the EPS32 with the Quest 3 when I should have paired it with my PC.
Another update: Experiments with the ESP-IDF (Espressif's IDE) and its bt_spp_acceptor example shows that
I (530247) SPP_ACCEPTOR_DEMO: ESP_BT_GAP_CFM_REQ_EVT Please compare the numeric value: 348874
I (532367) SPP_ACCEPTOR_DEMO: authentication success: Meta Quest 3 bda:[c0:dd:8a:82:a6:c7]
W (536407) BT_HCI: hci cmd send: disconnect: hdl 0x81, rsn:0x13
W (536497) BT_HCI: hcif disc complete: hdl 0x81, rsn 0x16
The Quest 3 is successfully authenticated, but then the connection is terminated with "rsn:0x13" which, according to the Bluetooth Core Spec means: "REMOTE USER TERMINATED CONNECTION" i.e. the Quest 3 is terminating the connection.
The Quest and the ESP32 are located right next to each other so signal integrity cannot be the issue. Anyone have any thoughts what might be causing this behavior?