Hi,
We are developing a product that involves ESP32 that communicates with Android/IOs app over BLE. Since we develop software for both sides of the communication, I wanted to ask what is it that we don't need, in terms of "standard" BLE communication. Out ESP32 application should only be accessible by our Smartphone application, and even that is not all - there will be one ESP32 per one Smartphone. Each ESP32 should be uniquely recognized by the matching phone, so if two ESP32s are in vicinity, it the phone will connect to correct ESP32.
I guess ESP32 needs to advertise as usual by sending it's address, but is it necessary to send service UUID? Our Smartphone application knows what it is. Same question is valid for other UUIDs or for maximum character value sizes. Would removal of these fields make the communication any safer?
What would you suggest in terms of security and simplicity of authorization? Do you think bonding is still the best/simplest option?
Thanks in advance for your suggestions.