Concepts — basic terminology of telematics hub

Explaining the key elements of the flespi telematics hub and their interaction.

Telematics hub is a set of tools allowing to:

  1. Set up bidirectional connectivity with GPS tracking devices

  2. Receive and store telemetry messages from tracking devices and platforms

  3. Embed telemetry data to Business Applications and ERPs

To work with flespi one must understand the following basic concepts:

  1. The platform is located at and can be accessed in UI mode and via API. UI part of the platform is described in Platform access section. API calls must be authorized with special keys called Tokens

  2. Receiving telemetry messages is one of the main purposes of Telematics Hub. The Messages section contains details on how flespi handles messages, parameter naming rules, ways to consume messages etc.

  3. Channel is an entry point to the gateway. It is the only way to receive data in Telematics Hub. Channels section explains what stands behind the idea of a channel and what types of channels flespi has with all the technical details.

  4. The work with tracking devices is always the most difficult part of creating complex Business Apps. flespi Device is a virtual instance of a real tracker. In Devices section one can find the description of tools to simplify the work with real tracking devices: settings, separate message storage, last device state etc.

See also
Use groups of devices to add more structure to your account and easily assign multiple devices to streams, plugins, and calculators.
The structured collection of main flespi MQTT topics grouped by the entity.