<?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>How I get the passkey value??</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/116369/how-i-get-the-passkey-value</link><description>Hello. I would like to receive the passkey value that the user entered when pairing Bluetooth and modify it. Originally, it was said that if you enter &amp;quot;0000&amp;quot;, you have to enter 6 digits according to the regulations to enable Bluetooth pairing. So if I</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 18 Nov 2024 01:06:50 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/116369/how-i-get-the-passkey-value" /><item><title>RE: How I get the passkey value??</title><link>https://devzone.nordicsemi.com/thread/510813?ContentTypeID=1</link><pubDate>Mon, 18 Nov 2024 01:06:50 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:028dab9a-4af2-4f63-b25b-f9b51dfdc2d0</guid><dc:creator>chosseang</dc:creator><description>&lt;p&gt;Thank you for your answer.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: How I get the passkey value??</title><link>https://devzone.nordicsemi.com/thread/510672?ContentTypeID=1</link><pubDate>Fri, 15 Nov 2024 12:05:35 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:d492d77e-bbcf-4611-9130-c023b0ecc48e</guid><dc:creator>Kenneth</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;You can for instance check out BLUETOOTH CORE SPECIFICATION Version 5.3 | Vol 3, Part H&lt;/p&gt;
&lt;p&gt;Under chapter&amp;nbsp;LE legacy pairing - Passkey Entry&lt;/p&gt;
&lt;p&gt;&amp;quot;If the IO capabilities of a device are DisplayOnly or if Table 2.8 defines that the&lt;br /&gt;device displays the passkey, then that device shall display a randomly&lt;br /&gt;generated passkey value between 000,000 and 999,999. The display shall&lt;br /&gt;ensure that all 6 digits are displayed – including zeros. The other device shall&lt;br /&gt;allow the user to input a value between 000,000 and 999,999.&amp;quot;&lt;/p&gt;
&lt;p&gt;Kenneth&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: How I get the passkey value??</title><link>https://devzone.nordicsemi.com/thread/510588?ContentTypeID=1</link><pubDate>Fri, 15 Nov 2024 03:15:01 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:768eeec5-9382-4a47-a65f-95b205a63ffc</guid><dc:creator>chosseang</dc:creator><description>&lt;p&gt;Oh.&lt;/p&gt;
&lt;p&gt;Thank you the answer, Kenneth.&lt;/p&gt;
&lt;p&gt;I understand your answer.&lt;br /&gt;&lt;br /&gt;&lt;/p&gt;
&lt;p&gt;It is related to terms of security.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;I&amp;#39;d like to see the official document of bluetooth and android on the passkey 6-digit limit, is it possible??&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: How I get the passkey value??</title><link>https://devzone.nordicsemi.com/thread/510552?ContentTypeID=1</link><pubDate>Thu, 14 Nov 2024 17:39:29 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:0778c15b-b8f9-4e39-8ee1-4651cb83b57e</guid><dc:creator>Kenneth</dc:creator><description>&lt;p&gt;Hello,&lt;/p&gt;
&lt;p&gt;I am not sure this request is possible.&lt;/p&gt;
&lt;p&gt;The passkey is either generated during BLE pairing by the device that have a display device, or it must be specified prior to BLE pairing as a static passkey by the device that claim it has a display. The passkey must be 6 digit long. It&amp;#39;s not transferred in clear text in any way, though I guess it&amp;#39;s possible to also write the 6 digit value to a characteristic, which the peer device can read during connection before pairing, but it&amp;#39;s a odd implementation, and in terms of security I don&amp;#39;t&amp;nbsp;see this as a good solution.&lt;/p&gt;
&lt;p&gt;Kenneth&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>