BLE Notifications limited to 1 per connection event on Zephyr v2.4.0 Central #29957
Labels
area: Bluetooth
bug
The issue is a bug, or the PR is fixing a bug
Regression
Something, which was working, does not anymore
Describe the bug
I am in the process of upgrading my application from v2.3.0 to v2.4.0. While doing testing I observed a decrease in throughput over the application BLE link. After taking a capture between my peripheral (custom) and central (Zephyr v2.4.0) devices I observed that only a single notification is being received per connection event. This is despite the notification payload setting the More Data flag which should cause the Central to ACK and receive the next notification as there is plenty of time before the next connection event.
To rule out complications due to my application I was able to reproduce this via the Zephyr BLE HRS samples (central_hr and peripheral_hr).
To Reproduce
Steps to reproduce the behavior on Zephyr v2.4.0:
On the central board
west build -b nrf52dk_nrf52832 zephyr/samples/bluetooth/central_hr && west flash
On the peripheral board
samples/bluetooth/peripheral_hr/src/main.c
with the following snippet:west build -b nrf52dk_nrf52832 zephyr/samples/bluetooth/peripheral_hr && west flash
Expected behavior
The peripheral should be able to send multiple notifications per connection event.
Impact
This issue greatly reduces possible throughput of a BLE application via notifications.
Logs and console output
I have attached a capture from Wireshark
Environment (please complete the following information):
zephyr_v2.4.0_notification_capture.pcapng.zip
The text was updated successfully, but these errors were encountered: