/problems/incompatible-telematics-unit-model

This is a description of a specific error response that you can receive when using the INVERS OneAPI via REST.¹

Check out our API Basics to learn more about the basic structure of all error responses and to find out how you should handle them.

{
    "type": "/problems/incompatible-telematics-unit-model",
    "type_documentation": "https://developers.invers.com/problems/incompatible-telematics-unit-model",
    "title": "The desired configuration is not available for the CloudBoxx 3G.",
    "status": 409,
    "detail": "…",
    "flow_id": "5e77e3e3-48ab-4955-8ab3-1c62339096ab"
}

Meaning

This problem type occurs when the telematics unit model does not support one or more of the desired configuration values.

Details

• Use the error response’s type property to handle specific errors and exception handling within your application. It’s comparable to an error code.
• The detail property contains additional, more human-readable information about the problem or error. This is explanatory text and you should not have any exception handling and error handling code depend on it, as it may change.

Detail examples

The following examples are typical texts which you might receive in the error response’s detail property. Note that it is not a complete list of all possible cases. Therefore expect to receive error responses with a detail property value not listed below.

Example problem details

The feature is only available for CloudBoxx 4G or 1020.

You are using a telematics unit model that is incompatible with the feature. The feature is only available for specific models, i.e. 4G or 1020 in this example.

Possible solutions:

• Use additional information from the detail to replace incompatible configuration values in your request.

---

1. The flow_id is specific to each API call, so it will be different in your case. However, type, title and status will match your actual error response if you receive the error described on this page. ↩