<?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>NRF52 peripheral visibility restriction</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/77030/nrf52-peripheral-visibility-restriction</link><description>Hi, 
 I&amp;#39;m developing a peripheral sensor and central receiver as a complete set. So I wish the peripheral is only visible(or connectable) to its central device. 
 I know the central could lock on certain peripheral by address filtering, is there any chances</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 05 Jul 2021 09:20:17 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/77030/nrf52-peripheral-visibility-restriction" /><item><title>RE: NRF52 peripheral visibility restriction</title><link>https://devzone.nordicsemi.com/thread/318579?ContentTypeID=1</link><pubDate>Mon, 05 Jul 2021 09:20:17 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:118d724e-9529-4bed-9779-779869b2f131</guid><dc:creator>Avadacadabara</dc:creator><description>&lt;p&gt;I&amp;#39;m checking out SDK sample.&lt;/p&gt;
&lt;p&gt;Thanks!&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: NRF52 peripheral visibility restriction</title><link>https://devzone.nordicsemi.com/thread/318441?ContentTypeID=1</link><pubDate>Fri, 02 Jul 2021 12:40:13 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:f869d5d2-ae5a-4ae0-a456-6b6a11fc489d</guid><dc:creator>Mttrinh</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;You can use whitelist on the peripheral to achieve this. Whitelist is used for filtering out which scan requests and connection request it will recieve and process. O&lt;span&gt;nly allowing scan requests/connections for those devices whose address is in the whitelist.&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;In order to populate the whitelist, you should either know the address of the central device in advance or establish a connection/bond with the central device.&amp;nbsp;&lt;/span&gt;&lt;span&gt;To store a resolvable private address in a whitelist you will need the IRK, which you get as part of the bonding process. For other address types you can put them in the whitelist directly.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;I suggest you take a look at our &lt;a href="https://infocenter.nordicsemi.com/topic/sdk_nrf5_v17.0.2/ble_sdk_app_hids_keyboard.html?cp=8_1_4_2_2_15" rel="noopener noreferrer" target="_blank"&gt;HID Keyboard example&lt;/a&gt; in our SDK, it will give you an idea on how to implement it.&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>