Good to know & FAQ
The points below are where beacon users most often get confused. Each links to the AT2 reference for details.
Good to know
The beacon has two different Bluetooth roles
| Role | What it is | Controlled by |
|---|---|---|
| Beaconing | The iBeacon / Eddystone / AltBeacon / Quuppa frame, advertised permanently. This is what your RTLS sees. | beaconing_* and beacon_id_* parameters |
| Connectivity advertising | A temporary advertisement (name ABW…) used to connect to the device. It stops after ble_cnx_adv_duration (600 s by default) if no device bonds. | ble_cnx_adv_duration, the magnet, the start/stop BLE advertisement downlink |
Seeing an ABW… device in a scanner does not mean beaconing is working. Look for your beacon frame (UUID, namespace…).
The magnet does not reset the beacon by default
With the default reed_switch_configuration (3), the magnet sequence starts connectivity advertising. It resets the beacon only if the parameter is set to 1. Before activation (shipping mode), the sequence always starts the LoRaWAN join. See Reset & re-join.
Moving the beacon speeds up advertising
The beacon uses two advertising intervals: beaconing_static_interval (500 ms in the delivered configuration) and beaconing_motion_interval (200 ms). When the accelerometer detects a motion, the beacon advertises at the motion interval for beaconing_motion_duration seconds (20 s). A beacon installed on a vibrating machine therefore advertises at the faster rate most of the time, and its battery drains faster. Set both intervals to the same value if you don't need this behaviour.
TX power is an index, not dBm
beaconing_tx_power = 1 means +3 dBm, not 1 dBm. The scale goes from 0 (+4 dBm) to 8 (−40 dBm): see the TX power table. Higher power means a longer range and a shorter battery life.
Negative values in configuration files are normal
beacon_id_0=-1410465791 is the same as 0xABEE0001. Configuration files and CLI commands read 32-bit signed integers, so values of 0x80000000 and above appear as negative numbers. See Why are some values negative?
After replacing the batteries, reset the battery counter
The battery level reported by the beacon is estimated from its consumption since the batteries were new (a primary battery's voltage stays flat until the end). After you replace the AA cells, reset the counter, otherwise the beacon keeps reporting the old level. Send this downlink on port 2:
0B01F700000000
(0B set parameter, 01 ack token, F7 power consumption, 00000000 = 0). Details: Power consumption.
The CLI equivalent requires a support access level. Use the downlink.
Without any downlink for a week, the beacon resets itself
To recover from a lost network, the beacon asks the network for a link check after 5 days without any downlink (including network MAC commands), then resets and re-joins 2 days later if it still gets no answer. On a working LoRaWAN network this never happens. Frequent resets point to a coverage or network-server problem. See Network timeout monitoring.
Downlinks are delivered only after an uplink
The beacon is a LoRaWAN Class A device: it listens only right after sending. With a heartbeat every 10 minutes, a downlink can take up to 10 minutes to reach the beacon.
A firmware update erases parameters set by downlink or CLI
Parameters changed by downlink or CLI are stored in flash and are lost when a new firmware is flashed. Re-apply your configuration after an update, or flash the firmware together with a configuration file (the Beacon configuration tool generates one).
Quuppa works differently
With beaconing_type = 2, the beacon emits a Quuppa tag packet. The tag ID is derived from the beacon DevEUI, so the beacon_id_* parameters are not used. See the Quuppa application note (AN-012) in Firmware resources.
FAQ
Is there a specific beacon firmware? No. The beacon runs the standard AT2 firmware with a beacon configuration. See What this beacon is.
Can I configure the beacon with the Abeeway mobile app? No, the app is discontinued. Use LoRaWAN downlinks (recommended), or the CLI over USB in a safe zone.
How do I know which configuration my beacon is running?
Send the request configuration downlink for the parameters you want to check. For example 0301 followed by 6A6B6C6D6E7071727374 returns the beaconing parameters. Over the CLI, use config show.
How do I check that beaconing is on?
Use a BLE scanner app next to the beacon and look for your frame. Over the CLI, ble info shows the beaconing state.
I changed beacon_id_x but my RTLS still sees the old ID.
Check that the downlink was received: the confirmation uplink, or the ack token in the next uplinks (see Ack token). Then check the byte order with the Beacon configuration tool, using its Decode mode.
How long does the battery last? It depends mainly on the advertising intervals, the TX power and how often the beacon moves. Contact Abeeway support for an estimate based on your configuration.
Can I make the beacon locate itself? The hardware can, but that is the compact tracker use case. See the AT2 reference guide.