Spec: correct MAC-and-advertising — stock firmware broadcasts no MAC; document the sanctioned broadcast format#11
Merged
Conversation
… MAC The section claimed the MAC "is included in the device's advertising data and can be read during scanning" — field-verified false on fw 1.7.x, whose default advertisements carry only the local name and the MetaWear service UUID. (Android/Windows see the MAC because the OS exposes the link-layer address, not because the payload carries it.) No MbientLab SDK ever parsed a MAC from advertisements, consistent with there being nothing to parse. Replaces the claim with reality and documents the sanctioned host-configured MAC broadcast: scan response = Complete Local Name AD + Manufacturer Specific Data AD (company 0x626D, MAC LSB-first), including the exact byte layout, the 0x08/0x07 partial-write split, on-boot-macro persistence semantics (record-without-execute, erase-all to update, wiped by firmware flashes), and the reference implementation in MetaWear-API-Swift. Heading unchanged so existing deep links keep resolving.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The "MAC Address and BLE Advertising" section claimed the MAC "is included in the device's advertising data and can be read during scanning". Field-verified false on firmware 1.7.x: default advertisements carry only the local name and the MetaWear service UUID. (Android/Windows see the MAC because the OS exposes the link-layer address itself; no MbientLab SDK ever parsed a MAC from advertisements — consistent with there being nothing to parse.)
This PR replaces the claim with reality and documents the sanctioned host-configured MAC broadcast now shipped in the Swift SDK: scan response = Complete Local Name AD + Manufacturer Specific Data AD under company
0x626D, MAC LSB-first — with the exact byte layout, the0x08/0x07partial-write split, and the persistence semantics (execute-on-boot macro, record-without-execute, erase-all to update, wiped by firmware flashes). Reference implementation linked.Heading text unchanged, so existing
#mac-address-and-ble-advertisingdeep links keep resolving. Merging deploys to docs.mbientlab.com.🤖 Generated with Claude Code