STM32WB5Multiple Connections – Handling Notification Completion per Connection

[netanelu]

Hi,

I'm working on a project using the STM32WB5MMG, which supports up to 4 simultaneous BLE connections.

When a central device enables or disables notifications, my firmware receives the corresponding events (NOTIFY_ENABLED_EVT / NOTIFY_DISABLED_EVT) inside the Custom_STM_App_Notification() function. However, I'm unsure whether the ConnectionHandle parameter in this context reliably identifies which central device triggered the change.

Additionally, when the firmware updates a characteristic's value using Custom_STM_App_Update_Char(), we know we must wait for the CUSTOM_STM_NOTIFICATION_COMPLETE_EVT (handled in custom_app.c) before sending the next notification.

Now that we're dealing with multiple central devices, here's my main concern:

Does CUSTOM_STM_NOTIFICATION_COMPLETE_EVT include the specific ConnectionHandle of the device that received the last notification?
If not, how can we safely coordinate and track per-connection notification completion to avoid sending notifications out of order?

I'd appreciate guidance on whether the SDK handles this internally per connection or if I need to implement a custom per-connection queue or state tracker.

Thanks!

[STTwo-32]

Hello @netanelu 

According to the BLE spec, the only way to notify a specific central device is to disable the notification for all other central devices.

Best Regards.

STTwo-32