Thanks for your continuous support and attention on ESP BLE Mesh, we are glad to announce that the first beta version of ESP BLE Mesh has been released. Please note this is a temporary BLE Mesh branch on GitHub, we will continue to update. It is now allowed to clone the ESP BLE Mesh project: Branch:...

Because in ESP32, IO capability is set to “Keyboard and Display” by default. So in your case of paring, smart phone acts as keyboard role (need to input passkey) and ESP32 acts as Display role (generate a random passkey and display in the screen). The passkey is received in the GAP event ESP_GAP_BLE...

Hi, Kolban Please refer to function example_write_event_env in “gatt server” example (IDF 2.1) to know more about how to process “write event” packets. If you have received a “write request” packet, what you need to send just only “write response”, so “conn id” and “transfer id” is sufficient and pa...

Hi, Kolban

Those events are generated for IDF debug use and they are not useful for developers. We will delete them in further IDF version.

It is allowed to call “set adv data”, “set scan rsp data” and “start adv” together under the condition that adv data and scan rsp data are all correctly set. Calling “Start adv” before adv data being set correctly will cause that peripheral advertises NULL packets, which may cause unexpected result....

Hi, Kolban In fact, ESP32 supports all 2-Byte UUID, 4-Byte UUID and 16-Byte UUID in advertising packets. But all types of UUID need to be converted to 16-Byte UUID format while setting advertising data using esp_ble_gap_config_adv_data. Bluedroid will re-convert the 16-Byte UUID to original UUID bef...