Automatically translate this page?

Channel — entry point to the gateway

A protocol-specific pipeline for incoming messages from tracking devices.

A channel is an entry point for messages from tracking devices or other platforms. A channel operates via a single protocol which means that one channel can receive messages from tracking devices of one manufacturer. Channel has a unique dedicated host:port to point your tracking devices to. 

Channel handles connections from tracking devices, parses the incoming data, and stores parsed messages in the internal buffer (100 MB for the free account, 1 GB for the commercial account) for 30 days. It's important to promptly take parsed messages away from the channel buffer and clear it regularly to avoid channel blocking due to buffer overflow. This article explains how to get messages from flespi.

As the channel is responsible for connections to devices, you can manage them via API. You can manually close each connection with DELETE /channels/connections request or send a custom configurational command to a certain device.

Note: you may want to create flespi devices on top of channels to get additional possibilities such as telemetry, remote configuration, dedicated long-term storage, plugins, and more.

Channels can accept data from some custom solutions. Customizable functionality is covered by special protocols:

  • MQTT channel — subscribes for the specified topic of any MQTT 3.1.1 or 5.0 compliant broker and accepts plain JSON-formatted messages.

  • HTTP channel — accepts HTTP POST request with messages as a request’s data parameter.

  • Wialon IPS, Wialon Combine — open protocols specifications (text and binary). May be used by device manufacturers or applications that must reduce traffic usage.

  • Wiatag — accepts data from Wiatag mobile application. Can be used for debugging, prototyping or small projects.

  • Telegram — pulls messages received by Telegram bot.

  • Proxy — can be used to split TCP traffic from one device to several platforms and to see HEX data from connections.

There are several types of devices that can work with one pre-configured platform and cannot be re-configured. These platforms provide API (HTTP, XML, SOAP, etc.) to integrate data from these devices to other platforms. flespi supports receiving messages from such platforms as fleetboard, scania-fms, etc. Wialon retranslator protocol is supported by many telematics platforms and can be used for cross-platform integrations too.

To analyze raw traffic in any channel, use the Traffic Viewer tool.

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


See also
Obtain telematics data from Ruptela devices via API in 5 easy steps.
Explaining the different methods to change the device behavior in Flespi.