This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Static address & pairing



Is it possible to solve device's public address in pairing, if it uses static address in adveritising? There is no reason to save any device specific data if just static address is known (because it can be changed when device powers up).

  • I think that you are mentioning about saving a device address to be matched after power cycle(off and on).
    If right, as I know, it is not possible. So, you need to use an approach using IRK to a resolvable address to get the public address of a device.
    When pairing, two devices should exchange their IRK, CSRK, LTK, and else and then save them to internal non-volatile memory like EEPROM or Flash.
    And when reconnecting, the resolving procedure should be done. Of course, you need to check if the address is public, resolvable address, or else.
  • Hi Juha,

    Our GAPBondManger exchanges keys to remember devices. This process is documented in our software developer's guide.
  • The question is more than 3 years old so I am not anymore 100% sure what I have had in my mind...

    Now I anyway know that there is always risk that device with static address can change it's address after power up and there is no way to recognize the device anymore after this. Usually devices with static addresses won't anyway change their addresses on boot up.

    (Or actually device with static address could have also public address that can be used for recognizion after connection, but usually static addresses are used to avoid use of public addresses so device with static address won't most likely have a public address.)