no-connection⚓︎

Problem

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/vehicle/no-connection",
    "type_documentation": "https://developers.invers.com/problems/vehicle/no-connection",
    "title": "No connection to vehicle",
    "status": 504,
    "detail": "…",
    "flow_id": "5e77e3e3-48ab-4955-8ab3-1c62339096ab"
}

Meaning⚓︎

This problem type occurs when: - The vehicle did not establish a connection with the INVERS OneAPI - The vehicle did not answer in time

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 vehicle ‘JQ7RP’ did not establish a connection.

You are trying to send a command to a vehicle that is not connected to the INVERS OneAPI.

Possible solutions:

Ensure that the vehicle is correctly configured
Ensure that the vehicle has a good network signal

The vehicle ‘JQ7RP’ didn’t answer in time.

The vehicle did not answer in time.