EEBUS connector and EEBUS devices
Switch on EEBUS, pair the controller with EEBUS devices and the grid operator's control box, and add EEBUS devices.
→ Overview
EEBUS is a standard protocol for energy devices on the local network. With the EEBUS connector the controller can:
- read and control EEBUS EV chargers, heat pumps and energy meters;
- receive power limits from the grid operator's control box (an energy guard, for example for §14a EnWG in Germany) and enforce them on the site.
The page has three cards: EEBUS connector (switch, state and the controller's own SKI), Pairing (the controller's pairing code) and Discovered devices (EEBUS devices found on the network, with buttons to pair and add them). The Add EEBUS device button at the end of the device list in the left menu opens the same page.
EEBUS devices only talk to devices they trust. Each device is identified by its SKI (subject key identifier), a fingerprint of its certificate. Pairing tells the controller to trust a device's SKI; the other device must trust the controller's SKI as well, which it does by pairing on its side, by scanning the controller's pairing code or by accepting the controller's request.
1 Add an EEBUS device
The screenshot shows the connector switched off, so there is no SKI, no pairing code and no discovery. When the connector is Active and Running, the SKI field shows the controller's SKI, the Pairing card shows a QR code and Discovered devices lists the EEBUS devices found.
If the device does not report its functions within 40 seconds, the add stops with a message, but the pairing is kept. Wait a moment, refresh Discovered devices and click Add again. A device that reports no function the controller supports is unpaired again and not added.
2 Parameters
EEBUS connector
| Parameter | What it does | Unit / default |
|---|---|---|
| Active / Inactive | Starts or stops the controller's EEBUS service. Saved at once when you switch it. While the service is starting or stopping, the card shows Applies in the background - refresh to check the state. | default Inactive |
| Service state | Running = the EEBUS service is up; Stopped = it is not. Read-only. | — |
| SKI | The controller's own EEBUS identifier. Shows - while the service has not started. Read-only. |
text |
| Copy button (SKI) | Copies the SKI to the clipboard, for example to enter it in a device or give it to the grid operator. | — |
| Refresh icon | Reads the state again; with the service running, it also refreshes Discovered devices. | — |
Inactive stops all EEBUS communication: EEBUS devices are no longer read or controlled, and a power limit received from the grid operator is lifted — the site returns to its own agreed limits. On a site where the grid operator controls the site over EEBUS, keep the connector Active.
Pairing
| Parameter | What it does | Unit / default |
|---|---|---|
| QR code (SHIP pairing code) | The controller's pairing code. A device or control box that supports pairing by code scans it (or you enter it in its app) and then trusts the controller. Shown only while the service is running. | — |
| Download | Saves the pairing code as an image file, for example to send it to the grid operator. | — |
| Status text | Enable the connector to get a pairing code. = the connector is off. Pairing code is not available yet. = the service is running but has no code yet; refresh after a moment. | — |
A device that pairs using the code becomes trusted by the controller automatically, without any click on this page. Give the code only to the grid operator or to the installer of the device that should control or be controlled by this site.
Discovered devices
| Parameter | What it does | Unit / default |
|---|---|---|
| Name | Brand and model of the EEBUS device, with its SKI below. | — |
| Type | The controller device type it would be added as, for example EEBUS EV Charger. | — |
| Open | Shown for a device that is already added. Opens its device page. | — |
| Remove | Shown for a device that is already added. After the confirmation Are you sure you want to remove this device and unpair the peer?, deletes the controller device and unpairs it. | — |
| Accept | Shown when the device asks to pair with the controller. Trusts it and completes the pairing. | — |
| Deny | Shown with Accept. Rejects the pairing request. | — |
| Add / Pair & add | Pairs with the device (if needed) and adds it. Pair & add appears when the type is only a guess from the device's network announcement; the controller confirms it after pairing. | — |
| Pair | Shown for a device that is not trusted and cannot be added as a device. Only trusts it. | — |
| Unpair | Shown for a trusted device. After the confirmation Are you sure you want to unpair this device?, removes the trust. Refused while a controller device still uses it — use Remove instead. | — |
| Refresh icon | Searches the network list again. | — |
3 Device types
| What the device announces | Added as | What the controller does with it |
|---|---|---|
| EV charging | EEBUS EV Charger | Reads and controls the charger like any other charger. |
| Heat pump control | EEBUS heat pump | Reads and controls the heat pump. |
| Grid or consumption metering | EEBUS energy meter | Reads the meter values. |
| Limitation of power consumption or production (grid operator) | Energy guard | Receives the grid operator's limits and enforces them. Shows the received limits. |
One EEBUS device can be added in more than one role — for example a grid connection box that both measures and limits becomes an energy meter and an energy guard. Each added device counts towards the device limit of the controller license.
4 Power limits from the grid operator
When an energy guard sends a consumption or production limit, the controller:
- applies it as a ceiling on the site's grid import or export, on top of all other strategy settings;
- shows it in the strategy's Default mode import or export limit while it is active;
- removes it again and restores the site's own limits when the limit expires, is withdrawn, or the energy guard goes away.
If the energy guard stops sending its heartbeat while it controls the site, the controller falls back to the failsafe limit — by default a consumption limit of 4.2 kW — and holds it for at least 2 hours after communication returns. EV chargers and heat pumps may then run at reduced power. Keep the network link to the control box reliable.
5 Checklist
- The connector is Active and Service state shows Running.
- The controller's SKI is entered in, or the pairing code was used by, every device that needs it.
- Each EEBUS device is listed in Discovered devices and shows Open (added).
- The added devices show live values on their device pages.
- On sites with a grid operator control box, an energy guard is added and the connector stays active.