Skip to main content

Download CSV File




  • Official comment
    Marcin Kacik

    For all nRF52-based devices we divide all possible advertising packets into four groups:

    • packets (Secure Profile, Telemetry and Location)
    • iBeacon
    • Eddystone (UID, URL, TLM)
    • Encrypted Eddystone (EID, ETLM)

    These beacons use separate virtual BLE broadcasters to send packets from each group. Because of that, packets from different groups have different MAC addresses, so by 3rd party scanners they are treated as packets sent by unrelated beacons.

    However, MAC addresses of and standard iBeacon and Eddystone packets are sequential and this information can be used to associate various packets with each other. For example, if a given beacon broadcasts packets with using 12:AB:45:CD:EF:F1 address, then iBeacon packets from that beacon will have 12:AB:45:CD:EF:F2 MAC and Eddystone packets will use 12:AB:45:CD:EF:F3.

    Please keep in mind that sequential MAC addresses apply only to standard, unencrypted and not shuffled packets. It means that Eddystone EID and ETLM packets, as well as Secure iBeacon and Eddystone packets always use random MAC addresses.

    MAC addresses can be extracted from API [getDevice]( That extracted MAC will be for Kontakt Packet.

  • Damian Kuźma

    Hello Terry,


    Due to the implementation of packet interleaving solution, each beacon can use multiple MAC addresses.

    It is possible to get the MAC address used for packets from the API and Panel but since the Eddystone and iBeacon use addresses that are randomly assigned when the chip is programmed, the only way is to scan each device individually. 

  • WVUMIT Web Services

    Right, but is it possible to get that mac address which is in the API exported out to a CSV?


Please sign in to leave a comment.