command-not-supported⚓︎

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/command-not-supported",
    "type_documentation": "https://developers.invers.com/problems/vehicle/command-not-supported",
    "title": "The command is not supported by the vehicle.",
    "status": 409,
    "detail": "…",
    "flow_id": "5e77e3e3-48ab-4955-8ab3-1c62339096ab"
}

Meaning⚓︎

This problem type occurs when the vehicle does not support the requested command.

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 command ‘lock central lock’ is not supported by the vehicle ‘JQ7RP’.

You are trying to send a ‘lock central lock’ command to a vehicle which does not support this command. This is expected for all vehicles that do not have a central lock, e.g. mopeds or kickscooters.

Possible solutions:

Check the vehicle’s capabilities and send a command that is supported by the vehicle.