Azuga Driver Beacon Card Technical Information and Pairing

← Back to the driver beacon card

This is the technical sheet for the Azuga driver and occupant beacon. It covers how the card is found, how it gets paired, the one light it has, and what Azuga has not said.

The one light: tap a step

Button version only

Azuga documents a red LED on the button version of the card. Azuga does not say whether the $15 shop card is that version. If your cards have no button, there is no light to read. The playback is sped up, since the real wait is about 30 seconds.

Tap a step to see it

Each button shows the card at that step and says out loud what Azuga documents.

Button version, documented steps

Sound

🔇 Azuga does not mention a speaker or beeps on the beacon card.

That is silence in the documents. We treat it as silent.

How the tracker finds the card

The OBD device scans for cards when the ignition goes on and, depending on configuration, when it goes off. It sends each card's details, plus its distance and location relative to the tracker, to Azuga. Azuga's back end matches the card to a person. Each card has its own serial number and MAC address.

Where the results show up

Azuga says occupants appear in its Breadcrumb, Activity and Summary reports. The Azuga Fleet mobile app also lists occupant recognition among its functions. Azuga's pricing page puts occupant recognition in the SafeFleet tier, not BasicFleet. Tier contents on Azuga's own pages do not always agree, so confirm the tier on your quote.

All the pairing methods Azuga lists

Azuga's driver and vehicle pairing article lists seven ways to tie a driver to a vehicle. Two involve beacons.

Method	Beacon?
Web portal	No
Manual, in the mobile app	No
Automatic Bluetooth, phone app to vehicle device	No
QR code sticker	No
Beacon (automatic detection)	Yes
Beacon button	Yes
API	No

Assigning a card to a person

In Azuga Fleet, open Admin, then Devices, then the Beacons tab.
Click the pencil icon for the card.
Pick the driver and click Submit.

The serial number and MAC address cannot be edited.

Rules of thumb from Azuga

With automatic detection, the driver is unpaired at ignition off, or when another card holder enters.
Button pairing: the last driver to press becomes the paired driver by default.
One pairing type per account at a time.
Existing button cards are enrolled through customer care.

When a card is not recognized

Azuga does not publish a fault tree for the card. These are the facts from its pairing articles that bear on a card that is missed:

Timing. For the button version, the press comes about 30 seconds after the ignition goes on. A press that comes late has no effect.
Pairing type. An account uses one type at a time. If the account is set to automatic detection, a button press is not the method in use.
Crowding. The tracker detects up to four cards at once. In a full crew cab, extra cards will not all be seen.
Interference. Bluetooth and Wi-Fi share 2.4 GHz, and Azuga says they can interfere.
Who wins. With several cards in a vehicle, the first one detected is the driver by automatic detection, and the last press is the driver with buttons.

Not verified

The model number of the $15 shop card.
Whether that card has a button and a red LED.
How long the red LED stays lit.
A product photo hosted by Azuga.

Sources: What is a beacon, Associating a driver with a beacon, Vehicle and driver pairing methods, Button press pairing, Pairing overview. AZUGA is a trademark of its owner. API Signal is an independent installer and is not Azuga.

Azuga Driver Beacon Card, technical information