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 an uneditable, randomly generated string of alphanumeric characters (4 characters long in case of Double battery Beacons, Tough Beacons, USB Beacons, Beacon Pro, and 5 characters for Cloud Beacons and Gateways).
You can find the Unique ID printed on sticker placed on the back or side of your beacon, for Cloud Beacons, this sticker is under the mounting bracket.
As long as a beacon is in the connectable mode, its Unique ID is also transmitted in a scan response packet. Thanks to that you can see that identifier in your Admin App without establishing a connection to a beacon.
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”.
Alias plays a similar role as Name does but in the Web Panel. If you need to add additional description (e.g. entrance or exit beacon) for your beacon in the Web Panel, using Alias is the best way to do this.
There are no limitations how long an Alias should be. Alias is stored only in the database, 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.