Skip to content
English
Contact us
  • There are no suggestions because the search field is empty.

My Assets Don't Show in the Geofence

If your assets are not showing inside the Geofence you just created, this article covers the main reasons.

How Asset-to-Geofence Association Works

Geofences in Perspio are dynamically evaluated based on an asset’s most recent GPS position. Once a geofence is created or updated, the system does not retroactively evaluate past locations; it waits for a new telemetry event from each asset before reassessing its location relative to the geofence boundaries.

This means that for an asset to appear inside a new geofence, the device installed on that asset must communicate again with a valid GPS reading after the geofence has been created.

Why Assets Might Not Appear

1. The Asset Has Not Reported a New Location Yet

Assets will only be evaluated against a geofence after the next position update. This applies to:

  • Stationary assets (parked)

  • Assets in storage

  • Devices that have not moved or are in idle mode.

What to do:

  • Wait for the asset to move or trigger a communication event.

  • Alternatively, power cycle the device or generate an ignition event to force a new position update.

2. The Device Is Offline or Not Communicating

If a device is inactive, suspended, or has not communicated for some time, Perspio cannot determine whether it is within any geofence.

What to check:

  • Navigate to Device Health to confirm the asset is online.

  • Review last communication time in the Asset Inspector.

  • Ensure the device is powered and has GPS location.

3. Manual Location Override Enabled

If the asset is configured with a manual static location, Perspio will not consider live GPS updates for that asset—meaning geofence association might not be calculated correctly.

How to resolve:

  • Navigate to the Assets module.

  • Open the asset’s configuration and disable Manual Location Override.

  • Save and wait for the next GPS event.

4. Geofence Sync Is Pending

When a new geofence is created or updated, it may take a few minutes for the system to fully index it. During this time, the asset list and map representation may not reflect the geofence correctly.

What to do:

  • Wait 1–3 minutes.

  • Refresh the map or re-open the Geofences module.

5. The Asset Is Outside the Boundary

The last reported GPS location of the asset may, in fact, place it just outside the defined geofence boundary—even if it seems like it should be inside.

To verify:

  • Open the Asset Inspector Map view.

  • Enable the Geofences Object in the Map Options - bottom right corner of the map.

  • Cross-check the GPS pin relative to the geofence polygon.

6. Filter or Visibility Restrictions

Ensure you’re not filtering out assets via:

  • Security Group visibility

  • Asset Type filters

These filters may prevent assets from being displayed on the map or in the geofence table.

Recommended Troubleshooting Steps

To resolve the issue of missing assets in a geofence:

  1. Open the Geofences Module

    • Search or locate the geofence in question.

    • Review the list of associated assets and condition, if applicable.

  2. Verify Device Health

    • Go to Device Health or Asset Inspector to ensure the device is online and GPS-capable.

  3. Check for Recent Communication

    • If the asset hasn’t moved or reported recently, wait or prompt a new communication.

  4. Review Manual Location Override

    • Disable static location if it's set.

  5. Check Visibility Filters

    • Ensure no filters are hiding assets from your view.

  6. Use the Map for Spatial Confirmation

    • Overlay the Geofences Object in Asset Inspector and check actual asset position.

Summary

Assets do not automatically appear in newly created geofences until they send a new GPS update. This real-time logic ensures that Perspio only displays assets based on current, reliable telemetry.

If an asset does not show, it’s usually due to a lack of recent communication, manual location override, or the asset being outside the boundary. Most issues resolve automatically with the next device event.