<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://devzone.nordicsemi.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>API to get a peripheral bonded device&amp;#39;s physical address</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/80538/api-to-get-a-peripheral-bonded-device-s-physical-address</link><description>Hey, 
 I have a nRF central that connects and bonds to peripheral devices via BLE. 
 From what I understand, the peripheral device has a BLE MAC address that isn&amp;#39;t consistent, but a resolvable MAC address of the physical address. 
 Is there an API to</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 12 Oct 2021 10:54:47 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/80538/api-to-get-a-peripheral-bonded-device-s-physical-address" /><item><title>RE: API to get a peripheral bonded device's physical address</title><link>https://devzone.nordicsemi.com/thread/333704?ContentTypeID=1</link><pubDate>Tue, 12 Oct 2021 10:54:47 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:0e9af024-db4b-474f-ab92-8d83e620b082</guid><dc:creator>Amanda Hsieh</dc:creator><description>&lt;p&gt;Hi,&amp;nbsp;&lt;/p&gt;
&lt;p&gt;There is no&amp;nbsp;&lt;span&gt;physical address when the device uses the resolvable address.&amp;nbsp;&lt;/span&gt;&lt;span&gt;It is only by bonding with a device that you may get the IRK (identity resolvable key) that you will be able to recognize a device that is advertising and thereby also potentially connect.&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;See&amp;nbsp;&lt;a title="Software Development Kit" href="https://infocenter.nordicsemi.com/topic/sdk_nrf5_v17.0.2/lib_pm_architecture.html?resultof=%22%49%64%65%6e%74%69%74%79%22%20%22%69%64%65%6e%74%22%20%22%52%65%73%6f%6c%76%69%6e%67%22%20%22%72%65%73%6f%6c%76%22%20%22%4b%65%79%73%22%20%22%6b%65%69%22%20"&gt;&amp;nbsp;&lt;/a&gt;&lt;a title="Peer Manager" href="https://infocenter.nordicsemi.com/topic/sdk_nrf5_v17.0.2/lib_peer_manager.html?cp=8_5_0_3_2_7"&gt;Peer Manager&lt;/a&gt;&amp;nbsp;/&amp;nbsp;&lt;a title="Software Development Kit" href="https://infocenter.nordicsemi.com/topic/sdk_nrf5_v17.0.2/lib_pm_architecture.html?resultof=%22%49%64%65%6e%74%69%74%79%22%20%22%69%64%65%6e%74%22%20%22%52%65%73%6f%6c%76%69%6e%67%22%20%22%72%65%73%6f%6c%76%22%20%22%4b%65%79%73%22%20%22%6b%65%69%22%20"&gt;Architecture&lt;/a&gt;&amp;nbsp;- ID Manager and&amp;nbsp;&lt;a title="Heart Rate Application" href="https://infocenter.nordicsemi.com/topic/sdk_nrf5_v17.1.0/ble_sdk_app_hrs.html?cp=8_1_4_2_2_13"&gt;Heart Rate Application&lt;/a&gt;.&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Regards,&lt;br /&gt;Amanda&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>