This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Sending keypress notifications when LESC is not in progress

Hi

This question is related to sd_ble_gap_keypress_notify(). According to Nordic softdevice S132 v3.0.0 API:-

"This function can only be used when an authentication procedure using LE Secure Connection is in progress. Calling it at other times will result in an @ref NRF_ERROR_INVALID_STATE"

However, when enabling keypress notifications without using LESC pairing, we can still get the keypress notifications on the remote side during legacy pairing (passkey entry). NRF_ERROR_INVALID_STATE is not returned in that case. Is this expected behaviour now?

We're using nRF52 with softdevice S132 v3.0.0.

Thanks

Parents
  • Hi,

    Keypress Notifications are limited to Passkey Entry modes, but should also be valid for legacy pairing. The documentation is a bit unclear at this point. The explanation for NRF_ERROR_INVALID_STATE is correct, but the sentence under "details" is wrong.

    Devices that are aware of the passkey notification bit in the pairing request/response should be able to make use of it. Older devices are required to set it to 0.

    I have raised this as an issue internally.

Reply
  • Hi,

    Keypress Notifications are limited to Passkey Entry modes, but should also be valid for legacy pairing. The documentation is a bit unclear at this point. The explanation for NRF_ERROR_INVALID_STATE is correct, but the sentence under "details" is wrong.

    Devices that are aware of the passkey notification bit in the pairing request/response should be able to make use of it. Older devices are required to set it to 0.

    I have raised this as an issue internally.

Children
No Data
Related