Eternet Portal Documentation

Vehicle Fleet Management

Module overview

The Vehicles module helps operators find a vehicle, review its current information, explore its telemetry, and manage which shared geofences apply to it. Fleet-level browsing and vehicle-specific work are available through the portal.

The portal presents vehicle data supplied by Eternet APIs and connected services. It does not replace the vehicle service, the time-series store, the MQTT broker, or Traccar.

Fleet view

Operators can browse the vehicle list, search for a vehicle, and open its detail workspace. The fleet experience also supports a map view for vehicles with usable location data.

  • Find and open a vehicle from the fleet list.
  • Review available vehicle status and location information.
  • Use the map view to understand vehicle locations geographically.
  • Open a vehicle to move from fleet-level visibility to its detailed workspace.

Map locations depend on valid coordinates being available from the configured data sources. Live updates depend on the relevant MQTT subscription and incoming telemetry.

Vehicle workspace

Each vehicle has a detail workspace organized around four areas:

Overview
Summarizes vehicle identity, connectivity, location, available data, and configured dashboard widgets.
Properties
Shows editable vehicle information such as its name, identifiers, phone, tags, visibility, publisher, and access settings.
Data Streams
Lists the vehicle’s available telemetry streams and provides access to recorded values and time-range exploration.
Geofence
Lists shared geofences and lets an operator assign or unassign an existing geofence for this vehicle.

Telemetry and history

Vehicle stream definitions and time-series records are loaded through the Eternet API. Historical vehicle records are queried for a selected time range and can be presented for review and charting.

MQTT telemetry can provide changing stream values and coordinates to the portal’s live vehicle and widget experience. For a value to update, the vehicle must be matched to the incoming message and the payload must contain a recognized stream name or valid latitude/longitude coordinates.

Live MQTT status should be distinguished from stored history: a broker message is a live event, while historical records are retrieved from the configured time-series service.

Geofence management

Geofences are shared definitions managed from the portal’s Geofences section and synchronized with Traccar. The Geofence tab on a vehicle is for assignment—not for creating a separate vehicle-owned copy of the area.

  1. Create or edit the shared geofence in the Geofences section.
  2. The portal sends the geofence operation through the Eternet Vehicle Service to Traccar.
  3. Assign or unassign the existing geofence from the vehicle’s Geofence tab.
  4. Traccar remains the system responsible for geofence processing and enforcement.

Removing an assignment from a vehicle is different from permanently deleting a shared geofence. Permanent deletion belongs in the central Geofences management area.

Data and service architecture

The Vehicles interface is a portal layer over Eternet’s vehicle APIs and connected systems. The main responsibilities are:

  • Eternet Portal: fleet browsing, vehicle workspace, data presentation, and geofence assignment controls.
  • Vehicle Service and Core API: vehicle resources, stream definitions, vehicle records, and Traccar integration endpoints.
  • MQTT broker: delivery of configured live telemetry messages used by the portal’s live values and location experience.
  • Time-series storage: persistence and retrieval of historical vehicle telemetry for selected time ranges.
  • Traccar: the authoritative system for shared geofence definitions, vehicle assignments, and geofence processing.

In short: the portal is where operators work; the connected Eternet services and Traccar provide and process the underlying vehicle data.