> For the complete documentation index, see [llms.txt](https://docs.unwaste.energy/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.unwaste.energy/en/unwaste-robot-configuration/optional-monitoring/monitoring-alerts.md).

# Monitoring alerts

Configure alerts for monitored readings and installation conditions.

## Monitoring alerts

## What Are Monitoring Alerts

**Monitoring alerts** let you define conditions that generate user-visible alerts when a reading crosses a threshold.

Alerts can be configured on:

* main reading blocks (Energy Import, Energy Production, Energy Consumed, and similar),
* optional monitoring blocks (Voltage, Current, Power Flow, and similar),
* each entry in [Additional readings](https://docs.unwaste.energy/en/unwaste-robot-configuration/optional-monitoring/additional-readings.md).

Alerts are for **monitoring and notification**. They do not change how the Unwaste Robot controls devices or storage.

***

## Configuring an Alert

Open **Monitoring alerts** on the reading block you want to watch. For each alert, configure:

* **Field** — which sensor or value to monitor (or **Any field** to watch all fields in that block)
* **Condition** — for example greater than, less than, or equal to
* **Threshold** — the limit value and unit
* **Message** — text shown when the alert triggers
* **Window size** — how many recent samples are considered
* **Required count** — how many samples in the window must match the condition before the alert fires

You can add multiple alerts on the same reading block.

***

## Viewing Alerts

Configured alerts appear in two places:

* **Design mode** — on the connection tile, use **MONITORING ALERTS** to see a list of all alerts defined for the installation (Element, Reading, Link to details).
* **Dashboard** (operational mode) — **Monitoring Alerts** section shows alerts that are currently active.

System alerts (for example missing dynamic prices) are shown separately from monitoring alerts configured by the user.

***

## Examples

* **Freeze alert** — Temperature less than 5 °C with message "Freeze alert!"
* **Low voltage** — Voltage L1 less than 207 V with message "Voltage too low!"
* **High voltage** — Voltage L1 greater than 253 V with message "Voltage too high!"

***

## Screenshot (alert form)

![](https://1824863031-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWf3M0a04WuhvfEbAgXFl%2Fuploads%2Fgit-blob-ca9f5e6dd33eb86fb13d6558fd452a3621653824%2F2026-07-10_Configuration_optional_monitoring_adding_alert.png?alt=media)

***

## Screenshot (voltage alerts)

![](https://1824863031-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWf3M0a04WuhvfEbAgXFl%2Fuploads%2Fgit-blob-30fc878ce72ac9d6a450b2585d91268e3c334d8e%2F2026-07-10_Configuration_optional_monitoring_adding_alert2.png?alt=media)

***

## Screenshot (alert list in Design mode)

![](https://1824863031-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWf3M0a04WuhvfEbAgXFl%2Fuploads%2Fgit-blob-77894b34c90055b733b00d26396d0a1dd5ad2780%2F2026-07-10_Design_defined_alerts_list.png?alt=media)


---

# 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://docs.unwaste.energy/en/unwaste-robot-configuration/optional-monitoring/monitoring-alerts.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.
