> 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/qna/using-navixy/my-device-is-configured-to-send-sensor-data-but-it-doesnt-display.md).

# My device is configured to send sensor data, but it doesn't display

Create a measurement sensor in Devices and Settings to map the incoming sensor parameter to a named field and enable display in the platform

## Question

The device is sending data to the platform, but how do I get it to display on the platform?

## Answer

If your device is showing data within the Air Console, meaning the device is sending data to the platform, then the most likely case is that the device needs a sensor built on the platform. When a device sends data to the platform, the platform needs to know how to associate it with the device. For example, if you are solving a math problem, remember to describe the units, otherwise no one will know what’s being described.

To create a sensor, we recommend reviewing our measurement sensor guide for guidance.

## Links

* [Air Console](/docs/admin/devices/air-console.md)
* [Measurement sensor](/docs/user/guide/devices-and-settings/vehicle-sensors/measurement-sensors.md)


---

# 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/qna/using-navixy/my-device-is-configured-to-send-sensor-data-but-it-doesnt-display.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.