> 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-operation/energy-usage-view.md).

# Energy Usage view

Review energy consumption and usage patterns across your electrical installation.

### What the Energy Usage view shows

The **Energy Usage** view shows accumulated energy flows for **today** (midnight to now), for the periods when the system was **STARTED**.

**Note: STOPPED periods**

If the Unwaste Robot was **STOPPED** during the day, the Energy Usage view reflects only the periods when it was **STARTED**. Missing time is not recorded.

See **System operation → Starting and stopping the Unwaste Robot**.

It is a "daily picture" of how energy moved through the installation:

* from grid connection into circuits and devices,
* from production sources into circuits,
* into and out of storage,
* and any residual (unmetered) usage.

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

***

### Energy flow diagram

The diagram shows components (nodes) and net energy transfer (lines):

* **Line label (Wh, kWh)** represents how much energy moved between nodes.
* The arrow direction represents **net flow** over the day so far.
* Some nodes can be bidirectional:
  * circuits,
  * storage.

**Colors and direction**

* **Red** indicates net flow in the "normal consumption direction" (typically from root towards loads).
* **Green** indicates net flow in the opposite direction (typically production flowing back into the installation).

**Important: net flow concept** For bidirectional elements, the view shows *net* results, not both directions simultaneously.

Example:

* Storage charged 3 kWh and discharged 1 kWh today.
* The diagram shows 2 kWh net flow in the discharge direction (storage → circuit).

Some elements have fixed direction by design:

* Production sources (e.g., PV inverter) only produce energy → arrow always points away from the inverter.
* Devices only consume energy → arrow always points towards the device.

***

### Unmetered usage

"Unmetered usage" is a calculated residual and appears only under specific conditions:

* It appears when a circuit has its own meter, and
* measured circuit energy is higher than the sum of all measured elements connected to it.

This typically indicates energy usage in that circuit that is not represented by separately metered devices.

**Important limitation**

* If the residual would be negative (for example due to an unmetered production source), it is not shown. Negative "unmetered usage" would be confusing and would suggest that "usage" can produce energy.

***

### Savings panel

The view shows three savings values:

* **Self Use Savings**
* **Storage Savings**
* **Unwasted**

These are always shown, even if currently zero, to keep the view consistent across installations.

For how these savings are computed and what is estimated vs measured, see *Inner workings → Savings calculation*.

***

### Per-device panels

Devices are always listed in the right panel, even if a device used 0 Wh today. This makes it easier to confirm that a device exists in the installation and is part of the model.


---

# 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://docs.unwaste.energy/en/unwaste-robot-operation/energy-usage-view.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.
