cancel
Showing results for 
Search instead for 
Did you mean: 

ST67W61 BLE pairing and bonding for iOS

Shirovaty
Associate II

Hello,

I've got a question about pairing and bonding for BLE with iOS devices for ST67W61.
I've checked available functions and AT commands, I don't see any mean to encrypt the characteristic. As the iOS BLE stack requires it to pair and bond - am I missing something or it's not yet implemented?

Best regards

4 REPLIES 4
TarikAb
ST Employee

Hi @Shirovaty 

I confirm that this feature is not available.

The BLEGATTSCHARCRE AT command can be called with char_perm set to read permission or write permission. This allows the remote device to access the characteristic without encryption.

By performing authenticated pairing, it is possible to encrypt the characteristic or data. You can replace the missing feature by requesting pairing automatically after the connection event. Does this solution meet your requirements?

Best regards,


In order to give better visibility on the answered topics, please click on 'Accept as Solution' on the reply which solved your issue or answered your question.

Hi @TarikAb,

I've came across this solution (using securityStart() at connection) but there is another issue linked to it.
For some reason both iOS and Android default to bonding instead of pairing, which is problematic in terms of iOS - unbonding is tedious on this OS.
BLE Specification mentions Bonding Flag in the pairing request, which is responsible for indicating if the request is for pairing or bonding. Is there any option to set it from x-cube-st67w61 or AT commands?

Thanks for your help!

TarikAb
ST Employee

Hi @Shirovaty 

I confirmed internally that the ST67 defaults to bonding. There is no flag implemented to select between pairing and bonding. I asked R&D to look into this topic, and I will update this post when there is news.

Best regards


In order to give better visibility on the answered topics, please click on 'Accept as Solution' on the reply which solved your issue or answered your question.

Hi @TarikAb 

Thanks for the info, for now it's not such a problem, but this update will come in handy in future :)

Best regards