Device — a virtual instance of a real tracker

More control over each individual GPS tracker, dedicated storage, telemetry, remote configuration.

Important: You must have at least one channel to make your flespi devices work.

Devices extend the functionality of channels in the following ways:

  • Each registered device has its own messages buffer (100 MB for the free account, 10 GB for the commercial account) with up to 10 years storage period.

  • You can perform calculations on device messages — extract trips/stops, detect geofence ins/outs, and a lot more.

  • You can apply plugins to device messages to modify their content.

  • You can configure your telematics devices remotely via API or a Setbox tool.

  • Devices feature telemetry that contains the latest values of all parameters received from the device and the time they were updated.

  • Device location can be visualized in TrackIt! — open-source web application for basic GPS tracking.

  • You can also export trips for your device in KML, GPX, or GeoJSON format.

In terms of IoT, a registered device is a kind of thing twin in AWS IoT hub or device shadow in MS Azure IoT. Even if your physical device is offline, you can get its last telemetry and plan to send a command as soon as the device connects to flespi. Moreover, the device can be configured via SMS which allows you to force the device to do something.

To forward the parsed data from your devices, explore our streaming options.

See also
An easy way to generate messages for a flespi device to test and debug plugins, streams, calculators, etc.
The structured collection of main flespi MQTT topics grouped by the entity.