I can add to this that Brownout suggests that the ESP's supply voltage is dropping below some predefined threshold. This could be caused by a number of things, among them the power supply being insufficient, the ESP drawing too much current (likely too much load on the pins), or some big transients ...

Hi tanmath, yes it can be captured. I followed the instructions in this Stackoverflow answer . I'll copy them here in case the link ever goes bad: To capture Bluetooth traffic using Wireshark you will need the BTP software package, you can get it here . Install the package and find the files (usuall...

Hey chucrut,

The connection being closed after pairing is normal for SPP. You should still be able to access the paired device later in your application.

I figured it out. The reason was entirely unrelated to the ESP32 or SPP. The reason I initially thought the Bluetooth Connection was being terminated was because the BluetoothHelper class I was using on the Oculus 3 was returning a "BlueToothNotReadyException" when I tried connecting to the ESP32 de...

This is about the same issue I describe in my other thread What do the acl_disconn_cmpl_stat error codes mean? . However, this is no longer about the meaning of the error codes, which is why I decided to split it out. This might be the same issue as reported by chucrut back in 2023 in their post: Bl...

Hi chucrut! Almost one year later I'm dealing with exactly the same issue with an ESP32-WROOM-32E and a Quest 3. I have created this post before finding yours: https://esp32.com/viewtopic.php?f=19&t=40345 One thing I found is that it may be related to the type of connection. The bt_spp_acceptor uses...

Sorry for double-post but ChatGTP served up the answer: 0x13 is from the Bluetooth Specification and indicates that the remote user terminated the connection. At this point I am led to conclude that it is not the ESP32 that is disconnecting but the Quest 3. The 0x119 may also be related to Bluetooth...

Some additional information, I installed the ESP-IDF and ran the bt_spp_acceptor demo. With that, the output was: I (1157) SPP_ACCEPTOR_DEMO: ESP_SPP_INIT_EVT I (1167) SPP_ACCEPTOR_DEMO: ESP_SPP_START_EVT handle:129 sec_id:55 scn:1 I (1177) SPP_ACCEPTOR_DEMO: event: 10 I (1177) SPP_ACCEPTOR_DEMO: Ow...

I am currently debugging an issue while trying to connect an ESP32 with a Meta Quest 3. The pairing is successful, but then is always terminated 3 seconds later. Setting the error log to verbose gives me: [ 41477] [BluetoothSerial.cpp:609] esp_bt_gap_cb(): ESP_BT_GAP_ACL_DISCONN_CMPL_STAT_EVT ACL di...