2022-04-22 03:31 PM
I went from the v1.12.1 stack to the v1.13.3 stack and LE Privacy seems to be no longer working. It advertises, but always with the static random address, not a random resolvable address. Also, the address never changes. Anyone else seeing this? Is there some new interface I need to use to get random resolvable addresses?
2022-04-25 06:29 AM
Hello,
If you want to use a random resolvable address, you need to configure the last parameter of aci_gap_set_authentication_requirement command (i.e CFG_BLE_ADDRESS_TYPE).
Best Regard
2022-04-25 08:10 AM
Thank you, I tried that. Passing RESOLVABLE_PRIVATE_ADDR to aci_gap_set_authentication_requirement results in a return code of BLE_STATUS_INVALID_PARAMS.
The comment for the function states that only these parameters are allowed.
* @param Identity_Address_Type Identity address type.
* Values:
* - 0x00: Public Identity Address
* - 0x01: Random (static) Identity Address
2022-04-28 01:31 AM
Hello,
You shall use this parameter 0x01: Random (static) Identity Address in aci_gap_set_authentication_requirement command and use RESOLVABLE_PRIVATE_ADDR parameter in aci_gap_set_discoverable command.
Best Regards
2022-04-28 08:19 AM
Ok, so in the following:
aci_gap_init I am passing 0x02 for privacy_enabled (ive tried 0x01 - like it used to be, and I get no difference)
aci_gap_set_authentication_requirement I am passing 0x01 for Identity_Address_Type
aci_gap_set_discoverable I am passing RESOLVABLE_PRIVATE_ADDR(0x02) for Own_Address_Type
The address never changes from the static random address. The device still advertises with the static random address (exactly what I program for CONFIG_DATA_RANDOM_ADDRESS_OFFSET) not a random resolvable address. This functionality has definitely changed from v1.12.1 - it used to work exactly the way I had it configured.
2022-05-11 02:50 AM
Hello,
Indeed, the privacy behavior have changed since v1.12 in order to be align with Bluetooth standards. In order to have a random resolvable address follow these steps:
Best Regards