Tracking
Device Status & Presence
Device status in Pointeron is split into separate layers. Presence tells you whether Pointeron has heard from a device or source recently. Tracking and lifecycle badges tell you whether Pointeron should process that device. Sync health tells you whether scheduled Apple source checks are healthy.
Status layers
Pointeron shows several badges because one word like "online" is not precise enough for every device type.
| Layer | What it answers | Examples |
|---|---|---|
| Presence | Has Pointeron heard from this device or location source recently? | Connected now, Recently reported, No recent update, Location available |
| Lifecycle | Is this device assigned and active in Pointeron? | Active, Pending, Pool, Repair |
| Tracking | Is Pointeron allowed to process incoming locations for this device? | Tracking, Not tracking |
| Sync health | Is the scheduled Apple source check healthy? | Active, Pending, Syncing, Failing |
| Configuration sync | Does a GPS tracker match the desired server-side configuration? | In sync, Pending, Drifted, Failed |
Read badges independently
A device can be active and tracking but still not connected. A device can also have a fresh location available while its lifecycle is pending if it has not been fully activated in Pointeron yet.
Tracking and activation
Tracking in the dashboard is shown as an effective state, not just the raw device toggle.
For a device to show as Tracking, all of these must be true:
- tracking is enabled for the device
- the device billing status allows tracking, such as active, exempt, or valid test mode
- the device is not in a non-tracking lifecycle state such as pool, repair, retired, or inactive
If a device shows an activation banner, its organization subscription can still be active. The banner means that this specific device is still in per-device activation, such as pending activation or pending billing, and Pointeron will not treat it as effectively tracking until activation is completed.
GPS tracker presence
GPS tracker presence is based on the TCP connection and the most recent tracker report.
| Presence | Meaning | How it changes |
|---|---|---|
| Connected now | The tracker currently has an open TCP session with Pointeron and the IMEI/device ID was recognized. | Starts when the tracker connects and completes protocol login. A location point is not required after login for the connection itself to be known. |
| Recently reported | Pointeron does not currently have a live TCP session, but the tracker reported recently. | Shown for up to 15 minutes after the latest report when there is no active TCP session. |
| Not connected | There is no live TCP session and the last report is older than the recent window. | Usually appears 15 minutes after the last report, or sooner for a device that has never sent a usable report. |
| Never seen | Pointeron has no report timestamp for the tracker. | Changes after the first valid report. |
When a GPS socket closes, the tracker leaves Connected now immediately. If the tracker reported shortly before closing, it will usually show Recently reported until the 15 minute recent window expires.
For supported Teltonika trackers, Connected now means Pointeron can dispatch a GPRS configuration command immediately. If the tracker is only Recently reported or Not connected, supported configuration changes and read-back requests stay queued and are delivered when the tracker opens its next TCP session.
Apple and API presence
Apple and Pointeron API sources do not have a long-lived TCP socket like GPS trackers. Their presence is based on the latest successful source check or report.
| Source | What refreshes presence | What the status means |
|---|---|---|
| Apple devices via Find My | A successful Find My check for iPhones, iPads, Macs, or Apple Watches. | Shows whether Apple returned a usable location, reported the device as reachable without a new location, reported it offline, or marked it lost. |
| Apple items via Find My | A successful Find My item check for AirTags and compatible items. | Shows whether the item returned a usable location or whether the item check has gone stale. |
| Pointeron API | A fresh location report sent to Pointeron for a device managed through the API. | Shows whether Pointeron received a recent report. It does not prove Apple reachability. |
Apple and API presence labels
| Presence | Meaning |
|---|---|
| Location available | The latest fresh check or report included a recent usable location. |
| Reachable, no new location | The source was reachable, but Pointeron does not have a recent usable location for the device. For Apple devices this can happen when Apple reports the device online without GPS/location data. |
| Offline at last check | The latest fresh Apple check reported the device as offline or unreachable. |
| Lost Mode | Apple reports the device or item as lost. |
| No recent update | Pointeron has not received a fresh check or report inside the allowed freshness window. |
The freshness window is based on the effective sync or reporting interval:
| Device/source type | Default freshness window |
|---|---|
| Apple devices via Find My | About 30 minutes |
| Apple items via Find My | About 10 minutes |
| Pointeron API devices | About two times the configured reporting interval, with a minimum of 120 seconds |
If a source reports again before the window expires, presence stays fresh. If it does not, the device becomes No recent update.
Sync health labels
Sync health is separate from presence. It describes the scheduler or source health, not the latest location result.
| Sync health | Meaning |
|---|---|
| Pending | The source is waiting for its first successful scheduled check or has been reset for retry. |
| Active | The latest scheduled check succeeded. The device may still be offline at the Apple side. |
| Syncing | A source check is currently in progress. |
| Failing | Repeated checks are failing, but Pointeron has not disabled tracking for the device. |
| Auto-Disabled | Repeated failures crossed the malfunction threshold and Pointeron disabled tracking for safety. |
| Disabled | Syncing or tracking was manually disabled. |
Test data and simulations
Synthetic location tools and API test reports can update current location, last reported time, counters, and history. They do not always prove the same thing as a real device.
| Test path | What it can prove | What it cannot prove |
|---|---|---|
| Direct location test data | Map/history behavior and last reported freshness. | A live GPS TCP connection or Apple reachability. |
| Pointeron API test reports | API reporting path, filtering, counters, live updates, and Pointeron API presence. | Apple reachability or GPS GPRS command delivery. |
| GPS TCP test data | TCP reporting behavior and GPS location processing. | A physical device will stay connected after the test socket closes. |
For troubleshooting, first identify which layer you are checking. Use Connected now for immediate GPS command delivery, Last seen for recent reports, No recent update for Apple/API freshness, and Sync health for scheduled source failures. Queued GPS commands still require the tracker to reconnect before they can be applied.