-
-
Notifications
You must be signed in to change notification settings - Fork 60
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
Difference in default BLE and nimBLE when having multiple advertisements #98
Comments
Hi @AndrewMagpie, I believe the cause to be in the different handling of the AD flags in the data count, I still need to verify this. For an explanation, the AD flags, IIRC, are accounted for differently in the advertisement data size with the original library, and in your situation you have now exceeded the data limit by 3 bytes. For now, if you don't need it I would suggest removing these calls:
This should be sufficient to resolve the issue and I will look into better handling of this. |
@h2zero removing those fixed the advertisement but were there to get around an issue we were having with iPhones. |
Please let me know if/when there is a fix for this so that we can start using those two APIs again. |
I don't think that issue exists any longer, I have not yet heard of it being a problem since I started this repo and that functionality was removed initially. |
When using the default BLE library and advertising a 128 bit followed by a 16 bit advertisement I see both in nRFConnect.
When using the nimBLE library I only see the the 128 bit advertisement (or whatever was added first with
addServiceUUID()
).Default BLE library:
nimBLE:
How do I get nimBLE to advertise both UUIDs?
Using PlatformIO on a ESP32S3.
The text was updated successfully, but these errors were encountered: