Streams push messages from flespi to other platforms (see how to create a stream [VIDEO]). A stream will push only newly received messages from channels or devices subscribed to the stream. If the target platform is unavailable, the stream stores unpushed messages in its internal buffer and pushes them as soon as the target platform is up again. flespi supports several types of streams.
Common protocol streams
HTTP, MQTT, Wialon Retranslator are the protocols with the open specification that can be used in your custom solution:
HTTP — sends POST requests with a list of messages to the specified URI. Max number of messages in one request can be set in the stream configuration. As soon as the server replies with 200 code, the sent messages are removed from the stream buffer.
MQTT — publishes messages to the MQTT connection (credentials specified in stream configuration). The stream uses QoS=1 to ensure that the message is removed from the stream buffer as soon as ACK from the broker is received.
Wialon Retranslator — sends telemetry collected from several sources (has open specification). This protocol is widely accepted by various telematics platforms.
Flespi gateway — sends data between different flespi accounts via HTTPS.
Streams to cloud IoT hubs
flespi allows easily sending your data into the major cloud services::
These platforms can accept the special data format implemented in flespi streams. So flespi user simply needs to configure the stream with the appropriate IoT hub credentials.
Streams to fleet management & GPS tracking platforms
Streams to specialized platforms
flespi offers ready-made solutions to push data to such platforms as:
Streams for toll road systems
flespi uses plugins to coerce the incoming messages to the format required by the national toll road systems:
- tollBG — with the help of a special tollbg plugin for each streamed device.