1.) How to avoid deletion of bonded remote device (mobile) after power cycle of device ? (We are using Thunderboard EFR32BG22)
2.) How to send notification from ble device to mobile over bluetooth ?
Hello vinay singh,
>1.) How to avoid deletion of bonded remote device (mobile) after power cycle of device ? (We are using Thunderboard EFR32BG22)
The bond information is stored automatically in the NVM when a bond is created. Make sure you don't delete the bondings in the boot event and your bonding information should be kept after a power cycle of the EFR32 device.
>2.) How to send notification from ble device to mobile over bluetooth ?
Check our documentation and guides in doc.silabs.com.
More specifically for sending a notification, you can check the:
Hello Jesus Grillet,
Thank you for your response !
I Followed the below link and created pairing process events for autoconnection and saving bonding with remote device :-
1.) In our mobile Bluetooth settings it only shows the device is paired but doesn't show it is connected for most of the GATT Profiles.
But for HID Over GATT Profile i am able to see connected in mobile Bluetooth settings.
2.) Once mobile Bluetooth is off the connection gets closed for most of the GATT profiles (I confirmed by debug print in event "sl_bt_evt_connection_closed_id").
3.) When mobile Bluetooth is turned on it doesn't open the connection again (simple word "autoconnection").
But in Case of HID over GATT Profile the EFR device gets autoconnected .
1.) Why only for HID Over Gatt profile I can observe connected in mobile Bluetooth settings ?
2.) Why autoconnection is only working in HID Over Gatt profile ? (not for any other Gatt profile)
Please refer any link or document to achieve above scenarios without the dependency of HID Over GATT profile.
Thank You !
Hello vinay singh,
Bluetooth Low Energy devices are not paired using the same process as classic Bluetooth devices are. Instead, everything is typically done at the application level, rather than in the main Bluetooth settings area of your client device. In this case HID over GATT profile is a special case that allows the device to appear in the Bluetooth settings because it is a profile that it is recognized by the OS.
Most of the GATT profiles and services need to be handled in application, meaning that you need to use a BLE application like EFR connect which is a development app or create your own custom mobile application that handles BLE scanning, connecting, GATT operations, etc.
You can find the source code for both the Android and iOS EFR Connect applications in the following links:
These questions are more related to Mobile Phone BLE app development, so I would recommend that you reach out to your mobile phone OS development documentation and support.