nRF52840 SDK16 s140 - Disable notifications when peer is disconnected

RE: nRF52840 SDK16 s140 - Disable notifications when peer is disconnected

Edvin — Fri, 06 Nov 2020 14:38:19 GMT

It is the central that controls the CCCD, always. You can't control this from the peripheral's application. The only thing the peripheral can do is to store the state of the CCCD between the connections if they are bonded.

You can of course disable bonding, but I assume there is a reason why you are using it in the first place.

Why do you need to unset the CCCD state?

BR,
Edvin

RE: nRF52840 SDK16 s140 - Disable notifications when peer is disconnected

Nikosant03 — Fri, 06 Nov 2020 13:58:22 GMT

Hi Edvin,

[quote userid="26071" url="~/f/nordic-q-a/68056/nrf52840-sdk16-s140---disable-notifications-when-peer-is-disconnected/278765#278765"]Is your peripheral using bonding? [/quote]

Yes

[quote userid="26071" url="~/f/nordic-q-a/68056/nrf52840-sdk16-s140---disable-notifications-when-peer-is-disconnected/278765#278765"]Perhaps you can stop the sending of notifications from the application if that is what you want[/quote]

Yes I can do that (it was my first thought), but I am wondering if it was more elegant to unset the CCCD value after a disconnection event.

RE: nRF52840 SDK16 s140 - Disable notifications when peer is disconnected

Edvin — Fri, 06 Nov 2020 11:57:19 GMT

Hello Nick,

Is your peripheral using bonding?

Devices that are bonded should store the CCCD state for the link between connections. This comes from the BLE specification. Is it an issue that it does? If so, it is the application that chooses whether or not to send any notifications. Perhaps you can stop the sending of notifications from the application if that is what you want?

Best regards,

Edvin