There are several ways to identify your beacons, and each of them has its pros and cons. This article will help you understand how beacon identifiers work so you can fully use them in your deployment management.
NOTE: Those properties should not be confused with identifiers that are transmitted as a part of iBeacon or Eddystone advertising packets, which are used to trigger content, events, actions, etc. in end-user apps. The identifiers that we’re covering here are meant to help you in beacon management.
Every beacon has its own Unique ID. There are no two Kontakt.io beacons with the same Unique ID. This identifier is a randomly generated string of alphanumeric characters (4, 5 or 6 characters long) that can't be edited.
You can find the Unique ID printed on a sticker placed on the side of your beacon or Gateway.
As long as a beacon is in the connectable mode, its Unique ID is also transmitted in a scan response packet (for older nRF51 chip devices) and only in the Secure Profile packet for the new nRF52 chip devices. Thanks to that you can see that identifier in your Admin App without establishing a connection to a beacon.
The Unique ID is also visible in the Kontakt.io Proximity Web Panel:
You can also use the filters to sort your devices by Unique Id (default filter option).
Apart from Unique ID, scan response packet contains a Name of a beacon, which is also visible in Admin Apps without connecting to a beacon.
As opposite to Unique ID, this value is editable, so you can set any beacon's Name you want, as long as it is 15 ASCII characters or shorter. You can do that directly in the app, or by creating a config for your beacon through the Kontakt.io Proximity API by specifying a new name property, and then synchronizing configs through the Admin App. Currently, there is no way to create a config with a new name through the Web Panel.
By default, all beacons have the same Name: “Kontakt”.
Notes play a similar role as Name, as they allow you to further identify your beacons. However, you can also describe where the beacon is located or enter additional information that would be of use in your current scenario. So, if you need to add further descriptions (e.g. entrance or exit beacon) for your beacon in the Web Panel, using Notes is the best way to do this.
The Notes should be less than 1024 characters. They are stored only in the database, which means they don't synchronize with the beacon, they only live in the Kontakt.io Cloud. You can access it in the Web Panel, Admin apps or via the API, but there is no way to read it directly from a beacon.
Notes are also available for Gateways, however, this information is only visible in the Web Panel.