Is the bluetooth broadcast data really 31 bytes?
-
I can't find where this is documented in the Bluetooth profile specs. The reason I ask is that using the resolve_adv_data() function, the long name from via the ADV_NAME_CMPL constant is incomplete when compared with the broadcasts I receive on my phone, e.g.
data = 0x020106020a0011069ecadc240ee5a9e093f3a3b50100406e0c09426c756566.
long name = BluefL�@? (0x426c756566) followed by some garbage.
name captured by phone = Bluefruit52 (0x426c756566727569743532).It looks like the data should be more than 31 bytes.
-
I've found some info that suggests it is possible for the scanner to request up to another 31 bytes of information if the advertising mode allows this. The question is therefore, is there a function to do this?
-
@alidaf
Nope that's not supported and unlikely to be in the near future.If you need more than 31 bytes I recommend establishing a BLE connection and transferring data through characteristics..
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login