+BLECONN only reported once

[mrx23dot]

Answers checklist

• [X] I have read the documentation ESP-AT Programming Guide and the issue is not addressed there.
• [X] I have used the latest released firmware or have updated my ESP-AT branch (master or release) to the latest version and checked that the issue is present there.
• [X] I have searched the issue tracker for a similar issue and not found a similar issue.

AT+GMR

AT version:3.2.0.0(s-ec2dec2 - ESP32 - Jul 28 2023 07:05:28) SDK version:v5.0.2-376-g24b9d38a24-dirty compile time(6118fc22):Jul 28 2023 10:14:50 Bin version:v3.2.0.0(PICO-D4)

ESP-AT Firmware Source

ESP32-PICO-D4-AT-V3.2.0.0.zip from website

Hardware Information

esp32-pico-mini-02

Power Supply used

USB

What is the expected behavior?

On second connect it should still report

+BLECONN:0
and
+BLEDISCONN:0

What is the actual behavior?

only reports first connection with

+BLECONN:0
and
+BLEDISCONN:0

Probability of recurrence

always

AT+SYSRAM?

D,ESPU:237,01-01-2017 00:00:04,tx:AT+SYSRAM? D,ESPU:209,01-01-2017 00:00:04,rx:+SYSRAM:104272,101652

Steps to reproduce

AT+BLEINIT=2
OK
AT+BLEGATTSSRVCRE
OK
AT+BLEGATTSSRVSTART
OK
AT+RFPOWER=84,0,0,0
OK
AT+BLEADDR=1,"d9:2c:b0:e1:26:19"
OK
AT+BLEADVPARAM=32,64,0,1,7,0,,
OK
AT+BLEADVSTART

connect with nRF app

+BLECONN:0,"61:c8:b3:ec:f2:6f" +BLECONNPARAM:0,0,0,6,0,500 +BLECONNPARAM:0,0,0,39,0,500

disconnect +BLEDISCONN:0,"61:c8:b3:ec:f2:6f"

connect with nRF app for second time.

It connects, but doesn't send more:

+BLECONN:0,"61:c8:b3:ec:f2:6f"
+BLEDISCONN:0,"61:c8:b3:ec:f2:6f"

AT command port output

see above

AT log port output

not needed to reproduce

More Information.

No response

[mrx23dot]

Looks like it stops advertising after disconnection,

what's the point of having connection id in +BLECONN:0 if this is the case?

[mrx23dot]

Also, first +BLECONN:0 doesn't seem to come if I reboot BLE server side (same code as above) with already connected client, and client auto reconnects.

[Luxin812]

@mrx23dot

1. Have you confirmed that the second connection to nrf app has created BLE successfully? The broadcast will be stopped after the connection establishment fails or succeeds. If you need to re-create the BLE connection, please re-execute AT+BLEADVSTART to turn on the BLE broadcast (this is a protocol requirement)

2. Because when the client establishes a BLE connection with the device as the BLE server, the reason why the BLE server executes the AT+BLECONN command to connect is just a false connection, and it only needs to be returned.