What is Flespi and How Does It Work with Teltonika Devices
What Flespi is, how it fits into a Teltonika telematics stack, and how to test your Flespi integration without waiting for physical hardware.
Flespi is a telematics middleware platform that sits between your GPS devices and your application backend. Instead of building your own TCP server to parse Teltonika's binary protocols, you point your devices at Flespi - it decodes the packets and exposes structured JSON through REST and MQTT APIs.
How It Fits in a Telematics Stack
1. A Teltonika device sends a Codec8 or Codec8 Extended packet over TCP
2. Flespi receives it on a configured channel, decodes the binary payload, and stores parsed records
3. Your backend queries Flespi's REST API or subscribes via MQTT
4. Your application processes the data: map rendering, alerts, reporting
Flespi handles the hardest part of telematics - parsing vendor-specific binary protocols, so you focus on application logic.
Key Concepts
Channels - an inbound endpoint for a specific device protocol. Create one for Teltonika; Flespi gives you a host and port to configure on your devices.
Devices - individual trackers registered within a channel, identified by IMEI.
Streams - forward incoming messages to an external destination (your server, a message queue) for real-time push instead of polling.
Plugins - data transformation, alerting, and routing logic.
Testing Without a Real Device
To validate a Flespi integration, you need a device sending data to your channel before you can verify your backend processes it correctly. Waiting for hardware - or driving a vehicle - just to confirm parsing logic works is impractical.
Telemify solves this. Configure a virtual Teltonika device with your Flespi channel's host and port, assign a route, and start the emulator. Within seconds, your channel receives real codec messages - identical to a physical tracker - and you can validate the full integration in software.
Flespi vs. Direct TCP Server
Use Flespi if you want to skip building your own device server - it handles protocol versioning, IMEI whitelisting, and message storage out of the box. Use a direct TCP server if you need full data pipeline control, strict data residency, or want to avoid a third-party dependency.
Telemify works with both.
Try Telemify for free 👉 https://telemify.io