> ## Documentation Index
> Fetch the complete documentation index at: https://docs.condense.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Teltonika (Input, Telematics Device)

**Connector Type:** Input Connector

**Description**

Ingests real-time telematics data from Teltonika devices into Condense.

**Brief Description**

The Teltonika Input Connector enables Condense to ingest real-time telemetry from Teltonika GPS trackers and telematics devices into Kafka-native topics. It provides built-in protocol decoding for supported Teltonika devices, automatically converting AVL packets into structured JSON events that are immediately available for stream processing, analytics, alerting, and downstream applications.

The connector is fully managed by Condense and eliminates the need for users to implement device protocol parsing, packet decoding, or infrastructure management.

**Links to Relevant Documents**

* [https://wiki.teltonika-gps.com/](https://wiki.teltonika-gps.com/)
* [https://kafka.apache.org/documentation/#security\_sasl](https://kafka.apache.org/documentation/#security_sasl)

**Connector Overview**

The Teltonika Input Connector provides a production-ready integration between Teltonika GPS devices and Condense. It accepts incoming AVL packets over supported protocols, decodes GPS, CAN, IO, and diagnostic information, authenticates using Kafka SASL credentials, and publishes structured events into Condense Kafka topics.

Typical use cases include:

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

**Supported Devices**

| **Series** | **Supported Models**                                                                                                                                                                   |
| :--------- | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| FMB        | FMB000, FMB001, FMB010, FMB020, FMB110, FMB120, FMB122, FMB125, FMB130, FMB140, FMB150, FMB202, FMB204, FMB209, FMB225, FMB230, FMB240, FMB641, FMB900, FMB910, FMB920, FMB930, FMB965 |
| FMC        | FMC003, FMC125, FMC130, FMC150, FMC225, FMC230, FMC234, FMC650, FMC800, FMC880, FMC920, FMC13A                                                                                         |
| TFT        | TFT100                                                                                                                                                                                 |

Support for additional Teltonika devices may be available in future releases.

**Core Functionality**

* 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.

**How It Works in Condense**

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.

**Configuration**

| **Category** | **Field Name** | **Description**                  | **Required** |
| :----------- | :------------- | :------------------------------- | :----------: |
| General      | Title          | Unique connector name            |      Yes     |
| Device       | Device Model   | Teltonika device series or model |      Yes     |
| Messaging    | Output Topic   | Kafka topic for decoded events   |      Yes     |
| Security     | SASL Username  | Kafka authentication username    |      Yes     |
| Security     | SASL Password  | Kafka authentication password    |      No      |

**Field-by-Field Explanation**

### 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.

**Sample Configuration Example**

```json theme={null}
{
  "title": "Fleet_FMB920_East",
  "deviceModel": "FMB920",
  "outputTopic": "vehicle.location",
  "saslUsername": "teltonika_user",
  "saslPassword": "********"
}
```

**Example Event**

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

**Troubleshooting and Common Issues**

### Device Not Sending Data

**Possible Causes**

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

**Resolution**

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

***

### Authentication Failed

**Possible Causes**

* Invalid SASL credentials.

**Resolution**

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

***

### No Messages in Topic

**Possible Causes**

* Incorrect output topic.
* Connector is not running.

**Resolution**

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

***

### Parsing Errors

**Possible Causes**

* Unsupported firmware.
* Unsupported device model.

**Resolution**

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

**Advanced Considerations**

### Mixed Device Fleets

Multiple Teltonika device models can publish into the same Kafka topic when a common event schema is used. For fleets with significantly different telemetry structures, separate topics are recommended.

***

### Device-Specific Fields

Certain models expose additional CAN bus or diagnostic fields. These fields are automatically included in events when supported by the device.

***

### Multiple AVL Records

Teltonika devices may send multiple AVL records in a single transmission. The connector automatically separates them into individual Kafka events.

***

### Stream Processing

The decoded output integrates directly with Condense transforms, alerts, dashboards, and downstream connectors.

**Best Practices**

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.