hassan789 wrote:You can see the UUID on scanning, just like you can see the mac.

Yes, but i want to filter my advertising from the server side, and not my scanning.

why can't you whitelist a custom UUID?

I didn't know it was possible ? How can i do that ?

Hello, I am working on a BLE device ( ESP32 ) with a pairing process, which allows only previously bonded device to connect back using C++ BLE library. For that, i use whitelisting to memorize the address, and only advertise to these addresses. The problem i have, is that the address of Android and ...

Hi, I am actually using BLE with ESP32 to interact between an application and a server, and i am working with the nkolban C++ library. I want the peripheral device be in discoverable mode before bonding with a central device, but then go into non-discoverable mode after the initial bonding, to have ...

Ok, i will try to use these functions. I am currently using C++ BLE by Kolban to work with BLE, where should i call these functions ?

Hi everybody, I am currently working on a project in which i want to control a device from an app ( for example, control the gain of a sound, by moving a slider ) with BLE. To do this, the app and the device has both their own characteristic, and they will send a command/answer by writing on these c...

Its happening because advertising packet cant be longer than 31 bytes. When you are advertising 128 bit UUID there is not much space left for device name. With name up to 5 chars it works, but with longer it wont because UUID is no included in advertising due to packet limitations. Oh ok, i underst...

Hi, I have some issues trying to connect a ESP32 Client to another ESP32 Server using BLE C++, with SampleClient and SampleServer : With basic programs, when i run the application on both ESP32, it works well, and the Client can connect to the Server, and then, the server characteristic is written. ...

Ble has this limit, but you treat the long messages as several messages within the limit, dividing them when sending and joining them when receiving by yourself :-) What I do to work with larger messages: - All messages (mobile and esp32) ends with a specific character (in my case \n) - On Android ...

Unless you dont need to send messages longer than about 500-512 bytes you dont have to worry, library will take care of it (have not tested longer messages). Messages longer than mtu are fragmented/defragmented, the issue is with notifications/indications. Those messages are truncated to (mtu - 3) ...