Whether the peripheral device can distinguish the central device's system when connected as a peripheral depends on whether it is an iOS or Android system.

I am currently developing my project using the nrf52832 and the nrf5SDK.

I utilized the peer_manager module, and in the application, when being connected as a peripheral, I did not use pm_conn_secure() to enforce pairing.

Therefore, when using an Android phone, by using third-party apps, one can scan the Bluetooth signal and achieve the function of only connecting and pairing the devices.

However, when using an iOS device, no matter which app is being used, the process of connection cannot avoid the need for pairing and binding.

We hope to achieve this by making the Android system behave in such a way that it does not require pairing and binding to implement a feature that allows visitors to use it. In the application, we will use a similar secondary password verification method to manage the permissions for visitors.

So, is it possible to distinguish the opposite end's system when the device is connected, and enable all mobile devices to connect or pair and bind only? Whether to initiate the pairing and binding is determined by the mobile device.

Parents
  • Hi

    Using I.E. the nRFConnect for Mobile app on iOS should definitely have support for connecting to peripherals without requiring pairing/bonding. Can you try explaining what exactly the issue you're seeing having here?

    It might be something lost in translation here, but what this could be due to is that iOS devices won't allow third party peripherals to initiate pairing/bonding on its own. You rather need to read/write to a characteristic requiring higher security and then pairing will be initiated if that is what you need.

    Best regards,

    Simon

Reply
  • Hi

    Using I.E. the nRFConnect for Mobile app on iOS should definitely have support for connecting to peripherals without requiring pairing/bonding. Can you try explaining what exactly the issue you're seeing having here?

    It might be something lost in translation here, but what this could be due to is that iOS devices won't allow third party peripherals to initiate pairing/bonding on its own. You rather need to read/write to a characteristic requiring higher security and then pairing will be initiated if that is what you need.

    Best regards,

    Simon

Children
No Data
Related