Mercedes-Benz

This page provides specific information about the Astara Connect system's supported Mercedes-Benz and Smart vehicles.

Connectivity

Astara Connect provides a direct connectivity solution for Mercedes-Benz fleet vehicles and retrieves dynamic vehicle data.

Markets

In the following countries, we can retrieve vehicle data from the vehicles: Austria, Belgium, Bulgaria, Croatia, Cyprus, Czech Republic, Denmark, Estonia, Finland, France, Germany, Greece, Hungary, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway, Poland, Portugal, Romania, Slovakia, Slovenia, Spain, Sweden, and Switzerland.

Packages and services

• Mercedes-Benz Basic: is the essential element for enabling the connection with Astara Connect, allowing you to access position data and mileage.
• Mercedes-Benz Extended: Ignition, fuel and consumption data, charging data, vehicle health data, tire data, driving and speed data, door and window data, and driving behavior.

📘

The availability of the products depends on the compatibility of the vehicle and should be checked individually.

Validation process

1. The first step is to launch the register endpoint for registering the tracker into Astara Connect and checking there is a unique tracker_id. This value is the VIN of the Mercedes-Benz vehicle.

You need to send a JSON payload for the request body, similar to this:

{
    "tracker_id": "WF0AXXWPMAJXXXXXX",
    "provider": "mercedes-benz",
    "type": "oem",
    "packages": "mercedesbenzextended",
    "vehicle_type": "car",
    "object_id": {
        "vin": "WF0AXXWPMAJXXXXXX",
        "license_plate": "6666KKK",
        "make": "Mercedes-Benz",
        "model": "eSprinter"
    }
}

2. Mercedes-Benz vehicles need to be validated to complete the connectivity process.
   1. For requesting the validation, the odometer value is required as a checking parameter. If the odometer matching fails, the vehicle changes to the error_access status, so you need to submit the current odometer value of the vehicle again.
      This is an example that accompanies the request body for validation of the Mercedes-Benz vehicles:

{
    "tracker_id": "359632104952350",
    "provider": "mercedes-benz",
    "type": "oem",
    "odo_value": "28319", //integer
}

🚧

Confirm that the odometer data is the current value in the vehicle. Otherwise, the validation will report an error_access.

3. The last step in validating a Mercedes-Benz vehicle is to upload the tracker documentation, the registration certificate, within 7 days of registration for checking the vehicle. Follow the endpoint instructions.

🚧

The vehicle data won't be available during the validation. After the check-in period, the vehicle will be disconnected from the platform.

Connectivity states

These are the connectivity states for MB vehicles:

pending: default state once the register endpoint is completed.

wrong_tracker_id: wrong VIN ID. Check the VIN and modify it if needed.

pending_for_data: waiting for the first coordinates from the provider.

error_data: no data is received, or telemetry data is incorrect. It may be due to a problem with the vehicle's emitting device, so please contact the data provider.

error_access: The odometer reading failed based on the provider. Enter the odometer value and validate the vehicle.

error_time_out : Validation is overdue. The vehicle has been deactivated from the data provider system, so resending the data for validation is necessary.

The validation process will be finished once the first coordinates are received, and the vehicle will change to connected.

Tips

• During the registration and validation process, the process may report a validation error if the vehicle is a few kilometers away and is parked in an indoor parking lot. Move the vehicle outdoors and re-launch the registration process with the correct data.

The Mercedes-Benz registration process is fully available on the Platform.

You can know more about the Connectivity states