> For the complete documentation index, see [llms.txt](https://docs.voltmasters.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.voltmasters.io/external-signal/external-signal.md).

# Overview

Some projects are operated, fully or partly, by an **external energy partner**, such as an aggregator, supplier, or flexibility service provider. Instead of the EMS deciding how to dispatch the battery and other assets on its own, the partner sends an **external steering signal** (setpoints or a dispatch schedule) to the controller, which then executes it on the connected assets within the configured limits and safety constraints.

This is typically used for services such as imbalance settlement, flexibility (e.g. FCR / aFRR), or supplier-optimized energy trading, where the external party is responsible for the market position and the EMS carries out the resulting dispatch.

### How it works

1. The controller establishes a **secure connection** to the partner's platform, either an **MQTT** connection (certificate-based) or a **REST API** connection (API key), depending on the partner.
2. The partner sends **setpoints / dispatch signals** to the controller.
3. The controller applies these to the connected assets, respecting the project's limits and safety constraints.

The partner is enabled per project in the project's **energy trading settings**, using the connection credentials supplied by the partner.

### Supported partners

| Partner                                                      | Website                                                   | Batteries |  PV | Imbalance market | FCR |
| ------------------------------------------------------------ | --------------------------------------------------------- | :-------: | :-: | :--------------: | :-: |
| [**BEE**](/external-signal/external-signal/bee.md)           | [bee.eu](https://www.bee.eu) (via the Companion platform) |     ✓     |  ✓  |         ✓        |     |
| [**Centrica**](/external-signal/external-signal/centrica.md) | [centricaenergy.com](https://www.centricaenergy.com)      |     ✓     |     |                  |  ✓  |
| [**Elion**](/external-signal/external-signal/elion.md)       | [klant.elindus.be](https://klant.elindus.be/)             |     ✓     |  ✓  |         ✓        |     |
| [**Trevion**](/external-signal/external-signal/trevion.md)   | [trevion.be](https://www.trevion.be)                      |     ✓     |  ✓  |         ✓        |     |
| [**Yuso**](/external-signal/external-signal/yuso.md)         | [yuso.com](https://www.yuso.com)                          |     ✓     |  ✓  |         ✓        |     |

{% hint style="info" %}
A ✓ indicates the steering each partner supports through the EMS.
{% endhint %}

To connect a specific partner, see its detail page for the connection method and the credentials it requires: [BEE](/external-signal/external-signal/bee.md), [Centrica](/external-signal/external-signal/centrica.md), [Elion](/external-signal/external-signal/elion.md), [Trevion](/external-signal/external-signal/trevion.md), [Yuso](/external-signal/external-signal/yuso.md).


---

# 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.voltmasters.io/external-signal/external-signal.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.