> 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/user/guide/devices-and-settings/device-specific-controls/other.md).

# Other controls

Other device-side blocks in Navixy: LED display, SMS channel usage, virtual ignition, and tracks upload. Availability depends on the device model.

These blocks cover smaller device-side options that appear on specific models.

<table data-view="cards"><thead><tr><th>Block</th><th>Purpose</th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><h4>LED display</h4></td><td>Keep the status LED on or switch it off after a timeout.</td><td><a href="/docs/user/guide/devices-and-settings/device-specific-controls/other/led-display.md">LED display</a></td></tr><tr><td><h4>SMS channel usage</h4></td><td>Control how the device uses its SMS channel.</td><td><a href="/docs/user/guide/devices-and-settings/device-specific-controls/other/sms-channel-usage.md">SMS channel usage</a></td></tr><tr><td><h4>Virtual ignition</h4></td><td>Derive ignition from on-board voltage or motion.</td><td><a href="/docs/user/guide/devices-and-settings/device-specific-controls/other/virtual-ignition.md">Virtual ignition</a></td></tr><tr><td><h4>Tracks upload</h4></td><td>Upload recorded track files from the device.</td><td><a href="/docs/user/guide/devices-and-settings/device-specific-controls/other/tracks-upload.md">Tracks upload</a></td></tr></tbody></table>


---

# 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/user/guide/devices-and-settings/device-specific-controls/other.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.