Welcome to the Forum!!
When you set the security Level as 'Authenticated Pairing with Encryption' or 'Authenticated LE Secure Connection Pairing with Encryption' you are supposed to go for Authentication means your device should have some I/O capabilities for authentication. So, if you set the I/O capabilities as 'No Input No output' you are pushing back your device for Un-authentication pairing which is not possible because you have set the security level for 'Authenticated Pairing before.
Please find a screenshot of BLE spec attached with this response. Here you can see that when you set 'Authenticated' pairing ,the MITM flag will set and it will check for I/O capabilities. Now if you do not have I/O capabilities , your pairing should be 'just work' means 'Un-Authenticated' .
So basically before setting the Security Level you are supposed to be known about your device I/O capabilities.
Hope this will help you!!
Please let us know if you have any further queries.
Security.PNG 51.7 K
@GYAN It sounds like you are saying that the order in which you choose the I/O capability and the security level makes a difference for the IDE setting up the "just works" pairing/authentication.
Thus, if we set the I/O capability first, before setting the security settings, then there will be no error(s)?
1 of 1 people found this helpful
No, the order of configuring IO capabilities and Security level will not solve the issue. It will still throw the error.
In Vol3, Part C of the Bluetooth spec, it is stated that the last security level or security level 4 is "Authenticated LE Secure Connections pairing with encryption.". It also says that security level 4 shall also satisfy the security requirements for security level 3. In simple words, Secure Connections always comes with "Authenticated". There is no way to have an unauthenticated secure connection (we can argue that the SMP says it's allowed but the GAP says authentication is mandatory).