https://devzone.nordicsemi.com/f/nordic-q-a/14427/nrf8001-pairing-problemsHi, I&#39;m trying to get pairing working. So far I have set the following in nrfgo studio:- Device security: security required Required level of security: Authenticated (Passkey) also tried Unauthenticated (Just Works) I/O Capabilitiesen-USTelligent Community 13Wed, 15 Jun 2016 07:51:17 GMThttps://devzone.nordicsemi.com/thread/55124?ContentTypeID=1Wed, 15 Jun 2016 07:51:17 GMT137ad170-7792-4731-bb38-c0d22fbe4515:b1d03748-2768-4c77-859f-215755d7ee77Simon<p>I have done as you suggested and can confirm the generated sources are taking effect. The response from the GetDeviceVersion command is as follows:</p> <p>0x0c, 0x84, 0x09, 0x00, 0x41, 0x00, 0x02, 0x03, 0x09, 0x00, 0x00, 0x00</p> <p>The setup id in nrfgo was 9 and is present in the response.</p> <p>The chip has the following etched onto it: NRF D 8001 1444VM</p> <p>Thanks for your help.</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/55123?ContentTypeID=1Sun, 12 Jun 2016 22:44:37 GMT137ad170-7792-4731-bb38-c0d22fbe4515:9dcf93e1-bfdc-439f-834c-514785b7fd36David Edwin<p>You need to verify that you have used the updated services.h file when you made the security changes and that the Setup contained in that file has been downloaded to the device. To verify this, I would typically set the Setup ID in the top right corner of the nRF8001 configuration window and then read the Setup ID back from the nRF8001 using the GetDeviceVersion ACI command.</p> <p>Additionally I would verify that the nRF8001 D version is being used (so post the version of the IC that you have using the GetDeviceVersion ACI command) and also the date code that is etched on the top of the IC.</p><div style="clear:both;"></div>