Not able to send notifications and indications after bonding

RE: Not able to send notifications and indications after bonding

Karl Ylvisaker — Tue, 18 Aug 2020 08:46:52 GMT

Hello,

[quote user="morozovoars"]I found mistake it was in my code. I have my own boolean variables, which indicates if notifications/indications enabled or no. I update them only during changing descriptor of characteristics. In case of bonding and after reset this variables are false and they reject any calls of hvx and handle this like INVALID_STATE error. I use it to overcome APP_ERROR_CHECK calls, because I also use it.
Now I check desriptors of the chars inside connected event and update those boolean variables. In this way everything works perfect.[/quote]

This is exactly what the APP_ERROR_CHECK function is made to do, and how it should be used - alert you that you have gotten an unexpected return from a function. I am happy to hear that you were able to identify and resolve the issue!

[quote user="morozovoars"]So, anyway thank you very much and sorry for false issue.[/quote]

Do not worry at all, I am happy to help!

Please do not hesitate to open a new ticket if you should encounter any other issues or questions in the future.

Good luck with your development! :)

Mvh.
Karl

RE: Not able to send notifications and indications after bonding

Ars Morozov — Mon, 17 Aug 2020 20:09:54 GMT

I found mistake it was in my code. I have my own boolean variables, which indicates if notifications/indications enabled or no. I update them only during changing descriptor of characteristics. In case of bonding and after reset this variables are false and they reject any calls of hvx and handle this like INVALID_STATE error. I use it to overcome APP_ERROR_CHECK calls, because I also use it.
Now I check desriptors of the chars inside connected event and update those boolean variables. In this way everything works perfect.
So, anyway thank you very much and sorry for false issue.

RE: Not able to send notifications and indications after bonding

Ars Morozov — Mon, 17 Aug 2020 19:42:47 GMT

[quote userid="87869" url="~/f/nordic-q-a/64841/not-able-to-send-notifications-and-indications-after-bonding/264823"]This happens if you try to notify a central that has not enabled notifications.
In your case, it sounds like you have enabled notifications, but you will need to verify that the particular CCCD is in fact enabled.[/quote]

How can I check this?

[quote userid="87869" url="~/f/nordic-q-a/64841/not-able-to-send-notifications-and-indications-after-bonding/264823"]Have you for instance created a custom characteristics that you would like to do notifications / indications on? In that case, the central will need to be told about this in advance, so it knows what to expect from this characteristic.[/quote]

Yes, I did. As I said it works perfectly without bonding.

RE: Not able to send notifications and indications after bonding

Karl Ylvisaker — Mon, 17 Aug 2020 10:33:37 GMT

[quote user="Karl Ylvisaker"]Notifications and/or indications not enabled in the CCCD[/quote]

This happens if you try to notify a central that has not enabled notifications.
In your case, it sounds like you have enabled notifications, but you will need to verify that the particular CCCD is in fact enabled.

[quote user="Karl Ylvisaker"]An ATT_MTU exchange is ongoing[/quote]

If a sd_ble_gattc_exchange_mtu_request has been made ( with return value NRF_SUCCESS ) you will need to wait for the BLE_GATTC_EVT_EXCHANGE_MTU_RSP to proceed.

If you are working out of the ble_app_hrs_rscs_relay example from the SDK, the 3. condition should be handled already, so my suspicion is on the 2nd condition.
Have you for instance created a custom characteristics that you would like to do notifications / indications on? In that case, the central will need to be told about this in advance, so it knows what to expect from this characteristic.

Best regards,
Karl

RE: Not able to send notifications and indications after bonding

Ars Morozov — Mon, 17 Aug 2020 09:30:14 GMT

Ok,
but how can I check 2nd and 3rd conditions?

RE: Not able to send notifications and indications after bonding

Karl Ylvisaker — Mon, 17 Aug 2020 09:26:34 GMT

Hello again,

The sd_ble_gatts_hvx API Reference Documentation lists the following possible reasons for the NRF_ERROR_INVALID_STATE return value:

NRF_ERROR_INVALID_STATE

One or more of the following is true:

Invalid Connection State
Notifications and/or indications not enabled in the CCCD
An ATT_MTU exchange is ongoing

Could you verify that neither of these are the case?

Best regards,
Karl

RE: Not able to send notifications and indications after bonding

Ars Morozov — Mon, 17 Aug 2020 08:35:29 GMT

Hi Karl,

sd_ble_gatts_hvx() returns NRF_ERROR_INVALID_STATE

RE: Not able to send notifications and indications after bonding

Karl Ylvisaker — Mon, 17 Aug 2020 07:51:21 GMT

Hello,

[quote user=""]But when I send notification I get the following error codes - NRF_ERROR_INVALID_STATE[/quote]

Which function is returning with the NRF_ERROR_INVALID_STATE value?

Best regards,
Karl