Teltonika (Input, Telematics Device)

• https://wiki.teltonika-gps.com/
• https://kafka.apache.org/documentation/#security_sasl

• Fleet tracking
• Vehicle telematics
• Driver behavior monitoring
• Fuel monitoring
• Route optimization
• Asset tracking

• Native Teltonika AVL packet decoding.
• Real-time GPS and telematics ingestion.
• Automatic parsing of CAN, IO, and diagnostic data.
• Kafka-native routing into Condense topics.
• SASL/PLAIN authentication.
• Fully managed device integration.

1. A Teltonika device sends AVL packets to the Condense endpoint.
2. The connector authenticates the connection.
3. Incoming packets are decoded into structured events.
4. Parsed events are published to the configured Kafka topic.
5. Downstream transforms, applications, dashboards, and connectors consume the events.

​

Title

• Description: Friendly name used to identify the connector.
• Example: Fleet_FMB920_East

​

Device Model

• Description: Select the Teltonika device series or model used in your deployment.
• Examples:
  • FMB920
  • FMB120
  • FMC125
  • FMC650
  • TFT100
• Note: Condense automatically applies the appropriate packet decoder for the selected device.

​

Output Topic

• Description: Kafka topic where decoded telemetry events are published.
• Examples:
  • vehicle.location
  • fleet.telemetry
  • driver.events

​

SASL Username

• Description: Kafka SASL username issued by Condense.
• Location: Condense Admin Console → Security Settings

​

SASL Password

• Description: Password associated with the configured SASL username.
• Recommendation: Store securely and rotate periodically.

{
  "title": "Fleet_FMB920_East",
  "deviceModel": "FMB920",
  "outputTopic": "vehicle.location",
  "saslUsername": "teltonika_user",
  "saslPassword": "********"
}

{
  "deviceId": "356307042441013",
  "timestamp": "2026-07-13T10:15:42Z",
  "latitude": 12.9738,
  "longitude": 77.6113,
  "speed": 42,
  "ignition": true,
  "rpm": 1560,
  "fuelLevel": 48.2
}

​

Device Not Sending Data

• Incorrect server IP or port.
• Incorrect APN configuration.

• Verify the device is configured to connect to the Condense endpoint.
• Confirm network connectivity.

​

Authentication Failed

• Invalid SASL credentials.

• Verify the configured username and password.
• Retrieve updated credentials from the Condense Admin Console.

​

No Messages in Topic

• Incorrect output topic.
• Connector is not running.

• Verify the configured topic exists.
• Check connector status and logs.

​

Parsing Errors

• Unsupported firmware.
• Unsupported device model.

• Verify the selected device model.
• Contact Condense Support for decoder updates if required.

​

Mixed Device Fleets

​

Device-Specific Fields

​

Multiple AVL Records

​

Stream Processing

1. Group devices by fleet, region, or business function using separate Kafka topics.
2. Protect SASL credentials and rotate them regularly.
3. Monitor connector health and parsing metrics using Condense observability.
4. Use downstream transforms to enrich telemetry with business-specific logic.
5. Validate device firmware compatibility before deploying new hardware models.