> For the complete documentation index, see [llms.txt](https://navixy.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://navixy.com/docs/navixy-api/user-api/guides/device-management/send-commands.md).

# Sending commands to a GPS tracker via IP protocol (OTA)

Most modern GPS tracking devices can be reconfigured remotely using IP commands sent over-the-air (OTA). With the Navixy API, you can easily change device configurations or develop applications that allow users to send commands directly from the UI. These commands can also be integrated into automation rules, status changes, or parameter triggers, offering extensive flexibility and customization for managing your telematics solutions.

## Sending a command

To send a command to a device, you only need the following parameters:

* `tracker_id`: The ID of the device to which you want to send the command.
* `command`: The text or hexadecimal representation of the command in a protocol-dependent manner.

#### Example: reconfiguring a Teltonika FMB140 device

Suppose you have a Teltonika FMB140 device with an ID of `231402` on the Navixy platform, and you want to reconfigure its IP address to `52.57.1.136`. According to the protocol, the command should be:

`setparam 2004:52.57.1.136`

### API Request

To send this command, use the API request [`raw_command/send`](/docs/navixy-api/user-api/resources/tracking/tracker.md#post-tracker-raw_command-send):

{% code title="cURL" %}

```shell
curl --request POST \
  --url 'https://api.eu.navixy.com/v2/tracker/raw_command/send' \
  --header 'Content-Type: application/json' \
  --data '{
        "hash": "a6aa75587e5c59c32d347da438505fc3",
        "tracker_id": 231402,
        "command": "setparam 2004:52.57.1.136"
    }'
```

{% endcode %}

Upon successful execution, the platform will confirm that the command has been sent.

This method lets you manage and control your GPS tracking devices via IP, with configuration updates applied in real time.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://navixy.com/docs/navixy-api/user-api/guides/device-management/send-commands.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.