This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Differentiating in bonding phase between another NRF52832 or Mobilephone

Hello everyone,

I have a question regarding the bonding process in the NRF52832 device. Currently I have one custom service with one character and my nrf device is a doing advertising. The character has a MITM protection for reading and writing and the devices has to bond before they can "communicate".

My Problem is that I want to differentiate between the device which wants to connect to my NRF52832. If it is a mobile phone it should went through the complete bonding process and also through a numeric comparison (my nrf52832 has to press the button once to accept). In case of the other device is another NRF52832 I dont want the complete bonding process I want directly to be able to read and write the character. If this is not possible at least I want that in this case the nrf52832 should wait for a button press it should directly accept the numeric comparison. But to do this step I have to know which device wants to get bonded... I hope I was able to explain my problem.

If this is not possible I am planning to create to different characters in my custom service. One for the mobile communication and the other one for the NRF52832 communciation with two different security types.

I hope you can help me or give me some hints how to proceed.

Best regards

Hani

Parents Reply
  • Hello Amanda,

    Thank you for your feedback! That means it is not possible as peripheral device to differentiate and say if it is a NRF52832 device skip the button press and bond directly and in case of a mobile phone the peripheral device has to press the button for bonding.

    In this case I have to always do the bonding process and have to code the button press seperatly after the bondig right?

Children
Related