Skip to main content

Getting started with the beacon

Based on AT2 firmware v2.6

Seven steps, from unboxing to a supervised beacon. Each step ends with a How do I know it worked? check.

1. Unbox​

  • Check the variant on the label: ATEX zone 0, ATEX zone 2 or IECEx (certifications). It must match the zone where the beacon will be installed.
  • Note the DevEUI, JoinEUI (AppEUI) and AppKey provided with your beacons. You need them in step 2.
ATEX

Never open the casing in a hazardous area. Opening it (USB access, battery replacement) is done in a safe zone only. Everything in this guide can be done with the casing closed.

How do I know it worked? You have one DevEUI / JoinEUI / AppKey triple per beacon, and the ATEX marking matches your site.

2. Register the beacon on your LoRaWAN network​

Create the device on your network server (ThingPark, The Things Network, ChirpStack, etc.) as an OTAA, LoRaWAN 1.0.2, Class A device, with the keys from step 1. If your network server offers an Abeeway device profile or decoder for AT2 trackers, use it. You can also decode payloads with the AT2 Payload Decoder.

How do I know it worked? The device appears on your network server, waiting for its first join.

3. Activate the beacon and join the network​

Recent beacons leave the factory activated: they start joining as soon as they are powered. Otherwise, use the magnet sequence.

How do I know it worked? On your network server you see a join request, a join accept, then the first uplinks, including a heartbeat (message type 0x05). If nothing arrives, check the keys, the region and the gateway coverage, then see Reset & re-join.

4. Configure the beacon frame​

The beacon is delivered as an iBeacon with a generic UUID (see Configuration explained). In most projects you set your own identifiers:

  1. Open the Beacon configuration tool.
  2. Choose the frame type required by your RTLS or indoor-location engine (iBeacon, Eddystone UID, AltBeacon or Quuppa) and enter its content.
  3. Copy the LoRaWAN downlinks and send them on port 2 from your network server. Downlinks are delivered after the beacon's next uplink, so allow up to one heartbeat period (10 minutes).
tip

Prepare a batch of beacons on the bench? The CLI over USB is faster, but requires opening the casing (safe zone only). The tool also generates the CLI commands.

How do I know it worked?

  • Each parameter change is confirmed by a configuration uplink (type 0x07, see Configuration messages).
  • A BLE scanner app (nRF Connect, Beacon Scanner, etc.) next to the beacon shows your new frame (for example your iBeacon UUID, Major and Minor).

5. Install the beacon​

Follow the placement rules: for BLE location, mount it vertically on a wall or a pole, 2 to 3 m above the floor, with few obstacles around it. For geozoning, place one beacon inside each room (wall or ceiling) and adjust the transmit power to the size of the room.

How do I know it worked? Your RTLS or location engine sees the beacon at its installed position.

6. Supervise​

With the delivered configuration, the beacon sends a heartbeat every 10 minutes. Every uplink header carries:

  • the battery level in % (estimated from consumption, see Power consumption),
  • the temperature.

See the common message header to decode them, or use the AT2 Payload Decoder.

Optional: configure temperature thresholds to receive an alert when the temperature leaves a range.

How do I know it worked? Your back-end shows a heartbeat about every 10 minutes for each beacon, with a battery level and a temperature.

7. Maintain​

TaskHow
Change the configurationBeacon configuration tool, sent by downlink
Reset or move to another networkReset & re-join
Replace the AA batteriesReplacing compact tracker batteries (safe zone only), then reset the battery counter, see Good to know
Update the firmwareFirmware update (opens the casing; re-apply the beacon configuration afterwards)

How do I know it worked? After maintenance, the beacon sends heartbeats again and still advertises your frame.