# Uplink Data

This is the data sent from the Device, it differs for different devices, but the format is the same. We are going to look into a few examples to get a feel on how to interpret it.

## Wireless Thermostat example

Let us look at an example uplink that is relatively data sparse. This comes from an MClimate Wireless Thermostat and it is a regular Keep-alive. You can have different types of uplinks (for example requested by a specific Get command), however they are out of the scope of this document.

<figure><img src="/files/LMn2Aj2W0rpl2RbT5s1U" alt=""><figcaption><p>Wireless Thermostat Uplink data</p></figcaption></figure>

* Raw Data - the payload in HEX format, not parsed
* Decoded Data - the decoded Raw Data, parameters in DEC format
* The Date - the data of ingestion of the Data packet
* Time - the exact time the Data packet arrived
* SF - the spreading factor, good for evaluating network coverage
* RSSI - the received signal strenght indicatior (how good the signal of your network is)
* Data selector - choose a single day period or a span of multiple days to display data for

### Raw Data

&#x20;This format should be identical to the data in your LNS's Application server (if you look at your TTN console live device data you will see the same data). You can find a detailed explanation for this and other device Keep-alives in the [MClimate Documentation repository](https://docs.mclimate.eu/mclimate-lorawan-devices/devices/mclimate-wireless-thermostat/wireless-thermostat-device-communication-protocol/keep-alive). It gives good insights into device operation and helps if you want to do some custom post-processing and analysis.

### Decoded data

The parameters are the as in the Monitor section. The benefit here is the fact that you can easily navigate to a specific Data packet and observe what the values of the parameters were at that point. This can give insights on the state of your system especially if you observe irregularities.

## Vicki Automatic control example

The Vicki is a more complex device that also has mechanical, moving parts, thus compared to a Wireless Thermostat, it does generate a Data packet that carries more data. Thus, the Decoded Data section is larger and has more parameter values. We are not going to go into detail here (there is a separate section that examines every Device in detail). The point we want to make is that Device data differs, some parameters are common (like Battery Voltage) and some specific (like Motor Position) and they are not all in the Monitor section. The Uplink data log is a tool that gives deeper insights into device behavior.

<figure><img src="/files/zL3FEDraJRxRmWECMTLr" alt=""><figcaption><p>Vicki example data - Automatic control</p></figcaption></figure>

## Vicki Automatic control with ext. temp

Lets look at another example, same device, but a different scenario.

This Vicki is operating in Automatic control mode with external temperature measurement and external temperature control. While very similar to the previous case there are some differences:

* The temperature measurement does not use the Vicki internal sensor, but an outside source (a Wireless Thermostat in this scenario).
* The target temperature is controlled by a separate device (same Wireless Thermostat).

These differences are reflected in 3 ways.

1. At the top, below the Device ID in the two colored boxes. The purple one denotes External Target Temperature control, the blue External Temperature measurement. The device that is performing the control/measurement is in the boxes for your reference.
2. The Raw Data payload signifies that there is external temperature measurement (4401071802 in HEX). It is followed by the regular keep-alive payload data, staring with 81.
3. The Decoded Data has an additional field - Ext Sensor Temperature.

<figure><img src="/files/GdU4PkJLGV13xeRZEhwT" alt=""><figcaption><p>Vicki example data - Automatic control with ext. temp.</p></figcaption></figure>


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.mclimate.eu/mclimate-enterprise/configuration-and-management/devices/uplink-data.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.