espressif / esp-at

AT application for ESP32/ESP32-C2/ESP32-C3/ESP32-C6/ESP8266
Apache License 2.0
883 stars 794 forks source link

ESP32-C6 AT Firmware v4.0.0.0 does not support write no reponse command as BLE client #840

Open xinkunlong opened 4 months ago

xinkunlong commented 4 months ago

Answers checklist.

General issue report

ESP32-C6 AT Firmware v4.0.0.0 does not support write no reponse command as BLE client

09:14:04.436 -> AT+BLEGATTCCHAR=0,3
09:14:04.438 -> +BLEGATTCCHAR:"char",0,3,1,0x000001BF5F01000000004F4D2D4F5441,0x18
09:14:04.444 -> +BLEGATTCCHAR:"char",0,3,2,0x000001BF5F02000000004F4D2D4F5441,0x04
09:14:04.450 -> +BLEGATTCCHAR:"char",0,3,3,0x000001BF5F03000000004F4D2D4F5441,0x1a

BLEGATTCCHAR:"char",0,3,2,0x000001BF5F02000000004F4D2D4F5441,0x04(Not Supported)
09:20:03.499 -> AT+BLEGATTCWR=0,3,2,,2
09:20:03.499 -> 
09:20:03.503 -> AT+BLEGATTCWR=0,3,2,,2
09:20:03.507 -> >1234
09:20:06.400 -> 
09:20:06.403 -> 
09:20:06.404 -> 
09:20:06.404 -> busy p...
09:20:06.404 -> 
09:20:06.404 -> OK

When I write data to this +BLEGATTCCHAR:"char",0,3,2,0x000001BF5F02000000004F4D2D4F5441,0x04, the server cannot receive the data, but when I write data to the other two char, the server can receive the data.

Luxin812 commented 3 months ago

Maybe you can confirm whether the ESP device has written the characteristic value 0x000001BF5F02000000004F4D2D4F5441 by capturing packets. It is possible that the ESP device writes the characteristic value successfully, but the mobile terminal does not report it.