Closed JerryZheng89 closed 3 years ago
Thanks for reporting, we will look into.
Is threre any progress about this problems, or any suggestion to let me move forward? @Alvin1Zhang
The uint8_t whitelist_addr[6] = {0xc9, 0xa7, 0xab, 0x5e, 0x2d, 0xbe};
is Static Random Device Address.
Maybe you need to modify it this way esp_ble_gap_update_whitelist(true, whitelist_addr, BLE_WL_ADDR_TYPE_PUBLIC);
=> esp_ble_gap_update_whitelist(true, whitelist_addr, BLE_WL_ADDR_TYPE_RANDOM);
The
uint8_t whitelist_addr[6] = {0xc9, 0xa7, 0xab, 0x5e, 0x2d, 0xbe};
is Static Random Device Address.Maybe you need to modify it this way
esp_ble_gap_update_whitelist(true, whitelist_addr, BLE_WL_ADDR_TYPE_PUBLIC);
=>esp_ble_gap_update_whitelist(true, whitelist_addr, BLE_WL_ADDR_TYPE_RANDOM);
Is threre any method to add public address into white list? I will try your suggestion tomorrow. @xiewenxiang thanks
The issue is solved, @xiewenxiang @Alvin1Zhang follow these steps:
esp_ble_gap_update_whitelist(true, whitelist_addr, BLE_WL_ADDR_TYPE_RANDOM);
And it works well!!!
but I really don't konw why the wl_addr_type is random, i really think it is the public address, vevry confusing me!
Environment
Problem Description
when I change scan policy to
BLE_SCAN_FILTER_ALLOW_ONLY_WLST
, flow 3steps change in gatt_client example:or
Expected Behavior
event list
Actual Behavior
event list
Code to reproduce this issue
Debug Logs
sniffer
Although, the scan type, which I set is BLE_SCAN_TYPE_ACTIVE, I don't have seen any scan or response package in Wireshark within the 30 seconds.