Mastering Azuga
★ Fleet GPS Trackers · Azuga Guide
Every light pattern Azuga documents, played on a drawing of the tracker, with a voice that says what each one means.
This page is the technical sheet for the Azuga plug-in tracker: what the lights mean, whether it makes any sound, the published specs, how to prove it is reporting, and what to do when it is not.
Azuga publishes more than one light scheme
Azuga's own articles describe more than one way to read these lights, and none says which hardware generation it covers. A third article (305) uses green for connected to the vehicle, amber for a GPS fix and red for communication with Azuga established, which does not match the stage article. The blink speeds in the stage view are for illustration, because Azuga does not publish exact timing. In the install-check scheme, green is the main status light. In the stage scheme, green, amber and red each stand for a stage (engine, GPS, carrier). We show both and label the source on each button. Trust the result in the Azuga portal over any single light. Azuga also names the third light "amber/blue" without describing it, so we draw it amber.
Tap a light pattern to see it
Each button plays the pattern on the device above and says out loud what it means.
🔇 No Azuga page lists a speaker or beeps for this tracker.
That is silence in the documents, not a statement from Azuga that it has no sound. We treat the tracker as silent in the field and will change this page if Azuga says otherwise. This is a light-only device guide for now.
Do not stare at one light and decide. Plug the tracker in, watch the first few seconds, then go to the portal. A solid green with no vehicle in the portal means the install light check passed but the account side is not finished, in our experience often a registration problem, such as a serial number never matched to a vehicle. A tracker that blinks green every two seconds and never settles is telling you it cannot reach the network, so look at where the vehicle is parked before you blame the unit.
Because Azuga documents more than one scheme, the safest habit is to write down what you saw, wait the registration time, and then check the portal. If the portal and the lights disagree, the portal wins.
| Item | Value |
|---|---|
| Dimensions and weight | 1.7 x 1.8 x 1 in, 31.1 g |
| Supply and sleep draw | 8 to 32 V, under 4 mA asleep |
| Satellite channels | 118 acquisition and 40 tracking, 2.0 m CEP, internal antenna |
| Vehicle protocols | GMLAN, ISO 15765, ISO 9141-2, J1850 PWM and VPW, KWP-2000, ISO 14230-4, auto-detected, plus multi-CAN |
| Processor and memory | Cortex A7 running Linux, about 250 MB RAM, about 500 MB flash, over-the-air updates |
| Backup power | 10 F supercapacitor |
| Certifications | FCC, PTCRB, AT&T, RoHS |
Sources: Azuga Fleet Device Cheat Sheet, Azuga "is it working" article, Azuga no-light article, Azuga technical specifications. AZUGA is a trademark of its owner. API Signal is an independent installer and is not Azuga.
Tell us how many vehicles and what they are. We'll quote the installation.
Constant. Ignition. Ground. API Signal.Disclosure: API Signal may receive a referral fee from Azuga when a fleet signs up with Azuga through us. It does not change what we tell you on these pages, including the places where Azuga is not the best fit.