Search found 18 matches
- Tue Apr 28, 2020 10:16 am
- Forum: ESP-IDF
- Topic: bonding with devices which use random BLE addresses
- Replies: 11
- Views: 17544
Re: bonding with devices which use random BLE addresses
@anthony Please take a look at this issue: https://github.com/espressif/esp-nimble/issues/8 and see if it resolves your problem. If you are looking to use RPA feature, please refer to following points: own_addr_type needs to be set to BLE_ADDR_RANDOM. ble_hs_pvcy_rpa_config() should be called in aft...
- Tue Apr 28, 2020 8:15 am
- Forum: Sample Code
- Topic: Pairing or bonding from ESP32 Central using NimBLE stack
- Replies: 14
- Views: 25135
Re: Pairing or bonding from ESP32 Central using NimBLE stack
Hi @nirmal.lad, It would be really helpful if you can provide console logs with DEBUG prints on as mentioned earlier :) I have left a few comment, please let me know if you find them helpful. On next connection, mobile phone doesn't generate pair request If the bond is established successfully then ...
- Mon Apr 27, 2020 10:13 am
- Forum: Sample Code
- Topic: Pairing or bonding from ESP32 Central using NimBLE stack
- Replies: 14
- Views: 25135
Re: Pairing or bonding from ESP32 Central using NimBLE stack
@nirmal.lad I could not reproduce the issue, Can you provide Debug logs(`make menuconfig--> component config --> Log output--> Default log verbosity` to `Debug` ) for the issue ? Is it possible for you to provide demo application to reproduce the issue? I believe you are calling `ble_gap_security_in...
Re: ble uart
Hi Dwayne, There is application present in mynewt-core for this, link: https://github.com/apache/mynewt-core/tree/master/apps/bleuart/src, it can be ported to ESP32 by referring to `bleprph` app in `$IDF/examples/bluetooth/nimble`. However, we can not use this off the shelf, as the service `bleuart`...
- Mon Dec 02, 2019 9:41 am
- Forum: ESP-IDF
- Topic: Persist Bonding Information with nimBLE
- Replies: 14
- Views: 17810
Re: Persist Bonding Information with nimBLE
Hi @IanWhitehead , apologies for delayed response, I am currently working on Host based privacy feature, wherein the NimBLE host shall be able to resolve the RPA address. Currently resolving RPA is not supported, I will update you as soon as the feature is available.
- Thu Nov 14, 2019 6:58 pm
- Forum: ESP-IDF
- Topic: Persist Bonding Information with nimBLE
- Replies: 14
- Views: 17810
Re: Persist Bonding Information with nimBLE
@IanWhitehead, Can you please confirm you did not get `BLE_GAP_EVENT_ENC_CHANGE` event after re-connection ? Can you please try `bleprph` example enabling bonding with "non address changing" device and provide me the complete log and sdkconfig file? I wondered if the Example Configuration setting "U...
- Thu Nov 14, 2019 6:24 am
- Forum: ESP-IDF
- Topic: Persist Bonding Information with nimBLE
- Replies: 14
- Views: 17810
Re: Persist Bonding Information with nimBLE
@IanWhitehead , from the logs it can be observed that the `peer_id_addr` is changed. Now from the Bluetooth spec (Vol 6, Part B, section 1.3.2.1) : If the static address of a device is changed, then the address stored in peer devices will not be valid and the ability to reconnect using the old addre...
- Tue Nov 12, 2019 9:01 am
- Forum: ESP-IDF
- Topic: Persist Bonding Information with nimBLE
- Replies: 14
- Views: 17810
Re: Persist Bonding Information with nimBLE
@IanWhitehead, this is quite unusual, Can you please share the console logs and sdkconfig for this issue? Can you please also make sure that IDF_PATH is set correctly ? Ideally you should be able to see logs like below: I (11254) NimBLE_BLE_PRPH: Accept or reject the passkey through console in this ...