-
-
Notifications
You must be signed in to change notification settings - Fork 142
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Extended Advertising Events are missed when the message length is longer than 57 bytes #330
Comments
Well that's a weird bug! But I suspect it's probably a bug in BlueZ (or maybe the Bluetooth adapter) rather than btleplug. Are you able to receive the manufacturer data you expect with the |
Does not look interesting imho
I used btmon tough -> and with that, I can see the longer messages. Example:
/edit: BUT with bluetootctl, I can only see the short ones, and the long ones are missing:
|
Describe the bug
I think I found an issue with Extended Advertising messages.
We are developing a BLE device that sends data via manufacturer data in advertising messages.
We confirmed that the messages are sent correctly from our BLE device using an app on a Mac.
But on the client I wrote, running on my Linux machine, I stop receiving advertising events once the message lengths exceed 57 bytes (not 57 bytes of manufacturer data, but 57 bytes of advertising).
This is going to be annoying to reproduce since none of you has our BLE device, but there is the client code anyway:
Expected behavior
I expect a
CentralEvent::ManufacturerDataAdvertisement
event with manufacturer data if a BLE device sends an "Extended Advertising".Actual behavior
There is no event produced at all.
Additional context
Fedora 38 on Intel with Intel Bluetooth chip. The BLE device is an ESP32-C3 with our firmware.
The Bluetooth chip on my PC is an Intel AX210.
The text was updated successfully, but these errors were encountered: