> 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/vehicle-sensors/aggregation-sensors.md).

# Aggregation sensors

The **Aggregation sensor** block in Navixy allows you to combine data from multiple sensors and process it using an aggregation function. This functionality is particularly useful in scenarios where multiple sensors are used to monitor similar parameters, such as fuel levels in a vehicle.

![](/files/SkgRMdL7EM8HDh1xibI7)

## Aggregation function options

The two available aggregation functions are **Average (AVG)** and **Sum (SUM)**.

* **AVG (Average)**: This function calculates the average value of the selected sensors. It is useful when you want to smooth out the readings from multiple sensors, providing a more stable and representative value.
* **SUM (Sum)**: This function adds up the values of the selected sensors. It is ideal when the total value of a parameter needs to be monitored, such as the combined fuel level from two tanks.

## Practical examples: multiple fuel sensors in a vehicle

1. **Single tank with two fuel level Sensors**:

* **Scenario**: You have a large fuel tank with two sensors positioned at different points inside the tank.
* **Goal**: To get a more accurate reading of the overall fuel level by averaging the readings from both sensors.
* **Configuration**:
  * **Aggregation function**: Select **AVG**.
  * **Sensors for aggregation**: Choose the two fuel level sensors.
  * **Result**: Navixy displays the average fuel level, providing a balanced reading that compensates for any discrepancies between the two sensors.

2. **Two tanks with separate sensors**:

* **Scenario**: You have two fuel tanks that are separate, and each tank has its own fuel level sensor.
* **Goal**: To monitor the total fuel available across both tanks.
* **Configuration**:
  * **Aggregation function**: Select **SUM**.
  * **Sensors for aggregation**: Choose the sensors from both tanks.
  * **Result**: Navixy sums the fuel levels from both tanks, giving you the total fuel available.

## Setting up the aggregation sensor

1. **Label**: Enter a name for your aggregation sensor that clearly identifies its purpose.
2. **Aggregation Function**: Select either **AVG** (for averaging) or **SUM** (for summing) depending on your needs.
3. **Sensor type**: Choose the type of sensor (e.g., fuel level).
4. **Accuracy**: Set the acceptable margin of error. For example, if the accuracy is set to 5% and the maximum value is 100 liters, changes of 5 liters or less are ignored.
5. **Max value**: Set the upper limit for the aggregated value. This prevents the aggregated reading from exceeding a certain threshold.
6. **Units**: Set the unit of measurement (e.g., liters).
7. **Sensors for Aggregation**: Select the individual sensors whose data you want to aggregate.
8. **Save**: After configuring the sensor, click **Save** to apply the settings.

## Availability

Available when the device has at least two compatible measurement sensors to combine.

## Limitations

* Aggregation combines **existing measurement sensors**: Create the source sensors first.
* Choose the sensor type and units to match the sources you are combining.


---

# 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 dynamically by asking a question.

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

```
GET https://navixy.com/docs/user/guide/devices-and-settings/vehicle-sensors/aggregation-sensors.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.