Basic: Registered devices layer extends the functionality of the flespi gateway:
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.
Most popular device types can be configured remotely.
Devices have a telemetry entity that contains the latest values of all parameters received from the device and the time they were updated.
Devices' location can be visualized in TrackIt! — open-source web-application for basic 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.
Advanced: Device configuration is available in various degrees for different device manufacturers:
Full (all possible settings): Queclink, Concox, Topflytech
Advanced (settings for most use cases): Teltonika, GoSafe, ATrack, Navtelecom, Borderless, Maxtrack, Navtelekom, Galileosky, Xexun
Basic (set up target server, restart): Ruptela, Calamp, Systech, Xirgo, SierraWireless, Meitrack, Tekelek, Suntech, ERM, Coban, etc.
All other devices currently can’t be configured from the flespi device configurator tool.