> 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/profiles-schedules-and-overrides/determining-what-controls-a-device.md).

# Determining what controls a device

Learn how price rules, schedules, and overrides determine device control.

## Determining what controls a device

## Why it is needed

Sometimes it might be needed to determine what element is now in force (that is, if the mode is determined by schedules or overrides or by default mechanism.

That's why we show this information directly in dashboard, because it could be useful for "debugging" your installation, where this rule comes from.

It is only a way to see this information, you cannot change it here.

## Devices

In dashboard, on the graph, each device is labeled with two important pieces of information:

* what mode it operates on
* what is the source of this mode

Mode, as usual, takes one of these values:

* Disabled
* Unmanaged
* Off
* Eco
* Comfort
* Surplus
* Boost

Mode source can take one of these values:

* **Tariff** — the mode was determined from electricity prices (default price-based control). When the active mode is Boost, price-based control took precedence over Surplus even if export conditions were also met.
* **Surplus** — Surplus mode was applied because [Surplus mode](/en/unwaste-robot-configuration/connection.md#surplus-mode) is enabled, export/import conditions were met, and the price-based mode was not Boost
* **Schedule** — a schedule determined this mode
* **Override** — an override forced this mode

Unmanaged indicates the device is not under tariff, schedule, or override control.

Mode source is not shown for Disabled or Unmanaged modes.

Surplus is not available in schedules or overrides — it applies only through the default control mechanism when Surplus mode is configured on the connection.

### Examples for devices

It can look like in these examples of the same device:

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

## Storages

Storages use a different control model than devices, so they do not have a mode source parameter — they show only their current mode, and it is one of valid storage operating modes:

* Disabled
* Unmanaged
* Default
* Force charge
* Force discharge
* Lock discharge
* Lock both


---

# 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-configuration/profiles-schedules-and-overrides/determining-what-controls-a-device.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.