The GSFleet connection automatically brings linked devices' locations and odometer readings from GSFleet to Spots in Spotilla. You can enable location updates, odometer updates, or both. A location update and a read event are separate things: a Spot's location can change without a new read event.
Prerequisites
The GSFleet feature must be enabled for your organization. Connection settings and device links are configured in the browser service with administrator permissions. You need edit access to the Spot you want to link, and the Spot must have a tag with an internal ID. You cannot create a link to a deleted Spot. If needed, see linking a tag to a Spot.
You need a GSFleet API key that provides access to the devices you want to use. If GSFleet does not appear under integrations, see integration setup prerequisites.
Save and verify the connection
- In the browser service navigation, open Settings → Integrations → GSFleet.
- Open Authentication, enter the API key, and select Save. Saving checks the connection to GSFleet. If the check fails, the new credentials are not saved.
- You can check the saved key later by selecting Test Connection. A successful test updates Last verified successfully.
The connection test checks access to the GSFleet device list. It does not confirm that a particular device's location or odometer reading has been updated on its Spot.
The Environment menu shows Production and Sandbox. The GSFleet connection uses the same service for both choices. Selecting Sandbox does not prevent Spot data from changing if updates are enabled.
Link a device and select the data to update
- Open GSFleet Settings and select Linked devices under Spot Sync.
- Select Link new device. Select a Spotilla Spot, then select the corresponding GSFleet device under Select device. The name, registration number, serial number, and IMEI can help identify the device if GSFleet returns these details.
- Confirm by selecting Link new device. One GSFleet device can be linked to a Spot, and the same GSFleet device can be linked to only one Spot.
- Under Spot Sync, select the updates you need: Update Spotilla locations from GSFleet, Update Spotilla odometer readings from GSFleet, or both.
- If you enable odometer updates, select an available numeric attribute under Odometer attribute (km). Make sure the same attribute exists on every Spot whose reading you want to update. A missing attribute is not created automatically. Save the settings.
The selected attribute is shared by all linked devices. If the field is missing from a Spot, see editing Spot details. The folder's device card can determine which fields a Spot has; changing it may also affect other Spots.
Automatic updates are scheduled approximately every 10 minutes. Linking a device does not immediately fetch data. Updates also depend on the background run completing and the data returned by GSFleet.
How is the odometer reading saved?
The odometer reading returned by GSFleet is saved in kilometres to the selected Spot attribute. It is an odometer reading, not an operating-hours reading or distance travelled calculated from GPS points. The returned number must be valid, finite, and greater than 1. The number is divided by one thousand and rounded to three decimal places: for example, 12345 is saved as 12.345 km.
An empty attribute value is filled in. An existing value is replaced only if the converted and rounded reading is greater. An equal or lower reading does not change the value. If the previous value is not a valid number, the update is skipped; check and correct the value in Spotilla if needed. The update changes the existing attribute value, and a history of changes is retained. See data field history.
An odometer update does not require a valid or new GPS location. The GPS measurement time is not used with the odometer reading, so the saved value or the run's log entry alone does not indicate when the reading was measured.
How are locations and read events updated?
When location updates are enabled, synchronization fetches the location of each linked device. An accepted location replaces the Spot's saved coordinates, including a location previously set manually. On Android and iOS, you can open the Location view from the Spot details to see it on the map. In the Android device list, the location may appear as Fixed location because the coordinates are saved on the Spot. This label does not mean that GSFleet updates have stopped.
- The first accepted location saves the location and initializes the movement reference point. It does not create a read event.
- Newer location data updates the Spot's coordinates if they have changed. An unchanged location does not create a read event.
- A distance of more than 50 metres from the reference point creates a read event. The reference point then changes to the location of the new event. Before the first event, the reference point is the location saved during initialization.
For example, a device moves 30 metres and then another 30 metres in the same direction. The first update changes the location without creating a read event. When the new location is 60 metres from the reference point, a read event is created. The distance is calculated between coordinate points, not as distance travelled. Exactly 50 metres is not enough.
A read event created by GSFleet is automatic: it is not associated with a mobile user and does not require a physical tag scan. The event time is when it was recorded in Spotilla, not when GSFleet took the measurement. The device's coordinates are saved with the event. See also viewing read events on the map.
Check the result and troubleshoot a missing update
After the first run, check the selected attribute on the correct Spot and compare the reading with the GSFleet data. For location updates, also check the Spot's location on the map. In the browser, open Settings → Integrations → GSFleet → Integration Logs and find the run summary. It shows, among other things, the number of updated locations and read events, as well as the numbers of odometer readings that were updated, unchanged, skipped, or processed with errors. The summary covers the entire run, so also check the individual Spot's data. See investigating an integration error in the log.
If the odometer is not updated, check the update selection, the device link, and that the selected numeric attribute exists on the Spot. Also check the reading returned by GSFleet and whether the Spot already has a higher or invalid value.
A location is accepted only if it has valid coordinates and a measurement time. Missing or invalid data is skipped. After initialization, data with the same measurement time or an older measurement time is also skipped. The location in Spotilla then remains unchanged; a point on the map alone does not guarantee the device's current location. Synchronization does not import the device's complete route or every measurement taken in between.
The Spot statuses Inactive and Faulty do not stop location or odometer updates. A connection error can prevent an individual device from being updated. An authentication error, exceeding the GSFleet request limit, or three consecutive temporary errors in location or odometer requests of the same type stop the remaining processing for that run. After an authentication error, automatic requests stop until the credentials are verified again by successfully saving them or testing the connection.
Pause updates and remove links
Temporary pause: under Spot Sync, clear the selection for the update you want to stop and save. Clearing the location selection does not stop odometer updates, and vice versa. To stop both, clear both selections. Links, last values, and read events are retained. When you enable location updates again, movement comparison continues from the previous reference point.
Unlink one device: open Linked devices, select the trash icon on the row, and confirm. This stops both updates for that device and removes the link between the device and the Spot. It does not delete the Spot, the GSFleet device, the Spot's last location, its attribute value, or its previous read events and attribute history. You can then link the device or Spot again. A new link initializes location tracking from the beginning.
Changing a Spot's status to Deleted automatically removes its GSFleet link. Restoring the Spot does not restore the link; you must create it again.
Disable the connection: first unlink all GSFleet devices. Then, on the Authentication tab, select Clear saved credentials. This removes the saved GSFleet API key and the settings for both updates. Spot locations, attribute values, and previous events are retained.