The a list of the multi-part identifiers of the beacon. Together, these identifiers signify
a unique beacon. The identifiers are ordered by significance for the purpose of grouping
A list of generic non-identifying data fields included in the beacon advertisement. Data
fields are limited to the size of a Java long, or six bytes.
A list of generic non-identifying data fields included in a secondary beacon advertisement
and merged into this beacon. Data fields are limited to the size of a Java long, or six
A double that is an estimate of how far the Beacon is away in meters. Note that this number
fluctuates quite a bit with RSSI, so despite the name, it is not super accurate.
The measured signal strength of the Bluetooth packet that led do this Beacon detection.
The calibrated measured Tx power of the Beacon in RSSI
This value is baked into an Beacon when it is manufactured, and
it is transmitted with each packet to aid in the mDistance estimate
The Bluetooth mac address
The number of rssi samples available, if known
The number of packets detected in the last cycle
If multiple RSSI samples were available, this is the running average
The two byte value indicating the type of beacon that this is, which is used for figuring
out the byte layout of the beacon advertisement
A two byte code indicating the beacon manufacturer. A list of registered manufacturer codes
may be found here:
If the beacon is a GATT-based beacon, this field will be set to -1
A 32 bit service uuid for the beacon
This is valid only for GATT-based beacons. If the beacon is a manufacturer data-based
beacon, this field will be -1
The Bluetooth device name. This is a field transmitted by the remote beacon device separate
from the advertisement data
The identifier of the beaconParser used to create this beacon. Useful for figuring out
An indicator marking this beacon as a potential multi frame beacon.
This will be set to true if the beacon was parsed by a BeaconParser which has extra
data parsers defined.