# Start here


import { ChapterLanding } from '@/components/ChapterLanding';

<ChapterLanding
  chapter="api"
  eyebrow="Build with Eniris"
  title="Eniris API"
  description="Build secure integrations on top of the data used by Eniris applications. Discover accessible companies and devices, manage metadata relationships, and query time-series telemetry from connected energy assets."
  highlightOne="REST & JSON"
  highlightTwo="JWT authentication"
  highlightThree="Telemetry"
/>

> [!IMPORTANT] Start with authentication
> Obtain an access token through the [Eniris Authentication API](https://authentication.eniris.be/docs) before trying a data request. In the interactive API reference, click `Authorize` and enter that access token. Signing in to the documentation website does not authorize API requests.

## Before you start

> **Use your existing account.** Sign in to the Authentication API with the same email address and password you use for SmartgridX or the Eniris app. You do not need separate API credentials.

Every API request requires a JWT access token. Obtain a token through the [Eniris Authentication API](https://authentication.eniris.be/docs) using those credentials and send it with each request:

```http
Authorization: Bearer <access-token>
```

The API uses HTTPS and JSON. Eniris also provides client packages for [Python](https://pypi.org/project/eniris/) and npm that implement the authentication flow and simplify communication with the API.

## How the API is organised

- **Users and access:** users receive permissions through roles. Member, manages and monitors relations determine role membership, role hierarchy and access to devices.
- **Devices and companies:** discover the assets and organisations that the authenticated user may access, or create and update them when the token has the required permissions.
- **Telemetry:** query time-series measurements for one or more devices, fields and retention policies.
- **Licences:** claim, activate and inspect controller licences where applicable.

## Typical integration flow

1. Sign in to the Authentication API with your SmartgridX or Eniris app credentials and obtain an access token.
2. Retrieve the user's companies and roles, then query the devices available through those roles.
3. Select the required measurement fields and retention policy from the reference below.
4. Send a telemetry query and process the returned time-series data.

For the current request schemas, response models and interactive endpoint explorer, use the [official Eniris API reference](https://api.eniris.be/docs/). Prefer the newer `POST .../query` endpoints where the reference marks an older `GET` endpoint as replaced.

> API access is intended for integrations and data export and may be subject to commercial fees. [Request API access or pricing information](https://eniris.io/api_request/).

## Measurement field reference

The following table lists the available fields for which data can be retrieved via the Eniris Metadata & Telemetry Query API.<br/>
Data for a specific field is only available for the specified measurements and retention policies.

## Power related fields


| Field name | Description | Unit Of Measurement | Measurement | Retention Policy |
| ---------- | ----------- | ------------------- | ----------- | ---------------- |
| actualPowerTot_W | Total active power at the current time. | Watt (W) | <ul><li>submeteringMetrics</li><li>batteryMetrics</li><li>hybridInverterMetrics</li></ul><div className='border-2 rounded-xl px-3 py-2'>⚠️ For the previous measurements:<br/>**Positive values** indicate charging, consumption or import.<br/>**Negative values** indicate discharging or export.</div><ul><li>solarInverterMetrics</li><li>solarInstallationMetrics</li><li>solarOptimizerMetrics</li><li>solarStringMetrics</li></ul><div className='border-2 rounded-xl px-3 py-2'>⚠️ For these measurements the values indicate production.</div><ul><li>gridMetrics</li><li>evChargerMetrics</li><li>heatPumpMetrics</li><li>boilerMetrics</li><li>switchedLoadMetrics</li><li>installationMetrics</li></ul><div className='border-2 rounded-xl px-3 py-2'>⚠️ For these measurements values indicate consumption.</div> | <ul><li>rp_one_s</li><li>rp_one_m</li><li>rp_ten_m</li></ul> | 
| childrenStoragePower_W | Total real-time charging or discharging power of all connected batteries at a particular site. | Watt (W) | submeteringMetrics | <ul><li>rp_one_s</li><li>rp_one_m</li><li>rp_ten_m</li></ul> | 
| childrenProducedPower_W | Total real-time power production of all connected power producing devices at a particular site. | Watt (W) | submeteringMetrics | <ul><li>rp_one_s</li><li>rp_one_m</li><li>rp_ten_m</li></ul> | 
| childrenEVPower_W | Total real-time power consumption of all connected EV chargers at a particular site. | Watt (W) | submeteringMetrics | <ul><li>rp_one_s</li><li>rp_one_m</li><li>rp_ten_m</li></ul> | 
| childrenConsumedPower_W | Total real-time power demand of all connected energy consuming devices at a particular site. | Watt (W) | submeteringMetrics | rp_one_m | 
| childrenOtherPower_W | Total real-time power consumption of devices that aren't EV chargers or heatpumps at a particular site. | Watt (W) | submeteringMetrics | <ul><li>rp_one_s</li><li>rp_one_m</li><li>rp_ten_m</li></ul> | 

## Energy related fields

| Field name | Description | Unit Of Measurement | Measurement | Retention Policy |
| ---------- | ----------- | ------------------- | ----------- | ---------------- |
| importedAbsEnergyTot_Wh | Total imported energy | Watt-hour (Wh) | <ul><li>hybridInverterMetrics</li><li>submeteringMetrics</li></ul> | <ul><li>rp_one_m</li><li>rp_ten_m</li></ul> |
| exportedAbsEnergyTot_Wh | Total exported energy | Watt-hour (Wh) | <ul><li>hybridInverterMetrics</li><li>submeteringMetrics</li></ul> | <ul><li>rp_one_m</li><li>rp_ten_m</li></ul> |
| producedAbsEnergyTot_Wh | Total produced energy | Watt-hour (Wh) | <ul><li>solarInverterMetrics</li><li>solarOptimizerMetrics</li><li>hybridInverterMetrics</li><li>installationMetrics</li><li>solarStringMetrics</li></ul> | <ul><li>rp_one_m</li><li>rp_ten_m</li></ul> |
| consumedAbsEnergyTot_Wh | Total consumed energy | Watt-hour (Wh) | <ul><li>solarInverterMetrics</li><li>evChargerMetrics</li><li>heatPumpMetrics</li><li>switchedLoadMetrics</li><li>hybridInverterMetrics</li></ul> | <ul><li>rp_one_m</li><li>rp_ten_m</li></ul> |
| chargedAbsEnergyTot_Wh | Total charged energy | Watt-hour (Wh) | <ul><li>evChargerMetrics</li><li>hybridInverterMetrics</li><li>batteryMetrics</li></ul> | <ul><li>rp_one_m</li><li>rp_ten_m</li></ul> |
| dischargedAbsEnergyTot_Wh | Total discharged energy | Watt-hour (Wh) | <ul><li>evChargerMetrics</li><li>hybridInverterMetrics</li><li>batteryMetrics</li></ul> | <ul><li>rp_one_m</li><li>rp_ten_m</li></ul> |
| importedEnergyDeltaTot_Wh | Imported energy delta between two points in time | Watt-hour (Wh) | <ul><li>hybridInverterMetrics</li><li>submeteringMetrics</li></ul> | <ul><li>rp_one_m</li><li>rp_ten_m</li></ul> |
| exportedEnergyDeltaTot_Wh | Exported energy delta between two points in time | Watt-hour (Wh) | <ul><li>hybridInverterMetrics</li><li>submeteringMetrics</li></ul> | <ul><li>rp_one_m</li><li>rp_ten_m</li></ul> |
| childrenStorageChargedEnergyDeltaTot_Wh | Total charged energy delta between two points in time of all connected batteries at a particular site. | Watt-hour (Wh) | submeteringMetrics | <ul><li>rp_one_m</li><li>rp_ten_m</li></ul> | 
| childrenStorageDischargedEnergyDeltaTot_Wh | Total discharged energy delta between two points in time of all connected batteries at a particular site. | Watt-hour (Wh) | submeteringMetrics | <ul><li>rp_one_m</li><li>rp_ten_m</li></ul> | 
| producedEnergyDeltaTot_Wh | Total produced energy delta between two points in time | Watt-hour (Wh) | <ul><li>solarInverterMetrics</li><li>solarInstallationMetrics</li><li>solarOptimizerMetrics</li><li>hybridInverterMetrics</li><li>installationMetrics</li><li>solarStringMetrics</li><li>submeteringMetrics (only rp_one_m)</li></ul> | <ul><li>rp_one_m</li><li>rp_ten_m</li></ul> |
| chargedEnergyDeltaTot_Wh | Charged energy delta between two points in time | Watt-hour (Wh) | <ul><li>evChargerMetrics</li><li>hybridInverterMetrics (only rp_one_m)</li><li>batteryMetrics</li></ul> | <ul><li>rp_one_m</li><li>rp_ten_m</li></ul> | 
| dischargedEnergyDeltaTot_Wh | Discharged energy delta between two points in time | Watt-hour (Wh) | <ul><li>evChargerMetrics</li><li>hybridInverterMetrics (only rp_one_m)</li><li>batteryMetrics</li></ul> | <ul><li>rp_one_m</li><li>rp_ten_m</li></ul> |

## Planning related fields

| Field name | Description | Unit Of Measurement | Measurement | Retention Policy |
| ---------- | ----------- | ------------------- | ----------- | ---------------- |
| powerSetpoint_W | Command power setpoint | Watt (W) | planning | <ul><li>rp_one_s</li><li>rp_one_m</li><li>rp_ten_m</li></ul> | 
| policy | Command Policy | - | planning | <ul><li>rp_one_s</li><li>rp_one_m</li><li>rp_ten_m</li></ul> | 
| constraint_ph0_label | Constraint Label | - | planning | <ul><li>rp_one_s</li><li>rp_one_m</li><li>rp_ten_m</li></ul> | 
| reactivePowerSetpoint_VAr | Reactive Power Setpoint | Volt-Ampere reactive (VAr) | planning | <ul><li>rp_one_s</li><li>rp_one_m</li><li>rp_ten_m</li></ul> |

## Other fields

| Field name | Description | Unit Of Measurement | Measurement | Retention Policy |
| ---------- | ----------- | ------------------- | ----------- | ---------------- |
| currentL1_A | Phase 1 (Line 1) current | Ampere (A) | <ul><li>evChargerMetrics</li><li>heatPumpMetrics</li><li>boilerMetrics</li><li>switchedLoadMetrics</li><li>solarInverterMetrics</li><li>solarOptimizerMetrics</li><li>hybridInverterMetrics</li><li>submeteringMetrics</li><li>batteryMetrics</li></ul> | <ul><li>rp_one_s</li><li>rp_one_m</li><li>rp_ten_m</li></ul> |
| currentL2_A | Phase 2 (Line 2) current | Ampere (A) | <ul><li>evChargerMetrics</li><li>heatPumpMetrics</li><li>boilerMetrics</li><li>solarInverterMetrics</li><li>solarOptimizerMetrics</li><li>hybridInverterMetrics</li><li>installationMetrics (only rp_one_m)</li><li>submeteringMetrics</li><li>batteryMetrics</li></ul> | <ul><li>rp_one_s</li><li>rp_one_m</li><li>rp_ten_m</li></ul> |
| currentL3_A | Phase 3 (Line 3) current | Ampere (A) | <ul><li>evChargerMetrics</li><li>heatPumpMetrics</li><li>boilerMetrics</li><li>solarInverterMetrics</li><li>solarOptimizerMetrics</li><li>hybridInverterMetrics</li><li>installationMetrics (only rp_one_m)</li><li>submeteringMetrics</li><li>batteryMetrics</li></ul> | <ul><li>rp_one_s</li><li>rp_one_m</li><li>rp_ten_m</li></ul> |
| currentN_A | Neutral current | Ampere (A) | <ul><li>evChargerMetrics</li><li>hybridInverterMetrics</li><li>submeteringMetrics</li></ul> | rp_one_m |
| voltageL1N_V | Phase 1 to Neutral voltage (Phase Voltage) | Volt (V) | <ul><li>evChargerMetrics</li><li>heatPumpMetrics (only rp_one_m)</li><li>boilerMetrics (only rp_one_m or rp_ten_m)</li><li>switchedLoadMetrics (only rp_one_m or rp_ten_m)</li><li>solarInverterMetrics</li><li>solarOptimizerMetrics (only rp_one_m or rp_ten_m)</li><li>hybridInverterMetrics (only rp_one_m or rp_ten_m)</li><li>submeteringMetrics (only rp_one_m or rp_ten_m)</li><li>batteryMetrics (only rp_one_m or rp_ten_m)</li></ul> | <ul><li>rp_one_s</li><li>rp_one_m</li><li>rp_ten_m</li></ul> | 
| voltageL2N_V | Phase 2 to Neutral voltage (Phase Voltage) | Volt (V) | <ul><li>evChargerMetrics</li><li>boilerMetrics (only rp_one_m or rp_ten_m)</li><li>solarInverterMetrics (only rp_one_m or rp_ten_m)</li><li>solarOptimizerMetrics (only rp_one_m or rp_ten_m)</li><li>hybridInverterMetrics (only rp_one_m or rp_ten_m)</li><li>submeteringMetrics (only rp_one_m or rp_ten_m)</li><li>batteryMetrics (only rp_one_m or rp_ten_m)</li></ul> | <ul><li>rp_one_s</li><li>rp_one_m</li><li>rp_ten_m</li></ul> | 
| voltageL3N_V | Phase 3 to Neutral voltage (Phase Voltage) | Volt (V) | <ul><li>evChargerMetrics</li><li>boilerMetrics (only rp_one_m or rp_ten_m)</li><li>solarInverterMetrics (only rp_one_m or rp_ten_m)</li><li>solarOptimizerMetrics (only rp_one_m or rp_ten_m)</li><li>hybridInverterMetrics (only rp_one_m or rp_ten_m)</li><li>submeteringMetrics (only rp_one_m or rp_ten_m)</li><li>batteryMetrics (only rp_one_m or rp_ten_m)</li></ul> | <ul><li>rp_one_s</li><li>rp_one_m</li><li>rp_ten_m</li></ul> | 
| voltageL1L2_V | Line-to-Line voltage between Phase 1 and Phase 2 | Volt (V) | <ul><li>evChargerMetrics</li><li>solarInverterMetrics</li><li>solarOptimizerMetrics (only rp_one_m)</li><li>hybridInverterMetrics</li><li>submeteringMetrics</li><li>batteryMetrics</li></ul> | <ul><li>rp_one_m</li><li>rp_ten_m</li></ul> | 
| voltageL2L3_V | Line-to-Line voltage between Phase 2 and Phase 3 | Volt (V) | <ul><li>evChargerMetrics</li><li>solarInverterMetrics</li><li>solarOptimizerMetrics (only rp_one_m)</li><li>hybridInverterMetrics</li><li>submeteringMetrics</li><li>batteryMetrics</li></ul> | <ul><li>rp_one_m</li><li>rp_ten_m</li></ul> | 
| voltageL3L1_V | Line-to-Line voltage between Phase 3 and Phase 1 | Volt (V) | <ul><li>evChargerMetrics</li><li>solarInverterMetrics</li><li>solarOptimizerMetrics (only rp_one_m)</li><li>hybridInverterMetrics</li><li>submeteringMetrics</li><li>batteryMetrics</li></ul> | <ul><li>rp_one_m</li><li>rp_ten_m</li></ul> | 
| frequency_Hz | System frequency | Hertz (Hz) | <ul><li>evChargerMetrics</li><li>boilerMetrics</li><li>switchedLoadMetrics</li><li>solarInverterMetrics</li><li>hybridInverterMetrics</li><li>submeteringMetrics</li></ul> | <ul><li>rp_one_s</li><li>rp_one_m</li><li>rp_ten_m</li></ul> |
| powerFactorTot | Total power factor | - | <ul><li>evChargerMetrics</li><li>solarInverterMetrics</li><li>hybridInverterMetrics</li><li>submeteringMetrics</li></ul> | <ul><li>rp_one_m</li><li>rp_ten_m</li></ul> |
| powerFactorL1 | Phase 1 power factor | - | <ul><li>hybridInverterMetrics</li><li>submeteringMetrics</li></ul> | rp_one_m |
| powerFactorL2 | Phase 2 power factor | - | <ul><li>hybridInverterMetrics</li><li>submeteringMetrics</li></ul> | rp_one_m |
| powerFactorL3 | Phase 3 power factor | - | <ul><li>hybridInverterMetrics</li><li>submeteringMetrics</li></ul> | rp_one_m |
| voltageDC_V | DC voltage | Volt (V) | <ul><li>evChargerMetrics</li><li>solarInverterMetrics</li><li>solarOptimizerMetrics</li><li>hybridInverterMetrics</li><li>solarStringMetrics</li><li>batteryMetrics</li></ul> | <ul><li>rp_one_m</li><li>rp_ten_m</li></ul> |
| currentDC_A | DC current | Ampere (A) | <ul><li>evChargerMetrics</li><li>solarInverterMetrics</li><li>solarOptimizerMetrics</li><li>hybridInverterMetrics</li><li>solarStringMetrics</li><li>batteryMetrics</li></ul> | <ul><li>rp_one_m</li><li>rp_ten_m</li></ul> |
| status | Device status (e.g. On, Off, Error) | - | <ul><li>evChargerMetrics</li><li>heatPumpMetrics</li><li>boilerMetrics</li><li>solarInverterMetrics (only rp_one_m)</li><li>hybridInverterMetrics</li><li>installationMetrics (only rp_one_m)</li></ul> | <ul><li>rp_one_s</li><li>rp_one_m</li><li>rp_ten_m</li></ul> |
| operationMode | Device operation mode | - | <ul><li>evChargerMetrics (only rp_one_m and rp_ten_m)</li><li>heatPumpMetrics</li><li>boilerMetrics</li><li>switchedLoadMetrics</li><li>solarInverterMetrics</li><li>solarOptimizerMetrics</li><li>hybridInverterMetrics</li><li>batteryMetrics</li></ul> | <ul><li>rp_one_s</li><li>rp_one_m</li><li>rp_ten_m</li></ul> |
| stateOfCharge_frac | State of Charge (SoC) | fraction (number between 0 and 1) | <ul><li>evChargerMetrics</li><li>hybridInverterMetrics</li><li>batteryMetrics</li></ul> | <ul><li>rp_one_s</li><li>rp_one_m</li><li>rp_ten_m</li></ul> |
| stateOfHealth_frac | State of Health (SoH) | fraction (number between 0 and 1) | batteryMetrics | rp_one_m |
| childrenStorageStateOfCharge_frac | Average State of Charge (SoC) of all connected batteries at a particular site. | fraction (number between 0 and 1) | submeteringMetrics | <ul><li>rp_one_m</li><li>rp_ten_m</li></ul> |
| batteryCurrent_A | Real-time current to/from the battery | Ampere (A) | batteryMetrics | <ul><li>rp_one_m</li><li>rp_ten_m</li></ul> |
| batteryVoltage_V | Real-time voltage of the battery | Volt (V) | batteryMetrics | <ul><li>rp_one_m</li><li>rp_ten_m</li></ul> |
| evRequiringCharge | Indicates whether an EV is connected and requires a charge | True or False | evChargerMetrics | <ul><li>rp_one_s</li><li>rp_one_m</li><li>rp_ten_m</li></ul> |
| setpoint_W | External signal power setpoint | Watt (W) | externalSignalMetrics | <ul><li>rp_one_s</li><li>rp_one_m</li><li>rp_ten_m</li></ul> | 
| strategy | External signal strategy | - | externalSignalMetrics | <ul><li>rp_one_s</li><li>rp_one_m</li><li>rp_ten_m</li></ul> | 
| signalActive | Is an external signal active or not | 0 or 1 | externalSignalMetrics | <ul><li>rp_one_s</li><li>rp_one_m</li><li>rp_ten_m</li></ul> | 
| reacPowerSetpoint_VAr | Reactive power setpoint | Volt-Ampere reactive (VAr) | externalSignalMetrics | <ul><li>rp_one_s</li><li>rp_one_m</li><li>rp_ten_m</li></ul> | 
| importLimit_W | Import power limit command for a particular site.  | Watt (W) | externalSignalMetrics | <ul><li>rp_one_s</li><li>rp_one_m</li><li>rp_ten_m</li></ul> | 
| exportLimit_W | Export power limit command for a particular site.  | Watt (W) | externalSignalMetrics | <ul><li>rp_one_s</li><li>rp_one_m</li><li>rp_ten_m</li></ul> |


# Data access and export


# Downloading data: CSV export and the Eniris API

Data from installations and devices linked to your Eniris account can be retrieved in two ways:

* manually as a CSV file from the portal;
* automatically through the Eniris API.

CSV export is free. The API can also be used free of charge within the limits of the Free API tier.

> [!IMPORTANT]
>   If an installation already has an active SmartgridOne software license for control, asset monitoring for that installation is included. You do not need to purchase a separate Monitoring Residential or Monitoring Commercial license for the same installation.

## Which option should I use?

| Use case                                   | Recommended option | Cost |
| ------------------------------------------ | ------------------ | ---: |
| One-time or occasional data export         | CSV export         | Free |
| Automated reporting or a small integration | API Free           | Free |
| Regular or larger data queries             | API Basic          | Paid |
| High-volume integrations                   | API Premium        | Paid |

## CSV export

Graph data in the SmartgridX portal can be downloaded as a CSV file. No API tier or separate export license is required.

1. Open the required installation or device in the portal.
2. Select the graph and time range you need.
3. Use the graph's CSV download option.
4. Open the downloaded file in Excel, Power BI, or another analysis tool.

You can only export data from installations and devices that your account is authorized to access. The relevant meter or device must also be correctly integrated and sending data to Eniris.

## Do I need a separate monitoring license?

### Installation with SmartgridOne control

An active SmartgridOne software license for control includes asset monitoring for the same installation. No separate monitoring license is required to:

* view the installation's devices and measurements in the portal;
* download graph data as CSV;
* query the available data through the Eniris API.

The API tier determines the available query capacity.

### Monitoring-only installation

A separate monitoring license is intended for an installation that is only monitored and does not have an active SmartgridOne control license. This can apply when Eniris is used solely for energy monitoring, reporting, or collecting meter data, without SmartgridOne controlling the installation.

> [!IMPORTANT] Start with authentication
> Obtain an access token through the [Eniris Authentication API](https://authentication.eniris.be/docs) before trying a data request. In the interactive API reference, click `Authorize` and enter that access token. Signing in to the documentation website does not authorize API requests.

## API access

The Eniris API is intended for automatically retrieving data for applications such as:

* custom dashboards;
* scheduled reports;
* energy management or billing software;
* automated analysis.

## API tiers

| Tier    | Monthly price | Compute-time allowance per minute | Bucket capacity |
| ------- | ------------: | --------------------------------: | --------------: |
| Free    |            €0 |                    100 compute-ms |          100 ms |
| Basic   |          €250 |                  6,000 compute-ms |        6,000 ms |
| Premium |        €1,500 |                 60,000 compute-ms |       60,000 ms |

With optimized queries, the Free tier is suitable for approximately 2,000 data points per minute. Actual usage depends on the number of queries, selected time range, estimated number of data points, and query complexity.

See the [Eniris webshop](https://webshop.eniris.com/) for current prices and limits.

## Using the API efficiently

To stay within the available capacity:

* always specify a clear start and end time;
* request only the fields you need;
* set an appropriate result limit;
* bundle queries where possible—the API accepts up to 1,000 queries in one request;
* avoid repeatedly retrieving the same historical data;
* store data already retrieved in your own application when appropriate.

If your integration consistently exceeds the Free tier, select the Basic or Premium tier in the webshop.

## CSV or API?

Use CSV for occasional, manual analysis. Use the API when data must be transferred to another system automatically or at regular intervals.

You do not need an API tier to download CSV files. For limited automated use, the Free API tier may be sufficient.

## More information

* [Available API measurement fields](/API/api/)
* [Interactive Eniris API documentation](https://api.eniris.be/docs/)
* [SmartgridOne licenses](/Controller/license/)
* [Select an API tier in the Eniris webshop](https://webshop.eniris.com/)
* [External Monitoring API for live data forwarding](/Controller/External%20Signals/Monitoring/monitoring-api/)

# Advanced/dynamic contract


import { GithubAlert } from '@/components/GithubAlert';
import PdfLink from "@site/src/components/PdfLink";

# Advanced/dynamic contract

The advanced dynamic energy contract configurator is available for any location and currency. This configurator requires you to specify a **default rule** and a list of **extra rules**, where each extra rule has an associated timing. This allows for the configuration of energy contracts where prices are time-dependent (e.g., dual tariffs).

> ![Example advanced energy contract configuration](/img/generic/energy-contracts/advanced.png)
> **Figure:** Configuration of Engie Flow variable (BE) contract as of April 2026, for a dual-tariff digital meter located in the Fluvius Imewo network. Note that the off-peak tariff is the default rule and peak tariff the additional rule. The peak rate will be applied on weekdays between 7 am and 10 pm, meaning that the off-peak tariff will be active during weekends and night time hours. <PdfLink url="/img/generic/energy-contracts/engie-flow-2026-04.pdf" />

## Rule configuration
Each rule specifies at least either a consumption or an injection price formula and (for non-default rules) a timing. In accordance with this, the rule configuration page has three sections:

1.  **General:** Specify the name, scope (consumption/injection), and timing.
2.  **Data sources:** Import data (like market prices) for use in formulas. E.g. adding a specific day-ahead market as a data source, enables a “day-ahead price” variable which may then be used in the formulas.
3.  **Formula:** Compose injection/consumption formulas via a drag-and-drop interface.


### General
The general section asks to specify the following inputs for non-default rules:
- **Name:** A non-functional name used for organizational purposes. (The default rule has no name.)
- **Applies to:** Define whether the rule specifies a **consumption (off-take)** price, an **injection** price, or both. (The default rule requires to specify both a consumption and an injection price.)
- **Timing:** When the rule should be applied. Options include:
  - **Always**
  - **On specific weekdays, the entire day:** Specify active weekdays.
  - **During a time range, repeated on specific weekdays:** Specify a start/end time and days. If the start time is later than the end time (e.g., 10 PM to 6 AM), the UI will automatically update to reflect the overnight span. Note that the times should always be expressed in local time in the timezone the controller is located.

> ![Example night rate](/img/generic/energy-contracts/advanced-general.png)
> **Figure:** Typical settings of a peak rate rule. Peak hours depend on the specific location but in Belgium 7 a.m. to 10 p.m. is the most common.

### Data sources
Adding data sources enables extra variables which can then be used in the consumption or injection formula. Click on the “+ Add” button to add a new data source and click on a pill to view the details of the corresponding data source. Pills in black are correctly configured, pills in red indicate a data source which requires extra input. Data sources can be removed by selecting them and using the delete button in their detail view.

> ![Example night rate](/img/generic/energy-contracts/advanced-data-sources.png)
> **Figure:** Example configuration of a day-ahead market price. The price data source is highlighted and in red, meaning it can be edited, but its configuration is not yet completed. The Netherlands are selected, but a choice between quarter hourly and hourly prices remains to be made. As of Oct. 2025, quarter hourly prices are commonly used.

Even though a single data source is sufficient for specifying the formulas, it is possible to configure multiple sources for less common setups. In case multiple data sources are configured, they are numbered and each variable receives a number corresponding to its data source.

Supported Sources (more may be added in the future):
- **Day-ahead market:** depending on the selected currency, a list of countries is shown. After selecting a country, a specific market must be chosen. Many countries have both hourly and quarter hourly prices and some (e.g. the Nordics) have regional prices. A paid "long-term market prediction" feature may be available, depending on the EMS installers and market. When configured, this allows the controller to take prices up to several days in the future into account. Adding a day ahead market adds a “day-ahead price” variable in the formula builder.
- **Tibber API:** Tibber is an energy provider which offers their customers to collect their consumption/injection prices via an API. To add a Tibber datasource, an API key must be provided, which will be used by the controller to fetch this data. Adding a Tibber data source adds a “consumption price” and “injection price” variable in the formula builder.

For Switzerland, the day-ahead selector also contains direct Groupe E, CKW and EKZ tariff feeds, plus the Swiss wholesale market in EUR and converted to CHF. See **[Switzerland - dynamic prices](/App/energy-contract/ch-dynamic)** for the available identifiers and commissioning guidance.

### Formula
The formula section allows configuring the consumption (offtake) and/or injection energy price formulas via a drag-and-drop interface. New blocks are added to a formula by dragging them from the **Available blocks** area to a formula area and they are removed by dragging them from a formula area to the **Drop to delete** area. A red border will show around a formula when it is currently invalid. All formulas must be valid before a rule can be saved.

For each formula, the unit may be configured (e.g. currency/kWh, currency/MWh). Which units are available depends on the selected currency. Because this type of configurator is generic, it directly applies the entered prices, so it is important to explicitly include VAT, transport costs, duties or any extra cost in the entered numbers.

> ![Example night rate](/img/generic/energy-contracts/advanced-formula.png)
> **Figure:** Example configuration of an Energie.be dynamic contract ( <PdfLink url="/img/generic/energy-contracts/energie-be-dynamisch-2026-04.pdf" /> ) for consumption and an Engie Empower ( <PdfLink url="/img/generic/energy-contracts/engie-empower-2026-04.pdf" /> ) contract for injection as of April 2026, for a dual-tariff digital meter located in the Fluvius Imewo network.

## Rule overview
The energy contract overview shows an overview of all configured rules and their corresponding timings and formulas. The controller will always calculate a price based on the first active extra rule which matches a specific moment in time. If no extra rules match, the prices are set by the default rule. 

Note that because the first matching rule is applied, the ordering of the extra rules matters when there are overlapping timeranges. Rules can be reordered using the arrow icons on the left hand side of their cards, or by dragging and dropping them using their handle.

> ![Example German rules (easy)](/img/generic/energy-contracts/advanced-germany-straightforward.png)
> ![Example German rules (hard)](/img/generic/energy-contracts/advanced-germany-odd.png)
> **Figure:** In Germany, net tariffs are time dependent. Often, there is a default rate (Standardtarif), a more expensive peak rate (Hochtarif) and a cheaper rate (Niedertarif). The images shows how two ways configure prices for an energy provider offering a dynamic tariff where the energy price equals the epex spot plus 4 cents/kWh, with net tariffs as follows:
> - off-peak tariff of 2 cents/kWh from 23:00 to 05:00 and from 10:00 to 14:00
> - peak tariff of 12 cents/kWh from 17:00 to 20:00
> - a default tariff of 7 cents/kWh at any other time
> Whilst both approaches are correct and minimal in terms of the number of rules, the second configuration relies on a correct ordering of rules and therefore the first modelling approach is preferable.


<GithubAlert variant="info" title="Note">
    <p>The rule set is usually easier to configure when the rule with the timing which is the hardest to describe is the default rule.</p>
</GithubAlert>


# Dynamic contract (BE)


import { GithubAlert } from '@/components/GithubAlert';
import PdfLink from "@site/src/components/PdfLink";

# Dynamic contract (BE)

While the “Advanced” configurator could also be used to configure a Belgian dynamic energy contract, there is a simpler option for this specific contract type which is faster and less complicated, helping to avoid manual input errors.

This option is available for controllers in Belgium located in a Fluvius region (i.e. Flanders). If a controller is in Flanders but the option is not visible, it is recommended to check whether the postal code of the location is correctly configured.

> ![Energy settings overview with dynamic selected](/img/generic/energy-contracts/be-dynamic-overview.png)
> **Figure:** Energy contract settings for a controller located in Belgium (Flanders) and a currency set to EUR, with “Dynamic” selected.

## Configuration

With the “Dynamic” card option selected, tap the “Provide contract details” button to start configuring.

First select the segment the energy contract relates to: private or business. Then pick the contract name and select the month in which the contract was concluded. Once the contract date is selected, the offtake and injection formulas and a price trading interval switch appear, prefilled with the values corresponding to that specific contract and date.

Carefully validate if the prefilled values and price trading interval match with the price sheet corresponding to the controller energy contract. The formula values should directly match the electricity price tariff of the energy provider, i.e. excluding net costs, VAT, contribution green power certificates,... These extra costs are automatically added.

<GithubAlert variant="warning" title="Warning">
    <p>The formula calculates the energy price in cent/kWh based on a market price in EUR/MWh, conforming to the formulas shared by the VNR (Vlaamse Nutsregulator). This convention involves a unit conversion: a market price multiplied by 0.1 corresponds to an energy provider offering the exact market price.</p>
    <p> Many energy providers follow this convention, but some share a formula to calculate the energy price in EUR/MWh. In such cases the numbers provided by the energy supplier must be divided by 10. The contract configurator will show an error when unlikely numbers are entered to avoid unit conversion errors.</p>
</GithubAlert>

> ![Example dynamic energy contract configuration](/img/generic/energy-contracts/be-dynamic.png)
> **Figure:** Configuration of Power2You Dynamic EL contract as of March 2026. The proposed tariffs exactly match the formula of the tariff sheet <PdfLink url="/img/generic/energy-contracts/power2you-2026-03.pdf" />

In case the prefilled values deviate from what the actual energy contract defines, the value(s) can be modified such that they align with the actual contract.


# Flex contract (BE)


# Flex contract (BE)

Flex contracts use a price system with three prices, which depend on the time of day and the average EPEX spot price at the end of the month.

This option is available for controllers in Belgium located in a Fluvius region (i.e. Flanders). If a controller is in Flanders but the option is not visible, it is recommended to check whether the postal code of the location is correctly configured.

> ![Energy settings overview with flex selected](/img/generic/energy-contracts/be-dynamic-overview.png)
> **Figure:** Energy contract settings for a controller located in Belgium (Flanders) and a currency set to EUR, with “Flex” selected.

## Configuration
On the energy settings overview, if the “Dynamic” card option is currently selected, tap the “Flex” card option to start the configuration. If the “Flex” card option is already selected, tap the “Provide contract details” button to start.

Select the contract name and select the month in which the contract was concluded. The system automatically takes into account the flex price windows as well as net costs, VAT, contribution green power certificates,... Click “Save” to configure the contract.

> ![Example flex energy contract configuration](/img/generic/energy-contracts/be-flex-details.png)
> **Figure:** Configuration of Engie Empower flex contract as of March 2026.


# Switzerland - dynamic prices


import { GithubAlert } from '@/components/GithubAlert';

# Switzerland - dynamic prices

SmartgridOne can plan around dynamic electricity prices in Switzerland. It supports both a general Swiss day-ahead reference and direct tariff feeds for selected Swiss electricity providers. This makes it possible to schedule flexible assets such as batteries, EV chargers and heat pumps for lower-cost intervals.

Swiss dynamic prices are configured with the **[Advanced dynamic contract](/App/energy-contract/advanced-generic)** option. There is no separate simplified Swiss contract card: the Advanced configurator provides the data source and formula controls needed for the different Swiss tariff models.

## Supported Swiss price feeds

Set the contract currency before adding a data source. The app filters the available feeds by that currency.

| Selection in the app | Currency | Resolution | What it represents |
| --- | --- | --- | --- |
| `CH_GroupeE-CHF-15m` | CHF | 15 minutes | Integrated tariff signal for Groupe E VARIO. |
| `CH_CKW-CHF-15m` | CHF | 15 minutes | Integrated dynamic tariff signal for CKW. |
| `CH_EKZ-CHF-15m` | CHF | 15 minutes | Integrated dynamic tariff signal for EKZ. |
| `CH-EUR_to_CHF-1h` | CHF | 1 hour | Swiss wholesale day-ahead reference converted from EUR to CHF. |
| `CH-EUR-1h` | EUR | 1 hour | Swiss wholesale day-ahead price in EUR/MWh. |

The provider feeds and the converted Swiss market series appear under **Day-ahead market** in the Advanced configurator. The names above are the current identifiers; the list is loaded live and may grow as new integrations are released.

<GithubAlert variant="warning" title="Choose the correct tariff component">
    <p>Swiss dynamic products differ. A signal can represent the energy component, grid usage or a more complete tariff. Do not assume that every feed is an all-in customer price. Confirm the selected provider product and compare a few intervals with the provider's tariff publication before putting the controller into operation.</p>
</GithubAlert>

## Configure a Swiss dynamic contract

1. Verify that the controller location is set to **Switzerland** and that its timezone is correct.
2. Open **Energy contract** and set the currency used by the customer's contract: normally **CHF**, or **EUR** when the contract is explicitly denominated in EUR.
3. Select **Advanced dynamic** and open the default rule.
4. Under **Data sources**, add **Day-ahead market**.
5. Select **Switzerland**, then choose the provider feed or wholesale series that matches the contract.
6. Build both the consumption and injection formulas. Include every component that is not already part of the selected signal.
7. Save the rule and compare the resulting prices with the supplier's published values for several intervals, including a low-price and a high-price interval.
8. Verify the next-day plan before allowing the controller to steer flexible assets automatically.

### Choosing a source

Use a **provider feed** when the customer has the matching dynamic product. These integrations follow the provider's published tariff signal and are usually the clearest option for that product.

Use the **Swiss wholesale day-ahead** series when the customer's formula is explicitly indexed to the Swiss spot market. `CH-EUR-1h` is the original EUR/MWh series. For a CHF contract, use `CH-EUR_to_CHF-1h` so the price signal and formula use the same currency.

The optional **day-ahead prediction** is currently available for the EUR Swiss market when the feature is enabled. It extends the planning horizon, but it is a forecast rather than a settled tariff. The controller should still fall back to the published market price when it becomes available.

## What must be included in the formula?

A dynamic customer price can contain more than the selected signal:

- the dynamic energy or grid-price component;
- a supplier surcharge or discount;
- fixed energy components;
- local and national grid charges;
- municipal or cantonal charges;
- federal levies;
- VAT;
- a separate remuneration formula for exported energy.

For a wholesale-indexed contract, the structure is commonly similar to:

```text
consumption price = market price × contract factor + supplier surcharge + other variable charges
injection price   = market price × contract factor - supplier fee
```

These are structural examples, not values to copy. Use the exact units and coefficients from the customer's tariff sheet. The Swiss feeds are stored as a price per MWh; the formula editor can display the result in `c/kWh` or `Fr/MWh` and applies the corresponding unit scale.

## Provider-specific notes

### Groupe E VARIO

Groupe E publishes prices for every 15-minute interval of the following day through a web API. The provider offers both grid-only and more complete tariff views, and the complete view can contain energy, national-grid charges, federal levies and VAT. Municipal or cantonal charges can still vary by location. In Eniris, select `CH_GroupeE-CHF-15m` and verify which tariff composition applies to the project.

[Read the official Groupe E VARIO information](https://www.groupe-e.ch/de/strom/vario)

### CKW dynamic tariff

CKW publishes a dynamic grid-usage profile through its public API. The API distinguishes grid usage, broader grid components, electricity and an integrated value. In Eniris, select `CH_CKW-CHF-15m`, then confirm the applicable CKW product and tariff component for the customer.

[Read the official CKW technical information](https://www.ckw.ch/energie/strom/dynamischer-tarif-fuer-privatkunden-und-unternehmen/dynamischer-tarif-technische-voraussetzungen)

### EKZ dynamic tariff

EKZ's optional dynamic tariff combines a dynamic energy component with dynamic grid usage. Prices change every 15 minutes and next-day tariff information is sent to the EMS. In Eniris, select `CH_EKZ-CHF-15m` and validate the resulting values against the customer's EKZ tariff.

[Read the official EKZ dynamic-tariff information](https://www.ekz.ch/de/angebote/strom/tarife/dynamischer-wahltarif.html)

## Commissioning checklist

- The site, currency and timezone are correct.
- The selected feed matches the customer's provider and tariff product.
- Consumption and injection are both configured, even if one is fixed.
- Formula units match the tariff sheet.
- Taxes, charges and VAT are neither omitted nor counted twice.
- At least several published intervals match the provider's values.
- The controller has a safe fallback when future prices are temporarily unavailable.
- The planned charging and discharging behaviour respects the asset limits and customer preferences.

<GithubAlert variant="info" title="Availability">
    <p>Dynamic Swiss tariffs require the corresponding product, metering setup and provider eligibility. Having a feed available in the Eniris app does not by itself enrol the customer in that tariff. Arrange the tariff and any required smart-meter or EMS registration directly with the electricity provider.</p>
</GithubAlert>


# Fixed/variable contract


import { GithubAlert } from '@/components/GithubAlert';
import PdfLink from "@site/src/components/PdfLink";

# Fixed/variable contract

The fixed/variable energy contract configurator is available for any location and currency, allowing to model the simplest types of energy contract with minimal configuration. A contract of this category uses a fixed, non-time dependent energy price for both consumption and injection.

The form offers two inputs, to configure the consumption and feed-in (injection) prices, in a configurable unit (e.g. currency/kWh, currency/MWh). Which units are available depend on the selected currency. Because this type of configurator is generic, it directly applies the entered prices, so it is important to explicitly include VAT, transport costs, duties or any extra cost in the entered numbers. Carefully confirm that both the entered prices and the picked unit match the energy contract before submitting.


<GithubAlert variant="warning" title="Warning">
    <p>Note that the advanced wizard should be used for contracts where the fixed price depends on the hour of day or the day of the week (e.g. day-night tariff)</p>
</GithubAlert>

> ![Example fixed/variable energy contract configuration](/img/generic/energy-contracts/fixed.png)
> **Figure:** Configuration of Luminus MaxxFix (BE) contract as of April 2026, for a single-tariff digital meter located in the Fluvius Imewo network. <PdfLink url="/img/generic/energy-contracts/luminus-maxxfix-2026-04.pdf" />


# Energy Contract


import { FolderOverview } from "@/components/FolderOverview";
import { GithubAlert } from '@/components/GithubAlert';
import { InsightsName } from "@site/src/components/customFields";

# Energy Contract

For the controller to make a plan which maximizes profit, it must be able to calculate at any time the worth of energy. This includes both the cost of consuming energy from the grid and the revenue made by exporting it to the grid. These costs are set in the energy contract of a site, and can be configured in the app both by the company which claimed the controller and any “installer”-level user of the controller, provided the controller has a firmware version released after April 26th, 2026.

The controller supports any energy contract where prices are either fixed or a function of the day-ahead market cost, with a formula which depends on the time-of-day and day-of-the-week. Notably, this covers most variable, fixed, dynamic and flex energy contracts.

In order to configure these prices, the app offers various configuration forms. Which forms are available depends on two factors:

- The **location** (country, zip code, ...) of the controller, which can be configured on the controller interface or alternatively via <InsightsName/>
- The **currency** used by the energy provider (e.g. EUR, USD, CHF, SEK), which can be configured on the settings page itself
  Note that changing the currency after a contract was configured will invalidate the contract. Depending on the specific configuration method, changing the location of a controller might also result in a configuration becoming invalid.

The app has the following contract configurators:

- **[Fixed/variable](/App/energy-contract/fixed-generic)** (available for any location/currency): Configure a contract by providing a fixed consumption and feed-in price.
- **[Advanced dynamic](/App/energy-contract/advanced-generic)** (available for any location/currency): Configure a contract by specifying a base rule and a set of extra time-dependent rules. The controller will always calculate a price based on the first active extra rule which matches a specific moment in time. If no extra rules match, the prices are set by the default rule. This option is the most flexible, but also the most complicated to set up.
- **[Belgium - dynamic](/App/energy-contract/be-dynamic)** (available for controllers in Belgium [Flanders] and prices in EUR): Pick a private or business energy contract by specifying a contract name and the contract conclusion date.
- **[Belgium - flex](/App/energy-contract/be-flex)** (available for controllers in Belgium (Flanders) and prices in EUR): Flex contracts use a price system with three prices, which depend on the time of day and the average EPEX spot price at the end of the month. There are currently two energy providers offering this system.
- **[The Netherlands - dynamic](/App/energy-contract/nl-dynamic)** (available for the Netherlands and prices in EUR): Dynamic contracts in the Netherlands charge a price equal to the market price with a fixed offset called "inkoopvergoeding" or "verkoopvergoeding". You can configure an energy contract by specifying an energy supplier.
- **[Switzerland - dynamic prices](/App/energy-contract/ch-dynamic)**: Use Swiss wholesale prices or one of the directly integrated Swiss tariff feeds from Groupe E, CKW or EKZ. Swiss contracts are configured through the Advanced dynamic configurator.

## Available price integrations

The exact choices shown in the app depend on the selected currency. Availability is loaded live, so the selector in the app is the definitive source if this table and the application ever differ.

| Integration | Market or provider | Currency | Resolution | Typical use |
| --- | --- | --- | --- | --- |
| Day-ahead market | Multiple European bidding zones | Depends on market | Hourly or 15 minutes | Build a contract formula from a wholesale market price. |
| Day-ahead prediction | Selected supported markets | Same as the linked market | Depends on market | Optional longer planning horizon; availability depends on the market and enabled features. |
| Tibber API | Tibber | Contract currency | Supplied by Tibber | Use the consumption and injection prices returned for a Tibber account. |
| Groupe E VARIO | Switzerland | CHF | 15 minutes | Use the integrated Groupe E tariff signal. |
| CKW dynamic tariff | Switzerland | CHF | 15 minutes | Use the integrated CKW tariff signal. |
| EKZ dynamic tariff | Switzerland | CHF | 15 minutes | Use the integrated EKZ tariff signal. |
| Swiss day-ahead | Switzerland | EUR | 1 hour | Use the Swiss wholesale day-ahead price directly. |
| Swiss day-ahead converted to CHF | Switzerland | CHF | 1 hour | Use the Swiss wholesale reference converted to CHF. |

<GithubAlert variant="info" title="Market price or customer tariff?">
    <p>A wholesale day-ahead price is not automatically the amount on the customer's invoice. Supplier margins, grid charges, duties, taxes and VAT may still need to be included in the formula. A provider-specific tariff feed can already contain several of these components. Always compare the configured result with the customer's current tariff sheet before enabling automated planning.</p>
</GithubAlert>

> ![Example energy contract configuration](/img/generic/energy-contracts/example.png)
> **Figure:** Energy contract configuration for a controller located in the Netherlands with the currency set to EUR.

<FolderOverview folder="App/energy-contract" />


# Dynamic contract (NL)



# Dynamic contract (NL)

While the “Advanced” configurator could also be used to configure a Dutch dynamic energy contract, there is a simpler option for this specific contract type which is faster and less complicated, helping to avoid manual input errors.

This option is available for any controllers located in the Netherlands. If a controller is located in the Netherlands but the option is not visible, it is recommended to check whether its location is correctly configured.

> ![Energy settings overview with dynamic selected](/img/generic/energy-contracts/nl-dynamic-overview.png)
> **Figure:** Energy contract settings for a controller located in the Netherlands and a currency set to EUR, with “Dynamic” selected.

## Configuration

With the “Dynamic” card option selected, tap the “Provide contract details” button to start configuring.

Select the energy provider corresponding to the contract which needs to be configured. Once the energy provider is selected, feed-in fees (one for “binnen salderen” and another for “buiten salderen”), as well as the price trading interval appear, prefilled with the values currently corresponding to that specific energy supplier.

Carefully validate if the prefilled values and price trading interval match with the energy contract (the contract should mention these fees). The fees should directly match the numbers provided by the energy provider, i.e. **including VAT**, but excluding the fixed energy taxes. The tax is automatically added by the controller.

> ![Example dynamic energy contract configuration](/img/generic/energy-contracts/nl-dynamic-details.png)
> **Figure:** Configuration of Easy Energy dynamic contract as of April 28th, 2026.

> ![Easy Energy website contract details](/img/generic/energy-contracts/easy-energy-2026-04-28.png)
> **Figure:** Feed-in fee as communicated by Easy Energy on April 28th, 2026. Note that this matches with the automatically provided prices.

In case the prefilled values deviate from what the actual energy contract defines, the value(s) can be modified such that they align with the actual contract. To avoid unit misinterpretations, input validation will show an error if the magnitude of the entered values is significantly off.


# Start here


import { ChapterLanding } from '@/components/ChapterLanding';
import { FolderOverview } from '@/components/FolderOverview';

<ChapterLanding
  chapter="app"
  introductionLabel="Chapter introduction"
  eyebrow="Mobile energy management"
  title="Eniris App"
  description="Give users a clear view of their energy setup from a mobile device. Learn how app-facing settings work and configure the energy contract that is used for prices, costs, and savings."
  highlightOne="Mobile access"
  highlightTwo="Energy contracts"
  highlightThree="Cost insights"
/>

## Explore the Eniris App

<FolderOverview folder="App" />


# App overview


import { BrandName, ControllerName } from '@site/src/components/customFields';
import ClickableImage from '@site/src/components/ClickableImage';

# App overview

After signing in, the app opens an overview of the energy devices connected to the <BrandName /> <ControllerName />. Select a device icon to open the corresponding detail page

<ClickableImage
  src="/img/generic/AppOverview.png"
  alt="App dashboard showing the connected energy devices"
  maxWidth="650px"
/>

## Understand the installation value

The home or installation value is calculated from the grid connection, solar production, and battery power:

<div style={{ display: 'flex', flexWrap: 'wrap', alignItems: 'center', justifyContent: 'left', gap: '8px', margin: '16px 0' }}>
  <img src="/img/generic/houseIcon.jpg" alt="Installation icon" style={{ width: '50px' }} />
  <span>=</span>
  <img src="/img/generic/gridIcon.png" alt="Grid icon" style={{ width: '50px' }} />
  <span>- (</span>
  <img src="/img/generic/solarPanelIcon.jpeg" alt="Solar panel icon" style={{ width: '50px' }} />
  <span>+</span>
  <img src="/img/generic/batteryIcon.jpeg" alt="Battery icon" style={{ width: '50px' }} />
  <span>)</span>
</div>

Production is shown as a negative value because it reduces the power drawn from the grid.

## Standard device categories

Depending on the installation, the overview can contain:

- **Grid connection:** power imported from or exported to the public grid
- **Solar inverters:** current and historical solar production
- **Battery system:** battery power, status, and stored energy
- **Home or installation:** the combined installation balance
- **Charging stations:** connected EV charging points
- **Heating and cooling:** heat pumps, air conditioners, and boilers

Icons shown in grey represent device categories that are not connected, monitored, or controlled for the selected installation.

## Navigate to device details

Select an icon on the overview or use the dropdown menu at the top of the app. The dropdown lists all available device categories and is useful when several devices of the same type are connected.

<ClickableImage
  src="/img/generic/Dropdown.png"
  alt="App dropdown for selecting a device category"
  maxWidth="700px"
/>

## Data update speed

The overview shows real-time data at the fastest rate provided by the <BrandName /> <ControllerName />. Device detail graphs use quarter-hour values.

The displayed **last update** can therefore be newer than the latest point in a quarter-hour graph. The real-time measurement is added to the historical graph after its aggregation interval has completed.


# Charging schedules


# Charging schedules

The app can schedule electric-vehicle charging per connector at each charging station. A rule defines how much energy or driving range a connected vehicle should receive before a deadline.

## Available rule types

Create a target for:

1. **A fixed time on selected days of the week**, for a recurring charging routine.
2. **A fixed date and time**, for a one-off deadline.

The app always uses the next applicable rule. When no future rule is configured, the vehicle is allowed to charge until it is full, subject to the charging station, vehicle, site limits, and active controller functions.

## Before relying on a schedule

- Confirm that the correct charging station and connector are selected.
- Choose whether the target is expressed in kilometres or kWh.
- Check that the vehicle remains connected long enough to reach the target.
- Allow for the maximum charging power of the vehicle and charging station.
- Verify whether another site or controller limit can reduce the available charging power.

> [!NOTE]
> A schedule defines a charging objective, not a guaranteed result. Available grid power, vehicle limits, communication, and other energy controls can affect the delivered energy.


# Controller setup and settings


import { BrandName, ControllerName } from '@site/src/components/customFields';
import ClickableImage from '@site/src/components/ClickableImage';

# Controller setup and settings

## Add a controller

Use **Add controller** to register a new <BrandName /> <ControllerName /> under the signed-in account. Enter the serial number and verification code printed on the controller label.

<ClickableImage
  src="/img/generic/AddController.png"
  alt="Form for adding a controller with its serial number and verification code"
  maxWidth="800px"
/>

Keep the verification code private. It is used to prove that the account is allowed to claim the controller.

## Open Controller Configuration

Select **Controller Configuration** to open the commissioning interface in a web browser. Use this interface for installation-level configuration and technical commissioning.

> [!CAUTION]
> If the controller interface does not open, confirm that the <BrandName /> <ControllerName /> is switched on, online, and reachable.

## Settings

The Settings page provides access to controller options such as energy prices and control modes.

<ClickableImage
  src="/img/generic/settings.jpg"
  alt="Controller settings available through the app"
  maxWidth="650px"
/>

The available options correspond to settings in the commissioning interface. End-user accounts generally see fewer settings than installer or administrator accounts.

For detailed controller configuration, continue to the [SmartgridOne documentation](/Controller/).

## Manual

Select **Manual** in the app to open the documentation for the controller and connected functionality.


# Using the app


import { FolderOverview } from '@/components/FolderOverview';

# Using the app

The Eniris app gives users a mobile view of their energy installation and provides access to the functions available for their account. Use these guides to understand the dashboard, configure planning and charging, add or configure a controller, and manage access.

<FolderOverview folder="App/using-the-app" columns={2} />

## How the guides fit together

1. Start with **App overview** to understand the dashboard, device icons, navigation, and update speed.
2. Use **Charging schedules** when an EV must reach a target by a specific time.
3. Open **Controller setup and settings** to register a controller or access its commissioning settings.
4. Read **Planning and energy prices** to interpret forecasts, import, export, and price data.
5. Use **Users and account** to share access and manage app-level preferences.

> [!NOTE]
> The available menus and settings depend on the connected equipment, supplier configuration, and permissions of the signed-in account.


# Planning and energy prices


import { BrandName, ControllerName } from '@site/src/components/customFields';
import ClickableImage from '@site/src/components/ClickableImage';

# Planning and energy prices

The Planning page combines a forecast of grid consumption and export with the energy prices used by the <BrandName /> <ControllerName />.

<ClickableImage
  src="/img/generic/Planning.png"
  alt="App planning page with energy-flow and price forecasts"
  maxWidth="750px"
/>

## Consumption and grid-return planning

The planning view contains two grid-connection forecasts:

- **Without control:** the expected installation behaviour if the controller does not optimise the flexible devices.
- **With control:** the expected result after planned controller actions.

A positive value represents consumption from the grid. A negative value represents energy returned to the grid.

Forecasts are estimates based on the available device data, weather, schedules, prices, and configured controls. Actual site behaviour can differ.

## Energy prices

The app shows the prices used by the <BrandName /> <ControllerName /> for planning and optimisation. The price source depends on the configured energy contract and can, for example, use Day-Ahead market prices or a supported supplier integration.

> [!NOTE]
> Purchase and feed-in prices are stored separately because an energy contract can use different prices for consumption and export.

To configure the price calculation, continue to [Energy Contract](/App/energy-contract).


# Users and account


import { BrandName, ControllerName } from '@site/src/components/customFields';
import ClickableImage from '@site/src/components/ClickableImage';

# Users and account

## User management

Use User Management to give another person access to the selected <BrandName /> <ControllerName />. Enter the user's email address and confirm the entry.

<ClickableImage
  src="/img/generic/userManagement.png"
  alt="App user-management page for sharing controller access"
  maxWidth="650px"
/>

Only grant access to people who need it and review the user list when an installer, employee, tenant, or service provider no longer requires access.

## Global settings

Global Settings can control app-wide presentation options such as colour schemes and the visibility of selected menus.

> [!WARNING]
> Global Settings may be unavailable depending on the supplier configuration and the permissions of the signed-in account.

## Account settings

Use Account Settings to change the username or password for the signed-in account.

> [!IMPORTANT]
> Use an email address as the username whenever possible. Without a recoverable email-based username, restoring access after a forgotten password may not be possible.


# Apple app setup


import LicenseDisclaimer from '@site/src/components/LicenseDisclaimer';

<LicenseDisclaimer />

# Apple developer Setup Guide

This guide walks you through setting up your white-labeled app on the Apple Developer 

## Initial Setup

1. Visit the [Apple Developer](https://developer.apple.com/account)
2. The app files will have been uploaded by Eniris

## Required Checklist Items

### 1. Screenshots
   Iphone 6'7, 6'5, 5'5 and both Ipad 12'9 versions are required to be added.

### 2. Description, Keywords, Keywords are also all mandatory fields.

### 3. App Review Information:
   Here is sign-in required, the login details here are those you have received for the insights/app platform

### 4. App information
   - Content Rights and Age Rating must be entered on this page. The app does not contain any sensitive content.
   - Under Privacy Policy URL should be the link to your company privacy policy.


### 5. Pricing and Availability
   1. Price Schedule:
   Here should be the usual price for the app
   2. App Availability:
   Here you can select all countries where the app should be available.

### 6. Add for Review
   When all these fields are completed click “Save”, then “Add for Review”. 

   Now Apple needs to review the app this can take 24h-48h.


## Creating Screenshots

### Browser Method
1. Visit [insights3.eniris.be](https://insights3.eniris.be) or your custom domain
2. Log in to your account
3. For mobile screenshots:
   - Open browser developer tools (F12)
   - Enable device simulation
   - Select mobile device preset
   - Use built-in screenshot tool
4. Save screenshots for Play Store listing

<video src="/videos/making_screenshots.mp4" controls autoPlay loop style={{maxWidth: "100%"}} />

## Resources

Need media assets? Access our mediakit:
[https://eniris.io/mediakit/](https://eniris.io/mediakit/)


# Creating App Store / Play Console developer accounts


import LicenseDisclaimer from '@site/src/components/LicenseDisclaimer';

<LicenseDisclaimer />

# Creating an iOS App Store / Google Play developer account

This page explains how to create the required developer accounts for publishing a white-labeled mobile app.


## Google Play Console Developer account

To create a Google Play developer account, follow Google’s official instructions:

- https://support.google.com/googleplay/android-developer/answer/6112435

More information about publishing an app can be found here:

- https://support.google.com/googleplay/android-developer/topic/7072031

## Apple Developer account

To create an Apple Developer account, follow Apple’s official instructions:

- https://developer.apple.com/support/app-account/

### App Store Connect access

After the developer account has been created:

1. Open App Store Connect:
   - https://appstoreconnect.apple.com/
2. Go to **Users and Access**.
3. Click the **+** (add) icon.
4. Fill in the required fields and assign roles.

![Apple setup img](/img/generic/1698057193453-995.png)


### D‑U‑N‑S number

When creating an Apple Developer account for an organization, you may need a D‑U‑N‑S number.

1. Check whether your organization already has a D‑U‑N‑S number (and request one if needed):
   - https://developer.apple.com/enroll/duns-lookup/#!/request
2. If the system does not find your company, you can request a new D‑U‑N‑S at the bottom of the page.

![Duns request](/img/generic/1698073985286-497.png)


# Google app setup


import LicenseDisclaimer from '@site/src/components/LicenseDisclaimer';
import DownloadButton from '@site/src/components/DownloadButton';

<LicenseDisclaimer />

# Google Play Console App Setup Guide

This guide walks you through setting up your white-labeled app on the Google Play Console

## Initial Setup

1. Visit the [Google Play Console](https://play.google.com/console)
2. Click **Create App**
3. Enter the following details:
   - App name
   - Default language
   - Type: **App** (not game)
   - Accept the declarations

## Required Checklist Items

### 1. Privacy Policy
- Add your company's privacy policy URL

### 2. App Access
1. Select **"All or some functionality in my app is restricted"**
2. Add test account credentials
3. Select **"No other information is required"**

### 3. Basic Settings
- **Ads**: Select "No ads"
- **Content Rating**: Complete the questionnaire
- **Target Audience**: Select appropriate age groups
- **News Apps**: Select "No"
- **COVID-19 Apps**: Select "Not a COVID-19 app"

### 4. Data Safety

![Data Safety Upload](/img/data-safety-upload.png)

Download the pre-filled CSV file with the required data safety declarations and upload it directly to the Google Play Console.
<DownloadButton file="/docs/eniris/data_safety_export.csv" label="Download Data Safety CSV" /> 


### 5. Category Settings
1. Select **Tools** as primary category
2. Add **Tools** as tag
3. Fill in store listing contact details

### 6. Store Listing
1. Prepare content:
   - Short description
   - Full description
   - App icon (512x512 px)
   - Feature graphic (1024x500 px)
   - Phone screenshots (minimum 2)
   - Tablet screenshots (minimum 1 per format)

### 7. App Release
1. Access the **Production** tab
2. Select distribution countries
3. Create new release:
   - Upload .aab file
   - Complete integrity declaration
   - Handle Android 13 ad ID declaration if prompted

### 8. Submit for Review
1. Go to **Publishing overview**
2. Submit for review
   - Review typically takes 24-48 hours

## Creating Screenshots

### Browser Method
1. Visit [insights3.eniris.be](https://insights3.eniris.be) or your custom domain
2. Log in to your account
3. For mobile screenshots:
   - Open browser developer tools (F12)
   - Enable device simulation
   - Select mobile device preset
   - Use built-in screenshot tool
4. Save screenshots for Play Store listing

<video src="/videos/making_screenshots.mp4" controls autoPlay loop style={{maxWidth: "100%"}} />

## Resources

Need media assets? Access our mediakit:
[https://eniris.io/mediakit/](https://eniris.io/mediakit/)


# Whitelabeling app


import { FolderOverview } from '@/components/FolderOverview';

# Whitelabeling app

<FolderOverview folder="App/Whitelabeling app" />


# Microsoft Graph API setup for mail sending


import LicenseDisclaimer from '@site/src/components/LicenseDisclaimer';

<LicenseDisclaimer />

# Microsoft Graph API Setup for Mail Sending

This guide explains how to grant your organization's admin consent to our multi-tenant mail sending app and restrict its access so that it can only send emails from a designated mailbox (for example, `noreply@yourdomain.com`). Even if you have limited IT experience, the step-by-step instructions and prerequisites provided here will help you complete the setup using tools installed on your PC.

> **Note:**  
> If you need assistance, please create a support ticket at [eniris.io/support](https://eniris.io/support).

## Table of Contents

- [Overview](#overview)
- [Prerequisites](#prerequisites)
- [Step 1: Granting Admin Consent](#step-1-granting-admin-consent)
- [Step 2: Capturing Your Tenant Details](#step-2-capturing-your-tenant-details)
- [Step 3: Configuring Access Restrictions](#step-3-configuring-access-restrictions)
- [Additional Information & Resources](#additional-information--resources)
- [Troubleshooting](#common-issues)

## Overview

Our mail sending app uses the Microsoft Graph API with application permissions to send emails from a designated mailbox. To enable this functionality, your admin must:

1. Grant tenant-wide consent to the app.
2. Provide us with your domain name, tenant ID, and the email address you want to use (e.g., `noreply@yourdomain.com`).

These details can be found in your tenant overview at [Microsoft Entra](https://entra.microsoft.com/#view/Microsoft_AAD_IAM/TenantOverview.ReactView).

## Prerequisites

Before you begin, please ensure you have the following:

- **Admin Credentials:** You must have Global Administrator rights for your Microsoft 365 tenant.
- **Access to Microsoft Entra:** You will need to view your tenant details at [Microsoft Entra](https://entra.microsoft.com/#view/Microsoft_AAD_IAM/TenantOverview.ReactView).
- **PowerShell on Your PC:**  
  - Windows PowerShell or [PowerShell Core](https://github.com/PowerShell/PowerShell).
  - Install the [ExchangeOnlineManagement module](https://learn.microsoft.com/en-us/powershell/exchange/exchange-online-powershell-v2?view=exchange-ps) by running:
    ```powershell
    Install-Module -Name ExchangeOnlineManagement -Scope CurrentUser
    ```
- **Basic Knowledge:** Familiarity with copying and pasting commands in PowerShell. Don’t worry if you are a beginner—the steps below are detailed and straightforward.

## Step 1: Granting Admin Consent

1. **Construct the Admin Consent URL:**  
   Use the following URL format. Replace `<YOUR-DOMAIN-NAME>` with your actual domain name (for example, if your domain is "contoso.com", use that):
   ```
   https://login.microsoftonline.com/<YOUR-DOMAIN-NAME>/adminconsent?client_id=03126c25-5828-4b2e-aa6d-d97380cb1cb5&redirect_uri=https://eniris.io
   ```

2. **Visit the URL:**  
   Have your Microsoft 365 global admin log into their browser and navigate to the URL. They will see a consent dialog listing the permissions our app is requesting (for example, **Mail.Send**).

3. **Grant Consent:**  
The admin should click **"Accept"** to grant consent. This action will create a service principal for our app in your tenant and allow it to send emails.

4. **Notify Us:**  
After granting consent, please create a ticket [eniris.io/support](https://eniris.io/support) with the following details:
- Your domain name.
- Your tenant ID (found at [Microsoft Entra Tenant Overview](https://entra.microsoft.com/#view/Microsoft_AAD_IAM/TenantOverview.ReactView)).
- The email address you wish to use for sending mails (e.g., `noreply@yourdomain.com`).

## Step 2: Capturing Your Tenant Details

Our onboarding process will capture your tenant ID automatically when the admin grants consent. However, if you need to manually verify this, you can:
- Sign in to [Microsoft Entra](https://entra.microsoft.com/#view/Microsoft_AAD_IAM/TenantOverview.ReactView).
- Copy your **Tenant ID** from the Tenant Overview page.

## Step 3: Configuring Access Restrictions

For security best practices, we'll create a dedicated security group and use it to restrict the app's access to only your designated mailbox. This implements the principle of least privilege, ensuring the app can only access what's absolutely necessary.

### Creating the Required Mail Security Group

1. **Log into the Microsoft 365 Admin Center:**  
Go to [admin.microsoft.com](https://admin.microsoft.com) and sign in with your admin account.

2. **Create a Security Group:**
- Navigate to **"Groups"** > **"Active groups"**
- Click **"Add a group"**
- Select **"Security"** as the group type and click **"Next"**
- Enter a name (e.g., "Noreply Access Only") and description
- Add the `noreply@yourdomain.com` account as a member
- Click **"Next"** and then **"Create group"**

### Applying Access Restrictions

1. **Open PowerShell:**  
Run PowerShell as an administrator on your PC.

2. **Connect to Exchange Online:**  
Install the ExchangeOnlineManagement module (if not already installed) and then connect:
   ```powershell
   Install-Module -Name ExchangeOnlineManagement -Scope CurrentUser
   Connect-ExchangeOnline -UserPrincipalName "<YOUR-ADMIN-EMAIL>"  # For example: admin@yourdomain.com
   ```

3. **Create the Application Access Policy:**  
Run the following command. Replace `<YOUR-SECURITY-GROUP-EMAIL>` with the actual email address or Object ID of your security group:
   ```powershell
   New-ApplicationAccessPolicy -AccessRight RestrictAccess -AppId "03126c25-5828-4b2e-aa6d-d97380cb1cb5" -PolicyScopeGroupId "<YOUR-SECURITY-GROUP-EMAIL>" -Description "Restrict app access to the noreply mailbox only"
   ```

4. **Verify the Policy:**  
Test that the policy works by running (replace with your actual noreply email address):
   ```powershell
   Test-ApplicationAccessPolicy -Identity "<YOUR-NOREPLY-EMAIL>" -AppId "03126c25-5828-4b2e-aa6d-d97380cb1cb5"
   ```
### Security Considerations

- **Data Isolation:** The service principal created in your tenant ensures the app only has access as allowed by the policy.
- **Least Privilege:** The app requests only the Mail.Send permission and is further restricted to a single mailbox.
- **Auditing:** We recommend periodic reviews of your service principal and Application Access Policy.

## Additional Information & Resources

### Common Issues:

#### Consent Errors:
- Verify admin account permissions at [Microsoft Entra roles](https://entra.microsoft.com/#view/Microsoft_AAD_IAM/RolesManagementMenuBlade/~/AllRoles)
- Check the [consent troubleshooting guide](https://learn.microsoft.com/en-us/azure/active-directory/manage-apps/application-sign-in-unexpected-user-consent-error)
- Ensure the URL is constructed correctly

#### PowerShell Errors:
- Check that the ExchangeOnlineManagement module is installed and up to date
- Verify your admin credentials have sufficient permissions

#### Policy Verification:
- Use `Test-ApplicationAccessPolicy` to verify access restrictions
- Review the [Application Access Policy documentation](https://learn.microsoft.com/en-us/exchange/clients-and-mobile-in-exchange-online/client-access-rules/client-access-rules)


# Commissioning


# Commissioning

Cloud commissioning starts in the manufacturer's platform. Complete the preparation below before requesting activation or enabling an automatic strategy.

## Information and access required

1. Confirm the exact device model, firmware and country or region in [Compatibility](./compatibility).
2. Make sure the device is online and visible in the manufacturer's portal.
3. Prepare the required portal account, site identifier, serial number and API authorization.
4. Confirm that the account includes **control permission**, not only data access, when remote control is required.
5. Record the responsible technical contact for the vendor account and site network.
6. Define the safe fallback if the internet connection, vendor API or control signal becomes unavailable.

The detailed device page lists integration-specific prerequisites, such as the required account role, API application, site identifier or commissioning route.

## Safe activation sequence

1. Connect or authorize one test site.
2. Verify that timestamps, measurements, units and power-sign conventions are correct.
3. Send a limited test setpoint or mode request when control is supported.
4. Confirm the resulting device behaviour and feedback in both the vendor platform and SmartgridOne.
5. Test timeout or communication-loss behaviour where possible.
6. Only then enable the intended automatic control strategy or onboard the remaining portfolio.

> [!CAUTION]
> Do not start with the full asset rating. Use a limited test request that is safe for the device, the grid connection and the active site load.

## Acceptance checks

- Measurements update at the expected interval and do not become stale.
- Import, export, charge and discharge use the agreed sign convention.
- The device accepts only commands permitted for the selected account.
- Feedback confirms whether the requested action was applied.
- The installation returns to the agreed fallback when cloud communication is interrupted.
- Site and device names are clear enough for portfolio operation and support.

If a device is visible but cannot be controlled, check the integration's control scope in [Compatibility](./compatibility), the account permissions and any firmware or regional restrictions.


# Compatibility


# Compatibility

Use this overview during engineering to determine whether an asset supports cloud control, monitoring only, or requires a local connection. Compatibility can depend on the exact model, firmware, account permissions and region; always review the linked setup page before commissioning.

## Cloud control

The devices below can receive control actions through a cloud connection. A listing means that an integration exists; it does not replace the prerequisites on the linked device page.

| Asset type | Manufacturer and supported devices | Cloud connection | Control scope | Detailed setup |
| --- | --- | --- | --- | --- |
| Battery / PV | **AlphaESS SMILE** | AlphaESS Cloud API | Monitoring and storage strategy control | [AlphaESS Cloud API](/Controller/Devices/Cloud/AlphaESS) |
| Battery / PV | **Neovolt systems linked to a Neovolt account** | Neovolt Cloud API | Monitoring and storage strategy control | [Neovolt Cloud API](/Controller/Devices/Cloud/Neovolt) |
| Battery | **Greener / Alfen battery containers, 250 kWh–2 MWh** | Greener API | Monitoring and constant-power setpoint | [Greener / Alfen](/Controller/Devices/PV-hybrid-and-battery-inverters/Greener) |
| PV | **Huawei inverters and SmartLoggers managed by NetEco** | Huawei NetEco | Site import and inverter or SmartLogger control | [Huawei NetEco](/Controller/Devices/Cloud/Huawei/NetEco) |
| PV | **SMA inverters connected to an SMA Data Manager** | SMA cloud API | Active-power and curtailment control | [SMA cloud control](/Controller/Devices/PV-hybrid-and-battery-inverters/SMA/API) |
| PV | **SolarEdge inverters on one SolarEdge monitoring site** | SolarEdge Grid Services API | Site-level monitoring and percentage power limitation | [SolarEdge cloud control](/Controller/Devices/Cloud/SolarEdge) |
| PV / hybrid | **Solis PV inverters and supported hybrid inverters** | SolisCloud API V3 | Monitoring and device control; hybrid support is marked experimental | [SolisCloud API V3](/Controller/Devices/Cloud/Solis) |
| PV | **Sungrow inverters registered in iSolarCloud** | iSolarCloud Open API | Monitoring and active-power limitation; firmware support can vary | [Sungrow iSolarCloud](/Controller/Devices/Cloud/ISolarCloud) |
| PV | **Sparky-connected systems** | Sparky Cloud API | Cloud site import and controller strategy integration | [Sparky Cloud API](/Controller/Devices/Cloud/Sparky) |
| EV charging | **Easee One, Up, Max, Pro, Charge and Core** | Easee Cloud API | Charging-station communication and control | [Easee](/Controller/Devices/EV-charging-station/Easee) |
| EV charging | **Zaptec Go, Go 2 and Pro** | Zaptec API | Charging-station communication and control | [Zaptec](/Controller/Devices/EV-charging-station/Zaptec) |
| EV charging | **Wallbox Pulsar Plus/Max/Pro, eM4, Quasar 2, Commander and Copper SB** | Wallbox API | Charging-station communication and control | [Wallbox](/Controller/Devices/EV-charging-station/Wallbox) |
| EV charging | **OCPP chargers connected through Volt Time Cloud** | Volt Time Cloud / OCPP | Cloud charging control | [Volt Time](/Controller/Devices/EV-charging-station/Volt-Time) |
| Flexible load | **MyEnergi Eddi** | MyEnergi API | Boost or Block control; no watt-level setpoint | [MyEnergi Eddi](/Controller/Devices/Heat-pump/MyEnergi) |

> [!IMPORTANT]
> SolarEdge currently does not accept onboarding of new sites through the API. Existing integrations remain documented, but verify availability before planning a new deployment.

## Monitoring without remote control

Some API integrations contribute measurements to the energy-management system but do not accept a power or charging setpoint.

| Device or data source | What is available | Control limitation | Detailed setup |
| --- | --- | --- | --- |
| **MyEnergi Zappi** | Charger status and measurements through the MyEnergi API | Monitoring only | [MyEnergi Zappi](/Controller/Devices/EV-charging-station/MyEnergi) |
| **Cloud Meter Data** | Cloud-delivered grid-meter measurements | Measurement input only | [Cloud Meter Data](/Controller/Devices/Energy-meter/CloudMeterData) |
| **P1 API meter** | Grid import and export measurements | Measurement input only | [P1 API](/Controller/Devices/Energy-meter/P1Api) |
| **Zeversolar inverter** | Inverter data through the existing API integration | Curtailment is not supported | [Zeversolar](/Controller/Devices/PV-hybrid-and-battery-inverters/Zeversolar) |

> [!NOTE]
> An `API` label on a device page does not always mean cloud control. For example, the Zendure SolarFlow integration uses a **local API**, and its P1 meter is a local measurement source. Those devices are therefore not part of this cloud-control list.

## Before selecting an integration

Confirm the exact device model and firmware, the country or region, the available API license, and whether the account grants control permission rather than data access only. Continue with [Commissioning](./commissioning) once the combination is confirmed.


# How cloud control works


# How cloud control works

SmartgridOne Cloud exchanges measurements and control requests with a manufacturer cloud, OCPP platform or partner EMS. The asset keeps its existing internet connection; a separate local Modbus or RS485 connection is not required for that integration.

<div className="not-prose my-8 grid gap-4 md:grid-cols-3">
  <div className="rounded-2xl border border-blue-200 bg-blue-50 p-5 dark:border-blue-900 dark:bg-blue-950/30">
    <strong className="block text-base text-blue-950 dark:text-blue-100">No local device bus</strong>
    <span className="mt-2 block text-sm leading-6 text-blue-900/75 dark:text-blue-100/75">The device communicates through its existing vendor cloud or partner platform.</span>
  </div>
  <div className="rounded-2xl border border-cyan-200 bg-cyan-50 p-5 dark:border-cyan-900 dark:bg-cyan-950/30">
    <strong className="block text-base text-cyan-950 dark:text-cyan-100">Portfolio-ready</strong>
    <span className="mt-2 block text-sm leading-6 text-cyan-900/75 dark:text-cyan-100/75">Multiple remote sites can be imported and managed from one environment.</span>
  </div>
  <div className="rounded-2xl border border-indigo-200 bg-indigo-50 p-5 dark:border-indigo-900 dark:bg-indigo-950/30">
    <strong className="block text-base text-indigo-950 dark:text-indigo-100">Internet-dependent</strong>
    <span className="mt-2 block text-sm leading-6 text-indigo-900/75 dark:text-indigo-100/75">Availability, latency and fallback behaviour depend on internet access and the vendor API.</span>
  </div>
</div>

## From measurement to control

1. The device publishes measurements and status to its manufacturer cloud or connected platform.
2. SmartgridOne Cloud retrieves the available measurements and evaluates the configured energy strategy.
3. When control is supported, SmartgridOne sends a permitted setpoint or operating-mode request through the platform API.
4. New measurements and status provide feedback for the next control decision.

The update frequency, command latency and available feedback differ per integration. Review the exact device page instead of assuming that every cloud connection behaves identically.

## Cloud or local connection?

Choose a cloud connection for remote portfolios and devices that do not expose a suitable local protocol. Prefer a local Modbus, RS485 or local-API connection when deterministic response time, site autonomy during an internet outage, or a customer-specific fail-safe is essential.

| Consideration | Cloud connection | Local connection |
| --- | --- | --- |
| Installation | Uses the device's existing platform connection | Requires a supported local interface and network path |
| Portfolio onboarding | Well suited to geographically distributed sites | Usually commissioned site by site |
| Internet outage | Cloud communication becomes unavailable | Local control can continue, depending on the installation |
| Response | Depends on internet and platform latency | Usually more deterministic |
| Capabilities | Limited to functions exposed by the platform API | Limited to the local protocol and device driver |

## Loss of communication

Define a safe fallback at the device or gateway for internet loss, API timeouts or stale commands. A cloud integration must not be the only protection for equipment that needs a safety-critical response.

> [!TIP]
> Confirm the expected control interval and fallback behaviour during engineering, then test both normal operation and loss of communication during commissioning.


# Start here


<ChapterLanding
  chapter="cloud"
  eyebrow="CLOUD-CONNECTED ENERGY CONTROL"
  title="SmartgridOne Cloud"
  description="Connect, monitor and control compatible energy devices through manufacturer clouds and partner APIs — without requiring a local protocol connection to every asset."
  highlightOne="Cloud device control"
  highlightTwo="Compatibility overview"
  highlightThree="Commissioning guidance"
/>

SmartgridOne Cloud runs energy-management logic in the cloud and communicates with supported equipment through a manufacturer's API, an OCPP platform or a partner EMS connection. It is useful when a direct Modbus or RS485 connection is unavailable, when sites are geographically distributed, or when a complete portfolio must be commissioned remotely.

## Explore SmartgridOne Cloud

<FolderOverview folder="Cloud" />


# Partner EMS and portfolio connections


# Partner EMS and portfolio connections

SmartgridOne Cloud can represent virtual sites whose measurements arrive from a partner platform and whose setpoints are returned to that platform. This is useful when the physical devices are already aggregated behind another EMS or portfolio interface.

## Available connections

| Integration | Connection | Supported asset groups |
| --- | --- | --- |
| **Enalpin, Neargrid, Scholt, Taylor and WithTheGrid** | Bidirectional MQTT | Solar, storage, heat pumps and grid/consumption meters; EV chargers are not currently included |
| **Helin** | Helin Cloud API | Solar inverters; storage devices are not currently included |

See the [EMS Control integrations](/Controller/Devices/Cloud/EMS%20Control) for topic structure, measurements, commands and partner-specific prerequisites.

## Define the exchange before onboarding

Agree on the site and device identifiers, measurement units, timestamps, power-sign convention, command frequency, response time, timeout and fallback behaviour. Also define which asset groups may be controlled and which health or availability signals the partner must provide.

## Commissioning approach

1. Validate one representative site and its complete measurement set.
2. Compare grid, production, consumption and storage signs with the partner platform.
3. Test a limited setpoint in both directions and confirm the feedback.
4. Simulate a stale measurement or lost connection and verify the agreed fallback.
5. Reuse the validated mapping when onboarding the rest of the portfolio.

> [!NOTE]
> Partner integrations can differ in supported assets and commands. Treat the connection agreement and linked integration page as the source of truth for a specific rollout.


# A1-Port


# Overview

The A1 is a plug-and-play device designed for easy installation and use.

## Installation

The device features simple connectivity:
- Plug-and-play functionality - no configuration needed
- Can be connected using either:
  - P1 cable
  - A1 cable

> [!TIP]
> Simply plug in the A1 and it will work automatically without any additional setup!


# dS1242 Ethernet-Relay module


import ClickableImage from '@site/src/components/ClickableImage';

## Distributor & DHCP network

If you purchased the dS1242 Ethernet relay module through your distributor, it will be preconfigured.

In networks where DHCP is used, you do not need to do anything. Just connect the module to Ethernet and connect the power adaptor.

Connect the relays as needed for the device you will use them to control.


## Purchased the module elsewhere or you are using it on a network with fixed IP addresses

### Connecting the dS1242 Ethernet Ethernet-Relay module
To connect a dS1242 you'll need to first check if there is a firmware version running on it.
Connect an ethernet cable connected to your network and the 12V power supply to the module.
Check if the blue LED flashes 3 times.
If it does not, you should install firmware on the module first. Therefore continue to the firmware update.
If it does flash 3 times, you need to check if the communication is set correctly. Go to set the control to modbus.
<ClickableImage src="/img/generic/ds1242.png" alt="Image" maxWidth="450px" />

### Updating the firmware

You'll need a PC and a mini-USB to USB cable to install and use the program to do the update of the firmware.

Please go to the following link:
> [!NOTE]
> https://www.robot-electronics.co.uk/dscript.html

Select the applicable version of dScript (see 1 on the figure). Download it and install it. If you already have a version make sure you have the latest version.

After this, download the Documentation and dScript Examples zip file (see 2 on the figure). Extract all data and remember the folder location.

Before continuing please make sure that:

1. dScript Editor closed down.

2. dS1242 not connected or powered.

<ClickableImage src="/img/generic/RobotElectronics.png" alt="Image" maxWidth="450px"/>

Continue by preparing the module as followed:

1. Power-up the dS1242.
2. Hold down the blue reset button for a couple of seconds until the red LED comes on (this indicates the module is in boot-loader mode).
3. Connect the USB-mini lead to the PC.

<ClickableImage src="/img/generic/ds1242Prepare.png" alt="Image" maxWidth="450px"/>

#### Update the firmware with dScript

1. Run the dScript editor.

2. Now look in the Module panel, you should see: ds1242 vX.XX indicates it's the boot-loader that is running.

3. Load the project: File -> Open project 'yourFolder'\dScriptPublish\Examples\app-dS1242-vx-xx\app-dS1242-vx-xx.dsj

    Substitute the path 'yourFolder' for where you placed the dScriptPublish folder.

4. Click the build button (white triangle on green button). This will update the system firmware and load the application.
5. When done, the new version will be displayed.

<ClickableImage src="/img/generic/UpdateFirmware.png" alt="Image" maxWidth="450px"/>


### Set the control to modbus
In order to set the control to modbus, you have to:

1. Connect the power supply and the ethernet cable (linked to your network)

2. Connect the dS1242 mini-USB to 5V DC power supply (for example a pc USB port)

3. Search for the IP-address in the network (mac-address starts with 60:8A:10:xx:xx:xx, D8:80:39:xx:xx:xx) or 

4. Go to the following URL: "IP-address/_config.htm"

5. In the tab TCP/IP, modify as shown in the top image
> [!NOTE]
> This can be prepared on beforehand

<ClickableImage src="/img/generic/ControlToModbus.png" alt="Image" maxWidth="450px"/>

# Eniris Generic protocol


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import ClickableImage from '@site/src/components/ClickableImage';
import PdfLink from '@site/src/components/PdfLink';
import DownloadButton from '@site/src/components/DownloadButton';


## Protocol implementation
The <BrandName /> <ControllerName /> supports adding any energy meter, PV, battery or hybrid inverter that supports the <BrandName /> <ControllerName /> protocol.

<DownloadButton file="docs/eniris/ENIRIS_SMARTGRIDONE_EMS_AS_MODBUS_MASTER_V4_1.xlsx" label="You can download the specifications of the protocol through this link." />



You are free to implement this protocol on your device.

# Accessories


import { FolderOverview } from '@/components/FolderOverview';

# Accessories

<FolderOverview folder="Controller/Accessories" />


# MBus-Ethernet Converter


import { BrandName, ControllerName, CustomerName, InsightsName, InsightsUrl } from '@site/src/components/customFields';
import Details from '@theme/Details';

> [!CAUTION] Compatible converters
> <CustomerName /> only warrants compatibility with the converter ordered from <CustomerName />. Other converters may not work out of the box.

> [!IMPORTANT]
> We do **not** provide support for cabling or wiring questions (e.g., identifying wire colors such as red, white, green). Please refer to your product manuals or a qualified technician for any cabling-related assistance.
>


# P1 Cable


import { BrandName, ControllerName, CustomerName, InsightsName, InsightsUrl } from '@site/src/components/customFields';
import Details from '@theme/Details';

> [!CAUTION] Compatible converters
> <CustomerName /> only warrants compatibility with the P1 cable ordered from <CustomerName />. Other cables may not work out of the box.

> [!IMPORTANT]
> We do **not** provide support for cabling or wiring questions (e.g., identifying wire colors such as red, white, green). Please refer to your product manuals or a qualified technician for any cabling-related assistance.
>


# P1-Ethernet Converter


import { BrandName, ControllerName, CustomerName, InsightsName, InsightsUrl } from '@site/src/components/customFields';
import Details from '@theme/Details';

## Compatible converters
- YouLess
- Home Wizard
- Sparky P1 meter

> [!IMPORTANT]
> We do **not** provide support for cabling or wiring questions (e.g., identifying wire colors such as red, white, green). Please refer to your product manuals or a qualified technician for any cabling-related assistance.
>


# Relay-Ethernet Converter


import { BrandName, ControllerName, CustomerName, InsightsName, InsightsUrl } from '@site/src/components/customFields';
import Details from '@theme/Details';

> [!CAUTION] Compatible converters
> <CustomerName /> only warrants compatibility with the converter ordered from <CustomerName />. Other converters that do a protocol conversion are generally not supported.

> [!IMPORTANT]
> We do **not** provide support for cabling or wiring questions (e.g., identifying wire colors such as red, white, green). Please refer to your product manuals or a qualified technician for any cabling-related assistance.
>


# RS232-Ethernet Converter


import { BrandName, ControllerName, CustomerName, InsightsName, InsightsUrl } from '@site/src/components/customFields';
import Details from '@theme/Details';

> [!CAUTION] Compatible converters
> <CustomerName /> only warrants compatibility with the converter ordered from <CustomerName />. Other converters that do a protocol conversion are generally not supported.

> [!IMPORTANT]
> We do **not** provide support for cabling or wiring questions (e.g., identifying wire colors such as red, white, green). Please refer to your product manuals or a qualified technician for any cabling-related assistance.


# RS422-Ethernet Converter


import { BrandName, ControllerName, CustomerName, InsightsName, InsightsUrl } from '@site/src/components/customFields';
import Details from '@theme/Details';

> [!CAUTION] Compatible converters
> <CustomerName /> only warrants compatibility with the converter ordered from <CustomerName />. Other converters that do a protocol conversion are generally not supported.
> [!IMPORTANT]
> We do **not** provide support for cabling or wiring questions (e.g., identifying wire colors such as red, white, green). Please refer to your product manuals or a qualified technician for any cabling-related assistance.


# RS485-Ethernet Converter


import Details from '@theme/Details';
import ClickableImage from '@site/src/components/ClickableImage';
import { BrandName, ControllerName } from '@site/src/components/customFields';

<img src="/img/generic/logoRS485.png" alt="RS485 Converter Logo" style={{ maxWidth: '200px', display: 'block', margin: '0 auto' }} />

## Connecting to the RS485 Converter

1. Connect the converter to a LAN network and plug in the adapter.

2. Download and install **EZ Manager** [here](https://www.eztcp.com/en/download/ezmanager).

3. Connect your computer to the same LAN network as the converter.

4. Open **EZ Manager** and select **"Search All"**.

   <ClickableImage src="/img/generic/stap 1 rs485.png" alt="Search All Button" maxWidth="400px" />

5. You can identify your converter in the column **"Search Results"** by its **MAC address**.

## Network settings

In the network tab, you can specify the network settings for the RS485 converter.  
On the left, you can find the settings for obtaining an automatic IP address (**recommended in most cases**).

<ClickableImage src="/img/generic/netwerkinstellingen_rs485_ethernet.png" alt="RS485 Converter Network Settings" maxWidth="400px" />

## As a serial extension

You can use the RS485 converter as a serial extension to the <BrandName /> <ControllerName />.

Fill in the settings in the tab **'Serial port'** as shown in the figure.

<ClickableImage src="/img/generic/serieleuitbreiding_rs485_ethernet.png" alt="Serial Extension settings" maxWidth="400px" />

## Additional settings

Fill in the settings of the **'Options'** tab exactly as shown in the image.

<ClickableImage src="/img/generic/additionalsettings_rs485_ethernet.png" alt="Option" maxWidth="400px" />

## Save

Select **"Write"** to save.

<ClickableImage src="/img/generic/opslaan_rs485_ethernet.png" alt="Option" maxWidth="400px" />

## Troubleshooting

No device found → error in:
- Modbus address
- Baud rate
- Parity bit (none, even, uneven)
- Stop bit
- Modbus A and B connection (loose or reversed)
- Chosen device (wrong make or type)
- Chosen protocol (wrong protocol)

> [!IMPORTANT]
> We do **not** provide support for cabling or wiring questions (e.g., identifying wire colors such as red, white, green). Please refer to your product manuals or a qualified technician for any cabling-related assistance.
>


# RS485-USB Converter


import { BrandName, ControllerName, CustomerName, InsightsName, InsightsUrl } from '@site/src/components/customFields';
import Details from '@theme/Details';
import ClickableImage from '@site/src/components/ClickableImage';

<img src="/img/generic/usb-to-rs485.png" alt="RS485 Converter Logo" style={{ maxWidth: '200px', display: 'block', margin: '0 auto' }} />

> [!CAUTION] Compatible converters
> <CustomerName /> only warrants compatibility with the converter ordered from <CustomerName />. Other converters that do a protocol conversion are generally not supported.

> [!IMPORTANT]
> We do **not** provide support for cabling or wiring questions (e.g., identifying wire colors such as red, white, green). Please refer to your product manuals or a qualified technician for any cabling-related assistance.
>


# Certificates


import { BrandName, ControllerName, CustomerName, InsightsName, InsightsUrl } from '@site/src/components/customFields';
import Details from '@theme/Details';
import PdfLink from '@site/src/components/PdfLink';
import DownloadButton from '@site/src/components/DownloadButton';

# Certificates

## <BrandName /> <ControllerName /> model OM1
EU Declaration of conformity:

<DownloadButton file="/docs/eniris/EU Declaration of conformity OM1.pdf" label="Download PDF File" /> 


# 1. Link to your account


import { BrandName, ControllerName, CustomerName, InsightsName, InsightsUrl } from '@site/src/components/customFields';
import InsightsLink from '@site/src/components/InsightsLink';
import Details from '@theme/Details';
import ClickableImage from '@site/src/components/ClickableImage';

# Link the <BrandName /> <ControllerName /> to your account

1. Log in to the app (smartphone) or <InsightsLink /> (computer).

2. Set the view to '<BrandName />'.

3. Click on 'Add controller'.
<ClickableImage src="/img/eniris/insights-add-controller-button.png" alt="Image 1" maxWidth="350px" />

4. Fill in the serial number and verification code. You can find these on the label of the <BrandName /> <ControllerName />. Click 'Claim'.
<ClickableImage src="/img/generic/example-label.jpg" alt="Image 1" maxWidth="350px" />
<ClickableImage src="/img/eniris/insights-add-controller.png" alt="Image 1" maxWidth="550px" />

5. The <BrandName /> <ControllerName /> is now linked to your account! You can now [access the commissioning interface from the portal](/Controller/Configuration%20from%20A%20to%20Z/2-accessing-commissioning-interface#option-1-access-through-the-app-or-portal), or [give access to the end user](/Controller/Configuration%20from%20A%20to%20Z/11-Extra-Information/user-management/).


# 10. External control signals


import {
  BrandName,
  ControllerName,
  CustomerName,
  InsightsName,
  InsightsUrl,
} from "@site/src/components/customFields";
import Details from "@theme/Details";

# 10. External control signals

> [!TIP]
> For the full list of support external control signals, see "[Supported External Control Integrations](/Controller/external%20signals/)"

> [!WARNING] external signals
> If external control signals (Yuso, Edmij, Frank Energie, ...) are active, the external control signal has priority and the default control modes will be used as fallback.


# Adding a device


import { BrandName, ControllerName, CustomerName, InsightsName, InsightsUrl } from '@site/src/components/customFields';
import Details from '@theme/Details';
import ClickableImage from '@site/src/components/ClickableImage';

# Adding a device

1. Log in to [the commissioning interface](/Controller/Configuration%20from%20A%20to%20Z/2-accessing-commissioning-interface/).

2. Go to the "Devices" tab and click "Start device wizard".
<ClickableImage src="/img/generic/add-device-en.jpg" alt="Image 1" maxWidth="550px" />

3. Choose which type of device you want to add.
<ClickableImage src="/img/generic/device-type-en.png" alt="Image 1" maxWidth="550px" />

4. Select the brand of the device.
<ClickableImage src="/img/generic/device-brand-en.png" alt="Image 1" maxWidth="550px" />

5. Select how the device is connected. Depending on the device type and brand, the following options are available:
Depending on the device type and brand, the following options are available:
    - Ethernet TCP
    - RS485 port (more info [here](/Controller/wiring-best-practices/#rs485))
    - RS232 port
    - P1 port USB cable
    - Digital output or relay
    - Pulse input
    - Ethernet TCP to RS485 converter (more info [here](/Controller/Accessories/rs485-ethernet))
    - Ethernet TCP to RS232 converter
    - Ethernet TCP to P1 port gateway
    - Ethernet TCP to relay converter
    - Ethernet TCP to MBus converter

<ClickableImage src="/img/generic/add-device-interface-en.png" alt="Image 1" maxWidth="550px" />

> [!NOTE]
> If the mode is not displayed then this connection mode is not supported, or - in the case of a P1 cable - your cable is not properly connected to the <BrandName /> <ControllerName />. Please contact your installer or supplier.
    
6. Select the used communication protocol of your device. If the model of your device is not mentioned, you can try using different communication protocols.
<ClickableImage src="/img/generic/add-device-model-en.png" alt="Image 1" maxWidth="250px" />

7. Enter the additional inputs as requested.
<ClickableImage src="/img/generic/device-additional-inputs-en.jpg" alt="Image 1" maxWidth="550px" />

8. (Only shown for Ethernet TCP connections, skip this step if you are using RS485 connection). Select the device you want to add. You can do this by:
    a. Add by MAC address (recommended).
    b. Add by IP address (not recommended unless you are sure the converter has a fixed IP address).
<ClickableImage src="/img/generic/add-device-ethernet-en.jpg" alt="Image 1" maxWidth="550px" />

9. (This steps and onwards are for both TCP and RS485) In the next step, if required, you can manually adjust the parameters used to search for the device. In most circumstances, we recommend staying with the default set values.
<ClickableImage src="/img/generic/add-device-scan-parameteres-summary-en.jpg" alt="Image 1" maxWidth="550px" />

10. The next step searches for the device. Click "End scan & go to results" when the device is found. You do not have to wait for the scan to end completely to continue.

> [!TIP] Tip for RS485 connections
> If your device has a high number as an address, it can take some time before it is found. It is recommended to choose low numbers as addresses in your device if you can (1, 2, 3, etc.).
<ClickableImage src="/img/generic/add-device-scan-log-en.jpg" alt="Image 1" maxWidth="550px" />

11. Save the device. In this step, the specifications of the device are read out. After this, you can save the device. Click on "Save and go to device settings".
<ClickableImage src="/img/generic/add-device-scan-save-en.jpg" alt="Image 1" maxWidth="550px" />

12. Further complete the device settings.
<ClickableImage src="/img/generic/device-settings-en.jpg" alt="Image 1" maxWidth="550px" />

> [!NOTE] Troubleshooting
> If you experienceany issue :
>     - With RS485 connection follow this [link](/Controller/Troubleshooting/device-communication/#rs485)
>     - With TCP connection follow this [link](/Controller/Troubleshooting/device-communication/#ethernet)

# Admin password and two-factor authentication


import { BrandName, ControllerName, CustomerName, InsightsName, InsightsUrl } from '@site/src/components/customFields';
import Details from '@theme/Details';
import ClickableImage from '@site/src/components/ClickableImage';

# Admin password and two-factor authentication

The commissioning interface has a local user 'admin'. This user can log in to the <BrandName /> <ControllerName /> on the local network, also when there is no internet connection. Access through the app, the portal or remote.eniris.be uses your <InsightsName /> account instead, so the admin password does not apply there, see [User management](/Controller/Configuration%20from%20A%20to%20Z/11-Extra-Information/user-management/).

<ClickableImage src="/img/generic/settings/change-password-2fa-en.png" alt="The change password and two-factor authentication sections of the settings page" maxWidth="550px" />

## Changing the admin password

> [!NOTE]
> The first time you log in locally with the default password, the <BrandName /> <ControllerName /> asks you to choose a new password before you can continue. This is a security measure: the default password must not stay in use.

1. Go to the 'Settings' tab of the commissioning interface and scroll to "Change password".
2. Enter the old password, the new password and the new password once more.
3. Click "Change password".

> [!WARNING]
> Keep the new password in a safe place. If the password is lost, the local login can only be restored with a [factory reset](/Controller/Configuration%20from%20A%20to%20Z/11-Extra-Information/reset/), or through the portal by your distributor.

## Two-factor authentication (2FA)

With two-factor authentication enabled, logging in to the commissioning interface requires the password and a six-digit code from an authenticator app (for example Google Authenticator or another app that supports time-based one-time passwords).

Two-factor authentication is enabled per user account, for the account with which you are logged in when you enable it:

- Enabled while logged in as 'admin', it protects the admin login on the local network. It does not apply to remote.eniris.be: the admin user cannot log in there, because remote access always uses your <InsightsName /> account.
- Enabled while logged in with your <InsightsName /> account (locally, or through the app, the portal or remote.eniris.be), it applies to every login of that account on this <BrandName /> <ControllerName />, including the logins through remote.eniris.be.

### Your <InsightsName /> account has 2FA: login fails after a restart or update

The 2FA that you enable on your <InsightsName /> account in the portal is separate from the controller-specific 2FA described on this page.

After a restart or software update, you may be taken back to the <BrandName /> <ControllerName /> login page. This page cannot complete the 2FA step for your <InsightsName /> portal account: it has no field for that account's verification code. Signing in there with your portal email address and password therefore fails when portal 2FA is enabled.

To reconnect, return to the portal, sign in with 2FA if prompted, and open the commissioning interface again using the "Remote" button for your controller. The portal passes your already verified identity to the controller, so you do not need to enter your portal credentials on the controller login page. You can keep 2FA enabled on your <InsightsName /> account.

If you have also enabled controller-specific 2FA for this account in the commissioning interface, the controller can still ask for its own verification code. That is a separate check and is not replaced by portal 2FA.

### Enabling 2FA

1. Go to the 'Settings' tab of the commissioning interface and scroll to "Two-Factor Authentication (2FA)". The section shows whether 2FA is currently enabled or disabled for the account you are logged in with.
2. Click "Enable 2FA".
3. A page with a QR code appears. Scan the QR code with your authenticator app. The entry in the app is named after the serial number of the <BrandName /> <ControllerName />.
4. Click "Proceed". From now on, every login of this account asks for the verification code of the app after the password.

<ClickableImage src="/img/generic/settings/2fa-qr-en.png" alt="The QR code page for enabling two-factor authentication" maxWidth="450px" />

> [!WARNING]
> If you lose the authenticator app, you can no longer log in with this account. Add the <BrandName /> <ControllerName /> to a second authenticator app or make a backup of the app before you close the QR code page.

### Disabling 2FA

1. In the section "Two-Factor Authentication (2FA)", click "Disable 2FA".
2. Enter the current verification code of your authenticator app to confirm.


# Advanced settings


import { BrandName, ControllerName, CustomerName, InsightsName, InsightsUrl } from '@site/src/components/customFields';
import Details from '@theme/Details';
import ClickableImage from '@site/src/components/ClickableImage';

# Advanced settings

The advanced settings are reached from the 'Settings' tab of the commissioning interface: scroll down to the section "Advanced settings" and click "Go to advanced settings".

> [!WARNING]
> These settings are intended for expert users. Wrong configurations can have an impact on the performance of the <BrandName /> <ControllerName />. Unless a chapter of this manual or your distributor tells you to change one of them, leave them at their default value.

<ClickableImage src="/img/generic/settings/advanced-settings-overview-en.png" alt="The advanced settings page with its collapsed groups" maxWidth="650px" />

## How the page works

- The settings are grouped in collapsible sections. Click the title of a section to open it.
- Every section is a table with the name of the setting, a help icon with the explanation of the setting, its current value and a field for the new value. Each section has its own "Save" button at the bottom: the changes of a section are only applied after you click that button.
- A warning is shown next to a setting that deviates from its standard value where that is risky. Such a warning is a hint to put the setting back to its default, unless you know why it was changed.
- Some settings are one-way: once they are switched off, they disappear from the page. See [Retired settings](#retired-settings).

<ClickableImage src="/img/generic/settings/advanced-settings-group-en.png" alt="One section of the advanced settings, opened" maxWidth="750px" />

## Data & scheduler

| Setting | Default | Explanation |
|:--|:--|:--|
| Data reading period (seconds) | 1 (cloud <BrandName /> <ControllerName />: 300) | How often the devices are read out. Leave this at zero or one, so that the devices are read out as often as possible. If the value is lower than the time a full readout takes, the devices are simply read out continuously. |
| Maximum communication backoff time (seconds) | 3840 | When communication with a device repeatedly fails, the <BrandName /> <ControllerName /> waits longer and longer between retries, up to this maximum. Retrying a failing device costs communication time (for example on a serial bus) and slows down the readout of the devices that do work. Lowering this value is only a last resort: rather fix the communication problem of the device. |
| Scheduler run period (seconds) | 1 (cloud <BrandName /> <ControllerName />: 10) | The minimum time between two consecutive executions of the control loop. See also [Control response time](/Controller/control-response-time/#scheduler-interval). |
| Settling check mode | Always check for settling (cloud <BrandName /> <ControllerName />: Never check for settling) | Whether the control loop waits until all controlled devices have settled to their setpoint before calculating the next setpoint. "Always check for settling" gives the most stable control. "Only check for settling if oscillating setpoints are detected" is a balance between stability and speed. "Use a state estimator instead of a settling check" is the fast and stable option, which will become the default in the future: the control loop does not wait for the devices, but estimates the actual power of every device from its measurements, its setpoints and the changes it observes in the grid power, and calculates the next setpoints from those estimates. "Never check for settling" runs the control loop as fast as possible without any of this, but may cause instability: only use it where open loop control is acceptable, for example when the <BrandName /> <ControllerName /> is used exclusively through an external API and exceeding the grid limits is not an issue. See also [The settling check](/Controller/control-response-time/#the-settling-check). |
| Maximum settling time (seconds) | 30 | How long the control loop waits at most for settling before it proceeds anyway. Lower values make the control react faster, but may cause instability. |
| Disable dynamic power derating | False | The dynamic derater detects devices that persistently deliver less power than their setpoint asks (for example because of a temperature or battery management limitation), and temporarily lowers the power planned for them so that other devices can compensate and the grid limits are still met. It periodically probes whether the device has recovered. Disable it only as a last resort, for example while diagnosing a device. |

## Grid limits

| Setting | Default | Explanation |
|:--|:--|:--|
| Grid limit safety factor | 0.9 | Multiplier applied to the grid limits. With the default of 0.9, everything (including solar production) is controlled to stay within 90% of the configured grid limits, which leaves room to react to sudden power fluctuations. Set it to 1 only if you are sure there is no risk of tripping breakers. See also [Troubleshooting: control issues](/Controller/Troubleshooting/control-malfunctioning/#grid-limits--circuit-breaker). |
| Grid export safety margin fraction | 0.015 | A minimum for the export safety margin, as a fraction of the larger of the two grid limits (after applying the safety factor). It is used when the absolute "Allowed grid export power safety margin" of the [grid settings](/Controller/Configuration%20from%20A%20to%20Z/3-grid-limits/#allowed-grid-export-power-safety-margin-kw) is lower. It is not applied on a cloud <BrandName /> <ControllerName />. Do not change this unless you absolutely know what you are doing. |
| Grid power limits mode | Instantaneous | How the grid limits are interpreted: as **instantaneous** limits or as **fifteen-minute averages**. With "Fifteen-minute average", the <BrandName /> <ControllerName /> limits the average grid power of the current quarter hour to the configured limits, which means that the instantaneous power can be much higher, especially if it was low during the first part of the quarter. See [Grid limits: grid power limits mode](/Controller/Configuration%20from%20A%20to%20Z/3-grid-limits/#grid-power-limits-mode). |
| Always treat the grid import power limit as instantaneous | False | Keeps the import limit instantaneous, regardless of the selected grid power limits mode. |
| Always treat the grid export power limit as instantaneous | False | Keeps the export limit instantaneous, regardless of the selected grid power limits mode. |

<ClickableImage src="/img/generic/settings/advanced-settings-grid-limits-en.png" alt="The grid limits section of the advanced settings" maxWidth="750px" />

Below this section you find the **Grid power limit schedule**, see [below](#grid-power-limit-schedule).

## Battery control

| Setting | Default | Explanation |
|:--|:--|:--|
| Allow putting batteries in standby at low power setpoints | False | Lets the <BrandName /> <ControllerName /> put a battery in standby when its setpoint is very small. Using an inverter at very low power is inefficient, so this generally saves costs. Do not enable it if it is important that the grid power is always controlled to exactly zero, even when the grid power is very low. |
| Storage cost optimization variability buffer size (%) | 10 | How big the self-consumption variability buffer is in cost optimization. This buffer counteracts the effect of weather and consumption variability within a single hour, to prevent fluctuations between import and export. See also [Battery cost optimization](/Controller/Configuration%20from%20A%20to%20Z/8-local-control-modes/extra-battery-cost-optimization/). |
| Enable phase overcurrent compensation with single phase batteries on three phase grids | False | Also uses single phase batteries to compensate an overcurrent on a three phase grid. Caution: the <BrandName /> <ControllerName /> looks at the heaviest loaded phase for protection, so the battery could be triggered to discharge for an overcurrent that is not on its own phase. This is not harmful, but may be undesirable. |
| Enable weekly battery maintenance charge | False | Fully charges all batteries once per week, on the given day and hour, to balance the battery cells. See [Battery maintenance charge](/Controller/Configuration%20from%20A%20to%20Z/11-Extra-Information/battery-maintenance-charge/). |
| Weekday of battery maintenance charge | Monday | The day of the maintenance charge. |
| Final hour of battery maintenance charge | 04:00 | The hour at which the maintenance charge ends. The battery is charged some hours before this and then holds its charge. |

Below this section you find the **Storage state of charge planning** and, on Swiss sites, the **Capacity tariff schedule**, see [below](#storage-state-of-charge-planning).

## EV control

| Setting | Default | Explanation |
|:--|:--|:--|
| Enable grid support from local storage for EV Charging | False | Actively uses the local batteries to support the grid connection, so that more EV charging is allowed than the grid on its own could provide. This forces the batteries to peak shaving, regardless of their working mode. **This setting is not compatible with external signals: if there are external signals, it is ignored.** |
| Maximum battery discharge margin for EV ramp up (kW) | Unlimited | With grid support enabled, the battery is pre-emptively discharged to keep room between the actual grid power and the grid limits, so that charging EVs can keep ramping up their current. This setting caps how much battery discharge power may be reserved as ramp-up room. Set a value if the battery discharges more than desired while EVs are ramping up. |
| EV suspension signal debounce time (seconds) | 180 | How long the <BrandName /> <ControllerName /> must persistently want to suspend an EV before the EV is actually suspended. Lowering this makes the EV stop faster when the conditions (for example self-consumption) no longer favour charging, but setting it too low can make the EV switch on and off frequently, which may harm the charger and the EV battery management system. |
| EV resume signal debounce time (seconds) | 120 | How long the <BrandName /> <ControllerName /> must persistently want to resume an EV before charging is actually resumed. The same warning applies. |

## PV control

| Setting | Default | Explanation |
|:--|:--|:--|
| Uncurtailment fraction | 0.015 | To find out how much additional PV production can be allowed, a little import or export from the grid must be allowed, so that a curtailed inverter can safely ramp up and the <BrandName /> <ControllerName /> can check whether more production is possible. This fraction of the total PV inverter power (or the total battery inverter power, whichever is the largest) is used for that small offset. 1.5% is the recommended value; lower values may cause the inverter not to switch on. |
| Curtail detector: on/off | True | Automatically detects and reports solar curtailment (the "curtailment" shown in the app and portal). |
| Curtail detector: detection tolerance (%) | 10 | If the current PV power is within this tolerance of the setpoint, the production is considered curtailed. |
| Curtail detector: measurement aggregation in seconds | 300 | The interval over which the power measurements are aggregated for the curtailment detector. |
| Curtail detector: ramp-up time (seconds) | 30 | How long an inverter is considered to be ramping up after a curtailment event. |

## Control signal when a device is not controlled

When the working mode of a device type is set to "Don't control" (or a device is excluded from control by the [Monitoring only](/Controller/Configuration%20from%20A%20to%20Z/8-local-control-modes/special-local-control-modes/monitoring-only/) mode), the <BrandName /> <ControllerName /> by default still sends a few commands to the device, so that it works again as it would without the <BrandName /> <ControllerName />. Per device category you can choose between "Reset the device to its default behaviour" (the default) and "Never send a reset command":

| Device category | Default reset behaviour | When "Never send a reset command" is selected |
|:--|:--|:--|
| Batteries of which the control mode is "don't control" | Nothing is imposed on the battery anymore; it runs on its own settings. | The battery keeps doing whatever the <BrandName /> <ControllerName /> last commanded, until it is controlled again. |
| EV chargers and controllable boilers of which the control mode is "don't control" | Charging at full power is allowed again. | The device keeps the last charge current that the <BrandName /> <ControllerName /> sent to it. |
| PV of which the control mode is "don't control" | Producing at full power is allowed again. | The inverter keeps the last production limit that the <BrandName /> <ControllerName /> sent to it. |
| Other loads of which the control mode is "don't control" | The heat pump, boiler or on/off load is put back in its own control mode. | The load stays in the last mode that the <BrandName /> <ControllerName /> sent to it. |

> [!CAUTION]
> Only select "Never send a reset command" for installations where the devices may never be written to as long as they are not controlled. With that option, a device that was curtailed or limited at the moment its control was switched off stays curtailed or limited.

<ClickableImage src="/img/generic/settings/advanced-settings-uncontrolled-reset-en.png" alt="The reset command settings per device category" maxWidth="750px" />

## Reactive power control

| Setting | Default | Explanation |
|:--|:--|:--|
| Enable reactive power control | False | Enables reactive power control on the site level. The settings below only appear when it is enabled. |
| Allowed grid import reactive power (kVAr) | 100 | The maximum reactive power that may be imported from the grid. |
| Allowed grid export reactive power (kVAr) | 100 | The maximum reactive power that may be exported to the grid. |
| Start generating reactive power above (kVAr) | 0 | Devices that can control their reactive power limit the reactive import power of the site to this value. |
| Stop generating reactive power below (kVAr) | 0 | Devices stop generating reactive power when the reactive power of the site drops below this value. |
| Stop consuming reactive power above (kVAr) | 0 | Devices stop consuming reactive power when the reactive power of the site rises above this value. |
| Start consuming reactive power below (kVAr) | 0 | Devices limit the reactive export power of the site to this value. |

See [Reactive power control](/Controller/Configuration%20from%20A%20to%20Z/8-local-control-modes/extra-reactive-power-control/) for the full explanation.

## Grid power limit schedule

Here you can specify rules for when the grid import and export power limits should be different from the defaults of the main settings page. Every rule has a day of week (a single day, Monday - Friday, Saturday - Sunday or Monday - Sunday), a month (all year round, a single month or a quarter), a start time, an end time, an export limit and an import limit in kW. Rules may not overlap. See also [Grid limits](/Controller/Configuration%20from%20A%20to%20Z/3-grid-limits/#grid-power-limit-schedule).

## Storage state of charge planning

Here you can specify rules for when the storage devices should have a certain minimum state of charge. Every rule has a day of week, an hour, a minute and the minimum state of charge (%) at that time. The rules apply to all storage devices and all working modes. See [Battery charging schedule](/Controller/Configuration%20from%20A%20to%20Z/8-local-control-modes/extra-battery-charging-schedule/) for the things to keep in mind.

> [!NOTE]
> The state of charge planning is disabled while the capacity tariff schedule is enabled. The two are incompatible.

<ClickableImage src="/img/generic/settings/soc-planning-en.png" alt="The storage state of charge planning" maxWidth="750px" />

## Capacity tariff schedule (Switzerland)

> [!NOTE]
> This section is only shown on sites whose address is in **Switzerland**.

With the capacity tariff schedule, the batteries switch to peak shaving during the periods in which a capacity tariff applies, so that the grid peaks are shaved during those periods. Outside those periods the batteries follow their normal working mode.

The section shows a checkbox "Enable capacity tariff schedule" and a summary of the current configuration: the critical reserve, whether the critical reserve is charged before each capacity tariff period, and the number of configured rules. When the schedule is disabled, the rules are kept but not applied. Enabling the schedule replaces the storage state of charge planning.

The configuration itself is done in the **capacity tariff schedule wizard** (button "Open capacity tariff wizard"):

1. **When is the capacity tariff active?** Add one or more weekly windows, each with its days of week, start time and end time. Windows may not overlap.
2. **Peak shaving battery reserve**: the critical reserve, the percentage of the total battery capacity that is reserved exclusively for peak shaving. This works like the critical reserve of the [peak shaving plus](/Controller/Configuration%20from%20A%20to%20Z/8-local-control-modes/extra-peak-shaving-plus/) mode.
3. **Minimum state of charge rule**: whether the storage must be charged to the top of the critical reserve before each capacity tariff period starts, so that the reserve is full from the start of the period.
4. **Peak shaving thresholds**: the four peak shaving thresholds (start discharging above, stop discharging below, stop charging above, start charging below) in kW, either the same all year round, one set per quarter or one set per month.

Finishing the wizard with "Save and enable capacity tariff schedule" enables the schedule and replaces any existing capacity tariff rules.


## Advanced self-consumption settings

By default, the self-consumption strategy uses the main grid meter to determine the power that is imported from or exported to the grid. Here you can select another energy meter as the reference for self-consumption instead. The system will then be controlled to show zero on this meter. This is only possible when more than one energy meter is configured. See [Self consumption on another meter than the grid meter](/Controller/Configuration%20from%20A%20to%20Z/8-local-control-modes/extra-self-consumption-on-another-meter/).

## Retired settings

The following settings are being phased out. They are only shown on sites that still have them switched on, so that those sites can switch them off. Once switched off, they disappear from the page and cannot be switched on again.

| Setting | Explanation |
|:--|:--|
| Disable scheduler | Nothing is controlled on the site anymore: the <BrandName /> <ControllerName /> still reads out its devices and sends their data to the server, but no longer sends setpoints, and the grid limits and peak shaving are no longer enforced. Rather set the working mode of the device types to "Don't control", or use the [Monitoring only](/Controller/Configuration%20from%20A%20to%20Z/8-local-control-modes/special-local-control-modes/monitoring-only/) mode for specific devices: the site protections then keep working for the devices that are still controlled. |
| Enable true three phase scheduler working mode (experimental) | Switches the control loop to a per-phase working mode, which requires that the phases of every device are mapped correctly to the phases of the main energy meter. The control system handles phase imbalance natively better than this experimental setting; it is kept working on the sites that already use it but gets no further development. See [Phase imbalance correction](/Controller/Configuration%20from%20A%20to%20Z/11-Extra-Information/phase-imbalance/). |
| Also transmit rarely used live data to server | Sends all one-second readings to the server database instead of only the power data. This increases the database load and may become subject to additional licensing. |

## Bulk settings

On a cloud <BrandName /> <ControllerName /> that manages several sites, the advanced site settings can be applied to a selection of sites at once from the bulk settings page. Only the settings that allow bulk editing are shown there.


# Backup


import { BrandName, ControllerName, CustomerName, InsightsName, InsightsUrl } from '@site/src/components/customFields';
import Details from '@theme/Details';
import ClickableImage from '@site/src/components/ClickableImage';

# Backup

## Making a backup
You can make a backup of the settings of the <BrandName /> <ControllerName /> through the commissioning interface, from the settings tab.
Scroll down to "Backup settings", and click "Backup".

<ClickableImage src="/img/generic/backup-make-en.png" alt="Image 1" maxWidth="350px" />

## Restoring a backup
You can restore a backup of the settings of the <BrandName /> <ControllerName /> through the commissioning interface, from the settings tab.
Scroll down to "Restore backup", upload your backup file, and click "Restore".

<ClickableImage src="/img/generic/backup-restore-en.png" alt="Image 1" maxWidth="350px" />


# Energy storage and EVs


You can configure per charging station socket whether EV charging on that socket may take energy from batteries or not.
To configure this, go to the "Devices" tab, and edit the settings of the charging station.

> [!NOTE]
> The default setting is that energy from batteries can be used to charge EVs.

# Battery maintenance charge


You can enable a weekly battery maintenance charge in the Advanced Settings.
Go to 'Settings' --> 'Advanced Settings' and enable 'Weekly battery maintenance charge'. You can change the day and hour on which the maintenance charge happens.

> [!TIP]
> The maintenance charge makes sure that the battery cells are internally balanced.

> [!WARNING]
> - The maintenance charge requires that a local control mode is set for storage. If set to "Don't control", the maintenance charge will not be executed.
> - The maintenance charge only works with local control modes, so it may not be executed if there is an external signal active.

# Data Saver


import { BrandName, ControllerName } from '@site/src/components/customFields';

# Data Saver

Data Saver reduces the amount of data that a <BrandName /> <ControllerName /> sends to the cloud. It is intended for installations with a metered mobile connection, a limited data bundle or a low-bandwidth internet connection.

> [!IMPORTANT]
> Data Saver does **not** stop local measurements or local energy management. The controller continues to communicate with devices, store measurements locally and run its control strategy. Only the timing and detail of cloud communication change.

## What changes when Data Saver is on

| Function | Data Saver off | Data Saver on |
|:--|:--|:--|
| Measurements sent to the cloud | New readings are forwarded without intentional buffering. | Readings are combined into one-minute summaries. |
| Cloud upload | Sent when new data is available. | Grouped and uploaded approximately every 15 minutes. |
| Live values in the app | Available with the normal connection delay. | Not live; values and charts update in batches. |
| Remote settings | A physical controller normally checks for changes about once a minute. | The controller normally checks for changes once per hour. |
| Detailed future control plan | Sent to the cloud periodically. | Not uploaded; the local plan still runs on the controller. |
| Local device control and safety limits | Unchanged. | Unchanged. |
| Local measurement storage | Unchanged. | Unchanged. |

Cloud controllers normally check for remote setting changes every five minutes while Data Saver is off. Exact timing can vary slightly with processing and connection quality.

## From device reading to cloud chart

1. The controller reads the connected devices.
2. It stores the original measurements locally and uses them for local control.
3. With Data Saver on, it builds a summary for each completed one-minute interval.
4. Completed summaries wait in an upload buffer.
5. Approximately every 15 minutes, the buffer is sent to the cloud and the app charts catch up.

An incomplete minute is held until that interval is complete. This prevents a partial interval from appearing as a complete one in the cloud.

### How one-minute summaries are calculated

- Continuous numeric readings, such as power, are represented by a time-weighted average.
- Incremental values, such as an energy change during the interval, are added together.
- States and text values keep the value that represented most of the interval.

This keeps totals and trends useful while sending considerably fewer individual readings.

## What continues locally

The following functions do not depend on immediate cloud upload and continue while Data Saver is enabled:

- communication between the controller and locally connected devices;
- local measurements and local history on the controller;
- local control modes, schedules, grid limits and device priorities;
- local calculation and execution of the control plan.

The app can therefore look behind while the controller is still operating normally. Loss of live values in the app does not by itself mean that local control has stopped.

## When to use Data Saver

Enable it when:

- the controller uses a capped or metered mobile data plan;
- the internet connection is stable but has limited bandwidth;
- live cloud values and immediate remote configuration are not required.

Keep it off during:

- initial commissioning and live signal checks;
- troubleshooting with remote support;
- periods in which settings must be changed and verified quickly;
- applications that require near-real-time cloud visibility.

> [!CAUTION]
> Data Saver only reduces traffic between the controller and the <BrandName /> platform. Devices connected through a manufacturer portal, third-party API or another cloud service can generate separate network traffic that is not reduced by this setting.

## Enable or disable Data Saver

1. Open the commissioning interface.
2. Go to **Settings**.
3. Find **Network usage** and set **Data Saver** to **On** or **Off**.
4. Select **Save**.

The option is also shown in the initial setup wizard. After saving, the data-logging and planning services reload the selected communication settings automatically.

## Verify the result

With Data Saver on, allow at least 15 minutes for a new batch to appear in the app. A remote setting can take up to approximately one hour to reach the controller. If measurements or settings remain outdated beyond those intervals, check the internet connection and controller status.

Older installations can retain previously customised communication intervals. If the observed timing differs consistently from this page, ask your distributor or Eniris Support to review the controller configuration.

## Related pages

- [Data usage](./data-usage)
- [Network settings](./network-settings)
- [Advanced network settings](/Controller/network-configuration/)


# Data usage


import { BrandName, ControllerName, CustomerName, InsightsName, InsightsUrl } from '@site/src/components/customFields';
import Details from '@theme/Details';

# Data usage

## Minimum data bundle

If your <BrandName /> <ControllerName /> is connected to the Internet via a mobile network, you must provide at least 5GB of data usage per month, and if you connect more than 5 devices to the <BrandName /> <ControllerName />, you must additionally provide 1GB/device.

> [!WARNING]
> If you use external control signals (e.g. for curtailment, imbalance market connections, ... etc.), it is highly recommended to use a fixed Internet connection or an unlimited mobile data plan.
>
> DISCLAIMER: The manufacturer of the <BrandName /> <ControllerName /> cannot be held responsible for mobile data usage outside your bundle.

## Data Saver

Data Saver reduces controller-to-cloud traffic by summarising readings and uploading them in batches. Local measurement storage and local control continue, but app data is no longer live and remote settings are synchronised less frequently.

See [Data Saver](/Controller/Configuration%20from%20A%20to%20Z/11-Extra-Information/data-saver/) for the exact timings, the effect on cloud planning and guidance on when to enable it.


# DC-Linking Inverters and Batteries


import { BrandName, ControllerName, CustomerName, InsightsName, InsightsUrl } from '@site/src/components/customFields';
import Details from '@theme/Details';
import ClickableImage from '@site/src/components/ClickableImage';

# DC-Linking Inverters and Batteries, and Battery Management Systems (BMS)

## Known cases
In a limited number of cases the <BrandName /> <ControllerName /> has to communicate separately with the battery (or BMS) and the inverter that controls the battery.
Known cases where this happens:
- Some inverters of Sinexcel and EnjoyPower in combination with a Poweroad BMS: The inverters don't have the state of charge of the battery.
- Multiple Kaco inverters that are connected to a single DC battery: The individual inverters don't have a the correct battery power.


## How to proceed
1. Add the inverter(s), BMS and/or battery separately to the <BrandName /> <ControllerName /> as standalone devices.
2. Go to the groups page.
3. At the bottom of the groups page, if there are dc-linkable inverters, batteries and/or bms systems, they will appear here. You can link the battery or BMS to (all) the inverters it belongs to.
<ClickableImage src="/img/generic/dc-linking.png" alt="AppOverview" maxWidth="100%" />


# Device settings


import { BrandName, ControllerName, CustomerName, InsightsName, InsightsUrl } from '@site/src/components/customFields';
import Details from '@theme/Details';
import ClickableImage from '@site/src/components/ClickableImage';

# Device settings

Every device has its own settings, which are changed from the "Devices" tab of the commissioning interface. This page is a reference of all the settings per device type.

## Where to find the device settings

On the "Devices" tab, every known device has a row with its name, manufacturer, connection, measurements and control status. The "Actions" column of a device has a button per action:

- **Change device name**: rename the device.
- **Change settings**: the settings described on this page (nominal power, priority, battery capacity, ...). The <BrandName /> <ControllerName /> shows a warning icon on a device whose settings are not complete yet: check the settings of such a device.
- **Change driver inputs**: the inputs that were asked when the device was added (for example an IP address, a serial number or an API key), for the devices whose driver allows changing them afterwards. The change is applied to the live device, no restart is needed.
- **Test / manual override**: send a specific setpoint to the device for a limited time, see [Testing and manual override](/Controller/Configuration%20from%20A%20to%20Z/11-Extra-Information/testing-and-manual-override/). While a test runs, **Stop test / manual override** ends it.
- **Other actions**: device-specific actions that the driver offers, for example resetting an alarm or synchronising the clock of the device. Only shown for devices whose driver supports such actions. Choose the action and click "Execute action"; while the action is executed the interface may seem to hang until the communication channel to the device is free.
- **Remove device**: deletes the device. Deleted devices are also removed from the external signals they were part of.

<ClickableImage src="/img/generic/settings/devices-actions-en.png" alt="The action buttons of a device on the Devices tab" maxWidth="650px" />

> [!NOTE]
> The save button of the settings page is at the bottom of the page. When a device is part of a group of devices (for example a hybrid inverter with its battery and PV inputs), the settings of all the devices of the group are shown on one page.

## Settings that many devices have

| Setting | Explanation |
|:--|:--|
| Name | The name of the device, as shown in the commissioning interface, the app and the portal. |
| Nominal power (kW) | The nominal power of the device. For an inverter this is the AC power it can deliver, for a load the power it draws when it is on. The <BrandName /> <ControllerName /> uses it to plan the device, so a wrong nominal power leads to wrong control. Batteries, EV chargers, heat pumps, boilers, on/off loads and PV inputs all have it. |
| Priority | Lowest, Low, Normal (default), High or Highest. Indicates whether the device has a higher or lower priority when it is scheduled. Available on batteries, EV chargers, heat pumps, boilers and on/off loads. See [Device priorities](/Controller/Configuration%20from%20A%20to%20Z/8-local-control-modes/extra-device-priorities/). |
| Is the device single or three phase? (How is the device wired?) | How the device is physically wired. This is a wiring specification that the <BrandName /> <ControllerName /> needs for accurate power and current calculations: setting "single phase" for a device that is wired for three phases does not force it to use one phase, but disrupts control and monitoring. |
| Operating voltage | "Same as the main circuit breaker" (default) or "Other". Choose "Other" for a device that operates or measures at another voltage level than the grid connection point, for example a device behind a transformer. With "Other", you also enter the **Nominal voltage type** (phase-neutral or phase-phase) and the **Nominal voltage (V)**. |
| Is the device connected to the neutral wire? and Device phase L1/L2/L3: which is the corresponding phase of the main energy meter? | Only shown when the retired true three phase working mode is enabled (see [Advanced settings](/Controller/Configuration%20from%20A%20to%20Z/11-Extra-Information/advanced-settings/#retired-settings)). Maps the terminals of the device to the phases of the main energy meter. You must verify this with a multimeter or similar. |

<ClickableImage src="/img/generic/settings/device-settings-phase-en.png" alt="The phase and voltage settings of a device" maxWidth="750px" />

## Energy meters

| Setting | Explanation |
|:--|:--|
| What does the energy meter mainly measure? | Grid connection point, Energy production, EV charging poles, Storage, Consumption loads, Heat pump or Other. This lets the <BrandName /> <ControllerName /> categorize the measurements: a meter that measures energy production shows up as PV production in the dashboard and the app. |
| Meter is connected forward / in reverse | Whether consumption is counted as positive power by the meter (forward) or production is counted as positive (in reverse). See [Reverse energy meter readings](/Controller/Configuration%20from%20A%20to%20Z/11-Extra-Information/reversing-energy-meter/). |
| Enable custom scale factors | Yes or No. With Yes, the power, current, voltage, energy and frequency scale factors appear. The measurements are multiplied by these factors. See [Rescale energy meter readings](/Controller/Configuration%20from%20A%20to%20Z/11-Extra-Information/rescale-energy-meter-values/). |

<ClickableImage src="/img/generic/settings/device-settings-energy-meter-en.png" alt="The settings of an energy meter" maxWidth="750px" />

## Batteries

| Setting | Default | Explanation |
|:--|:--|:--|
| Nominal power (kW) | read from the device where possible | The power at which the battery can charge and discharge. |
| Battery capacity (kWh) | read from the device where possible | The usable capacity of the battery. |
| Minimum battery state of charge (%) | 20 | The state of charge to which the battery may be discharged. 20% is recommended for lithium-ion batteries, 50% for lead-acid batteries. The <BrandName /> <ControllerName /> stops discharging 1% above this value and charges the battery a little when it drops below it, see [Troubleshooting: control issues](/Controller/Troubleshooting/control-malfunctioning/#batteries). |
| Maximum battery state of charge (%) | 100 | The state of charge to which the battery may be charged. |
| Maximum battery charge power (kW) | Unlimited | Caps the charge power. Left empty, the charge power is at most the nominal power. |
| Maximum battery discharge power (kW) | Unlimited | Caps the discharge power. Left empty, the discharge power is at most the nominal power. |
| Roundtrip efficiency (%) | 80 | The roundtrip efficiency of the battery. Together with the wear cost, this determines the cost of using the battery in cost optimization. See [Accounting for the battery wear and efficiency](/Controller/Configuration%20from%20A%20to%20Z/8-local-control-modes/extra-wear-battery/). |
| Priority | Normal | See above. |

<ClickableImage src="/img/generic/settings/device-settings-battery-en.png" alt="The settings of a battery" maxWidth="750px" />

## Hybrid inverters and PV

- A **hybrid inverter** has a nominal power (kW). Its battery and its PV inputs are separate devices with their own settings.
- A **solar inverter**, **PV input** or **solar optimizer** has a nominal power (kW) and the question "Are there PV panels connected to this input?". Answer "No" for the inputs of an inverter that are not used, so that they are not counted as production.
- A **solar plant** or **solar installation** (a group of inverters) has a nominal power (kW).

## EV chargers and connectors

An EV charger has one or more connectors (sockets). The charger itself has a nominal power and the setting "Allow suspending charging"; every connector has its own settings.

| Setting | Default | Explanation |
|:--|:--|:--|
| Nominal power (kW) | read from the device where possible | The maximum charge power of the charger or the connector. |
| Allow suspending charging | Yes | With Yes, charging may be fully paused to wait for the most cost-effective or green energy windows. Some EVs do not support a full suspension and need a constant minimum current: if your car shows an error or fails to start charging, set this to No. |
| Allow using battery storage to charge EVs | Yes | Whether battery storage may be used to charge EVs on this connector. Only applied when the storage is in self-consumption or cost optimization; when the storage is in peak shaving or follows a setpoint, it is always used if needed. See [Energy storage and EVs](/Controller/Configuration%20from%20A%20to%20Z/11-Extra-Information/battery-and-ev/). |
| Maximum capacity of connected EV (kWh) | 100 | The battery capacity of the largest EV that charges on this connector, used for the planning. |
| Discover the EV capabilities automatically upon plug-in | Yes | When an EV is plugged in, the <BrandName /> <ControllerName /> gives it the maximum allowed current for a few moments to discover how much current it draws and how many phases it uses. This is required for a good planning. Leave it on if different EVs charge on this connector. |
| Maximum current the EV can draw (A) | 32 | The maximum current per phase of the EV. Only shown and used when the automatic discovery is disabled. |
| Number of phases the EV can use | Three phases | Three phases, two phases or single phase. Only shown and used when the automatic discovery is disabled. |
| Enable Smart Phase Switching (Experimental) | No | Lets the charger switch between one and three phases to charge on lower solar output without importing from the grid. Only shown for chargers that support phase switching. Not all cars support this: disable it if your car goes into fault. |
| Priority | Normal | See above. |

<ClickableImage src="/img/generic/settings/device-settings-ev-connector-en.png" alt="The settings of an EV charger connector" maxWidth="750px" />

## Heat pumps

| Setting | Default | Explanation |
|:--|:--|:--|
| Nominal power (kW) | | The electrical power of the heat pump. |
| Default heatpump mode | Normal operation mode | In **Normal operation mode** the heat pump works on its own and is only boosted or blocked when that is beneficial. In **Blocking mode** it is blocked by default and only released when beneficial; in **Boosting mode** it is boosted by default and only released when beneficial. A mode that the heat pump does not support falls back to normal operation. Caution: the <BrandName /> <ControllerName /> is not a thermostat, so the blocking and boosting modes can influence the comfort significantly. |
| Minimum and maximum time in normal operation mode (minutes) | 180 | How long the heat pump stays at least and at most in normal operation when it is not optimal to block or boost it. |
| Minimum and maximum block time (minutes) | 180 | How long the heat pump is at least and at most blocked when it is optimal to block it. |
| Minimum wait time after blocking (minutes) | 120 | How long the heat pump stays in normal operation after it was blocked, so that the temperature of the building does not drop too much. |
| Minimum and maximum boost time (minutes) | 180 | How long the heat pump is at least and at most boosted when it is optimal to boost it. |
| Minimum wait time after boosting (minutes) | 120 | How long the heat pump stays in normal operation after it was boosted. |
| Priority | Normal | See above. |

The block times are only shown for heat pumps that can be blocked, and the boost times only for heat pumps that can be boosted.

See [Heat pumps, boilers and on/off devices](/Controller/Configuration%20from%20A%20to%20Z/8-local-control-modes/complete-explanation/#heat-pumps-boilers-and-onoff-devices) for what blocking and boosting mean.

<ClickableImage src="/img/generic/settings/device-settings-heat-pump-en.png" alt="The settings of a heat pump" maxWidth="750px" />

## Boilers

A boiler and a controllable boiler (a boiler whose power can be modulated) have a nominal power (kW) and a priority.

## Relays, switches and other on/off loads

| Setting | Default | Explanation |
|:--|:--|:--|
| What is the use case? | | **Switching a device or circuit**: the relay switches a load that the <BrandName /> <ControllerName /> plans like any other on/off load. **Direct passthrough of an external control signal**: the relay follows an external signal directly, without the local control modes, limits or timing constraints. See [Direct relay or switch control](/Controller/Configuration%20from%20A%20to%20Z/11-Extra-Information/direct-relay-control/). |
| Nominal power (kW) | 100 | The power of the load behind the relay. |
| Default device state | | **Switched on**: the device is on by default and is only switched off when it is optimal to block its consumption or when an external signal says so (for example a fridge that may be off for an hour, or a boiler that may be off for 8 hours). **Switched off**: the device is off by default and is only switched on when it is optimal to boost consumption or when an external signal says so (for example pool heating). Caution: do not use "Switched off" for devices whose comfort you care about, because they can stay off for extended periods. In passthrough mode this is the fallback state when no external signal is present. |
| Minimum and maximum switch off time (minutes) | 3 and 120 | How long the device is at least and at most switched off when it is optimal to reduce consumption. |
| Minimum wait time after switching back on (minutes) | 120 | How long the device stays on after it was switched back on, for example to make sure a boiler heats some water. |
| Minimum and maximum switch on time (minutes) | 3 and 120 | How long the device is at least and at most switched on when it is optimal to increase consumption. |
| Minimum wait time after switching back off (minutes) | 120 | How long the device stays off after it was switched back off. |
| Priority | Normal | See above. |

Only the timings that apply to the selected default device state are shown: the switch on times for a relay that is switched off by default, and the switch off times for a relay that is switched on by default.

> [!NOTE]
> The timing settings are ignored when the relay is directly controlled by an external signal or by the [peak shaving relay cascade](/Controller/Configuration%20from%20A%20to%20Z/8-local-control-modes/special-local-control-modes/peakshaving-relay-cascade/). They are also ignored when the grid limits are exceeded.

<ClickableImage src="/img/generic/settings/device-settings-switched-load-en.png" alt="The settings of a relay" maxWidth="750px" />

## Groups (switchboards)

A group created on the [Groups tab](/Controller/Configuration%20from%20A%20to%20Z/7-grouping-devices/) has two settings:

| Setting | Default | Explanation |
|:--|:--|:--|
| Circuit breaker current (A) | Unlimited | The current limit of the circuit breaker of the switchboard. The <BrandName /> <ControllerName /> keeps the current of the devices in the group below it. |
| Protected phases | L1, L2, L3 and N | The phases that the circuit breaker protects, for example "L1 and N" for a single phase sub-board. |


# Direct relay or switch control


import { BrandName, ControllerName, CustomerName, InsightsName, InsightsUrl } from '@site/src/components/customFields';
import Details from '@theme/Details';
import ClickableImage from '@site/src/components/ClickableImage';

# Direct control of relays or switches
It is possible to directly control relays or switches [through MQTT](/Controller/External%20Signals/MQTT/eniris-mqtt/). You can use this to implement custom logic regarding the relays.

## Modes: Device switching mode and external signal passthrough mode
Each relay or switch can be configured to operate in device switching mode or external signal passthrough mode from the device settings of the relay or switch.

### Device switching mode
When the relay or switch is in 'device switching mode', the <BrandName /> <ControllerName /> will plan the relay as a load with a certain power that can be switch on and off. The <BrandName /> <ControllerName /> will take power limits into account, but timing constraints are ignored when the relay is directly controlled through an external signal (they are taken into account only in local control without an external signal).

### External signal passthrough mode
When the relay is in 'external signal passthrough mode', the <BrandName /> <ControllerName /> will directly pass through the external control signals. **No validation checks for limits or timing constraints are applied.** This mode is solely intended for allowing to connect the relay or switch to an external third party device for further processing there, e.g. signaling a certain state. In absense of an external control signal, the default device state is applied.

<ClickableImage src="/img/generic/relay-passthrough.png" alt="Image 1" maxWidth="850px" />

# Email alarms


import { BrandName, ControllerName, CustomerName, InsightsName, InsightsUrl } from '@site/src/components/customFields';
import Details from '@theme/Details';
import ClickableImage from '@site/src/components/ClickableImage';

# Email alarms

The <BrandName /> <ControllerName /> can send an email when it repeatedly detects a problem on the site. An alarm is only sent when the issue persists over time, not for one-off events, so that a short communication hiccup does not trigger a mail.

## Configuring the email alarms

Go to the 'Settings' tab of the commissioning interface and scroll to the section "Email alarms".

<ClickableImage src="/img/generic/settings/email-alarms-en.png" alt="The email alarms section of the settings page" maxWidth="550px" />

### Which alarms to send

| Alarm | When it is sent |
|:--|:--|
| Device communication malfunction (missing measurements) | A device repeatedly does not answer, so its measurements are missing. See also [Troubleshooting: device communication](/Controller/Troubleshooting/device-communication/). |
| Device not following the power setpoint or limit | A controlled device persistently delivers another power than the setpoint or the limit the <BrandName /> <ControllerName /> sends it. See also [Troubleshooting: control issues](/Controller/Troubleshooting/control-malfunctioning/). |
| PV is not producing energy | A PV installation does not produce during the day, while production is expected. |
| Issues with external signals (if available for the external signal) | An external signal reports a problem, for example a lost connection to the provider. Only for the signals that report their status. |

### Maximum alarm frequency

The maximum frequency applies per alarm type and per site: at most once per hour, once per day or once per week. Once an alarm of a type has been sent, the same type is not sent again until this time has passed, even if the problem persists.

### Recipients

Up to four email addresses can receive the alarms. The plus button adds a row, the minus button removes one.

### Devices to exclude from alarms

Devices that are known to be unreliable, or that are intentionally switched off for a while, can be excluded from the alarms. Select the device from the dropdown (up to 20 devices); excluded devices do not trigger the device communication, setpoint and production alarms.

Click "Save" to store the configuration.


# Energy Costs

# Energy Costs

## Dynamic Energy Tariff

A dynamic energy tariff follows market prices (EPEX Spot), where prices evolve hourly and vary daily.

At certain times of the day, prices are lower than at others. By setting the control mode to *Minimize Costs*, connected devices can be managed to optimize consumption based on cost efficiency.

Energy prices serve as the foundation for all cost optimization efforts (control mode: *Minimize Costs*). To ensure proper functionality, it is essential to enter the price parameters accurately.

In most cases, the formula used to determine the electricity price for consumption is as follows:

```
eSpot (€/kWh) × EPEX Spot Consumption Scaling Factor + Energy Consumption Price (€/kWh) + Network Consumption Costs (€/kWh)
```

Where:
 - eSpot: The hourly rate on the Day-Ahead EPEX SPOT Belgium market, expressed in €/kWh.
 - Scaling Factor and Energy Price (surcharge): These depend on the specific energy contract.
 - Network Consumption Costs: These are determined by the distribution network operator (DNO) and vary by region.

These price parameters can be configured in the app under *Settings* > *Energy Cost Settings*.
 - Select *Dynamic Tariff (BE, NL, D)*.
 - Enter the *Scaling Factor for EPEX SPOT Consumption*, representing the adjustment relative to the EPEX Spot prices.
 - Specify the *Energy Price Surcharge* for Consumption in €/kWh.
 - Input the applicable *Network Costs* for Consumption per kWh, in €/kWh.

### Examples

 - **Engie Dynamic**

    |  | Before December 2024 |
    |--|--|
    | Price Formula for Consumption₁ | 1 × EPEX DA + 11.02 €/MWh |
    | Price Formula for Injection₂ | 1 × EPEX DA − 13.05 €/MWh |

    - *Scaling Factor EPEX SPOT Consumption*: 1.06 (including 6% VAT).
    - *Energy Prices Consumption*: 0,01102 + 0,0006612 (6% VAT) = 0,0117 €/kWh (incl. 6% VAT)
    - *Network Costs Consumption*: €0.1209/kWh (incl. 6% VAT).
        - *Energy Contribution*: €0.0020417/kWh (0.20417 €cent/kWh).
        - *Federal Excise Duty*: €0.0503288/kWh (5.03288 €cent/kWh).
        - *Green Energy and CHP Costs*: €0.01582/kWh (1.582 €cent/kWh).
        - *Network Costs (distribution and transport)*: €0.0527163/kWh (5.27163 €cent/kWh).
    - *Scaling Factor EPEX SPOT Injection*: 1.00
    - *Energy Prices Injection*: -€0.01305/kWh
    - *Network Costs Injection*: €0.00/kWh

 - **Ecopower Dynamische Burgerstroom**

    |  | Before December 2024 |
    |--|--|
    | Price Formula for Consumption₁ | 1.02 × EPEX DA + 4 €/MWh |
    | Price Formula for Injection₂ | 0.98 × EPEX DA − 15 €/MWh |

    - *Scaling Factor EPEX SPOT Consumption*: 1.0812 (including 6% VAT).
    - *Energy Prices Consumption*: 0.00424 €/kWh (incl. 6% VAT)
    - *Network Costs Consumption*: €0.1209/kWh (incl. 6% VAT).
    - *Scaling Factor EPEX SPOT Injection*: 0.98
    - *Energy Prices Injection*: -€0.015/kWh
    - *Network Costs Injection*: €0.00/kWh

 >[!IMPORTANT]
> ₁ Excluding 21% VAT for businesses and 6% VAT for private individuals\
> ₂ Excluding 21% VAT for businesses, VAT is not applicable for private individuals





# 11 Extra Information


import { FolderOverview } from '@/components/FolderOverview';

# 11 Extra Information

<FolderOverview folder="Controller/Configuration from A to Z/11-Extra-Information" />


# Master/slave inverters


import { BrandName, ControllerName, CustomerName, InsightsName, InsightsUrl } from '@site/src/components/customFields';
import Details from '@theme/Details';
import ClickableImage from '@site/src/components/ClickableImage';

# Master/slave inverters

Some inverters can operate in parallel as a group, in which one inverter is the **master** and the others are its **slaves**. The master receives the setpoint of the whole group and distributes it over its slaves itself. The <BrandName /> <ControllerName /> then sends its commands only to the master, while it keeps reading out every inverter of the group individually.

Use this when the inverters are wired in parallel and the manufacturer requires or recommends that the group is steered through one of them. Only devices whose driver supports master/slave operation are offered on the groups page. Contact <CustomerName /> if your inverters are not offered.

## How the group is controlled

- The <BrandName /> <ControllerName /> plans the group as one device with the nominal power of all its members together, and sends the resulting setpoint to the master. The slaves receive no setpoint of their own: they are released, so that they follow their master.
- Every inverter is still read out on its own, so the app and the data pages keep showing the power, the energy and the state of charge of every inverter.
- A test on the [device test page](/Controller/Configuration%20from%20A%20to%20Z/11-Extra-Information/device-settings/) of a member of the group goes through the master: the other members are put on a neutral value during the test, and the value shown is the total of the group.
- The master and its slaves must be of the same device type (for example all hybrid inverters), and use the same driver or compatible variants of one driver (for example the Modbus RTU and the Modbus TCP variant of a driver).
- A device can be the slave of one master only, and a slave cannot be the master of another group. To move a slave to another master, remove it from its current configuration first.

## Mode

Some drivers support more than one way to operate the group. In that case, a "Mode" dropdown appears after the master is selected; when the driver supports a single mode, nothing has to be chosen.

| Mode | Behaviour |
|:--|:--|
| Total setpoint to the master | Every device is monitored on its own. The master receives the setpoint of the whole group and distributes it over its slaves. |
| Lumped through the master | The master monitors and controls its slaves on its own, and reports the total of the whole group. |
| Lumped monitoring, individual setpoints | The group is monitored through the master, but every device receives its own setpoint. |

## Adding a configuration

1. Go to the "Groups" tab of the commissioning interface and scroll to the section "Master/slave inverters" at the bottom of the page. It lists the current master/slave configurations.
2. Under "Add master/slave configuration", select the master device. The list of possible slaves is narrowed down to the devices that can be a slave of that master.
3. If a "Mode" dropdown is shown, choose the mode.
4. Tick the slave devices.
5. Click "Set configuration". The <BrandName /> <ControllerName /> restarts its control services, so it takes a moment before the group is controlled as such.

<ClickableImage src="/img/generic/settings/groups-master-slave-en.png" alt="The master/slave inverters section of the groups page" maxWidth="650px" />

Devices that cannot be added (for example because they are already the slave of another master) are skipped, and a message names them.

## Changing or removing a configuration

- To add a slave to an existing group, select the same master again, tick the extra slave(s) and click "Set configuration". The slaves that were already in the group stay in it.
- A slave is removed from its configuration with "Remove slave" in the table of current configurations. Removing the last slave removes the whole configuration, and the inverters are controlled individually again.
- A configuration whose master was removed from the <BrandName /> <ControllerName /> is shown with "missing device": remove its slaves to clean it up.

## Related

- [Grouping devices](/Controller/Configuration%20from%20A%20to%20Z/7-grouping-devices/): the groups page itself.
- [DC-Linking Inverters and Batteries](/Controller/Configuration%20from%20A%20to%20Z/11-Extra-Information/dc-linking/): linking a battery or battery management system to the inverter(s) it belongs to, also on the groups page.


# Network settings


import { BrandName, ControllerName, CustomerName, InsightsName, InsightsUrl } from '@site/src/components/customFields';
import Details from '@theme/Details';
import ClickableImage from '@site/src/components/ClickableImage';

# Network settings

The network related settings are on the 'Settings' tab of the commissioning interface. For the network requirements of the <BrandName /> <ControllerName /> (firewall, ports, VLAN), see [Advanced network settings](/Controller/network-configuration/).

## Network configuration

The section "Network configuration" configures the ethernet port(s) and, on models with a modem, the mobile network. What is shown depends on the model of the <BrandName /> <ControllerName />.

<ClickableImage src="/img/generic/settings/network-configuration-en.png" alt="The network configuration section of the settings page" maxWidth="550px" />

### Ethernet port 1

| Setting | Explanation |
|:--|:--|
| Port mode | **Internet port (WAN)**: the port connects the <BrandName /> <ControllerName /> to the network with the internet router; this is the default. **Separated network (LAN)**: only on models with a mobile network: the port serves a separate local network for the devices, while the internet comes in over the mobile network. The <BrandName /> <ControllerName /> then acts as DHCP server on that network. |
| Network mode | **DHCP client** (default): the router assigns the IP address. **Fixed IP**: you enter the IP address, netmask, gateway and DNS servers yourself. |
| IP Address, Netmask, Gateway, DNS Server 1 and 2 | Only with a fixed IP. Enter the address of the <BrandName /> <ControllerName />, the netmask of the network, the address of the router and the DNS servers (for example 1.1.1.1 and 8.8.8.8). |
| DHCP server start and end IP address | Only in LAN mode: the range of addresses that the <BrandName /> <ControllerName /> hands out to the devices on the separated network. |

### Ethernet port 2

On models with two ethernet ports, the second port can be **Bridged with ethernet port 1** (both ports are on the same network, so the devices can be connected to port 2 and share the network of port 1) or a **Separated network (LAN)** with its own IP configuration and DHCP server. The separated network is the usual choice for devices that must not be reachable from the rest of the network.

### Mobile network

On models with a modem, enter the **APN** of the SIM card as provided by the mobile operator.

### Current IP config

Below the form, the section "Current IP config" shows the IP address and netmask that each port actually has, or "Not connected". Click "Apply network configuration" to save the changes.

> [!WARNING]
> Write down the configuration you apply. If the <BrandName /> <ControllerName /> becomes unreachable after a change, see [Troubleshooting: access to the commissioning interface](/Controller/Troubleshooting/device-communication/#access-to-the-commissioning-interface). A [factory reset](/Controller/Configuration%20from%20A%20to%20Z/11-Extra-Information/reset/) puts the network configuration back to DHCP.

> [!TIP]
> Only configure a fixed IP address if you have no other choice. It is recommended to keep DHCP and to let your router always assign the same IP address to the <BrandName /> <ControllerName />. See [Fixed IP addresses](/Controller/network-configuration/#fixed-ip-addresses).

## Network usage and data saver

The section "Network usage" shows how many MiB were downloaded and uploaded in the last 30 days. This is useful for a <BrandName /> <ControllerName /> on a mobile data plan: the minimum recommended amount of data is 5 GB per month for less than five devices, plus 1 GB per additional device, and external control signals need considerably more.

The **Data Saver** reduces controller-to-cloud traffic by creating one-minute summaries and uploading them in batches. Local storage and local control continue, but the app no longer shows live readings and remotely changed settings are applied less frequently. Choose **On** or **Off** and select **Save**. See [Data Saver](/Controller/Configuration%20from%20A%20to%20Z/11-Extra-Information/data-saver/) for the full behaviour and timing, or [Data usage](/Controller/Configuration%20from%20A%20to%20Z/11-Extra-Information/data-usage/) for mobile data guidance.

The section also contains an **internet test** ("Do speed test"), which measures the download speed and the lowest, average and highest latency of the internet connection of the <BrandName /> <ControllerName />. Use it when the <BrandName /> <ControllerName /> is slow to react from the app or regularly shows as offline: see [Troubleshooting: network](/Controller/Troubleshooting/netwerkTroubelShooting/).

<ClickableImage src="/img/generic/settings/network-usage-data-saver-en.png" alt="The network usage section with the data saver" maxWidth="550px" />

## Remote service connection

The remote service connection allows diagnostic services, updates and remote support by your distributor. It is strongly recommended to keep it enabled.

| Setting | Explanation |
|:--|:--|
| Enable remote service connection | Enables or disables the connection. |
| Service port | The port over which the <BrandName /> <ControllerName /> makes the outgoing connection: the default port (1194), the secondary port (1192) or a custom port in the range 35000-40000. Change it only when the firewall of the site blocks the default port. |

Click "Apply change" to save. You may have to allow an outgoing TCP connection from the <BrandName /> <ControllerName /> over the selected port in the firewall of the internet router, see [Network ports for outbound connections](/Controller/network-configuration/#network-ports-for-outbound-connections).

<ClickableImage src="/img/generic/settings/remote-service-connection-en.png" alt="The remote service connection section of the settings page" maxWidth="550px" />


# Phase imbalance correction


import { BrandName, ControllerName, CustomerName, InsightsName, InsightsUrl } from '@site/src/components/customFields';
import Details from '@theme/Details';
import ClickableImage from '@site/src/components/ClickableImage';


The <BrandName /> <ControllerName /> looks at all the phases of the electric installation, and will adjust the setpoints of the controlled devices to avoid exceeding the current limits on any phase.

> [!TIP] 
> ### Solving imbalances
> If you experience a severe imbalance, it is strongly advised to physically distribute the loads on your installation over the phases as equally as possible. This is almost always the most energy-efficient and reliable method for solving imbalances.

> [!NOTE] 
> ### Symmetrical phase control
> Most devices do not allow controlling the current per phase they are connected to, but only symmetrically on all phases together (they draw the same current on all phases).
> The <BrandName /> <ControllerName /> does control all the phases of a device together for this reason. It does not control individual phases.

> [!WARNING] 
> ### Severe imbalances
> In rare cases, if the imbalance is too severe, it may be impossible to compensate it. One of the known cases is when correcting too much active current on one phase would lead to too much active current in the opposite direction on another phase (if there is import power on one phase and export power on another phase).

# Predictions


import { BrandName, ControllerName, CustomerName, InsightsName, InsightsUrl } from '@site/src/components/customFields';
import Details from '@theme/Details';
import ClickableImage from '@site/src/components/ClickableImage';


### What does the <BrandName /> <ControllerName /> predict?
The <BrandName /> <ControllerName /> uses machine learning to predict the grid power of the near future (12h to 36h ahead of time, based on the available weather and price data). The prediction is based on historical data, for a given time, weekday and solar irradiation from weather data.

> [!TIP] Why predict the grid power, and not the PV power and consumption power?
> Firstly, most control objectives care about what the final power at the grid is - because you get billed based on the energy you get from the grid - so this is also one of the most important parameters in the control algorithm.
> Secondly, the <BrandName /> <ControllerName /> almost always has real, measured values from the grid energy meter. This is not always true for PV (not all inverters might be read out) and very often not for the base load consumption (this is usually a calculated value from the grid power, after subtracting all the values measured from the devices the <BrandName /> <ControllerName /> communicates with). Predictions based on directly measured values are often more accurate.

### Frequently asked questions
<Details summary='How much time does the EMS have to gather data for before predictions can be made?'>
Typically, within one to two days, the EMS can already detect patterns in your grid power. After one to two weeks, the predictions should be reasonably accurate.
</Details>

<Details summary='Does the prediction algorithm take seasonal effects in account?'>
Yes, seasonal variations are accounted for. 
</Details>

<Details summary='Does the prediction algorithm take the orientation of PV panels into account?'>
Yes. Because the predicted grid power is affected by how much energy your PV installation actually produces (which is a function of both the solar irradiation and the orientation of the panels), the effect of the orientation of the panels is inherently included in the data the prediction is based on. As such, the orientation is accounted for.
</Details>

### Resetting the prediction data

The **Prediction data reset** action in the advanced settings erases the historical energy data used by the forecasting model. Use it only when the stored history is no longer representative, for example after a substantial change to the installation or its measurement topology.

After a reset, the controller must collect new measurements before its forecasts become reliable again. Initial patterns normally become visible after one or two days; allow one to two weeks for a more representative history.


# Priorities

You can use priorities to control the order in which devices are planned.

{/* TODO: Expand this section.*/}

See also [Full explanation of the local control modes](/Controller/Configuration%20from%20A%20to%20Z/8-local-control-modes/complete-explanation/)

# Reboot and automatic reboot


import { BrandName, ControllerName, CustomerName, InsightsName, InsightsUrl } from '@site/src/components/customFields';
import Details from '@theme/Details';
import ClickableImage from '@site/src/components/ClickableImage';

# Reboot and automatic reboot

## Rebooting the <BrandName /> <ControllerName />

Go to the 'Settings' tab of the commissioning interface, scroll to "Reboot" and click "Reboot". The <BrandName /> <ControllerName /> restarts; this takes a few minutes. The page shows the progress and returns to the login page when the <BrandName /> <ControllerName /> is back.

> [!NOTE]
> During the reboot, the devices are not read out and nothing is controlled. The devices fall back to their own behaviour. A reboot never changes the settings; use the [backup](/Controller/Configuration%20from%20A%20to%20Z/11-Extra-Information/backup/) and the [factory reset](/Controller/Configuration%20from%20A%20to%20Z/11-Extra-Information/reset/) for that.

## Automatic reboot period

The <BrandName /> <ControllerName /> can reboot itself periodically. This is not needed in a normal installation, but it can be a workaround for a device or a converter that stops answering after a number of days, or for a mobile network connection that hangs.

1. In the section "Automatic reboot period", tick "Reboot automatically".
2. Enter the number of days between two reboots.
3. Click "Save".

<ClickableImage src="/img/generic/settings/automatic-reboot-en.png" alt="The automatic reboot period section of the settings page" maxWidth="550px" />

> [!TIP]
> Rather solve the cause of the hanging device or connection: every reboot interrupts the control of the site for a few minutes.


# Rescale energy meter readings


import { BrandName, ControllerName, CustomerName, InsightsName, InsightsUrl } from '@site/src/components/customFields';
import Details from '@theme/Details';
import ClickableImage from '@site/src/components/ClickableImage';


For the <BrandName /> <ControllerName /> energy meters are pre-configured with the most common scaling factors.
However, if you have a different scaling factor, you can rescale the energy meter readings.

> [!WARNING]
> For stable functioning of the control system, it is important that the <BrandName /> <ControllerName /> knows the correct scaling factor of each energy meter.
## What are scaling factors?
Scaling factors are used to convert the raw data from the energy meter into meaningful values. For example, if an energy meter reports a value of 1000, and the scaling factor is set to 10, the actual value would be 100 watts (1000 / 10 = 100).
Manufacturers often provide energy meters with a default scaling factor, but this may not always match the actual setup or requirements of your system.
In other cases, the scaling factor is configured by the installer or user during the commissioning of the system and need to be adjusted in the <BrandName /> <ControllerName />.

## How to recognize wrong scaling?
We showcase a typical example of a scaling issue:

The installation below, is an installation in which we know \* by speaking with the customer \* that there is very little consumption.
This is not reflected on what we see in the app:
    <ClickableImage src="/img/generic/scaling-issues/0.jpg" alt="Image 1" maxWidth="400px" />
What we see instead, is that the consumption is 118 kW, which is not possible.
The first step is to check the raw data in the <BrandName /> <ControllerName />. This can be done by going to the commissioning interface, and then to the **Data** tab. We immediately notice the following on our grid meter:
- _Marked in green_: The current value (across all phases) is 149 + 146 + 147 = ~442 A
- _Marked in green_: The average voltage value (across all phases) is around ~246 V
- _Marked in orange_: The power value (across all phases) is ~2800 W, which is not possible with such a high current and voltage.
  Instead, it should have been 2800 000 W, which is 2800 kW! That's a scaling factor of 1000.

<ClickableImage src="/img/generic/scaling-issues/1.png" alt="Image 1" maxWidth="800px" />

## How to rescale the energy meter readings?
To rescale the energy meter readings, follow these steps:
1. [Open the commissioning interface](/Controller/Configuration%20from%20A%20to%20Z/2-accessing-commissioning-interface/).
2. Go to the **Devices** tab.
3. Click on the **Settings** button of the energy meter you want to rescale.
<ClickableImage src="/img/generic/scaling-issues/2.png" alt="Image 1" maxWidth="600px" />
4. In the settings, find the appropriate  **Scaling factor** field.
5. Adjust the scaling factor to the correct value. In our example, we would set the power scaling factor to 1000.
<ClickableImage src="/img/generic/scaling-issues/3.png" alt="Image 1" maxWidth="600px" />

# Factory reset


import { BrandName, ControllerName, CustomerName, InsightsName, InsightsUrl, ModelPro, ModelHome, ModelLite, ModelConnect } from '@site/src/components/customFields';
import Details from '@theme/Details';
import ClickableImage from '@site/src/components/ClickableImage';
import Tabs from '@theme/Tabs';
import TabItem from '@theme/TabItem';

# Factory Reset

> [!WARNING]
> If you reset the <BrandName /> <ControllerName />, the network configuration will be reset to DHCP. Take care if you perform a factory reset remotely, because the <BrandName /> <ControllerName /> might lose network access if it needs a specific network configuration!

> [!WARNING]
> Before you perform a factory reset, it is recommended that you [make a backup of the settings](/Controller/Configuration%20from%20A%20to%20Z/11-Extra-Information/backup/).

## Through the commissioning interface
> [!TIP] Lost access to commissioning interface
> You can retrieve the IP address through mDNS. See also Option 3.2 of [Accessing the commissioning interface](/Controller/Configuration%20from%20A%20to%20Z/2-accessing-commissioning-interface#option-32-find-the-ip-address-with-mdns-also-works-if-the--does-not-have-a-good-network-configuration).

You can reset the <BrandName /> <ControllerName /> through the commissioning interface, from the settings tab.
Scroll down to "Factory reset", and click "Factory reset".

<ClickableImage src="/img/generic/factory-reset-en.png" alt="Image 1" maxWidth="350px" />

## Without the commissioning interface

<Tabs
  defaultValue="om1"
  values={[
    { label: 'Model OM1', value: 'om1' },
    { label: 'Model EDS', value: 'eds' },
    { label: 'Model M1S', value: 'm1s' },
    { label: 'Model M2S', value: 'm2s' },
  ]}
>
<TabItem value="om1">
## <BrandName /> <ModelPro /> (Model OM1)
<ClickableImage src="/img/eniris/model-OM1.webp" srcWhitelabeled = "/img/whitelabeled/ModelOM1.png" alt="Model OM1" maxWidth="350px" border="" />

Switch on the <BrandName /> <ControllerName /> and wait until it has booted (the status LED turns green). This can take several minutes without internet. Then reset it with the physical reset button in the pin hole next to the RS485 interface:

1. Press the reset button and keep it pressed. The status LED blinks red and yellow.
2. After 5 seconds the status LED turns solid red and the factory reset starts. You can release the reset button.
3. The <BrandName /> <ControllerName /> reboots: the status LED is green and blue while it starts and turns green when it is ready.

If you release the button before the status LED turns red, nothing is reset.

> [!TIP]
> Make sure you feel the reset button clicking when pressing it.

<ClickableImage src="/img/generic/om1-reset-button.jpg" alt="Image 1" maxWidth="500px" />
</TabItem>

<TabItem value="eds">
## <BrandName /> <ModelPro /> (Model EDS)
<ClickableImage src="/img/eniris/model-EDS.png" srcWhitelabeled = "/img/whitelabeled/ModelM1.png" alt="Model EDS" maxWidth="350px" border="" />
This model does not have physical reset button. You must reset the <BrandName /> <ModelPro /> through the commissioning interface.
</TabItem>

<TabItem value="m1s">
## <BrandName /> <ModelLite /> (Model M1S)
<ClickableImage src="/img/eniris/model-M1S.png" alt="Model M1S" maxWidth="350px" border="" />
This model does not have physical reset button. You must reset the <BrandName /> <ModelLite /> through the commissioning interface.
</TabItem>

<TabItem value="m2s">
## <BrandName /> <ModelHome /> (Model M2S)
<ClickableImage src="/api/media/controller/model-m2s/model-M2S-unbranded.webp" alt="Model M2S" maxWidth="350px" border="" />

Switch on the <BrandName /> <ControllerName /> and wait until it has booted (the status LED turns green). This can take several minutes without internet. Then reset it with the reset button in the pin hole next to the DC IN connector:

1. Press the reset button with a paperclip or a pin and keep it pressed. The status LED blinks red and yellow.
2. After 5 seconds the status LED turns solid red. Release the reset button now.
3. The factory reset starts when you release the button. The <BrandName /> <ControllerName /> reboots: the status LED is blue while it starts and turns green when it is ready.

If you release the button before the status LED turns red, nothing is reset.

<ClickableImage src="/api/media/controller/model-m2s/model-M2S-rs485-dc-panel.webp" alt="Reset button of the Model M2S, next to the DC IN connector" maxWidth="550px" />
</TabItem>

</Tabs>

# Reverse energy meter readings


import { BrandName, ControllerName, CustomerName, InsightsName, InsightsUrl } from '@site/src/components/customFields';
import Details from '@theme/Details';
import ClickableImage from '@site/src/components/ClickableImage';

> [!TIP]
> For the <BrandName /> <ControllerName /> energy meters are installed 'in reverse' when they count export / production / discharging as a positive number, and import / consumption / charging as a negative number.

> [!WARNING]
> For stable functioning of the control system, it is important that the <BrandName /> <ControllerName /> knows when an energy meter is installed in reverse.

You can indicate in the settings of the energy meter in the 'Devices tab' that an energy meter is installed in reverse.

<ClickableImage src="/img/generic/device-go-to-settings-en.png" alt="Image 1" maxWidth="600px" />
<ClickableImage src="/img/generic/energy-meter-reverse-en.png" alt="Image 1" maxWidth="600px" />


# Savings Estimates


import { BrandName, ControllerName } from '@site/src/components/customFields';
import ClickableImage from '@site/src/components/ClickableImage';
import { Accordion, Accordions } from 'fumadocs-ui/components/accordion';

# Savings Estimates
Estimates for the savings realized can be viewed in the app.

> [!NOTE] The savings as are estimates and calculated compared to 
> baseline cases. We try to stick to the principles outlined in international standards such as ISO 50006 and ISO 50015 
> for the used methodologies, adapted to the specific use cases and country where the <BrandName /> <ControllerName />
> is installed.
>
> Because the calculation is based on baseline cases, the savings are indicative. They should not be used for
> billing purposes, and the used methodologies may be updated with a recalculation happening later.


## Base methodology for estimating the savings
Every estimate follows the same simple idea: **compare what actually happened to what would have happened without smart control.**

Each morning, the <BrandName /> <ControllerName /> looks back at the previous full day. Using the measured power of your
installation and the energy prices that applied, it works out two numbers for every type of device it controls:

1. **The actual cost** — what your energy actually cost that day, given how the
   <BrandName /> <ControllerName /> steered your devices.
2. **The baseline cost** — what the *same* day would have cost in a **baseline case**:
   the same installation with the same energy needs, but without the smart control of
   that device.

The estimated saving is simply the difference between the two:

> **Saving = baseline cost − actual cost**

When the smart control saved you money, the baseline cost is higher than the actual cost, so the saving is positive.

### How cost is calculated

To turn power into cost, the <BrandName /> <ControllerName /> goes through the day moment by moment
and prices every bit of energy that crossed your grid connection:

- Energy **taken from the grid** (import) is valued at your **buy price**.
- Energy **sent back to the grid** (export) is valued at your **sell price**.

Both prices can change throughout the day — for example with a dynamic energy contract —
so each moment is priced with the tariff that applied at that time. Adding this up over
the whole day gives the total cost. Doing this once for the actual situation and once
for the baseline gives the saving.

Because every saving is the difference between two full-day cost calculations on the
*same* real measurements, everything outside the control's influence — your consumption,
the weather, the overall price level — appears in **both** numbers and cancels out. What
remains is the value the <BrandName /> <ControllerName /> added.

### The baseline for each device type

Each type of controllable device is compared against its own, fair baseline — the most
reasonable "what would have happened otherwise" for that device:

| Device | Baseline case (what it is compared against) |
| --- | --- |
| **Battery** | The same day **without any battery**, with every charge and discharge removed from the grid power. The saving reflects the value of storing energy and shifting it to better moments. |
| **Solar (PV)** | The same day **without any solar production**. This captures the full value of the produced solar energy — split into the part that offset your own consumption (valued at the buy price) and the part exported to the grid (valued at the sell price). When the <BrandName /> <ControllerName /> deliberately reduces solar production (for example at negative prices or to respect an export limit), the cost that would have been incurred *without* that adjustment is added on top. |
| **EV charging** | The **same charging sessions, but charging at full power** from the moment the car was plugged in — the way an ordinary charger would — instead of the smartly spread-out charging. The saving reflects the value of shifting that charging to cheaper moments. |
| **Flexible loads** (heating, cooling, switched loads) | The **same total energy spread evenly** across the whole day, instead of concentrated at the moments the <BrandName /> <ControllerName /> chose. |
| **Peak power** | The highest grid import and export **peaks** that would have occurred in the baseline (no battery, no curtailment, EV charging at full power) versus the peaks that actually occurred. |

The savings of all controlled devices are added together into the total saving for the
day, and the daily figures are summed into the totals shown in the app.

### When a day is left out

A saving is only reported when it can be estimated reliably. If, for a given day, the
required measurement data is missing or incomplete, a price or power reading is clearly
implausible, or a device did not actually follow the commands of the <BrandName />
<ControllerName />, then that device's saving for that day is left out rather than
reported as a potentially misleading figure. This keeps the totals honest, but it also
means the estimates are conservative: a real saving is sometimes skipped rather than
risk overstating it.

<Accordions>
<Accordion title="Which days are left out, and why">

Days are left out **per asset category** — leaving out a battery day, for example, does
not affect the solar or EV savings of that same day. A day is excluded from an asset
category's savings when:

- **There was no controllable device of this type.** If the <BrandName /> <ControllerName /> does not
  actively steer any device in this category, there is nothing it could have saved, so
  no savings are reported.

- **The control strategy is not price-driven.** Some strategies do not aim to save on
  the energy bill and so cannot be measured against a price-based baseline. For example,
  in peak-shaving the battery charges and discharges based on fixed power thresholds at
  the grid connection — the decision is driven by power, not by the energy price of that
  moment — so a price-based saving cannot be reliably estimated.

- **An external control signal was active.** When an outside party temporarily steers a
  device, its behaviour follows that party's own algorithm and possibly different prices
  than the day-ahead market. The <BrandName /> <ControllerName /> was not in control, so the saving
  for that day cannot be attributed to it.

- **No power measurements were available for a device.** Savings are computed from
  measured power. Without it for a device, there is nothing to calculate from.

- **The power measurements contain outliers.** Occasionally a meter reports values far
  outside a device's normal operating range — a sign that something went wrong in the
  read-out. Such values would badly distort the estimate, so the day is skipped rather
  than trusted.

- **The device did not follow the controller's instructions.** If the measured behaviour
  does not match the setpoints the <BrandName /> <ControllerName /> sent (for instance because the
  device was overridden, faulty, or ignored the commands), then the device did not do
  what it was told, and the day is not representative of the control.

- **Following the instructions could not be verified.** When there is too little setpoint
  or measurement data to confirm that the device actually followed the <BrandName /> <ControllerName />,
  the saving cannot be claimed with confidence, so the day is left out.

- **A battery was essentially idle.** A battery of meaningful size that barely charged or
  discharged over the whole day was not really being used, so there is no real control
  effect to credit for that day.

- **The energy prices contain outliers.** Buy or sell prices far outside a realistic
  range usually point to a misconfigured tariff. Since every cost is derived from these
  prices, an unrealistic price would make the whole estimate meaningless, so the day is
  excluded.

- **No grid meter is configured.** Savings are based on the cost of the power flowing
  through the grid connection point. Without a main grid meter measuring it, that cost —
  and therefore the saving — cannot be determined reliably.

- **The grid meter is wired incorrectly.** If the main grid meter's wiring is wrong, its
  readings do not represent the real grid connection, so any saving derived from them
  would be unreliable.

</Accordion>
</Accordions>

## Why savings are shown over a period, not day by day

Savings are always presented over a longer period — a week, a month, or more — never as a
figure for a single day. A day on its own can be misleading, and the battery is the
clearest example of why.

To save money, the <BrandName /> <ControllerName /> often **charges the battery when energy
is cheap** so that stored energy can be used later, when energy would otherwise be
expensive. On the day it charges, that energy has to be bought, which shows up as a
cost — so that day can look like a **loss**. But nothing was actually lost: the energy is
sitting in the battery, waiting to be used. The benefit only appears on a *later* day,
when the battery discharges and avoids buying expensive energy.

Looked at in isolation:

- the **charging day** shows only the cost, not the stored value it created, so it looks
  worse than it is;
- the **discharge day** shows an unusually large gain that was really "paid for" earlier.

Neither day tells the full story on its own. Only when enough days are added together does
the stored energy get used up and the true saving become visible. For this reason the
daily numbers naturally swing between negative and positive even when the control is
working exactly as intended, so the app reports savings over a period that is long enough
for these charge-and-use cycles to complete.

## Your average energy price

A clear way to see what the <BrandName /> <ControllerName /> does for you is to look at
your **average energy price**: how much, on average, one kilowatt-hour of the energy you
actually *use* costs you. By working out that price for a few different situations — all
based on the *same* energy you consumed — you can see how much value the <BrandName /> <ControllerName />
and your solar panels add.

> [!NOTE] **Mostly a production site?**
> Some installations are built mainly to produce energy and consume very little of it
> locally (or don't measure that consumption). When the solar production is much larger
> than the consumption — more than about ten times as much — the price per kilowatt-hour
> *consumed* says very little. In that case the <BrandName /> <ControllerName /> shows the
> average price of the energy you **produce** instead: calculated in the same way, but per
> kilowatt-hour generated rather than consumed.

> [!WARNING] **Consumed energy is not the same as imported energy**
> This average price is per kilowatt-hour of energy you **consume**, not per kilowatt-hour
> you **buy from the grid**. Your grid meter only registers what you import and export,
> while your solar panels can cover part of your consumption directly, without that energy
> ever passing through the meter. That is why this average price is usually **lower** than
> the price on your energy bill, which is based only on imported and exported energy.

### With the <BrandName /> <ControllerName />

This is what your energy actually cost: the real prices of each moment applied to the real
power that flowed to and from the grid. It already includes everything the <BrandName /> <ControllerName />
and your solar did for you.



### Without the <BrandName /> <ControllerName />, but with solar

This is what the same energy would have cost if you still had your solar panels, but the
<BrandName /> <ControllerName /> was not there to steer anything smartly (no smart battery use, no smart
charging or load shifting, no curtailment). The amount the <BrandName /> <ControllerName /> saved you is,
by definition, exactly the extra you would have paid without it.



### Without the <BrandName /> <ControllerName /> and without solar

This is what the same energy would have cost with neither the <BrandName /> <ControllerName /> nor any
solar panels — as if everything were bought straight from the grid.


# Settings page overview


import { BrandName, ControllerName, CustomerName, InsightsName, InsightsUrl } from '@site/src/components/customFields';
import Details from '@theme/Details';
import ClickableImage from '@site/src/components/ClickableImage';

# Settings page overview

The 'Settings' tab of the [commissioning interface](/Controller/Configuration%20from%20A%20to%20Z/2-accessing-commissioning-interface/) groups every site-wide setting of the <BrandName /> <ControllerName />. This page lists all the sections of the settings page, in the order in which they appear, and links to the chapter that explains each of them.

> [!NOTE]
> The settings of individual devices (nominal power, battery capacity, priority, ...) are not on the settings page. They are changed from the "Devices" tab, see [Device settings](/Controller/Configuration%20from%20A%20to%20Z/11-Extra-Information/device-settings/).

<ClickableImage src="/img/generic/settings/settings-page-overview-en.png" alt="The settings page of the commissioning interface" maxWidth="550px" />

| Section | What it does | Read more |
|:--|:--|:--|
| Grid settings | The main circuit breaker current, the grid system (single or three phase) and the allowed grid import and export power. | [Grid limits](/Controller/Configuration%20from%20A%20to%20Z/3-grid-limits/) |
| vZEV (Energy Community) | Only shown on sites in Switzerland: set up or manage the virtual energy community this <BrandName /> <ControllerName /> is part of. | [vZEV](/Controller/External%20Signals/vzev/) |
| Default working mode of the <BrandName /> <ControllerName /> | The local control mode per device type (storage, production, EVs, heat pumps, hot water boilers and on/off loads), with their thresholds and sub-settings. | [Setting control modes](/Controller/Configuration%20from%20A%20to%20Z/8-local-control-modes/setting-control-modes/) |
| Special local control modes | Control modes for specific, less common situations, such as green certificates, genset control with relays or excluding devices from control. | [Special local control modes](/Controller/Configuration%20from%20A%20to%20Z/8-local-control-modes/special-local-control-modes/) |
| Change password | The password of the local 'admin' user. | [Admin password and two-factor authentication](/Controller/Configuration%20from%20A%20to%20Z/11-Extra-Information/admin-password-and-2fa/) |
| Two-Factor Authentication (2FA) | Enable or disable a second factor for logging in to the commissioning interface. | [Admin password and two-factor authentication](/Controller/Configuration%20from%20A%20to%20Z/11-Extra-Information/admin-password-and-2fa/) |
| Location | The address of the installation, used for the weather forecast. | [Location / address](/Controller/Configuration%20from%20A%20to%20Z/4-location/) |
| PV installation details | The peak power, tilt and orientation of the solar panels, used for the production forecast. | [PV panel configuration](/Controller/Configuration%20from%20A%20to%20Z/9-pv-panel-config/) |
| Network usage | The data used in the last 30 days, the data saver and an internet connectivity test. | [Network settings](/Controller/Configuration%20from%20A%20to%20Z/11-Extra-Information/network-settings/), [Data Saver](/Controller/Configuration%20from%20A%20to%20Z/11-Extra-Information/data-saver/) and [Data usage](/Controller/Configuration%20from%20A%20to%20Z/11-Extra-Information/data-usage/) |
| Network configuration | The mode and IP configuration of the ethernet ports and the APN of the mobile network. | [Network settings](/Controller/Configuration%20from%20A%20to%20Z/11-Extra-Information/network-settings/) |
| Remote service connection | The connection that allows remote diagnostics, updates and support, and the port it uses. | [Network settings](/Controller/Configuration%20from%20A%20to%20Z/11-Extra-Information/network-settings/) |
| Backup settings and Restore backup | Download a backup file of all the settings, or restore one. | [Backup](/Controller/Configuration%20from%20A%20to%20Z/11-Extra-Information/backup/) |
| Check for updates | Check for a new software version, install it, and enable or disable automatic updates. | [Software updates](/Controller/Configuration%20from%20A%20to%20Z/11-Extra-Information/software-updates/) |
| Automatic reboot period | Reboot the <BrandName /> <ControllerName /> automatically every so many days. | [Reboot](/Controller/Configuration%20from%20A%20to%20Z/11-Extra-Information/reboot/) |
| Reboot | Reboot the <BrandName /> <ControllerName /> now. | [Reboot](/Controller/Configuration%20from%20A%20to%20Z/11-Extra-Information/reboot/) |
| Factory reset | Erase all settings and devices. | [Factory reset](/Controller/Configuration%20from%20A%20to%20Z/11-Extra-Information/reset/) |
| Prediction data reset | Erase the historic energy data of the forecasting model. | [Predictions](/Controller/Configuration%20from%20A%20to%20Z/11-Extra-Information/predictions/#resetting-the-prediction-data) |
| Email alarms | Get an email when the <BrandName /> <ControllerName /> repeatedly detects a problem. | [Email alarms](/Controller/Configuration%20from%20A%20to%20Z/11-Extra-Information/email-alarms/) |
| Advanced settings | Expert settings of the data logger, the control loop, the grid limits, batteries, EVs, PV and reactive power, plus the grid power limit schedule and the state of charge planning. | [Advanced settings](/Controller/Configuration%20from%20A%20to%20Z/11-Extra-Information/advanced-settings/) |
| About | The software version, the licenses and the changelog. | [Software version](/Controller/Troubleshooting/software-version/) |

> [!TIP]
> The grid settings, the default working mode, the data saver and the location are also asked during the initial setup wizard that appears the first time you open the commissioning interface. Everything you enter there can be changed later on the settings page.

> [!NOTE]
> ### Cloud controllers
> On a cloud <BrandName /> <ControllerName /> some sections are not applicable and are not shown, for example the network configuration, the remote service connection, the reboot and the factory reset. In multi-site mode, the site-specific sections (grid settings, working modes, location, PV details) are managed per site instead.


# Software updates


import { BrandName, ControllerName, CustomerName, InsightsName, InsightsUrl } from '@site/src/components/customFields';
import Details from '@theme/Details';
import ClickableImage from '@site/src/components/ClickableImage';

# Software updates

The software of the <BrandName /> <ControllerName /> is updated over the internet. Updates bring new device integrations, new external signals, improvements of the control algorithms and security fixes.

## Automatic updates

By default, automatic updates are enabled: the <BrandName /> <ControllerName /> installs a new software version as soon as it is released for it. This is the recommended setting.

To change it, go to the 'Settings' tab of the commissioning interface, scroll to "Check for updates", tick or untick "Enable automatic updates" and click "Save".

<ClickableImage src="/img/generic/settings/check-for-updates-en.png" alt="The check for updates section of the settings page" maxWidth="550px" />

> [!WARNING]
> If you disable the automatic updates, you may miss out on critical bug fixes and security updates. Damages that incur due to not updating the software may not be covered. Please check the contract with your distributor.

## Checking for updates manually

1. In the section "Check for updates", click "Check for updates now". The <BrandName /> <ControllerName /> contacts the update server; if there is no connection to the server, the buttons are greyed out.
2. The software update page shows whether the <BrandName /> <ControllerName /> is up to date, or which version is available.
3. Click "Update now" to install the available version. The <BrandName /> <ControllerName /> shows a page "updating" while it installs the update, and it may reboot. Do not unplug the <BrandName /> <ControllerName /> during the update; the page refreshes automatically when the update has finished.

<ClickableImage src="/img/generic/settings/software-update-page-en.png" alt="The software update page" maxWidth="550px" />

> [!NOTE]
> The devices are not read out and nothing is controlled while the update installs. The devices fall back to their own behaviour during those minutes, as they do at any restart of the <BrandName /> <ControllerName />.

## Which version is installed?

The section "About" at the bottom of the settings page shows the installed version, the licenses and the changelog with the contents of every release. See also [Software version](/Controller/Troubleshooting/software-version/).

## Updates through the toolbox

Distributors can install specific versions on specific <BrandName /> <ControllerName />s through the toolbox. See [Controllers toolbox](/Controller/Toolbox/Controllers/).


# Testing and manual override


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';

# Testing and manual override

You can test if a device reacts properly to a control signal / manually override the control with the "Test/manual override" button from the "Devices" tab. This will give a specific setpoint to the device.

> [!TIP]
> By default the override will last for 5 minutes, but you can extend this to any time you like. This function can thus be used for a manual override for any given amount of time.

<ClickableImage src="/img/generic/test-manual-override-en.png" alt="Image 1" maxWidth="850px" />
<ClickableImage src="/img/generic/test-manual-override-pt2-en.png" alt="Image 1" maxWidth="850px" />
<ClickableImage src="/img/generic/test-manual-override-pt3-en.png" alt="Image 1" maxWidth="850px" />


# User management


import {
  BrandName,
  ControllerName,
  CustomerName,
  InsightsName,
  InsightsUrl,
} from "@site/src/components/customFields";
import Details from "@theme/Details";

# User management

Check the [mobile app manual](/App/using-the-app/users-and-account#user-management) for user management and how to give the end user access to the app.


# Virtual energy meters and meter aggregation


# Virtual energy meters and meter aggregation

The term **virtual meter** is used for several different configurations. Choose the option based on the electrical question you need to answer.

| Situation | Correct option | Result |
| --- | --- | --- |
| Two or more physical meters together represent one shared electrical boundary | **Aggregate the meters in an advanced group** | The switchboard total is the sum of its meter members. |
| A real meter covers a switchboard, but one part has no submeter | **Add a virtual energy submeter** | The controller calculates the unmetered remainder. |
| You want to add or subtract arbitrary historical signals | **Create a SmartgridX virtual meter** | A calculated chart and CSV series, not a controller input. |
| Each grid connection has its own contractual or physical limit | **Keep separate control boundaries** | Each connection can be protected independently. |

> [!WARNING]
> Do not aggregate independent grid connections merely to obtain one convenient number. A safe total can hide an overload on one transformer, feeder, or connection. Aggregate only when the sum is the actual agreed control boundary, and preserve every individual equipment limit.

## Aggregate several physical energy meters

Use this topology when several measured feeders together form one common control boundary. Typical examples are two transformer feeders behind one shared site limit, or several departures whose powers must be summed for curtailment.

```text
Meter A  ──┐
           ├──  Shared switchboard total = Meter A + Meter B
Meter B  ──┘
```

### Configure the aggregate

1. Add every physical energy meter and verify that each one reports plausible power and energy values.
2. Open **Groups** and enable **Advanced groups**.
3. Create a **Switchboard** that represents the shared electrical boundary.
4. Add the physical meters as members of that switchboard.
5. Organise the controlled devices and any lower-level switchboards according to the single-line diagram.
6. Confirm that the calculated switchboard power equals the sum after applying the configured direction of each physical meter.
7. Test import, export, and the intended control action before commissioning the site.

An energy meter that is **assigned to** a device or group has a different meaning: it measures that entire child branch. Do not also add the same electrical flow elsewhere in the group tree, because it will be counted twice.

> [!NOTE]
> Meters may arrive through different supported communication routes, but every source must be timely and stable enough for the chosen control mode. A delayed or missing meter makes the aggregate an incomplete view of the boundary.

### Transformer and connection limits

Keep the hierarchy faithful to the electrical installation:

- use a common parent switchboard only for a limit that applies to the sum;
- keep a switchboard per transformer or feeder when it has its own current or power limit;
- configure both the shared site limit and the lower-level equipment limits when both apply;
- use separate EMS configurations when grid connections must operate independently.

For complex multi-transformer sites, validate the proposed single-line diagram and failure behaviour during commissioning before enabling automatic curtailment.

## Calculate an unmetered remainder

A **virtual energy submeter** estimates the part below one real meter that is not covered by its other measured children.

```text
Virtual remainder = Real parent meter - all other known child branches
```

For example, a main meter measures a complete switchboard and a branch meter measures the EV chargers. The virtual submeter can represent everything else on that switchboard.

### Create the virtual submeter

1. Open **Groups** and use **Advanced groups**.
2. Choose **Assign an energy meter to a device or a group**.
3. Select the real energy meter and the branch it measures.
4. Select the checkbox **Add a virtual energy submeter**.
5. Assign the meter.
6. Verify the calculated power and imported/exported energy with a known site state.

The controller creates a meter named after the measured branch with `remaining energy (virtual meter)` appended.

### Boundaries of a controller virtual submeter

- It is a fixed residual calculation, not an arbitrary formula editor.
- Only one virtual submeter is supported below a real meter.
- A virtual submeter cannot be selected as the grid energy meter.
- It is intended for remaining-energy measurements below its real parent meter.
- Removing the parent-meter assignment also removes its automatically created virtual submeter.
- Import and export are netted correctly when the subtraction crosses from one direction to the other.

## Create an analysis-only virtual meter

For arbitrary sums, differences, and scale factors in charts, use [Virtual meters in SmartgridX Monitoring](/Monitoring/Web%20portal/features/virtual-meters/).

That function is well suited to questions such as:

- `Transformer total = Meter A + Meter B`;
- `Unmetered load = Main meter - Submeter A - Submeter B`;
- comparing a calculated total with an existing physical reference.

It does not change the controller configuration and cannot be used as a setpoint or grid-control meter.

## Commissioning checklist

| Check | Verify before enabling control |
| --- | --- |
| **Communication** | Every physical meter is supported and reports reliably. |
| **Direction** | Import and export are confirmed with a known site event. |
| **Scaling** | Units, phase configuration, CT ratios, and scaling are correct. |
| **Topology** | The group tree matches the current single-line diagram. |
| **No double counting** | Every electrical flow occurs only once in the aggregate. |
| **Limits** | Shared and individual transformer, feeder, and grid limits are configured separately. |
| **Fallback** | Loss of one meter has an agreed safe operating response. |
| **Validation** | The calculated total is compared with a trusted reference. |

See [Grouping devices](/Controller/Configuration%20from%20A%20to%20Z/7-grouping-devices/) for the advanced group editor and [Supported energy meters](/Controller/Devices#energy-meters) for device-specific wiring and setup.


# Configuring a fixed IP address in Windows

import { BrandName, ControllerName, CustomerName, InsightsName, InsightsUrl, ModelPro, ModelHome, ModelLite, ModelConnect } from '@site/src/components/customFields';
import ClickableImage from '@site/src/components/ClickableImage';

## Windows 11
1. Open the Settings app of Windows, go to "Network & Internet" and click on "Ethernet".
2. Open the dropdown menu of your ethernet interface, and click on "Edit" next to "IP assignment"
<ClickableImage src="/img/eniris/networking/ethernet-interface-configure-fixed-ip-pt1.png" alt="Powershell start" maxWidth="600px" border="" />
3. Set the "IP Settings" to Manual, and give your computer a fixed IP address in the same range as the <BrandName />. For example, if your <BrandName /> has IP address 192.168.10.2, you should give your computer another IP address in the 192.168.10.x range. Make sure that the IP address you choose is not used by another device on the same network!
<ClickableImage src="/img/eniris/networking/ethernet-interface-configure-fixed-ip-pt2.png" alt="Powershell start" maxWidth="300px" border="" />
4. Click save. You can now surf to the IP address of the <BrandName /> in a web browser to access the commisioning interface.
5. When you're done, don't forget to put your ethernet interface back on "DHCP".

# 2. Accessing commissioning interface


import { BrandName, ControllerName, CustomerName, InsightsName, InsightsUrl } from '@site/src/components/customFields';
import InsightsLink from '@site/src/components/InsightsLink';
import Details from '@theme/Details';
import ClickableImage from '@site/src/components/ClickableImage';

# Accessing the commissioning interface

> [!NOTE]
> Make sure the <BrandName /> <ControllerName /> is switched on and connected to the network.

> [!TIP] 
> ### Troubleshooting
> If you have have trouble accessing the commissioning interface, see also "[Troubleshooting: Access to the commissioning interface](/Controller/Troubleshooting/device-communication/#access-to-the-commissioning-interface)".

## Option 1: Access through the app or portal
> [!TIP]
> Make sure you have [linked the <BrandName /> <ControllerName /> to your account](/Controller/Configuration%20from%20A%20to%20Z/1-link-to-your-account/) before proceeding.

1. Log in to the app (smartphone) or <InsightsLink /> (computer).
2. Set the view to '<BrandName />'

3. In the settings menu, switch to the <BrandName /> <ControllerName /> that you want to access.
<ClickableImage src="/img/eniris/insights-settings.png" alt="Image 1" maxWidth="250px" />
<ClickableImage src="/img/eniris/insights-switch-site.png" alt="Image 1" maxWidth="550px" />

4. Access the commissioning interface by clicking "Controller configuration".

> [!TIP] If it says that the <BrandName /> <ControllerName /> is offline, check out the [wiring & connectivity guidelines](/Controller/wiring-best-practices/) and the [network firewall guidelines](/Controller/network-configuration/#firewall)

## Option 2: Access locally through mDNS
> [!WARNING] 
> ### Software version
> This option is valid from software version 1.18.x.y onwards.

> [!NOTE] 
> ### Operating system
> The <BrandName /> broadcasts its IP address through mDNS. This protocol is supported on Windows 11 and newer builds of Windows 10.
> Older Windows versions do not support mDNS.

1. Connect your computer through ethernet to the same network as the <BrandName /> <ControllerName />.
2. Make sure you have DHCP configured for the ethernet interface of your computer. (NOT a fixed IP address! See also [give your computer a fixed IP address](/Controller/Configuration%20from%20A%20to%20Z/11-Extra-Information/windows-fixed-ip-address/))
3. Switch off WiFi on your computer (and 4G if you have that), and restart your computer so all network connections are cleared. After restarting, make sure all VPN connections are disabled.
4. Open a browser, surf to http://[SERIAL_NUMBER].local, where [SERIAL_NUMBER] is to be replaced by the serial number of your controller. For example, http://OM1241105ZEXO12B10A.local
5. It can take a minute for your computer to find the <BrandName /> <ControllerName />.
6. If no connection can be made, you need to find the local IP address of the <BrandName /> <ControllerName />. See option 3.

> [!TIP] 
> ### Initial configuration for a network without DHCP
> If you need to initially configure the controller in a network without DHCP, you can directly connect the controller to your computer (without a router) - and access it through mDNS.

## Option 3: Access locally through the <BrandName /> <ControllerName />'s IP address.

### Option 3.1: Find the IP address with an IP scanner (works if the <BrandName /> has a good network configuration)
1. Download an IP scanner such as "Fing" ([Google Play Store](https://play.google.com/store/apps/details?id=com.overlook.android.fing&hl=en&gl=US) or [iOS App Store](https://apps.apple.com/nl/app/fing-netwerk-scanner/id430921107)) or "[Advanced IP Scanner](https://www.advanced-ip-scanner.com/)" (Windows).

2. Connect your smartphone or computer to the same network as the <BrandName /> <ControllerName />.

3. Scan for devices on the network and find the IP address of the device with the MAC address listed on the <BrandName /> <ControllerName />'s label.
<ClickableImage src="/img/generic/example-label.jpg" alt="Image 1" maxWidth="350px" />
<ClickableImage src="/img/generic/advanced-ip-scanner.png" alt="Image 1" maxWidth="750px" />
<ClickableImage src="/img/generic/fing.png" alt="Image 1" maxWidth="350px" />

4. In a webbrowser, surf to the IP address.

### Option 3.2: Find the IP address with mDNS (also works if the <BrandName /> does NOT have a good network configuration)
> [!WARNING] 
> ### Software version
> The procedure below is valid from software version 1.18.x.y onwards.

> [!NOTE] 
> ### Operating system
> The <BrandName /> broadcasts its IP address through mDNS. This protocol is supported on Windows 11 and newer builds of Windows 10.
> Older Windows versions do not support mDNS.

1. Connect your computer through ethernet to the same network as the <BrandName />. Switch off WiFi on your computer (and 4G if you have that), and restart your computer so all network connections are cleared. After restarting, make sure all VPN connections are disabled.
2. Open the Windows start menu, type "powershell" and open "Windows PowerShell".
<ClickableImage src="/img/eniris/networking/powershell-start.png" alt="Powershell start" maxWidth="600px" border="" />
3. In PowerShell, type: "Resolve-DnsName -Name [SERIAL_NUMBER].local", where [SERIAL_NUMBER] is to be replaced by the serial number of your controller. For example, "Resolve-DnsName -Name OM1241105ZEXO12B10A.local"
4. After a minute, the IP addresses of the controller should appear.
<ClickableImage src="/img/eniris/networking/powershell-mdns.png" alt="Powershell mDNS" maxWidth="800px" border="" />
5. Only the address of the type "A" (an IPv4 address) can be used to access to the commissioning interface, due to general restrictions in web browsers.
6. If your computer is in the same subnet as the <BrandName />, then you should be able to access the commissioning interface by surfing to the IP address in a web browser.
7. Else, first [give your computer a fixed IP address](/Controller/Configuration%20from%20A%20to%20Z/11-Extra-Information/windows-fixed-ip-address/) in the same subnet as the <BrandName /> before accessing the commissioning interface.

# 3. Grid limits


import { BrandName, ControllerName, CustomerName, InsightsName, InsightsUrl } from '@site/src/components/customFields';
import Details from '@theme/Details';
import ClickableImage from '@site/src/components/ClickableImage';

# Grid limits
 
> [!NOTE]
> The grid system, current and power limits are requested during the initial setup. You can later change them from the menu "Settings" in the commissioning interface.

<ClickableImage src="/img/generic/grid-limits-en.png" alt="Image 1" maxWidth="350px" />

1. Enter the **nominal current of the main circuit breaker** of the electrical installation.

2. Choose the appropriate **grid system** under "Grid system." You have the choice of:
    - Single-phase 230V
    - Three-phase wye 230V line-neutral / 400V line-line
    - Three-phase delta 230V line-line

3. Under "Allowed grid import power", enter the maximum power that may be taken from the grid.\
This corresponds to an import limit.

4. Under "Allowed grid export power" enter the maximum power that may be fed back to the grid.\
This corresponds to an export limit.

5. You can optionally enter a safety margin, under "Allowed grid export power safety margin" if desired.

> [!NOTE]
> "Three-phase delta 230V line-line" occurs only in certain geographical areas. 


## Allowed Grid Export Power Safety Margin (kW)

By default, this is set to **0.0** if you’re working in the cloud—meaning no extra buffer is added.  
If you’re running outside of the cloud, a minimum safety margin of **1.5%** is required.

### How is the Grid Export Margin Determined?

The Grid Export Safety Margin is an optional extra buffer added to the maximum power your system can send back to the grid. It helps make sure you follow utility rules and accounts for small measurement errors.

By default, this safety margin is read from the system’s settings (called **metadata**).

This value is given in kilowatts (kW) and converted internally to watts (W).

If the system is not running in the cloud, a minimum safety margin is enforced to protect the grid.

### Grid Export Safety Margin Explanation

To keep the electrical grid safe and stable, a minimum safety margin of **1.5%** is always applied.

This margin is based on whichever power limit—import or export—is farthest from zero.

The export limit is then lowered by this margin to create a safety buffer.

This buffer prevents the system from running too close to the export limit, helping keep the grid reliable and safe.

---

### Example:

| Parameter                | Value      |
|-------------------------|------------|
| Import power limit       | 10.0 kW    |
| Export power limit       | 10.0 kW    |
| Standard safety margin   | 0.0 kW     |
| Minimum required margin  | 1.5% of 10.0 kW = 0.15 kW |
| **Adjusted export limit**| **9.85 kW** |

---

## Grid power limits mode

The advanced **Grid power limits mode** setting determines how the configured import and export limits are interpreted:

- **Instantaneous** applies the configured limits to every measurement.
- **Fifteen-minute average** limits the average grid power during the current quarter hour. Instantaneous power may temporarily exceed the configured value when the average earlier in that quarter hour was lower.

The separate **Always treat the grid import power limit as instantaneous** and **Always treat the grid export power limit as instantaneous** settings can keep either side instantaneous while the other side uses the fifteen-minute average.

> [!WARNING]
> Change these advanced settings only when the grid-connection requirements explicitly use quarter-hour averages. Instantaneous protection remains the safer default when there is any uncertainty.

## Grid power limit schedule
Sometimes we need to deviate from the import or export powers on certain days or certain time of the days.
This is can be enabled as followed:
1. On the settings page, scroll down to navigate to the 'advanced settings'.
<ClickableImage src="/img/generic/advanced_settings.jpg" alt="Image 1" maxWidth="550px" />
2. Scroll down to the section 'Grid power limit schedule'. Here you can specify rules for when the grid import and export power limits should be different from the defaults one of the main settings page.
<ClickableImage src="/img/generic/grid-limits-schedule-en.png" alt="Image 1" maxWidth="550px" />
3. Save the settings.


# 4. Location / address

 
import { BrandName, ControllerName, CustomerName, InsightsName, InsightsUrl } from '@site/src/components/customFields';
import Details from '@theme/Details';
import ClickableImage from '@site/src/components/ClickableImage';

# Location / address

> [!NOTE]
> The <BrandName /> <ControllerName /> uses its location to retrieve local weather forecasts. This is necessary for accurate control of connected devices.
>
> If you wish to not share the exact address for privacy reasons, use the name of a nearby town or city instead.

> [!NOTE]
> The location is requested during the initial setup. You can change it later under the "Settings" menu in the commissioning interface, in the "Location" submenu.

> [!TIP] 
> ### Troubleshooting
> If you have have trouble setting the address, see also "[Troubleshooting: Address / Location](/Controller/Troubleshooting/configuration/#address--location)".

1. Enter the installation's address.

2. Click "Validate address".
<ClickableImage src="/img/generic/location-en.png" alt="Image 1" maxWidth="350px" />

3. Check on the map if the location of the address is correct, and click "Save address".
<ClickableImage src="/img/generic/location-map-en.png" alt="Image 1" maxWidth="350px" />

# 5. Add grid energy meter


import { BrandName, ControllerName, CustomerName, InsightsName, InsightsUrl } from '@site/src/components/customFields';
import Details from '@theme/Details';

# Add grid energy meter
> [!NOTE]
> You should add the grid energy meter as the first device. This makes the rest of the configuration a bit easier.

For the specific wiring and configuration of your device, see "[Supported energy meters](/Controller/Devices#energy-meters)"

For the general flow on how to add a device, see "[Adding a device](/Controller/Configuration%20from%20A%20to%20Z/11-Extra-Information/adding-device/)".

If several physical meters together represent one shared grid or transformer boundary, or if you need an unmetered remainder, see [Virtual energy meters and meter aggregation](/Controller/Configuration%20from%20A%20to%20Z/11-Extra-Information/virtual-energy-meters/).


# 6. Add other devices


import { BrandName, ControllerName, CustomerName, InsightsName, InsightsUrl } from '@site/src/components/customFields';
import Details from '@theme/Details';

# Add other devices

For the specific wiring and configuration of your device, see "[Supported devices](/Controller/Devices/)"

For the general flow on how to add a device, see "[Adding a device](/Controller/Configuration%20from%20A%20to%20Z/11-Extra-Information/adding-device/)".

# 7. Grouping devices


import { BrandName, ControllerName, CustomerName, InsightsName, InsightsUrl } from '@site/src/components/customFields';
import Details from '@theme/Details';
import ClickableImage from '@site/src/components/ClickableImage';
import ClickableVideo from '@site/src/components/ClickableVideo';

# Grouping devices

Go to the "Groups" tab in the commissioning interface.

The grouping function allows you to schematically organize the devices as they are connected to the electrical groups in your building as shown in the first figure.

You can compare this with the single-wire diagram of your building.

<ClickableImage src="/img/generic/groups-example-en.png" alt="Image 1" maxWidth="550px" />

You need to do this so that the <BrandName /> <ControllerName /> knows how everything is connected. It can for example take the maximum current of a group into account.

There are two configuration options:
1. Simple groups (default)
2. Advanced groups

## Simple groups
Simple groups is the default option. With this option, the <BrandName /> <ControllerName /> will automatically use the first energy meter you connect as the grid energy meter, and place all devices in one group. You can compare this to an installation with one energy meter and one distribution board.

> [!TIP] For most installations, this is the recommended option.
>
> You do not need to do anything when this option is enabled.


## Advanced groups
Advanced groups can be used for more complex installations. Here you have complete freedom to configure how the electrical installation is structured.

> [!TIP] When do I need advanced groups?
> **You do not need advanced groups if...**\
> ... you have a single energy meter and all devices connected straight to your main distribution board.
>
> **You may want to use advanced groups if...**\
> ... you have multiple energy meters and sub-metering\
> ... you have a commercial or industrial installation with a need for separate load guarding of electrical groups.

Advanced groups can also aggregate several physical energy meters that together represent one shared control boundary, or calculate the unmetered remainder below a real meter. See [Virtual energy meters and meter aggregation](/Controller/Configuration%20from%20A%20to%20Z/11-Extra-Information/virtual-energy-meters/) before configuring these topologies.

> [!NOTE]
> When a new device is added, it will appear at the top level.

> [!NOTE]
> Only one item may appear at the top level (i.e., just below “distribution grid” of the installation), and it must be the energy meter of the grid, a group or a solar installation.


### Creating a new group
1. Choose "Create a new device group" from the dropdown menu.
2. Choose a group name and type. The following types are available:
    - Switchboard (distribution board): This corresponds to an electrical distribution board.
    - Solar installation (PV installation): This corresponds to a group of PV inverters, and is specifically intended for monitoring PV installations.

<ClickableVideo 
  videoSrc="/img/generic/create-new-group-en.mp4" 
  alt="Demo Video" 
  maxWidth="200px" 
/>


### Assigning an energy meter to a group or device
1. Choose "Assign an energy meter to a device or a group" from the dropdown menu.
2. Choose the energy meter you want to assign.
3. Choose the group to which you want to assign it.
4. Click on "Assign energy meter".

Enable **Add a virtual energy submeter** only when you want the controller to calculate the part measured by the real parent meter that is not covered by its other known child branches.

> [!WARNING] Do not add the energy meter you want to assign as the energy meter of a group as a member to the group!

<ClickableVideo 
  videoSrc="/img/generic/assign-energy-meter-en.mp4" 
  alt="Demo Video" 
  maxWidth="200px" 
/>


### Adding devices to a group
1. Choose "Manage existing groups" from the dropdown menu.
2. Choose the group to which you want to add devices.
3. Select the device you want to add.
4. Click on "Add member".

<ClickableVideo 
  videoSrc="/img/generic/add-devices-to-group-en.mp4" 
  alt="Demo Video" 
  maxWidth="200px" 
/>


### Adding a subgroup
1. Create a new group as described in "Creating a new group"
2. Choose "Manage existing groups" from the dropdown menu.
3. Select the group to which you want to add the subgroup.
4. Choose the subgroup you want to add.
5. Click on "Add member".

<ClickableVideo 
  videoSrc="/img/generic/add-subgroup-en.mp4" 
  alt="Demo Video" 
  maxWidth="200px" 
/>


# Capacity tariff schedule


import { BrandName, ControllerName } from '@site/src/components/customFields';
import ClickableImage from '@site/src/components/ClickableImage';

# Capacity tariff schedule

The capacity tariff schedule tells the <BrandName /> <ControllerName /> when peak-shaving protection is needed, how much battery energy should remain available, and which grid-power thresholds control charging and discharging.

> [!IMPORTANT]
> The schedule reserves battery capacity and applies peak shaving only during the periods when grid peaks are commercially important. The applicable peak calculation, averaging interval, tariff windows, and billing method are defined by the grid operator or energy contract. Confirm those rules before choosing thresholds.

## What problem does this solve?

Many electricity network tariffs include a capacity component. Instead of charging only for total energy consumption, the grid operator may also consider the highest power peak reached during a billing period or measurement window. A short, high import peak can therefore have a disproportionate effect on network costs.

A battery can reduce those peaks by temporarily supplying part of the site's demand. Scheduling this protection avoids reserving the entire battery all day and keeps more capacity available for self-consumption or cost optimisation outside the relevant tariff windows.

### Energy and power are different

- **Energy (kWh)** is the amount consumed over time.
- **Power (kW)** is the rate of consumption at a specific moment or over an averaging interval.

Two sites can consume the same amount of energy in a day but create very different grid peaks. A site that runs several large loads simultaneously requires more grid capacity at that moment.

<ClickableImage
  src="/img/controller/capacity-tariff-schedule/energy-vs-power.svg"
  alt="Two sites using the same daily energy while creating different power peaks"
  maxWidth="900px"
/>

### What the schedule provides

- **Time control:** protect selected tariff windows instead of reserving the battery all day.
- **Energy security:** keep a defined battery partition available for peak shaving.
- **Seasonal flexibility:** use one threshold set for the full year, per quarter, or per month.
- **Stable control:** separate start and stop thresholds prevent rapid switching around a single limit.

## How the controller responds

1. **Before the window:** optionally charge the reserved battery partition so it is ready.
2. **During the window:** monitor grid power and discharge or pause charging according to the four configured thresholds.
3. **Outside the window:** release the non-reserved part of the battery to the configured secondary objective, such as self-consumption or cost optimisation.

For example, suppose a site should remain below a target import level during weekday mornings. When demand rises above the discharge-start threshold, the battery supplies part of the load. Once import falls below the discharge-stop threshold, discharging stops. Charging is allowed again only when sufficient grid headroom or local surplus is available.

<ClickableImage
  src="/img/controller/capacity-tariff-schedule/scheduled-peak-shaving.svg"
  alt="Capacity tariff window using a reserved battery partition to shave a grid-power peak"
  maxWidth="900px"
/>

## Open the capacity tariff schedule

In the commissioning interface, go to:

**Settings → Advanced settings → Capacity tariff schedule**

The summary shows whether the feature is enabled, the current critical reserve, whether pre-charging is active, and the number of configured rules. Select **Open capacity tariff wizard** to review or build the schedule.

<ClickableImage
  src="/img/controller/capacity-tariff-schedule/capacity-tariff-summary.png"
  alt="Capacity tariff schedule summary in the SmartgridOne advanced settings"
  maxWidth="850px"
/>

> [!WARNING]
> Opening the wizard does not activate the feature. Activation happens only when **Save and enable capacity tariff schedule** is selected at the end.

## Configure tariff windows and battery reserve

### Step 1 - Choose when the tariff is active

Add one or more weekly windows. Each window combines a day selection with a start and end time. Presets are available for the full week, weekdays, weekends, and individual days. Times are selected in 15-minute steps.

- Use separate windows when weekdays and weekends have different tariff rules.
- Do not overlap windows; define each protected period clearly.
- Match the schedule to the official tariff window, not simply to the site's normal operating hours.

### Step 2 - Set the critical reserve

The critical reserve is the percentage of total battery capacity held specifically for peak shaving. This partition protects the site when the normal operating partition has been used and grid power exceeds the configured thresholds.

A larger reserve provides more peak-shaving endurance but leaves less battery capacity for the secondary objective. A smaller reserve leaves more room for normal optimisation but may be exhausted during a long or severe peak period.

Before choosing a reserve, consider:

- How long the expected peak can last.
- How much usable battery energy remains between the minimum and maximum state of charge.
- Whether the battery's charge and discharge power and response time can cover the expected load step.

### Step 3 - Decide whether to pre-charge

When **Charge the critical reserve before each capacity tariff period** is enabled, the controller charges the battery to the minimum state of charge plus the reserved partition before the window starts. This makes the full reserve available from the beginning of the protected period.

<ClickableImage
  src="/img/controller/capacity-tariff-schedule/capacity-tariff-wizard.png"
  alt="Capacity tariff schedule wizard with tariff windows, critical reserve, and pre-charging settings"
  maxWidth="850px"
/>

## Configure the peak-shaving thresholds

The four thresholds create a control band around the desired grid-power level. Separate start and stop values provide hysteresis, preventing the battery from continuously switching between charging, idle, and discharging when measured power fluctuates around one boundary.

| Threshold | What it controls |
| --- | --- |
| **Start discharging above** | Begin discharging when grid import rises above this level. |
| **Stop discharging below** | Stop discharging after grid import falls to the lower release level. |
| **Stop charging above** | Pause charging before it consumes too much grid headroom. |
| **Start charging below** | Allow charging again when grid import is low enough or sufficient local surplus is available. |

The thresholds must use this order:

`Start charging below <= Stop charging above <= Stop discharging below <= Start discharging above`

<ClickableImage
  src="/img/controller/capacity-tariff-schedule/capacity-tariff-thresholds.png"
  alt="Monthly capacity tariff threshold settings and the charging and discharging control bands"
  maxWidth="850px"
/>

### Choose the time resolution and starting values

Choose **All year round** for one consistent target, **Per quarter** for seasonal groups, or **Per month** when network limits or operating conditions change throughout the year.

- Start from the official capacity limit or target agreed with the grid operator.
- Leave a practical margin below the contractual or billing limit for measurement delay and sudden load changes.
- Set discharge start slightly below the maximum level that must not be exceeded.
- Set discharge stop lower than discharge start so small fluctuations do not cause rapid cycling.
- Keep both charging thresholds below the discharge thresholds to preserve grid headroom.
- Validate the first protected periods using live grid-power and battery state-of-charge data.

## Review, enable, and monitor

Before enabling the schedule, review every active window and threshold set. Selecting **Save and enable capacity tariff schedule** enables the feature and replaces the existing capacity tariff rules.

### Pre-activation checklist

- [ ] The tariff windows match the grid operator's published rules.
- [ ] The reserve is large enough for the expected peak duration and battery power limit.
- [ ] Pre-charging will not create an unwanted peak before the tariff window.
- [ ] All four thresholds are complete and use the required order.
- [ ] The selected yearly, quarterly, or monthly detail matches the contract.
- [ ] The installation's grid limits, meter direction, and battery controls have been validated.

### Interaction with other control functions

- **External signals** and special local control modes take priority while they are active.
- **The capacity tariff schedule** controls battery peak shaving during its windows. Outside those windows, one configured secondary objective can operate.
- **Storage state-of-charge planning** is replaced when the capacity tariff schedule is enabled. Do not use both planning functions simultaneously.
- **Grid power limit schedule** is a separate function and continues to apply independently.

### Practical commissioning approach

1. Start with the official tariff windows and a conservative grid-power target.
2. Choose a reserve based on usable battery energy, expected peak duration, and battery charge and discharge power.
3. Monitor the first protected periods and compare grid power, battery state of charge, and whether the reserve was exhausted.
4. Adjust thresholds or reserve gradually; avoid changing several parameters at once.
5. Review the schedule whenever the tariff, site loads, battery capacity, or operating strategy changes.

> [!NOTE]
> During protected periods, the controller uses the reserved battery capacity to reduce grid peaks while preserving a predictable operating band. This can reduce exposure to capacity charges, but it cannot guarantee a specific invoice because billing rules and site conditions remain external factors.

## When to contact your installer or support partner

Ask for assistance if the tariff calculation is unclear, the battery reserve empties too early, charging creates a new peak, the meter sign convention is uncertain, or another control signal appears to override the schedule. Validate changes against both the electrical installation limits and the applicable network tariff.

For the underlying battery control behaviour, see [Battery peak shaving](/Controller/Configuration%20from%20A%20to%20Z/8-local-control-modes/extra-peak-shaving-battery/).


# Full explanation


import { BrandName, ControllerName, CustomerName, InsightsName, InsightsUrl } from '@site/src/components/customFields';
import Details from '@theme/Details';
import ClickableImage from '@site/src/components/ClickableImage';
import PdfLink from '@site/src/components/PdfLink';

# Full explanation of the local control modes

## Introduction
The <BrandName /> <ControllerName /> has different control modes for the following types of devices:
- Storage, e.g. batteries
- Energy production devices, e.g. solar panels
- EV charging infrastructure
- Heat pumps, boilers & devices switched on/off by relay

## Order of planning and priorities
The scheduler follows an order of planning in devices, in a two stage system.

In the first stage, the scheduler plans everything except for solar production with no active curtailment setpoint via API and unoccupied EV chargers. This stage has three layers:
1. Device priorities are the top layer. First, all the highest-priority devices are scheduled, then all high-priority devices, and so on. You can assign a priority to each device in its settings.
2. The type of device is the second layer. For all devices with the same priority, the devices are scheduled in the following order according to their type:
    1. Heat pumps, boilers & devices switched on/off by relay. These devices are the least flexible to control.
    2. EV charging infrastructure. It is more efficient to consume your own energy immediately than to store it.
    3. Storage.
    4. Solar production with an active setpoint through control via API. (Note, if there is an external signal configured for solar production, but it is not presently active and local control is used, then solar production will be planned in during the second stage)
3. The control mode is the third layer. For all devices with the same priority, of the same type, they are scheduled in the following order according to their control mode:
    1. Control not active, device always off and device always on.
    2. Control via API (if an external signal is active)
    3. Peakshaving / load balancing only
    4. Maximize self-consumption
    5. Cost optimisation

In the second stage, solar production with no active setpoint via API and unoccupied EV chargers are planned in. Here the order is a little bit different:
1. All solar production in the 'cost optimisation' control mode, in order of device priorities.
2. All solar production in the 'feed in restriction' control mode, in order of device priorities.
3. All unoccupied EV chargers, in order of device priorities.

To assign a priority to a device, see also [Priorities](/Controller/Configuration%20from%20A%20to%20Z/8-local-control-modes/extra-device-priorities).

By playing with the priorities, you can obtain a different order of scheduling if desired.

> [!NOTE]
> #### Application Example: Priority EV Charging Station
> You have a parking lot with several EV charging stations. You want some charging stations to be given priority when charging for people who are often on the road. To do this, you can use the priorities and give priority to the EV charging stations.

> [!NOTE]
> #### Heat pumps, boilers and on/off loads
> For heat pumps, boilers and on/off loads, the consumption is not known if they do not provide measurements or are not explicitly measured with a separate energy meter. As a result, the <BrandName /> <ControllerName /> cannot distinguish this from the basic consumption of the building, and therefore cannot be taken into account in the priorities.


## Pricing parameters
Energy prices are used as the basis for all cost optimisations. The following formulas are used to convert market prices into your energy price:

- Actual **purchase price you pay** for **purchased energy** = [Day ahead price in EUR/kWh] x [Buy energy cost scale factor] + [Buy energy cost scale offset in EUR/kWh] + [Buy grid cost]

- Actual **selling price you get** for **feed-in energy** = [Day ahead price in EUR/kWh] x [Sell energy cost scale factor] + [Sell energy cost scale offset in EUR/kWh] – [Sell grid cost in EUR/kWh]

(Note the minus sign next to the grid costs of the energy fed in)

You can set these price parameters via the "Settings" tab of the app.

### Grid costs
**For grid costs, you enter the grid costs per kWh you pay.** This is typically around 0.08 EUR/kWh for purchased energy. You can find this on your final energy bill or contract. For feed-in energy, this may vary:

- If you have a reversing meter (Belgium) or if you are allowed to net (the Netherlands), the grid cost is the same for feed-in as for offtake.

- Otherwise, you probably won't have to pay grid costs on feed-in energy. You then enter 0 in the grid costs for the energy that is fed in.

### Scale factor on day ahead and fixed energy costs
**The scale factor on the day-ahead price** and the **fixed cost for purchased and feed-in energy** depend on your type of contract.

#### For a fixed and variable contract
The day ahead price does not play a role here. So, you need to set the vendor scaling factor to 0.

For "fixed cost of purchased energy in EUR/kWh" and "fixed cost of feed-in energy in EUR/kWh", enter respectively the price you pay to the supplier per kWh purchased and the price you receive from the supplier per kWh fed in.

If you have a reversing meter (Belgium) or if you are allowed to net (the Netherlands), the fixed costs for purchased and returned energy are the same.

#### For a dynamic contract
You can find the scale factor and fixed cost on your supplier's website or on your contract. Most suppliers work with a scale factor of 1, a fixed cost for purchase around 0.02 EUR/kWh and a fixed cost for feed-in around -0.02 EUR/kWh.

## Current and Power limits
### On the grid connection
In the <BrandName />, you can set the current and power limits of the electrical installation. The <BrandName /> will take this into account when scheduling the controllable devices.

The **current limit** is used to **monitor against overflowing**. Please note, this is not a substitute for an electrical protection, but will ensure that your security will not trip unnecessarily. This limit is not intended to limit offtake and feed-in to the grid. To do this, use the power limits.

The **power limits** serve to indicate that only a limited amount of power from the grid may be taken from or fed back into the grid. You need to set these limits large enough, otherwise you run the risk that your devices will never be able to draw the power they need.

You can specify a **safety margin** to ensure that the maximum feed-in limit is never exceeded.

**Please note**, if you have an electric car, keep in mind that it needs at least 1500W if it is charging single-phase, or 4500W if it is charging three-phase. (Most electric cars require a minimum current of 6A or even 12A, and can temporarily malfunction until you plug it in again if the charging station is not allowed to provide it).

### By groups
You can also use the groups page to indicate whether specific power limits apply to a group. These will also be included in the planning. To do this, enable advanced groups, and go to the settings of the group you want to apply the power limit to.

### Three-phase connections
In the <BrandName />, under "Settings" and → "Advanced settings", you can enable three-phase planning and monitoring.

**Unless you absolutely need three-phase planning and monitoring due to, for example, a large imbalance in the phase currents, it is recommended to leave this option OFF.** This is because this option requires you to also set which phases each device is connected to, and whether any phase mapping is required. **This is prone to errors.** This mapping is necessary to ensure that the current of a phase as measured by the energy meter actually corresponds to the current of a phase as reported by a device (it happens that the terminals L1, L2 and L3 of a device are not connected to the phases L1, L2 and L3 of the grid on a one-to-one basis, but for example extension L1 on network L2, extension L2 on network L1 and extension L3 on network L3).

If you leave the three-phase option off, the <BrandName /> will look internally at the most heavily loaded phase for current monitoring. In almost all cases, this is sufficient.

The three-phase option does not affect the power limits. Here, the <BrandName /> always look at the total power.

## Storage
> [!NOTE] General Note: Charging Schedules
> You can specify charging schedules to ensure that the storage has a certain charge percentage at fixed times on fixed days of the week. Please note that the <BrandName /> will try to follow the control mode in order to respect this charging schedule.
>
> For more information, see [Charging schedule batteries](/Controller/Configuration%20from%20A%20to%20Z/8-local-control-modes/extra-battery-charging-schedule)

### Maximize self-consumption
In this mode, storage is used to cover as much self-consumption as possible with self-produced energy. The battery charges when energy would be fed back and discharges when energy would be drawn.

#### Self-consumption with (dis)charging at specific grid power thresholds
If you only want the battery to charge or discharge above or below a certain threshold, you can use the "Peakshaving only" strategy for this. Underlying this, the "Maximize self-consumption" and "Peakshaving only" strategies use the same algorithm, with all grid power thresholds set to zero for "Maximize self-consumption".

### Peakshaving only
In this mode, storage is used to smooth out peaks. To do this, you enter the following thresholds for the grid power:
- Start discharge above (kW) (Discharge start): Above this grid power, the storage will discharge and the grid power will level off to this threshold.
- Stop discharging below (kW) (Discharge stop): When the storage is discharging, it will stop discharging as soon as the grid power drops below this threshold.
- Stop charging above (kW) (Charge stop): When the storage is charging, it will stop charging as soon as the grid power rises above this threshold.
- Start charging below (kW): Below this grid power, the storage will load and the grid power will level off to this threshold.

<ClickableImage src="/img/generic/peakshaving_thresholds.png" alt="Peakshaving charging and discharging thresholds" maxWidth="800px" />

#### APPLICATION EXAMPLE 1
You have a grid connection that is limited to 100kW consumption. To avoid exceeding this power, you can, for example, use 80kW as a threshold value for starting and stopping discharging and 70kW for starting and stopping charging. As soon as the grid power rises above 80kW, the storage will discharge to limit the grid power to 80kW. At a later date when the grid power drops below 70kW, the storage is charged (resulting in a final grid power of 70kW).

#### APPLICATION EXAMPLE 2
Your installation falls under the system of the "terugdraaiende teller" (BE) / "salderen" (NL), but you have more solar generation than your grid connection can handle. You only want to charge your battery when there is more than 10kW of feed-in, and only have it discharged when you have more than 5 kW of consumption. To achieve this, you can set the thresholds "Start discharging above" and "Stop discharging below" to 5kW, and "Stop charging above" and "Start charging below" to **-10kW**. (*minus* 10kW).

### Cost optimisation
In this mode, the storage charges at the cheapest possible times and discharges the storage to cover consumption at the most expensive times. The <BrandName /> takes into account:
- The energy prices, including differences between purchase and sale prices (charging your own solar energy is usually more interesting than charging from the grid).
- The predicted grid power.
- The efficiency of the battery.
- A minimum price difference between the cheap and expensive moments. You can use this to take into account, for example, the wear and tear when using the battery. See also [Accounting for wear and tear costs, and battery efficiency](/Controller/Configuration%20from%20A%20to%20Z/8-local-control-modes/extra-wear-battery).

#### Power Limit Monitoring 
If necessary, the <BrandName /> will deploy the storage to prevent exceeding the power limits of the installation – regardless of the energy price at that time.

#### Energy trading 
It is also possible to indicate that the storage may be used for **energy trading**. With this option, you can use the storage to buy energy at cheap times and sell it back at expensive times.

#### Risk profile
Since the control is based on predictions, there is always a risk that the predictions do not come true. With the predictive AI algorithm, you choose how much risk the <BrandName /> may take with **Strategy & Aggressiveness**, right below the cost optimization mode on the "Settings" page. The default is **Balanced**. All cost optimization settings are explained in [Battery cost optimization settings](/Controller/Configuration%20from%20A%20to%20Z/8-local-control-modes/extra-battery-cost-optimization/).

|  | Conservative | Balanced (default) | Aggressive |
|:--|:--|:--|:--|
| Charging to a minimum level before high prices start | Always, at the level set for "Make sure that the battery is charged to a minimum level before high prices start" (70% unless changed), even when that option is not ticked. | Only when that option is ticked. | Only when that option is ticked. |
| Charging now versus waiting for a better price | Leans towards charging and keeping energy in the battery. It also plans as if the battery had no conversion losses, so it already charges for smaller price differences. | Leans towards charging and keeping energy in the battery. | Follows the forecast prices without leaning towards charging: the highest return when the forecasts come true, but the battery may be charged less than ideal when they do not. |

For all three strategies, a small part of the battery follows self-consumption as long as buying energy costs noticeably more than selling it. This keeps a buffer of cheap solar energy to cover fluctuations in consumption and production within the hour, which could otherwise lead to more expensive energy from the grid. This is especially useful on changeable days. A possible side effect is that the battery always charges a little on solar energy in the morning. The size of this buffer is the advanced setting "Storage cost optimization variability buffer size (%)", see [Advanced settings](/Controller/Configuration%20from%20A%20to%20Z/11-Extra-Information/advanced-settings/#battery-control).

> [!NOTE] Predictions versus ex-post analyses
> The "cost optimisation" mode looks at the expected production surplus and the expected consumption in the future, in combination with energy prices. These forecasts are updated at any time according to what happens during the day.
>
> It is important to take into account that the cost optimisation is done by means of **predictions**. In other words, the information with which the <BrandName /> makes its decisions at any given moment is based on what is **likely to happen** in the **future**. This also means that when you look back at what the <BrandName /> has done, you look at the actual consumption and production of the **whole day up to the moment you look** at it – information that the <BrandName /> did not have at the time of steering itself – and on the basis of which other decisions might have been made.
>
> <ins>For example:</ins> In the morning it is expected that there will be a lot of surplus solar production in the afternoon, which can only be sold at a low price. For the <BrandName />, this is the cheapest energy with which it expects to be able to charge the battery that day. He therefore decides to postpone charging to the afternoon, and to have the solar production of the morning fed back into the grid. However, in the afternoon the weather changes, and the solar production is lower than expected. The <BrandName /> will charge the battery less than it could have done, if it had been known in the morning that the weather would change.

## Energy poduction devices (solar panels)
### Limit feed-in to permissible feed-in limit
In this control mode, the power of production devices such as solar panel inverters is reduced when necessary to limit the feed-in of energy to the grid to the set limit.

### Cost optimisation
In this control mode, the power of production devices such as solar panel inverters is curtailed to limit the feed-in to the grid when:
- Energy sales prices are negative; In this case, production is curtailed in order to have no net feed-in.
- The purchase prices of energy are negative; In this case, production is completely shut down. After all, you are being paid to consume at this moment!
- At other  times, the set feed-in limit would be exceeded.

## EV charging infrastructure
> [!NOTE] General remark: minimum charging current
> Many combinations of electric cars and EV charging stations do not allow charging to be switched off completely. As a result, a minimum charging current is always allowed. In most cases of AC chargers, this is 6A. You can (experimentally) try to force per charging station that charging can be completely interrupted (but unfortunately this cannot be guaranteed). To do this, use the "Allow pause charging (experimental)" setting, available in the settings of a charging station.

> [!NOTE] General Note: Charging Schedules
> You can set charging schedules from the app. In the app, you can specify rules per connector at each charging station where a connected car must have charged a certain number of kilometers or kWh since the last time it was plugged in against:
> 1. A fixed time on fixed days of the week
> 2. A certain time and date
>
> The <BrandName /> always takes into account the next rule that has been set. (An extension to this to take all the rules into account at the same time is planned).
>
> When there are no more rules set, the car will load until it is full.

### Peakshaving / load balancing only
In this mode, charging is set so that the permissible consumption limit from the grid is not exceeded. The power is distributed as evenly as possible between the different cars if there are several EV charging stations.

> [!NOTE]
>  Use charging station priorities if there are EV charging stations that need to charge faster than others.

### Maximize self-consumption
In this mode, the electric vehicles are charged as much as possible on self-produced energy. There are three sub-modes:
1. Pure charging on solar power: No energy is taken from the grid for charging.
2. Charging at times of energy surplus: Charging takes place when there is a surplus of energy production, but at fullspeed. If there is no surplus, loading is done at a minimum speed.
3. Mainly charging on solar power, with matching deficit from the grid.

### Cost optimisation
In this mode, an attempt is made to charge electric vehicles at times of cheapest possible energy price.

> [!NOTE]
> Your vehicle will most likely always charge a little regardless of the price. See also the general remark regarding the minimum charging current.

## Heat pumps, boilers and on/off devices
### General Note: Boosting and Blocking
For most devices in this category, there are one or more of three possible operational states:
1. Blocking: The device is blocked in order to limit energy consumption.
2. Boosting: The device is 'boosted' with the objective to increase consumption or to switch on the device at times when it is advantageous, so that energy consumption is lower at times when it is less advantageous.
3. Own operation / no intervention: The <BrandName /> does not interfere with the operation of the device. This is usually desired at times when there is no clear benefit to blocking or boosting.

Depending on the available operational statuses, you can choose per device whether the device works in its own operation, blocking or boosting mode by default. In addition, you can specify how long the minimum or maximum can be blocked or boosted, and how long the device must be on its own in order to block or boost. The minimum duration is intended to prevent too much switching on/off (this is detrimental to efficiency for some devices). The maximum duration is intended to avoid a detrimental impact on comfort.

Examples of how you can use this to your advantage:
- You'll want to block your heat pump at the most expensive times of the day, for up to three hours, as you'll notice a difference in comfort from then on.
- You want to boost your heat pump at the cheapest times of the day.
- You only want to have your pool heating switched on when you have a surplus of solar energy.
- You want to force your biggest consumption off at the most expensive time of the day with a contractor.

> [!NOTE]
> If the grid limits are exceeded, the minimum and maximum times for blocking and/or boosting will be ignored. If this happens too much, consider giving the device a higher priority.

#### Relay contacts
For the relay contacts and external relay modules, you can specify in the settings of the device whether it can be turned on and off by default, or off and switched on by default.

### Maximize self-consumption
In this mode, the devices are boosted when there is a surplus of self-produced energy, and blocked at times of greatest consumption. There are three sub-modes:
1. Schedule only at times of production surplus, but allow offtake from the grid at those times if the surplus is not sufficient to cover the expected consumption of the device.
2. Schedule only if there is sufficient production surplus to cover the entire expected consumption of the device.
3. Preferably schedule when there is a production surplus, but also allow the device to switch on at times of low consumption from the grid.

Modes 1 and 2 are intended for when there may not be sufficient surplus of solar energy, for example in smaller PV installations or during the winter.

All sub-modes work with both blocking and boosting.

### Peakshaving only
In this mode, the devices are boosted when grid consumption falls below an adjustable threshold, and blocked when grid consumption rises above an adjustable threshold.

This mode can be used to avoid exceeding the maximum grid limits.

### Cost optimisation
In this mode, the devices are boosted when the energy is cheapest, and blocked when it is most expensive.

## Control via API
If you have a license to control via API, you have the option to override the standard schedule of the <BrandName /> with your own schedules or those of a third party. In this way, it is possible, for example, to use the <BrandName /> in imbalance markets. Please contact your distributor for more information.

> [!NOTE]
> If control via an external signal is active, it will override the set default control mode. When the external signal is not active, the default control mode is used as a fallback.

## Control without grid energy meter
In certain cases, it is possible to use the <BrandName /> without a grid energy meter. You can only do this when the <BrandName />
- only has to take into account the devices connected to it, and nothing else in your electrical installation. After all, the other consumption is not known by the <BrandName /> if there is no grid energy meter;
- and when there is no need for precise control with feedback control.

Nevertheless, it is always strongly recommended to provide a grid energy meter.

#### APPLICATION EXAMPLE: PV PARK Control
You have a solar panel park without consumers where the <BrandName /> is used for monitoring and control. There are no consumers in the solar park, and you only want to switch off the inverters when energy prices are negative. In this case, all you need to do is connect the inverters to the <BrandName />.


# Extra - Battery charging schedule


import { BrandName, ControllerName, CustomerName, InsightsName, InsightsUrl } from '@site/src/components/customFields';
import Details from '@theme/Details';
import ClickableImage from '@site/src/components/ClickableImage';


# Battery charging schedule
You can set a charging schedule for the global minimum battery charge.

Log in to the <BrandName /> <ControllerName /> and go to ‘Settings’→ ‘Advanced Settings’. Under the ‘Storage state of charge scheduling’ section, you can specify rules for times when the battery charge should have a certain minimum percentage.

<ClickableImage src="/img/generic/charging-planning-en.png" alt="Image 1" maxWidth="650px" />

Keep the following things in mind:

> [!WARNING]
> - The charging schedules requires that a local control mode is set for storage. If set to "Don't control", the charging schedule will not be executed.
> - The charging schedule only works with local control modes, so it may not be executed if there is an external signal active.

> [!NOTE]
> The percentage set is a minimum, but not a maximum. The control algorithm can charge the batteries to a higher percentage if this is deemed more optimal.

> [!NOTE]
> The rules are followed chronologically, and at any time only the rule with the next highest time is active as of that moment.

> [!NOTE]
> When self-consumption is controlled, you may need to define rules not only with high battery percentages, but also with lower battery percentages. Otherwise, the batteries might not discharge on days with little surplus PV production (to meet the next rule set!).

> [!NOTE]
> If you have multiple batteries, the set percentage refers to the battery capacity-weighted average of the percentages of the individual batteries. For example, if you have two 10kWh batteries, one charged to 80% and one to 60%, then the overall battery percentage is 70%.
> However, efforts are made to charge the batteries as evenly as possible, but due to external factors this is not always possible.

> [!NOTE]
> The physical limitations of the system are respected if the rules contradict them. For example, it is impossible to load from 0 to 100 % in a minute.

# Extra - Battery cost optimization settings


import { BrandName, ControllerName, CustomerName, InsightsName, InsightsUrl } from '@site/src/components/customFields';
import Details from '@theme/Details';
import ClickableImage from '@site/src/components/ClickableImage';

# Battery cost optimization settings

When the default working mode of the storage devices is set to **Cost optimization** on the settings page, the box **Choose your cost optimization mode** appears below the dropdown. It decides how the <BrandName /> <ControllerName /> uses the battery to lower the energy bill:

| Mode | When to choose it |
|:--|:--|
| [Predictive AI algorithm](#predictive-ai-algorithm) (default) | Recommended for most sites. The <BrandName /> <ControllerName /> plans the battery with forecasts of the weather, the consumption and the energy prices. |
| [Control manually via fixed rules](#control-manually-via-fixed-rules) | You want predictable behaviour that you set yourself: charge and discharge at fixed price levels and charge levels, without forecasts. |
| [Recharge at low cost and discharge only at the peak shaving discharge thresholds](#recharge-at-low-cost-and-discharge-only-at-the-peak-shaving-discharge-thresholds) | Only offered for the cost optimization partition of the [peak shaving plus](/Controller/Configuration%20from%20A%20to%20Z/8-local-control-modes/extra-peak-shaving-plus/) mode. |

<ClickableImage src="/img/generic/settings/battery-cost-optimization-mode-en.png" alt="The cost optimization modes for storage" maxWidth="550px" />

> [!TIP]
> Cost optimization is only as good as the prices it works with. Check that the energy contract and grid costs are configured correctly in the app, see [Pricing parameters](/Controller/Configuration%20from%20A%20to%20Z/8-local-control-modes/complete-explanation/#pricing-parameters).

After changing any of the settings below, scroll down and click **Save**.

## Predictive AI algorithm

The predictive AI algorithm analyzes the weather and consumption forecasts and combines them with the energy prices to maximize the return of the battery. It continuously calculates the most profitable plan based on the data it has at that moment. Forecasts change during the day, and what actually happens can differ from what was predicted, so a decision that looks wrong afterwards can have been the best one at the time it was made. See [Predictions versus ex-post analyses](/Controller/Configuration%20from%20A%20to%20Z/8-local-control-modes/complete-explanation/#cost-optimisation).

<ClickableImage src="/img/generic/settings/battery-cost-ai-settings-en.png" alt="The predictive AI algorithm settings" maxWidth="550px" />

### Strategy and aggressiveness

| Strategy | Behaviour |
|:--|:--|
| Conservative | Opts for the safest predictions, so that there is always enough energy in the battery, possibly at a slightly lower return. This strategy always charges the battery to a minimum level before high prices start, even when that option is not ticked: it then uses the level entered next to that option (70% unless changed). |
| Balanced (default) | The middle ground between safety and return. |
| Aggressive | Hunts for the highest possible return, with a higher risk that the battery is charged less than ideal when the forecasts turn out wrong. |

### Tuning parameters

| Parameter | Default | Explanation |
|:--|:--|:--|
| Allow energy trading (stop trading below X% charged) | Off, 70% | Allows selling energy from the battery to the grid to maximize profit. When it is off, the battery is only discharged to cover the consumption of the site. Below the chosen state of charge no energy is sold, except in two cases: when negative purchase prices are expected in the next 12 hours, or when the current selling price is higher than the highest purchase price expected in the next 6 hours (the energy can then be bought back for less). |
| Factor battery wear into decisions (X cent/kWh per charging cycle) | On, 4 cent/kWh | The algorithm accounts for this wear cost for every kWh that passes through the battery, on top of the efficiency losses. The battery is only used when the price difference is worth it, so on days with relatively flat prices the battery may not be very active. The settings page warns when the value is above 6 cent/kWh, because the battery would then rarely be used. See [Accounting for the battery wear and efficiency](/Controller/Configuration%20from%20A%20to%20Z/8-local-control-modes/extra-wear-battery/). |
| All PV of the installation is connected to the <BrandName /> <ControllerName /> | Off | Tick this only if all the PV in the electrical installation is connected to the <BrandName /> <ControllerName />. The algorithm then knows that it can curtail PV that would otherwise exceed the grid export limit or inject at negative selling prices. When it is not ticked, the algorithm must assume that there can be PV it does not know of, and therefore that injection beyond the grid export limit or at negative selling prices remains possible. Leave it unticked if you are not sure. |
| Preferentially store excess production immediately in the battery | Off | Charges excess production into the battery immediately, even when the algorithm would rather charge later. This setting is ignored when trading is allowed and the purchase prices are high (otherwise selling would not always be possible), and when negative purchase prices are expected in the next 12 hours (charging at those prices is always better). |
| Make sure that the battery is charged to a minimum level before high prices start (X%) | Off, 70% | Charges the battery to at least this level right before the prices go from low to high, so that the charge is available during the high prices. A transition only counts when there is a noticeable difference between the night and morning prices, or between the afternoon and evening prices. No energy is sold to the grid below this level; it is meant for self-consumption only. |

> [!NOTE]
> - The state of charge of "Allow energy trading" may not be below the one of "Make sure that the battery is charged to a minimum level before high prices start". The page adjusts the values automatically if you enter them the other way around.
> - While the minimum level before high prices applies (the option is ticked, or the Conservative strategy is chosen), selling stops at that level instead of at the level of "Allow energy trading", as long as buying energy costs noticeably more than selling it. The energy above the level kept for the high prices can then be sold.
> - The minimum level before high prices is not applied when negative purchase prices are expected in the next 12 hours, or when a [storage state of charge planning](/Controller/Configuration%20from%20A%20to%20Z/11-Extra-Information/advanced-settings/#storage-state-of-charge-planning) is active. The rules of a state of charge planning are always respected on top of the predictive AI algorithm.

> [!WARNING]
> "Make sure that the battery is charged to a minimum level before high prices start" can keep the battery from discharging during the night before a day with very low prices around noon. The same applies to the Conservative strategy.

## Control manually via fixed rules

The fixed rules take predictable actions: you set exactly what the battery does at which prices and charge levels. The rules do not use forecasts; for more adaptive control, use the predictive AI algorithm.

The price thresholds are set as a number of hours **within each half of the day**: from 00:00 till 12:00 and from 12:00 till 24:00. "The 4 hours of lowest prices" means the 4 cheapest hours of the current half day. This way the rules anticipate both the typical morning peak and the evening peak, also on days when the evening prices are much higher than the morning prices. As soon as the conditions of a rule are met, the battery charges or discharges, either for self-consumption or at the highest possible power, depending on the rule.

<ClickableImage src="/img/generic/settings/battery-cost-fixed-rules-en.png" alt="The fixed rule settings" maxWidth="550px" />

### Charge battery from the grid

| Option | Behaviour |
|:--|:--|
| Never charge from the grid | The battery is only charged with excess PV production. |
| Only charge from the grid at negative purchase prices (default) | The battery charges from the grid at the highest possible power, up to 100%, only when the purchase price is negative, so you get paid for consuming. |
| Smart charging at low purchase prices | The battery charges from the grid at the highest possible power when the purchase price is among the X hours of lowest prices (default 4) and the battery is less than Y% charged (default 50%). At negative purchase prices it charges up to 100%. |

### Charge from excess PV production

| Option | Behaviour |
|:--|:--|
| Always store all excess PV production immediately in the battery (default) | Every bit of excess PV production goes into the battery. |
| Only store PV production that would otherwise be sold at a low price | Excess PV production is only stored when the selling price is among the X hours of lowest prices (default 6), or negative. Otherwise it is sold to the grid. |

### Discharge battery for self-consumption

| Option | Behaviour |
|:--|:--|
| Always discharge for self-consumption (default) | The battery covers the consumption of the site, so that no energy is bought from the grid, except when the purchase price is zero or negative. |
| Only use at a high purchase price | The battery covers the consumption only when the purchase price is among the X hours of highest prices (default 4). It never discharges at a zero or negative purchase price. |

### Discharge battery to sell power to the grid

| Option | Behaviour |
|:--|:--|
| Never sell from the battery (default) | The energy in the battery is only used for self-consumption. |
| Sell at a high selling price | The battery discharges at the highest possible power when the selling price is positive and at least X cent/kWh (default 20) above the lowest selling price of the current half day. It stops below Y% charged (default 70%). |

### How the rules work together

- Grid charging comes first: while the battery charges from the grid, the other rules wait.
- While "Sell at a high selling price" applies, excess PV production is sold to the grid instead of stored, even when the battery has dropped to its minimum level for selling.

> [!NOTE]
> - "Smart charging at low purchase prices" cannot be combined with "Always discharge for self-consumption", as this could lead to ambiguous decisions. The page prevents choosing both.
> - The combined hours of "Smart charging at low purchase prices" and "Only use at a high purchase price" may not exceed 12 hours; the page adjusts the values automatically.
> - If cost optimization is also enabled for PV, the PV is switched off at negative purchase prices, and any excess that cannot be charged in the battery is curtailed so as not to export at negative selling prices.
> - A [storage state of charge planning](/Controller/Configuration%20from%20A%20to%20Z/11-Extra-Information/advanced-settings/#storage-state-of-charge-planning) is not yet fully supported by the fixed rules and can influence their decisions. The settings page shows a warning when both are active.

## Recharge at low cost and discharge only at the peak shaving discharge thresholds

This mode only appears for the cost optimization partition of the [peak shaving plus](/Controller/Configuration%20from%20A%20to%20Z/8-local-control-modes/extra-peak-shaving-plus/) mode. The partition is used for peak shaving only: it is recharged at the cheapest moments, but never discharged for cost reasons, even when prices are high. To keep the risk low, it always recharges within the next 6 hours. This mode has no further settings.

## Related advanced settings

Two advanced settings influence the cost optimization of storage, see [Advanced settings](/Controller/Configuration%20from%20A%20to%20Z/11-Extra-Information/advanced-settings/#battery-control): the size of the self-consumption variability buffer, and whether batteries may be put in standby at low power setpoints.


# Device priorities


import { ControllerName } from '@site/src/components/customFields';
import ClickableImage from '@site/src/components/ClickableImage';
import { PlanningStages, PriorityDecisionFlow, PriorityParkingExample } from '@site/src/components/DevicePriorityGuide';

# Device priorities

When several controllable devices ask for the same limited power, the scheduler needs a consistent order. A device's **priority** is the first decision layer. If two devices have the same priority, SmartgridOne compares their device type and then their control mode.

<PriorityDecisionFlow
  ariaLabel="The three decision layers used to plan controllable devices"
  eyebrow="Planning logic"
  title="Three filters determine who is planned first"
  description="Read the flow from left to right. The scheduler only moves to the next filter when devices are still tied after the previous one."
  levels={[
    { label: "First filter", title: "Device priority", summary: "Your explicit preference is considered before any automatic device rule.", items: ["Highest", "High", "Normal", "Low", "Lowest"] },
    { label: "Second filter", title: "Device type", summary: "Devices with the same priority are ordered by how flexibly SmartgridOne can control them.", items: ["Thermal & switched loads", "Occupied EV chargers", "Storage", "Controlled solar"] },
    { label: "Third filter", title: "Control mode", summary: "Devices of the same priority and type are ordered by the active operating strategy.", items: ["Fixed state", "Active external signal", "Peak shaving", "Self-consumption", "Cost optimisation"] },
  ]}
  resultTitle="The first differing filter decides."
  resultText="Only devices that remain tied continue to the next filter. Priority therefore changes planning order, but it does not bypass grid limits or device safety limits."
/>

## Set a priority on a device

1. Open the commissioning interface and select **Devices**.
2. Open **Change settings** for the controllable device.
3. Select **Highest**, **High**, **Normal**, **Low** or **Lowest** in the **Priority** field and save the settings.

<ClickableImage src="/img/generic/priorities-en.png" alt="Device settings with the priority selector open, showing Lowest, Low, Normal, High and Highest" maxWidth="520px" />

*The default level is Normal. Change it only when the installation needs an intentional preference between controllable devices.*

> [!TIP]
> Start with small differences. Set the most important device to **High** and leave the others at **Normal**. Use **Highest** and **Lowest** only when the operational preference must be unmistakable.

## How the planning order works

SmartgridOne builds the plan in two stages. The first stage handles devices that are available for active planning. The second stage adds solar without an active external curtailment setpoint and EV chargers without a connected vehicle.

<PlanningStages
  ariaLabel="The two stages of the SmartgridOne device planning process"
  eyebrow="Two-stage scheduler"
  title="Plan active devices first, then add deferred devices"
  description="Within each stage, the numbered order is applied before the scheduler moves to the next group."
  areas={[
    { label: "Stage 1", title: "Build the active plan", summary: "Plan controllable devices that can influence the current energy balance.", items: ["Highest to lowest device priority", "Thermal and switched loads", "Occupied EV chargers", "Storage", "Solar with an active external setpoint"] },
    { label: "Stage 2", title: "Add deferred devices", summary: "Complete the plan with devices that are not actively available in the first stage.", items: ["Solar in cost optimisation", "Solar with feed-in restriction", "Unoccupied EV chargers"] },
  ]}
  noteTitle="Priority still applies inside each group."
  noteText="For example, cost-optimised solar devices are ordered by device priority before the scheduler continues with feed-in restriction and then unoccupied chargers."
/>

### Stage 1: active devices

Within the first stage, SmartgridOne applies the following hierarchy:

1. **Device priority:** Highest is considered before High, Normal, Low and Lowest.
2. **Device type:** thermal and relay-switched loads come first, followed by occupied EV charging, storage and solar with an active external setpoint.
3. **Control mode:** fixed states are considered first, followed by an active external signal, peak shaving or load balancing, self-consumption and cost optimisation.

If a solar device has an external signal configured but that signal is not active, local control applies and the device moves to the second stage.

### Stage 2: solar and unoccupied chargers

The second stage is ordered differently:

1. Solar in **cost optimisation**, ordered by device priority.
2. Solar in **feed-in restriction**, ordered by device priority.
3. EV chargers without a connected vehicle, ordered by device priority.

## Example: prioritise a frequently used charger

Imagine a workplace with three charging points and limited power at the grid connection. The vehicle used by field staff should be ready first. Give its charger a higher priority and leave the other chargers at their normal or lower setting.

<PriorityParkingExample
  ariaLabel="Example of three EV chargers evaluated in priority order"
  eyebrow="Worked example"
  title="Make the operational preference visible"
  description="The available grid power remains the same. Priority changes the sequence in which the chargers are evaluated when they compete for that power."
  powerLabel="Illustrative available power"
  powerValue="22 kW"
  levels={[
    { label: "Highest priority", title: "Field-service vehicle", summary: "Evaluated first because this vehicle is needed for daily operations.", items: ["Most urgent charging need"] },
    { label: "Normal priority", title: "Employee vehicle", summary: "Evaluated after the higher-priority charger.", items: ["Standard charging preference"] },
    { label: "Low priority", title: "Visitor vehicle", summary: "Evaluated last while the power budget is constrained.", items: ["May receive power later"] },
  ]}
  resultTitle="Priority defines the queue, not a guaranteed power allocation."
  resultText="The actual result still depends on connected vehicles, their charging limits, the active control mode, other site loads and the configured grid limits."
/>

## Measurement matters for fixed loads

Heat pumps, boilers and on/off loads do not always report their own consumption. If the load is not measured by the device or by a dedicated energy meter, the <ControllerName /> sees that consumption as part of the building's base load and cannot reliably use it in device-priority planning.

> [!IMPORTANT]
> Add a dedicated measurement when the scheduler must distinguish a fixed load from the rest of the building. Without that measurement, changing its device priority cannot create information that the controller does not have.


# Extra - Battery peak shaving


import { BrandName, ControllerName, CustomerName, InsightsName, InsightsUrl } from '@site/src/components/customFields';
import Details from '@theme/Details';
import ClickableImage from '@site/src/components/ClickableImage';

# Battery peak shaving

> [!NOTE]
> When peakshaving is used with batteries, the grid power is regulated to zero by default. This means that all excess self-generation goes to the battery, and any shortfall in generation when consumed is supplied from the battery.

Alternative threshold values can be set from which grid power the battery should charge or discharge.

Log in to the <BrandName /> <ControllerName /> and go to Settings. If you switch the default working mode to "Peak shaving only" for batteries, then the following options will become available:

|Option|Impact|
|:--|:--|
|Start discharging above (kW)|Grid power above which the battery will start discharging. The grid power is also tuned down to this power when discharging.|
|Stop discharging below (kW)|Grid power below which a battery that is discharging will stop discharging.|
|Stop charging above (kW)|Grid power above which a battery that is charging will stop charging.|
|Start charging below (kW)|Grid power under which the battery will start charging. The grid power is also adjusted to this power when charging.|

In the example on the image will:
- A battery starts discharging as soon as the grid power rises above 10kW.
- A battery that is discharging stop discharging as soon as the grid power drops below 8kW.
- A battery starts charging as soon as the grid power drops below -1kW (i.e., at 1kW feed-in)
- A battery that is charging stop charging as soon as the grid power rises above 0kW.

<ClickableImage src="/img/generic/battery-peak-shaving-en.png" alt="Image 1" maxWidth="350px" />


# Extra - Peak shaving plus (secondary control mode)


import { BrandName, ControllerName, CustomerName, InsightsName, InsightsUrl } from '@site/src/components/customFields';
import Details from '@theme/Details';
import ClickableImage from '@site/src/components/ClickableImage';

# Peak shaving plus: a secondary control mode for the battery

> [!WARNING]
> This function is currently available for public testing only (public beta). Future access may be subject to an additional license.

When the default working mode of the storage devices is "Peak shaving", the battery normally does nothing else than shaving the grid peaks between the [peak shaving thresholds](/Controller/Configuration%20from%20A%20to%20Z/8-local-control-modes/extra-peak-shaving-battery/). With a **secondary control mode**, the battery does something useful in the meantime: a part of the battery, the **critical reserve**, is reserved exclusively for peak shaving, and the rest of the battery is controlled according to the secondary control mode, cost optimization or self-consumption optimization.

**Peak shaving is always guaranteed.** When the grid power exceeds the peak shaving thresholds, the <BrandName /> <ControllerName /> shaves the peak with the whole battery, not only with the critical reserve: the partition of the secondary control mode is used for peak shaving first, and only when that partition is empty, the critical reserve is used. The critical reserve is therefore the energy that is still available for peak shaving in the worst case, after the secondary control mode has emptied its own partition. The secondary control mode itself never touches the critical reserve.

## Settings

On the settings page, with "Peak shaving" selected for the storage devices, the option "Secondary control mode (public beta)" appears below the dropdown:

| Option | Behaviour |
|:--|:--|
| Peak shaving only / no secondary control mode (default) | The whole battery is used for peak shaving. |
| Cost optimization | A reserved partition is used for peak shaving, the rest follows the [cost optimization settings](/Controller/Configuration%20from%20A%20to%20Z/8-local-control-modes/extra-battery-cost-optimization/) that appear under "Cost optimization partition settings". |
| Self-consumption optimization | A reserved partition is used for peak shaving, the rest maximizes self-consumption. |

<ClickableImage src="/img/generic/settings/peak-shaving-secondary-mode-en.png" alt="The secondary control mode and the critical reserve" maxWidth="550px" />

### Critical reserve

The **critical reserve** is the battery partition reserved exclusively for peak shaving, as a percentage of the total battery capacity (at least 10%, 40% by default). The secondary control mode never discharges the battery below the top of this partition. Peak shaving does use the reserve, but only after the partition of the secondary control mode is empty and as long as the grid power exceeds the peak shaving thresholds. The reserve is recharged as soon as the grid power drops below the "Start charging below" threshold, so that it is full again for the next peak.

> [!NOTE]
> The percentage goes on top of the minimum battery state of charge. If the minimum state of charge of the battery is 20% and the reserved part is 40%, the reserved part lies between 20% and 60% of the real battery.

### Recharging the partition at low prices only

For the cost optimization partition, the mode "Recharge at low cost and discharge only at the peak shaving discharge thresholds" is available among the cost optimization modes. The whole battery is then used for peak shaving only: the critical reserve is kept full whenever possible, and the cost optimization partition is recharged when the prices are low, but it is never discharged for cost reasons, even when the prices are high and the local demand is low.

## Related

- On Swiss sites, the [capacity tariff schedule](/Controller/Configuration%20from%20A%20to%20Z/11-Extra-Information/advanced-settings/#capacity-tariff-schedule-switzerland) switches the batteries to peak shaving plus during the capacity tariff periods only, with the same critical reserve.
- The peak shaving thresholds themselves are explained in [Battery peak shaving](/Controller/Configuration%20from%20A%20to%20Z/8-local-control-modes/extra-peak-shaving-battery/).


# Extra - Reactive power control


import { BrandName, ControllerName, CustomerName, InsightsName, InsightsUrl } from '@site/src/components/customFields';
import Details from '@theme/Details';
import ClickableImage from '@site/src/components/ClickableImage';

# Reactive power control

> [!WARNING]
> Reactive power control is only possible with certain device brands. Contact your reseller for more information.

### Enabling reactive power control
In the commissioning interface, go to the "Settings" tab, scroll down to "Advanced Settings" and open the Advanced Settings.

<ClickableImage src="/img/generic/reactive-power-control.png" alt="Reactive power control settings" maxWidth="800px" />
Here you can Enable reactive power control. When reactive power control is enabled, a few options will appear.

### Grid limits
- Allowed grid import reactive power (kVAr): Maximum kVAr that may be imported from the grid.
- Allowed grid export reactive power (kVAr): Maximum kVAr that may be exported to the grid.

### Reactive power peakshaving settings
- Start generating reactive power above (kVAr): When the imported grid reactive power rises above this value, the inverters will start producing reactive power to limit the grid reactive power to this value.
- Stop generating reactive power below (kVAr): When the imported grid reactive power drops below this value, the inverters will stop producing reactive power.
- Stop consuming reactive power above (kVAr): When the imported grid reactive power rises below this value, the inverters will stop consuming reactive power.
- Start consuming reactive power below (kVAr): When the exported grid reactive power goes below this value, the inverters will start consuming reactive power to limit the grid reactive power to this value.

The reactive power peak shaving settings are similar to the settings for peak shaving of active power.

> [!TIP] Reactive power compensation
> To aim towards complete reactive power compensation, set all the reactive power peak shaving settings to zero.

# Extra - Self consumption on another meter than the grid meter


import { BrandName, ControllerName, CustomerName, InsightsName, InsightsUrl } from '@site/src/components/customFields';
import Details from '@theme/Details';
import ClickableImage from '@site/src/components/ClickableImage';

# Self-consumption on a separate meter

Use a separate power meter as the reference for self-consumption optimization instead of the main grid meter. This lets you exclude a specific part of the installation from self-consumption control while keeping the import and export limits at the grid connection in place.

## How it works

The two meters have different roles:

- **Grid meter:** measures the entire installation and guards the import and export limits at the grid connection.
- **Self-consumption meter:** defines the part of the installation used for self-consumption optimization.

<ClickableImage src="/api/media/controller/configuration-from-a-to-z/8-local-control-modes/extra-self-consumption-on-another-meter/self-consumption-meter.png" alt="Grid meter upstream of two branches: a solar sub-site excluded from self-consumption, and a self-consumption meter serving the battery, main solar installation and consumption. Grid import and export limits apply to the entire installation." maxWidth="1000px" />

*The solar sub-site branches off before the self-consumption meter. The battery, main solar installation and consumption are within the self-consumption scope.*

For example, a solar sub-site may have a separate contract with a fixed export tariff. You can exclude that solar production from self-consumption optimization while the grid meter continues to guard the limits for the entire installation.

## Before you start

- Install both a **grid meter** and an additional **power meter** in the installation.
- The additional meter must measure the part of the installation you want to use for self-consumption control.
- This feature is **disabled by default**.

## Configuration

1. **Open Advanced settings.** On the settings page, scroll down to **Advanced settings**.

   <ClickableImage src="/img/generic/advanced_settings.jpg" alt="Advanced settings section on the settings page" maxWidth="550px" />

2. **Enable the feature.** Check the option to use another meter for self-consumption. This is only available when at least one additional meter is installed alongside the grid meter.

   <ClickableImage src="/img/generic/self-consumption-am1.jpg" alt="Checkbox to enable self-consumption on another meter" maxWidth="650px" />

3. **Select the self-consumption meter.** Choose the additional power meter that defines the intended scope. The grid meter cannot be selected.

   <ClickableImage src="/img/generic/self-consumption-am2.jpg" alt="Meter selection for self-consumption control" maxWidth="650px" />

4. **Save your changes.** Click **Save**.

> [!NOTE]
> If the self-consumption meter is removed and re-added, this feature is automatically disabled.


# Extra - Battery account for wear and efficiency


import { BrandName, ControllerName, CustomerName, InsightsName, InsightsUrl } from '@site/src/components/customFields';
import Details from '@theme/Details';
import ClickableImage from '@site/src/components/ClickableImage';

# Accounting for the battery wear and efficiency

The <BrandName /> <ControllerName />'s control algorithm, when set to cost optimization, takes into account battery efficiency, as well as a minimum price difference (between less expensive and more expensive moments) that must be present before the <BrandName /> <ControllerName /> will use the battery. You can use that minimum price difference to factor in battery wear.

You can set the efficiency under the "Devices"→"Change settings" tab under the corresponding battery→"Roundtrip efficiency (%)."

The minimum price difference for using the battery can be set under the "Settings"→"Minimum price difference between peak and off-peak for use of storage (EUR/kWh)". This option is visible if cost optimization is active for storage.

> [!NOTE]
> **Please note**: The control algorithm will only utilize the battery when controlling for cost optimization if the price of the energy with which it is charged is sufficiently lower than the price of the energy at the scheduled time of discharge.
>
> This takes **both into account** the **stated minimum price difference** and the **efficiency of the battery**. After all, the losses when charging/discharging the battery also have a cost.
>
> The price of the charged energy depends on:
> - Whether the charged energy comes from its own production (then the selling price of the energy to the grid is used)
> - Whether the charged energy comes from the grid (then the purchase price of energy from the grid is used)
> - Battery wear cost
> - Battery efficiency
>
> **Example:**
>
> If the purchase price of energy from the grid is 0.20 EUR/kWh at time B, and the battery has an efficiency of 80%, and a minimum price differential of 0.04 EUR/kWh is set, then the battery will only charge at an earlier time A to cover the consumption at that purchase price at time B as soon as the purchase price at the time A of charging is lower than:\
> 0.20 EUR/kWh - 0.20 EUR/kWh*(1-0.80) - 0.04 EUR/kWh = 0.11 EUR/kWh.
>
> **Consequences:**
>
> This may mean that during periods of long-term stable prices, the battery is hardly ever used. After all, the difference between the minimum and maximum energy price is then potentially rarely greater than the utility cost of the battery.

# 8 Local Control Modes


import { FolderOverview } from '@/components/FolderOverview';

# 8 Local Control Modes

<FolderOverview folder="Controller/Configuration from A to Z/8-local-control-modes" />


# Setting control modes


import { BrandName, ControllerName, CustomerName, InsightsName, InsightsUrl } from '@site/src/components/customFields';
import Details from '@theme/Details';
import ClickableImage from '@site/src/components/ClickableImage';
import PdfLink from '@site/src/components/PdfLink';

# Setting the local control modes

## Setting the control modes
> [!NOTE]
> The default control modes are requested during the initial setup. You can change them later under the "Settings" menu.

> [!WARNING] external signals
> If external control signals (Yuso, Edmij, Frank Energie, ...) are active, the external control signal has priority and the default control modes will be used as fallback.

> [!TIP] Full explanation
> Below is a brief description of the available control modes.
> For more information, see the document "<PdfLink url="/docs/eniris/control-modes-en.pdf">Control modes of the <BrandName /> <ControllerName /></PdfLink>".

Under "Default working mode" choose for each type of device which type of control mode you want to use.

<ClickableImage src="/img/generic/control-modes-en.png" alt="Image 1" maxWidth="350px" />

### STORAGE DEVICES (BATTERY SYSTEMS)
- **Don't control**: No active control. (Note that this can be overwritten by an external signal).
- **Self-consumption optimalization**: Charging when there is excess solar power, and discharging when energy is taken from the grid.
- **Cost optimalization**: Charge with the least expensive possible energy, and cover consumption at the most expensive times. You can optionally allow energy trading.
- **Peak shaving only**: Discharge at times of peak consumption from the grid, and charge at off-peak times. You can set your own threshold values for this.
- **Exclusive control through external API**: Only charge and discharge according to external control signals.

### PRODUCTION DEVICES
- **Don't control**: No active control. (Note that this can be overwritten by an external signal).
- **Cost optimalization**: PV production is turned off at negative purchase prices (you are then paid to consume), and limited to your energy consumption at negative sales prices (you pay to inject your surplus). At other times, PV production is limited to allowable feed-in power.
- **Feed in restriction till allowed grid export power**: Limit PV production to the allowed grid export power.
- **Exclusive control via external API**: Only limit PV production according to external control signals.

### EVs (ELECTRIC VEHICLES)
> [!NOTE] Minimum charging current
> Most electric vehicles always require a minimum charging current of 6A. So possibly charging is not reduced to zero when ideally it should be.
- **Don't control**: No active control. (Note that this can be overwritten by an external signal).
- **Self-consumption optimalization**: Charging when there is excess solar power.
- **Cost optimalization**: Charge with the least expensive possible energy.
- **Peak shaving only**: Limit charging to the maximum allowed grid import power.

### HEAT PUMPS, BOILERS AND ON/OFF LOADS
- **Don't control**: No active control. (Note that this can be overwritten by an external signal).
- **Self-consumption optimalization**: Prefer consumption when there is surplus solar energy. There are three submodes:
    - Only schedule when there is surplus production, but still allow that switching the heat pump / boiler or on/off load on causes import from the grid.
    - Only schedule when there is sufficient surplus production to not cause import from the grid.
    - Prefer scheduling at moments of surplus production, but also schedule at moments of low import.
- **Cost optimalization**: Prefer consumption with the least expensive possible energy.
- **Peak shaving only**: Limit consumption when grid power exceeds a threshold.
- **Always powered on**: Always on unless overridden by an external control signal.
- **Always powered off**: Always off, unless overridden by an external control signal.

# Boiler schedule


# Boiler schedule

Use a boiler schedule to define recurring periods in which SmartgridOne must force a connected boiler on or off. Outside those periods, the boiler returns to the site's default control strategy.

> [!NOTE]
> This mode is intended for devices configured as a **boiler** in SmartgridOne. If a thermal load is configured as a relay, contactor or smart socket instead, use the [Switched load schedule](./switched-load-schedule).

## Available modes

| Scheduled mode | Behaviour during the window | Typical purpose |
| --- | --- | --- |
| **Force on** | Requests the selected boiler to run. | Heating water before a peak-price or grid-congestion period. |
| **Force off** | Requests the selected boiler to stop. | Avoiding consumption during a defined period. |
| **Follow default control** | Uses the site's normal SmartgridOne control strategy. | Returning explicitly to the standard energy-management behaviour. |

The boiler's own thermostat, temperature limits and safety functions remain responsible for safe operation.

## Configure the schedule

1. Open the commissioning interface and go to **Settings** > **Special local control modes**.
2. Start the configuration wizard and select **Boiler schedule**.
3. Add one or more rules with the required weekdays, active months or date period, start time, end time and mode.
4. Select the boilers that the schedule may control.
5. Position the schedule in the **External signals** priority list and save the configuration.

## How time windows work

- Rules run in the site's configured local time zone and follow daylight-saving-time changes.
- The start time is included and the end time is excluded.
- A rule cannot cross midnight. Create two rules for an overnight period.
- Rules in the same schedule may not overlap.
- If no rule matches, the boiler follows the site's default control strategy.

### Example: prepare domestic hot water off-peak

| Days | Time | Mode | Purpose |
| --- | --- | --- | --- |
| Every day | 13:00–15:00 | Force on | Use the expected solar-production period. |
| Monday–Friday | 17:00–20:00 | Force off | Avoid the evening peak. |
| All other times | — | Default control | Resume normal site optimisation. |

## Interaction with other controls

The boiler schedule is part of the external-signal priority system. A higher-priority signal overrides a lower-priority request.

Forced on and off commands are manual overrides. Normal minimum and maximum on, off or waiting times do not delay a forced schedule transition. SmartgridOne accounts for the requested boiler load before planning flexible assets such as EV chargers, batteries and PV control.

> [!CAUTION]
> Make sure the schedule still provides enough heating time for the installation. Avoid rapid cycles and follow the boiler manufacturer's operating requirements.

## Troubleshooting

### No boiler appears in the device selection

Confirm that the device is configured with the boiler node type. Relay-controlled loads appear under the switched load schedule instead.

### The schedule is active but the boiler does not run

Check the boiler's thermostat, temperature limit and local safety conditions. Then review the device connection and the schedule status.

### Another signal controls the boiler

Review the **External signals** priority order. The highest-priority active request determines the resulting mode.


# Green certificates (Groenestroomcertificaten)


import { BrandName, ControllerName } from '@site/src/components/customFields';


# Introduction

## What are green certificates?

Green certificates are a **Belgian** support scheme for renewable electricity production. They are granted per amount of electricity that an installation actually **produces**, and can then be sold, so they form a production-based income for the owner of the installation. Because of this, every megawatt-hour of curtailed solar production is lost certificate income, and owners of installations that receive green certificates usually want those inverters to keep producing at full power at all times.

The scheme is organised per region, each with its own rules and its own name. It is being **phased out**: newer installations no longer receive green certificates, but older installations keep receiving them for the duration of their support period (which can run for many years). The cut-off dates differ per region:

- **Flanders**: *groenestroomcertificaten*, see the [Flemish government's information page](https://www.vlaanderen.be/groenestroomcertificaten-voor-zonnepanelen) and the [Fluvius page on green certificates](https://www.fluvius.be/nl/groene-energie/zonnepanelen-geinstalleerd/groenestroomcertificaten). Small solar installations (up to 10 kW) commissioned after 14 June 2015 receive no certificates, and no new solar installations commissioned after 16 July 2021 do.
- **Wallonia**: *certificats verts*, managed by the public service SPW Energie, see [energie.wallonie.be](https://energie.wallonie.be/). Small solar installations (up to 10 kW) commissioned after 28 February 2014 (the end of the Solwatt scheme) receive no certificates; larger installations can still qualify.
- **Brussels**: *certificats verts / groenestroomcertificaten*, managed by the regional regulator, see [Brugel](https://www.brugel.brussels/themes/energies-renouvelables-11/certificats-verts-35). Here the scheme is still active for new installations; it is expected to be replaced by another support mechanism in 2028 at the earliest.

> [!NOTE]
> If your site is not in Belgium, this control mode is most likely not relevant for you.

## What this control mode does

The *Green Certificates - Inverters Driver* is a special local control mode that forces the selected solar inverters to always produce at their full nominal power. The selected inverters are never curtailed by the <BrandName /> <ControllerName />; other devices on the site remain controlled as usual.


# Configuring the special control mode

## Solar inverters

Make sure that the solar inverters that receive green certificates are added to the <BrandName /> <ControllerName />.

## Enabling the special control mode

1. Go to the 'Settings' tab on the <BrandName /> <ControllerName />'s interface and click 'Manage special local control modes'.
2. Click 'Start wizard' under 'Enable a new special local control mode'.
3. Choose 'Green Certificates - Inverters Driver' and click 'Next'.
4. Select the solar inverter(s) that receive green certificates and must never be curtailed, and click 'Apply mode to selected devices'.

See [Special local control modes](/Controller/Configuration%20from%20A%20to%20Z/8-local-control-modes/special-local-control-modes/) for the priority towards other signals, and for pausing or removing the mode.


# Heat pump schedule


# Heat pump schedule

Use a heat pump schedule when the heat pump should follow a predictable weekly routine. During a scheduled window, SmartgridOne can force a selected operating mode. Outside those windows, the heat pump returns to the site's default control strategy.

> [!NOTE]
> A schedule is a control instruction, not a replacement for the heat pump's own safety limits, thermostat or frost protection. The result also depends on the control functions supported by the connected model.

## Available modes

| Scheduled mode | Behaviour during the window | When to use it |
| --- | --- | --- |
| **Force boost** | Requests the heat pump's boost or maximum-heating mode. | Preheating a building or thermal buffer before a known peak period. |
| **Force block** | Requests the heat pump's blocking mode. | Avoiding consumption during an expensive or constrained period. |
| **Force self control** | Hands operation to the heat pump's own controller or thermostat. | Keeping comfort control local during a specific period. |
| **Follow default control** | Uses the site's normal SmartgridOne control strategy. | Creating an explicit return to the standard energy-management behaviour. |

If the selected heat pump cannot execute **Force boost** or **Force block**, SmartgridOne falls back to self control. The status message identifies the affected device so that you can verify its supported functions.

## Configure the schedule

1. Open the commissioning interface and go to **Settings** > **Special local control modes**.
2. Start the configuration wizard and select **Heat pump schedule**.
3. Add one or more rules. For every rule, select the weekdays, the active months or date period, the start time, the end time and the required mode.
4. Select the heat pumps that the schedule may control.
5. Position the schedule in the **External signals** priority list and save the configuration.

> [!TIP]
> Start with a short test window and verify the reported device state before applying the schedule to every weekday.

## How time windows work

- The schedule uses the site's configured local time zone and follows daylight-saving-time changes.
- The start time is included; the end time is excluded. A rule from 09:00 to 10:00 is active at 09:00, but no longer at 10:00.
- A time window cannot cross midnight. Split a 22:00–06:00 period into a 22:00–24:00 rule and a 00:00–06:00 rule.
- Rules for the same schedule may not overlap.
- When no rule matches, the heat pump follows the site's default control strategy.

### Example: preheat before the evening peak

| Days | Time | Mode | Purpose |
| --- | --- | --- | --- |
| Monday–Friday | 15:00–17:00 | Force boost | Build thermal reserve before the evening peak. |
| Monday–Friday | 17:00–19:00 | Force block | Reduce heat-pump demand during the peak period. |
| All other times | — | Default control | Resume the site's normal optimisation. |

## Interaction with other controls

The heat pump schedule participates in the site's external-signal priority system. If two signals request different actions, the signal with the higher configured priority wins.

Forced schedule modes are treated as manual overrides. Normal minimum and maximum boost, block, on, off or waiting times do not restrict a forced transition. The controller plans the resulting fixed load before flexible assets such as EV chargers, batteries and PV control, allowing those assets to compensate where possible while respecting the grid limits.

> [!CAUTION]
> Frequent switching can reduce comfort or conflict with manufacturer recommendations. Choose practical windows and confirm that the heat pump and installation are suitable for the intended control pattern.

## Troubleshooting

### The rule does not become active

Check the site's time zone, selected weekdays, active month or date period, and start and end time. Also confirm that a higher-priority external signal is not overriding the schedule.

### Boost or block is not applied

Confirm that the exact heat-pump model and integration support the requested function. Unsupported boost or block commands fall back to self control.

### The heat pump keeps following another control source

Review the **External signals** priority order and the schedule's status message. A higher-priority signal can legitimately take control.


# Special Local Control Modes


import { BrandName, ControllerName } from '@site/src/components/customFields';
import ClickableImage from '@site/src/components/ClickableImage';
import { FolderOverview } from '@/components/FolderOverview';
import YouTubeEmbed from '@site/src/components/YouTubeEmbed';

# Special local control modes

Special local control modes are control modes for specific, less common situations: for example keeping inverters that receive green certificates at full power, switching a generator on with a relay when the batteries run empty, or excluding a few devices from control. They run locally on the <BrandName /> <ControllerName /> and do not talk to an external party, but they behave like external signals: they override the default working mode of the devices they are applied to, and they take a place in the priority list of the external signals.

For a rule built from measurements, conditions and actions, see [Custom control logic](#custom-control-logic) below, including the full video walkthrough.

## Available modes

<FolderOverview folder="Controller/Configuration from A to Z/8-local-control-modes/special-local-control-modes" />

Two more special local control modes are documented under the external signals, because they serve test purposes or belong with the price based signals:

- [Diagnostic tests](/Controller/External%20Signals/diagnostic-tests/): charge and discharge test curves for batteries.
- [EPEX SPOT solar curtailment](/Controller/External%20Signals/epex-spot-solar/): curtails PV inverters when the day-ahead price drops below a threshold.

## Managing the special local control modes

1. Go to the 'Settings' tab of the commissioning interface and scroll to the section "Special local control modes". It lists the modes that are active on this site, and whether they are paused.
2. Click "Manage special local control modes". The page that opens shows the active modes with their devices and status, and lets you pause, resume, edit or delete each of them.
3. To add a mode, click "Start wizard" under "Enable a new special local control mode", choose the mode from the list and click "Next".
4. Fill in the inputs of the mode, if it has any (for example the state of charge thresholds of a relay mode).
5. Select the devices to which the mode applies. By default "Select all" and "Always apply this special local control mode to all devices that are compatible with it, including devices that are newly added later" are ticked, so the mode covers every compatible device, now and in the future. To apply the mode to specific devices only, untick both options and tick the devices one by one. Click "Apply mode to selected devices".

<ClickableImage src="/img/generic/settings/special-local-control-modes-box-en.png" alt="The special local control modes section on the settings page" maxWidth="550px" />
<ClickableImage src="/img/generic/settings/special-local-control-modes-page-en.png" alt="The management page of the special local control modes" maxWidth="750px" />
<ClickableImage src="/img/generic/settings/special-local-control-modes-wizard-en.png" alt="The list of special local control modes in the wizard" maxWidth="550px" />
<ClickableImage src="/img/generic/settings/special-local-control-modes-devices-en.png" alt="Selecting the devices of a special local control mode" maxWidth="650px" />

> [!TIP]
> The same modes can also be reached from the 'External signals' tab: click "Start wizard", choose the category "Special local control modes", choose the provider (usually "Generic" or "Eniris") and then the mode. Both routes lead to the same configuration.

> [!CAUTION]
> Every special local control mode can only be enabled once per site. Enabling it again overwrites the previous configuration. Use "Edit special local control mode" on the management page to change the devices of an active mode.

## Priority towards external signals

A device can be part of several external signals and special local control modes at the same time. The signal that is highest in the priority list of the 'External signals' tab wins for that device. Special local control modes share this list with the external signals, and their priority is changed there: the management page of the special local control modes only shows them, in the order of their priority, without the arrows.

## Pausing a mode

"Pause" on the management page temporarily suspends a mode without deleting its configuration: the devices fall back to the next signal in the priority list, or to the default working mode. "Resume" activates it again. A paused mode is marked "(Paused)" on the settings page.

## Custom control logic

Custom control logic lets you build your own rules on the <BrandName /> <ControllerName />. Combine measurements, device states, energy prices and time conditions with visual blocks, then use the result to select a control mode, request a device action, set a power limit or send a message.

The logic runs locally on the controller, once per control cycle. A useful starting point is: **read a value → decide when a rule applies → request an action**.

> **Public beta:** in the version shown here, this feature is a pre-release for testing. It may still contain bugs and should not yet be used for critical production installations.

### Video walkthrough

This Dutch-language course shows the commissioning interface, a practical control-mode example, the available blocks and how to check, preview and save your design.

<YouTubeEmbed videoId="dTNQ3z2aek4" title="Custom Control Logic walkthrough" />

Video chapters: [Access and editor — 00:00](https://www.youtube.com/watch?v=dTNQ3z2aek4&t=0s) · [Control modes and example — 01:51](https://www.youtube.com/watch?v=dTNQ3z2aek4&t=111s) · [Outputs and messages — 07:04](https://www.youtube.com/watch?v=dTNQ3z2aek4&t=424s) · [Measurements — 10:33](https://www.youtube.com/watch?v=dTNQ3z2aek4&t=633s) · [Time and signals — 20:14](https://www.youtube.com/watch?v=dTNQ3z2aek4&t=1214s) · [Comparison and math — 26:18](https://www.youtube.com/watch?v=dTNQ3z2aek4&t=1578s) · [Logic — 31:19](https://www.youtube.com/watch?v=dTNQ3z2aek4&t=1879s) · [Checking and managing — 34:06](https://www.youtube.com/watch?v=dTNQ3z2aek4&t=2046s).

### Open the editor

1. In the **SmartgridX platform**, open **Settings**, select the controller under **Current Site** and open **Controller Configuration**. See [Accessing the commissioning interface](/Controller/Configuration%20from%20A%20to%20Z/2-accessing-commissioning-interface/) for the available access routes.
2. In the controller's commissioning interface, select **Settings**. Scroll to **Custom control logic** and select **Open logic editor**.
3. If the feature is not enabled yet, select **Enable the custom control logic** and complete the activation. The editor then opens.

The block library is on the left, the canvas in the centre and **Problems** on the right. The toolbar contains editing, validation, live-value and file controls. The bottom status bar shows whether changes have been saved and which live values are being displayed.

Drag a block onto the canvas. Double-click it, or select **Parameters**, to choose devices and enter settings. **Apply** updates the block in your design; **Save** activates the saved design on the controller. Connect an output on the right of one block to a compatible input on the left of another. Each input accepts one wire; connecting a new wire replaces its previous connection.

### Start with a control mode

**Control modes** select how the chosen devices should be regulated while the block is active. The device selector only offers devices that support that mode.

- **Power setpoint:** request a power level. Positive power means consumption or battery charging; negative power means production or battery discharging. A setpoint for several devices is shared according to their nominal power.
- **Self-consumption:** use local production as effectively as possible.
- **Cost optimization:** let the devices follow the lowest-energy-cost plan.
- **Peak shaving:** let devices act to keep grid power within the relevant thresholds and limits. Thresholds supplied by this block apply across the site to devices in peak shaving.
- **Feed-in restriction:** limit solar, wind or water production to keep grid export within the permitted power.
- **Don't control:** let the selected devices operate without <BrandName /> control while this block is active.

An unconnected **Active** input means the output block is always active. Connect a true/false condition when the request should apply only at certain times. If the block is inactive or a required value is missing, it makes no request. The applicable default control or other control requests can then take over.

#### Example: request battery charging from 12:00 to 14:00

1. Add **Time schedule**. Select the required weekdays and enter **12:00–14:00**. The schedule uses the site's timezone.
2. Add **Constant** and enter **2 kW**.
3. Add **Power setpoint** and select a compatible battery in its parameters.
4. Connect the schedule output to **Active**, and the constant output to **Setpoint**.
5. Use **Check**, inspect the result with **Live values**, then use **Save** when the design is ready to become active.

During the selected period, the block requests 2 kW of charging, subject to the device's capabilities, applicable limits and control priorities. Outside that period, this block stops requesting the setpoint. It does not force the battery to stop or request 0 kW.

### Choose the building blocks

Use the search field to find a block. Each parameter dialog explains what the block does. Besides **Control modes**, the library contains these groups:

- **Control outputs:** request heat-pump modes, switch relays, select EV charging phases, or set grid and device power limits. Use these for a specific action or limit.
- **Messages:** show a status message or send an e-mail, HTTP request or MQTT message when a condition applies. Configure repeat behaviour and the minimum interval where available. A message block's **Test** action sends a real test message.
- **Measurements:** read grid, device or category power, state of charge, nominal power and temperatures. **Device has data** checks freshness; **History** reads an earlier measurement; **Grid power forecast** supplies a forecast.
- **Device states:** read relay and digital-input states, heat-pump mode, EV connection and the number of charging phases.
- **Prices:** use the current price, a price at another time, its percentile rank, or the lowest/highest price within a window.
- **Time:** use a weekly **Time schedule** or **Daytime** condition.
- **Constants:** provide a fixed number with the appropriate unit, or a fixed true/false value.
- **Comments:** explain the purpose of a rule directly on the canvas.
- **Timing:** reject short fluctuations, delay a signal, enforce minimum/maximum on and off times, count run time or energy, or remember the preceding cycle's value.
- **Signal shaping:** smooth measurements, limit how fast a value changes, protect switching behaviour or enforce a minimum operating value.
- **Routing:** allocate a value between outputs, choose which input passes through, gate or switch a signal, or replace a missing value.
- **Compare:** compare two values or use **Hysteresis** with separate upper and lower thresholds to avoid repeated switching around one boundary.
- **Math:** add, subtract, multiply, divide, limit and scale values, or use integration, differentiation and proportional calculations.
- **Logic:** combine true/false conditions with **AND**, **OR**, **XOR** and **NOT**; count true inputs, detect an edge or hold a state with **Latch**.

Choose compatible signal types and units. **False**, **zero** and **no value** have different meanings. Use **Replace missing value** only when you have deliberately chosen a suitable fallback. A dashed feedback wire uses the preceding execution's value; **Memory** makes that delay explicit.

### Check, preview and activate

The editor checks the design after changes. Select **Check** to validate it again, then inspect **Problems**. Clicking an issue brings you to the relevant block or connection. Resolve errors before activation; a design with errors can be stored, but it will not run.

**Live values** shows the values calculated by the controller. Green means true, red means false and grey means no value. Unsaved changes are evaluated as a preview with dashed markings and **Would command** output descriptions. The preview itself does not command devices or send messages. Check the status bar and timestamp to distinguish preview values from those of the saved logic.

**Save** stores the design and restarts the controller's control loop to run it. Review the resulting live values afterwards. Where several output blocks request the same device setting, their block priorities determine which request takes precedence; configured grid limits still apply.

### Edit and reuse a design

Use **Undo**, **Redo**, **Duplicate** and **Delete** while editing, and **Zoom in**, **Zoom out** or **Fit to screen** to navigate. **Help** explains the editor, signal types and shortcuts.

**Export** downloads the current design as a JSON file, including unsaved edits but excluding passwords. **Import** loads a file into the editor; it does not activate it. Check device selections, parameters, required credentials and **Problems**, then use **Save** when ready. Keep an export of a working design before making substantial changes.


# Monitoring only (don't control the selected devices)


import { BrandName, ControllerName } from '@site/src/components/customFields';


# Introduction

## What this control mode does

The *Monitoring only* special local control mode excludes the selected devices from control. The devices stay on the <BrandName /> <ControllerName /> like any other device: they are read out, their measurements are stored and shown, and they count in the site totals and in the grid limits. But the <BrandName /> <ControllerName /> never steers them. Every selected device is treated exactly like a device whose control mode is set to *don't control*, while all the other devices on the site remain controlled as usual.

What that means per device type:

- **EV chargers**: the charger may charge at its full current; the <BrandName /> <ControllerName /> never lowers it. This also holds when the other chargers of the site are being load-balanced or limited by an external signal.
- **Solar inverters**: the inverter may produce at full power and is never curtailed.
- **Batteries**: nothing is imposed on the battery; it runs on its own settings.
- **Boilers, heat pumps and other loads**: the load is put back in its own mode.

The typical use case is a site with many EV chargers of which a few must never be limited, for example the chargers of the site owner, while the other chargers are load-balanced as usual.

## Other signals on the same devices

This mode takes its place in the priority list on the external signals page, like every external signal and every other special local control mode. For a device that is both excluded by this mode and steered by another signal, the signal that is higher in the list wins:

- With this mode **above** the other signal, the device is only monitored; the other signal keeps steering its other devices.
- With this mode **below** the other signal, the other signal still steers the device. This also holds for a signal that is configured to apply to all compatible devices.

So put this mode on top of the list to make the exclusion absolute, or keep for example a grid operator (DSO) signal above it when that signal must still be able to limit the excluded devices.

> [!NOTE]
> The *Diagnostic tests* special local control mode cannot share a device with this mode: it requires exclusive control over its devices. Select different devices for the two modes.


# Configuring the special control mode

## Devices

Make sure that the devices that must only be monitored are added to the <BrandName /> <ControllerName /> as controllable devices, in the same way as the devices that are controlled. Devices that are not controllable are never steered anyway and do not need this mode.

## Enabling the special control mode

1. Go to the 'Settings' tab on the <BrandName /> <ControllerName />'s interface and click 'Manage special local control modes'.
2. Click 'Start wizard' under 'Enable a new special local control mode'.
3. Choose 'Monitoring only (don't control the selected devices)' and click 'Next'.
4. Untick 'Always apply this special local control mode to all devices that are compatible with it, including devices that are newly added later' and 'Select all': both are ticked by default, which would exclude every device on the site from control, including the devices that are added later. Then tick only the devices that must be monitored and never controlled, and click 'Apply mode to selected devices'.
5. If the site also has external signals, check the position of the mode in the priority list on the external signals page (see above).

The devices that are not selected keep being controlled as before.

## Disabling the special control mode

Remove the mode on the 'Manage special local control modes' page, or edit it to change the selection of devices. The devices that are no longer selected are controlled again according to the control mode of the site. See [Special local control modes](/Controller/Configuration%20from%20A%20to%20Z/8-local-control-modes/special-local-control-modes/) for pausing, editing and the priority towards other signals.


# Negative price wind control


import { BrandName, ControllerName } from '@site/src/components/customFields';
import ClickableImage from '@site/src/components/ClickableImage';


# Introduction

## What this control mode does

The *Negative Price Wind Control* special local control mode switches the selected wind inverters off as long as the purchase price of energy on the site is negative, and lets them produce at their nominal power the rest of the time. At negative purchase prices you are paid to consume energy, so every kWh that is produced costs money; a wind turbine, unlike a solar installation, cannot simply be limited to the self-consumption of the site, so it is stopped completely.

- When the site purchase price is negative, a setpoint of 0 W is sent to all selected inverters.
- Otherwise, a setpoint equal to the nominal power of each inverter is sent, so the inverters produce at full power.

> [!NOTE]
> The purchase price used is the price of the site, as configured in the app under the energy cost settings (the day-ahead price with the scale factor, the surcharge and the grid costs applied). See [Pricing parameters](/Controller/Configuration%20from%20A%20to%20Z/8-local-control-modes/complete-explanation/#pricing-parameters). The mode needs energy prices to be available; check the [energy prices troubleshooting page](/Controller/Troubleshooting/energy-prices/) if the inverters are never switched off.

> [!NOTE]
> This mode is also offered for solar inverters, as it works with any production device. For solar installations the "Cost optimization" working mode is usually the better choice: it limits the production to the self-consumption of the site at negative selling prices, instead of switching everything off.


# Configuring the special control mode

## Wind inverters

Make sure that the wind inverters are added to the <BrandName /> <ControllerName /> as production devices, and that their nominal power is set correctly in their [device settings](/Controller/Configuration%20from%20A%20to%20Z/11-Extra-Information/device-settings/).

## Enabling the special control mode

1. Go to the 'Settings' tab of the <BrandName /> <ControllerName />'s interface and click "Manage special local control modes".
2. Click "Start wizard" under "Enable a new special local control mode".
3. Choose "Negative Price Wind Control" and click "Next". The mode has no further inputs.
4. Select the wind inverters that must be switched off at negative prices, and click "Apply mode to selected devices".

See [Special local control modes](/Controller/Configuration%20from%20A%20to%20Z/8-local-control-modes/special-local-control-modes/) for the priority towards other signals, and for pausing or removing the mode.


# Peak Shaving Relay Cascade


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';


<img
    src="/img/sgo/Logo_Generic.png"
    alt="Enervalis logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

# Introduction

## Peak shaving

The peak shaving relay cascade is a special local control mode that is implemented to switch relays in specific order on or off for peak shaving. This works similar to a **last-in-first-out (LIFO) queue**.
- When the grid power drops below the switch-on threshold: The next relay that is currently off will be switched on
- When the grid power rises above the switch-off threshold: The last relay that is currently on will be switched off

This can be used to control the grid power to remain between the on and off thresholds, with on/off loads.

## Order of the relays

The order of the relays is determined by:
1. The device priority (configureable on the device settings page)
2. For device of the same priority, devices are switched on in alphabetical order


# Configuring the special control mode

## Relay device settings
For each of the relays that are controlled, it is recommended to set the 'Use case' to 'Switching a device or circuit' in the [device settings](/Controller/Configuration%20from%20A%20to%20Z/11-Extra-Information/device-settings/#relays-switches-and-other-onoff-loads) page.
You should also set the 'Default device state' to whatever is desirable in case there is a problem with the control mode.

> [!NOTE] **Minimum & maximum switch on and wait times:** Timing related device settings are ignored in the peak shaving relay cascade control mode. You can however configure a debounce time between switching on and off when enabling the control mode.

## Enabling the special control mode
1. Go to the 'Settings' tab on the <BrandName /> <ControllerName />'s interface and click 'Manage special local control modes'.
2. Click 'Start wizard' under 'Enable a new special local control mode'.
3. Choose 'Peak shaving relay cascade' and click 'Next'.
4. Set the grid power above which the last active relay is switched off, the grid power below which the next relay is switched on, and the minimum debounce time between switching relays. Leave sufficient room between the two thresholds to avoid relay chatter.
5. Select the relays and click 'Apply mode to selected devices'.

See [Special local control modes](/Controller/Configuration%20from%20A%20to%20Z/8-local-control-modes/special-local-control-modes/) for the priority towards other signals, and for pausing or removing the mode.

# Relay control based on the total battery state of charge


import { BrandName, ControllerName } from '@site/src/components/customFields';
import ClickableImage from '@site/src/components/ClickableImage';


<img
    src="/img/sgo/Logo_Generic.png"
    alt="Generic logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

# Introduction

## Relay control based on the total battery state of charge

This special local control mode switches one or more relays on when the total state of charge of all the batteries on the site drops below a configurable value, and off again when it rises above another value. It is the general-purpose version of [Switching on a generator at low battery state of charge](/Controller/Configuration%20from%20A%20to%20Z/8-local-control-modes/special-local-control-modes/switching-generator-on-at-low-battery-soc/): use it for any load or signal that must follow the state of charge of the batteries, for example a warning lamp, a load that may only run while there is enough energy in the batteries, or a contact towards a building management system.

- Below the lower threshold, the selected relays are switched **on**.
- Above the upper threshold, the selected relays are switched **off**.
- Between the two thresholds, the relays keep their position (hysteresis), and a relay stays at least the configured minimum time in the same position.

> [!NOTE]
> The total state of charge is the capacity-weighted average of the state of charge of all the batteries of the site.

> [!NOTE]
> The timing settings of the relays (minimum and maximum switch on and off times) are ignored in this mode. Only the minimum hold time configured in the mode itself applies.

> [!WARNING]
> If the total battery capacity is zero (no batteries, or batteries without a configured capacity), the mode cannot decide and puts the relays in their default device state. The mode reports this as an error on the external signals page.


# Configuring the special control mode

## Batteries
Make sure that your batteries are added to the <BrandName /> <ControllerName />.

## Relay device settings
1. Add the relay through the device wizard, see [Adding a device](/Controller/Configuration%20from%20A%20to%20Z/11-Extra-Information/adding-device/): choose 'On/off load', 'Generic', and then 'Relay' or 'Ethernet to relay converter', as suited to how the relay is connected.
2. In the [device settings](/Controller/Configuration%20from%20A%20to%20Z/11-Extra-Information/device-settings/#relays-switches-and-other-onoff-loads) of the relay, set the 'Default device state' to the position the relay must take when the mode cannot decide. The mode itself puts the 'Use case' of the relay to 'Direct passthrough of an external control signal' as soon as it is active.

## Enabling the special control mode
1. Go to the 'Settings' tab of the <BrandName /> <ControllerName />'s interface and click "Manage special local control modes".
2. Click "Start wizard" under "Enable a new special local control mode".
3. Choose "Relay control based on the total battery state of charge" and click "Next".
4. Configure the mode:
    - The total battery state of charge (as a percentage) below which the relays should be switched on.
    - The total battery state of charge (as a percentage) above which the relays should be switched off.
    - The minimum time (in seconds) the relays should remain in the same position.
5. Select the relay(s) and click "Apply mode to selected devices".

See [Special local control modes](/Controller/Configuration%20from%20A%20to%20Z/8-local-control-modes/special-local-control-modes/) for the priority towards other signals, and for pausing or removing the mode.


# Switched load schedule


# Switched load schedule

Use a switched load schedule for fixed loads that SmartgridOne controls through a relay, contactor or smart socket. It provides recurring on and off windows while keeping the site's default control strategy active at all other times.

Typical applications include pumps, immersion heaters, ventilation equipment and other non-modulating loads. Only connect loads that are technically and operationally suitable for remote switching.

## Available modes

| Scheduled mode | Behaviour during the window | Typical purpose |
| --- | --- | --- |
| **Force on** | Closes or enables the selected switched output. | Running a load during solar production or a low-price period. |
| **Force off** | Opens or disables the selected switched output. | Preventing consumption during a peak or restricted period. |
| **Follow default control** | Uses the site's normal SmartgridOne control strategy. | Returning explicitly to the standard energy-management behaviour. |

## Configure the schedule

1. Open the commissioning interface and go to **Settings** > **Special local control modes**.
2. Start the configuration wizard and select **Switched load schedule**.
3. Add one or more rules with the required weekdays, active months or date period, start time, end time and mode.
4. Select the relays, contactors or smart sockets that the schedule may control.
5. Position the schedule in the **External signals** priority list and save the configuration.

> [!TIP]
> Give devices clear names before configuring the schedule. This makes it easier to distinguish similar relay outputs during commissioning and troubleshooting.

## How time windows work

- Rules use the site's configured local time zone and follow daylight-saving-time changes.
- The start time is included and the end time is excluded.
- A rule cannot cross midnight. Split an overnight period into two rules.
- Rules in the same schedule may not overlap.
- Outside matching rules, each load follows the site's default control strategy.

### Example: run an immersion heater on midday solar

| Days | Time | Mode | Purpose |
| --- | --- | --- | --- |
| Every day | 11:00–15:00 | Force on | Use the expected solar-production window. |
| Every day | 17:00–21:00 | Force off | Avoid the evening demand peak. |
| All other times | — | Default control | Resume normal site optimisation. |

## Interaction with other controls

The schedule participates in the external-signal priority system. If several signals request different modes, the active signal with the highest configured priority wins.

Forced on and off modes act as manual overrides, so normal minimum and maximum on, off or waiting times do not delay a forced transition. SmartgridOne plans the resulting fixed load before flexible EV, battery and PV actions and can use those assets to compensate where possible within the grid limits.

> [!IMPORTANT]
> A switched load configured to pass through an external signal ignores schedule control. The schedule status identifies affected devices. Disable passthrough only when the schedule is meant to control that output.

> [!CAUTION]
> Do not use this function to interrupt safety-critical equipment. Loads with compressors, pumps or mandatory run-on periods may require additional protection against frequent switching.

## Troubleshooting

### The selected output ignores the schedule

Check whether the switched load is configured for external-signal passthrough. Also verify that a higher-priority external signal is not active.

### The output is not available for selection

Confirm that the device is configured as a supported relay, contactor or smart socket and is assigned to the correct site.

### The rule activates at the wrong time

Verify the site's configured time zone, including daylight-saving-time behaviour, and review the selected weekdays and active date period.


# Switching on a generator at low battery state of charge


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';


<img
    src="/img/sgo/Logo_Generic.png"
    alt="Generic logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

# Introduction

## Switching on a generator at low battery state of charge

This is a special local control mode that is implemented to switch a relay on when the total state of charge of the batteries drops below a configurable value. This will allow a generator to take over and power the loads, and recharge the battery.

> [!NOTE]
> The <BrandName /> <ControllerName /> does not control how much power that generator produces. It only gives a signal to switch the generator on/off.


# Configuring the special control mode

## Batteries
Make sure that your batteries are added to the <BrandName /> <ControllerName />.

## Relay device settings
1. Add the relay through the device wizard:
    1. Go to the 'Devices' page.
    2. Click 'Start wizard'
    3. Choose 'On/off load'
    4. Choose 'Generic'
    5. Choose 'Relay', or 'Ethernet to relay converter', as suited to how the relay is connected.
    6. Scan for and add the relay.
2. For the relay that is controlled, set the 'Default device state' in the [device settings](/Controller/Configuration%20from%20A%20to%20Z/11-Extra-Information/device-settings/#relays-switches-and-other-onoff-loads) page to the position the relay must take when the mode cannot decide (for example when no battery capacity is known). The mode itself puts the 'Use case' of the relay to 'Direct passthrough of an external control signal' as soon as it is active.

## Enabling the special control mode
1. Go to the 'Settings' tab on the <BrandName /> <ControllerName />'s interface and click 'Manage special local control modes'.
2. Click 'Start wizard' under 'Enable a new special local control mode'.
3. Choose 'Backup genset switch on/off based on the total battery state of charge' and click 'Next'.
4. Configure the total battery state of charge below which the relay switches on, the state of charge above which it switches off again, and how long (in seconds) it should at least stay on or off after switching. Between the two thresholds the relay keeps its position.
5. Select the relay and click 'Apply mode to selected devices'.

See [Special local control modes](/Controller/Configuration%20from%20A%20to%20Z/8-local-control-modes/special-local-control-modes/) for the priority towards other signals, and for pausing or removing the mode.

> [!TIP]
> The same mechanism is available for any relay, not only a generator, as [Relay control based on the total battery state of charge](/Controller/Configuration%20from%20A%20to%20Z/8-local-control-modes/special-local-control-modes/relay-control-on-battery-soc/).

# 9. PV panel configuration


import { BrandName, ControllerName, CustomerName, InsightsName, InsightsUrl } from '@site/src/components/customFields';
import Details from '@theme/Details';
import ClickableImage from '@site/src/components/ClickableImage';

# PV panel configuration

> [!NOTE]
> The PV panel configuration is requested during the initial setup. You can change it later under the "Settings" menu in the commissioning interface, in the "PV installation details" submenu.

> [!NOTE]
> The panel configuration is used to improve the accuracy of predicted PV production.

You have a choice between the simple and advanced configurator. 

In the simple configurator, you only enter the total output of the PV system.
<ClickableImage src="/img/generic/pv-panel-config-basic-en.png" alt="Image 1" maxWidth="350px" />

In the advanced configurator, you can account for configuration down to the panel level.
<ClickableImage src="/img/generic/pv-panel-config-advanced-en.png" alt="Image 1" maxWidth="350px" />

# Configuration From A To Z


import { FolderOverview } from '@/components/FolderOverview';

# Configuration From A To Z

<FolderOverview folder="Controller/Configuration from A to Z" />


# Control response time

 
import { BrandName, ControllerName, CustomerName, InsightsName, InsightsUrl } from '@site/src/components/customFields';
import Details from '@theme/Details';
import DownloadButton from '@site/src/components/DownloadButton';
import ClickableImage from '@site/src/components/ClickableImage';


# Control response time
When controlling assets (EV's, batteries), the <BrandName /> <ControllerName /> sends a command to the device, which then needs time to process this command and adjust its state accordingly. This is known as the control response time.
The time needed for this, and the time it takes for the <BrandName /> <ControllerName /> to send a new command, depends on the following factors:
- The type of device (e.g., battery, EV charger, heat pump)
- The settling check
- Limitation on the RS485 bus
- The scheduler interval

When your <BrandName /> <ControllerName /> is active in ancilllary services, a fast response time is crucial.
On this page, we will explain how these factors influence the control response time and how you can optimize it for your specific use case.

> [!TIP]
> __Key takeaways:__
> - Don't use Modbus-RTU (RS485) when having multiple devices connected to the RS485 bus. Use Modbus-TCP instead.
> - Disable ramp-up and ramp-down settings on devices that support it, such as batteries and inverters, to allow for faster response times.
> - Disable settling check, if you understand the implications.
> - Set the scheduler interval to 1 second for faster command processing.
>
> __For the full explanation of these factors, continue reading below.__


## The type of device
Different types of devices have inherently different response times due to their technical characteristics and communication protocols:

### Battery and/or solar inverters (including hybrid inverters)
- Typically fast response times (1-5 seconds)
- Response time mainly depends on the inverter's internal controls
- May have built-in ramp rates for power transitions


### EV Chargers
- Medium response time (5-15 seconds)
- Response depends on:
  - Communication protocol (OCPP, Modbus, proprietary)
  - Vehicle's charging capabilities
  - Current charging state
- Must respect minimum charging current requirements

### Heat Pumps
- Slower response times (30-180 seconds)
- Gradual power adjustments to protect the compressor
- Response time affected by:
  - Operating mode (heating/cooling)
  - Current temperature conditions
  - Internal protection mechanisms

### Relays and Switches
- Fast response times (1-5 seconds)
- Typically used for simple on/off control

> [!TIP]
> For optimal control, consider the slowest responding device when setting up your control parameters. This ensures stable operation across all connected devices.


## The 'Settling Check'
When working with multiple device brands, protocols, and models, patience becomes essential. Although devices like batteries, inverters, and EV chargers typically respond quickly to commands, they need time to update their measurements and send them back to the <ControllerName />.

Two key factors affect response times:
1. Energy meters may send data at slower rates, which means they don't immediately reflect the latest device actions
2. Devices often need time to ramp up and stabilize to reach their target states

This is where settling checks become important. A settling check is a waiting period that ensures devices have fully reached their commanded states before new decisions are made. Think of it as letting the dust settle after a change. Without this mechanism, our control system could react to temporary states during the transition period. This would lead to unnecessary corrections - similar to trying to balance on a wobbling platform while constantly overcorrecting, making the situation worse.

Our implementation monitors three crucial aspects: First, it verifies that measurements are recent and reliable, ensuring we're not reacting to outdated information. Second, it tracks how power flows change over time, confirming that devices are responding as expected. Finally, it respects the inherent delays in device responses, giving equipment the time it needs to reach stable operation.

Consider a site with two devices: a modern battery system and an older heat pump. When we send a command to reduce power consumption by 5kW:

| Time | Battery | Heat Pump | System Response |
|------|---------|-----------|-----------------|
| 0:00 | 0kW     | 5kW       | Command sent: reduce by 5kW |
| 0:01 | -2kW    | 5kW       | Battery responds quickly |
| 0:03 | -2kW    | 3kW       | Heat pump starts responding |
| 0:05 | -2kW    | 3kW       | Waiting for stability |
| 0:07 | -2kW    | 3kW       | System confirms settled state |

The battery responds almost immediately, but the heat pump's older control system takes longer to adjust and report its new state. Without settling checks, we might misinterpret this delay as a failure to respond and send additional commands, potentially destabilizing the system. Instead, our controller patiently waits for all devices to report stable states before making any new decisions.
The timeline for this exact flow then looks like this:
<ClickableImage src="/img/generic/settling-check.png" alt="Settling check timeline" maxWidth="60%" />

This measured approach might seem overly cautious, but in the world of power systems, stability and equipment longevity far outweigh the appeal of rapid-fire adjustments.
<ClickableImage src="/img/generic/settling-check-2.png" alt="Settling check timeline" maxWidth="60%" />

__Disabling the settling check__
> [!WARNING]
> - Disabling is not recommended and should only be done in exceptional cases. Otherwise, you risk destabilizing the system and causing oscillations.
> - Proceed with causion and only if you fully understand the implications and prefer speed over stability.
The settling check can be disabled in the <BrandName /> <ControllerName /> app under the advanced settings. This will allow the controller to send commands without waiting for the devices to settle, potentially speeding up response time.

<Details summary='Click here to see the instructions '>
1. Open the settings page:
<ClickableImage src="/img/generic/advanced-settings.png" alt="Reach the the 'Advanced settings' by going to 'Settings' and clikc the 'Advanced settings' button" maxWidth="100%" />
2. Change the "Enable device settling check" to `False`:
<ClickableImage src="/img/generic/advanced-settings-1.png" alt="Reach the the 'Advanced settings' by going to 'Settings' and clikc the 'Advanced settings' button" maxWidth="100%" />
3. Click on 'Save' to the right of the row.
</Details>


## Limitation on the RS485 bus

When multiple devices are connected to the RS485 bus, the control response time can be affected due to the inherent limitation of RS485 communication - only one device can communicate at a time.

As devices take turns communicating over the bus, each additional device increases the overall communication cycle time. This can lead to slower response times for all connected devices.

For optimal performance:
- Limit the number of devices to 5 or fewer per RS485 bus
- Use RS485 expansion accessories when connecting more devices

> [!TIP]
> For detailed information about RS485 wiring and best practices, refer to the [Wiring Best Practices](/Controller/wiring-best-practices/) guide.

## Scheduler interval
The scheduler interval determines how often the <BrandName /> <ControllerName /> checks for new commands and sends them to the devices. A shorter interval allows for faster response times, while a longer interval can lead to delays in command execution.
Check if the scheduler interval is set to a reasonable value for your use case. The default interval is 1 second, but you can adjust it in the advanced settings:
<Details summary='Click here to see the instructions '>
1. Open the settings page:
<ClickableImage src="/img/generic/advanced-settings.png" alt="Reach the the 'Advanced settings' by going to 'Settings' and clikc the 'Advanced settings' button" maxWidth="100%" />
2. Change the "Enable device settling check" to `False`:
<ClickableImage src="/img/generic/advanced-settings-1.png" alt="Reach the the 'Advanced settings' by going to 'Settings' and clikc the 'Advanced settings' button" maxWidth="100%" />
3. Click on 'Save' to the right of the row.
</Details>


# Eneco


import { ControllerName } from '@site/src/components/customFields';


<img
    src="/img/customers/eneco/logo.png"
    alt="Eneco"
    style={{ display: "block", margin: "0 auto", width: "25%"}}
/>

Eneco Belgium is a sustainable energy provider focused on delivering 100% green electricity and offering innovative energy solutions for homes and businesses, aiming to accelerate the transition to a carbon-neutral future.

## Installation of the Eneco <ControllerName />

### 1. Preparation

#### Before you start, make sure you have the following:
    - Eneco <ControllerName />
    - Power Supply
    - Ethernet Cable (Not delivered with the <ControllerName />)
    - P1 to USB Cable (Delivered with the <ControllerName />)
    - Laptop for configuration
    - Basic tools for installation
    - HomeWizard P1 Dongle (Not delivered, will be used if the Smart Meter is too far from the <ControllerName />)

#### Depending on the installation it could also be useful to have the following:
    - DIN Rail Mounting Kit
    - Extension Chord
    - Ethernet Switch

#### The following should be available on site:
    - Ethernet Connection
    - Power Connection
    - Smart Meter

> [!WARNING]
>
> The P1 Port on the Fluvius Smart Meter needs to be activated, make sure this is done before the installation.\
> This can take up to 3 days!
>

### 2. Installation

<div style={{ display: 'flex', alignItems: 'start' }}>
    <div style={{ flex: 1 }}>
        <h4>Before installing the <ControllerName /> make sure to claim it in the Eneco Portal</h4>
        <p>To claim the <ControllerName />, follow these steps:</p>
        <ol>
            <li>Go to the Eneco Portal</li>
            <li>Log in with your installer credentials</li>
            <li>In the menu select "Add Controller"</li>
            <li>Enter the serial number of the controller</li>
            <li>Enter the verification code of the controller</li>
            <li>Click "Claim"</li>
        </ol>
    </div>

    <div style={{ marginLeft: '20px' }}>
        <img
            src="/img/customers/eneco/claim.png"
            alt="Claiming the Eneco Controller"
            style={{ maxWidth: '200px' }}
        />
    </div>
</div>

<div style={{ display: 'flex', alignItems: 'start' }}>
    <div style={{ flex: 1 }}>
        <h4>Install the <ControllerName /></h4>
        <ol>
            <li>Connect the <ControllerName /> to the power supply</li>
            <li>Connect the <ControllerName /> to the internet using the Ethernet cable</li>
            <li>In the menu select "Add Controller"</li>
            <li>Connect the <ControllerName /> to the smart meter using the P1 to USB cable or the [HomeWizard Dongle](/Controller/Devices/Energy-meter/HomeWizard/)</li>
            <li>Wait for the <ControllerName /> to boot up</li>
            <li>The <ControllerName /> is now ready for configuration</li>
        </ol>
    </div>

    <div style={{ marginLeft: '20px' }}>
        <img
            src="/img/customers/eneco/installation.png"
            alt="Installing the Eneco Controller"
            style={{ maxWidth: '200px' }}
        />
    </div>
</div>

> [!NOTE]
>
> You can check the status of the Eneco Controller by the color of the status LED:
> - <span style={{ color: 'blue' }}>Booting</span>
> - <span style={{ color: 'green' }}>Ready</span>
> - <span style={{ color: 'red' }}>Error</span>
>

### 3. Configuration

<div style={{ display: 'flex', alignItems: 'start' }}>
    <div style={{ flex: 1 }}>
        <h4>You can easily connect to the configuration page following the following steps:</h4>
        <ol>
            <li>Go to the Eneco Portal</li>
            <li>Log in with your installer credentials</li>
            <li>In the menu select "Settings"</li>
            <li>Under "Current site" select the serial number of the installed controller</li>
            <li>In the menu click "Controller Configuration"</li>
        </ol>
    </div>

    <div style={{ marginLeft: '20px' }}>
        <img
            src="/img/customers/eneco/change_site.png"
            alt="Change to a different site in the Eneco Portal"
            style={{ maxWidth: '200px' }}
        />
    </div>
</div>

#### Once you are in the configuration interface follow the following steps:
    1. Log in using your installer credentials
    2. Click start on the setup wizard
    3. Fill in the Current (A) of the main circuit breaker
    4. Select the correct grid type (single phase, three phase wye or delta)
    5. Fill in the correct power and current limits.  
    The import limit can be set to past year's average power consumption. If it is a Belgian site, then you can fill in the power as used in your capacity tariff calculations of the past year. 
    6. Click next on the page with the default working modes.
    7. Leave the data saver off
    8. Fill in the address of the customer's house and click validate
    9. Click finish setup wizard

> [!TIP]
> The import limit can be set to past year's average power consumption. If it is a Belgian site, then you can fill in the power as used in your capacity tariff calculations of the past year. 
>
> For more information on the limits click [here](/Controller/Configuration%20from%20A%20to%20Z/3-grid-limits/)
>

> [!WARNING]
>
> You should always connect the energy meter directly to the **controller**, not to the inverter.
> Connecting the energy meter to the inverter can cause control problems, especially if your site has many different kinds of devices to control.
>

<div style={{ display: 'flex', alignItems: 'start' }}>
    <div style={{ flex: 1 }}>
        <h4>Now that the basic configuration has been done you can add the Smart Meter:</h4>
        <ol>
            <li>Select "Devices" in the menu</li>
            <li>Start the device wizard</li>
            <li>Choose "Energy Meters"</li>
            <li>Select "Fluvius"</li>
            <li>Select "P1 port USB cable"</li>
            <li>When asked for a device type/protocol select "P1 port DSMR 4.2/DSMR 5"</li>
            <li>Click "Search"</li>
            <li>Click "End scan and go to results"</li>
            <li>Select "Save and go to device settings"</li>
            <li>Fill in the correct settings and click save</li>
        </ol>
    </div>

    <div style={{ marginLeft: '20px' }}>
        <img
            src="/img/customers/eneco/meter.png"
            alt="Smart meter settings"
            style={{ maxWidth: '200px' }}
        />
    </div>
</div>

#### After adding the Smart Meter we can now add the hybrid inverter:
    1. Select "Devices" in the menu
    2. Start the device wizard
    3. Choose "Solar inverter" or "Battery systems"
    4. Select "Sigenergy/Energreen" from the list of brands
    5. Select "Ethernet TCP" and click "Next"
    6. Select "SigenStor" and click "Next"
    7. Open "Option 1. Add by MAX address"
    8. If no devices are listed click "Refresh table"
    9. Click "Select" next to the MAC address of the inverter
    
> [!NOTE]
>
>         These inverters are usually listed as "Espressif Inc."
>

    10. Click "Search"
    11. Click "End scan and go to results"
    12. Click "Save and go to device settings"
    13. Fill in the correct settings and click save

> [!WARNING]
>
> Make sure to enable "Modbus TCP" in the Sigenergy/Energreen app.\
> For correct battery control the control mode should be set to "External Control"
> Make sure the Energreen battery is installed WITHOUT meter and no grid export/import limits have been set.
>

### 4. Final steps

#### We want to control the battery inverter based on the prices provided by Eneco
    1. Select "External data sources" in the menu
    2. Click "Start wizard"
    3. Select "External Signal"
    4. Select "Eneco"
    5. Fill in the necessary information and click "Save"

### 5. Done

#### Your Eneco Controller is now fully configured and ready to control the energy flows in your home!




# Customer Specific


import { FolderOverview } from '@/components/FolderOverview';

# Customer Specific

<FolderOverview folder="Controller/Customer Specific" />


# Boiler


import { FolderOverview } from '@/components/FolderOverview';

# Boiler

<FolderOverview folder="Controller/Devices/Boiler" />


# My-PV


import { BrandName, ControllerName, CustomerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';


# AC•THOR / AC ELWA 2


---

| Model | Instruction video |
| --- | --- |
| my-PV AC ELWA 2 | <InstructionVideo videos={[{"videoId": "GZx75GLeH64", "title": "my-PV AC ELWA 2", "description": "Models: AC ELWA 2."}]} /> |
| my-PV AC•THOR | <InstructionVideo videos={[{"videoId": "3F5RPqCPsHs", "title": "my-PV AC•THOR", "description": "Models: AC•THOR."}]} /> |
| my-PV AC•THOR9s | <InstructionVideo videos={[{"videoId": "gKRhuzgpgQU", "title": "my-PV AC•THOR9s", "description": "Models: AC•THOR9s."}]} /> |

## 1. Basic settings on the my-PV device

First read the installation and user manual supplied with the device, as well as the online manual.

- The user manual for **AC•THOR** can be found [here](https://download.my-pv.com/acthor/acthor_doc_en_a0020708.pdf)  
- The user manual for **AC ELWA 2** can be found [here](https://www.my-pv.com/en/manuals/ac-elwa-2/)  
- Make sure the device is correctly installed and connected before proceeding.

---

## 2. Settings on the my-PV device

Configure the following parameters in the web interface or via my-PV Cloud:

| Setting | Value / Comment |
|----------|-----------------|
| **Control source** | Modbus TCP |
| **Power time-out** | 60 seconds |

<img src="/img/customers/mypv/ModbusTCP.png" alt="AC•THOR" width="50%" />
<img src="/img/customers/mypv/PowerTimeOut.png" alt="AC ELWA 2" width="50%" />


These settings can be applied directly on the device, via the web interface, or through my-PV Cloud.

---

## 3. Network & communication

1. The **AC•THOR** or **AC ELWA 2** devices are connected to **<BrandName /> <ControllerName />** through your local network (router).  
2. Within this network, the my-PV device receives commands indicating how much power it should deliver.

> [!IMPORTANT] Notes & Limitations
> - A maximum of **10 my-PV devices** can be controlled within a single network.  
> - The operating mode **M3** is **not supported** in this configuration.  
> - Do **not** connect the my-PV device directly to the inverter or battery system — control must occur via the network.

---

## 4. Settings on <BrandName /> <ControllerName />

Perform the following steps in the web interface of <BrandName /> <ControllerName />:

### Step 1: Select the device type
You will be asked: **"What kind of device do you want to add?"**

### Step 2: Select the manufacturer
Choose **MYPV** from the list of manufacturers.

### Step 3: Select the model
You will be asked: **"Which device model are you adding?"**  
Select the correct model, for example:
- **AC Elwa 2**
- **Acthor**
- **Acthor 9s**

### Step 4 & 5: Network & communication
<BrandName /> <ControllerName /> will perform a network scan. In the **"Device network parameters"** screen, you can add the device:
- **Option 1:** Add by MAC address (recommended for networks with DHCP)  
- **Option 2:** Add by fixed IP address, domain, or hostname  

### Step 6: Configure the device settings
In the **"Device/group settings"** screen, configure the specific settings for the my-PV device.

| Setting | Example value | Comment |
|----------|----------------|----------|
| **Is the device single or three phase?** | Single phase | Select the correct phase configuration |
| **Normal power (W)** | [device-specific] | Nominal power of the my-PV device |
| **Operating voltage** | Same as the main device | Operating voltage |
| **Normal voltage type** | Phase-neutral | Select voltage type (Phase-neutral or Phase-phase) |
| **Normal voltage (V)** | 2300 | Nominal voltage in Volts (e.g. 230V × 10) |

Don’t forget to click the **Save button** at the bottom of the page.

---


# AlphaESS


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/sgo/Logo_AlphaESS.png"
    alt="AlphaESS logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

# AlphaESS Cloud API

## Supported Devices

<DeviceSupportTable
  devices={[
    {
        type: 'SMILE', 
        customCol: '✅' 
    }
  ]}
    customColumns={{ "customCol": "Cloud API" }}
  
/>

## Adding a Device


### Find your API keys

In order to connect to the AlphaESS Cloud API, you will need to obtain your public and private API keys from the AlphaESS Cloud portal.
You can find these keys under *API Application* -> *API Key Management* section of the portal.

<ClickableImage src="/img/customers/alphaESS/cloud/alphaess_cloud_api_keys.png" alt="API Keys"  />


### Generate a site

1. Select 'Start import wizard' under the 'Add sites' header.
2. Select AlphaESS.
3. Fill in your AlphaESS API public and private keys.
4. Fill in the serial number of the inverter. You can leave this empty to scan all systems linked to your AlphaESS Cloud account. 

The site(s) should now be generated.

> [!WARNING]
>
> Each selected site will regenerate the site if it is already present!
> This will reset all settings of the site and the devices in it to the default settings.
>

### Changing site and device settings

1. Enter the generated site.

<ClickableImage src="/img/customers/alphaESS/cloud/alphaess_cloud_enter_site.png" alt="enter site"  />


2. Under site settings, set your desired strategy for storage devices (e.g. Cost optimisation).

<ClickableImage src="/img/generic/cloud/cloud_site_settings.png" alt="site settings"  />

3. Under the device settings of the inverter, configure the settings as preferred.

<ClickableImage src="/img/generic/cloud/cloud_devices.png" alt="site devices"  />

<ClickableImage src="/img/customers/alphaESS/cloud/alphaess_cloud_device_settings.png" alt="device settings"  />



# Enalpin


import { BrandName, ControllerName, CustomerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';
import DownloadButton from '@site/src/components/DownloadButton';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
  src="/img/sgo/Logo_Enalpin.png"
  alt="Enalpin"
  style={{ display: 'block', margin: '0 auto', width: '40%' }}
/>

# Enalpin MQTT Driver

The following integration can be used to send site measurements via MQTT, and receive commands for the different device types installed.

## Python demo script

Contact <CustomerName /> to request a demo script.

## Prerequisites

### Cloud Controller

The sites will be controlled via a Cloud Controller. Please contact <CustomerName /> to set up a new Cloud Controller

### Site Setup

Once a Cloud Controller has been created, it will contain a unique serial number (`<Controller SN>`).

New sites can be generated on the Cloud Controller using unique site filters `<site_filter>`

These two variables must be used in the MQTT Topics and Body.

> [!WARNING]
> Using identical site filters will result in errors.

#### Device Selection

<DeviceSupportTable
  devices={[
    {
        type: 'Solar Inverters',
        customCol: '✅'
    },
    {
        type: 'Storage Devices',
        customCol: '✅'
    },
    {
        type: 'Heatpumps',
        customCol: '✅'
    },
    {
        type: 'Grid & Consumption Meters',
        customCol: '✅'
    },
    {
        type: 'EV Chargers',
        customCol: '❌'
    }
  ]}
    customColumns={{ "customCol": "Supported" }}
/>

> [!NOTE]
> The devices in a site cannot be edited after creation.


#### MQTT Credentials

Unlike other brands, Enalpin does not use a single MQTT user shared across all sites. Request the credentials through the [Eniris webshop](https://webshop.eniris.com/) and specify that a separate MQTT username is required for each site. Enter the issued site-specific username when generating the site.

> [!NOTE]
> The MQTT username is required per site and cannot be left blank.


## Sending measurements

To send measurements to the <BrandName /> <ControllerName />, the following MQTT topic can be used for publishing: ```standard1/outbound/enalpin_meas/<site_filter>/<Controller SN>/```

Optional fields are mentioned in *italics*.

The following fields can be sent per device type:

- **Storage**
    - mean_soc_perc
    - active_power_W
    - *today_charged_Wh*
    - *today_discharged_Wh*
    - *energy_stored_Wh*

- **Solar**
    - active_power_W
    - *today_energy_Wh*

- **Heat Pumps**
    - operation_modes
        - Possible operation modes are *off, on*
    - *active_power_W*
        - *Equals nominal power while heat pump is *on**

- **Meters**
    - active_power_W
    - *today_imported_energy_Wh*
    - *today_exported_energy_Wh*

The message must be structured as follows:
```json
{
    "time": "<Unix Timestamp>",
    "data": {
        "state": {
            "grid": {
                "active_power_W": <Grid Active Power in Watts>,
                "today_imported_energy_Wh": <Grid Imported Energy in Watt-hours>,
                "today_exported_energy_Wh": <Grid Exported Energy in Watt-hours>,
            },
            "meter": {
                "active_power_W": <Grid Active Power in Watts>,
                "today_imported_energy_Wh": <Grid Imported Energy in Watt-hours>,
                "today_exported_energy_Wh": <Grid Exported Energy in Watt-hours>,
            },
            "storage": {
                "energy_stored_Wh": <Energy Stored in Watt-hours>,
                "mean_soc_perc": <Mean State of Charge Percentage>,
                "active_power_W": <Active Power in Watts>,
                "today_charged_Wh": <Energy Charged on the Current Today in Watt-hours>,
                "today_discharged_Wh": <Energy Discharged on the Current Today in Watt-hours>,
            },
            "solar": {
                "active_power_W": <Solar Active Power in Watts>,
                "today_energy_Wh": <Energy Produced Today in Watt-hours>.
            },
            "heat_pump": {
                "active_power_W": <Heat Pump Active Power in Watts>,
                "operation_modes": <Heat Pump Operation Mode>
            }
        },
        "response_code": <Response Code>
    },
    "fields": {},
    "requestTime": "<Unix Timestamp>",
    "time": "<Unix Timestamp>",
    "siteNodeId": "<site_filter"
}
```

### Measurement Acknowledgement

When a measurement has been successfully received, an acknowledgement will be sent on the following topic: ```standard1/rp_one_s/enalpin_ack/<site_filter>/<Controller SN>```

This acknowledgement can be used to:
1. Verify that the measurement message was received successfully.
2. Verify that the measurement message contained all necessary data.

# Receiving commands

To receive commands from the <BrandName /> <ControllerName />, subscribe to the following MQTT topic: ```standard1/outbound/enalpin_cmd/<site_filter>/<Controller SN>/```

The response is structured as follows:
```json
{
    "extraTags": {
        "nodeId": "<Controller SN>_site_0"
    },
    "time": "<Unix Timestamp>",
    "fields": {
        "solar_policy": "<policy>",
        "solar_power_setpoint_w": 5000,
        "storage_policy": "<policy>",
        "storage_power_setpoint_w": -5000
    }
}
```

The list of policies than can be received is found here: [List of Potential Policies](/Controller/External%20Signals/MQTT/eniris-mqtt/#components-and-policies)


# Helin


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/sgo/Logo_Helin.png"
    alt="Helin logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

# Helin Cloud API

## Supported Devices

<DeviceSupportTable
  devices={[
    {
        type: 'Solar Inverters', 
        variants: 'All', 
        customCol: '✅' 
    },
    {
        type: 'Storage Devices', 
        variants: 'All', 
        customCol: '❌' 
    }
  ]}
    showVariants={true}
    customColumns={{ "customCol": "Cloud Driver" }}
  
/>

## Adding a Device

### Generate a site

1. Select 'Start import wizard' under the 'Add sites' header.
2. Select Helin.
3. Fill in your Helin API Client ID, Client Secret Key and (not required), location filters.

**Warning! Each selected site will regenerate the site if it is already present! Use with caution.**

The sites will now be generated.

### Correctly setting the settings

1. Enter the generated site.
2. Under the device settings of the inverter, configure the settings as preferred.
3. Under general settings, set your desired strategy for production devices (e.g. Feed-In Restriction).


# Ems Control


import { FolderOverview } from '@/components/FolderOverview';

# Ems Control

<FolderOverview folder="Controller/Devices/Cloud/EMS Control" />


# Neargrid


import { BrandName, ControllerName, CustomerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';
import DownloadButton from '@site/src/components/DownloadButton';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
  src="/img/sgo/Logo_Neargrid.png"
  alt="Neargrid"
  style={{ display: 'block', margin: '0 auto', width: '40%' }}
/>

# Neargrid MQTT Driver

The following integration can be used to send site measurements via MQTT, and receive commands for the different device types installed.

## Python demo script

Contact <CustomerName /> to request a demo script.

## Prerequisites

### Cloud Controller

The sites will be controlled via a Cloud Controller. Please contact <CustomerName /> to set up a new Cloud Controller

### Site Setup

Once a Cloud Controller has been created, it will contain a unique serial number (`<Controller SN>`).

New sites can be generated on the Cloud Controller using unique site filters `<site_filter>`

These two variables must be used in the MQTT Topics and Body.

> [!WARNING]
> Using identical site filters will result in errors.

#### Device Selection

<DeviceSupportTable
  devices={[
    {
        type: 'Solar Inverters',
        customCol: '✅'
    },
    {
        type: 'Storage Devices',
        customCol: '✅'
    },
    {
        type: 'Heatpumps',
        customCol: '✅'
    },
    {
        type: 'Grid & Consumption Meters',
        customCol: '✅'
    },
    {
        type: 'EV Chargers',
        customCol: '❌'
    }
  ]}
    customColumns={{ "customCol": "Supported" }}
/>

> [!NOTE]
> The devices in a site cannot be edited after creation.


#### MQTT Credentials

Request the Eniris MQTT credentials through the [Eniris webshop](https://webshop.eniris.com/). The issued MQTT username must be entered when generating a new site.

> [!NOTE]
> The credentials must only be supplied once. One set of MQTT credentials can be used to control all sites.


## Sending measurements

To send measurements to the <BrandName /> <ControllerName />, the following MQTT topic can be used for publishing: ```standard1/outbound/neargrid_meas/<site_filter>/<Controller SN>/```

Optional fields are mentioned in *italics*.

The following fields can be sent per device type:

- **Storage**
    - mean_soc_perc
    - active_power_W
    - *today_charged_Wh*
    - *today_discharged_Wh*
    - *energy_stored_Wh*

- **Solar**
    - active_power_W
    - *today_energy_Wh*

- **Heat Pumps**
    - operation_modes
        - Possible operation modes are *off, on*
    - *active_power_W*
        - *Equals nominal power while heat pump is *on**

- **Meters**
    - active_power_W
    - *today_imported_energy_Wh*
    - *today_exported_energy_Wh*

The message must be structured as follows:
```json
{
    "time": "<Unix Timestamp>",
    "data": {
        "state": {
            "grid": {
                "active_power_W": <Grid Active Power in Watts>,
                "today_imported_energy_Wh": <Grid Imported Energy in Watt-hours>,
                "today_exported_energy_Wh": <Grid Exported Energy in Watt-hours>,
            },
            "meter": {
                "active_power_W": <Grid Active Power in Watts>,
                "today_imported_energy_Wh": <Grid Imported Energy in Watt-hours>,
                "today_exported_energy_Wh": <Grid Exported Energy in Watt-hours>,
            },
            "storage": {
                "energy_stored_Wh": <Energy Stored in Watt-hours>,
                "mean_soc_perc": <Mean State of Charge Percentage>,
                "active_power_W": <Active Power in Watts>,
                "today_charged_Wh": <Energy Charged on the Current Today in Watt-hours>,
                "today_discharged_Wh": <Energy Discharged on the Current Today in Watt-hours>,
            },
            "solar": {
                "active_power_W": <Solar Active Power in Watts>,
                "today_energy_Wh": <Energy Produced Today in Watt-hours>.
            },
            "heat_pump": {
                "active_power_W": <Heat Pump Active Power in Watts>,
                "operation_modes": <Heat Pump Operation Mode>
            }
        },
        "response_code": <Response Code>
    },
    "fields": {},
    "requestTime": "<Unix Timestamp>",
    "time": "<Unix Timestamp>",
    "siteNodeId": "<site_filter"
}
```

### Measurement Acknowledgement

When a measurement has been successfully received, an acknowledgement will be sent on the following topic: ```standard1/rp_one_s/neargrid_ack/<site_filter>/<Controller SN>```

This acknowledgement can be used to:
1. Verify that the measurement message was received successfully.
2. Verify that the measurement message contained all necessary data.

# Receiving commands

To receive commands from the <BrandName /> <ControllerName />, subscribe to the following MQTT topic: ```standard1/outbound/neargrid_cmd/<site_filter>/<Controller SN>/```

The response is structured as follows:
```json
{
    "extraTags": {
        "nodeId": "<Controller SN>_site_0"
    },
    "time": "<Unix Timestamp>",
    "fields": {
        "solar_policy": "<policy>",
        "solar_power_setpoint_w": 5000,
        "storage_policy": "<policy>",
        "storage_power_setpoint_w": -5000
    }
}
```

The list of policies than can be received is found here: [List of Potential Policies](/Controller/External%20Signals/MQTT/eniris-mqtt/#components-and-policies)


# Scholt


import { BrandName, ControllerName, CustomerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';
import DownloadButton from '@site/src/components/DownloadButton';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
  src="/img/sgo/Logo_Scholt.png"
  alt="Scholt"
  style={{ display: 'block', margin: '0 auto', width: '40%' }}
/>

# Scholt MQTT Driver

The following integration can be used to send site measurements via MQTT, and receive commands for the different device types installed.

## Python demo script

This test code does a simple job of continuously sending dummy measurements to an installation, and receiving commands:

Please download the file below in your preferred Python IDE. Fill in your serial number, site filter and the MQTT credentials requested through the [Eniris webshop](https://webshop.eniris.com/), then execute the script:
<DownloadButton file="/docs/eniris/mqtt_scholt_demo_27-05-25.zip" label="Download Tutorial Files" />

## Prerequisites

### Cloud Controller

The sites will be controlled via a Cloud Controller. Please contact <CustomerName /> to set up a new Cloud Controller

### Site Setup

Once a Cloud Controller has been created, it will contain a unique serial number (`<Controller SN>`).

New sites can be generated on the Cloud Controller using unique site filters `<site_filter>`

These two variables must be used in the MQTT Topics and Body.

> [!WARNING]
> Using identical site filters will result in errors.

#### Device Selection

<DeviceSupportTable
  devices={[
    {
        type: 'Solar Inverters',
        customCol: '✅'
    },
    {
        type: 'Storage Devices',
        customCol: '✅'
    },
    {
        type: 'Heatpumps',
        customCol: '✅'
    },
    {
        type: 'Grid & Consumption Meters',
        customCol: '✅'
    },
    {
        type: 'EV Chargers',
        customCol: '❌'
    }
  ]}
    customColumns={{ "customCol": "Supported" }}
/>

> [!NOTE]
> The devices in a site cannot be edited after creation.


#### MQTT Credentials

Request the Eniris MQTT credentials through the [Eniris webshop](https://webshop.eniris.com/). The issued MQTT username must be entered when generating a new site.

> [!NOTE]
> The credentials must only be supplied once. One set of MQTT credentials can be used to control all sites.


## Sending measurements

To send measurements to the <BrandName /> <ControllerName />, the following MQTT topic can be used for publishing: ```standard1/outbound/scholt_meas/<site_filter>/<Controller SN>/```

Optional fields are mentioned in *italics*.

The following fields can be sent per device type:

- **Storage**
    - mean_soc_perc
    - active_power_W
    - *today_charged_Wh*
    - *today_discharged_Wh*
    - *energy_stored_Wh*

- **Solar**
    - active_power_W
    - *today_energy_Wh*

- **Heat Pumps**
    - operation_modes
        - Possible operation modes are *off, on*
    - *active_power_W*
        - *Equals nominal power while heat pump is *on**

- **Meters**
    - active_power_W
    - *today_imported_energy_Wh*
    - *today_exported_energy_Wh*

The message must be structured as follows:
```json
{
    "time": "<Unix Timestamp>",
    "data": {
        "state": {
            "grid": {
                "active_power_W": <Grid Active Power in Watts>,
                "today_imported_energy_Wh": <Grid Imported Energy in Watt-hours>,
                "today_exported_energy_Wh": <Grid Exported Energy in Watt-hours>,
            },
            "meter": {
                "active_power_W": <Grid Active Power in Watts>,
                "today_imported_energy_Wh": <Grid Imported Energy in Watt-hours>,
                "today_exported_energy_Wh": <Grid Exported Energy in Watt-hours>,
            },
            "storage": {
                "energy_stored_Wh": <Energy Stored in Watt-hours>,
                "mean_soc_perc": <Mean State of Charge Percentage>,
                "active_power_W": <Active Power in Watts>,
                "today_charged_Wh": <Energy Charged on the Current Today in Watt-hours>,
                "today_discharged_Wh": <Energy Discharged on the Current Today in Watt-hours>,
            },
            "solar": {
                "active_power_W": <Solar Active Power in Watts>,
                "today_energy_Wh": <Energy Produced Today in Watt-hours>.
            },
            "heat_pump": {
                "active_power_W": <Heat Pump Active Power in Watts>,
                "operation_modes": <Heat Pump Operation Mode>
            }
        },
        "response_code": <Response Code>
    },
    "fields": {},
    "requestTime": "<Unix Timestamp>",
    "time": "<Unix Timestamp>",
    "siteNodeId": "<site_filter"
}
```

### Measurement Acknowledgement

When a measurement has been successfully received, an acknowledgement will be sent on the following topic: ```standard1/rp_one_s/scholt_ack/<site_filter>/<Controller SN>```

This acknowledgement can be used to:
1. Verify that the measurement message was received successfully.
2. Verify that the measurement message contained all necessary data.

# Receiving commands

To receive commands from the <BrandName /> <ControllerName />, subscribe to the following MQTT topic: ```standard1/outbound/scholt_cmd/<site_filter>/<Controller SN>/```

The response is structured as follows:
```json
{
    "extraTags": {
        "nodeId": "<Controller SN>_site_0"
    },
    "time": "<Unix Timestamp>",
    "fields": {
        "solar_policy": "<policy>",
        "solar_power_setpoint_w": 5000,
        "storage_policy": "<policy>",
        "storage_power_setpoint_w": -5000
    }
}
```

The list of policies than can be received is found here: [List of Potential Policies](/Controller/External%20Signals/MQTT/eniris-mqtt/#components-and-policies)


# Taylor


import { BrandName, ControllerName, CustomerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';
import DownloadButton from '@site/src/components/DownloadButton';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
  src="/img/sgo/Logo_Taylor.png"
  alt="Taylor"
  style={{ display: 'block', margin: '0 auto', width: '40%' }}
/>

# Taylor MQTT Driver

The following integration can be used to send site measurements via MQTT, and receive commands for the different device types installed.

## Python demo script

Contact <CustomerName /> to request a demo script.

## Prerequisites

### Cloud Controller

The sites will be controlled via a Cloud Controller. Please contact <CustomerName /> to set up a new Cloud Controller

### Site Setup

Once a Cloud Controller has been created, it will contain a unique serial number (`<Controller SN>`).

New sites can be generated on the Cloud Controller using unique site filters `<site_filter>`

These two variables must be used in the MQTT Topics and Body.

> [!WARNING]
> Using identical site filters will result in errors.

#### Device Selection

<DeviceSupportTable
  devices={[
    {
        type: 'Solar Inverters',
        customCol: '✅'
    },
    {
        type: 'Storage Devices',
        customCol: '✅'
    },
    {
        type: 'Heatpumps',
        customCol: '✅'
    },
    {
        type: 'Grid & Consumption Meters',
        customCol: '✅'
    },
    {
        type: 'EV Chargers',
        customCol: '❌'
    }
  ]}
    customColumns={{ "customCol": "Supported" }}
/>

> [!NOTE]
> The devices in a site cannot be edited after creation.


#### MQTT Credentials

Request the Eniris MQTT credentials through the [Eniris webshop](https://webshop.eniris.com/). The issued MQTT username must be entered when generating a new site.

> [!NOTE]
> The credentials must only be supplied once. One set of MQTT credentials can be used to control all sites.


## Sending measurements

To send measurements to the <BrandName /> <ControllerName />, the following MQTT topic can be used for publishing: ```standard1/outbound/taylor_meas/<site_filter>/<Controller SN>/```

Optional fields are mentioned in *italics*.

The following fields can be sent per device type:

- **Storage**
    - mean_soc_perc
    - active_power_W
    - *today_charged_Wh*
    - *today_discharged_Wh*
    - *energy_stored_Wh*

- **Solar**
    - active_power_W
    - *today_energy_Wh*

- **Heat Pumps**
    - operation_modes
        - Possible operation modes are *off, on*
    - *active_power_W*
        - *Equals nominal power while heat pump is *on**

- **Meters**
    - active_power_W
    - *today_imported_energy_Wh*
    - *today_exported_energy_Wh*

The message must be structured as follows:
```json
{
    "time": "<Unix Timestamp>",
    "data": {
        "state": {
            "grid": {
                "active_power_W": <Grid Active Power in Watts>,
                "today_imported_energy_Wh": <Grid Imported Energy in Watt-hours>,
                "today_exported_energy_Wh": <Grid Exported Energy in Watt-hours>,
            },
            "meter": {
                "active_power_W": <Grid Active Power in Watts>,
                "today_imported_energy_Wh": <Grid Imported Energy in Watt-hours>,
                "today_exported_energy_Wh": <Grid Exported Energy in Watt-hours>,
            },
            "storage": {
                "energy_stored_Wh": <Energy Stored in Watt-hours>,
                "mean_soc_perc": <Mean State of Charge Percentage>,
                "active_power_W": <Active Power in Watts>,
                "today_charged_Wh": <Energy Charged on the Current Today in Watt-hours>,
                "today_discharged_Wh": <Energy Discharged on the Current Today in Watt-hours>,
            },
            "solar": {
                "active_power_W": <Solar Active Power in Watts>,
                "today_energy_Wh": <Energy Produced Today in Watt-hours>.
            },
            "heat_pump": {
                "active_power_W": <Heat Pump Active Power in Watts>,
                "operation_modes": <Heat Pump Operation Mode>
            }
        },
        "response_code": <Response Code>
    },
    "fields": {},
    "requestTime": "<Unix Timestamp>",
    "time": "<Unix Timestamp>",
    "siteNodeId": "<site_filter"
}
```

### Measurement Acknowledgement

When a measurement has been successfully received, an acknowledgement will be sent on the following topic: ```standard1/rp_one_s/taylor_ack/<site_filter>/<Controller SN>```

This acknowledgement can be used to:
1. Verify that the measurement message was received successfully.
2. Verify that the measurement message contained all necessary data.

# Receiving commands

To receive commands from the <BrandName /> <ControllerName />, subscribe to the following MQTT topic: ```standard1/outbound/taylor_cmd/<site_filter>/<Controller SN>/```

The response is structured as follows:
```json
{
    "extraTags": {
        "nodeId": "<Controller SN>_site_0"
    },
    "time": "<Unix Timestamp>",
    "fields": {
        "solar_policy": "<policy>",
        "solar_power_setpoint_w": 5000,
        "storage_policy": "<policy>",
        "storage_power_setpoint_w": -5000
    }
}
```

The list of policies than can be received is found here: [List of Potential Policies](/Controller/External%20Signals/MQTT/eniris-mqtt/#components-and-policies)


# WithTheGrid


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/sgo/Logo_Teleport.png"
    alt="Teleport logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

# Teleport/WithTheGrid Cloud API

## Supported Devices

<DeviceSupportTable
  devices={[
    {
        type: 'Solar Inverters', 
        variants: 'All', 
        customCol: '✅' 
    },
    {
        type: 'Storage Devices', 
        variants: 'All', 
        customCol: '✅'  
    }
  ]}
    showVariants={true}
    customColumns={{ "customCol": "Cloud Driver" }}
  
/>

## Adding a Device

### Generate a site

1. Contact Eniris to add new sites
2. Send the serial numbers of the new installations to Eniris

The sites will now be generated.

### Correctly setting the settings

1. Enter the generated site.
2. Under the device settings of the inverter, configure the settings as preferred.
3. Under general settings, set your desired strategy for production devices (e.g. Feed-In Restriction).


# Huawei


import { FolderOverview } from '@/components/FolderOverview';

# Huawei

<FolderOverview folder="Controller/Devices/Cloud/Huawei" />


# Huawei NetEco


# Huawei NetEco Cloud API

## Adding a Device

### Generate a site

1. Select 'Start import wizard' under the 'Add sites' header.
2. Select Huawei.
3. Select Neteco.
4. Fill in your NetEco Username and Password.
5. Enter your own NetEco hostname (for example, `https://neteco.example.com`). Refer to the [official Huawei NetEco 1000S documentation](https://support.huawei.com/enterprise/en/digital-power/imanager-neteco-1000s-pid-8319720?category=release-documents) if you need help locating it.
6. Filter by stations, and select whether the inverters or smartloggers are controlled. 
**Warning! Each selected site will regenerate the site if it is already present! Use with caution.**

The site should now be generated.


# Cloud


import { FolderOverview } from '@/components/FolderOverview';

# Cloud

<FolderOverview folder="Controller/Devices/Cloud" />


# Sungrow iSolarCloud


import { BrandName }         from '@site/src/components/customFields';
import DeviceSupportTable    from '@site/src/components/DeviceSupportTable';

<img
  src="/img/customers/sungrow/logo.jpeg"
  alt="Sungrow iSolarCloud"
  style={{ display: 'block', margin: '0 auto', width: '40%' }}
/>

## Supported devices

<DeviceSupportTable
  devices={[
    { type: 'All Sungrow inverters registered in iSolarCloud', modbusTcp: '—', rs485: '—' },
  ]}
  showModbusTcp={false}
  showRs485={false}
/>

---

## Configuration steps

> **Prerequisite:** each inverter is already added to your *iSolarCloud*
> account and visible in the web portal or mobile app.

1. **Gather the API credentials**  
   *iSolarCloud → Settings → Open API* gives you:  
   **API Key**, **Access Key**, and **RSA Key**.

2. **Create a read-only user (recommended)**  
   In *Users & Roles* add a dedicated “API” user and limit its rights to
   *Read*.

3. **Add the driver in <BrandName />**  
   - *Integrations → Add device*  
   - Choose **iSolarCloud API**  
   - Fill in the fields:

     | Field | Example |
     | ----- | ------- |
     | **Username / Password** | `api_user / S3cureP@ss` |
     | **API Key / Access Key / RSA Key** | values from step 1 |
     | **Location filter** | `100;101` *(optional – semicolon list)* |
     | **Command type** | default *(active-power limit)* |

   Save – every inverter belonging to the selected locations will appear
   automatically.

---

## Metrics exposed

| Key                         | Description                                     | Unit |
| --------------------------- | ----------------------------------------------- | ---- |
| `actualPowerTot_W`          | Instantaneous AC power of the PV plant          | W    |
| `producedEnergyDeltaTot_Wh` | PV energy since previous read-out ¹             | Wh   |
| `importedEnergyDeltaTot_Wh` | Grid import energy (if provided by Sungrow)     | Wh   |
| `exportedEnergyDeltaTot_Wh` | Grid export energy (feed-in)                    | Wh   |

¹ The driver integrates power over time when absolute kWh counters are
not available.

---

## Troubleshooting

* **HTTP 401 / 403** – double-check the *API* credentials and that the
  user has *API access* enabled in iSolarCloud.
* **No inverters discovered** – verify the *location ID* list; leave the
  field empty to fetch *all* plants associated with the account.
* **Curtailment ignored** – some older Sungrow firmwares don’t honour
  active-power limits; switch the driver to *Alternative* command mode
  (ON/OFF) in the settings.

---

### Useful resources


* Open API documentation – *visible after login* at  
  [portal / Open API](https://isolarcloud.com/#/openapi)  
* Sungrow technical support – service@sungrowpower.com


# Neovolt


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/customers/Neovolt/Logo_Neovolt.png"
    alt="Neovolt logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

# Neovolt Cloud API

## Supported Devices

<DeviceSupportTable
  devices={[
    {
        type: 'All', 
        customCol: '✅' 
    }
  ]}
    customColumns={{ "customCol": "Cloud API" }}
  
/>

## Adding a Device

### Generate a site

1. Select 'Start import wizard' under the 'Add sites' header.
2. Select Neovolt.
3. Fill in your Neovolt API public and private keys.
4. Fill in the serial number of the inverter. You can leave this empty to generate a site for all systems linked to your Neovolt APICloud account. 

The site(s) should now be generated.

> [!WARNING]
>
> Each selected site will regenerate the site if it is already present!
> This will reset all settings of the site and the devices in it to the default settings.
>

### Changing site and device settings

1. Enter the generated site.

<ClickableImage src="/img/customers/Neovolt/Neovolt_cloud_enter_site.png" alt="enter site"  />


2. Under site settings, set your desired strategy for storage devices (e.g. Cost optimisation).

<ClickableImage src="/img/generic/cloud/cloud_site_settings.png" alt="site settings"  />

3. Under the device settings of the inverter, configure the settings as preferred.

<ClickableImage src="/img/generic/cloud/cloud_devices.png" alt="site devices"  />

<ClickableImage src="/img/customers/Neovolt/Neovolt_cloud_device_settings.png" alt="device settings"  />



# Simulation


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/sgo/Logo_Eniris.png"
    alt="Eniris logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

# Simulation Sites

## Supported Devices

<DeviceSupportTable
  devices={[
    {
        type: 'Solar Inverters',
        variants: 'All',
        customCol: '✅',
    },
    {
        type: 'Storage Devices',
        variants: 'All',
        customCol: '✅'
    },
    {
        type: 'EV Chargers',
        variants: 'All',
        customCol: '❌'
    }
  ]}
    showVariants={true}
    customColumns={{ "customCol": "Supported" }}
/>

### Generate a site

1. Select 'Start import wizard' under the 'Add sites' header.
2. Select Simulation.
3. Fill in your site details- battery capacity, device nominal powers, and simulated consumption loads.

### Setting up customised control signals

Under the 'External Signals' tab, add any required external control signals.

The Energy Prices are automatically generated when filling in the site address.


# SMA


# SMA Cloud API

## Authorization

1. Eniris must be given authorization to access the SMA installation

## Adding a Device

After Eniris has been given access to the installation, please contact Eniris to add the installation to the controller.

# SolarEdge


import { BrandName, ControllerName } from '@site/src/components/customFields';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';
import ClickableImage from '@site/src/components/ClickableImage';


![SolarEdge](/img/sgo/Logo_SolarEdge.png)

> [!CAUTION]
>   Onboarding new sites via the SolarEdge API is currently not possible. We are working on enabling this again in the future.

> [!WARNING]
>   The API is only available for Cloud controllers.

## Supported Devices

> The **SolarEdge Grid API driver** works at site level:
> once the gateway is connected, **all inverters registered on the same
> SolarEdge monitoring site become visible**.
> Below are the models we frequently encounter – any other SolarEdge
> inverter should behave identically.

<DeviceSupportTable
  devices={[
{ type: 'HD-Wave single-phase (SE3000–SE7600)', modbusTcp: '❌', rs485: '❌' },
{ type: 'Three-phase (SE9K–SE33.3K)',          modbusTcp: '❌', rs485: '❌' },
{ type: 'Commercial Synergy (SE66K / SE100K)',  modbusTcp: '❌', rs485: '❌' },
]}
  showModbusTcp={false}
  showRs485={false}
/>

***

## Configuration steps

> **Prerequisite:** your SolarEdge site must already send data to the **SolarEdge monitoring** portal (`monitoring.solaredge.com`).

1. **Sharing the Site**
   * Share the SolarEdge installation with [solaredge@eniris.io](mailto:solaredge@eniris.io) to allow external control.
2. **Add in** <BrandName />
   * Contact <BrandName /> regarding the addition of a new site.

***

### Inverter Control

The inverters can be controlled by setting the maximum power to a percentage of the inverter's nominal power.

> [!TIP]
>   If a SolarEdge Grid Meter is connected to the inverter, the inverter can be set to self-consumption. This ensures that no energy is injected back into the grid, but enough is produced to compensate for consumption.


# SolisCloud API V3


import { BrandName, ControllerName } from '@site/src/components/customFields';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/sgo/Logo_Solis.png"
    alt="Solis logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

# Solis Cloud API

## Supported Devices

<DeviceSupportTable
  devices={[
    {
        type: 'Solis API V3', 
        api: '✅'
    }
  ]}
  showApi={true}
/>

Every PV inverter that is visible in your SolisCloud account can be added with this protocol.

> [!NOTE]
>
> This protocol reads the **PV inverter** only. For a hybrid inverter with a battery, select the
> **SolisCloud APIV3 hybrid inverters (experimental)** protocol instead: it also reads the battery
> of the inverter.

## Prerequisites

- A SolisCloud account in which the inverters are already installed and visible.
- The datalogger of the inverter is online in SolisCloud. An inverter that is offline in SolisCloud
  is also offline for the **<ControllerName/>**.
- Permission to grant Eniris both **data access** and **device control** on that account. Both
  permissions are required: without device control the integration cannot be added at all.

## Adding a Device

You can add a Solis inverter to the cloud controller by generating a new site, or adding an inverter to an existing site.
When generating new sites, it is possible to add all inverters linked to your SolisCloud account at once, or to select specific inverters by their serial number. 
When adding an inverter to an existing site, you can only add one inverter at a time by its serial number.

Add a Solis inverter to the cloud controller by following these steps:

1. Select 'Start import wizard' under the 'Add sites' header to generate a new site, or select 'Start device wizard' under the 'Devices' tab in an existing site to add an inverter.
2. Select Solis -> SolisCloud APIV3 inverters (experimental).
3. Follow the instructions to grant Eniris permissions to monitor and control your Solis systems.

    - Go to [https://api-oauth2.soliscloud.com/oauth/authorize?client_id=solis273720868a840d13](https://api-oauth2.soliscloud.com/oauth/authorize?client_id=solis273720868a840d13).
    The wizard also offers this link directly ("CLICKING HERE").
    - Log in with your SolisCloud credentials.
    - Grant **data access** and **device control** permissions to Eniris.
    - After granting access, you will be redirected to a page that displays your access code.
    Copy the access code from that page and paste it in the field in the import wizard.

> [!NOTE]
>
> **Older controller versions (legacy):** on older versions the redirect does not land on a page
> that shows the code. Instead you end up on a URL that looks like
> `https://solis.eniris.be/callback-app?code=XXXXXX`. In that case, copy the code from the
> **URL itself** (the part after `code=`) and paste it in the field in the import wizard.

<ClickableImage src="/img/customers/solis/cloud/solis_apiv3_add_device.png" alt="Adding a Solis inverter via API"  />


> [!WARNING]
>
> Each selected site will regenerate the site if it is already present!
> This will reset all settings of the site and the devices in it to the default settings.

### Inverters from more than one SolisCloud account

An access code is valid for the SolisCloud account you logged in with, and returns only the
inverters of that account. To combine inverters from several accounts, add them one group at a time:
run the wizard again for every account and paste the access code of that account.


# Sparky


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';


# sparky Cloud API

## Supported Devices

<DeviceSupportTable
  devices={[
    {
        type: 'sparky', 
        customCol: '✅' 
    }
  ]}
    customColumns={{ "customCol": "Cloud API" }}
  
/>

## Adding a Device

### Generate a site

1. Select 'Start device wizard'.
2. Select Sparky.
3. Fill in your sparky credentials.
4. Fill in the serial number of the inverter. You can leave this empty to generate a site for all systems linked to your sparky APICloud account. 

The site should now be generated.

> [!WARNING]
>
> Each selected site will regenerate the site if it is already present!
> This will reset all settings of the site and the devices in it to the default settings.
>





# Custom Modbus drivers


import YouTubeEmbed from '@site/src/components/YouTubeEmbed';
import ClickableImage from '@site/src/components/ClickableImage';

# Custom Modbus drivers

A device that SmartgridOne does not support yet no longer has to wait for a software release. With **Custom Modbus drivers**, you build the integration yourself, directly in the commissioning interface of the controller: identification, measurements, alarms and control. Hand the manufacturer's register map to **Niri**, the built-in AI assistant, and Niri writes the driver, tests it on a simulated device and explains every step. You approve each change before it is made.

A finished driver is used like any built-in driver: add the device in the device wizard and SmartgridOne monitors and controls it in its energy management.

> [!NOTE]
> Custom Modbus drivers are available from software version 1.32, as a public beta. Check the behaviour of a driver well before you rely on it. They are not available on cloud controllers.

<YouTubeEmbed videoId="NGyOGrAfPZw" videoIdNl="_ubfcC7j34c" title="SmartgridOne Custom Modbus drivers: integrate a device yourself" />

The video walks through the complete editor. Jump to a chapter:

| Chapter | Topic |
| --- | --- |
| [0:00](https://www.youtube.com/watch?v=NGyOGrAfPZw&t=0s) | Getting started and overview |
| [2:05](https://www.youtube.com/watch?v=NGyOGrAfPZw&t=125s) | Your first working driver |
| [4:38](https://www.youtube.com/watch?v=NGyOGrAfPZw&t=278s) | Driver settings and connection |
| [7:04](https://www.youtube.com/watch?v=NGyOGrAfPZw&t=424s) | Device structure and measurements |
| [9:53](https://www.youtube.com/watch?v=NGyOGrAfPZw&t=593s) | Control and watchdog |
| [12:41](https://www.youtube.com/watch?v=NGyOGrAfPZw&t=761s) | Command logic in practice |
| [17:23](https://www.youtube.com/watch?v=NGyOGrAfPZw&t=1043s) | Testing and troubleshooting |
| [19:59](https://www.youtube.com/watch?v=NGyOGrAfPZw&t=1199s) | Advanced registers and calculations |
| [22:39](https://www.youtube.com/watch?v=NGyOGrAfPZw&t=1359s) | Helper functions and logic |
| [25:22](https://www.youtube.com/watch?v=NGyOGrAfPZw&t=1522s) | Saving, reusing and installing |

## What you can build

- **Device types:** hybrid, battery and PV inverters, EV chargers, energy meters, heat pumps, boilers, switched loads, wind and water turbines, water and gas meters, calorimeters, pyranometers and digital inputs. PFC capacitor banks are supported from software version 2.0.
- **Connections:** Modbus TCP and Modbus RTU over the controller's RS485 ports, including devices that share one connection.
- **Measurements:** registers with data type, scale, unit, sign convention and word order, plus computed measurements.
- **Status and alarms:** status codes and alarm bits with your own texts and severities.
- **Control:** battery setpoints, PV limits, AC setpoints, EV charging currents, reactive power and on/off control, with a watchdog. The command logic is drawn as blocks, not programmed.
- **Installer questions:** one driver supports several installation variants through questions answered in the device wizard.
- **Lifecycle:** test before installing, version history with compare and restore, export and import between controllers.

## Before you start

- Log in to the commissioning interface with your personal account (an e-mail address). Niri cannot be used with the shared local logins. See [Accessing the commissioning interface](/Controller/Configuration%20from%20A%20to%20Z/2-accessing-commissioning-interface/).
- Have the manufacturer's Modbus register map for the exact model and firmware: addresses, data types, scaling, and the sequence to take and release remote control.
- Open **Devices → Custom Modbus drivers**. Check first whether a built-in driver already supports the device.

## Write a driver with Niri

Niri reads the register map, builds the device structure and the command logic, validates the result and tests it on the Playground: a simulated installation inside the controller with a hybrid inverter, PV, a battery, a grid meter and an EV charger. Nothing is written to real equipment without your approval.

### 1. Start a new driver with AI

Click **Help me write a new driver with AI** and select the brand of the device. The editor opens on an empty driver with **Ask Niri** open.

<ClickableImage src="/api/media/agent-uploads/Controller/custom-modbus-drivers/custom-modbus-help-me-write-with-ai.png" alt="The Custom Modbus drivers list with the Help me write a new driver with AI dialog" maxWidth="1140px" />

### 2. Add the register map and describe the device

Attach the manual with the paper clip. Niri reads PDF, Word (.docx), Excel (.xlsx), CSV, YAML, TOML and plain text: up to five documents of 5 MB each per chat. Then say what the driver must do. Name the components and the control you need, for example:

> Write the driver for this hybrid inverter from the attached register map: identification, the AC port, PV, battery, grid meter and backup output, the alarms, and control with a battery setpoint and a PV limit, including the watchdog.

<ClickableImage src="/api/media/agent-uploads/Controller/custom-modbus-drivers/custom-modbus-niri-register-map.png" alt="Ask Niri with the register map attached and the request to write the driver" maxWidth="560px" />

### 3. Review and approve each change

Before Niri saves the driver, starts a test or writes to a device, it asks your approval and shows exactly what changes. Reading the driver and the test results never needs approval.

| Choice | Effect |
| --- | --- |
| **Approve this action** | Niri carries out this one action. |
| **Approve all actions** | After you confirm the risks, Niri continues without asking until you choose **Ask me again** or start a new chat. Every action still appears in the chat. |
| **Deny** | Niri does not carry out the action. Add a reason to steer its next attempt. |

<ClickableImage src="/api/media/agent-uploads/Controller/custom-modbus-drivers/custom-modbus-niri-approval.png" alt="Niri asks approval to edit and save the driver, with the list of changes" maxWidth="1140px" />

### 4. Let Niri test the driver

Niri connects the driver to the matching Playground device, checks recognition and measurements, sends a control command and the release, and compares the register writes with the manual.

<ClickableImage src="/api/media/agent-uploads/Controller/custom-modbus-drivers/custom-modbus-niri-tests-on-playground.png" alt="Niri started a test on the Playground and asks approval to send a command" maxWidth="560px" />

### 5. Check the result

Niri ends with a summary: what the driver reads, how it controls the device, the test results and the points it could not settle from the manual. The problem counter in the header shows **No problems** when the driver can be used to add a device.

<ClickableImage src="/api/media/agent-uploads/Controller/custom-modbus-drivers/custom-modbus-niri-driver-ready.png" alt="The finished driver without problems and the summary of Niri" maxWidth="1140px" />

> [!IMPORTANT]
> Niri is an AI and can be wrong. Before installing, verify addresses, scaling, signs and the control sequence against the manufacturer's documentation and your own test results, and test on the real device as described in [Test the driver](#test-the-driver).

### Ask Niri in any driver

**Ask Niri for help** is available in every driver, also one you wrote by hand. Niri starts with three suggestions: *Explain what this driver reads and controls*, *Find the problems of this driver and fix them* and *Test this driver on the playground*. Other typical requests:

- "Add the alarm registers 400 to 405 from chapter 6 of the manual."
- "The battery power has the wrong sign. Fix it and test again."
- "Test the driver on 192.168.1.50, unit ID 3, and compare the readings with the inverter display."
- "Why does the PV limit command fail with illegal data address?"

A chat belongs to you and to one driver. It ends with **Start over**, after 30 minutes without activity, or when the controller restarts; its documents are removed with it. Only one user at a time can work with Niri on a driver.

### Connect your own AI agent

Power users can connect their own AI agent, such as Claude Code or Claude Desktop, to the driver over MCP. Click the computer icon in the header of Ask Niri, confirm the statement and copy the configuration it shows into the agent. The agent then reads, changes and tests this one driver **without asking approval**, for up to 12 hours or until you click **Disconnect**. Use it only where test commands have no consequences.

For an AI chatbot without a connection to the controller, the help topic **Another AI chatbot** gives a prompt, the format reference and the JSON schema. Import the resulting file with **Import a driver**.

## Build and refine in the editor

Every driver, written by Niri or by hand, is edited in the same editor. Without Niri, start from **New driver** with an empty device type or one of the examples, such as the Playground hybrid inverter, the Playground EV charger or the Eastron SDM630 energy meter. **Tutorial** builds the Playground hybrid inverter driver step by step.

| Tab | Purpose |
| --- | --- |
| **Driver** | Name, supported models, protocol document, connection defaults, search range and installer questions. |
| **Device structure** | Components, identification, recognition, measurements, status, alarms, control option and watchdog. |
| **Command logic** | Control, release and manual commands as connected blocks, with reusable functions. |
| **Test** | Run the driver as shown in the editor, including unsaved changes, on the Playground or a real device. |
| **Live** | Devices that use the driver: their readings and latest commands. Shown once a device uses the driver. |
| **History** | Saved versions: compare, pin as a snapshot, restore, download. |

### Device structure and measurements

Build the tree of components that the device exposes, for example a hybrid inverter with a PV total, MPPT inputs, a battery total and batteries, a backup output and a grid meter. Drag components from the palette onto the tree. Per component, map:

- **Identification**, read once: manufacturer, model, serial number, nominal power, firmware.
- **Recognition**: conditions on registers that confirm the device during a scan, for example a plausible frequency and a model string.
- **Measurements**: address, register type, data type, scale factor, unit and, for power and current, which direction is positive. SmartgridOne counts battery power positive when charging; select the device's own convention in **Sign** and the driver converts it.
- **Status and alarms**: status codes and alarm bits with clear texts and a severity.

<ClickableImage src="/api/media/agent-uploads/Controller/custom-modbus-drivers/custom-modbus-device-structure.png" alt="The measurement registers of a battery in the Device structure tab" maxWidth="1140px" />

Addresses are the zero-based addresses on the bus. **Add computed measurement** derives values from other readings, such as the sum of phase powers.

### Control and watchdog

Choose the control option that matches the device's registers: for example **Battery setpoint and PV limit**, an inverter AC setpoint, an EV charging current or monitoring only. The option decides which setpoints and limits SmartgridOne passes to the command logic. A setpoint requests a value; a limit caps it.

Set up the **watchdog** as the protocol requires: a countdown, a heartbeat counter or a toggling bit. If commands stop arriving, the device falls back to its own operation. The command is repeated at the interval you set, well within the watchdog timeout.

### Command logic

**Control logic** runs with every command while SmartgridOne controls the device; **Release logic** returns the device to its own operation. Solid grey wires set the order of the actions; dotted wires carry the values. Blocks cover register reads and writes, bits, math, conditions, limits, timing, variables and status messages. **Functions** hold logic you reuse, **Manual commands** become actions for the installer on the devices page, and **Physical settings** expose device settings such as an export limit.

After a test command, the canvas outlines the blocks that ran and shows the values on the wires. In the example below, a PV limit of 4 kW becomes 50 % of the 8 kW PV capacity.

<ClickableImage src="/api/media/agent-uploads/Controller/custom-modbus-drivers/custom-modbus-command-logic-trace.png" alt="The control logic after a test command, with the blocks that ran and the values on the wires" maxWidth="1140px" />

Handle failures explicitly: connect **On exception** where a failed write must stop or redirect the command, and end normal paths with **Return from command**. Variables keep values between commands, for example to ramp a battery setpoint, and start over after a controller restart.

## Test the driver

The **Test** tab runs the driver exactly as shown in the editor, unsaved changes included.

1. Under **Connection to test on**, select **Playground (a simulated device)** or the IP address and port, or RS485 port, of the real device. Answer the driver user inputs and click **Connect**.
2. Check **Recognition** and the identification values.
3. Under **What the driver reads**, compare raw registers with decoded values: units, scaling and power direction.
4. Under **Send a command**, enter setpoints and limits and click **Send command**. The result lists every register write in order; **Repeat it every** sends it repeatedly, for example to observe a ramp or the watchdog.
5. Clear **Control active** and send again to test the release.

<ClickableImage src="/api/media/agent-uploads/Controller/custom-modbus-drivers/custom-modbus-test-playground.png" alt="The Test tab connected to the Playground hybrid inverter, with the simulated installation and recognition" maxWidth="1140px" />

> [!WARNING]
> On a real device, test commands, manual commands and register writes take effect immediately. Test only on equipment that may be controlled at that moment.

For diagnosis, use **Registers by hand** and **Raw communication**. Exception 1 (illegal function), 2 (illegal data address) and 3 (illegal data value) point to the function code, the address or the written value respectively.

## Save, install and maintain

- **Save** stores a new version. A driver with problems can be saved as a draft but cannot be used to add a device; devices that already use the driver keep running its last version without problems.
- **Add a device** opens the device wizard with this driver selected, using the saved version. After adding, check recognition, measurements and control on the devices page.
- A driver used by devices opens read-only. **Unlock editing** to change it; saving then updates every device that uses it. On the **Live** tab you can try changed command logic on one device without saving it.
- **History** lists every version with its author, including the versions Niri saved. Compare any two versions, pin a snapshot or restore a version as unsaved changes.
- **Export** downloads the saved driver as a JSON file; **Import a driver** loads it on another controller. A driver made with a newer engine version needs controller software that supports that engine.

<ClickableImage src="/api/media/agent-uploads/Controller/custom-modbus-drivers/custom-modbus-history.png" alt="The History tab comparing the version created by the installer with the version saved by Niri" maxWidth="1140px" />

Every field and block has a **(?)** help button, and **Help** in the editor header opens the full reference.


# ABB


import { BrandName, ControllerName } from '@site/src/components/customFields';
import ClickableImage from '@site/src/components/ClickableImage';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/customers/abb/logo.png"
    alt="ABB"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

## Supported Devices

<DeviceSupportTable
  devices={[
    { 
        type: 'ABB B21',
        modbusTcp: '❌',
        rs485: '✅',
    },
    { 
        type: 'ABB B23',
        modbusTcp: '❌',
        rs485: '✅',
      instructionVideos: [{"videoId": "wQNvrlEUHSo", "title": "ABB B23"}]
    },
    { 
        type: 'ABB B24',
        modbusTcp: '❌',
        rs485: '✅',
    }
  ]}
  showModbusTcp={true}
  showRs485={true}
  />
<ClickableImage src="/img/customers/abb/b23.jpg" alt="Image 1" maxWidth="450px" />

## Wiring

### RS485

The ABB B-series meters (B21, B23, B24) use a 3-pole RS485 connection. Connect these to the <ControllerName /> as follows, based on the meter's terminal markings.

#### 1. Device (ABB Meter) Pinout

This table shows the terminals on the meter itself.


| Signal | Terminal Number |
| :--- | :--- |
| A | 37 |
| B | 36 |
| C (GND) | 35 |

<br />

> **IMPORTANT: Troubleshooting**
>
> The 'A' and 'B' labels are not universally standardized. If the <ControllerName /> **cannot find the device** during a scan, it is often due to a wiring mismatch.
>
> **Swap the A and B wires** (between the controller and the meter) and try scanning again.

#### 2. Controller & Converter Pinout

This table shows the corresponding RS485 pins on <BrandName /> controllers and converters. Match the 'A' and 'B' from the meter (see table above) to the 'A' and 'B' on your controller.


<RS485ConnectionTable firstColumn={["A", "B", "N/A"]} />


## Configuration

<RS485AddressNote />

Use the following Modbus settings in the <ControllerName />'s device wizard. These are the default settings for the meter:

* **Baudrate:** 19200
* **Modbus Address:** 1 (or the address set on the meter)
* **Parity:** Even
* **Stop bits:** 2

# Accuenergy


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/sgo/Logo_Accuenergy.png"
    alt="Accuenergy"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

## Supported Devices


<DeviceSupportTable
  devices={[
    { 
        type: 'Acuvim IIR Energy Meter',
        modbusTcp: '✅',
        rs485: '✅',
      instructionVideos: [{"videoId": "tjPojKfFyp4", "title": "Accuenergy Acuvim IIR-D · RS485", "description": "Use the exact model and connector version shown in this video."}]
    },
    { 
        type: 'Acuvim 3 Energy Meter',
        modbusTcp: '✅',
        rs485: '✅',
      instructionVideos: [{"videoId": "Jlmi5RL_mys", "title": "Accuenergy Acuvim 3-D · RS485", "description": "Original Acuvim 3-D housing with integrated touchscreen; RS485."}]
    },
  ]}
  showModbusTcp={true}
  showRs485={true}
  />


## Connection 
### Ethernet
For correct ethernet wiring: Follow the [the guidelines for ethernet wiring](/Controller/wiring-best-practices/#ethernet).


If you have an accuenergy energy meter you should have an interface to manage it, in this interface go to the <b>Settings</b> page, then select the <b>Communications</b> menu.

<ClickableImage src="/img/customers/accuenergy/settings_communication_page_access.png" alt="Header of the Settings>Communication" maxWidth="450px" />

Then scroll until you find these fields : 
<ClickableImage src="/img/customers/accuenergy/modbus_settings.png" alt="Modbus settings" maxWidth="450px" />

> [!WARNING]
> Be sure that the port is set to <b>502</b> and the <b>Fast Read Mode is enabled</b> and set to <b>100ms Fast Read</b>.

### RS485
<RS485ConnectionTable firstColumn={["", "", ""]} />
<RS485AddressNote />

# Acrel


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/sgo/Logo_Acrel.png"
    alt="Acrel"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

## Supported Devices


<DeviceSupportTable
  devices={[
    { 
        type: 'Acrel DTSD1352-C',
        modbusTcp: '✅',
        rs485: '✅',
      instructionVideos: [{"videoId": "H0BSF2FO5M8", "title": "Acrel DTSD1352-C/1(6)A · RS485", "description": "DTSD1352-C/1(6)A CT version with eight upper auxiliary terminal positions and the V3.1 menu."}]
    },
    { 
        type: 'Acrel ADL3000-E-A',
        modbusTcp: '✅',
        rs485: '✅',
      instructionVideos: [{"videoId": "QEY1U2hzHxQ", "title": "Acrel ADL3000-E-A/KC · direct-connected 80 A · RS485", "description": "ADL3000-E-A/KC direct-connected 3×10(80) A version with seven lower measurement terminals, as shown in the video."}]
    },
    { 
        type: 'Acrel ADL400',
        modbusTcp: '❌',
        rs485: '✅'
    }
  ]}
  showModbusTcp={true}
  showRs485={true}
  />



<ClickableImage src="/img/customers/acrel/dtsd1352-c-1.png" alt="Image 1" maxWidth="450px" />

# Algodue


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/customers/algodue/logo.png"
    alt="Algodue"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

## Supported Devices

<DeviceSupportTable
  devices={[
    { 
        type: 'UPM209',
        modbusTcp: '✅',
        rs485: '✅',
      instructionVideos: [{"videoId": "ewaY6EfoafU", "title": "Algodue UPM209 ENH · 1/5 A CT · RS485", "description": "UPM209 ENH 1/5 A CT RS485, product reference 1208.0003.0001."}]
    }   
  ]}
  showModbusTcp={true}
  showRs485={true}
/>

<ClickableImage src="/img/customers/algodue/upm209.jpg" alt="Image 1" maxWidth="450px" />

## Wiring

### Ethernet
For correct ethernet wiring: Follow the [the guidelines for ethernet wiring](/Controller/wiring-best-practices/#ethernet).

### RS485
<RS485ConnectionTable firstColumn={["", "", ""]} />


## Configuration

### RS485
Set the modbus address on the meter. (Baud rate and parity can also be set, but we recommend leaving this to the default.)
<ClickableImage src="/img/customers/algodue/rs485_config_pt1.png" alt="Image 1" maxWidth="450px" />
<ClickableImage src="/img/customers/algodue/rs485_config_pt2.png" alt="Image 1" maxWidth="450px" />

### Ethernet
If connected through ethernet, you may have to adjust the IP address settings of the energy meter .
<ClickableImage src="/img/customers/algodue/ethernet_config_pt1.png" alt="Image 1" maxWidth="450px" />
<ClickableImage src="/img/customers/algodue/ethernet_config_pt2.png" alt="Image 1" maxWidth="450px" />



# Anexo


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/sgo/Logo_Anexo.png"
    alt="Anexo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

## Supported Devices


<DeviceSupportTable
  devices={[
    { 
        type: 'Energy Meter',
        modbusTcp: '❌',
        rs485: '✅',
    }
  ]}
  showModbusTcp={true}
  showRs485={true}/>
## Connection

### RS485 Connection
For RS485 wiring, follow the [guidelines for RS485 wiring](/Controller/wiring-best-practices/#rs485).

# BMR


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';
import ClickableImage from '@site/src/components/ClickableImage';

<img
    src="/img/customers/bmr/bmr-logo.png"
    alt="BMR"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

## Supported Devices

<DeviceSupportTable
  devices={[
    { 
        type: 'PLA33',
        modbusTcp: '✅',
        rs485: '✅',
    },
    { 
        type: 'PLA33RX',
        modbusTcp: '✅',
        rs485: '✅',
      instructionVideos: [{"videoId": "MaQvA7UJekI", "title": "BMR PLA33RX · RS485", "description": "Use the exact model and connector version shown in this video."}]
    }
  ]}
  showModbusTcp={true}
  showRs485={true}
/>

<ClickableImage src="/img/customers/bmr/pla33.png" alt="BMR PLA33" maxWidth="450px" />
<p style={{ fontSize: "14px", color: "#555" }}>
    **Figure 1**: Front panel of the PLA33 showing buttons like SET, cursor keys, and ESC.
  </p>
<ClickableImage src="/img/customers/bmr/pla33rx.png" alt="BMR PLA33RX" maxWidth="450px" />
  <figcaption style={{ fontSize: "14px", color: "#555" }}>
    **Figure 2**: Front panel of the PLA33RX showing buttons like ESC, cursor keys, and status LEDs for recording and relay outputs.
  </figcaption>

## Wiring

### RS485
For RS485 wiring, follow the [guidelines for RS485 wiring](/Controller/wiring-best-practices/#rs485).

<RS485ConnectionTable firstColumn={["A", "B", "GND"]} />
<RS485AddressNote />

### Ethernet
For Ethernet wiring, follow the [guidelines for Ethernet wiring](/Controller/wiring-best-practices/#ethernet).

---

## Configuration

### RS485 Configuration
To configure RS485 communication on BMR energy meters, follow these steps:

1. **Set the Modbus Address**:
   - Access the settings menu by pressing the **SET** button for 5 seconds.
   - Navigate to the communication menu (`P_2`) using the cursor keys.
   - Set the **Id** (unique Modbus address) between 1 and 247.

2. **Set the Baud Rate**:
   - In the communication menu (`P_2`), configure the **bd** (baud rate) to match your system. Supported baud rates include `9.6 / 19.2 / 38.4 / 57.6 / 115 kBd`.

3. **Parity and Stop Bits**:
   - Configure **PAr** (parity) as `None`, `Odd`, or `Even`.
   - Set the **St** (stop bits) to `1` or `2` as needed.

4. **RS485 Termination**:
   - If the meter is the last device on the RS485 bus, add a 120 Ω termination resistor.

<RS485AddressNote />

---

### Ethernet Configuration (PLA33RX Only)
For devices with Ethernet capability:

1. Ensure the Ethernet cable is properly connected.
2. Use the Power Monitoring Software (PMS) to configure the IP address, subnet mask, and gateway.
3. Verify that the Modbus TCP port is set to **502**.



# EM111


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/customers/carlo_gavazzi/logo.png"
    alt="logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>


## Supported Devices


<DeviceSupportTable
  devices={[
    { 
        type: 'Carlo Gavazzi EM111',
        modbusTcp: '❌',
        rs485: '✅',
      instructionVideos: [{"videoId": "jUE0i1da9oM", "title": "Carlo Gavazzi EM111 · S1 X · RS485", "description": "Models: EM111 DIN AV8 1 X S1 X."}]
    }
  ]}
  showModbusTcp={true}
  showRs485={true}
/>

<ClickableImage src="/img/customers/carlo_gavazzi/em111.jpg" alt="Image 1" maxWidth="450px" />


## Wiring

### RS485
<RS485ConnectionTable firstColumn={["Terminal 8 / A-", "Terminal 6 / B+", "N/A"]} />


## Configuration
Check that the Carlo Gavazzi meter is set to read both import and export power. An unsuitable mode may lead to:
- Missing readings of feed-in, or
- Feed-in being counted as offtake (on top of the ‘actual offtake’)

You can set this in the ‘MEASurE’ configuration menu on the energy meter. This should be set to ‘b’.

> [!WARNING]
> This setting may not be present on MID certified models (model numbers ending in PFA and PFB).
<ClickableImage src="/img/customers/carlo_gavazzi/em111_config_pt1.png" alt="Image 1" maxWidth="450px" />

<RS485AddressNote />
Set the Modbus address through the power meter's “Address” configuration menu.
<ClickableImage src="/img/customers/carlo_gavazzi/em111_config_pt2.png" alt="Image 1" maxWidth="450px" />

# EM210


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/customers/carlo_gavazzi/logo.png"
    alt="logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>


## Supported Devices


<DeviceSupportTable
  devices={[
   {
        type: 'Carlo Gavazzi EM210',
        modbusTcp: '❌',
        rs485: '✅',
   }
  ]}
  showModbusTcp={true}
  showRs485={true}
/>

<ClickableImage src="/img/customers/carlo_gavazzi/em210.png" alt="Image 1" maxWidth="450px" />


## Wiring

The <BrandName /> <ControllerName /> and the device communicate via RS485.

### RS485
<RS485ConnectionTable firstColumn={["Terminal 15 / A-", "Terminal 16 / B+", "Terminal 17 / GND"]} />
<ClickableImage src="/img/customers/carlo_gavazzi/em210_wiring.png" alt="Image 1" maxWidth="450px" />

## Configuration

<RS485AddressNote />

# EM24


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/customers/carlo_gavazzi/logo.png"
    alt="logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>


## Supported Devices


<DeviceSupportTable
  devices={[
   {
        type: 'Carlo Gavazzi EM24',
        modbusTcp: '✅',
        rs485: '✅',
   }
  ]}
  showModbusTcp={true}
  showRs485={true}
/>
> [!NOTE]
> The availability of ethernet and rs485 depends on the exact subtype of EM24 you use.

<ClickableImage src="/img/customers/carlo_gavazzi/em24.png" alt="Image 1" maxWidth="450px" />


## Wiring

The <BrandName /> <ControllerName /> and the device communicate via RS485 or Ethernet.

### Ethernet
For correct ethernet wiring: Follow the [the guidelines for ethernet wiring](/Controller/wiring-best-practices/#ethernet).

### RS485
<RS485ConnectionTable firstColumn={["Terminal 41 / A-", "Terminal 42 / B+", "Terminal 43 / GND"]} />
<ClickableImage src="/img/customers/carlo_gavazzi/em24_wiring.png" alt="Image 1" maxWidth="450px" />

## Configuration
Check that the Carlo Gavazzi meter is set to read both import and export power. An unsuitable mode may lead to:
- Missing readings of feed-in, or
- Feed-in being counted as offtake (on top of the ‘actual offtake’)

You can set this in the ‘MEASurE’ configuration menu on the energy meter. This should be set to ‘b’.

> [!WARNING]
> This setting may not be present on MID certified models (model numbers ending in PFA and PFB).
<ClickableImage src="/img/customers/carlo_gavazzi/em24_config_pt1.png" alt="Image 1" maxWidth="450px" />

<RS485AddressNote />
Set the Modbus address through the power meter's “Address” configuration menu.

# EM300 Series


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/customers/carlo_gavazzi/logo.png"
    alt="logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>


## Supported Devices


<DeviceSupportTable
  devices={[
    {
        type: 'Carlo Gavazzi EM330',
        modbusTcp: '❌',
        rs485: '✅',
      instructionVideos: [{"videoId": "Fmn9oDCqqYg", "title": "Carlo Gavazzi EM330 S1 · touch", "description": "EM330 S1 touch-interface version."}]
    },
    { 
        type: 'Carlo Gavazzi EM340',
        modbusTcp: '❌',
        rs485: '✅',
      instructionVideos: [{"videoId": "Pifk4XH8CLU", "title": "Carlo Gavazzi EM340 S1 · touch", "description": "EM340 S1 touch-interface version."}]
    }
  ]}
  showModbusTcp={true}
  showRs485={true}
/>

<ClickableImage src="/img/customers/carlo_gavazzi/em340.jpg" alt="Image 1" maxWidth="250px" />


## Wiring

### RS485
<RS485ConnectionTable firstColumn={["", "", ""]} />


## Configuration
<RS485AddressNote />

Set the Modbus address through the power meter's “Address” configuration menu.
<ClickableImage src="/img/customers/carlo_gavazzi/em340_config_pt1.png" alt="Image 1" maxWidth="450px" />
<ClickableImage src="/img/customers/carlo_gavazzi/em340_config_pt2.png" alt="Image 1" maxWidth="450px" />

# EM511


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/customers/carlo_gavazzi/logo.png"
    alt="logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>


## Supported Devices

<DeviceSupportTable
  devices={[
    { 
        type: 'Carlo Gavazzi EM511',
        modbusTcp: '❌',
        rs485: '✅',
      instructionVideos: [{"videoId": "xcuHr76gWD4", "title": "Carlo Gavazzi EM511 · S1 X · RS485", "description": "Models: EM511 DIN AV8 1 X S1 X."}]
    }
  ]}
  showModbusTcp={true}
  showRs485={true}
/>

<ClickableImage src="/img/customers/carlo_gavazzi/em511.webp" alt="Image 1" maxWidth="450px" />


## Wiring

### RS485
<RS485ConnectionTable firstColumn={["Terminal 8 / A-", "Terminal 6 / B+", "Terminal 7 / GND"]} />
<ClickableImage src="/img/customers/carlo_gavazzi/em511config.png" alt="Image 1" maxWidth="450px" />
## Configuration
<RS485AddressNote />


# EM500 Series


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/customers/carlo_gavazzi/logo.png"
    alt="logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>


## Supported Devices


<DeviceSupportTable
  devices={[
    { 
        type: 'Carlo Gavazzi EM500 Series',
        Variants: 'EM530, EM540',
        modbusTcp: '❌',
        rs485: '✅',
      instructionVideos: [{"videoId": "T4Kf1sV9zlU", "title": "Carlo Gavazzi EM530 · S1 X · RS485", "description": "Models: EM530 DIN AV5 3 X S1 X."}, {"videoId": "q8sZrsEDZq0", "title": "Carlo Gavazzi EM540 · S1 X · RS485", "description": "Models: EM540 DIN AV2 3 X S1 X."}]
    }
  ]}
  showVariants={true}
  showModbusTcp={true}
  showRs485={true}
/>
  

<ClickableImage src="/img/customers/carlo_gavazzi/em530.png" alt="Image 1" maxWidth="450px" />


## Wiring

### RS485
<RS485ConnectionTable firstColumn={["Terminal 9 / A-", "Terminal 8 / B+", "N/A"]} />
<ClickableImage src="/img/customers/carlo_gavazzi/em530_config_pt1.png" alt="Image 1" maxWidth="450px" />


## Configuration
<RS485AddressNote />

# Carlo Gavazzi


import { FolderOverview } from '@/components/FolderOverview';

# Carlo Gavazzi

<FolderOverview folder="Controller/Devices/Energy-meter/Carlo Gavazzi" />


# VMU-S Series


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/customers/carlo_gavazzi/logo.png"
    alt="logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>


## Supported Devices

<DeviceSupportTable
  devices={[
    { 
        type: 'Carlo Gavazzi VMU-S',
        modbusTcp: '❌',
        rs485: '✅',
    }
  ]}
  showModbusTcp={true}
  showRs485={true}
/>

> [!NOTE] System Architecture
> The **VMU-S** is a modular system. It requires a **VMU-M (Master)** unit to handle the RS485 communication. The VMU-S modules plug directly into the side of this master unit.

| VMU-S (String Unit) | VMU-M (Master Unit) |
| :---: | :---: |
| <ClickableImage src="/img/customers/carlo_gavazzi/vmu-s.png" alt="Carlo Gavazzi VMU-S" maxWidth="400px" /> | <ClickableImage src="/img/customers/carlo_gavazzi/vmu-m.png" alt="Carlo Gavazzi VMU-M" maxWidth="400px" /> |


## Wiring

### Bus Connection (Mechanical)
The VMU-S connects to the VMU-M master unit via the local bus connector on the side. 

> [!CAUTION] Do not Hot-Swap!
> **Risk of equipment damage:** Only join or separate the VMU-S modules from the Master unit when the power supply is **OFF**. Connecting modules while the system is powered can damage the internal electronics.

### RS485 (Data Connection)
Although you are measuring with the VMU-S, the **RS485 cable** connects to the **VMU-M Master unit**. The VMU-S sends its data internally to this master unit.

<RS485ConnectionTable firstColumn={["Terminal 11 / B-", "Terminal 12 / A+", "Terminal 10 / GND"]} />

### DC Power Wiring (VMU-S)
The VMU-S modules are wired in series with the PV strings:
* **Top Terminals (1 & 3):** Input from PV String (+ and -).
* **Bottom Terminals:** Output to Inverter (+ and -).

> [!WARNING] Polarity
> Ensure the correct polarity (Top to Bottom). If the polarity is reversed, the Status LED on the VMU-S will blink **Violet** (Blue -> Violet cycle).

## Configuration

### 1. Hardware Configuration (VMU-M)
Since the VMU-S has no display, you configure the Modbus settings on the **Master unit** (VMU-M).

<RS485AddressNote />

1.  On the VMU-M unit, hold the joystick to enter the menu (Password: **0000**).
2.  Go to **SETTINGS** > **COM**.
3.  Set **ADDRESS** (e.g., 1). This is the address you will use in the <ControllerName />.
4.  Set **BAUDRATE** to **9600** (default).
5.  Set **PARITY** to **No** (default).

### 2. Module Scan
After installing the VMU-S modules, the Master unit must recognize them:
1.  On the VMU-M, go to **SETTINGS** > **SYSTEM**.
2.  Select **Modules Scan**.
3.  Verify on the display that the number of found modules matches the amount of installed VMU-S units.

### 3. <ControllerName /> Configuration
When adding this device to the <ControllerName />, you will be asked for the **Amount of Strings**.
* Enter the total number of VMU-S modules connected to this specific VMU-M Master unit.
* The driver will automatically scan and add each string as a sub-device.

<ClickableImage src="/img/customers/carlo_gavazzi/vmu-m.png" alt="VMU-M master unit display and controls" maxWidth="450px" />


# Chargee


import { BrandName, ControllerName } from '@site/src/components/customFields';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

Chargee produces energy readout devices that connect to the p1-interface of smart meters.
The <BrandName /> <ControllerName /> supports the Sparky P1 meter from Chargee. More information can be found on the [Chargee website](https://chargee.energy/).
<ClickableImage
  src="/img/customers/chargee/sparky.png"
  alt="Wiring"
  maxWidth="30%"
/>
## Supported Devices
You can use two different methods to connect the Sparky P1 meter to the <BrandName /> <ControllerName />: via the Local API (recommended) or via the Cloud API. 
- The local API means that we directly connect to the Sparky P1 meter using the local network. The <BrandName /> <ControllerName /> connects to the Sparky P1 meter using its IP address.
- The cloud API means that we connect to the Sparky P1 meter via Chargee's cloud servers. In this case, the <BrandName /> <ControllerName /> connects to Chargee's cloud using your Chargee account credentials.

__We recommend using the Local API__, as it offers better reliability and faster readout speeds. Use the Cloud API only if the Local API is not an option for you.

<DeviceSupportTable
  devices={[
    { type: 'Sparky P1 Meter', localApiCol: '✅', cloudApiCol: '✅'}
  ]}
  customColumns={{ "localApiCol": "Local API (recommended)", "cloudApiCol": "Cloud API" }}/>


## Local API: Setup Instructions
1. First, configure the Sparky P1 meter and app according to the [Chargee Sparky P1 meter manual](https://support.chargee.energy/en/articles/8774240-how-do-i-install-sparky).
2. Connect your <BrandName /> <ControllerName /> to the same network as your Sparky P1 meter.
3. Scan your Sparky P1 meter in Devices Wizard of the <BrandName /> <ControllerName />. Identify it using its IP address or MAC address.
4. Finish the Devices Wizard. By default, we configure the Sparky P1 meter as a grid meter, but you can change this in the device settings after adding the device.

## Cloud API: Setup Instructions
1. First, configure the Sparky P1 meter and app according to the [Chargee Sparky P1 meter manual](https://support.chargee.energy/en/articles/8774240-how-do-i-install-sparky).
3. Scan your Sparky P1 meter in Devices Wizard of the <BrandName /> <ControllerName /> and enter your Chargee username and password when prompted.
4. Finish the Devices Wizard. By default, we configure the Sparky P1 meter as a grid meter, but you can change this in the device settings after adding the device.

# Chint


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/sgo/Logo_Chint.png"
    alt="Chint"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

## Supported Devices


<DeviceSupportTable
  devices={[
    { 
        type: 'DDSU666',
        variants: '230V-5/80A 230V-100A/40mA',
        modbusTcp: '✅',
        rs485: '✅',
      instructionVideos: [{"videoId": "sOIv-lWvyt0", "title": "CHINT DDSU666 · 36 mm · single button"}, {"videoId": "y4DW5fvJfU4", "title": "CHINT DDSU666 · 100 A / 40 mA · single button"}]
    },
    { 
        type: 'DTSU666',
        variants: '3x230V/400V-5/80A 3x230V/400V-1.5(6)A 3x230V/400V-100A/40mA',
        modbusTcp: '✅',
        rs485: '✅',
      instructionVideos: [{"videoId": "qNfsDyM7sA4", "title": "CHINT DTSU666 · 5(80) A / 1.5(6) A"}, {"videoId": "Dsj_QSy1oIQ", "title": "CHINT DTSU666 · 100 A / 40 mA"}]
    },
    { 
        type: 'DTSU666-CT',
        variants: '3x230V/400V-100A/40mA 3x230V/400V-250A/50mA',
        modbusTcp: '❌',
        rs485: '✅',
    },
    { 
        type: 'DTSU666HW',
        variants: '3x230V/400V-5/80A 3x230V/400V-1.5(6)A 3x230V/400V-100A/40mA',
        modbusTcp: '✅',
        rs485: '✅',
      instructionVideos: [{"videoId": "GjLXzcb4rSI", "title": "CHINT DTSU666-HW · two measurement channels"}]
    },
        { 
        type: 'DTSU666 for Afore',
        variants: '3x230V/400V-5/80A',
        modbusTcp: '❌',
        rs485: '✅',
      instructionVideos: [{"videoId": "kiWdfm-mXno", "title": "CHINT DTSU666 for Afore · 5(80) A"}]
    },
    { 
        type: 'DTSU666-20',
        variants: '',
        modbusTcp: '❌',
        rs485: '✅',
      instructionVideos: [{"videoId": "qggSNX2-UTA", "title": "CHINT DTSU666-20 · A/B terminal strip"}]
    }
  ]}
  showVariants={true}
  showModbusTcp={true}
  showRs485={true}/>

### Which variant do I have?

The current specification is printed on the front of the meter:

- **1.5(6)A** is the DTSU666 for standard current transformers with a 5 A secondary (x/5A).
- **100A/40mA** and **250A/50mA** are meters that come with their own current transformers (DTSU666-CT).
- **5(80)A** is a direct-connected meter, without current transformers.

## Connection

The communication between the <BrandName /> and the energy meter operates via an RS-485 serial bus or Modbus TCP.

It is recommended to use shielded cables with twisted pairs for optimal performance. For short distances, a twisted pair from a network cable (minimum CAT5e) can be used.

The following guidelines apply:
 - **Maximum Distance**: The total cable length, including the main cable and branches, is limited to 100 meters.
 - **Connecting Multiple Energy Meters**: The cable should be daisy-chained from meter to meter or branched off the main cable (branches must not exceed 1 meter).
 - **Long Distances**: It is recommended to install a 120Ω termination resistor at the end of the main cable and activate the termination resistor on the <BrandName /> <ControllerName />.


<RS485ConnectionTable firstColumn={["Terminal 24", "Terminal 25", "N/A"]} />
![Chint Wiring](/media/chint/chint-1.png)

<RS485AddressNote />

# Cloud Meter Data

import { BrandName, ControllerName } from '@site/src/components/customFields';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/sgo/Logo_CloudData.png"
    alt="logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>


## Supported Devices

<DeviceSupportTable
  devices={[
    {
      type: "Energy Meter",
      api: '✅', 
    },
  ]}
  showApi={true}
/>

# Dornscheidt


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/sgo/Logo_Dornscheidt.png"
    alt="Dornscheidt"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

## Supported Devices


<DeviceSupportTable
  devices={[
    { 
        type: 'Pro380',
        modbusTcp: '✅',
        rs485: '✅',
    }   
  ]}
  showModbusTcp={true}
  showRs485={true}/>

<ClickableImage src="/img/customers/dornscheidt/pro380.jpg" alt="Image 1" maxWidth="450px" />

## Wiring

### RS485

> [!IMPORTANT] Check the Pro380 terminal labels
> Follow the manufacturer wiring diagram for the exact Pro380 revision. Connect **RS485 A/+** to controller **A**, **RS485 B/-** to controller **B**, and the communication reference to **GND** when available. Verify the labels on the installed meter before energising the bus.


## Configuration

<RS485AddressNote />


# Eastron


import { FolderOverview } from '@/components/FolderOverview';

# Eastron

<FolderOverview folder="Controller/Devices/Energy-meter/Eastron" />


# SDM120M


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/customers/eastron/logo.png"
    alt="logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>


## Supported Devices


<DeviceSupportTable
  devices={[
    { 
        type: 'Eastron SDM120M',
        modbusTcp: '❌',
        rs485: '✅',
      instructionVideos: [{"videoId": "haoUGgswT7o", "title": "Eastron SDM120-M · 118 mm · RS485", "description": "Use the exact model and connector version shown in this video."}]
    },
  ]}
  showModbusTcp={true}
  showRs485={true}
/>

<ClickableImage src="/img/customers/eastron/sdm120m.png" alt="Image 1" maxWidth="200px" />

## Wiring
### RS485
<RS485ConnectionTable firstColumn={["Terminal 10 / A+", "Terminal 9 / B-", "N/A"]} />
<ClickableImage src="/img/customers/eastron/sdm120m_wiring.png" alt="Image 1" maxWidth="150px" />


## Configuration
<RS485AddressNote />
<ClickableImage src="/img/customers/eastron/sdm120m_config_pt1.png" alt="Image 1" maxWidth="350px" />

# SDM630


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/customers/eastron/logo.png"
    alt="logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>


## Supported Devices

<DeviceSupportTable
  devices={[
    { 
        type: 'Eastron SDM630',
        modbusTcp: '❌',
        rs485: '✅',
      instructionVideos: [{"videoId": "XWyCm2qC6Ko", "title": "Eastron SDM630-Modbus V2 · RS485", "description": "Use the exact model and connector version shown in this video."}]
    }
  ]}
  showModbusTcp={true}
  showRs485={true}
/>

<ClickableImage src="/img/customers/eastron/sdm630.png" alt="Image 1" maxWidth="350px" />

## Wiring
### RS485
<RS485ConnectionTable firstColumn={["A", "B", "N/A"]} />
<ClickableImage src="/img/customers/eastron/sdm630_wiring.png" alt="Image 1" maxWidth="350px" />


## Configuration
<RS485AddressNote />
<ClickableImage src="/img/customers/eastron/sdm630_config_pt1.png" alt="Image 1" maxWidth="350px" />

# Smartrail X835


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/customers/eastron/logo.png"
    alt="logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>


## Supported Devices


<DeviceSupportTable
  devices={[
    { 
        type: 'Eastron Smartrail X835',
        modbusTcp: '❌',
        rs485: '✅',
    }
  ]}
  showModbusTcp={true}
  showRs485={true}
/>

<ClickableImage src="/img/customers/eastron/smartrail_x835.png" alt="Image 1" maxWidth="350px" />

## Wiring
### RS485
<RS485ConnectionTable firstColumn={["Terminal 14 / A", "Terminal 13 / B", "N/A"]} />
<ClickableImage src="/img/customers/eastron/smartrail_x835_wiring.png" alt="Image 1" maxWidth="350px" />


## Configuration
<RS485AddressNote />
<ClickableImage src="/img/customers/eastron/smartrail_x835_config_pt1.png" alt="Image 1" maxWidth="350px" />
<ClickableImage src="/img/customers/eastron/smartrail_x835_config_pt2.png" alt="Image 1" maxWidth="350px" />

# Eneco


import { ControllerName } from '@site/src/components/customFields';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/customers/eneco/logo.png"
    alt="Eneco"
    style={{ display: "block", margin: "0 auto", width: "25%"}}
/>

The Eneco Dongle is a P1 reader that plugs into the P1 port of your digital utility meter and shares its readings over the local network.

## Supported Devices

<DeviceSupportTable
  devices={[
    {
        type: 'Eneco Dongle',
        network: '✅',
    }
  ]}
  customColumns={{ network: 'Network (Wi-Fi / Ethernet)' }}
  />

## Configuration

### Installation Requirements
- The dongle must be plugged into the P1 port of your digital utility meter.
- The dongle and the <ControllerName /> must be on the same local network.
- The dongle must be connected to the internet using the **Eneco app** or the **SmartBridge Connect app** from NET2GRID.

### Adding the Device
1. Select **Devices** in the menu and start the device wizard.
2. Choose **Energy Meters** and select **Eneco**.
3. Select **Ethernet TCP** and search for the device with the MAC address of your dongle (this is printed on the dongle) 
4. Click **Search**, then **End scan and go to results**.
5. Click **Save and go to device settings**, fill in the settings and click **Save**.


# Eniris


import { FolderOverview } from '@/components/FolderOverview';

# Eniris

<FolderOverview folder="Controller/Devices/Energy-meter/Eniris" />


# Pulse energy meters


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/sgo/Logo_Eniris.png"
    alt="Eniris"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

## Supported Devices

<DeviceSupportTable
  devices={[
    { 
        type: 'Bidirectional Pulse Energy Meter',
        customCol: '✅',
    },
    { 
        type: 'Unidirectional Pulse Energy Meter',
        customCol: '✅',   
    }
  ]}
   customColumns={{ "customCol": "Digital I/O Inputs" }}
  showManual={true}
  showModbusTcp={true}
  showRs485={true}
/>

# EnjoyPowers


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/sgo/Logo_EnjoyPowers.png"
    alt="EnjoyPowers"
    style={{ display: "block", margin: "0 auto", width: "40%" }}
/>

# EnjoyPowers

## Supported Devices

<DeviceSupportTable
  devices={[
    {
        type: 'SinE-STS static transfer switch',
        modbusTcp: '❌',
        rs485: '✅',
        curtailment: '❌'
    }
  ]}
  showModbusTcp={true}
  showRs485={true}
  showCurtailment={true}
/>

The SinE-STS is the static transfer switch of an EnjoyPowers PCS+STS system. It switches the
installation between the grid and a diesel generator, and it measures the connection point it
switches. The <BrandName /> <ControllerName /> reads it as an energy meter: line and phase
voltages, phase currents, active, reactive and apparent power per phase and in total, power
factor, grid frequency, the switch temperature, and the cumulative and daily charge and discharge
energy. Faults reported by the switch (grid, hardware, system, switch and other fault words) are
shown as status messages on the device.

> [!NOTE] The STS is measured, not controlled
> The <BrandName /> <ControllerName /> never sends power setpoints to the STS and never switches it
> between grid and generator mode by itself. Control the battery through the EnjoyPowers PCS
> instead: see [EnjoyPowers PV, hybrid and battery inverters](/Controller/Devices/PV-hybrid-and-battery-inverters/EnjoyPowers/).

## Wiring

### RS485

The STS is connected over RS485 only. It communicates at 9600 baud, 8 data bits, no parity, 1 stop
bit — the factory default settings.

<RS485ConnectionTable firstColumn={["RS485 A", "RS485 B", "GND"]} />

## Configuration

<RS485AddressNote />

### Settings on the STS

Two settings of the STS can be changed from the <BrandName /> <ControllerName />. Open the
**Devices** page, find the STS and click **Change physical settings**:

| Setting | Values | Description |
| --- | --- | --- |
| STS enable | Disabled / Enabled (dedicated for PCS+STS systems) | Enables the static transfer switch. Only enable this in a PCS+STS system. |
| Diesel generator mode | Grid mode / Diesel generator mode | Selects whether the installation runs on the grid or on the diesel generator. |

> [!WARNING] Switching modes is a manual action
> Neither setting is changed automatically. The <BrandName /> <ControllerName /> only writes them
> when you change them here, and it does not switch to diesel generator mode on a grid outage.
> All other STS parameters (grid voltage and frequency limits, PCS host address, STS parallel
> master/slave, transformer soft-start) must be set on the STS itself.


# Fluvius


import { BrandName, ControllerName } from '@site/src/components/customFields';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';
import ClickableImage from '@site/src/components/ClickableImage';

<img
    src="/img/sgo/Logo_Fluvius.png"
    alt="Fluvius"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

## Supported Devices

<DeviceSupportTable
  devices={[
    {
        type: 'Fluvius Digital Meter (Standard P1)',
        description: 'Residential & SME (DSMR 5 / 4.2 / 2.2)',
        p1: '✅',
    },
    {
        type: 'Fluvius Industrial (A1 Port)',
        description: 'Industrial meters with Transformer connection',
        p1: '✅',
    },
  ]}
  showP1={true}
  />

> [!CAUTION] Crucial: Activate the P1 Port first!
> By default, the User Port (P1) on the digital meter is **closed**. The <ControllerName/> cannot detect the meter if the port is not active.
>
> 1.  Log in to [mijn.fluvius.be](https://mijn.fluvius.be).
> 2.  Go to **Producten & Diensten** > **Verbruik** > **Beheer poorten**.
> 3.  **Enable** the P1 port.
> 4.  **Check the display on the meter:** A small triangle arrow (▼) must be visible above the text **"P1"**. If this arrow is missing, the port is dead.

## Connection

### 1. Wiring
Connect the Digital Meter to the <ControllerName/> using a **P1 Cable** (USB to RJ12).

1.  Locate the yellow rubber cover labeled **P1** on the right side of the meter.
2.  Plug the **RJ12 connector** into the P1 port.
3.  Plug the **USB connector** into the <ControllerName/>.

> [!WARNING] P1 vs S1
> Do **not** use the **S1** port (often an RJ45 port on top). This is for the grid operator only. You must use the **P1** user port on the side.

## Configuration

### Standard Meter (Most Common)
For standard residential and small business connections (direct measurement):

1.  Navigate to the **Settings** page on the <ControllerName/>.
2.  Click on **Scan for devices**.
3.  The system will automatically detect the meter protocol (DSMR 5 or older DSMR 2.2).
4.  Add the device labeled **"Digital Smart Meter"**.

### Industrial Meter (A1 Port)
Only for installations using the **A1 port** (typically high voltage/current with transformers):

When adding an A1 device, the system will ask for **Scale Factors**. You must match these to the installation's transformers (CT/PT ratios) to get correct readings.

* **Voltage Scale Factor:** The ratio of the voltage transformer. (Default: 1.0)
* **Current Scale Factor:** The ratio of the current transformer. (Default: 1.0)

> *Example: If you have a 100A/5A Current Transformer, your Current Scale Factor is 20.*

## Troubleshooting

| Problem | Possible Cause & Solution |
| :--- | :--- |
| **Meter not found** | **P1 Port inactive:** Check the Fluvius portal. Is the arrow (▼) visible above "P1" on the LCD display? |
| **Meter not found** | **Wrong Port:** Ensure the cable is in the P1 port (RJ12), not the S1 port. |
| **Meter not found** | **Cable issue:** Use a verified P1 cable. Standard telephone cables often do not work because the signal lines are inverted. |
| **No Voltage displayed** | Some older meters (DSMR 2.2) or specific brands (Landis+Gyr) do not send voltage data. This is a limitation of the meter itself, not the controller. |
| **Wrong Power Values (A1)** | If values are too low/high on an A1 meter, check the **Scale Factors** in the device settings. You may have entered `1` instead of the transformer ratio. |

# Fronius


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/customers/fronius/logo.png"
    alt="Fronius"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>


## Supported Devices


<DeviceSupportTable
  devices={[
    { 
        type: 'Fronius 63A1',
        modbusTcp: '❌',
        rs485: '✅',
      instructionVideos: [{"videoId": "cIbXgExWryQ", "title": "Fronius Smart Meter 63A-1 · RS485", "description": "Models: Fronius Smart Meter 63A-1."}]
    },
      { 
        type: 'Fronius 63A3',
        modbusTcp: '❌',
        rs485: '✅',
      instructionVideos: [{"videoId": "CFslQ9zGgcg", "title": "Fronius Smart Meter 63A-3 · RS485", "description": "Models: Fronius Smart Meter 63A-3."}]
    }   
  ]}
  showModbusTcp={true}
  showRs485={true}/>  

<ClickableImage src="/img/customers/fronius/63A1.png" alt="Image 1" maxWidth="200px" />

## Wiring

### RS485

> [!IMPORTANT] Check the terminal labels for the exact meter model
> Terminal positions differ between the Fronius 63A1 and 63A3. Follow the manufacturer wiring diagram and connect **RS485 A/+** to controller **A**, **RS485 B/-** to controller **B**, and the communication reference to **GND** when available. Do not copy terminal numbers from a different Fronius meter.


## Configuration

<RS485AddressNote />


# Hager


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/sgo/Logo_Hager.png"
    alt="Hager"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

## Supported Devices


<DeviceSupportTable
  devices={[
    { 
        type: 'Hager EC - Series',
        modbusTcp: '❌',
        rs485: '✅',
      instructionVideos: [{"videoId": "6FKFFV5-HCE", "title": "Hager EC700 · RS485", "description": "Models: Hager EC700."}]
    },
    {
      type: 'Hager TXF121',
        modbusTcp: '❌',
        rs485: '✅'
    },
  ]}
  showModbusTcp={true}
  showRs485={true}/>

<ClickableImage src="/img/customers/hager/ec700.png" alt="Image 1" maxWidth="450px" />

## Wiring

### RS485

> [!IMPORTANT] Check the terminal labels for the exact meter model
> Hager terminal numbers differ between the EC series and TXF121. Follow the manufacturer wiring diagram and connect the meter's **RS485 A/+** to controller **A**, **RS485 B/-** to controller **B**, and the communication reference to **GND** when the meter provides one. Do not infer terminal numbers from another Hager model.


## Configuration

<RS485AddressNote />


# HomeWizard


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/sgo/Logo_HomeWizard.png"
    alt="HomeWizard"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

## Supported Devices


<DeviceSupportTable
  devices={[
    { 
        type: 'HomeWizard Wifi P1 Dongle',
        modbusTcp: '✅',
    },
    { 
        type: 'HomeWizard Wifi 1-Phase Meter',
        modbusTcp: '✅',
    },
    { 
        type: 'HomeWizard Wifi 3-Phase Meter',
        modbusTcp: '✅',
    },
    { 
        type: 'HomeWizard Wifi Energy Socket',
        modbusTcp: '✅',
    }   
  ]}
  showModbusTcp={true}
  />

The Energy Socket can be added as an energy meter to monitor the consumption of a single appliance
without ever switching it. See the [Energy Socket page](/Devices/Switched-loads/Homewizard/) for
details on the switched-load and energy-meter use cases.

<ClickableImage src="/img/customers/homewizard/p1dongle.png" alt="Image 1" maxWidth="450px" />

## Configuration

To communicate with your HomeWizard device the local API must be enabled.

1. Open the HomeWizard Energy app.
2. Go to "Settings"
3. Go to "Meters"
4. Select the meter you want to connect to.
5. Enable the "Local API" option.

# Huawei


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/sgo/Logo_Huawei.png"
    alt="Huawei"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

## Supported Devices


<DeviceSupportTable
  devices={[
    { 
        type: 'Energy Meter via Smartlogger',   
        modbusTcp: '✅',
        rs485: '❌',
    }   
  ]}
  showModbusTcp={true}
  showRs485={false}
  />

<ClickableImage src="/img/customers/huawei/smartlogger3000.jpg" alt="Image 1" maxWidth="250px" />

The Huawei SmartLogger can be used to read and control energy meters/solar inverters/batteries.

An energy meter that is connected to the SmartLogger, such as the Chint DTSU666-H or DTSU666-HW, is read through the SmartLogger over Modbus TCP. Do not connect it to the RS485 bus of the <BrandName /> <ControllerName /> as well: the SmartLogger already reads that bus, and an RS485 bus can only have one reading device. When adding the SmartLogger, answer **Yes** to "Is an energy meter connected to the Huawei inverter or Huawei SmartLogger?".

## Wiring - Ethernet
For correct ethernet wiring: Follow the [the guidelines for ethernet wiring](/Controller/wiring-best-practices/#ethernet).

## Configuration

### 1. Activating Modbus in the SmartLogger
1. Surf to the IP address of the SmartLogger.
2. Login to the SmartLogger (default password: "Changeme").
3. Change “Link setting” to “Enable (Unlimited)”.
4. Set “Address mode” to “Communication address”.
5. Choose the Modbus address of the logger. We recommend that this is different from the addresses of the inverters (see also the next step in the manual).
6. Click submit.

<ClickableImage src="/img/customers/huawei/smartlogger3000_config_pt1.png" alt="Image 1" maxWidth="600px" />
<ClickableImage src="/img/customers/huawei/smartlogger3000_config_pt2.png" alt="Image 1" maxWidth="600px" />

### 2. Device Modbus Addresses
The smartlogger can connect both inverters and energy meters via 3 COM ports. Adding and giving Modbus addresses can be done automatically or not.

However... all Modbus addresses must be different!

<ClickableImage src="/img/customers/huawei/smartlogger3000_config_pt3.png" alt="Image 1" maxWidth="600px" />

To adjust this, it is best to first adjust the possible addresses per COM port so that there is no overlap.
<ClickableImage src="/img/customers/huawei/smartlogger3000_config_pt4.png" alt="Image 1" maxWidth="600px" />

Then you remove the devices with the same address and add them back with an address different from all other devices.
<ClickableImage src="/img/customers/huawei/smartlogger3000_config_pt5.png" alt="Image 1" maxWidth="600px" />

# IMT


# IMT irradiance sensor

Measure the sunlight reaching your PV installation with the IMT Si-RS485TC-T-MB. This sensor reports solar irradiance in W/m², providing context alongside solar-production measurements.

## Supported model

| Sensor manufacturer | Compatible sensor model | Data connection | Measured quantity |
| --- | --- | --- | --- |
| IMT Technology (Mencke & Tegtmeyer) | Si-RS485TC-T-MB | RS485 / Modbus RTU | Solar irradiance in W/m² |

Find the sensor in the commissioning wizard using this selection:

```text
Energy meter → IMT → SiRS485TCTMB-Pyranometer
```

Although it appears in the Energy meter category, it measures sunlight, not electrical power or energy. It does not replace the grid meter used for import/export measurement. The supported measurement for this connection is irradiance; cell temperature and optional temperature or wind sensors are not read by this integration.

## Before you connect

- Mount the sensor with the same tilt and orientation as the PV modules, away from shading.
- Provide the sensor's power supply: 24 V DC nominal, within its 10–28 V DC operating range.
- Connect the sensor to a supported RS485 connection on the controller. Follow the [RS485 cable routing, polarity and termination](/Controller/wiring-best-practices) and the [IMT installation instructions](https://imt-technology.com/fileadmin/docs/en/products/Si-Sensor-RS485_IM_EN.pdf) for polarity, shielding and mounting.

The sensor's factory communication settings are:

| Setting | Factory value |
| --- | --- |
| Communication protocol | `Modbus RTU` |
| Default Modbus address | `1` |
| Default serial speed | `9600 baud` |
| Serial framing | 8 data bits, no parity, 1 stop bit (8N1) |

If the sensor has already been configured, use its actual settings. Each sensor on the same RS485 bus needs a unique Modbus address; supported addresses are 1–247. This model uses RS485, not a direct Ethernet/Modbus TCP connection.

## Add the sensor

1. Open the commissioning wizard and go to [Add other devices](/Controller/Configuration%20from%20A%20to%20Z/6-other-devices).
2. Choose the category, manufacturer and sensor model shown above.
3. Select the RS485 connection and use the sensor's communication settings.
4. Run the scan in daylight with the sensor uncovered, then select and save the detected sensor.
5. Check that the irradiance reading in W/m² updates when sunlight changes.

<Callout type="info" title="Scan in daylight">
  A reading of 0 W/m² can prevent this sensor from being detected. If it is not found at night or while covered, repeat the scan with light on the sensor before changing the wiring or settings.
</Callout>

## Using the measurement

Irradiance helps distinguish reduced solar production caused by less sunlight from changes that need further investigation. It is a measurement per unit of area, not the installation's total power in kW or generated energy in kWh.

For the wider monitoring overview, see [Meters, sensors, gateways & building systems](/Monitoring/Integrations/Energy%20meters). Sensor communication details are available in the [IMT Modbus specification](https://imt-technology.com/fileadmin/docs/en/products/Si-RS485_Modbus_SPEC_EN.pdf).


# Energy Meter


import { FolderOverview } from '@/components/FolderOverview';

# Energy Meter

## Irradiance sensors

The Energy meter category in the commissioning wizard also includes this solar-irradiance sensor:

| Manufacturer | Supported model | Connection | Measurement |
| --- | --- | --- | --- |
| [IMT](/Controller/Devices/Energy-meter/IMT) | Si-RS485TC-T-MB | RS485 / Modbus RTU | Solar irradiance in W/m² |

See the [IMT connection guide](/Controller/Devices/Energy-meter/IMT) for wiring, communication settings and commissioning.

## Browse manufacturers

<FolderOverview folder="Controller/Devices/Energy-meter" />


# Inepro


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/customers/inepro/logo.png"
    alt="logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>


## Supported Devices


<DeviceSupportTable
  devices={[
    { 
        type: 'Inepro PRO380',
        modbusTcp: '❌',
        rs485: '✅',
      instructionVideos: [{"videoId": "_QyCDOCciSM", "title": "Inepro PRO380-Mod · RS485", "description": "PRO380-Mod 100 A direct-connected version with green auxiliary terminals and menu V2.18."}]
    }   
  ]}
  showModbusTcp={true}
  showRs485={true}
/>  

## Wiring
### RS485
<RS485ConnectionTable firstColumn={["A (pin 22)", "B (pin 23)", "N/A"]} />
<ClickableImage src="/img/customers/inepro/pro380-wiring.png" alt="Image 1" maxWidth="350px" />


## Configuration
<RS485AddressNote />

Refer to the meter manual for more detailed information on changing the Modbus address.
By default, the meter is set to address 1. This can be changed via the meter display.

1. Use the buttons to go to Program Mode 2.
2. Press and hold the right button for 3 seconds to open the menu.
3. Scroll to the LCD page Modbus/M-bus ID (addr xxx).
4. Press and hold the right button for 5 seconds to enter programming mode.
5. The value begins to flash: select 3 digits (Modbus: 001-247). Confirm each digit by holding down both buttons for 3 seconds.
6. The LCD shows OK when the setting is confirmed.

<ClickableImage src="/img/customers/inepro/pro380_config_pt1.png" alt="Image 1" maxWidth="350px" />

# Iskra


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/sgo/Logo_Iskra.png"
    alt="Iskra"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

## Supported Devices



<DeviceSupportTable
  devices={[
    { 
        type: 'DSMR Smart Meter',
        customCol: '✅',
    }
  ]}
    customColumns={{ "customCol": "P1 to USB" }}
    />

<ClickableImage src="/img/customers/iskra/image.png" alt="Image 1" maxWidth="450px" />

# Janitza


import { FolderOverview } from '@/components/FolderOverview';

# Janitza

<FolderOverview folder="Controller/Devices/Energy-meter/Janitza" />


# RMU 301 CBM


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable'; 

<img
    src="/img/customers/janitza/logo.png"
    alt="logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>


## Supported Devices


<DeviceSupportTable
  devices={[
    { 
        type: 'Janitza RMU 301 CBM',
        modbusTcp: '❌',
        rs485: '✅',
      instructionVideos: [{"videoId": "EwIzEMhicsA", "title": "Janitza RMU 301-CBM · three-pole RS485", "description": "RMU 301-CBM with the three-pole RS485 connector shown in manual 2.057.008.0.c."}]
    },
  ]}
  showModbusTcp={true}
  showRs485={true}
/>


<ClickableImage src="/img/customers/janitza/rmu301-cbm.png" alt="Image 1" maxWidth="350px" />

## Wiring
### RS485
<RS485ConnectionTable firstColumn={["A", "B", "N/A"]} />
<ClickableImage src="/img/customers/janitza/rmu301-cbm-wiring.png" alt="Image 1" maxWidth="350px" />


## Configuration
<RS485AddressNote />


# UMG 103-CBM


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable'; 

<img
    src="/img/customers/janitza/logo.png"
    alt="logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>


## Supported Devices


<DeviceSupportTable
  devices={[
    { 
        type: 'Janitza UMG 103-CBM',
        modbusTcp: '❌',
        rs485: '✅',
    },
  ]}
  showModbusTcp={true}
  showRs485={true}
/>


<ClickableImage src="/img/customers/janitza/umg103-cbm.png" alt="Image 1" maxWidth="350px" />

## Wiring
### RS485
<RS485ConnectionTable firstColumn={["A", "B", "N/A"]} />
<ClickableImage src="/img/customers/janitza/umg103-cbm-wiring.png" alt="Image 1" maxWidth="350px" />


## Configuration
<RS485AddressNote />


# UMG 604 PRO


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/customers/janitza/logo.png"
    alt="logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>


## Supported Devices



<DeviceSupportTable
  devices={[
    { 
        type: 'Janitza UMG 604 PRO',
        modbusTcp: '✅',
        rs485: '✅',
      instructionVideos: [{"videoId": "ltN149q-xH0", "title": "Janitza UMG 604-PRO · RS485", "description": "Models: UMG 604-PRO 52.16.202."}]
    },
    { 
        type: 'Janitza UMG 605 PRO',
        modbusTcp: '✅',
        rs485: '✅',
    },
  ]}
  showModbusTcp={true}
  showRs485={true}
/>

<ClickableImage src="/img/customers/janitza/umg604-pro.png" alt="Image 1" maxWidth="350px" />

## Wiring
### Ethernet
For correct ethernet wiring: Follow the [the guidelines for ethernet wiring](/Controller/wiring-best-practices/#ethernet).

### RS485
<RS485ConnectionTable firstColumn={["A", "B", "N/A"]} />
<ClickableImage src="/img/customers/janitza/umg604-pro-wiring.png" alt="Image 1" maxWidth="350px" />


## Configuration
### Ethernet
View the images for more information on configuration.
<ClickableImage src="/img/customers/janitza/umg604-pro-config_pt1.png" alt="Image 1" maxWidth="350px" />
<ClickableImage src="/img/customers/janitza/umg604-pro-config_pt2.png" alt="Image 1" maxWidth="350px" />

### RS485
<RS485AddressNote />
Make sure the energy meter is set as a 'Modbus RTU/slave'!
<ClickableImage src="/img/customers/janitza/umg604-pro-config_pt3.png" alt="Image 1" maxWidth="350px" />

# UMG 96-PA


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/customers/janitza/logo.png"
    alt="logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>


## Supported Devices

<DeviceSupportTable
  devices={[
    { 
        type: 'Janitza UMG 96-PA',
        modbusTcp: '✅',
        rs485: '❌',
      instructionVideos: [{"videoId": "f2mqdLL1Mac", "title": "Janitza UMG 96-PA · Modbus TCP", "description": "UMG 96-PA 52.32.001 with Ethernet module 52.32.010; Modbus TCP."}]
    },
    { 
        type: 'Janitza UMG 96-PAMID',
        modbusTcp: '✅',
        rs485: '❌',
      instructionVideos: [{"videoId": "gBpOEqLGNfk", "title": "Janitza UMG 96-PA-MID+ · Modbus TCP", "description": "UMG 96-PA-MID+ 52.32.004 with Ethernet module 52.32.010; Modbus TCP."}]
    }
  ]}
  showModbusTcp={true}
  showRs485={true}
/>

<ClickableImage src="/img/customers/janitza/umg96-pa.png" alt="Janitza UMG 96-PA" maxWidth="350px" />

## Wiring


## Configuration


<RS485AddressNote />




# UMG 96 PQ L


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/customers/janitza/logo.png"
    alt="logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>


## Supported Devices


<DeviceSupportTable
  devices={[
    { 
        type: 'Janitza UMG 96 PQ L',
        modbusTcp: '❌',
        rs485: '✅',
      instructionVideos: [{"videoId": "4prTTwjKgbk", "title": "Janitza UMG 96-PQ-L · RS485", "description": "Models: UMG 96-PQ-L 52.36.001."}]
    }
  ]}
  showModbusTcp={true}
  showRs485={true}
/>

## Wiring
### RS485
<RS485ConnectionTable firstColumn={["RS485 A / Terminal 15", "RS485 B / Terminal 16", "RS485 C / Terminal 14"]} />
<ClickableImage src="/img/customers/janitza/umg96-pq-l-wiring.png" alt="Image 1" maxWidth="350px" />


## Configuration
<RS485AddressNote />

# UMG 96 RM


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/customers/janitza/logo.png"
    alt="logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>


## Supported Devices


<DeviceSupportTable
  devices={[
    { 
        type: 'Janitza UMG 96 RM',
        modbusTcp: '❌',
        rs485: '✅',
      instructionVideos: [{"videoId": "h8dM2GPbBHw", "title": "Janitza UMG 96RM · RS485", "description": "Models: Janitza UMG 96RM."}]
    },
    { 
        type: 'Janitza UMG 96 RM-P',
        modbusTcp: '❌',
        rs485: '✅',
      instructionVideos: [{"videoId": "jSE0fH270Jw", "title": "Janitza UMG 96RM-P · RS485", "description": "Models: Janitza UMG 96RM-P."}]
    },
    { 
        type: 'Janitza UMG 96 RM-CBM',
        modbusTcp: '❌',
        rs485: '✅',
      instructionVideos: [{"videoId": "pdHMS3bljro", "title": "Janitza UMG 96RM-CBM · RS485", "description": "Models: Janitza UMG 96RM-CBM."}]
    },
    { 
        type: 'Janitza UMG 96 RM-PN',
        modbusTcp: '✅',
        rs485: '✅',
    }
  ]}
  showModbusTcp={true}
  showRs485={true}
/>

<ClickableImage src="/img/customers/janitza/umg96-rm.png" alt="Image 1" maxWidth="350px" />

## Wiring
### Ethernet
For correct ethernet wiring: Follow the [the guidelines for ethernet wiring](/Controller/wiring-best-practices/#ethernet).

### RS485
<RS485ConnectionTable firstColumn={["A", "B", "N/A"]} />
<ClickableImage src="/img/customers/janitza/umg96-rm-wiring.png" alt="Image 1" maxWidth="350px" />


## Configuration
### Ethernet
See the device manual.

### RS485
<RS485AddressNote />
<ClickableImage src="/img/customers/janitza/umg96-rm-config_pt1.png" alt="Image 1" maxWidth="350px" />

# UMG 96 S2


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/customers/janitza/logo.png"
    alt="logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>


## Supported Devices


<DeviceSupportTable
  devices={[
    { 
        type: 'Janitza UMG 96 S2',
        modbusTcp: '✅',
        rs485: '✅',
      instructionVideos: [{"videoId": "Rxym6Er3Rag", "title": "Janitza UMG 96-S2 · RS485", "description": "Models: Janitza UMG 96-S2 5234002."}]
    }
  ]}
  showModbusTcp={true}
  showRs485={true}
/>

<ClickableImage src="/img/customers/janitza/umg96-s2.png" alt="Image 1" maxWidth="350px" />

## Wiring
### RS485
<RS485ConnectionTable firstColumn={["RS485 A / Terminal 14", "RS485 B / Terminal 15", "RS485 C / Terminal 13"]} />
<ClickableImage src="/img/customers/janitza/umg96-s2-wiring.png" alt="Image 1" maxWidth="350px" />


## Configuration
<RS485AddressNote />

# Joulz


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/sgo/Logo_Joulz.png"
    alt="Joulz"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

## Supported Devices


<DeviceSupportTable
  devices={[
    {
        type: 'Realtime Insights Converter',
        modbusTcp: '✅',
        rs485: '❌',
    }
  ]}
  showModbusTcp={true}
  showRs485={true}  
  />

# Kaifa


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/sgo/Logo_Kaifa.png"
    alt="Kaifa"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

## Supported Devices


<DeviceSupportTable
  devices={[
    { 
        type: 'DSMR Smart Meter',
        customCol: '✅',
    }
  ]}
    customColumns={{ "customCol": "P1 to USB" }}
    />

<ClickableImage src="/img/customers/kaifa/meter.jpg" alt="Image 1" maxWidth="450px" />

# Kamstrup


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/sgo/Logo_Kamstrup.png"
    alt="Kamstrup"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

## Supported Devices



<DeviceSupportTable
  devices={[
    { 
        type: 'DSMR Smart Meter',
        customCol: '✅',
    }
  ]}
    customColumns={{ "customCol": "P1 to USB" }}
    />

<ClickableImage src="/img/customers/kamstrup/meter.png" alt="Image 1" maxWidth="450px" />

# Landis+Gyr


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/sgo/Logo_LandisGyr.png"
    alt="Landis+Gyr"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

## Supported Devices


<DeviceSupportTable
  devices={[
    { 
        type: 'DSMR Smart Meter',
        customCol: '✅',
    }
  ]}
  customColumns={{ "customCol": "P1 to USB" }}/>

<ClickableImage src="/img/customers/landisgyr/meter.jpg" alt="Image 1" maxWidth="450px" />

# Legrand


import { BrandName, ControllerName } from "@site/src/components/customFields";
import RS485ConnectionTable from "@site/src/components/RS485ConnectionTable";
import ClickableImage from "@site/src/components/ClickableImage";
import RS485AddressNote from "@site/src/components/RS485AddressNote";
import DeviceSupportTable from "@site/src/components/DeviceSupportTable";

<img
  src="/img/customers/legrand/logo.png"
  alt="logo"
  style={{ display: "block", margin: "0 auto", width: "40%" }}
/>

## Supported Devices

<DeviceSupportTable
  devices={[
    {
      type: "Legrand EMDX3",
      modbusTcp: "❌",
      rs485: "✅",
      instructionVideos: [{"videoId": "foj9IWYkBV0", "title": "Legrand EMDX³ 412091 / 412093 · RS485", "description": "Use the exact model and connector version shown in this video."}]
    },
    {
      type: "Legrand Nemo-D4-EC MFD4ORFCDT",
      modbusTcp: "❌",
      rs485: "✅",
    },
  ]}
  showModbusTcp={true}
  showRs485={true}
/>

> [!IMPORTANT]
> For the LeGrand EMDX3 make sure that the protcol is set to BASIC!

<ClickableImage
  src="/img/customers/legrand/emdx3.png"
  alt="Image 1"
  maxWidth="350px"
/>

## Wiring

### RS485

<RS485ConnectionTable firstColumn={["RS485 +", "RS485 -", "RS485 SG"]} />

## Configuration

<RS485AddressNote />
<ClickableImage
  src="/img/customers/legrand/emdx3-config_pt1.png"
  alt="Image 1"
  maxWidth="550px"
/>


# Litiot


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/sgo/Logo_Litiot.png" 
    alt="Litiot"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

## Supported Devices

The **Litiot LHE34D** is a whitelabel version of the **Chint DTSU666 for Afore**. In the <BrandName /> configuration, this device uses the same communication protocol and driver settings as the Afore-compatible Chint meters.

<DeviceSupportTable
  devices={[
    { 
        type: 'LHE34D',
        variants: '3x230V/400V-5/80A',
        modbusTcp: '❌',
        rs485: '✅',
    }
  ]}
  showVariants={true}
  showModbusTcp={true}
  showRs485={true}/>

> [!NOTE]
> Because the **Litiot LHE34D** is hardware-identical to the **Chint DTSU666 for Afore**, all installation instructions, wiring diagrams, and terminal connections are the same.

## Connection & Wiring

For detailed instructions on how to connect the RS-485 communication bus, terminal pinouts, and wiring diagrams, please refer to the main Chint documentation page:

**[View Chint DTSU666 Wiring & Connection Instructions](/Controller/Devices/Energy-meter/Chint/)**

### Quick Reference
* **Protocol**: Modbus RTU (RS-485)
* **Terminal 24**: RS485-A
* **Terminal 25**: RS485-B

<RS485AddressNote />


# M-Bus


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import ClickableImage from '@site/src/components/ClickableImage';

<img
    src="/img/customers/mbus/mbus-logo.png"
    alt="M-Bus"
    style={{ display: "block", margin: "0 auto", width: "30%"}}
/>

## M-Bus (Meter-Bus)

This driver supports energy meters and other devices that comply with the **M-Bus (Meter-Bus)** standard (EN 13757-2 / EN 13757-3). The <ControllerName /> connects to these devices via an **M-Bus Master / Gateway** (also known as a level converter).

> [!NOTE] IMPORTANT
> This driver uses the **M-Bus** protocol. This is a **different** physical and electrical standard from Modbus (RS485) and requires an M-Bus Master / Gateway.

---

## Wiring

### M-Bus Wiring

M-Bus is a 2-wire bus system. Unlike RS485, it is typically **not sensitive to polarity** (the two wires can be swapped).

1.  **Connect the Meters:**
    * Connect all M-Bus devices in parallel using a 2-wire cable (daisy-chain topology).
    * Consult your meter's manual for the specific M-Bus connection terminals.

2.  **Connect the M-Bus Master:**
    * The M-Bus line must be connected to an **M-Bus Master** (also called a level converter or gateway). This device powers the bus and converts the M-Bus signal into a protocol the <ControllerName /> can read (usually Ethernet/IP).
    * Connect the M-Bus Master to the same network as your <ControllerName />.



---

## Configuration


To ensure the <ControllerName /> can find your M-Bus devices, each device must have a **unique Primary Address**.

* **Primary Address:**
    * Set a unique address for each meter on the same bus, **between 1 and 250**.
    * This is typically done via the meter's display menu.
    * Make a note of each device's address.

* **Baudrate:**
    * All devices on the same M-Bus bus *must* be set to the same baudrate (e.g., 2400, 9600).
    * The M-Bus Master / Gateway must also be set to this same baudrate. The default is often **2400**.



# Metcom


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/customers/metcom/logo.png"
    alt="logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>


## Supported Devices


<DeviceSupportTable
  devices={[
    { 
        type: 'Metcom MCS301',
        modbusTcp: '✅',
        rs485: '✅',
    },
    { 
        type: 'Metcom Blue2box',
        modbusTcp: '✅',
        rs485: '❌',
    }
  ]}
  showModbusTcp={true}
  showRs485={true} />

## Wiring
### Ethernet
For correct ethernet wiring: Follow the [the guidelines for ethernet wiring](/Controller/wiring-best-practices/#ethernet).

### RS485
<RS485ConnectionTable firstColumn={["A", "B", "N/A"]} />
<ClickableImage src="/img/customers/metcom/mcs301-wiring.png" alt="Image 1" maxWidth="350px" />


## Configuration
### Ethernet
View the manual for more information on configuration.
<ClickableImage src="/img/customers/metcom/mcs301-config_pt1.png" alt="Image 1" maxWidth="350px" />

### RS485
View the manual for more information. The energy meter uses the DLMS/COSEM broadcast protocol, so it should not be necessary to set an address.

# P1Api

import { BrandName, ControllerName } from '@site/src/components/customFields';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/sgo/Logo_CloudP1.png"
    alt="logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>


## Supported Devices

<DeviceSupportTable
  devices={[
    {
      type: "Energy Meter",
      api: '✅', 
      modbusTcp: '✅',
      rs485: '❌',
    },
  ]}
  showApi = {true}
  showModbusTcp ={true}
  showRs485 ={false}
/>

# Phoenix-Contact


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/customers/phoenix-contact/logo.png"
    alt="logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>


## Supported Devices

<DeviceSupportTable
  devices={[
    { 
        type: 'Phoenix-Contact EEM-MA370',
        modbusTcp: '✅',
        rs485: '❌',
    },
    { 
        type: 'Phoenix-Contact EEM-MA371',
        modbusTcp: '✅',
        rs485: '❌',
    },
    { 
        type: 'Phoenix-Contact EEM-EM375',
        modbusTcp: '✅',
        rs485: '❌',
      instructionVideos: [{"videoId": "lRMz-r7bdEU", "title": "Phoenix Contact EEM-EM375 · Ethernet", "description": "Models: Phoenix Contact EEM-EM375."}]
    },
    { 
        type: 'Phoenix-Contact EEM-EM377',
        modbusTcp: '✅',
        rs485: '❌',
      instructionVideos: [{"videoId": "6cnKoXbZHUo", "title": "Phoenix Contact EEM-EM377 · Ethernet", "description": "Models: Phoenix Contact EEM-EM377."}]
    }
  ]}
  showModbusTcp={true}
  showRs485={true}
/>

<ClickableImage src="/img/customers/phoenix-contact/eem-ma370.png" alt="Image 1" maxWidth="350px" />

## Wiring
For correct ethernet wiring: Follow the [the guidelines for ethernet wiring](/Controller/wiring-best-practices/#ethernet).

## Configuration

### EEM-MA370 / EEM-MA371

In the interface of the meter, set the Modbus settings as indicated in the screenshot.
- Modbus TCP should be enabled
- Compatibility mode should be disabled
<ClickableImage src="/img/customers/phoenix-contact/Phoenix_contact_modbus_settings.png" alt="Image 1" maxWidth="350px" />


View the device manual for more information on configuration.
<ClickableImage src="/img/customers/phoenix-contact/eem-ma370-config_pt1.png" alt="Image 1" maxWidth="350px" />

### EEM-EM375 / EEM-EM377

<ClickableImage src="/img/customers/phoenix-contact/eem-em375.jpg" alt="EEM-EM375" maxWidth="350px" />

The EEM-EM375 and EEM-EM377 are three-phase MID-certified energy meters with an Ethernet interface.
The EEM-EM375 measures through current transformers (1 A / 5 A secondary), the EEM-EM377 measures
directly (up to 80 A). The <ControllerName /> communicates with them over Modbus TCP on port 502.

- Configure the network settings (IP address / DHCP), and on the EEM-EM375 the current transformer
  ratio, through the meter's integrated web server.
- Make sure the meter is reachable from the <ControllerName /> over the local network.

The other meters of the EEM-EM/DM3xx family are not supported: the EEM-EM355, EEM-EM357,
EEM-DM357 and EEM-DM357-70 only have an RS-485 (Modbus RTU) interface, and the EEM-EM325 and
EEM-EM327 only have an M-Bus interface.

View the device manual for more information on configuration.


# Pilot


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/sgo/Logo_Pilot.png"
    alt="Pilot"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

## Supported Devices

<DeviceSupportTable
  devices={[
    { 
        type: 'Pilot SPM33',
        modbusTcp: '✅',
        rs485: '✅',
      instructionVideos: [{"videoId": "UgSpUluXpq4", "title": "Pilot SPM33 · legacy version · RS485", "description": "Legacy SPM33 housing with the green measurement terminal block."}]
    }
  ]}
  showModbusTcp={true}
  showRs485={true}
  />

## Wiring

### RS485

The RS485 terminals are located on the back of the device.

<RS485ConnectionTable firstColumn={["13 (A+)", "12 (B-)", "14 (Shield)"]} />

> [!NOTE] Power Supply
> Ensure the device is powered using terminals **1 (L/+)** and **3 (N/-)**. The auxiliary power supply range is AC 85-265V or DC 100-300V.

## Configuration

<RS485AddressNote />

Use the following Modbus settings in the <ControllerName />'s device wizard. These are the default settings for the meter:

* **Baudrate:** 9600
* **Modbus Address:** 1 (or the address set on the meter)
* **Parity:** None
* **Stop bits:** 1
* **Data bits:** 8

# Sagemcom


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/sgo/Logo_Sagemcom.png"
    alt="Sagemcom"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

## Supported Devices



<DeviceSupportTable
  devices={[
    { 
        type: 'DSMR Smart Meter',
        customCol: '✅',
    }
  ]}
  customColumns={{ "customCol": "P1 to USB" }}/>

<ClickableImage src="/img/customers/sagemcom/meter.jpg" alt="Image 1" maxWidth="450px" />

# ComPact NSX


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

# ComPact NSX

<img
    src="/img/customers/schneider-electric/logo.png"
    alt="Schneider Electric"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

The Schneider ComPact NSX is a circuit breaker that can also measure energy. To communicate with the <BrandName /> <ControllerName />, it must be equipped with a **MicroLogic 5, 6, or 7** trip unit.

## Supported Devices

We support the ComPact NSX range with Electronic Trip Units. Choose the driver that matches your device's Modbus profile.

<DeviceSupportTable
  devices={[
    { 
      type: 'ComPact NSXe ', 
      modbusTcp: '✅', 
      rs485: '✅',
      description: 'Standard profile using Floating Point registers (32xxx).',
      instructionVideos: [{"videoId": "VhXdmh6P7fA", "title": "IFM LV434000 + LV434211 · Modbus RS485", "description": "IFM LV434000 with the LV434211 RS485 connector. The video covers the external IFM interface; use the compatible breaker and trip unit specified on this page."}]
    },
    { 
      type: 'ComPact NSXs ', 
      modbusTcp: '✅', 
      rs485: '✅',
      description: 'Legacy profile using Integer registers (12xxx).',
      instructionVideos: [{"videoId": "VhXdmh6P7fA", "title": "IFM LV434000 + LV434211 · Modbus RS485", "description": "IFM LV434000 with the LV434211 RS485 connector. The video covers the external IFM interface; use the compatible breaker and trip unit specified on this page."}]
    }
  ]}
  showModbusTcp={true}
  showRs485={true}
/>

> [!CAUTION] Important: Check your Trip Unit
> This driver **only works** if your breaker has a **MicroLogic 5.x, 6.x, or 7.x** trip unit.
> * **Look for the LCD screen:** These units always have a digital display.
> * **Incompatible:** Basic thermal-magnetic units (TM-D/TM-G) or MicroLogic 2.x/4.x (dials only) **cannot** measure energy.

<ClickableImage src="/img/customers/schneider-electric/compactnsx.jpg" alt="Schneider ComPact NSX" maxWidth="450px" />

## Wiring

> [!CAUTION] You cannot wire directly to the breaker
> The ComPact NSX does not have built-in RS485 or Ethernet terminals. You **must** install an external Interface Module (Gateway) on the DIN rail next to the breaker.

### Step 1: The "NSX Cord"
Regardless of your communication method, you need the **NSX Cord**.
1.  Open the front cover of the breaker.
2.  Connect the **NSX Cord** to the test port on the MicroLogic Trip Unit.
3.  Route the cable out of the breaker to your DIN rail.

### Step 2: Choose your Interface Module

#### Option A: Modbus RTU (RS485)
**Required Part:** EcoStruxure **IFM** Module (Ref: LV434000)

1.  Snap the IFM module onto the DIN rail.
2.  Plug the **NSX Cord** into the bottom of the IFM module.
3.  Wire the **Top Connector** (green) to the <BrandName /> <ControllerName /> RS485 bus:

<RS485ConnectionTable firstColumn={["D1 (+)", "D0 (-)", "0V"]} />

<ClickableImage src="/img/customers/schneider-electric/ifm-module.jpg" alt="Schneider IFM Module (LV434000)" maxWidth="300px" />

#### Option B: Ethernet (Modbus TCP)
**Required Part:** EcoStruxure **IFE** Module (Ref: LV434001)

1.  Snap the IFE module onto the DIN rail.
2.  Plug the **NSX Cord** into the bottom of the IFE module.
3.  Connect a standard Ethernet cable (LAN) from the top RJ45 port to your network switch/router.

<ClickableImage src="/img/customers/schneider-electric/ife-module.jpg" alt="Schneider IFE Module (LV434001)" maxWidth="300px" />

## Configuration

### 1. Check the Trip Unit
Ensure the trip unit is powered (the **Ready LED** should be blinking green).

### 2. Configure Modbus RTU (IFM Module)
If you are using the **IFM (RS485)** module, use the rotary dials on the front to set the address.

1.  **Set the Address:** Turn the two blue dials to match your desired ID.
    * **x10** = The first digit (tens).
    * **x1** = The second digit (ones).
    * *Example:* For Address **15**, set **x10** to **1** and **x1** to **5**.
2.  **Lock It:** Slide the small switch down to the **Padlock** icon. This saves the address.
3.  **Communication Speed:** You do not need to set the Baud Rate. The module detects it automatically. Just ensure your controller is set to **19200 / Even / 1 Stop Bit**.
### 3. Configure Modbus TCP (IFE Module)
If using the **IFE (Ethernet)** module, you must configure it via a web browser:

1.  Connect your PC to the same network as the IFE.
2.  Find the IP address of the IFE (often DHCP by default, check your router's client list).
3.  Log in to the web interface.
4.  Navigate to **Settings** > **Modbus TCP/IP**.
5.  Set a **Static IP** (Recommended).
6.  Ensure the Port is **502**.

| Parameter | Value |
| :--- | :--- |
| **IP Address** | Select a free IP (e.g. 192.168.1.50) |
| **Subnet Mask** | 255.255.255.0 |
| **Gateway** | Your Router's IP (e.g. 192.168.1.1) |
| **Port** | 502 |

# IEM 2100 Series


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
  src="/img/customers/schneider-electric/logo.png"
  alt="logo"
  style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

## Supported Devices

The **IEM 2100 Series** are single-phase energy meters.

<DeviceSupportTable
  devices={[
    { 
        type: 'Schneider-Electric iEM 2100 Series',
        modbusTcp: '❌',
        rs485: '✅',
    },
    { 
        type: 'Schneider-Electric iEM 2150',
        modbusTcp: '❌',
        rs485: '✅',
    },
    { 
        type: 'Schneider-Electric iEM 2155',
        modbusTcp: '❌',
        rs485: '✅',
    }
  ]}
  showModbusTcp={true}
  showRs485={true}
/>


<ClickableImage src="/img/customers/schneider-electric/iem2150.png" alt="Schneider iEM 2150" maxWidth="350px" />

## Wiring

The IEM 2100 series communicates via **Modbus RTU** over RS485. 

<RS485ConnectionTable firstColumn={["D1 (+)", "D0 (-)", "0V / Shield"]} />

Please refer to the device manual for the exact pin locations, as they may vary slightly between specific sub-models (e.g., iEM2150 vs iEM2155).


## Configuration

<RS485AddressNote />

### Communication Settings
Ensure the device settings match the driver capabilities defined below:

* **Baud Rate:** 9600, 19200, or 38400 (Default is often 19200)
* **Parity:** Even, Odd, or None
* **Stop Bits:** 1
* **Data Bits:** 8

Check the device manual on how to enter the energy meter's configuration menu to set the Modbus Address and Baud Rate.




# IEM 2100 Series


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
  src="/img/customers/schneider-electric/logo.png"
  alt="logo"
  style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

## Supported Devices

The **IEM 2100 Series** are single-phase energy meters.

<DeviceSupportTable
  devices={[
    { 
        type: 'Schneider-Electric iEM 2100 Series',
        modbusTcp: '❌',
        rs485: '✅',
    },
    { 
        type: 'Schneider-Electric iEM 2150',
        modbusTcp: '❌',
        rs485: '✅',
    },
    { 
        type: 'Schneider-Electric iEM 2155',
        modbusTcp: '❌',
        rs485: '✅',
    }
  ]}
  showModbusTcp={true}
  showRs485={true}
/>


<ClickableImage src="/img/customers/schneider-electric/iem2150.png" alt="Schneider iEM 2150" maxWidth="350px" />

## Wiring

The IEM 2100 series communicates via **Modbus RTU** over RS485. 

<RS485ConnectionTable firstColumn={["D1 (+)", "D0 (-)", "0V / Shield"]} />

Please refer to the device manual for the exact pin locations, as they may vary slightly between specific sub-models (e.g., iEM2150 vs iEM2155).


## Configuration

<RS485AddressNote />

### Communication Settings
Ensure the device settings match the driver capabilities defined below:

* **Baud Rate:** 9600, 19200, or 38400 (Default is often 19200)
* **Parity:** Even, Odd, or None
* **Stop Bits:** 1
* **Data Bits:** 8

Check the device manual on how to enter the energy meter's configuration menu to set the Modbus Address and Baud Rate.




# IEM 3000 Series


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/customers/schneider-electric/logo.png"
    alt="logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>


## Supported Devices



<DeviceSupportTable
  devices={[
    { 
        type: 'Schneider-Electric IEM 3150',
        modbusTcp: '❌',
        rs485: '✅',
    },
    { 
        type: 'Schneider-Electric IEM 3155',
        modbusTcp: '❌',
        rs485: '✅',
    },
    { 
        type: 'Schneider-Electric IEM 3250',
        modbusTcp: '❌',
        rs485: '✅',
    },
    { 
        type: 'Schneider-Electric IEM 3255',
        modbusTcp: '❌',
        rs485: '✅',
    },
    { 
        type: 'Schneider-Electric IEM 3350',
        modbusTcp: '❌',
        rs485: '✅',
    },
    { 
        type: 'Schneider-Electric IEM 3355',
        modbusTcp: '❌',
        rs485: '✅',
    },
    { 
        type: 'Schneider-Electric IEM 3455',
        modbusTcp: '❌',
        rs485: '✅',
    },
    { 
        type: 'Schneider-Electric IEM 3555',
        modbusTcp: '❌',
        rs485: '✅',
    }
  ]}
  showModbusTcp={true}
  showRs485={true}
/>


> [!WARNING]
> Not all Schneider-Electric IEM 3000 series energy meters register exported energy! Check with the energy meter manufacturer if in doubt.
> At least IEM 3150, IEM 3250 and IEM 3350 do not allow reading out exported energy.

<ClickableImage src="/img/customers/schneider-electric/iem3250.png" alt="Image 1" maxWidth="350px" />

## Wiring
<RS485ConnectionTable firstColumn={["D1", "D0", "0V"]} />
<ClickableImage src="/img/customers/schneider-electric/iem3250-wiring.png" alt="Image 1" maxWidth="450px" />


## Configuration
<RS485AddressNote />

Check the device manual on how to enter the energy meter's configuration menu.
<ClickableImage src="/img/customers/schneider-electric/iem3250-config_pt1.png" alt="Image 1" maxWidth="550px" />
<ClickableImage src="/img/customers/schneider-electric/iem3250-config_pt2.png" alt="Image 1" maxWidth="250px" />

# Schneider


import { FolderOverview } from '@/components/FolderOverview';

# Schneider

<FolderOverview folder="Controller/Devices/Energy-meter/Schneider" />


# MasterPact MTZ


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';
import RS485AddressNote from '@site/src/components/RS485AddressNote';

# MasterPact MTZ

<img
    src="/img/customers/schneider-electric/logo.png"
    alt="Schneider Electric"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

The MasterPact MTZ is a high-power air circuit breaker equipped with the **MicroLogic X** control unit. It provides advanced energy monitoring and protection.

## Supported Devices

The driver supports the MasterPact MTZ range (MTZ1, MTZ2, MTZ3) when communicating via Modbus RTU.

<DeviceSupportTable
  devices={[
    { 
      type: 'MasterPact MTZ (MicroLogic X)', 
      modbusTcp: '❌', 
      rs485: '✅',
      description: 'Communicates via the ULP system using an IFM Interface.',
      instructionVideos: [{"videoId": "VhXdmh6P7fA", "title": "IFM LV434000 + LV434211 · Modbus RS485", "description": "IFM LV434000 with the LV434211 RS485 connector. The video covers the external IFM interface; use the compatible breaker and trip unit specified on this page."}]
    }
  ]}
  showModbusTcp={true}
  showRs485={true}
/>

> [!CAUTION] Important: MicroLogic X Required
> This driver interacts with the **MicroLogic X** control unit. Ensure your breaker is powered and the control unit is active (The "Ready" LED should be blinking green).

## Wiring

> [!CAUTION] Interface Module Required
> The MasterPact MTZ communicates using the internal ULP protocol. It does **not** have direct RS485 screw terminals on the breaker itself. 
>
> To connect it to the <BrandName /> <ControllerName /> via RS485, you **must** use the **EcoStruxure IFM Interface** (Ref: LV434000).

### Step 1: Connect the ULP Cord
1. Locate the **ULP Port** on the MasterPact MTZ (usually located on the front or connection area of the chassis).
2. Connect a ULP cord (RJ45) from the breaker to the bottom of the **IFM Module**.

### Step 2: Connect RS485 to the IFM Module
1. Snap the **IFM Module** (LV434000) onto the DIN rail.
2. Wire the **Top Connector** (green 5-pin connector) to the <BrandName /> <ControllerName /> RS485 bus.

<RS485ConnectionTable firstColumn={["D1 (+)", "D0 (-)", "0V / Common"]} />

<ClickableImage src="/img/customers/schneider-electric/ifm-module.jpg" alt="Schneider IFM Module (LV434000)" maxWidth="300px" />
*ifm module*
## Configuration

The configuration is handled physically on the **IFM Module**, not on the breaker's screen.

### 1. Set Modbus Address
Use the two rotary dials on the front of the IFM module to set the Modbus address (1 to 99).

* **Tens Dial (x10):** Sets the first digit.
* **Ones Dial (x1):** Sets the second digit.
* **Lock:** Slide the switch to the **Padlock** position to save the address.

<RS485AddressNote />

### 2. Communication Settings
The IFM module automatically detects the baud rate and parity. However, ensure your <BrandName /> <ControllerName /> and the IFM are aligned.

Recommended settings for the **IFM**:
* **Baud Rate:** 19200
* **Parity:** Even
* **Stop Bits:** 1

### 3. Validating the Connection
The driver performs a validation check upon connection. It verifies:
1.  **Frequency:** Must be within 50Hz or 60Hz ranges.
2.  **Voltage:** Must be within standard grid voltage ranges (e.g., 230V, 400V, 690V).

> [!TIP] Troubleshooting
> If the driver fails to load, check the voltage readings on the MicroLogic X display. If the breaker sees 0V (is not connected to a live busbar) and is not powered by an external 24V supply, the communication might fail or be rejected by the driver's validation logic.


# PM 3250


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/customers/schneider-electric/logo.png"
    alt="logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>


## Supported Devices


<DeviceSupportTable
  devices={[
    { 
        type: 'Schneider-Electric PM 3250',
        modbusTcp: '❌',
        rs485: '✅',
    }
  ]}
  showModbusTcp={true}
  showRs485={true}
  />


<ClickableImage src="/img/customers/schneider-electric/pm3250.png" alt="Image 1" maxWidth="350px" />

## Wiring
<RS485ConnectionTable firstColumn={["D1/+", "D0/-", "0V"]} />
<ClickableImage src="/img/customers/schneider-electric/pm3250-wiring.png" alt="Image 1" maxWidth="450px" />


## Configuration
<RS485AddressNote />

Check the device manual on how to enter the energy meter's configuration menu.
<ClickableImage src="/img/customers/schneider-electric/pm3250-config_pt1.png" alt="Image 1" maxWidth="550px" />
<ClickableImage src="/img/customers/schneider-electric/pm3250-config_pt2.png" alt="Image 1" maxWidth="250px" />

# PM 5000 Series


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/customers/schneider-electric/logo.png"
    alt="logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>


## Supported Devices

The PM 5000 series covers a wide range of meters. Capabilities vary by specific model number (e.g., PM51xx are generally RS485 only, while PM5320/PM5340 include Ethernet).

<DeviceSupportTable
  devices={[
    { 
        type: 'Schneider-Electric PM 5100 / 5110 / 5111',
        modbusTcp: '❌',
        rs485: '✅',
      instructionVideos: [{"videoId": "V2ul4ppmHrA", "title": "Schneider PM5110 / PM5111 · RS485", "description": "Use the exact model and connector version shown in this video."}]
    },
    { 
        type: 'Schneider-Electric PM 5310 / 5330 / 5331',
        modbusTcp: '❌',
        rs485: '✅',
      instructionVideos: [{"videoId": "RQKqUhMZk4Q", "title": "Schneider PM5310 · RS485", "description": "Models: Schneider PM5310."}, {"videoId": "9Y7nHqpzDOQ", "title": "Schneider PM5330 / PM5331 · RS485", "description": "Models: Schneider PM5330, Schneider PM5331."}]
    },
    { 
        type: 'Schneider-Electric PM 5320 / 5340 / 5341',
        modbusTcp: '✅',
        rs485: '✅',
    }
  ]}
  showModbusTcp={true}
  showRs485={true}
  />

<ClickableImage src="/img/customers/schneider-electric/pm5300.png" alt="Schneider PM5000 Series" maxWidth="350px" />
*pm5300*

## Wiring

### Ethernet
**Applicable only to PM5320, PM5340, and PM5341.**
For correct ethernet wiring: Follow the [guidelines for ethernet wiring](/Controller/wiring-best-practices/#ethernet).

### RS485
The RS485 terminals are located on the bottom of the device (connector 6 in the diagram below).

<RS485ConnectionTable firstColumn={["Terminal 22 / D1 (+)", "Terminal 23 / D0 (-)", "Terminal 25 / 0V"]} />

> [!NOTE]
> **Shielding:** The shield wire should be connected to **Terminal 24 (SHLD)**. Note that the ground terminal is not available on the meter itself; the shield should be connected to ground at the other end of the bus[cite: 246, 1627].

<ClickableImage src="/img/customers/schneider-electric/pm5000-wiring.png" alt="PM5000 RS485 Wiring Diagram" maxWidth="450px" />


## Configuration

### Ethernet
**Applicable only to PM5320, PM5340, and PM5341.**
To configure the IP address:
1. Navigate to **Maint > Setup > Comm > Enet**.
2. Configure the IP Address, Subnet Mask, and Gateway.
3. Ensure the Modbus TCP protocol is enabled (usually Port 502).

### RS485
<RS485AddressNote />

To configure the Serial settings (Baud rate, Parity, ID):
1. Navigate to **Maint > Setup > Comm > Ser**.
2. Edit the **Address** (Unit ID), **Baud** rate, and **Parity** to match your gateway settings. 

<ClickableImage src="/img/customers/schneider-electric/pm5000-menu.png" alt="PM5000 Menu Navigation" maxWidth="500px" />

# PM 800 Series


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';


<img
    src="/img/customers/schneider-electric/logo.png"
    alt="logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>


## Supported Devices


<DeviceSupportTable
  devices={[
    { 
        type: 'Schneider-Electric PM 820',
        modbusTcp: '❌',
        rs485: '✅',
      instructionVideos: [{"videoId": "31fLshB06Xc", "title": "Schneider PM820 / PM850 / PM870 · COM1", "description": "Models: PM820MG, PM850MG, PM870MG."}]
    },
    { 
        type: 'Schneider-Electric PM 850',
        modbusTcp: '❌',
        rs485: '✅',
      instructionVideos: [{"videoId": "31fLshB06Xc", "title": "Schneider PM820 / PM850 / PM870 · COM1", "description": "Models: PM820MG, PM850MG, PM870MG."}]
    },
    { 
        type: 'Schneider-Electric PM 870',
        modbusTcp: '❌',
        rs485: '✅',
      instructionVideos: [{"videoId": "31fLshB06Xc", "title": "Schneider PM820 / PM850 / PM870 · COM1", "description": "Models: PM820MG, PM850MG, PM870MG."}]
    }
  ]}
  showModbusTcp={true}
  showRs485={true}
/>


<ClickableImage src="/img/customers/schneider-electric/pm800.png" alt="Image 1" maxWidth="350px" />

## Wiring
<RS485ConnectionTable firstColumn={["D1/+", "D0/-", "0V"]} />
<ClickableImage src="/img/customers/schneider-electric/pm800-wiring.png" alt="Image 1" maxWidth="450px" />


## Configuration
<RS485AddressNote />

Check the device manual on how to enter the energy meter's configuration menu.
<ClickableImage src="/img/customers/schneider-electric/pm800-config_pt1.png" alt="Image 1" maxWidth="500px" />
<ClickableImage src="/img/customers/schneider-electric/pm800-config_pt2.png" alt="Image 1" maxWidth="500px" />

# PM 8000


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/customers/schneider-electric/logo.png"
    alt="logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>


## Supported Devices


<DeviceSupportTable
  devices={[
    { 
        type: 'Schneider-Electric PM 8000',
        modbusTcp: '✅',
        rs485: '✅',
      instructionVideos: [{"videoId": "2UHQ-G5TmNQ", "title": "Schneider PM8240 · COM1 RS485", "description": "Models: METSEPM8240."}, {"videoId": "JKSZiHwIvZk", "title": "Schneider PM8244 + PM89RD96 · COM1 RS485", "description": "Models: METSEPM8244 (PM8243 + PM89RD96)."}]
    }
  ]}
  showModbusTcp={true}
  showRs485={true}
  />

<ClickableImage src="/img/customers/schneider-electric/PM8000.png" alt="Schneider Electric PM8000 energy meter" maxWidth="350px" />

## Wiring
### Ethernet
For correct ethernet wiring: Follow the [the guidelines for ethernet wiring](/Controller/wiring-best-practices/#ethernet).

### RS485
<RS485ConnectionTable firstColumn={["Terminal 22 / +", "Terminal 23 / -", "Terminal 25 / C"]} />
<ClickableImage src="/img/customers/schneider-electric/pm8000-wiring.png" alt="Image 1" maxWidth="450px" />


## Configuration
### Ethernet
See the device manual.

### RS485
<RS485AddressNote />
Check the device manual on how to change the Modbus address.


# PowerTag Energy


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/customers/schneider-electric/logo.png"
    alt="logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>


## Supported Devices

The PowerTag Energy sensors are wireless energy sensors designed to be mounted directly on circuit breakers. They communicate wirelessly to a concentrator/gateway, which in turn communicates via Modbus TCP.

<DeviceSupportTable
  devices={[
    { 
        type: 'Schneider-Electric PowerTag Energy (R9M Series)',
        modbusTcp: '✅',
        rs485: '❌',
    }
  ]}
  showModbusTcp={true}
  showRs485={true}
/>

> [!NOTE]
> **Gateway Required:** The PowerTag sensors are wireless devices. To communicate with the <ControllerName />, they must be paired with a compatible Modbus TCP gateway (e.g., Acti9 Smartlink SI D, Wiser Gateway, or PowerTag Link).

<ClickableImage src="/img/customers/schneider-electric/powertag.jpg" alt="Schneider PowerTag" maxWidth="350px" />


## Wiring

### Voltage Connection
The PowerTag is mounted directly onto the circuit breaker. The voltage measurement cables must be connected to the terminals of the breaker or the load.

1.  **Mounting:** Clip the PowerTag to the top or bottom of the circuit breaker (depending on the model and space available).
2.  **Voltage Taps:** Connect the voltage measurement wires (Phase and Neutral) to the appropriate terminals on the breaker.


### Communication Wiring (Ethernet)
For correct ethernet wiring of the Gateway: Follow the [guidelines for ethernet wiring](/Controller/wiring-best-practices/#ethernet).


## Configuration

### Gateway Configuration
1.  **Pairing:** The PowerTag must be paired with the Gateway using the specific commissioning software or App provided by Schneider Electric (e.g., EcoStruxure Power Commission or Wiser App).
2.  **Network:** Assign a static IP address to the Gateway to ensure stable communication with the <ControllerName />.


* **IP Address:** Enter the IP address of the Gateway.
* **Slave Address (Unit ID):** This corresponds to the specific address assigned to the PowerTag within the Gateway. Check your Gateway's configuration to determine the Modbus Slave ID (Address) for the specific PowerTag you wish to read.

> [!NOTE]
> The driver scans for devices based on the Modbus Address. Ensure the "maxBusAddress" parameter covers the range of addresses assigned to your PowerTags in the gateway.

# Self configured energy meter

import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import { BrandName, ControllerName } from '@site/src/components/customFields';
import Details from '@theme/Details';


## Self-configured energy meter (*\*special support terms apply*)
When your energy meter has configurable modbus addresses (or when your energy meter is not in the list of supported devices)
, we supply a feature to configure an energy meter yourself.
It's a process that allows you to set up the energy meter as a modbus slave, enabling it to communicate with the <BrandName /> <ControllerName />.

> [!CAUTION] WARNING: Special support terms apply:
> *Please note that this feature is provided “as-is” and should be used at your own risk.
> If you run into any issues or need dedicated assistance, we’re happy to help under a support contract.
> Contact sales@smartgridone.com for pricing and availability.

### Step 1
Connect the meter to the <BrandName /> <ControllerName /> using RS485 or Modbus TCP.
- **For Modbus-TCP ethernet**: Please follow [the guidelines for ethernet wiring](/Controller/wiring-best-practices/#ethernet).
For correct ethernet wiring:
- **For RS485**: Please follow [the guidelines for RS485 wiring](/Controller/wiring-best-practices/#rs485)

Also, check your meter's manual for the correct wiring and connection details and **check if any settings need to be
changed to enable the modbus communication**.

### Step 2
Collect the following information from your energy meter:
- **Modbus address**: The address of the energy meter on the RS485 bus.
- **Baud rate**: The communication speed of the energy meter (e.g., 9600, 19200, etc.).
- **Parity**: The parity setting of the energy meter (e.g., None, Even, Odd).
- **Register information**: For each measurement you want to read, you'll need:
  - Register address (in decimal)
  - Data type (e.g., int16, uint32, float32)
  - Word order (if applicable for multi-register values)
  - Any scaling factor or offset needed
  - The type of measurement (e.g., voltage, current, power)

### Step 3
Open the <BrandName /> <ControllerName /> web interface and navigate to the energy meter configuration section.
Then, find the "Generic" driver:
<img
    src="/img/generic/generic.png"
    alt="Driver selection"
    style={{ display: "block", margin: "0 auto", width: "60%"}}
/>

Select the interface you'd like to use (RS485 or Modbus TCP).

### Step 4:
You'll need to provide a JSON configuration that defines which registers to read and how to interpret them. The configuration follows this structure:

```json
[
  {
    "dataType": "float32",
    "address": 3000,
    "wordOrder": "bigEndian",
    "scaleFactor": 1,
    "measurement": "actualPowerTot_W"
  },
  {
    "dataType": "uint32",
    "address": 3002,
    "wordOrder": "bigEndian",
    "scaleFactor": 0.1,
    "measurement": "importedAbsEnergyTot_Wh"
  }
]
```

Each register configuration requires:
- `dataType`: The type of data stored in the register (e.g., "int16", "uint32", "float32")
- `address`: The Modbus register address in decimal
- `measurement`: The standardized measurement name (e.g., "actualPowerTot_W", "importedAbsEnergyTot_Wh")

Optional fields include:
- `wordOrder`: How multi-register values are ordered ("bigEndian", "littleEndian", "middleEndian", "reverseWord")
- `scaleFactor`: Value to multiply the raw register value by (default: 1)
- `offset`: Value to add after scaling (default: 0)
- `bytePosition`: Position within a byte array (if applicable)
- `enumMapping`: For enum types, maps values to strings
- `length`: For arrays or byte fields, number of items
- `signed`: For numeric types, whether the value is signed

We strongly recommend including at least:
- Total Power (`actualPowerTot_W`)
- Total Imported Energy (`importedAbsEnergyTot_Wh`)
- Total Exported Energy (`exportedAbsEnergyTot_Wh`) if bi-directional

Enter the code in this place:
<img
    src="/img/generic/generic2.png"
    alt="Driver selection"
    style={{ display: "block", margin: "0 auto", width: "80%"}}
/>


<Details summary='I see an error'>
The input is strictly validated, and will not accept any mistakes:
<img
    src="/img/generic/generic3.png"
    alt="Driver selection"
    style={{ display: "block", margin: "0 auto", width: "80%"}}
/>
The example above is not accepted because the user choose `total power` instead of `actualPowerTot_W`.
The following measurements are accepted:
```
actualPowerL1_W
actualPowerL2_W
actualPowerL3_W
actualPowerTot_W
reacPowerL1_VAr
reacPowerL2_VAr
reacPowerL3_VAr
reacPowerTot_VAr
importedAbsEnergyL1_Wh
importedAbsEnergyL2_Wh
importedAbsEnergyL3_Wh
importedAbsEnergyTot_Wh
importedEnergyTodayTot_Wh
importedAbsReacEnergyL1_VArh
importedAbsReacEnergyL2_VArh
importedAbsReacEnergyL3_VArh
importedAbsReacEnergyTot_VArh
importedEnergyDeltaTot_Wh
grossImportedEnergyDeltaTot_Wh
importedReacEnergyDeltaL1_VArh
importedReacEnergyDeltaL2_VArh
importedReacEnergyDeltaL3_VArh
importedReacEnergyDeltaTot_VArh
exportedAbsEnergyL1_Wh
exportedAbsEnergyL2_Wh
exportedAbsEnergyL3_Wh
exportedAbsEnergyTot_Wh
exportedEnergyTodayTot_Wh
exportedAbsReacEnergyL1_VArh
exportedAbsReacEnergyL2_VArh
exportedAbsReacEnergyL3_VArh
exportedAbsReacEnergyTot_VArh
exportedEnergyDeltaL1_Wh
exportedEnergyDeltaL2_Wh
exportedEnergyDeltaL3_Wh
exportedEnergyDeltaTot_Wh
grossExportedEnergyDeltaTot_Wh
exportedReacEnergyDeltaL1_VArh
exportedReacEnergyDeltaL2_VArh
exportedReacEnergyDeltaL3_VArh
exportedReacEnergyDeltaTot_VArh
producedAbsEnergyL1_Wh
producedAbsEnergyL2_Wh
producedAbsEnergyL3_Wh
producedAbsEnergyTot_Wh
producedAbsReacEnergyTot_VArh
consumedAbsEnergyL1_Wh
consumedAbsEnergyL2_Wh
consumedAbsEnergyL3_Wh
consumedAbsEnergyTot_Wh
consumedEnergyTodayTot_Wh
consumedAbsReacEnergyTot_VArh
producedEnergyDeltaTot_Wh
consumedEnergyDeltaTot_Wh
producedEnergyTodayTot_Wh
chargedAbsEnergyTot_Wh
chargedEnergyTodayTot_Wh
chargedEnergyDeltaTot_Wh
dischargedAbsEnergyTot_Wh
dischargedEnergyTodayTot_Wh
dischargedEnergyDeltaTot_Wh
childrenProducedEnergyDeltaTot_Wh
childrenConsumedEnergyDeltaTot_Wh
childrenLoadsPower_W
childrenLoadsImpEnergyDeltaTot_Wh
childrenLoadsExpEnergyDeltaTot_Wh
childrenOtherPower_W
childrenOtherImpEnergyDeltaTot_Wh
childrenOtherExpEnergyDeltaTot_Wh
childrenUnmeasPower_W
childrenUnmeasImpEnergyDeltaTot_Wh
childrenUnmeasExpEnergyDeltaTot_Wh
childrenProducedPower_W
childrenConsumedPower_W
childrenStoragePower_W
childrenEVPower_W
childrenHVACPower_W
autoconsumedEnergyDeltaTot_Wh
producedExpEnergyDeltaTot_Wh
childrenStorageChargedEnergyDeltaTot_Wh
childrenStorageDischargedEnergyDeltaTot_Wh
childrenStorageSolarChargeEnergyDeltaTot_Wh
childrenStorageGridChargeEnergyDeltaTot_Wh
childrenStorageSolarDischargeEnergyDeltaTot_Wh
childrenStorageGridDischargeEnergyDeltaTot_Wh
childrenEVChargeEnergyDeltaTot_Wh
childrenHVACEnergyDeltaTot_Wh
currentL1_A
currentL2_A
currentL3_A
currentN_A
currentLAvg_A
voltageL1N_V
voltageL2N_V
voltageL3N_V
voltageLNAvg_V
voltageL1L2_V
voltageL2L3_V
voltageL3L1_V
voltageLLAvg_V
frequency_Hz
powerFactorTot
powerFactorL1
powerFactorL2
powerFactorL3
voltageDCBus_V
voltageInput1_V
currentInput1_A
powerInput1_W
voltageInput2_V
currentInput2_A
powerInput2_W
voltageInput3_V
currentInput3_A
powerInput3_W
voltageInput4_V
currentInput4_A
powerInput4_W
voltageInput5_V
currentInput5_A
powerInput5_W
voltageInput6_V
currentInput6_A
powerInput6_W
voltageInput7_V
currentInput7_A
powerInput7_W
voltageInput8_V
currentInput8_A
powerInput8_W
voltageInput9_V
currentInput9_A
powerInput9_W
voltageInput10_V
currentInput10_A
powerInput10_W
voltageDC_V
currentDC_A
voltageInputA_V
currentInputA_A
powerInputA_W
voltageInputA1_V
currentInputA1_A
powerInputA1_W
voltageInputA2_V
currentInputA2_A
powerInputA2_W
voltageInputA3_V
currentInputA3_A
powerInputA3_W
voltageInputA4_V
currentInputA4_A
powerInputA4_W
voltageInputA5_V
currentInputA5_A
powerInputA5_W
voltageInputA6_V
currentInputA6_A
powerInputA6_W
voltageInputB_V
currentInputB_A
powerInputB_W
voltageInputB1_V
currentInputB1_A
powerInputB1_W
voltageInputB2_V
currentInputB2_A
powerInputB2_W
voltageInputB3_V
currentInputB3_A
powerInputB3_W
voltageInputB4_V
currentInputB4_A
powerInputB4_W
voltageInputB5_V
currentInputB5_A
powerInputB5_W
voltageInputB6_V
currentInputB6_A
powerInputB6_W
currentInputTot_A
voltageInputAvg_V
powerInputTot_W
cabinetTemp_degC
ambientTemp_degC
heatSinkTemp_degC
isolationResistance_kOhm
runTimeTot_s
status
statusMsg
workingMode
operationMode
heatingAbsEnergy_Wh
heatingAbsVolume_m3
flowRate_m3ph
thermalPower_W
departureLineTemp_degC
returnLineTemp_degC
chargedAbsSessionEnergyTot_Wh
sessionDuration_s
chargingSessionId
evNumOfPhases
evUsedPhases
evTargetACChargeCurrent_A
evRequiringCharge
remainingEnergy_Wh
batteryVoltage_V
batteryCurrent_A
batteryPower_W
batteryTemp_degC
batteryOperationMode
PVOperationMode
gridOperationMode
current_A
consumedEnergy_Ah
stateOfCharge_frac
powerSetpoint_W
minStateOfCharge_frac
stateOfHealth_frac
storedEnergy_Wh
absVolume_m3
volumeDelta_m3
flow_m3ps
absPulseCount
pulseCountDelta
pulseRate_ph
flow1_m3ps
flow2_m3ps
flow3_m3ps
flow4_m3ps
flow5_m3ps
flow6_m3ps
flow7_m3ps
flow8_m3ps
flow9_m3ps
flow1_Lps
flow2_Lps
flow3_Lps
flow4_Lps
flow5_Lps
flow6_Lps
flow7_Lps
flow8_Lps
flow9_Lps
```

</Details>


### Step 5
After filling in the required information, save the configuration.
The <BrandName /> <ControllerName /> will now attempt to communicate with the energy meter using the provided settings.

> [!TIP]
> For better organization, you can create your JSON configuration in a text editor first, then paste it into the configuration field. This makes it easier to edit and validate the structure before applying it.

# Seneca S604


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/customers/seneca/logo.png"
    alt="logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>


## Supported Devices


<DeviceSupportTable
  devices={[
    { 
        type: 'Seneca S604 Ethernet models',
        modbusTcp: '✅',
        rs485: '❌',
    }
  ]}
    showModbusTcp={true}
    showRs485={true}
    />

{/* TODO: Check if our protocols also support the RS485 models */}

<ClickableImage src="/img/customers/seneca/s604.png" alt="Image 1" maxWidth="350px" />

## Wiring
### Ethernet
For correct ethernet wiring: Follow the [the guidelines for ethernet wiring](/Controller/wiring-best-practices/#ethernet).

## Configuration
### Ethernet
Check the device manual for connecting the energy meter to ethernet.
<ClickableImage src="/img/customers/seneca/s604-config_pt1.png" alt="Image 1" maxWidth="450px" />

# Sessy


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/customers/sessy/sessy.png"
    alt="Sessy"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

## Supported Devices



<DeviceSupportTable
  devices={[
    { 
        type: 'Energy Meter',
        modbusTcp: '✅',
        rs485: '❌',
    }
  ]}
  customColumns={{ "customCol": "P1 to USB" }}/>

You'll need to input your Sessy P1 dongle username and password when connecting your energy meter.


# Shelly Energy meters


import { BrandName, ControllerName } from '@site/src/components/customFields';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img alt="logo" src="/img/customers/shelly/shelly_logo_blue.png" />

## Supported Devices

Shelly offers two kinds of metering hardware, each with its own protocol in the <ControllerName />.

### Dedicated energy meters

Meters with CT clamps that measure a whole circuit. Select the **Shelly Energy Meter API protocol**.

<DeviceSupportTable
  devices={[
  {
    type: "Shelly Pro 3 EM (400)",
    localApi: '✅',
    instructionVideos: [{"videoId": "wQXIp2pw_IA", "title": "Shelly Pro 3EM SPEM-003CEBEU · 120 A CT · Ethernet", "description": "Shelly Pro 3EM SPEM-003CEBEU, 120 A CT version; local API over Ethernet."}]
  },
  {
    type: "Shelly 3EM",
    localApi: '✅',
  },
]}
  showLocalApi={true}
  showRs485={false}
/>

### Relays with power metering (PM)

Switches with a built-in power meter, which measure the load wired to their relay output. Select the
**Shelly Energy Meter via Switch (relay) component** protocol: it only reads the metering values and
never switches the relay. Use the [Shelly relay](/Devices/Switched-loads/ShellyRelay/) integration
instead when the <ControllerName /> must be able to switch the load on and off.

<DeviceSupportTable
  devices={[
  {
    type: "Shelly Plus 1PM",
    localApi: '✅',
  },
  {
    type: "Shelly Plus 2PM",
    localApi: '✅',
  },
  {
    type: "Shelly Pro 1PM",
    localApi: '✅',
  },
  {
    type: "Shelly Pro 2PM",
    localApi: '✅',
  },
  {
    type: "Shelly Pro 4PM",
    localApi: '✅',
  },
  {
    type: "Shelly Plus Plug S",
    localApi: '✅',
  },
  {
    type: "Shelly 1PM Gen3",
    localApi: '✅',
  },
  {
    type: "Shelly 1PM Mini Gen3",
    localApi: '✅',
  },
  {
    type: "Shelly 2PM Gen3",
    localApi: '✅',
  },
]}
  showLocalApi={true}
  showRs485={false}
/>

> [!NOTE]
>   Every switch with power metering is added as a separate meter, so a Shelly Pro 4PM results in four meters.

> [!NOTE]
>   This integration has not been tested with all the devices listed above, however, since they all use the same communication protocol, they should work without issues.

## Wiring

The communication between the <ControllerName /> and the Shelly relay is established via **Local API** (over TCP/IP).
For proper Ethernet wiring, please follow the [Ethernet wiring guidelines](/Controller/wiring-best-practices/#ethernet).

## Wiring Instructions

1. **Power Supply Connections**
   <ClickableImage src="/img/customers/shelly/shelly-blue.png" alt="Power Connections" maxWidth="450px" />
   * **L (Live)**: Connect the live wire to the **L** terminal of the device.
   * **N (Neutral)**: Connect the neutral wire to the **N** terminal of the device.
2. **Device Diagram**
   Refer to the diagram printed on the device for detailed wiring instructions. Ensure all connections match the diagram.
   <ClickableImage src="/img/customers/shelly/shelly-instructions.png" alt="Device Wiring Diagram" maxWidth="500px" />

***

## Configuration Instructions

1. **Wire the Device**
   Ensure the device is wired according to the provided wiring diagram and connect the Ethernet cable securely.
   <ClickableImage src="/img/customers/shelly/shelly-wire-cable.jpg" alt="Shelly Wiring Example" maxWidth="450px" />
2. **Access the Shelly Interface**
   * Using a phone or other device, connect to the Shelly relay's Wi-Fi network (e.g. **SSID: ShellyPro2-XXXXXX**).
   * Open a browser and navigate to [**http://192.168.33.1**](http://192.168.33.1) to access the Shelly interface.
3. **Locate the Ethernet Settings**
   <ClickableImage src="/img/customers/shelly/shelly-interface.jpg" alt="Shelly Interface Example" maxWidth="300px" />
   <ClickableImage src="/img/customers/shelly/shelly-ethernet.png" alt="Ethernet Settings Example" maxWidth="700px" />
   * In the Shelly interface, navigate to the **Ethernet Settings** section.
   * Here, you will find the assigned **Ethernet IP address**, which is required for connecting the device to the controller.

> [!NOTE]
>   **Note**: Do not modify any settings while locating the Ethernet IP address.

By following these steps, you will retrieve the required IP address for integrating the Shelly relay with the <ControllerName />.
For further details and comprehensive documentation, please refer to the official [Shelly Installation Guides](https://kb.shelly.cloud/knowledge-base/installation-guides).


# Siemens


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/sgo/Logo_Siemens.png"
    alt="Siemens"
    style={{ display: "block", margin: "0 auto", width: "40%" }}
/>

## Supported Devices

<DeviceSupportTable
  devices={[
    { 
        type: 'PAC energy meter',
        modbusTcp: '✅',
        rs485: '✅',
      instructionVideos: [{"videoId": "3Vj0w5qCwMY", "title": "Siemens PAC2200 5 A · RS485", "description": "PAC2200 5 A, reference 7KM2200-2EA30-1DA1, with RS485."}]
    },
    {
        type: 'PAC digital inputs (built-in)',
        modbusTcp: '✅',
        rs485: '✅',
    },
    {
        type: 'PAC digital inputs (via extension)',
        modbusTcp: '✅',
        rs485: '✅',
    },
    {
        type: '3WA',
        modbusTcp: '✅',
        rs485: '✅',
    }
  ]}
  showModbusTcp={true}
  showRs485={true}
/>

<div
  style={{
    display: "flex",
    justifyContent: "center",
    alignItems: "flex-start",
    gap: "20px",
    flexWrap: "wrap",
    margin: "20px 0"
  }}
>
  <ClickableImage
    src="/img/customers/siemens/meter.jpg"
    alt="Siemens PAC energy meter"
    maxWidth="450px"
  />

  <ClickableImage
    src="/img/controller/devices/energy-meter/siemens/s3.gy.digital_technomat_uploads_asset_data_728502_05.03.6267_1.webp"
    alt="Siemens device"
    maxWidth="450px"
  />
</div>

Wiring
------

### RS485

> [!IMPORTANT] Check the terminal labels for the exact PAC or 3WA model
> Siemens terminal positions depend on the meter and communication module. Follow the device-specific Siemens wiring diagram and connect **RS485 A/+** to controller **A**, **RS485 B/-** to controller **B**, and the reference conductor to **GND** when provided. For Ethernet-capable models, follow the [Ethernet wiring guidelines](/Controller/wiring-best-practices/#ethernet).

## Configuration

<RS485AddressNote />


# Smappee


import {
  BrandName,
  ControllerName,
  CustomerName,
} from "@site/src/components/customFields";
import RS485ConnectionTable from "@site/src/components/RS485ConnectionTable";
import ClickableImage from "@site/src/components/ClickableImage";
import RS485AddressNote from "@site/src/components/RS485AddressNote";
import PdfLink from "@site/src/components/PdfLink";
import DeviceSupportTable from "@site/src/components/DeviceSupportTable";

<img
  src="/img/customers/smappee/logo.png"
  alt="logo"
  style={{ display: "block", margin: "0 auto", width: "40%" }}
/>

## Supported Devices

<DeviceSupportTable
  devices={[
    {
      type: `Smappee energy meters with MQTT`,
      mqtt: "✅",
      modbusTcp: "❌",
      rs485: "❌",
    },
  ]}
  customColumns={{ mqtt: "MQTT" }}
  showModbusTcp={true}
  showRs485={true}
/>

<ClickableImage
  src="/img/customers/smappee/smappee-infinity-modularity.jpg"
  alt="Image 1"
  maxWidth="550px"
/>


> [!NOTE]
> The integration is at the moment available only for the older Genius models (Serial number starting with 501xx).

## Configuration

Smappee should communicate through MQTT to the <CustomerName /> database. This database is then used as a source for the Smappee data.

Documentation about Smappee MQTT can be found in the attached document from Smappee: <PdfLink url="/docs/API_and_MQTT_documentation.pdf" />.

### 1. Creating MQTT credentials

Request the Eniris MQTT username and password through the [Eniris webshop](https://webshop.eniris.com/). New credentials must no longer be created through the legacy **Credentials & Licenses** page in Insights.

Keep the issued credentials available for the broker configuration in step 4. Do not invent a username or reuse credentials from another protocol.

### 2. Get the Smappee UUID

The Smappee UUID is an important link to the correct Smappee location.

Obtain it through:

- Dashboard:
  1. go to https://dashboard.smappee.net
  2. add a Location configuration card
- REST API call:
  1. Go to https://smappee.atlassian.net/wiki/spaces/DEVAPI/pages/526483487/Get+Servicelocations
- MQTT wildcard:
  1. Match the Configuration Topic results to the serial number you need, see https://www.hivemq.com/blog/mqtt-essentials-part-5-mqtt-topics-best-practices

<ClickableImage
  src="/img/customers/smappee/smappee-uuid.png"
  alt="Image 1"
  maxWidth="550px"
/>

### 3. Get the Smappee IP address

1. Open the Smappee APP
2. Go to Settings
3. Click Your Smappee monitors
4. Click Smappee Infinity
5. Click Infinity Components
6. Click Smappee Genius
7. Find the IP-address in the details

<ClickableImage
  src="/img/customers/smappee/smappee-ip-address-pt1.png"
  alt="Image 1"
  maxWidth="550px"
/>
<ClickableImage
  src="/img/customers/smappee/smappee-ip-address-pt2.png"
  alt="Image 1"
  maxWidth="550px"
/>

### 4. Configuring the MQTT broker in the Smappee Energy Meter

1. Navigate to the in the previous step determined IP of your Smappee monitor followed by /smappee.html . Example: 192.168.0.128/smappee.html
2. Click Logon/logoff and log in
3. Click advanced
4. Fill in the MQTT local broker url: mqtt://mqtt.eniris.be:1883
5. Fill in the MQTT username and password issued after your webshop request
6. Click apply changes and restart monitor
   <ClickableImage
     src="/img/customers/smappee/smappee-config-settings-pt1.png"
     alt="Image 1"
     maxWidth="550px"
   />
   <ClickableImage
     src="/img/customers/smappee/smappee-config-settings-pt2.png"
     alt="Image 1"
     maxWidth="550px"
   />

### 5. Configuration in the <BrandName /> <ControllerName />

Add the device in the <BrandName /> <ControllerName />. When asked for, enter the:

- UUID
- serial number of the meter
- number of phases that are measured
  <ClickableImage
    src="/img/customers/smappee/smappee-configuration-controller-pt1.png"
    alt="Image 1"
    maxWidth="550px"
  />


# Smartgrid-ready



# ✅ Smart Grid Ready Heat Pumps

This list contains heat pump models that support SG Ready

---

## 2G Energy AG
- afilia air series  
  e.g., `afilia air C-sl 0452 HE/XL/RV P2U- R454B` and variants

## Airwell
- Wellea Monobloc A, DF, WT, Monobloc R32, Split R32
- Wellea Split A
- R290 Series: `4DC`, `6DC`, `9DC`, `12DC`, `16DC`, `19DC`
- DCT-R290 Series: `9DCT`, `12DCT`, `16DCT`, `19DCT`, `22DCT`

## Alpha Innotec
- Luxtronik controlled heat pumps

## Atag
- Energion M Compact / Hybrid / Plus
- Energion M All Electric series

## Atlantic
- Alfea Extensa M
- Calypso VM
- Explorer V4

## Bosch
- Compress 3400i AWS
- Compress 7000 LW, 7800i LW
- Compress Hybrid 3000i, 5800i, 7000i AW
- CS 3000 AWP

## Bulex
- MagnaAqua (PV-ready)

## Clivet
- Aqua Plus
- Sphera Evo

## CTC
- GSI
- EcoZenith
- EcoLogic L M

## Daikin
- Altherma 3 H HT F, 3 H MT F, 3 M, 3 RF, 3 RW
- Altherma H Hybrid
- EKHHE, EKHHP, EHS, RoCon HP

## Dynamis (Kospel)
- HPM2

## Heliotherm
- Models with Remote Control Gateway

## Hitachi
- Yutaki Series
- Yutaki S Combi

## IDM
- Smart Grid Ready models (unspecified)

## Itho Daalderop
- Amber

## Kronoterm
- VERSI-I, VERSI-X
- ETERA S, M, L
- VERSI-O

## LG
- HN1616.NK5
- HN1616M.NK5
- HN0916M.NK4
- HN091MR.NK5
- HN1600MB.NK0

## Midea
- ESG INV M (Swimming Pool Heat Pumps)

## Mitsubishi Electric
- Ecodan Series
- Ecodan EHPT20X-MHEDW
- PAC-IF071B-E
- PAC-TH012HT-E
- Hydrobox

## Nefit (Bosch Group)
- EnviLine AW Monoblock / IDU Monoblock E / TTS
- EnviLine AW Split

## Nibe
- F1155, F1245
- S1155, S1255
- Other Smart Grid Ready variants

## Nulite
- R290 Series
- Flamingo Series
- Geothermal Series *(SG Ready to be confirmed model-by-model)*

## Ochsner
- AIR FALCON 212
- AIR HAWK 208
- AIR M2+M4

## Panasonic
- Aquarea Series
- WH-MDC Monobloc
- WH-SDC
- WH-UD/UX/UQ Series
- EasyPLUG (PAW) for SG 230V

## R-Aqua
- HPB 100–300
- HPB-S Solar

## Remeha
- Elga Ace (hybrid air-water)

## Rinnai
- Enviroflo Hot Water Heat Pumps *(SG capability in development — verify)*

## Stiebel Eltron
- SG Ready models available *(verify per model)*

## Thermia
- Atlas
- Calibra
- Mega

## Tongyi Heat Pump
- SG Ready certification (model-specific confirmation needed)

## Vaillant
- aroTHERM (plus)
- aroSTOR
- flexoTHERM
- flexoCOMPACT
- climaVAIR

## Viessmann
- Vitocal Series
  - e.g., Vitocal 250-A

## Vivax
- HPP Swimming Pool

## Weishaupt
- Geoblock WGB
- Splitblock WSB

## Wolf
- BWL
- FHA
- CHA


# Socomec


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
  src="/img/customers/Socomec/logo.png"
  alt="logo"
  style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

## Supported Devices

<DeviceSupportTable
  devices={[
    {
      type: 'Diris',
      variants: 'A30',
      modbusTcp: '✅',
      rs485: '✅',
      instructionVideos: [{"videoId": "IFLUgsIebS4", "title": "Socomec DIRIS A-30 · module 48250092 · RS485", "description": "DIRIS A-30 48250403 with the RS485 module 48250092 already installed."}]
    }, {
      type: 'Diris',
      variants: 'A40',
      modbusTcp: '✅',
      rs485: '✅',
    }, 
    {
        type: 'Diris',
        variants: 'I30',
        modbusTcp: '✅',
        rs485: '✅',
    }, {
        type: 'Diris',
        variants: 'I35',
        modbusTcp: '✅',
        rs485: '✅',
    },{
      type: 'Countis',
      variants: 'E27',
      modbusTcp: '✅',
      rs485: '✅',
    }
  ]}
  showVariants = { true }
  showModbusTcp = { true }
  showRs485 = { true }
/>

## Wiring

### Ethernet
For correct ethernet wiring: Follow the [the guidelines for ethernet wiring](/Controller/wiring-best-practices/#ethernet).


# Solax


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/sgo/Logo_Solax.png"
    alt="Solax"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

## Supported Devices

<DeviceSupportTable
  devices={[
    { 
        type: 'Energy Meter via Hybrid G4 Inverter',
        modbusTcp: '✅',
        rs485: '❌',
    }
  ]}
  showModbusTcp={true}
  showRs485={true}/>

<ClickableImage src="/img/customers/solax/g4.jpg" alt="Image 1" maxWidth="450px" />

# Solis Energy Meter


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/customers/solis/logo.png"
    alt="Solis"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

## Supported Devices

<DeviceSupportTable
  devices={[
    {
        type: 'Solis Energy Meter',
        modbusTcp: '✅',
        rs485: '✅',
    },
    {
        type: 'Autarco Energy Meter',
        modbusTcp: '✅',
        rs485: '✅',
    }
  ]}
  showModbusTcp={true}
  showRs485={true}
  />

## Connection

### Ethernet
For correct ethernet wiring: Follow the [the guidelines for ethernet wiring](/Controller/wiring-best-practices/#ethernet).

### RS485
<RS485ConnectionTable firstColumn={["A", "B", "GND (optional)"]} />

## Configuration

<RS485AddressNote />

Ensure the meter is configured with the following Modbus settings to match the driver specifications:

* **Baudrate:** 9600
* **Data bits:** 8
* **Stop bits:** 1
* **Parity:** None
* **Modbus Address:** 1 (default) - Range: 1 to 254

# Solis Grid-Tied Energy Meter


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/customers/solis/logo.png"
    alt="Solis"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

## Supported Devices


<DeviceSupportTable
  devices={[
    {
        type: 'Solis Grid-Tie Meter (via Inverter/EPM)',
        modbusTcp: '✅',
        rs485: '✅',
    },
    {
        type: 'Autarco Grid-Tie Meter (via Inverter/EPM)',
        modbusTcp: '✅',
        rs485: '✅',
    }
  ]}
  showModbusTcp={true}
  showRs485={true}
  />

## Connection

### Ethernet
For correct ethernet wiring: Follow the [the guidelines for ethernet wiring](/Controller/wiring-best-practices/#ethernet).

### RS485
Connect the RS485 wires to the communication port of the Solis device (Inverter or Export Power Manager).

<RS485ConnectionTable firstColumn={["A", "B", "GND (optional)"]} />

## Configuration

<RS485AddressNote />

Ensure the device is configured with the following Modbus settings to match the driver specifications:

* **Baudrate:** 9600
* **Data bits:** 8
* **Stop bits:** 1
* **Parity:** None
* **Modbus Address:** 1 (default) - Range: 1 to 254

# Solis


import { FolderOverview } from '@/components/FolderOverview';

# Solis

<FolderOverview folder="Controller/Devices/Energy-meter/Solis" />


# Sunwoda


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/sgo/Logo_Sunwoda.png"
    alt="logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>
# Sunwoda

## Supported Devices

<DeviceSupportTable
  devices={[
    { type: 'Energy Meter via Sunwoda OSP', modbusTcp: '❌', rs485: '✅'}
  ]}
  showModbusTcp={true}
  showRs485={true}
/>



## Wiring

### RS485
<RS485ConnectionTable firstColumn={["", "", ""]} />

## Configuration
<RS485AddressNote />

# Tillquist


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/sgo/Logo_Tillquist.png"
    alt="Tillquist"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

## Supported Devices


<DeviceSupportTable
  devices={[
    { 
        type: 'LQT40M',
        modbusTcp: '✅',
        rs485: '❌',
      instructionVideos: [{"videoId": "fW3m1TBBBvM", "title": "Tillquist LQT40M-20000 · Ethernet", "description": "Models: Tillquist LQT40M-20000."}]
    }
  ]}
  showModbusTcp={true}
  showRs485={true}/>

## Connection

The communication between the <BrandName /> and the energy meter operates via Modbus TCP.

### Ethernet
For correct ethernet wiring: Follow the [the guidelines for ethernet wiring](/Controller/wiring-best-practices/#ethernet).

# Victron


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/sgo/Logo_Victron.png"
    alt="Victron"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

## Supported Devices


<DeviceSupportTable
  devices={[
    { 
        type: 'Energy Meter via Cerbo GX',
        modbusTcp: '✅',
        rs485: '❌',
    }
  ]}
  showModbusTcp={true}
  showRs485={true}/>

<ClickableImage src="/img/customers/victron/cerbogx.png" alt="Image 1" maxWidth="450px" />

# Weidmüller


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/customers/weidmuller/logo.png"
    alt="logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>


## Supported Devices
<ClickableImage src="/img/customers/weidmuller/610-230.png" alt="Image 1" maxWidth="350px" />


<DeviceSupportTable
  devices={[
    { 
        type: 'Weidmüller 610-230',
        modbusTcp: '❌',
        rs485: '✅',
      instructionVideos: [{"videoId": "tCjjQXFR3Kc", "title": "Weidmüller ENERGY METER 610-230 · RS485", "description": "ENERGY METER 610-230, reference 2540850000."}]
    }
  ]}
  showModbusTcp={true}
  showRs485={true}/>

## Wiring
<RS485ConnectionTable firstColumn={["", "", ""]} />
{/* TODO: Confirm wiring */}

## Configuration
<RS485AddressNote />

Check to the meter manual for more detailed information on activating Modbus RTU and changing the Modbus address.
<ClickableImage src="/img/customers/weidmuller/610-230-config_pt1.png" alt="Image 1" maxWidth="350px" />

# WhatWatt


import { BrandName, ControllerName } from '@site/src/components/customFields';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/customers/whatwatt/logo.png"
    alt="WhatWatt"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

## Supported Devices

<DeviceSupportTable
  devices={[
    { 
        type: 'WhatWatt GO Energy Meter',
        modbusTcp: '✅',
        rs485: '❌',
    }
  ]}
    showModbusTcp={true}
    showRs485={true}
    />

<ClickableImage src="/img/customers/whatwatt/ww-go-physical.png" alt="WhatWatt GO Energy Meter" maxWidth="350px" />

## Configuration
### Installation Requirements
- Must purchase a whatwatt Plus license to enable Modbus TCP support.
- The Energy Meter must be connected to the P1 port of your digital utility meter and be joined to the same local network as the <ControllerName />.

### Modbus TCP
1. Visit the device's **web interface** at `http://<DEVICE_IP_ADDRESS>/` and enter your **license key**.
2. Navigate to the **Integrations** page and enable Modbus. Keep the port as 502.
3. Click the **check mark** in the top right to save the settings.

# YouLess


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/sgo/Logo_YouLess.png"
    alt="YouLess"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

## Supported Devices


<DeviceSupportTable
  devices={[
    { 
        type: 'LS120 P1 Converter',
        modbusTcp: '✅',
        rs485: '❌',
    }
  ]}
  showModbusTcp={true}
  showRs485={true}/>

<ClickableImage src="/img/customers/youless/ls120.jpg" alt="Image 1" maxWidth="450px" />

# Zendure P1 Meter


import { BrandName, ControllerName } from '@site/src/components/customFields';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/customers/zendure/zendure-logo.jpg" 
    alt="Zendure Logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

## Supported Devices

The Zendure P1 Smart Meter provides high-precision grid monitoring, typically used to feed data into the SolarFlow energy management logic.

<DeviceSupportTable
  devices={[
    {
      type: "P1 Smart Meter",
      api: '✅', 
      rs485: "❌",
      curtailment: "❌"
    },
  ]}
  showModbusTcp={false}
  showRs485={false}
  showCurtailment={false}
  showApi={true}
/>

---
<img
    src="/img/customers/zendure/p1-meter.jpg" 
    alt="Zendure p1 meter image"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>
---

## System Integration

The P1 Meter is a monitoring-only device that provides real-time grid data. This data is used by the <ControllerName /> to determine the necessary power setpoints for the battery system.

> [!NOTE] Companion Device
> To control your battery storage based on the P1 Meter's readings, see the [Zendure SolarFlow Documentation](../PV-hybrid-and-battery-inverters/Zendure-SolarFlow).

---

## Configuration

### 1. Installation Requirement
The P1 Meter must be connected to the P1 port of your digital utility meter and be joined to the same local network as the <ControllerName />.

### 2. Network Stability
As with all Zendure local API devices, you should **connect it via MAC Address Reservation**.

### 3. Required Parameters
* **IP Address:** The local IP of the P1 Meter.


# Ziv


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/sgo/Logo_Ziv.png"
    alt="Ziv"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

## Supported Devices

| Device Type | Variants | P1 to USB |
|:--:|:--:|:--:|
| DSMR Smart Meter | / | ✅ |

<DeviceSupportTable
  devices={[
    { 
        type: 'ZIV DSMR Smart Meter',
        customCol: '✅',
    }
  ]}
  customColumns={{ "customCol": "Digital I/O Inputs" }}
  showModbusTcp={true}
  showRs485={true}/>

<ClickableImage src="/img/customers/ziv/meter.jpeg" alt="Image 1" maxWidth="450px" />

# a-TroniX



# ABB


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

# ABB charging stations

<img
    src="/img/customers/abb/logo.png"
    alt="a-TroniX"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>


## Supported Devices

<DeviceSupportTable
  devices={[
    { 
      type: 'ABB Terra AC', 
      variants: '/',
      modbusTcp: '✅', 
      rs485: '✅'
    }
  ]}
  showVariants={true}
  showModbusTcp={true}
  showRs485={true}
/>

<ClickableImage src="/img/customers/abb/terra-ac.jpg" alt="Image 1" maxWidth="450px" />


## Wiring

### Ethernet
For correct ethernet wiring: Follow the [the guidelines for ethernet wiring](/Controller/wiring-best-practices/#ethernet).

### RS485
<RS485ConnectionTable firstColumn={["", "", ""]} />


## Configuration
After the electrical installation of a charger is complete, follow these steps to configure the charger:
1. Install ABB TerraConfig using the links on the official [Terra AC digital tools page](https://new.abb.com/ev-charging/terra-ac-wallbox/digital-tools). Current manuals are available in the [ABB EV charging document library](https://new.abb.com/ev-charging/ev-charging-infrastructure/documents).
2. On the dashboard, select "Configure a charger."
3. Enable Bluetooth on your phone, as this is necessary for the app to communicate with the charger during the commissioning process.
4. Choose a charger from the available list.
<ClickableImage src="/img/customers/abb/terra-config-step1.png" alt="Image 1" maxWidth="450px" />

5. You can also select a charger by scanning the SN barcode with the app.
6. Be sure to scan the charger's SN bar code, which usually begins with "TAC" (although this may vary depending on the product variant).
<ClickableImage src="/img/customers/abb/terra-config-step2.png" alt="Image 1" maxWidth="450px" />

7. After selecting a charger to connect to, enter the PIN.
8. Select below the option "EDIT CURRENT CONFIGURATION" - or if the charging station has not yet been configured, then select "Start from scratch."
9. Make sure your phone or mobile app is connected to the Internet for PIN validation.
10. Throughout the process, the app will display a pop-up confirming that all settings will be applied to the charger simultaneously once you get to the last step.
<ClickableImage src="/img/customers/abb/terra-config-step3.png" alt="Image 1" maxWidth="450px" />

11. Click on the "Energy management" submenu.
<ClickableImage src="/img/customers/abb/terra-config-step4.png" alt="Image 1" maxWidth="450px" />

12. Toggle "Modbus" on.
<ClickableImage src="/img/customers/abb/terra-config-step5.png" alt="Image 1" maxWidth="450px" />

13. Select "Local controller" and then "Modbus RTU (RS485)" or "Modbus TCP/IP" depending on whether the charging station is connected to the  via RS485 or Ethernet.

    **Modbus RTU (RS485)**
14. Choose a unique Modbus address, different from all other Modbus addresses of devices on the same RS485 bus.
15. Choose baud rate 9600, parity Even, stop bits 1 and data bits 8.

    **Modbus TCP/IP**
16. You must set a fixed IP address in the charging station within the same network range as the.
17. Important: Always choose 502 as the server port.
18. For home and small business networks, a typical setup is with e.g. fixed IP address 192.168.1.50:
    - IP address: 192.168.1.50
    - Mask address: 255.255.255.0
    - Gateway address (the address of your router): 192.168.1.1
    - Server Port: 502
<ClickableImage src="/img/customers/abb/terra-config-step6.png" alt="Image 1" maxWidth="450px" />


# Alfen


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

# Alfen charging stations

<img
    src="/img/customers/alfen/logo.png"
    alt="Alfen"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>


This guide will serve as a guide to adjust the Alfen charging station settings to allow communication with and control by the <BrandName /> <ControllerName />.
For more in depth information you can use the [Alfen Smart charging implementation guide](https://knowledge.alfen.com/space/SER/854327297/Manuals+and+Guides+in+English_EN)


## Supported Devices


<DeviceSupportTable
  devices={[
    { type: 'Most Alfen charging stations', modbusTcp: '✅', rs485: '❌',
  instructionVideos: [{"videoId": "3RpwVBGfCLo", "title": "Alfen Eve Single S-line / Pro-line"}, {"videoId": "vpOvK3KNuxk", "title": "Alfen Eve Double Pro-line"}, {"videoId": "jIDB0Cp7KKo", "title": "Alfen Eve Single Plus"}, {"videoId": "jBPknmTZaZU", "title": "Alfen Eve Double Plus"}]
}
  ]}
  showModbusTcp={true}
  showRs485={true}
/>

## Configuration

Install the charging station.

1. Update the Alfen charging station to firmware version 4.2.0 (or higher).
2. Connect the Alfen charging station to a network with the following requirements:
    - The charging station is in the same local network as the <BrandName /> <ControllerName />.
    - Make sure the communication between the charging station and the <BrandName /> <ControllerName /> is open.
3. Install the [ACE service installer tool](https://knowledge.alfen.com/space/IN/1627488257/Download+the+ACE+Service+Installer), or search for the latest version of the ACE service installer on the internet if the link does not work.
4. Create a valid account for Alfen ACE Service Installer now (to be requested via https://support.alfen.com)

5. To control the charging station, the smart charging functionality must first be purchased and then rolled out. 
    1. Unlocking functionality via the ACE Service Installer: to unlock functionality via the ACE Service Installer, do the following:
        1. Open the ACE Service Installer
        2. Click on the desired charging station
        3. Go to the *General info* tab and select *License key*
            <ClickableImage src="/img/customers/alfen/alfen_config_pt1.png" alt="Image 1" maxWidth="400px" />

        4. Click *Update license key* to activate the purchased functionality. The charging station will restart after the license key is updated.

    2. If the location has a weak internet connection, the following procedure can be used to unlock the desired functionality:
        1. Open the ACE Service Installer
        2. Go to *Device* in the menu
        3. Select *Install feature(s)*
            <ClickableImage src="/img/customers/alfen/alfen_config_pt2_1.png" alt="Image 2.1" maxWidth="300px" />

        4. Enter the license key and click *OK*. The charging station will restart after the license key is updated.
            <ClickableImage src="/img/customers/alfen/alfen_config_pt2_2.png" alt="Image 2.2" maxWidth="300px" />

6. Configuring ALB via the ACE Service Installer
    1. Open the ACE Service Installer
    2. Select the charging station
    3. Select the *Smart Charging* tab
    4. Check the box next to *Active load balancing*. The following parameters are displayed.
        <ClickableImage src="/img/customers/alfen/alfen_config_pt3.png" alt="Image 3" maxWidth="400px" />

    5. Data Source; enter the data source type: 
        - Energy Management System: The customer's Energy Management System will transmit the dynamic minimum and maximum values ​​to the charging station. Based on these values, the charging station will increase or decrease the power output from the socket.
        <ClickableImage src="/img/customers/alfen/alfen_config_pt4.png" alt="Image 4" maxWidth="400px" />

    6. Enter the Safe current. This is the current limit the charging station uses when the connection between the charging station and the energy meter/Energy Management System is lost.
        <ClickableImage src="/img/customers/alfen/alfen_config_pt5.png" alt="Image 5" maxWidth="400px" />

    7. If permitted, enter the phase rotation. Note: This is the phase sequence of the power cable (to the charging station). There are several options depending on the type of charging station and connection.
        <ClickableImage src="/img/customers/alfen/alfen_config_pt6.png" alt="Image 6" maxWidth="400px" />

    8. Click *Save*
    9. Click the power button to restart the charging station.
        <ClickableImage src="/img/customers/alfen/alfen_config_pt7.png" alt="Image 7" maxWidth="100px" />

7. Configuring an EMS via the ACE Service Installer
    1. If the Energy Management System is selected as the data source (see step 6: "Configuring ALB via the ACE Service Installer"), an additional page will appear on the screen. Double-click to open the screen. Select *TCP/IP EMS* in the menu.
        <ClickableImage src="/img/customers/alfen/alfen_config_pt8_1.png" alt="Image 8.1" maxWidth="400px" />

    2. Enter the mode. Select whether the EMS manages each individual socket or an entire Smart Charging Network.
        <ClickableImage src="/img/customers/alfen/alfen_config_pt8_2.png" alt="Image 8.2" maxWidth="400px" />
    
    3. Enter the validity period (default 60 s). If the charging station has not received updates from the EMS within the configured validity period, it will interpret this as a disconnection and will return to the configured safe current.
        <ClickableImage src="/img/customers/alfen/alfen_config_pt8_3.png" alt="Image 8.3" maxWidth="400px" />

8. Test the connection of a ALB with a EMS
    1. Configure the installation according to the instructions in the previous steps.
    2. Go to the *Live Monitoring* tab, select *States*, and observe the Modbus TCP/IP connection status as shown below:
        <ClickableImage src="/img/customers/alfen/alfen_config_pt9.png" alt="Image 9" maxWidth="400px" />

        If this status is *Not in use (communication idle)*, there is a loss of communication. Check your installation or consult the *Troubleshooting* section for more information.

    3. Connect a vehicle and start a charging session.
    4. Use the EMS to change the maximum available power. The method for doing this varies by EMS. Consult the EMS manufacturer's manual for more information.
    5. Go to the *Live Monitoring* tab, select *Currents*, and view the currents being drawn.


# Alpitronic


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

# Alpitronic charging stations

<img
    src="/img/customers/alpitronic/logo.png"
    alt="Alpitronic"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>


## Supported Devices


<DeviceSupportTable
  devices={[
    { type: 'Alpitronic HYC', variants: 'HYC50, HYC150, HYC300, HYC400', modbusTcp: '✅', rs485: '❌' }
  ]}
  showVariants={true}
  showModbusTcp={true}
  showRs485={true}
/>

<ClickableImage src="/img/customers/alpitronic/charger.jpg" alt="Image 1" maxWidth="450px" />


## Configuration

External control of the charging station must be activated in the configuration menu via the web page of the charging station. To do this:

1. Surf to the IP address and log in with the default data or your own set of data (default user = admin, default password = admin123).
2. In the settings of the charging station:
    1. Go to "General"
    2. Go to "Power"
    3. Set "ModBus Enabled" to "True"
    4. Click on "Save Settings"
<ClickableImage src="/img/customers/alpitronic/config_pt1.png" alt="Image 1" maxWidth="450px" />
<ClickableImage src="/img/customers/alpitronic/config_pt2.png" alt="Image 1" maxWidth="450px" />

3. "Grid Fallback Timeout" is the maximum time allowed between 2 commands from the <BrandName /> <ControllerName />. The default is 5 seconds, set this to 60 seconds by default. Afterward, click "Save Settings" again.
<ClickableImage src="/img/customers/alpitronic/config_pt3.png" alt="Image 1" maxWidth="450px" />

4. Activate the changes by Resetting the charging station.
    1. Go to the main page
    2. Check that no cars are connected to the charging station
    3. Go to "Reset"
    4. Click on "Soft Reset HYC"
<ClickableImage src="/img/customers/alpitronic/config_pt4.png" alt="Image 1" maxWidth="450px" />

# Autel


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

# Autel charging stations

<img
    src="/img/customers/autel/Autel-Logo.png"
    alt="Autel"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

## Supported Devices

<DeviceSupportTable
  devices={[
    { 
      type: 'MaxiCharger DC Compact', 
      variants: '40 kW',
      modbusTcp: '✅', 
      rs485: '✅'
    },
    { 
      type: 'MaxiCharger DC Fast', 
      variants: '40–240 kW',
      modbusTcp: '✅', 
      rs485: '✅'
    },
    { 
      type: 'MaxiCharger AC Ultra', 
      variants: '2 × 22 kW',
      modbusTcp: '✅', 
      rs485: '❌'
    }
  ]}
  showVariants={true}
  showModbusTcp={true}
  showRs485={true}
/>

## Wiring

### Ethernet
For correct Ethernet wiring, follow the [guidelines for Ethernet wiring](/Controller/wiring-best-practices/#ethernet).

### RS485
<RS485ConnectionTable firstColumn={["", "", ""]} />


## Configuration

After the electrical installation of a charger is complete, follow these steps to configure communication with the <BrandName /> <ControllerName />.  

---

### MaxiCharger DC Compact and DC Fast

#### Step 1 – Access the Local Service Portal

1. On the charging station’s touchscreen, go to the **Home** screen.  
2. **Double-tap the upper-left corner** of the screen.  
3. Tap **Device Maintenance**.  
4. Enter the password — the **last six digits of the serial number** found on the product label.  


---

#### Step 2 – Set Modbus Parameters

1. Tap **Set Parameters**.  
2. Wait for the system to load data.  
3. Configure communication settings as follows:  

##### For **Modbus TCP (Ethernet)**  
- **OCPP IP**: IP of the <BrandName /> <ControllerName /> (e.g. `192.168.1.100`)  
- **OCPP PORT**: `502`  
- **MGR IP / URL / PORT**: Optional management platform details  
- **Running environment**: Select correct region (EU, UK, USA, etc.)

##### For **Modbus RTU (RS485)**  
- **Modbus Slave Address**: Unique ID (1–247)  
- **Baud Rate**: `9600`  
- **Parity**: `None`  
- **Data Bits**: `8`  
- **Stop Bits**: `1`


---

#### Step 3 – Save and Verify

1. Tap **Save**. The system will restart with the new settings.  
2. Wait for about 1–2 minutes until boot completes.  
3. On the Home screen, check the **Internet connection icon**:  
   - ✅ Connected — icon shows a network link  
   - ❌ Disconnected — icon shows “x”; check cables or settings  


---

###  MaxiCharger AC Ultra

#### Step 1 – Power On and Initial Setup

1. Switch on the power to the charger.  
2. The charger will launch the setup wizard.  
3. Follow the on-screen steps:  
   - Select the **language**.  
   - Connect via **Wi‑Fi**, **Ethernet**, or **Cellular**.  
   - Set **time zone**.  
   - Set **maximum input current** to match grid capacity.  


---

#### Step 2 – Access the Maintenance Menu

1. On the **Standby Screen**, tap the **currency ($)** icon (bottom-left corner).  
2. The **Cost Details** screen will open.  
3. **Double-tap the top-left corner** to enter the maintenance menu.  
4. Tap **Device Maintenance**.  
5. Enter the **last six digits of the charger’s serial number**.  


---

#### Step 3 – Configure Modbus TCP Settings

1. Tap **Set Parameters**.  
2. Fill in the following fields:

| Setting | Description | Example |
|----------|--------------|----------|
| **OCPP IP** | IP address of the <BrandName /> <ControllerName /> | `192.168.1.100` |
| **OCPP PORT** | Modbus port number | `502` |
| **MGR IP/URL/PORT** | Optional backend connection details | – |
| **Running Environment** | Corresponding operating region | `Europe` |


---

#### Step 4 – Save and Verify

1. Tap **Save** to confirm and restart the device.  
2. Once restarted, confirm the connection icon shows active network status.  



# Blitz-Power


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';


## Access to the web interface
### Accessing the Blitz Power Station web interface

> [!NOTE] After starting up the charging station, the webpage becomes accessible after about 8 minutes.
To access the platform, there are 2 different options:

Via Internet connection (see image next to this)

1. You must connect the ETH0 port via a router to access the Master BPS from your PC if it is connected to the same router.

2. Browse to: http://ev3000.local:3000.

3. The webpage opens and you can start the configuration.

4. We recommend assigning a static IP address to the charging station via the network settings now. Note: if the Blitz webpage does not open, follow this step.
> [!NOTE]
> If the Blitz webpage does not open, follow these steps: 

1. Make sure the PC you are connecting with is set to DHCP (automatic IP address assignment) in the internet settings. You can check this via network connections:



<ClickableImage src="/img/customers/Blitz-power/BlitzCompleteRoute.png" alt="blitz-power" maxWidth="450px" />


## Configuration via Modbus modbusTcp

1. Click on Load Management in the menu bar.

2. Enter a custom name under Charging Park Name.

3. Set the maximum current value of the fuse protecting the charging park under Load Circuit Fuse.

4. For High Level Measuring, choose the communication protocol. • IP Address

5. Enter the (IP) address of the energy meter from the electrical cabinet.

6. Device type is EEM377 (if the meter is supplied by Blitz Power).

7. Under Charging Points, select the charging points that should participate in Load Management.

8. Click Save: Success appears on the screen.

9. Perform a restart of the charging station.

> [!WARNING]
>  Dynamic Load Management only works if the facilities for the charging station are tapped directly from the main fuse.

<ClickableImage src="/img/customers/Blitz-power/BlitzLoadManagement.png" alt="blitz-power-LoadManagement" />

## Configuration via RS485

Dynamic load management (WITH energy meter)

1. Click on Load Management in the menu bar.

2. Enter a custom name under Charging Park Name.

3. Set the maximum current value of the main fuse protecting the entire site under Load Circuit Fuse.

4. For High Level Measuring, choose the communication protocol. • RS 485 (modbus)

5. Select the name of the master charging station (position 1).

6. Under Charging Points, select the charging points that should participate in Load Management.

7. Click Save: Success appears on the screen.

8. Perform a restart of the charging station.

> [!WARNING]
>  Dynamic Load Management only works if the facilities for the charging station are tapped directly from the main fuse.


# Easee

import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/customers/easee/logo.png"
    alt="Easee logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

<DeviceSupportTable
  devices={[
    { 
        type: 'Easee One',
        api: '✅',
        modbusTcp: '❌',
        rs485: '❌'
    },
    {
        type: 'Easee Up',
        api: '✅',
        modbusTcp: '❌',
        rs485: '❌'
    },
    {
        type: 'Easee Max',
        api: '✅',
        modbusTcp: '❌',
        rs485: '❌'
    },
    {
        type: 'Easee Pro',
        api: '✅',
        modbusTcp: '❌',
        rs485: '❌'
    },
          {
        type: 'Easee Charge',
        api: '✅',
        modbusTcp: '❌',
        rs485: '❌'
    },
    {
        type: 'Easee Core',
        api: '✅',
        modbusTcp: '❌',
        rs485: '❌'
    },
  ]}
  showModbusTcp={true}
  showRs485={true}
  showApi={true}
/>
<img
    src="/img/customers/easee/2.webp"
    alt="Easee charger"
    style={{ display: "block", margin: "0 auto", width: "20%"}}
/>
## Configuration
The <BrandName /> <ControllerName /> communicates with Easee chargers via the Easee API.
To enable communication, you need to have an account on the Easee Cloud platform and link your chargers to that account.
You can then enter your Easee Cloud credentials in the <BrandName /> <ControllerName /> configuration.

In addition, an _site key_ is needed. This can be found in the __Easee__ app. This is the card shown when you press About in the Site Settings page.
More information about this card can be found in the [site card page of the Easee documentation](https://support.easee.com/hc/en-gb/articles/7807449952401-About-Site-Card).
<img
    src="/img/customers/easee/1.jpg"
    alt="Easee app"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>


# Enovates


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
  src="/img/customers/enovates/Enovates-logo.png"
  alt="Enovates"
  style={{ display: "block", margin: "0 auto", width: "40%" }}
/>

# Enovates charging stations



## Supported Devices

<DeviceSupportTable
  devices={[
    {
      type: "Enovates Single Wallbox (SWB_4xx_22 series)",
      variants: "T2 / C7 / T2S / T2S+E",
      modbusTcp: "✅",
      rs485: "❌",
      curtailment: "✅ (per-connector current setpoint)"
    }
  ]}
  showVariants={true}
  showModbusTcp={true}
  showRs485={true}
  showCurtailment={true}
/>

<ClickableImage src="/img/customers/enovates/enovates-wallbox.jpg" alt="Enovates Single Wallbox" maxWidth="450px" />

---

## Wiring

### Ethernet
1. Connect the LAN (Ethernet) port of the charger to the same network as the <BrandName /> <ControllerName />.  
2. For correct Ethernet wiring standards, follow the [Ethernet wiring guidelines](/Controller/wiring-best-practices/#ethernet).  
3. Make sure port 502 (Modbus TCP) is not blocked by your firewall or switch configuration.

---

## Configuration

After completing the physical installation and powering on the unit, follow these steps to configure the Wallbox.

### 1. Install the *My‑eNovates* App
The charger is configured using the official **My‑eNovates** mobile app.



### 2. Prepare the charger
1. **Power on** the charger and wait until the LED frame lights up.  
   - **Steady yellow:** Vehicle detected / ready for authorization  
   - **Steady green:** Authorized / ready for charging  
2. Enable **Bluetooth** on your phone or tablet.  
3. Locate the **User QR code** printed on the back of the installer manual or charger label. You will need this to connect through the app.

### 3. Connect and configure the device
1. Open **My‑eNovates** and **scan** the User QR code.  
2. Follow the app’s instructions to connect to the charger and set parameters:
   - **Charger name (alias)** – for easy identification  
   - **Authentication mode**  
     - *Plug & Charge* – charging starts automatically when a car is plugged in  
     - *RFID authorization* – the user must swipe a valid RFID card  
   - **Token management** – add or remove RFID tags  
   - **Charging schedule** – optional time scheduling  
   - **LED light intensity** – adjust brightness if required
3. Confirm and **save settings**. All configurations are stored locally in the charger.

### 4. Verify network and Modbus TCP access
1. Connect the **Ethernet port** of the charger to the site LAN that hosts the <ControllerName />.  
2. Ensure the charger is assign**ed a fixed IP address** (either manually or via DHCP reservation).  
3. The **Modbus TCP port 502** must be open.  
4. You can confirm accessibility by pinging the charger’s IP from a PC or the controller network.  
5. On the <BrandName /> <ControllerName /> interface, go to:  
   **Devices → Add device → EV Charging Station → Modbus TCP**  
   - **IP address:** enter the charger’s IP  
   - **Port:** 502  
   - **Unit ID:** 1 (default)

Start the scan. The controller detects the Enovates Wallbox automatically and creates:
- One **parent node** for the charger  
- One **child node per connector**



# Etrel


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

# Etrel INCH charging stations

<img
  src="/img/customers/etrel/etrel-logo.png"
  alt="Etrel"
  style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

This guide explains how to configure and connect the **Etrel INCH** and **INCH Duo** smart AC chargers for communication with the <BrandName /> <ControllerName />.

## Supported Devices

<DeviceSupportTable
  devices={[
    { 
      type: 'Etrel INCH / INCH Duo', 
      variants: 'All variants supporting Modbus TCP (via local network)',
      modbusTcp: '✅', 
      rs485: '❌',
      curtailment: '✅ (per‑connector current control)'
    }
  ]}
  showVariants={true}
  showModbusTcp={true}
  showRs485={true}
  showCurtailment={true}
/>

<ClickableImage src="/img/customers/etrel/etrel-inch-pro.png" alt="Etrel Inch EV charger" maxWidth="450px" />


## Wiring

### Ethernet connection
1. Connect the **Ethernet (LAN)** port of the charging station to the same local network as the <BrandName /> <ControllerName />.  
2. Make sure the LAN connection is live and the LEDs on the port are on.  
3. Recommended network cable: **Cat 5e or higher**, shielded for outdoor use if needed.

For general Ethernet wiring best practices, see the [Ethernet wiring guidelines](/Controller/wiring-best-practices/#ethernet).

---

## Configuration

After the electrical installation of a charger is complete:

1. **Power up the charger.**  
   - The green LED will blink while the unit boots.  
   - Wait until the LED turns steady green (charger ready).

2. **Access the local web interface.**
   - Connect your laptop to the same network as the charger.  
   - Open a web browser and enter the **charger IP address** shown on the sticker inside the side maintenance door.  
   - If you cannot find the IP, press and hold the small **reset button** inside the maintenance area until a beep—then the current IP address is displayed on the screen.

3. **Log in and verify communication settings.**
   - Check that the **network configuration** uses a fixed IP address in the same range as the <ControllerName />.  
   - Subnet mask `255.255.255.0` and **port 502** must be open for Modbus TCP.  
   - DHCP can also be used if the controller supports automatic discovery.

4. **Enable Modbus TCP communication.**
   - Open the web‑interface settings menu.  
   - Ensure **Modbus TCP** communication is active (default unit ID = 1 / port 502).  
   - No RS485 configuration is necessary.

5. **Check protection devices.**  
   - Confirm that RCD and over‑current protection are installed and active.  
   - Etrel INCH units without built‑in RCD / MCB must be protected by external devices in the main distribution cabinet.

6. **Verify the LED and LCD indicators.**
   - **Steady green:** charger available.  
   - **Blue blinking:** charging in progress.  
   - **Red:** fault—inspect or reboot before proceeding.

7. **Test communication.**  
   - From a PC, run `ping <charger_ip>` to verify the connection.  
   - Then add the charger in the <BrandName /> <ControllerName /> interface (**Devices → Add device → EV charging station → Modbus TCP**).  
   - Enter the charger IP and port 502. Keep Unit ID = 1.

8. **Confirm Modbus control.**  
   - The controller will automatically read model, serial number, and connector data.  
   - Each connector appears as a controllable child node.

> [!NOTE] Installer tip
> If connection fails, use the side maintenance door to restart the station. Hold the reset button for 4 seconds until the beep, then choose **Reset network** to restore default IP (192.168.1.250).


# EVChargeKing


import { BrandName, ControllerName } from '@site/src/components/customFields';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

# EVChargeKing charging stations

<img
    src="/img/customers/EVChargeKing/logo.png"
    alt="EVChargeKing"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

## Supported Devices


<DeviceSupportTable
  devices={[
    { type: 'ETAPpro', modbusTcp: '✅', rs485: '❌' }
  ]}
  showModbusTcp={true}
  showRs485={false}
/>

## ETAP Pro Configuration
1. Download the E-Tap mobile app and create an account.
2. Scan the QR code on the E-Tap Pro device or card it comes with to add it in the app
3. During the setup, connect the EVChargeKing charging station to a network with the following requirements:
    - The charging station is in the same local network as the <BrandName /> <ControllerName />.
    - Make sure the communication between the charging station and the <BrandName /> <ControllerName /> is open.
4. Check that the device is connected to the internet in settings -> chargers -> select the charger -> Connection status. Either Wifi or Ethernet should be connected.
    <ClickableImage src="/img/customers/EVChargeKing/etap-mobile-app-network-page.png" alt="ETAP Mobile App Network Page" maxWidth="400px" />
5. Find the mac address of the device in settings -> chargers -> select the charger -> Information. This will be needed to add the device in the <BrandName /> <ControllerName />.
    <ClickableImage src="/img/customers/EVChargeKing/etap-mobile-app-info-page.png" alt="ETAP Mobile App Info Page" maxWidth="400px" />
6. The device should now be ready to be added in the <BrandName /> <ControllerName />.

# FLEXeCHARGE


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

# FLEXeCHARGE charging stations

<img
    src="/img/customers/flexecharge/flexecharge-logo.png"
    alt="FLEXeCHARGE"
    style={{ display: "block", margin: "0 auto", width: "40%" }}
/>

This guide will help installers set up the FLEXeCHARGE charging station, ensuring proper communication and integration with the <BrandName /> <ControllerName />. This guide covers common configurations, but **always refer to the official FLEXeCHARGE manuals** available at [FLEXeCHARGE Help Desk] for the most accurate and up-to-date instructions [[1]](https://support.flexecharge.com/hc/en-dk/categories/10364785688988-Manuals)[[2]](https://support.flexecharge.com/hc/en-dk).

## Supported Devices

<DeviceSupportTable
  devices={[
    {
      type: 'FLEXeCHARGE Controller with Metcom Meter',
      modbusTcp: '✅',
      rs485: '❌'
    }
  ]}
  showModbusTcp={true}
  showRs485={true}
/>

---

## Wiring

### Ethernet
For a proper Ethernet connection:
1.  Connect the FLEXeCHARGE controller to the local network via an Ethernet cable.
2.  Ensure TCP port **502** is open between the FLEXeCHARGE controller and the <BrandName /> <ControllerName />.
3.  Follow the [Ethernet wiring best practices](/Controller/wiring-best-practices/#ethernet).

---

## Configuration

**Step 1: Configure the FLEXeCHARGE Gateway**

1.  **Connect to the Gateway:** Connect your laptop directly to the Gateway via Ethernet.
2.  **Access the Gateway Interface:** Open a web browser and enter the Gateway's IP address.  The default IP address is likely `192.168.0.10` [[3]](https://support.flexecharge.com/hc/en-dk/articles/16573654926876-2-Configuration-Manual-for-Hybrid-Setup), but **verify this in the Gateway manual**.
3.  **Log In:** Log in to the Gateway interface. The default username and password are often `admin` [[3]](https://support.flexecharge.com/hc/en-dk/articles/16573654926876-2-Configuration-Manual-for-Hybrid-Setup), but **verify this in the Gateway manual and change it immediately for security reasons.**
4.  **Network Configuration:**
    *   Assign a fixed IP address to the Gateway [[3]](https://support.flexecharge.com/hc/en-dk/articles/16573654926876-2-Configuration-Manual-for-Hybrid-Setup). This IP address should be within the same subnet as your local network and the <BrandName /> <ControllerName />.
    *   Configure the Subnet Mask and Gateway address to match your network settings.
    *   Connect the Gateway to your local network router [[3]](https://support.flexecharge.com/hc/en-dk/articles/16573654926876-2-Configuration-Manual-for-Hybrid-Setup).
5.  **HARMON-E Registration:** Ensure the Gateway is registered with your HARMON-E account.  Follow the instructions in the FLEXeCHARGE manual for registering the Gateway [[3]](https://support.flexecharge.com/hc/en-dk/articles/16573654926876-2-Configuration-Manual-for-Hybrid-Setup).  You may need to contact FLEXeCHARGE support to link the power meter to your cloud site [[3]](https://support.flexecharge.com/hc/en-dk/articles/16573654926876-2-Configuration-Manual-for-Hybrid-Setup).

**Step 2: Configure the FLEXeCHARGE Charging Station**

1.  **Access the Charging Station Interface:** Once the Gateway is configured and connected to the internet, you should be able to access the charging station's configuration interface through the Gateway.  The exact method for accessing the charging station's interface will be detailed in the FLEXeCHARGE manual.
2.  **Enable Modbus TCP:** Navigate to the communication settings and enable Modbus TCP.
3.  **Modbus TCP Settings:**
    *   Set the IP address of the charging station. This IP address should be different from the Gateway's IP address but within the same subnet.
    *   Set the Modbus Unit ID (Modbus address). Choose a unique address between 1-247 that does not conflict with other Modbus devices on the network.
    *   Ensure the port is set to 502.

**Step 3: Configure the <BrandName /> <ControllerName />**

1.  In the <BrandName /> <ControllerName /> interface, add a new Modbus TCP device.
2.  Enter the IP address of the **charging station** (not the Gateway).
3.  Enter the Modbus Unit ID you configured in Step 2.
4.  Start the scan to confirm the connection.

### Setup without FLEXeCHARGE Gateway (Direct Connection)

If you are not using a FLEXeCHARGE Gateway, you may be able to connect the charging station directly to your network.

1.  **Connect to the Charging Station:** Connect your laptop to the charging station via Ethernet. You might need to set a static IP address on your laptop to be in the same subnet as the charging station's default IP address (check the manual).
2.  **Access the Charging Station Interface:** Open a web browser and enter the charging station's IP address (check the manual for the default IP address).
3.  **Log In:** Log in to the charging station interface (check the manual for the default username and password).
4.  **Configure Network Settings:** Assign a static IP address, subnet mask, and gateway address to the charging station.
5.  **Enable Modbus TCP and set the Modbus Unit ID as described in "Step 2: Configure the FLEXeCHARGE Charging Station" above.**
6.  **Configure the <BrandName /> <ControllerName /> as described in "Step 3: Configure the  <ControllerName />" above.**



# Go-e


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

# Go-e EV charger

<img
    src="/img/customers/go-e/logo.png"
    alt="Go-e"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>


## Supported Devices



<DeviceSupportTable
  devices={[
    { type: 'Go-e EV charger', modbusTcp: '✅', rs485: '❌' }
  ]}
  showModbusTcp={true}
  showRs485={true}
/>


## Configuration
1. In the go-e application, go to your device, then "Settings".

2. Go in the "Connection" tab.

<ClickableImage src="/img/customers/go-e/go-e-configuration1.png" alt="Image 1" maxWidth="200px" />

3. Go in the "API Settings" tab.

<ClickableImage src="/img/customers/go-e/go-e-configuration2.png" alt="Image 1" maxWidth="200px" />

4. Be sure that the "Allow local Modbus TCP API" and "Swap Registers" option are enabled.

<ClickableImage src="/img/customers/go-e/go-e-configuration3.png" alt="Image 1" maxWidth="200px" />

5. Then reboot your go-e.

<ClickableImage src="/img/customers/go-e/go-e-configuration4.png" alt="Image 1" maxWidth="200px" />
<ClickableImage src="/img/customers/go-e/go-e-configuration5.png" alt="Image 1" maxWidth="200px" />

# Huawei EV Chargers


import { BrandName, ControllerName } from '@site/src/components/customFields';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/customers/huawei/logo.png"
    alt="Huawei logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

# Huawei EV Chargers

Two Huawei product families are supported: the **SCharger** (AC wallbox) and the **FusionCharge** (commercial DC fast charger). Both communicate via Modbus TCP.

## Supported Devices

<DeviceSupportTable
  devices={[
    {
      type: "SCharger-7KS-S0",
      manual: "https://support.huawei.com/enterprise/en/doc/EDOC1100260967",
      modbusTcp: "✅",
      rs485: "❌",
      curtailment: "✅"
    },
    {
      type: "SCharger-22KT-S0",
      manual: "https://support.huawei.com/enterprise/en/doc/EDOC1100260967",
      modbusTcp: "✅",
      rs485: "❌",
      curtailment: "✅"
    },
    {
      type: "FusionCharge EV-charger",
      manual: "https://solar.huawei.com/admin/asset/v1/gray/view/6183827d5c314514ab0dd4d0f5c20941.pdf",
      modbusTcp: "✅",
      rs485: "❌",
    }
  ]}
  showManual={true}
  showModbusTcp={true}
  showRs485={true}
  showCurtailment={true}
/>

---

## SCharger

The SCharger is an AC wallbox for residential and light commercial use.

<ClickableImage src="/img/customers/huawei/huawei-wallbox.jpg" alt="Huawei SCharger Wallbox" maxWidth="300px" />

### Wiring

#### Power Wiring
* **SCharger-7KS-S0 (1-Phase):** L1, N, PE.
* **SCharger-22KT-S0 (3-Phase):** L1, L2, L3, N, PE.

#### Network Connection (FE/Ethernet)
For the most stable connection with the <ControllerName />, use a hardwired Ethernet (FE) connection.

1. Open the charger cover.
2. Route the network cable through the **left cable hole** at the bottom of the rear cover.
3. Connect the network cable to the **FE port** on the rear side of the internal unit.
4. Connect the other end to the same router/network switch as the <ControllerName />.

> [!NOTE]
> While the charger supports Wi-Fi, a wired Ethernet connection is strongly recommended for reliable control by the <ControllerName />.

### Configuration

#### 1. Initial Setup (via Huawei App)
Use the **FusionSolar App** (Installer account) to configure the network and Modbus settings.

1. Log in to the FusionSolar app as an **Installer**.
2. Tap **Setup Wizard** > Scan the QR code on the side of the charger.
3. Connect to the charger's internal WLAN hotspot (password is on the label).

#### 2. Enable Third-Party Control (Modbus TCP)
By default, the charger does not accept commands from external controllers. You must enable this:

1. In the FusionSolar app (connected to the device hotspot), go to **Settings**.
2. Navigate to **Communication configuration** > **Dongle parameter settings**.
3. Find **Modbus TCP**.
4. Set to **Enable (unrestricted)** or **Enable**.
5. Ensure the port is set to **502**.

> [!WARNING]
> If Modbus TCP is not enabled here, the <ControllerName /> cannot detect or control the charger.

#### 3. Static IP Address
To ensure the <ControllerName /> never loses connection, assign a static IP:

1. Go to **Quick Settings** > **Communication networking**.
2. Select **FE** (Fast Ethernet) if wired, or **WLAN** if wireless.
3. **Disable DHCP**.
4. Enter a static **IP Address**, **Subnet Mask**, and **Gateway** matching the site network.

#### 4. Eniris Controller Configuration

| Setting | Value |
| :--- | :--- |
| **IP Address** | The static IP you assigned in step 3 (e.g., `192.168.1.50`) |
| **Port** | `502` |
| **Slave ID** | `1` (default) |

---

## FusionCharge

The FusionCharge is a commercial DC fast charger with multiple physical connector slots.

### Configuration

#### Enable Modbus TCP

Access the antohill web interface or use antoeci cloud.

1. Navigate to **Settings** > **Communication configuration**.
2. Find **Modbus TCP** and set it to **Enable (unrestricted)** or **Enable**.
3. Confirm the port is set to **502**.

<img
    src="/img/customers/huawei/antoeco-config.png"
    alt="AntoEco configuration"
    style={{ display: "block", margin: "0 auto", width: "100%"}}
/>

<img
    src="/img/customers/huawei/antohill-config.png"
    alt="Antohill configuration"
    style={{ display: "block", width: "40%"}}
/>

> [!WARNING]
> If Modbus TCP is not enabled, the <ControllerName /> cannot detect or control the charger.

### Technical Notes

#### Multi-Connector Aggregation

The FusionCharge has multiple physical connector slots, but accepts a single global power setpoint. The <ControllerName /> therefore treats all connectors as one virtual connector for control, while still reading each one individually for monitoring:

- **Power** is summed across all active connectors.
- **Status** follows a priority hierarchy the most significant active state is reported.
- **State of Charge (SOC)** is averaged over all connected vehicles.


# Ilumen


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

# Ilumen charging stations

<img
    src="/img/customers/ilumen/ilumen-logo.png"
    alt="Ilumen"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>


## Supported Devices

<DeviceSupportTable
  devices={[
    { 
      type: 'Ilumen', 
      variants: '/',
      modbusTcp: '✅', 
      rs485: '❌'
    }
  ]}
  showVariants={true}
  showModbusTcp={true}
  showRs485={true}
/>



## Wiring

### Ethernet
For communication with Eniris (Modbus TCP) the Ilumen charging station must be connected to a local IP network.

- The charger must have a fixed/static IP address (recommended) or a DHCP reservation.
- The Eniris gateway must be able to reach the charger's IP address on TCP port 502.
- Use standard Ethernet cabling and switches; follow the general [Ethernet wiring guidelines](/Controller/wiring-best-practices/#ethernet).

> [!WARNING]
> Port 502 (Modbus TCP) is commonly used across the network. Ensure firewall rules allow TCP traffic between the Eniris gateway and the charger's IP on port 502. Do NOT expose port 502 to the public internet.

### RS485
Ilumen devices supported by this driver communicate over Modbus TCP only. RS485/Modbus RTU is not supported by the Ilumen driver described here.

<RS485ConnectionTable firstColumn={["Not applicable", "Not applicable", "Not applicable"]} />


## Configuration
Follow these steps to enable Modbus TCP communication between an Ilumen charging station and the Eniris gateway. The steps assume the charger is already powered and reachable on the local network.

1. Access the charge station network configuration:
   - Use the Ilumen configuration UI (web interface) or the vendor-provided configuration tool.
   - If the charger uses DHCP by default, set a static IP or reserve an IP in your DHCP server for the charger.

2. Network settings:
   - Set IP address within the same subnet as the Eniris gateway (for example: 192.168.1.50).
   - Set subnet mask and gateway consistent with your local network.
   - DNS is optional for Modbus TCP but may be required for firmware updates or vendor tools.

3. Modbus TCP server settings:
   - Enable Modbus communication and select "Modbus TCP/IP" as the communication mode.
   - Set the server port to 502 (the Eniris Modbus driver expects port 502).
   - Confirm the Modbus unit/slave ID (also called Device ID). Typical range: 1–247. Note this ID is required by the Eniris Modbus driver configuration.

> [!TIP]
> The Ilumen driver in Eniris expects Modbus slave IDs in the 1–247 range. Use a unique ID on the network to avoid collisions with other Modbus/TCP devices.

4. Ensure the device is reachable:
   - From the Eniris gateway, verify TCP connectivity: e.g., use telnet 502 or an equivalent network test.
   - If connectivity fails, check switch/router VLANs, firewall rules, and physical cabling.

5. Configure the Eniris gateway:
   - In Eniris device configuration, create a device entry with:
     - Protocol: "Ilumen EV Charger protocol V1"
     - Connection mode: Modbus TCP
     - IP address: the charger's static IP (or DNS name)
     - Port: 502
     - Modbus slave/unit ID: the configured Device ID on the charger
   - Optionally provide serial number and model in the driver parameters to help device identification.

6. Match communication parameters:
   - Modbus TCP: no serial line parameters required (baud/parity/stopbits do not apply).
   - Ensure the Eniris gateway's Modbus client is configured to use Modbus TCP framing.

7. Discovery and verification:
   - After adding the device in Eniris, run a device scan/discovery.
   - The driver validates the device by reading specific registers (e.g., voltage measurement registers). Successful reads confirm the charger is online.
   - In Eniris logs you should see the charger appear with a nodeId like: SGW-Ilumen-EVC-.



# Ev Charging Station


import { FolderOverview } from '@/components/FolderOverview';

# Ev Charging Station

<FolderOverview folder="Controller/Devices/EV-charging-station" />


# Kempower


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

# Kempower Charging Stations

<img
    src="/img/customers/kempower/logo.png"
    alt="Kempower"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

## Supported Devices

<DeviceSupportTable
    devices={[
      { type: 'Kempower Charger', variants: 'All models supporting Modbus TCP Interface', modbusTcp: '✅', rs485: '❌' }
    ]}
    showVariants={true}
    showModbusTcp={true}
    showRs485={true}
/>


## Configuration and Interface Details

The Kempower Charging Station uses Modbus TCP as the communication basis.

To ensure communication with the <BrandName /> <ControllerName />, note the following:

1.  **Connection Requirements:** Connections are only allowed from the same subnet the charging station is connected to.
2.  **Modbus Port:** The standard Modbus Port used is **502**.
3.  **Maximum Connections:** The maximum number of simultaneous connections is **10**.

### Power Limit Management

The Kempower Charging Station accepts power limit control *only* via the Modbus TCP interface when Modbus messages are detected.

* **OCPP Conflict:** OCPP power limitation messages are not accepted when Modbus is used.
* **Fallback Power:** The maximum power used when communication times out reverts to the **Fallback Power (W)** setting. This power is also used at startup until the **Assigned Maximum Power** has been received.
* **Minimum Power:** Any power limit values below 1000W are interpreted as 0W, which effectively stops charging.


# Amtron


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

# Mennekes 

<img
    src="/img/customers/Mennekes/Mennekes.png"
    alt="Go-e"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>


## Supported Devices



<DeviceSupportTable
  devices={[
    { type: 'Amtron EV charger', modbusTcp: '✅', rs485: '✅' }
  ]}
  showModbusTcp={true}
  showRs485={true}
/>


## Configuration
1. In the application, go to your device, then "Settings".

2. Go in the "Connection" tab to enable Modbus TCP, and set the Modbus TCP server to **"Read and Write"** mode (HEMS Read and Write). In "Read only" mode the <ControllerName/> can read the charger's data but cannot control its charging current.

3. Give the charger a fixed IP address in the same network as the <ControllerName/>.


# MyEnergi EV Charging Stations


import { BrandName, ControllerName } from '@site/src/components/customFields';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/sgo/Logo_MyEnergi.png"
    alt="MyEnergi"
    style={{ display: "block", margin: "50px auto", width: "40%" }}
/>

# MyEnergi EV Charging Stations

## Supported Devices


<DeviceSupportTable
  devices={[
    { type: 'Zappi', api: '✅', modbusTcp: '❌', rs485: '❌' }
  ]}
  showApi={true}
  showModbusTcp={true}
  showRs485={true}
/>

> [!WARNING]
>
> Control is not possible! Only monitoring is supported.
>

## Connection

The communication between the <BrandName /> <ControllerName /> and the Zappi EV Chargers operates via API.

### API

You need an API key to connect the Zappi EV Charger to the <BrandName /> <ControllerName />. To generate an API key, follow these steps:
    1. Log in to the MyEnergi portal.
    2. Go to the "Products" tab.
    3. Under your Gateway or Zappi click "Advanced"
    4. Click "Generate new API key"

<ClickableImage src="/img/customers/myenergi/advanced.jpg" alt="Zappi Settings" maxWidth="500px" />

# NexBlue


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

# NexBlue

<img
    src="/img/customers/nexblue/Logo_Nexblue.png"
    alt="NexBlue"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

<img
    src="/img/customers/nexblue/Nexblue_Charger.png"
    alt="NexBlueCharger"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

## Supported Devices



<DeviceSupportTable
  devices={[{ type: 'Edge 2', modbusTcp: '✅', rs485: '❌' },
    { type: 'Edge Max', modbusTcp: '✅', rs485: '❌' },
    { type: 'Delta', modbusTcp: '✅', rs485: '❌' },
    { type: 'Delta Max', modbusTcp: '✅', rs485: '❌' }
  ]}
  showModbusTcp={true}
  showRs485={true}
/>


## Wiring

### Ethernet connection
1. Connect the **Ethernet (LAN)** port of the charging station to the same local network as the <BrandName /> <ControllerName />.  
2. Make sure the LAN connection is live and the LEDs on the port are on.  
3. Recommended network cable: **Cat 5e or higher**, shielded for outdoor use if needed.

For general Ethernet wiring best practices, see the [Ethernet wiring guidelines](/Controller/wiring-best-practices/#ethernet).


# OCPP


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

# Charging stations with OCPP support

<img
    src="/img/customers/ocpp/logo.png"
    alt="Alpitronic"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>


## Supported Devices
> [!WARNING]
> OCPP is only supported on chargers that do not need to be connected to a mobility service provider backend. This by definition excludes all public charging stations.


<DeviceSupportTable
  devices={[
    { 
      type: 'Most charging stations with support for OCPP v1.6 and the smart charging OCPP profile. Consult the manufacturer.', 
      modbusTcp: '✅', 
      rs485: '❌' 
    }
  ]}
  showModbusTcp={true}
  showRs485={true}
/>

> [!WARNING]
> The OCPP enabled charger must allow setting a local IP address as the OCPP backend. Consult the charger manufacturer in case of doubt.


## Configuration

OCPP is enabled by default on the <BrandName /> <ControllerName /> on TCP port 9000.

> [!WARNING]
> The controller must be configured to have a fixed IP address in your network to enable OCPP. This is because the <BrandName /> <ControllerName /> acts as an OCPP server, and the IP adress must be configured in your charger. See [Network](/Controller/network-configuration/) on how to set up a fixed IP address.

In the charger's settings, go the OCPP settings and follow these steps: 
1. Enable OCPP on the charger.
2. Set the address to: **ws://[<BrandName /> <ControllerName /> IP address]:9000**. 
3. Check that the OCPP version is set to version **1.6J** if the option is present.

It is recommended to wait a minute or two for the charger to connect to the <BrandName /> <ControllerName /> before adding it as a device in the commissioning interface.

# Peblar EV Charging Stations


import { BrandName, ControllerName } from '@site/src/components/customFields';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/customers/peblar/peblarlogo.png"
    alt="Peblar"
    style={{ display: "block", margin: "50px auto", width: "40%" }}
/>

# Peblar EV Charging Stations

## Supported Devices


<DeviceSupportTable
  devices={[
    { type: 'Peblar Home', modbusTcp: '✅', rs485: '❌' },
    { type: 'Peblar Home Plus', modbusTcp: '✅', rs485: '❌' },
    { type: 'Peblar Business', modbusTcp: '✅', rs485: '❌' }
  ]}
  showModbusTcp={true}
  showRs485={true}
/>

## Connection

The communication between the <BrandName /> <ControllerName /> and the Peblar EV Chargers operates via Modbus TCP.

### Settings

<ClickableImage src="/img/customers/peblar/api_enable.png" alt="Peblar Settings" maxWidth="500px" />

The Peblar EV Chargers need to have modbus enabled:
    1. Open the chargers web interface
    2. Navigate to "Settings" -> "Advanced"
    3. Enable "Modbus API"
    4. Set the "Access mode" to "Read & write"


# Raedian


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

# Raedian charging stations

<img
    src="/img/sgo/Logo_Raedian.png"
    alt="Raedian"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

## Supported Devices

<DeviceSupportTable
  devices={[
    { 
      type: 'Raedian NEO', 
      modbusTcp: '❌', 
      rs485: '✅' 
    },
    { 
      type: 'Raedian NEX', 
      modbusTcp: '✅', 
      rs485: '❌' 
    }
  ]}
  showModbusTcp={true}
  showRs485={true}
/>

<ClickableImage src="/img/customers/Raedian/wallbox.png" alt="Raedian Charger" maxWidth="450px" />

## Wiring

### Ethernet (Raedian NEX)
For correct ethernet wiring: Follow the [the guidelines for ethernet wiring](/Controller/wiring-best-practices/#ethernet).

### RS485 (Raedian NEO)
<RS485ConnectionTable firstColumn={["A", "B", "GND"]} />

> [!NOTE]
> Ensure the termination resistor is set correctly if the charger is at the end of the RS485 bus.

## Configuration

After the electrical installation is complete, you need to configure the charger using the **Raedian App**.

1. Download the **Raedian** app from the App Store or Google Play Store.
2. Open the app and register/login.
3. Add the charging station via Bluetooth/Wi-Fi following the in-app instructions.
4. Once connected, navigate to the **Settings** menu (usually represented by a gear icon).

### For Raedian NEO (RS485)

To allow the <BrandName /> <ControllerName /> to control the NEO charger via Modbus RTU:

1. In the settings menu, look for **Communication** or **Modbus Settings**.
2. Enable **Modbus RTU**.
3. Configure the following parameters:
    * **Address (Slave ID):** Set a unique address (e.g., 1). This must match the configuration in the <BrandName /> <ControllerName />.
    * **Baud Rate:** 9600 (Recommended)
    * **Parity:** None
    * **Data Bits:** 8
    * **Stop Bits:** 1
4. Save the settings and reboot the charger if prompted.


### For Raedian NEX (Modbus TCP)

To allow the <BrandName /> <ControllerName /> to control the NEX charger via Modbus TCP:

1. Ensure the charger is connected to the same local network as the <BrandName /> <ControllerName /> via Ethernet or Wi-Fi.
2. In the app settings, go to **Network Settings**.
3. It is highly recommended to assign a **Static IP** to the charger to ensure connectivity remains stable after power outages.
    * **IP Address:** Choose a free IP in your network range (e.g., 192.168.1.50)
    * **Subnet Mask:** 255.255.255.0
    * **Gateway:** Your router IP (e.g., 192.168.1.1)
4. Enable **Modbus TCP** in the Communication settings.
5. Ensure the **Port** is set to `502`.


# Schneider Electric


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

# Schneider Electric charging stations

<img
  src="/img/customers/schneider-electric/logo.png"
  alt="Schneider Electric"
  style={{ display: "block", margin: "0 auto", width: "40%"}}
/>


## Supported Devices

<DeviceSupportTable
  devices={[
    { 
      type: 'EVlink Pro AC', 
      variants: 'GEX Series',
      modbusTcp: '✅', 
      rs485: '❌'
    },
    {
      type: 'Schneider Charge Pro',
      variants: 'NAT Series',
      modbusTcp: '✅', 
      rs485: '❌'
    }
  ]}
  showVariants={true}
  showModbusTcp={true}
  showRs485={true}
/>

<ClickableImage src="/img/customers/schneider-electric/evlink-pro-ac.jpg" alt="Schneider EVlink" maxWidth="350px" style={{display: "inline-block"}}/>
<ClickableImage src="/api/media/editor-uploads/Controller/Devices/EV-charging-station/Schneider/schneider-charge-pro.png" alt="schneider charge pro" maxWidth="350px" style={{display: "inline-block"}}/>

## Connection

The communication between the <BrandName /> <ControllerName /> and the Schneider charging station takes place via **Modbus TCP**.

1. Connect the charging station to the same local network (LAN) as the <ControllerName /> using an Ethernet cable.
2. For correct ethernet wiring standards, follow the [guidelines for ethernet wiring](/Controller/wiring-best-practices/#ethernet).

## Configuration

To allow the <BrandName /> <ControllerName /> to control the station, you must enable Modbus TCP via the **eSetup for Electrician** app or the charger's web interface.

1. Log in to the charger using the **eSetup** app.
2. Go to the **Network** settings and assign a **Static IP address** to the charger. This ensures the <ControllerName /> can always find it.
3. Go to **Communication** (or Backend) settings.
4. Set **Modbus TCP** to **Enable**.
5. Ensure the Port is set to **502**.
6. Save the settings and reboot the charger if prompted.

> [!WARNING]
> Make sure the Modbus Slave ID is set to **1** (or between 1 and 247). The default address is usually 1 or 255.

### Adding to the Controller

1. Go to the <BrandName /> <ControllerName /> web interface.
2. Navigate to **Devices** > **Add Device**.
3. Select **Schneider** > **Modbus TCP**.
4. Enter the **IP Address** you configured in the charger.
5. Enter Port **502**.
6. Click **Scan**.

# Siemens



# SMA


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

# SMA EV Business Charger

<img
    src="/img/customers/sma/logo.png"
    alt="Alpitronic"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>


## Supported Devices



<DeviceSupportTable
  devices={[
    { type: 'SMA EV Business Charger', modbusTcp: '✅', rs485: '❌' }
  ]}
  showModbusTcp={true}
  showRs485={true}
/>

<ClickableImage src="/img/customers/sma/ev-business-charger.png" alt="Image 1" maxWidth="450px" />


## Configuration
1. Connect to your computer in the same LAN network as the charging station, and surf to the charging station's IP address.
2. Log into the charging station's local web interface (default login "operator", password "service.kraft"), and go to the "Load Management" tab.
3. Fill this out exactly as shown in the image on the below and click save.

> [!WARNING] Please note:
> - Different configurations from the indicated image have not been tested.
> - In all cases, you must turn on the Modbus TCP server, leave the base port at 502 and set the register address group to TQ-DM100.
> - If you activate SEMP interface, EEBUS, Dynamic Load Management or ASKI via OCPP-S, it may interfere with the control of the <ControllerName />. It is strongly discouraged to activate these functions.

<ClickableImage src="/img/customers/sma/ev-business-charger-config_pt1.png" alt="Image 1" maxWidth="650px" />

# Smappee


import { ControllerName } from '@site/src/components/customFields';
import ClickableImage from '@site/src/components/ClickableImage';

# Smappee EV chargers

<ClickableImage src="/img/customers/smappee/logo.png" alt="Smappee" maxWidth="300px" />

The <ControllerName /> connects to the Smappee Flex (Genius II) on the local network. This gateway exposes the connected EV chargers through its local MQTT broker. The controller reads charging states and energy measurements and sends charging commands through that connection.

> [!IMPORTANT]
> Keep the default TCP port `443` for this connection. The Smappee EV integration uses MQTT over TLS on this port, not the generic MQTT TLS port `8883`.

## Connection settings

| Wizard setting | What to enter |
| --- | --- |
| Gateway address | Local IP address of the Smappee Flex (Genius II). |
| Communication protocol | `MQTT over TLS` |
| TCP connection port | `443` |
| MQTT username and password | Credentials generated for Local MQTT in Smappee. |
| Charger UUID | Optional. Leave blank to discover chargers communicating with this gateway. |

<ClickableImage src="/img/customers/smappee/smappee-infinity-modularity.jpg" alt="Smappee gateway and connected components" maxWidth="550px" />

## Enable Local MQTT in Smappee

1. Make sure the Flex (Genius II) is activated at the location in Smappee.
2. Open the Smappee mobile app and go to `Control → Smappee Store`.
3. Choose `Manage`, find the `MQTT` app and select `Install Integration`.
4. Generate and retain the local MQTT username and password.

<ClickableImage src="/img/customers/smappee/mqtt-steps.png" alt="Enabling the local MQTT integration in Smappee" maxWidth="550px" />

These are credentials for the local Smappee gateway, generated in Smappee. They are not credentials for the Eniris MQTT broker. A separate connection to the Eniris broker uses credentials requested through the [Eniris webshop](https://webshop.eniris.com/).

## Add the chargers

1. Connect the controller and the Smappee gateway to the same local network. Allow the controller to reach the gateway on TCP port `443`.
2. In the device wizard, choose `EV charging station → Smappee`.
3. Enter the gateway's local IP address and local MQTT credentials. Keep port `443`.
4. Leave `Charger UUID` blank to discover chargers exposed by that gateway, or enter a specific UUID from `Local MQTT` in the Smappee Expert Portal.
5. Run discovery, add the required chargers and check their charging state and measurements.

If a UUID copied from the mobile app does not find the expected charger, leave the field empty and run discovery again. The charger must be communicating with the gateway's MQTT broker to be discovered.

## Multiple connectors and charging states

A single gateway can expose multiple connectors. Each connector appears as a separate child device and can be controlled independently while sharing the gateway connection.

| Charging state | Meaning |
| --- | --- |
| No vehicle connected | No vehicle is plugged in. |
| Vehicle connected | A vehicle is plugged in but is not charging. |
| Charging | The charging session is active. |
| Paused | The session is paused. |
| Session ended | The charging session has finished. |
| Unavailable | The connector is unavailable. |
| Error | The charger reports a fault. |
| Booting | The charger is starting up. |

## If the connection fails

- Verify the gateway's local IP address and TCP port `443`.
- Check that Local MQTT is enabled and that you used its generated credentials.
- Check whether local MQTT access was revoked in Smappee.
- For an empty discovery result, check the gateway connection and try without a charger UUID.


# Sofar


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

# Sofar charging stations

<img
    src="/img/customers/sofar/sofar-logo.png"
    alt="Sofar"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>


This guide will serve as a guide to adjust the Sofar charging station settings to allow communication with and control by the <BrandName /> <ControllerName />.


## Supported Devices


<DeviceSupportTable
  devices={[
    { type: 'Sofar EV11k-AC-02', modbusTcp: '✅', rs485: '✅' }
  ]}
  showModbusTcp={true}
  showRs485={true}
/>

Note that, for access via Modbus TCP, an external converter is required. For more information you can check our [supported accessories.](/Controller/Accessories/rs485-ethernet)


# Teltonika EV Charging Stations


import { BrandName, ControllerName } from '@site/src/components/customFields';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import RS485AddressNote from '@site/src/components/RS485AddressNote';

<img
    src="/img/customers/teltonika/Logo_Teltonika.png"
    alt="Teltonika"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>


# Teltonika EV Charging Stations

## Supported Devices


<DeviceSupportTable
  devices={[
    { type: 'TeltoCharge', variants: '7.4kW/11kW/22kW', modbusTcp: '✅*', rs485: '✅',
  instructionVideos: [{"videoId": "Qu61gm5mRD8", "title": "Teltonika EVC2 with fixed charging cable", "description": "EVC2 fixed-cable version. Use the Load management settings shown for this hardware generation."}, {"videoId": "NKIS6qYPSNE", "title": "Teltonika EVC2 with Type 2 socket", "description": "EVC2 Type 2 socket version. Use the Load management settings shown for this hardware generation."}]
}
  ]}
  showVariants={true}
  showModbusTcp={true}
  showRs485={true}
/>

> [!WARNING]
> TCP is only available for version EVC2 or newer generation EV chargers.

## Connection

<ClickableImage src="/img/customers/teltonika/wiring.png" alt="TeltoCharge Wiring" maxWidth="350px" />

The communication between the <BrandName /> <ControllerName /> and the TeltoCharge operates via an RS-485 serial bus or Modbus TCP.


<RS485ConnectionTable firstColumn={["RS485 A", "RS485 B", "GND"]} />

<RS485AddressNote />


### Settings

Follow the steps below to enable Modbus on the TeltoCharge:

- Open the device settings in the Teltonika app.
<ClickableImage src="/img/customers/teltonika/teltocharge_app_home.jpeg" alt="TeltoCharge Wiring" maxWidth="350px" />

- Open the Installer Menu, you will need to input the installer code to access this menu.
<ClickableImage src="/img/customers/teltonika/teltocharge_app_settings.jpeg" alt="TeltoCharge Wiring" maxWidth="350px" />

- Open the Load management menu.
<ClickableImage src="/img/customers/teltonika/teltocharge_app_installer_menu.jpeg" alt="TeltoCharge Wiring" maxWidth="350px" />

- Select the Modbus RTU option. You will need to disable other communication options to enable Modbus RTU.
<ClickableImage src="/img/customers/teltonika/teltocharge_app_load_management.jpeg" alt="TeltoCharge Wiring" maxWidth="350px" />

- Select "Secondary device" mode, and enable it. You can also set the Modbus address and other advanced settings in this menu, but the default settings should work fine.
<ClickableImage src="/img/customers/teltonika/teltocharge_app_secondary_device_settings.jpeg" alt="TeltoCharge Wiring" maxWidth="350px" />

- The <BrandName /> <ControllerName /> will now be able to communicate with the TeltoCharge via Modbus RTU. You can check the connection status in the app.
<ClickableImage src="/img/customers/teltonika/teltocharge_app_status.jpeg" alt="TeltoCharge Wiring" maxWidth="350px" />

## Older Models

The TeltoCharge needs to have modbus enabled:
    1. Open the Teltonika app
    2. Navigate to "Settings" -> "Installer Menu"
    3. Enable "Dynamic Load Balancing"
    4. After doing this "Dynamic Load Management" will become visible
    5. Scroll down and enable "Dynamic Load Management"
    6. Click "Save"
    7. The TeltoCharge will now reboot and modbus will be enabled


# Triathlon


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

# Triathlon charging stations

<img
    src="/img/customers/triathlon/Logo_Triathlon.png"
    alt="Triathlon"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>


## Supported Devices


<DeviceSupportTable
  devices={[
    { type: 'Triathlon MDLoadmanagement', modbusTcp: '✅', rs485: '❌' }
  ]}
  showModbusTcp={true}
  showRs485={true}
/>

## Configuration

> [!IMPORTANT]
> Make sure that the battery and the <BrandName /> <ControllerName /> are connected to the same network /subnetwork.


# Veton


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

# Veton charging stations

<img
    src="/img/customers/veton/logo.png"
    alt="Veton"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

## Supported Devices

<DeviceSupportTable
  devices={[
    { 
      type: 'ONE', 
      modbusTcp: '✅', 
      rs485: '❌'
    },
    { 
      type: 'TWO', 
      modbusTcp: '✅', 
      rs485: '❌'
    },
    { 
      type: 'Wall', 
      modbusTcp: '✅', 
      rs485: '❌'
    },
    { 
      type: 'Wall+', 
      modbusTcp: '✅', 
      rs485: '❌'
    },
  ]}
  showModbusTcp={true}
  showRs485={true}
/>

## Access to the web interface
### Accessing the Veton Station web interface

> [!NOTE] After starting up the charging station, the webpage becomes accessible after about 8 minutes.
To access the platform, there are 2 different options:

Via Internet connection (see image next to this)

1. You must connect the ETH0 port via a router to access the Master BPS from your PC if it is connected to the same router.

2. Browse to: http://ev3000.local:3000.

3. The webpage opens and you can start the configuration.

4. We recommend assigning a static IP address to the charging station via the network settings now. Note: if the Veton webpage does not open, follow this step.
> [!NOTE]
> If the Veton webpage does not open, follow these steps: 

1. Make sure the PC you are connecting with is set to DHCP (automatic IP address assignment) in the internet settings. You can check this via network connections:



<ClickableImage src="/img/customers/Blitz-power/BlitzCompleteRoute.png" alt="blitz-power" maxWidth="450px" />


## Configuration via Modbus modbusTcp

1. Click on Load Management in the menu bar.

2. Enter a custom name under Charging Park Name.

3. Set the maximum current value of the fuse protecting the charging park under Load Circuit Fuse.

4. For High Level Measuring, choose the communication protocol. • IP Address

5. Enter the (IP) address of the energy meter from the electrical cabinet.

6. Device type is EEM377 (if the meter is supplied by Veton).

7. Under Charging Points, select the charging points that should participate in Load Management.

8. Click Save: Success appears on the screen.

9. Perform a restart of the charging station.

> [!WARNING]
>  Dynamic Load Management only works if the facilities for the charging station are tapped directly from the main fuse.

<ClickableImage src="/img/customers/Blitz-power/BlitzLoadManagement.png" alt="blitz-power-LoadManagement" />

## Configuration via RS485

Dynamic load management (WITH energy meter)

1. Click on Load Management in the menu bar.

2. Enter a custom name under Charging Park Name.

3. Set the maximum current value of the main fuse protecting the entire site under Load Circuit Fuse.

4. For High Level Measuring, choose the communication protocol. • RS 485 (modbus)

5. Select the name of the master charging station (position 1).

6. Under Charging Points, select the charging points that should participate in Load Management.

7. Click Save: Success appears on the screen.

8. Perform a restart of the charging station.

> [!WARNING]
>  Dynamic Load Management only works if the facilities for the charging station are tapped directly from the main fuse.


# Volt-Time



import { BrandName, ControllerName } from '@site/src/components/customFields';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/sgo/Logo_Volt Time.png"
    alt="logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>


## Supported Devices

<DeviceSupportTable
  devices={[
    {
      type: "Volt Time Source",
      modbusTcp: '✅',
      rs485: '❌',
    },
    {
      type: "Volt Time Source 2",
      modbusTcp: '✅',
      rs485: '❌',
    },
    {
      type: "OCPP EV Chargers via Volt Time Cloud",
      api: '✅', 
    },
  ]}
  showApi={true}
  showModbusTcp ={true}
  showRs485 ={false}
/>


# Vool

import { BrandName, ControllerName } from '@site/src/components/customFields';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

# Vool EV Charger

<img
    src="/img/customers/vool/Logo_Vool.png"
    alt="Vool"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

## Supported Devices

<DeviceSupportTable
  devices={[
    { type: 'Vool EV Charger', modbusTcp: '✅'}
  ]}
  showModbusTcp={true}
/>

## Configuration

1. Connect your computer to the same LAN network as the Vool charger.
2. Access the charger's configuration interface and enable parameter **522 – Enable Modbus TCP/UDP interface**. By default, Modbus is disabled on the charger.
3. Ensure the charger is reachable on port **502** (TCP).

> [!WARNING] Please note:
> - Modbus and OCPP cannot be used simultaneously. The charger uses one common interface at a time — hybrid connections (e.g. Modbus on Wi-Fi and OCPP on Ethernet) are not supported.
> - The Modbus interface does not include any security. Only use Modbus in local, secure networks.
> - The charger supports a maximum of **3 simultaneous Modbus connections**. Additional connection attempts will be rejected.

<img
    src="/img/customers/vool/vool_charger.jpg"
    alt="Vool charger"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>


# Wallbox EV Charging Stations


import { BrandName, ControllerName } from '@site/src/components/customFields';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/customers/wallbox/Logo_Wallbox.png"
    alt="Wallbox"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>


# Wallbox EV Charging Stations

## Supported Devices

<DeviceSupportTable
  devices={[
    { type: 'Pulsar', variants: 'Plus/Max/Pro', modbusTcp: '❌', rs485: '❌', api: '✅' },
    { type: 'eM4', variants: 'All', modbusTcp: '❌', rs485: '❌', api: '✅' },
    { type: 'Quasar 2', variants: 'All', modbusTcp: '❌', rs485: '❌', api: '✅' },
    { type: 'Commander', variants: 'All', modbusTcp: '❌', rs485: '❌', api: '✅' },
    { type: 'Copper SB', variants: 'All', modbusTcp: '❌', rs485: '❌', api: '✅' },
    { type: 'Supernova', variants: 'All', modbusTcp: '✅', rs485: '❌', api: '❌' }
  ]}
  showVariants={true}
  showApi={true}
  showModbusTcp={true}
  showRs485={true}
/>

## Connection

The communication between the <BrandName /> <ControllerName /> and the Wallbox EV Charging Stations is established through API and Modbus TCP. No physical cables are required to the <BrandName /> <ControllerName />.

## Settings

### Pulsar | eM4 | Quasar 2

No additional settings have to be made on the Wallbox side.

### Supernova

<img 
    src="/img/customers/wallbox/supernova.png" 
    alt="Supernova Settings" 
    style={{ float: 'right', marginLeft: '1rem', maxWidth: '500px' }}
/>

    1. Open the WebManager of the Supernova
    2. Go to "Configuration" > "Modbus TCP"
    3. Set the "Power Management Mode" to "Current"
    4. Set a static IP address for the Supernova
    5. Set the "Port" to "502"
    6. Save the settings


# Zaptec


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';
import YouTubeEmbed from '@/components/YouTubeEmbed'

<img
    src="/img/customers/zaptec/logo.png"
    alt="logo"
    style={{ display: "block", margin: "0 auto", width: "40%" }}
/>

# Zaptec EV Charging Stations

## Supported Devices

<div
  style={{
    display: "flex",
    justifyContent: "center",
    alignItems: "flex-start",
    gap: "20px",
    flexWrap: "wrap",
    margin: "20px 0"
  }}
>
  <ClickableImage src="/img/controller/devices/ev-charging-station/zaptec/Zaptec_Go-2_Front_AsphaltBlack.png" alt="Zaptec Go" maxWidth="350px" />

  <ClickableImage src="/img/controller/devices/ev-charging-station/zaptec/Zaptec_Pro_with_AFIR-1.png" alt="Zaptec Pro" maxWidth="350px" />
</div>

<DeviceSupportTable
  devices={[
    { type: 'Zaptec Go', modbusTcp: '❌', rs485: '❌', api: '✅' },
    { type: 'Zaptec Go 2', modbusTcp: '❌', rs485: '❌', api: '✅' },
    { type: 'Zaptec Pro', modbusTcp: '❌', rs485: '❌', api: '✅' }
  ]}
  showApi={true}
  showModbusTcp={true}
  showRs485={true}
/>

## Connection

The communication between the <BrandName /> <ControllerName /> and the charging stations is established through API. Make sure the charging stations have a functioning internet connection.

## Configuration

Make sure the charging station is connected to the Internet and Zaptec's portal. When you add the charging station to the controller, you will be prompted for your portal login to add your station. Have this information ready ahead of time.

No additional communication wiring between the controller and the charging stations is required. Configure the charging mode and available current in the Zaptec portal before using SmartgridOne to manage charging.

### Configure the Zaptec portal

1. Open the relevant installation in the Zaptec portal and go to **Settings > Power management** (the **Charging mode / Laadmodus** section).
2. Select **Standard charging** (**Standaard laden**) for this SmartgridOne integration. Do not leave **Automatic charging** (**Automatisch opladen**) active alongside SmartgridOne's control: Zaptec's own power management can otherwise restrict charging.
3. Set **Available current** (**Beschikbare stroom**) for **phase 1, phase 2 and phase 3** to the current the charging installation is allowed to use, then save. Choose values high enough for the intended charging capacity, within the site's electrical limits. These are limits for the charging installation per phase, not a separate allowance for each charging point.

SmartgridOne adjusts the maximum charging current for each charging point according to the available capacity at the site. The available-current settings in Zaptec remain an additional ceiling: a higher current allowance from SmartgridOne cannot override a lower limit in Zaptec.

**Choose a safe current limit.** Account for the main fuse, charging circuits, cabling and other building loads. Do not rely on active EMS control alone when choosing this ceiling: the installation must remain safe if EMS communication stops. There is no single current value suitable for every site.

### If charging power remains too low

Check the charging mode and all three available-current values in Zaptec first. Then compare SmartgridOne's permitted current with the actual charging current. The vehicle, cable and number of phases in use can also limit charging power.

## How to install Zaptec

<YouTubeEmbed title="How to Install Zaptec Go (2) with SmartgridOne (Step-by-Step)" videoId="MiRmneBsSZ8" />



## More installation information about Zaptec

Zaptec Go & Zaptec Go 2: [https://help.zaptec.com/installation/how-to-install-zaptec-go-and-zaptec-go-2](https://help.zaptec.com/installation/how-to-install-zaptec-go-and-zaptec-go-2)

Zaptec Pro: [https://help.zaptec.com/installation/how-to-install-zaptec-pro](https://help.zaptec.com/installation/how-to-install-zaptec-pro)

# Xargeon / ZhongDe Energy


import { BrandName, ControllerName } from '@site/src/components/customFields';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';
import Details from '@theme/Details';
import ClickableImage from '@site/src/components/ClickableImage';

<img
    src="/img/sgo/Logo_Xargeon.png"
    alt="Xargeon"
    style={{ display: "inline", margin: "0 auto", width: "40%"}}
/>

<img
    src="/img/sgo/Logo_ZDK.png"
    alt="Xargeon"
    style={{ display: "inline", margin: "0 auto", width: "40%"}}
/>

# Xargeon / ZhongDe Energy
The <BrandName /> <ControllerName /> supports two versions of the booster product
line. The booster is a DC-fast charger with a built-in battery. Typically the battery is used to support the grid
when charging an EV at high power, but it can be used for other purposes.
<img
    src="/img/customers/zdk/1.jpeg"
    alt="booster"
    style={{ display: "block", margin: "0 auto", width: "20%"}}
/>
## Supported Devices

<DeviceSupportTable
  devices={[
    { type: 'Xargeon Booster generation 1', modbusTcp: '✅', rs485: '❌', api: '❌' },
    { type: 'Xargeon Booster generation 2', modbusTcp: '✅', rs485: '❌', api: '❌' },
  ]}
  showModbusTcp={true}
  showRs485={true}
/>

## Setup
> [!DANGER]
> ### Safety warning: risk of electrocution
> Disconnect power before performing the steps below. When the back panel is opened, it exposes a high voltage 800v DC bus.

__Prerequisites:__
The system should be physically installed and connected to the power using the installation manual.
The guide below only covers the installation if the communication with the network and with the <BrandName /> <ControllerName />.

__Step 1:__
The communication between the <BrandName /> <ControllerName /> and the Xargeon Booster is established through Modbus TCP.
Shutdown the power and open the back panel of the booster. Focus on the marked part in the picture:

<ClickableImage src="/img/customers/zdk/2.jpeg" alt="Step 2" maxWidth="250px" />
__Step 2:__
Use two ethernet cables to connect:
- Yellow: The interface for Modbus TCP. This cable can be connected to a network switch that is in the same subnet as the <BrandName /> <ControllerName />.a
- Orange: The interface for internet. This is, among other things, used for the payment interface.
<ClickableImage src="/img/customers/zdk/3_ann.jpeg" alt="Step 3" maxWidth="400px" />

__Step 3:__
Only for commissioning: Connect your computer with a LAN cable directly to the diagnostic interface of the Booster. This is the interface marked
in purple in the image above. After commissioning, you do not need this interface anymore.

__Step 4:__
Open the network settings on you computer, and manually assign IP address 192.168.1.101:
<ClickableImage src="/img/customers/zdk/4a.png" alt="Step 3" maxWidth="550px" />

__Step 5:__
Open the browser and go to <a href="https://192.168.1.1/" target="_blank" rel="noopener noreferrer">https://192.168.1.1/</a>.
Proceed trough security dialogs if the browser warns about an insecure page.

The default username is `default_admin` and the default password is `Default_Admin22!` (pay attention to the capital letters).

<ClickableImage src="/img/customers/zdk/4b.png" alt="Step 3" maxWidth="450px" />

__Step 6:__
In the sidebar, select 'Online configuration', and scroll down on the page. Adjust your settings to the marked areas in the image below:
<ClickableImage src="/img/customers/zdk/6.png" alt="Step 3" maxWidth="550px" />

__Step 7:__
In this step, we need to upload a setting file to enable remote control.

IMPORTANT: This setting file __must__ be provided by Xargeon.
<BrandName />, nor yourself can create this setting file as it the file is only accepted if it is electronically signed by Xargeon.
<ClickableImage src="/img/customers/zdk/7.png" alt="Step 3" maxWidth="550px" />

__Step 8:__
Check the firewall settings. You have two options here:
1. Disable the firewall entirely. This is the easiest option but should only be used in secure environments.
2. Enable the firewall, and create a whitelist entry for the <BrandName /> <ControllerName /> on port 502. You need to use the <BrandName /> <ControllerName /> IP-address here.
<ClickableImage src="/img/customers/zdk/8.png" alt="Step 3" maxWidth="550px" />

__Completed:__ The system is now prepared for a connection with the <BrandName /> <ControllerName />. Proceed in
the <BrandName /> <ControllerName /> interface find the device in the wizard.
{/* <img */}
{/*     src="/img/customers/zdk/3_ann.jpeg" */}
{/*     alt="Step 3" */}
{/*     style={{ display: "block", margin: "0 auto", width: "40%"}} */}
{/* /> */}


## Settings


## Technical notes
### Booster generation 2
#### Control modes
The Booster generation 2 has the following characteristics:
    - 80 kW AC/DC converter
    - EV connector 1: 200 kW DC
    - EV connector 2: 210 kW DC
    - Battery 218 kWh energy capacity; 240 kW power capacity

This means that the battery can only be (dis)charged with 80 kW __from and to the grid__.
The discharge power is up to 200 kW __when discharged to DC meant for EV charging__.
Depending on the battery control power, we switch between two modes that are provided by Xargeon:
- Recharge mode: This is activated when the battery is charged from the AC side or when the battery setpoint is 0.
    When this is active, the EV charging power is limited to 200 for EV connector 1 and 210 kW DC for EV connector 2 (combined up to 240 kW)
- Feed in mode: This is activated when the battery is discharged to the AC side.
  When this is active, the EV charging power is limited to 130 for EV connector 1 and 140 kW DC for EV connector 2 (combined up to 160 kW).

#### Minimum state of charge
By default, the minimum state of charge is set to 10%. When it discharges to this level, it should be charged __up to 20%__
before discharging again.


# Zerova


import { BrandName, ControllerName } from '@site/src/components/customFields';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';
import ClickableImage from '@site/src/components/ClickableImage';

<img
    src="/api/media/editor-uploads/Controller/Devices/EV-charging-station/Zerova/logo-horizontal-while-scaled.png"
    alt="Zerova logo" 
    style={{ display: "block", margin: "0 auto", width: "40%", padding: "0 0 2em 0"}}
/>

# Zerova charging stations

<DeviceSupportTable
  devices={[
    { 
      type: 'DSY', 
      modbusTcp: '✅', 
      rs485: '❌'
    },
    { 
      type: 'DTY', 
      modbusTcp: '✅', 
      rs485: '❌'
    },
    { 
      type: 'DQY', 
      modbusTcp: '✅', 
      rs485: '❌'
    },
    { 
      type: 'DLY', 
      modbusTcp: '✅', 
      rs485: '❌'
    },
    { 
      type: 'DMY', 
      modbusTcp: '✅', 
      rs485: '❌'
    },
    { 
      type: 'DWY', 
      modbusTcp: '✅', 
      rs485: '❌'
    },
    { 
      type: 'DDY', 
      modbusTcp: '✅', 
      rs485: '❌'
    },
    { 
      type: 'DOY', 
      modbusTcp: '✅', 
      rs485: '❌'
    },
    { 
      type: 'DZY', 
      modbusTcp: '✅', 
      rs485: '❌'
    }
  ]}
  showModbusTcp={true}
  showRs485={true}
/>


<img src="/api/media/editor-uploads/Controller/Devices/EV-charging-station/Zerova/zerova-dc-charger.png" alt="zerova dc charger" style={{ display: "block", width: "50%", padding: "0 0 2em 0"}}
/>


## Connection

The communication between the <BrandName /> <ControllerName /> and the Zerova charging station takes place via **Modbus TCP**.

1. Connect the charging station to the same local network (LAN) as the <ControllerName /> using an Ethernet cable.
2. For correct ethernet wiring standards, follow the [guidelines for ethernet wiring](/Controller/wiring-best-practices/#ethernet).

## Configuration

To allow the <BrandName /> <ControllerName /> to control the station, you must enable Modbus TCP via the Zerova web portal.

### Enable Modbus TCP

1. Log in to the Zerova web portal of the charger.
2. Go to **SET** > **Backend**.
3. Open the **Modbus TCP Server** section.
4. Set **Mode** to **Enable**.
5. Leave **Password Verify** and **TLS encryption** unchecked.
6. Save the settings.

<ClickableImage src="/api/media/editor-uploads/Controller/Devices/EV-charging-station/Zerova/modbus-tcp-enable.png" alt="modbus tcp enable" maxWidth="600px" />


### Check the model name and serial number

1. Go to **SET** > **System**.
2. Under **System Information**, you will find the **Model Name** and **Serial Number** of the charger.

<ClickableImage src="/api/media/editor-uploads/Controller/Devices/EV-charging-station/Zerova/find-charger-model-name.png" alt="find charger model name" maxWidth="600px" />


### Check the IP and MAC address

1. Go to **SET** > **Network**.
2. Open the **Ethernet** section to find the **MAC Address** and **IP Address** of the charger.

<ClickableImage src="/api/media/editor-uploads/Controller/Devices/EV-charging-station/Zerova/check-ip-and-mac.png" alt="check ip and mac" maxWidth="600px" />

> [!TIP]
> Assign a **static IP address** to the charger (or a DHCP reservation for its MAC address in your router). This makes sure the <ControllerName /> can always find it.

### Adding to the Controller

1. Go to the <BrandName /> <ControllerName /> web interface.
2. Navigate to **Devices** > **Add Device**.
3. Select **Zerova** > **Modbus TCP**.
4. Enter the **IP Address** of the charger.
5. Enter Port **502** and Modbus address **1**.
6. Click *


*Scan**.

# Eniris



# Hager



import DeviceSupportTable from '@site/src/components/DeviceSupportTable';


<DeviceSupportTable
devices={[
{
type: "HPS",
modbusTcp: "✅",
rs485: "❌",
},
{
type: "TPCS-630",
modbusTcp: "✅",
rs485: "❌",
}
]}
showModbusTcp={true}
showRs485={true}
/>

> [!NOTE]
>  If you want to change the interval between measurements to avoid granularity issues you can go in <i>Settings > Advanced Settings</i> and modify :
> <ul>
> <li><b>Data reading period :</b> How often the data is read out from the devices. You should set this to 0, which means as fast as possible.</li>
> <li><b>Scheduler run period :</b> How much seconds there must be at least between two consecutive control loop executions. Less excecutions mean less data usage, but come at the cost of slower and less accurate control.</li>
> </ul>

# Gas Meter


import { FolderOverview } from '@/components/FolderOverview';

# Gas Meter

<FolderOverview folder="Controller/Devices/Gas-meter" />


# a-TroniX

import { BrandName, ControllerName } from '@site/src/components/customFields';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/customers/a_tronix/logo.png"
    alt="Vaillant"
    style={{ display: "block", margin: "50px auto", width: "40%" }}
/>

# A-TroniX Heatpumps

## Supported Devices


<DeviceSupportTable
  devices={[
    { type: 'Heatpump via DS1242',  modbusTcp: '❌', rs485: '❌' }
  ]}
  showModbusTcp={true}
  showRs485={true}
/>

> [!WARNING]
>
> Control is only possible to turn on or off the smart grid mode of the device.
> Specific Wattage control or Boost and Block mode is not supported!
>


### Ethernet


## Connection

The communication between the <BrandName /> <ControllerName /> and the A-TroniX Heatpump is SG-Ready.


# Daikin Altherma 3 Heatpumps


import { BrandName, ControllerName } from "@site/src/components/customFields";
import ClickableImage from "@site/src/components/ClickableImage";
import DeviceSupportTable from "@site/src/components/DeviceSupportTable";

<img
  src="/img/sgo/Logo_Daikin.png"
  alt="Daikin"
  style={{ display: "block", margin: "50px auto", width: "40%" }}
/>

# Daikin Altherma 3 Heatpumps

## Supported Devices
    <DeviceSupportTable
      devices={[
         { 
            type: ' EHV\* ', 
            api: '❌', 
            modbusTcp: '❌', 
            rs485: '❌', 
            relays: '✅',
         },
         { 
            type: 'ETV\*', 
            api: '❌', 
            modbusTcp: '❌', 
            rs485: '❌', 
            relays: '✅',
         }   
      ]}
      showApi={true}
      showModbusTcp={true}
      showRs485={true}
      showRelays={true}
      />
> [!WARNING]
>
> Control is only possible using Boost or Block.
> Specific Wattage control is not supported!
>

## Connection

The communication between the <BrandName /> <ControllerName /> and the Daikin heatpump operates via Relays.
This guide follows the installation of the installer reference guide.

### 1. Preparation

Turn off the heat pump completely by disconnecting the power supply to the heat pump.

### 2. Opening the Switchbox

Follow the steps as described in section **7.2.4 - To open the indoor unit** of the installers reference guide:

- Remove the **MMI plate**.
- Then remove the **front plate**.

### 3. Locating Terminal Block X5M

Locate terminal block **X5M** inside the unit. On this terminal block, you will find:

- **Positions 9-10**: `S10S` (12V)
- **Positions 5-6**: `S11S` (12V)

### 4. Wiring to the Controller

For the connection between the <BrandName /> <ControllerName /> and the Daikin Altherma heat pump wire with 0.5mm2 cross section is required.
Wire the heat pump to the controller as follows:

| Terminal X5M | Controller |
| ------------ | ---------- |
| 9            | R1 NO      |
| 10           | R1 COM     |
| 5            | R2 NO      |
| 6            | R2 COM     |

### 5. Adding the Heat Pump to the Controller

In the controller interface, navigate to:
Devices > Start device wizard > Heat Pump > Generic > Relays > Relay-controlled heat pump > My device is fully connected.

Then enter the following data:

- An estimate of the **maximum required power** for the heat pump at that location.

Continue through the wizard to complete the setup.

You may modify the device settings afterward as desired, but the default values are sufficient in most cases.

### 6. Reconnecting the Heat Pump

Once the wiring is complete, you may power the heat pump back on.

### 7. Configuration via MMI

Using the heat pump's MMI, enter **installer mode** and set the following parameters:

| Breadcrumb | Value            | Name                      |
| ---------- | ---------------- | ------------------------- |
| 9.8.4      | 3 = Smart Grid   | Benefit kWh power supply  |
| 9.8.5      | _set as desired_ | Smart Grid operation mode |
| 9.8.6      | _set as desired_ | Allow electrical heaters  |
| 9.8.7      | _set as desired_ | Enable room buffering     |
| 9.8.8      | _set as desired_ | Limit setting kW          |

> 💡 **Tip**: To turn on the breadcrumbs press the (i) button on the MMI while on the homescreen.

---

After completing these steps, the heat pump will be properly connected, registered in the software, and configured for use via relay control.

# Heat Pump


import { FolderOverview } from '@/components/FolderOverview';

# Heat Pump

<FolderOverview folder="Controller/Devices/Heat-pump" />


# Itho-Daalderop


import { BrandName, ControllerName } from '@site/src/components/customFields';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';

<img
    src="/img/customers/itho-daalderop/logo.png"
    alt="Itho-Daalderop"
    style={{ display: "block", margin: "50px auto", width: "40%" }}
/>

# Itho-Daalderop Heatpump

## Supported Devices


<DeviceSupportTable
  devices={[
    { type: 'Itho-Daalderop heatpump', api: '❌', modbusTcp: '❌', rs485: '✅' }
  ]}
  showModbusTcp={true}
  showRs485={true}
/>

> [!WARNING]
>
> Control is only possible using Boost or Block.
> Specific Wattage control is not supported!
>

## Connection

The communication between the <BrandName /> <ControllerName /> and the Itho-Daalderop heatpump operates via RS485.

### RS485

<RS485ConnectionTable firstColumn={["A", "B", "GND (if available)"]} />

# MyEnergi Heatpumps and Boilers


import { BrandName, ControllerName } from '@site/src/components/customFields';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/sgo/Logo_MyEnergi.png"
    alt="MyEnergi"
    style={{ display: "block", margin: "50px auto", width: "40%" }}
/>

# MyEnergi Heatpumps and Boilers

## Supported Devices


<DeviceSupportTable
  devices={[
    { type: 'Eddi', api: '✅', modbusTcp: '❌', rs485: '❌' }
  ]}
  showApi={true}
  showModbusTcp={true}
  showRs485={true}
/>

> [!WARNING]
>
> Control is only possible using Boost or Block.
> Specific Wattage control is not supported!
>

## Connection

The communication between the <BrandName /> <ControllerName /> and the Eddi operates via API.

### API

You need an API key to connect the Eddi to the <BrandName /> <ControllerName />. To generate an API key, follow these steps:
    1. Log in to the MyEnergi portal.
    2. Go to the "Products" tab.
    3. Under your Gateway or Eddi click "Advanced"
    4. Click "Generate new API key"

<ClickableImage src="/img/customers/myenergi/advanced.jpg" alt="Zappi Settings" maxWidth="500px" />

# Nibe


import { BrandName, ControllerName } from '@site/src/components/customFields';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';

<img
    src="/img/customers/nibe/Logo_Nibe.png"
    alt="Nibe"
    style={{ display: "block", margin: "50px auto", width: "40%" }}
/>

# NIBE heat pumps

The connection and available functions differ between the F-series and the S-series. Use the section for the heat pump installed on your site: a Modbus connection for monitoring does not automatically provide heating control.

| Heat pump | Connection covered here | Function |
| --- | --- | --- |
| F-series | RS485 / Modbus RTU through a NIBE MODBUS 40 module | The existing wired connection is described below. Available heating functions depend on the controller software; this page does not establish rollout of additional control modes. |
| S1155, S1156, S1255 and S1256 | Built-in Modbus TCP/IP | Monitoring connection currently being validated. Heating boost, blocking and direct power control are not provided by this connection. |

## F-series: RS485 connection

### Supported devices

<DeviceSupportTable
  devices={[
    { type: 'Nibe F-Series Heatpump', api: '❌', modbusTcp: '❌', rs485: '✅' }
  ]}
  showModbusTcp={true}
  showRs485={true}
/>

The **[NIBE MODBUS 40 communication module](https://www.nibe.eu/nl-nl/producten/accessoires/modbus-40)** is required to enable Modbus communication on the F-series heat pump.

The communication between the <BrandName /> <ControllerName /> and the F-series heat pump operates via RS485.

<RS485ConnectionTable firstColumn={["A", "B", "GND (if available)"]} />

## S-series: monitoring over Modbus TCP/IP

> [!IMPORTANT]
> The S-series monitoring connection is currently being validated. Contact support to arrange the appropriate controller software before commissioning it. Do not use this connection as a basis for a promise of heating control.

This connection covers the **S1155, S1156, S1255 and S1256** register set. These models have built-in Modbus TCP/IP, so this connection does **not** use the MODBUS 40 module required for the F-series route above.

### Prepare the heat pump

1. Connect the heat pump and the <ControllerName /> to the same local network.
2. On the heat pump, open **5.2 — Network settings** and configure Ethernet or Wi-Fi.
3. Open **7.5.9 — Modbus TCP/IP** and enable Modbus TCP/IP.
4. Note the heat pump's IP address under **3.1.13 — Connections**. The connection uses **TCP port 502**.
5. If **IP address restriction** is enabled, allow the <ControllerName />'s IP address. **Reading Modbus only** can remain enabled for this monitoring connection.

### Add it to the controller

With the appropriate controller software installed, open the commissioning wizard and select **Heat pump → Nibe → S-Series** with a **Modbus TCP** connection. Enter the heat pump's local IP address and port **502**, then discover and add the device.

Compare the first readings with **3.1 — Operating info** on the heat pump display.

If the device is reachable but not detected, check that the heat pump reports a valid **BT50 room temperature between 0 °C and 50 °C**. A missing room sensor or a value outside that range can prevent detection.

### What is monitored?

| Measurement group | Examples |
| --- | --- |
| Temperatures | Outdoor and room temperature, supply and return temperature, hot-water temperatures and brine temperatures. |
| Circulation pumps | Heating-medium and brine-pump speeds. |
| Compressor and operating state | Compressor frequency, on/off status and whether the reversing valve is in the heating or hot-water position. |

Readings depend on the sensors and accessories present on the heat pump. This connection does not provide an electrical consumption measurement in watts or kWh.

### Monitoring is not heating control

The S-series connection described here does **not** provide **Boost**, **Block** or a target power in watts. Keep the heat pump's own heating controls in place. A separate SG Ready or PV-contact arrangement is a different connection and is not established by enabling Modbus TCP/IP.

For the manufacturer's menu descriptions and register information, see [NIBE's S-series Modbus guide](https://www.nibe.eu/download/18.42a6470a1963dded290bb1/1746538843623/Technical%20information%20Modbus%20S-Series.pdf).


# Remeha


import { BrandName, ControllerName } from '@site/src/components/customFields';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';

<img
    src="/img/customers/remeha/Logo_Remeha.png"
    alt="Remeha"
    style={{ display: "block", margin: "50px auto", width: "40%" }}
/>

# Remeha Heatpump

## Supported Devices


<DeviceSupportTable
  devices={[
    { type: 'Remeha heatpump', api: '❌', modbusTcp: '✅', rs485: '✅' }
  ]}
  showModbusTcp={true}
  showRs485={true}
/>

> [!WARNING]
>
> Control is only possible using Boost or Block.
> Specific Wattage control is not supported!
>

## Connection

The communication between the <BrandName /> <ControllerName /> and the Remeha heatpump operates via RS485 or Modbus TCP.

### RS485

<RS485ConnectionTable firstColumn={["A", "B", "GND (if available)"]} />

# Heatpump via Shelly relays


import { BrandName, ControllerName } from '@site/src/components/customFields';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/customers/shelly/shelly_logo_blue.png"
    alt="Shelly Logo"
    style={{ display: "block", margin: "0 auto", width: "40%" }}
/>

Shelly relays can be used to control heat pumps with smartgrid ready contacts.
See  [Smartgrid Ready Contacts](/Devices/Heat-pump/SmartgridReadyContact) for more information on smartgrid ready contacts.

## Supported Devices

<DeviceSupportTable
  devices={[
    {
      type: "Shelly Plus",
      variants: '2PM, Uni',
      localApi: '✅',
    },
    {
      type: "Shelly Pro",
      variants: '2, 2PM, 3, 4PM',
      localApi: '✅',
    },
    {
      type: "Shelly Gen3",
      variants: '2PM, 2L',
      localApi: '✅',
    },
    {
      type: "Shelly Gen4",
      variants: '2PM, PowerStrip',
      localApi: '✅',
    },
  ]}
  showLocalApi={true}
  showRs485={false}
  showVariants={true}
/>

> [!NOTE]
> Please note: This integration has not been tested with all the devices listed above. However, since they utilize the same communication protocol, they are expected to operate seamlessly.  
> Configuration examples in this document are based on the **Shelly Pro 2** relay.

<ClickableImage src="/img/customers/shelly/shelly-pro2.png" alt="Shelly Pro 2 Relay" maxWidth="450px" />

## Wiring
The communication between the **<ControllerName/>** and the Shelly relay is established via **Local API** (over TCP/IP).
For proper Ethernet wiring, please follow the [Ethernet wiring guidelines](/Controller/wiring-best-practices/#ethernet).

## Wiring Instructions

1. **Power Supply Connections**  
   - **L (Live)**: Connect the live wire to the **L** terminal of the device.  
   - **N (Neutral)**: Connect the neutral wire to the **N** terminal of the device.

   <ClickableImage src="/img/customers/shelly/shelly-blue.png" alt="Power Connections" maxWidth="450px" />


2. **Relay Output Connections**  
   - **O1 (Relay 1)**: Connect the live wire for the first circuit to the **O1** terminal.  
   - **O2 (Relay 2)**: Connect the live wire for the second circuit to the **O2** terminal.

   <ClickableImage src="/img/customers/shelly/shelly-green.png" alt="Relay Connections" maxWidth="450px" />

3. **Device Diagram**  
   Refer to the diagram printed on the device for detailed wiring instructions. Ensure all connections match the diagram.

   <ClickableImage src="/img/customers/shelly/shelly-instructions.png" alt="Device Wiring Diagram" maxWidth="500px" />

---

## Configuration Instructions



1. **Wire the Device**  
   Ensure the device is wired according to the provided wiring diagram and connect the Ethernet cable securely.

   <ClickableImage src="/img/customers/shelly/shelly-wire-cable.jpg" alt="Shelly Wiring Example" maxWidth="450px" />

2. **Access the Shelly Interface**  
   - Using a phone or other device, connect to the Shelly relay's Wi-Fi network (e.g. **SSID: ShellyPro2-XXXXXX**).  
   - Open a browser and navigate to **http://192.168.33.1** to access the Shelly interface.

3. **Locate the Ethernet Settings**  
   - In the Shelly interface, navigate to the **Ethernet Settings** section.  
   - Here, you will find the assigned **Ethernet IP address**, which is required for connecting the device to the controller.

   <ClickableImage src="/img/customers/shelly/shelly-interface.jpg" alt="Shelly Interface Example" maxWidth="300px" />
   <ClickableImage src="/img/customers/shelly/shelly-ethernet.png" alt="Ethernet Settings Example" maxWidth="700px" />

> [!NOTE]
> **Note**: Do not modify any settings while locating the Ethernet IP address.

By following these steps, you will retrieve the required IP address for integrating the Shelly relay with the **<ControllerName/>**. 
For further details and comprehensive documentation, please refer to the official [Shelly Installation Guides](https://kb.shelly.cloud/knowledge-base/installation-guides).


# Smartgrid Ready Heat Pumps



# ✅ Smart Grid Ready Heat Pumps

This list contains heat pump models that support SG Ready

---

## 2G Energy AG
- afilia air series  
  e.g., `afilia air C-sl 0452 HE/XL/RV P2U- R454B` and variants

## Airwell
- Wellea Monobloc A, DF, WT, Monobloc R32, Split R32
- Wellea Split A
- R290 Series: `4DC`, `6DC`, `9DC`, `12DC`, `16DC`, `19DC`
- DCT-R290 Series: `9DCT`, `12DCT`, `16DCT`, `19DCT`, `22DCT`

## Alpha Innotec
- Luxtronik controlled heat pumps

## Atag
- Energion M Compact / Hybrid / Plus
- Energion M All Electric series

## Atlantic
- Alfea Extensa M
- Calypso VM
- Explorer V4

## Bosch
- Compress 3400i AWS
- Compress 7000 LW, 7800i LW
- Compress Hybrid 3000i, 5800i, 7000i AW
- CS 3000 AWP

## Bulex
- MagnaAqua (PV-ready)

## Clivet
- Aqua Plus
- Sphera Evo

## CTC
- GSI
- EcoZenith
- EcoLogic L M

## Daikin
- Altherma 3 H HT F, 3 H MT F, 3 M, 3 RF, 3 RW
- Altherma H Hybrid
- EKHHE, EKHHP, EHS, RoCon HP

## Dynamis (Kospel)
- HPM2

## Heliotherm
- Models with Remote Control Gateway

## Hitachi
- Yutaki Series
- Yutaki S Combi

## IDM
- Smart Grid Ready models (unspecified)

## Itho Daalderop
- Amber

## Kronoterm
- VERSI-I, VERSI-X
- ETERA S, M, L
- VERSI-O

## LG
- HN1616.NK5
- HN1616M.NK5
- HN0916M.NK4
- HN091MR.NK5
- HN1600MB.NK0

## Midea
- ESG INV M (Swimming Pool Heat Pumps)

## Mitsubishi Electric
- Ecodan Series
- Ecodan EHPT20X-MHEDW
- PAC-IF071B-E
- PAC-TH012HT-E
- Hydrobox

## Nefit (Bosch Group)
- EnviLine AW Monoblock / IDU Monoblock E / TTS
- EnviLine AW Split

## Nibe
- F1155, F1245
- S1155, S1255
- Other Smart Grid Ready variants

## Nulite
- R290 Series
- Flamingo Series
- Geothermal Series *(SG Ready to be confirmed model-by-model)*

## Ochsner
- AIR FALCON 212
- AIR HAWK 208
- AIR M2+M4

## Panasonic
- Aquarea Series
- WH-MDC Monobloc
- WH-SDC
- WH-UD/UX/UQ Series
- EasyPLUG (PAW) for SG 230V

## R-Aqua
- HPB 100–300
- HPB-S Solar

## Remeha
- Elga Ace (hybrid air-water)

## Rinnai
- Enviroflo Hot Water Heat Pumps *(SG capability in development — verify)*

## Stiebel Eltron
- SG Ready models available *(verify per model)*

## Thermia
- Atlas
- Calibra
- Mega

## Tongyi Heat Pump
- SG Ready certification (model-specific confirmation needed)

## Vaillant
- aroTHERM (plus)
- aroSTOR
- flexoTHERM
- flexoCOMPACT
- climaVAIR

## Viessmann
- Vitocal Series
  - e.g., Vitocal 250-A

## Vivax
- HPP Swimming Pool

## Weishaupt
- Geoblock WGB
- Splitblock WSB

## Wolf
- BWL
- FHA
- CHA


# Smartgrid Ready Contact


import { BrandName, ControllerName, CustomerName, InsightsName, InsightsUrl } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';

> [!NOTE]
> We support most heat pumps with a Smartgrid Ready contact.

## What is SG-Ready?

SG-Ready (Smart Grid Ready) is a standardized interface defined by the German Heat Pump Association (BWP). It lets an energy management system control a heat pump using just **two physical relay contacts**, no digital communication required.

Each relay is either open (off = `0`) or closed (on = `1`). The combination of both relays encodes one of four operating modes. The **binary code** in the table below directly represents the relay states: the **first digit is Relay 1**, the **second digit is Relay 2**.

For example, `10` means Relay 1 is closed and Relay 2 is open.

This relay mapping is **standardized**, every SG-Ready certified heat pump uses the same relay ordering. The exact behavior (e.g. how aggressively the pump boosts) depends on the manufacturer.

## The Four SG-Ready Modes

| Binary Code | Relay 1 | Relay 2 | Mode |
| :---: | :---: | :---: | :--- |
| **00** | Open | Open | Normal operation: heat pump runs on its own schedule |
| **01** | Open | Closed | Recommended operation: heat pump is encouraged to run more (e.g. solar surplus) |
| **10** | Closed | Open | Block: heat pump is switched off to reduce grid load |
| **11** | Closed | Closed | Boost: heat pump runs at maximum power |

## How <BrandName /> Uses SG-Ready

<BrandName /> uses three of the four modes. Mode `01` (Recommended) is part of the standard but is not currently used.

| Binary Code | Relay 1 | Relay 2 | <BrandName /> Purpose | Typical Heat Pump Response |
| :---: | :---: | :---: | :--- | :--- |
| **00** | Open | Open | Default: device operates autonomously | Runs according to its own internal schedule |
| **10** | Closed | Open | Grid stabilization: reduce consumption | Switches off immediately; resumes when signal changes |
| **11** | Closed | Closed | Boost: maximize self-consumption or support the grid | Runs at maximum power regardless of internal state |

## Practical Example: Daikin Altherma

On a Daikin Altherma, Relay 1 connects to terminal **S10S** (pins 9–10) and Relay 2 connects to terminal **S11S** (pins 5–6).

| Situation | Relay 1 | Relay 2 | Code | Effect |
| :--- | :---: | :---: | :---: | :--- |
| High electricity price or grid overload | Closed | Open | **10** | Heat pump switches off |
| Excess solar energy or cheap grid electricity | Closed | Closed | **11** | Heat pump runs at full output |
| No active signal | Open | Open | **00** | Heat pump manages itself |

See the [Daikin Altherma installation guide](/Devices/Heat-pump/DaikinAltherma/) for full wiring instructions.


# Vaillant


import { BrandName, ControllerName } from '@site/src/components/customFields';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/customers/vaillant/logo.png"
    alt="Vaillant"
    style={{ display: "block", margin: "50px auto", width: "40%" }}
/>

# Vaillant Heatpumps

## Supported Devices


<DeviceSupportTable
  devices={[
    { type: 'Heatpump via DS1242',  modbusTcp: '✅', rs485: '❌' }
  ]}
  showModbusTcp={true}
  showRs485={true}
/>

> [!WARNING]
>
> Control is only possible to turn on or off the smart grid mode of the device.
> Specific Wattage control or Boost and Block mode is not supported!
>


### Ethernet
For correct ethernet wiring: Follow the [the guidelines for ethernet wiring](/Controller/wiring-best-practices/#ethernet).

## Connection

The communication between the <BrandName /> <ControllerName /> and the Vaillant Heatpump operates via TCP.


# Supported Devices


# Supported devices overview

import CollapsibleBrandTable from '@site/src/components/CollapsibleBrandTable';

## Wind turbines, water turbines and gensets

Wind turbines, water turbines (hydro) and gensets (backup power generators) are supported device categories from controller software **1.32**. The corresponding category must be enabled by the controller licence.

| Supported equipment | Production monitoring | Control options |
| --- | --- | --- |
| **Wind turbines** | Through a compatible energy meter or a custom Modbus turbine integration. | Production limiting through a compatible turbine integration. |
| **Water turbines (hydro)** | Through a compatible energy meter or a custom Modbus turbine integration. | Production limiting through a compatible turbine integration. |
| **Gensets / backup power generators** | Through a compatible energy meter configured for generator production. | Start/stop through a separately configured relay based on battery state of charge; no variable-power regulation. |

A meter-only connection measures production but cannot limit the connected turbine or control the generator. Direct turbine control requires a supported writable production-limit interface; custom turbine integrations can use Modbus TCP or Modbus RTU (RS485).

[See connection options, configuration and control behaviour for turbines and gensets](/Controller/Devices/wind-and-water-turbines/).

## Device brands and models

Click on a brand name ('+' icon) to expand/collapse the list of its supported devices within the table.

Entries marked ⚠️ are in testing or validation and require controller software that includes the integration. They are not a promise of availability on every installed controller. Open the corresponding device guide for connection details and limitations.

<div className="device-table-container">
{/* TODO: It is probably possible to generate this and/or individual device pages automatically based on a type of JSON.*/}

### Boilers
<CollapsibleBrandTable overviewDataJson='{"my-PV":{}}' />

### Cloud Supported Devices
<CollapsibleBrandTable overviewDataJson='{"Huawei":{},"EMS Control":{"EV Chargers":{"modbus tcp (ethernet)":"N/A","rs485":"N/A","Cloud":"❌"},"Grid &amp; Consumption Meters":{"modbus tcp (ethernet)":"N/A","rs485":"N/A","Cloud":"❌"},"Heatpumps":{"modbus tcp (ethernet)":"N/A","rs485":"N/A","Cloud":"❌"},"Solar Inverters":{"modbus tcp (ethernet)":"N/A","rs485":"N/A","Cloud":"❌"},"Solar Inverters (All)":{"modbus tcp (ethernet)":"N/A","rs485":"N/A","Cloud":"❌"},"Storage Devices":{"modbus tcp (ethernet)":"N/A","rs485":"N/A","Cloud":"❌"},"Storage Devices (All)":{"modbus tcp (ethernet)":"N/A","rs485":"N/A","Cloud":"❌"}},"SMA":{},"Sparky":{"sparky":{"modbus tcp (ethernet)":"N/A","rs485":"N/A","Cloud":"❌"}},"AlphaESS":{"SMILE":{"modbus tcp (ethernet)":"N/A","rs485":"N/A","Cloud":"❌"}},"SolarEdge":{"Commercial Synergy (SE66K / SE100K)":{"modbus tcp (ethernet)":"❌","rs485":"❌","Cloud":"❌"},"HD-Wave single-phase (SE3000–SE7600)":{"modbus tcp (ethernet)":"❌","rs485":"❌","Cloud":"❌"},"Three-phase (SE9K–SE33.3K)":{"modbus tcp (ethernet)":"❌","rs485":"❌","Cloud":"❌"}},"ISolarCloud":{"All Sungrow inverters registered in iSolarCloud":{"modbus tcp (ethernet)":"—","rs485":"—","Cloud":"❌"}},"Neovolt":{"All":{"modbus tcp (ethernet)":"N/A","rs485":"N/A","Cloud":"❌"}}}' />

### Energy Meters
<CollapsibleBrandTable overviewDataJson='{"IMT":{"Si-RS485TC-T-MB":{"modbus tcp (ethernet)":"❌","rs485":"✅"}},"Eniris":{"Bidirectional Pulse Energy Meter":{"modbus tcp (ethernet)":"N/A","rs485":"N/A"},"Unidirectional Pulse Energy Meter":{"modbus tcp (ethernet)":"N/A","rs485":"N/A"}},"Janitza":{"Janitza RMU 301 CBM":{"modbus tcp (ethernet)":"❌","rs485":"✅"},"Janitza UMG 604 PRO":{"modbus tcp (ethernet)":"✅","rs485":"✅"},"Janitza UMG 605 PRO":{"modbus tcp (ethernet)":"✅","rs485":"✅"},"Janitza UMG 96 PQ L":{"modbus tcp (ethernet)":"❌","rs485":"✅"},"Janitza UMG 96 RM":{"modbus tcp (ethernet)":"❌","rs485":"✅"},"Janitza UMG 96 RM-CBM":{"modbus tcp (ethernet)":"❌","rs485":"✅"},"Janitza UMG 96 RM-P":{"modbus tcp (ethernet)":"❌","rs485":"✅"},"Janitza UMG 96 RM-PN":{"modbus tcp (ethernet)":"✅","rs485":"✅"},"Janitza UMG 96 S2":{"modbus tcp (ethernet)":"✅","rs485":"✅"},"Janitza UMG 96-PA":{"modbus tcp (ethernet)":"❌","rs485":"✅"},"Janitza UMG 96-PAMID":{"modbus tcp (ethernet)":"❌","rs485":"✅"}},"Solis":{"Autarco Energy Meter":{"modbus tcp (ethernet)":"✅","rs485":"✅"},"Autarco Grid-Tie Meter (via Inverter/EPM)":{"modbus tcp (ethernet)":"✅","rs485":"✅"},"Solis Energy Meter":{"modbus tcp (ethernet)":"✅","rs485":"✅"},"Solis Grid-Tie Meter (via Inverter/EPM)":{"modbus tcp (ethernet)":"✅","rs485":"✅"}},"Eastron":{"Eastron SDM120M":{"modbus tcp (ethernet)":"❌","rs485":"✅"},"Eastron SDM630":{"modbus tcp (ethernet)":"❌","rs485":"✅"},"Eastron Smartrail X835":{"modbus tcp (ethernet)":"❌","rs485":"✅"}},"Schneider":{"ComPact NSXe":{"modbus tcp (ethernet)":"✅","rs485":"✅"},"ComPact NSXs":{"modbus tcp (ethernet)":"✅","rs485":"✅"},"MasterPact MTZ (MicroLogic X)":{"modbus tcp (ethernet)":"❌","rs485":"✅"},"Schneider-Electric iEM 2100 Series":{"modbus tcp (ethernet)":"❌","rs485":"✅"},"Schneider-Electric iEM 2150":{"modbus tcp (ethernet)":"❌","rs485":"✅"},"Schneider-Electric iEM 2155":{"modbus tcp (ethernet)":"❌","rs485":"✅"},"Schneider-Electric IEM 3150":{"modbus tcp (ethernet)":"❌","rs485":"✅"},"Schneider-Electric IEM 3155":{"modbus tcp (ethernet)":"❌","rs485":"✅"},"Schneider-Electric IEM 3250":{"modbus tcp (ethernet)":"❌","rs485":"✅"},"Schneider-Electric IEM 3255":{"modbus tcp (ethernet)":"❌","rs485":"✅"},"Schneider-Electric IEM 3350":{"modbus tcp (ethernet)":"❌","rs485":"✅"},"Schneider-Electric IEM 3355":{"modbus tcp (ethernet)":"❌","rs485":"✅"},"Schneider-Electric IEM 3455":{"modbus tcp (ethernet)":"❌","rs485":"✅"},"Schneider-Electric IEM 3555":{"modbus tcp (ethernet)":"❌","rs485":"✅"},"Schneider-Electric PM 3250":{"modbus tcp (ethernet)":"❌","rs485":"✅"},"Schneider-Electric PM 5100 / 5110 / 5111":{"modbus tcp (ethernet)":"❌","rs485":"✅"},"Schneider-Electric PM 5310 / 5330 / 5331":{"modbus tcp (ethernet)":"❌","rs485":"✅"},"Schneider-Electric PM 5320 / 5340 / 5341":{"modbus tcp (ethernet)":"✅","rs485":"✅"},"Schneider-Electric PM 8000":{"modbus tcp (ethernet)":"✅","rs485":"✅"},"Schneider-Electric PM 820":{"modbus tcp (ethernet)":"❌","rs485":"✅"},"Schneider-Electric PM 850":{"modbus tcp (ethernet)":"❌","rs485":"✅"},"Schneider-Electric PM 870":{"modbus tcp (ethernet)":"❌","rs485":"✅"},"Schneider-Electric PowerTag Energy (R9M Series)":{"modbus tcp (ethernet)":"✅","rs485":"❌"}},"Carlo Gavazzi":{"Carlo Gavazzi EM111":{"modbus tcp (ethernet)":"❌","rs485":"✅"},"Carlo Gavazzi EM210":{"modbus tcp (ethernet)":"❌","rs485":"✅"},"Carlo Gavazzi EM24":{"modbus tcp (ethernet)":"✅","rs485":"✅"},"Carlo Gavazzi EM330":{"modbus tcp (ethernet)":"❌","rs485":"✅"},"Carlo Gavazzi EM340":{"modbus tcp (ethernet)":"❌","rs485":"✅"},"Carlo Gavazzi EM500 Series (EM530, EM540)":{"modbus tcp (ethernet)":"❌","rs485":"✅"},"Carlo Gavazzi EM511":{"modbus tcp (ethernet)":"❌","rs485":"✅"},"Carlo Gavazzi VMU-S":{"modbus tcp (ethernet)":"❌","rs485":"✅"}},"Algodue":{"UPM209":{"modbus tcp (ethernet)":"✅","rs485":"✅"}},"Dornscheidt":{"Pro380":{"modbus tcp (ethernet)":"✅","rs485":"✅"}},"Solax":{"Energy Meter via Hybrid G4 Inverter":{"modbus tcp (ethernet)":"✅","rs485":"❌"}},"Sunwoda":{"Energy Meter via Sunwoda OSP":{"modbus tcp (ethernet)":"❌","rs485":"✅"}},"bmr":{"PLA33":{"modbus tcp (ethernet)":"✅","rs485":"✅"},"PLA33RX":{"modbus tcp (ethernet)":"✅","rs485":"✅"}},"Phoenix-Contact":{"Phoenix-Contact EEM-MA370":{"modbus tcp (ethernet)":"✅","rs485":"❌"},"Phoenix-Contact EEM-MA371":{"modbus tcp (ethernet)":"✅","rs485":"❌"},"EEM-EM375 (testing)":{"modbus tcp (ethernet)":"⚠️","rs485":"❌"},"EEM-EM377 (testing)":{"modbus tcp (ethernet)":"⚠️","rs485":"❌"}},"Victron":{"Energy Meter via Cerbo GX":{"modbus tcp (ethernet)":"✅","rs485":"❌"}},"Inepro":{"Inepro PRO380":{"modbus tcp (ethernet)":"❌","rs485":"✅"}},"Kamstrup":{"DSMR Smart Meter":{"modbus tcp (ethernet)":"N/A","rs485":"N/A"}},"Pilot":{"Pilot SPM33":{"modbus tcp (ethernet)":"✅","rs485":"✅"}},"Fluvius":{"Fluvius Digital Meter (Standard P1)":{"modbus tcp (ethernet)":"N/A","rs485":"N/A"},"Fluvius Industrial (A1 Port)":{"modbus tcp (ethernet)":"N/A","rs485":"N/A"}},"Fronius":{"Fronius 63A1":{"modbus tcp (ethernet)":"❌","rs485":"✅"}},"Hager":{"Hager EC - Series":{"modbus tcp (ethernet)":"❌","rs485":"✅"},"Hager TXF121":{"modbus tcp (ethernet)":"❌","rs485":"✅"}},"Metcom":{"Metcom Blue2box":{"modbus tcp (ethernet)":"✅","rs485":"❌"},"Metcom MCS301":{"modbus tcp (ethernet)":"✅","rs485":"✅"}},"LandisGyr":{"DSMR Smart Meter":{"modbus tcp (ethernet)":"N/A","rs485":"N/A"}},"Weidmueller":{"Weidmüller 610-230":{"modbus tcp (ethernet)":"❌","rs485":"✅"}},"Accuenergy":{"Acuvim 3 Energy Meter":{"modbus tcp (ethernet)":"✅","rs485":"✅"},"Acuvim IIR Energy Meter":{"modbus tcp (ethernet)":"✅","rs485":"✅"}},"Abb":{"ABB B21":{"modbus tcp (ethernet)":"❌","rs485":"✅"},"ABB B23":{"modbus tcp (ethernet)":"❌","rs485":"✅"},"ABB B24":{"modbus tcp (ethernet)":"❌","rs485":"✅"}},"LeGrand":{"Legrand EMDX3":{"modbus tcp (ethernet)":"❌","rs485":"✅"},"Legrand Nemo-D4-EC MFD4ORFCDT":{"modbus tcp (ethernet)":"❌","rs485":"✅"}},"P1Api":{"Energy Meter":{"modbus tcp (ethernet)":"✅","rs485":"❌"}},"Chargee":{"Sparky P1 Meter":{"modbus tcp (ethernet)":"N/A","rs485":"N/A"}},"Anexo":{"Energy Meter":{"modbus tcp (ethernet)":"❌","rs485":"✅"}},"Acrel":{"Acrel ADL3000-E-A":{"modbus tcp (ethernet)":"✅","rs485":"✅"},"Acrel DTSD1352-C":{"modbus tcp (ethernet)":"✅","rs485":"✅"}},"Sagemcom":{"DSMR Smart Meter":{"modbus tcp (ethernet)":"N/A","rs485":"N/A"}},"HomeWizard":{"HomeWizard Wifi 1-Phase Meter":{"modbus tcp (ethernet)":"✅","rs485":"N/A"},"HomeWizard Wifi 3-Phase Meter":{"modbus tcp (ethernet)":"✅","rs485":"N/A"},"HomeWizard Wifi P1 Dongle":{"modbus tcp (ethernet)":"✅","rs485":"N/A"}},"Huawei":{"Energy Meter via Smartlogger":{"modbus tcp (ethernet)":"✅","rs485":"❌"}},"Kaifa":{"DSMR Smart Meter":{"modbus tcp (ethernet)":"N/A","rs485":"N/A"}},"self-configured-energy-meter":{},"Tillquist":{"LQT40M":{"modbus tcp (ethernet)":"✅","rs485":"❌"}},"Chint":{"DDSU666 (230V-5/80A 230V-100A/40mA)":{"modbus tcp (ethernet)":"✅","rs485":"✅"},"DTSU666 (3x230V/400V-5/80A 3x230V/400V-1.5(6)A 3x230V/400V-100A/40mA)":{"modbus tcp (ethernet)":"✅","rs485":"✅"},"DTSU666-20":{"modbus tcp (ethernet)":"❌","rs485":"✅"},"DTSU666HW (3x230V/400V-5/80A 3x230V/400V-1.5(6)A 3x230V/400V-100A/40mA)":{"modbus tcp (ethernet)":"✅","rs485":"✅"}},"ShellyMeter":{"Shelly 3EM":{"modbus tcp (ethernet)":"✅","rs485":"N/A"},"Shelly Pro 3 EM (400)":{"modbus tcp (ethernet)":"✅","rs485":"N/A"}},"Joulz":{"Realtime Insights Converter":{"modbus tcp (ethernet)":"✅","rs485":"❌"}},"Iskra":{"DSMR Smart Meter":{"modbus tcp (ethernet)":"N/A","rs485":"N/A"}},"CloudMeterData":{"Energy Meter":{"modbus tcp (ethernet)":"N/A","rs485":"N/A"}},"Socomec":{"Diris (A30)":{"modbus tcp (ethernet)":"✅","rs485":"✅"},"Diris (A40)":{"modbus tcp (ethernet)":"✅","rs485":"✅"},"Diris (I30)":{"modbus tcp (ethernet)":"✅","rs485":"✅"},"Diris (I35)":{"modbus tcp (ethernet)":"✅","rs485":"✅"}},"Siemens":{"PAC":{"modbus tcp (ethernet)":"✅","rs485":"✅"}},"Ziv":{"ZIV DSMR Smart Meter":{"modbus tcp (ethernet)":"N/A","rs485":"N/A"}},"Sessy":{"Energy Meter":{"modbus tcp (ethernet)":"✅","rs485":"❌"}},"MBus":{},"YouLess":{"LS120 P1 Converter":{"modbus tcp (ethernet)":"✅","rs485":"❌"}},"Smappee":{},"Seneca":{"Seneca S604 Ethernet models":{"modbus tcp (ethernet)":"✅","rs485":"❌"}},"EnjoyPowers":{"SinE-STS (testing)":{"modbus tcp (ethernet)":"❌","rs485":"⚠️"}}}' />

### Solar irradiance sensor

The IMT Si-RS485TC-T-MB measures sunlight in W/m² through RS485 / Modbus RTU. In the commissioning wizard, it is listed in the Energy meter category under manufacturer IMT.

[Connect and commission the IMT irradiance sensor](/Controller/Devices/Energy-meter/IMT).


### EV Charging Stations
<CollapsibleBrandTable overviewDataJson='{"SMA":{"SMA EV Business Charger":{"modbus tcp (ethernet)":"✅","rs485":"❌"}},"Teltonika":{"TeltoCharge (7.4kW/11kW/22kW)":{"modbus tcp (ethernet)":"❌","rs485":"✅"}},"Wallbox":{"Commander (All)":{"modbus tcp (ethernet)":"❌","rs485":"❌"},"Copper SB (All)":{"modbus tcp (ethernet)":"❌","rs485":"❌"},"eM4 (All)":{"modbus tcp (ethernet)":"❌","rs485":"❌"},"Pulsar (Plus/Max/Pro)":{"modbus tcp (ethernet)":"❌","rs485":"❌"},"Quasar 2 (All)":{"modbus tcp (ethernet)":"❌","rs485":"❌"},"Supernova (All)":{"modbus tcp (ethernet)":"✅","rs485":"❌"}},"Raedian":{"Raedian NEO":{"modbus tcp (ethernet)":"❌","rs485":"✅"},"Raedian NEX":{"modbus tcp (ethernet)":"✅","rs485":"❌"}},"Mennekes":{"Amtron EV charger":{"modbus tcp (ethernet)":"✅","rs485":"✅"}},"a-TroniX":{},"sofar":{"Sofar EV11k-AC-02":{"modbus tcp (ethernet)":"✅","rs485":"✅"}},"HuaweiSCHarger":{"SCharger-22KT-S0":{"modbus tcp (ethernet)":"✅","rs485":"❌"},"SCharger-7KS-S0":{"modbus tcp (ethernet)":"✅","rs485":"❌"}},"Blitz-Power":{},"Alpitronic":{"Alpitronic HYC (HYC50, HYC150, HYC300, HYC400)":{"modbus tcp (ethernet)":"✅","rs485":"❌"}},"ABB":{"ABB Terra AC (/)":{"modbus tcp (ethernet)":"✅","rs485":"✅"}},"Schneider":{"EVlink Pro AC (GEX Series)":{"modbus tcp (ethernet)":"✅","rs485":"❌"}},"Kempower":{"Kempower Charger (All models supporting Modbus TCP Interface)":{"modbus tcp (ethernet)":"✅","rs485":"❌"}},"Zaptec":{"Zaptec Go":{"modbus tcp (ethernet)":"❌","rs485":"❌"},"Zaptec Pro":{"modbus tcp (ethernet)":"❌","rs485":"❌"}},"Ilumen":{"Ilumen (/)":{"modbus tcp (ethernet)":"✅","rs485":"❌"}},"Go-E":{"Go-e EV charger":{"modbus tcp (ethernet)":"✅","rs485":"❌"}},"Volt-Time":{"OCPP EV Chargers via Volt Time Cloud":{"modbus tcp (ethernet)":"N/A","rs485":"N/A"},"Volt Time Source":{"modbus tcp (ethernet)":"✅","rs485":"❌"},"Volt Time Source 2":{"modbus tcp (ethernet)":"✅","rs485":"❌"}},"Autel":{"MaxiCharger AC Ultra (2 × 22 kW)":{"modbus tcp (ethernet)":"✅","rs485":"❌"},"MaxiCharger DC Compact (40 kW)":{"modbus tcp (ethernet)":"✅","rs485":"✅"},"MaxiCharger DC Fast (40–240 kW)":{"modbus tcp (ethernet)":"✅","rs485":"✅"}},"Siemens":{},"Peblar":{"Peblar Business":{"modbus tcp (ethernet)":"✅","rs485":"❌"},"Peblar Home":{"modbus tcp (ethernet)":"✅","rs485":"❌"},"Peblar Home Plus":{"modbus tcp (ethernet)":"✅","rs485":"❌"}},"FLEXeCHARGE":{"FLEXeCHARGE Controller with Metcom Meter":{"modbus tcp (ethernet)":"✅","rs485":"❌"}},"MyEnergi":{"Zappi":{"modbus tcp (ethernet)":"❌","rs485":"❌"}},"Etrel":{"Etrel INCH / INCH Duo (All variants supporting Modbus TCP (via local network))":{"modbus tcp (ethernet)":"✅","rs485":"❌"}},"Enovates":{"Enovates Single Wallbox (SWB_4xx_22 series) (T2 / C7 / T2S / T2S+E)":{"modbus tcp (ethernet)":"✅","rs485":"❌"}},"Easee":{"Easee Charge":{"modbus tcp (ethernet)":"❌","rs485":"❌"},"Easee Core":{"modbus tcp (ethernet)":"❌","rs485":"❌"},"Easee Max":{"modbus tcp (ethernet)":"❌","rs485":"❌"},"Easee One":{"modbus tcp (ethernet)":"❌","rs485":"❌"},"Easee Pro":{"modbus tcp (ethernet)":"❌","rs485":"❌"},"Easee Up":{"modbus tcp (ethernet)":"❌","rs485":"❌"}},"OCPP":{"Most charging stations with support for OCPP v1.6 and the smart charging OCPP profile. Consult the manufacturer.":{"modbus tcp (ethernet)":"✅","rs485":"❌"}},"Alfen":{"Most Alfen charging stations":{"modbus tcp (ethernet)":"✅","rs485":"❌"}}}' />

### Gas Meter
<CollapsibleBrandTable overviewDataJson='{"Eniris":{},"Hager":{"HPS":{"modbus tcp (ethernet)":"✅","rs485":"❌"},"TPCS-630":{"modbus tcp (ethernet)":"✅","rs485":"❌"}}}' />

### Heat Pumps
<CollapsibleBrandTable overviewDataJson='{"Itho-Daalderop":{"Itho-Daalderop heatpump":{"modbus tcp (ethernet)":"❌","rs485":"✅"}},"DaikinAltherma":{"EHV\\*":{"modbus tcp (ethernet)":"❌","rs485":"❌"},"ETV\\*":{"modbus tcp (ethernet)":"❌","rs485":"❌"}},"a-TroniX":{"Heatpump via DS1242":{"modbus tcp (ethernet)":"❌","rs485":"❌"}},"Vaillant":{"Heatpump via DS1242":{"modbus tcp (ethernet)":"✅","rs485":"❌"}},"Nibe":{"Nibe F-Series Heatpump":{"modbus tcp (ethernet)":"❌","rs485":"✅"}},"SmartgridReadyContact":{},"Remeha":{"Remeha heatpump":{"modbus tcp (ethernet)":"❌","rs485":"✅"}},"MyEnergi":{"Eddi":{"modbus tcp (ethernet)":"❌","rs485":"❌"}},"SmartGridReady":{}}' />

### PLC Supported Devices
<CollapsibleBrandTable overviewDataJson='{"fluvius-telecontrol-plc":{},"plc-slave-protocol":{}}' />

### PV/Hybrid Inverters
<CollapsibleBrandTable overviewDataJson='{"KSTAR":{"BluE-S (1st Gen) Single-Phase (BluE-S 3680D/5000D/6000D-M1)":{"modbus tcp (ethernet)":"❌","rs485":"✅"},"BluE-S (1st Gen) Three-Phase (E4KT/E5KT/E6KT/E8KT/E10KT/E12KT)":{"modbus tcp (ethernet)":"❌","rs485":"✅"},"BluePulse Hybrid Inverter (KAC50DP-BC100DE)":{"modbus tcp (ethernet)":"✅","rs485":"✅"},"BluePulse Hybrid Inverter (KAC50DP-BC107DE / KAC50DP-BC107DE2)":{"modbus tcp (ethernet)":"✅","rs485":"✅"},"BluePulse Hybrid Inverter (KAC50DP-BC197DE / KAC50DP-BC197DE2)":{"modbus tcp (ethernet)":"✅","rs485":"✅"},"BlueSpark (2nd Gen) Single-Phase (E(3.68/5/6)KS-D22)":{"modbus tcp (ethernet)":"❌","rs485":"✅"},"BlueSpark (2nd Gen) Three-Phase (E(4/5/6/8/10/12)KT-D22)":{"modbus tcp (ethernet)":"❌","rs485":"✅"}},"SMA":{"Inverters connected to an SMA Data Manager":{"modbus tcp (ethernet)":"❌","rs485":"N/A"}},"Sofar":{"...":{"modbus tcp (ethernet)":"✅","rs485":"✅"},"PowerMagic 400V C&amp;I":{"modbus tcp (ethernet)":"✅","rs485":"❌"},"Sofar HYD 3000…6000-ES":{"modbus tcp (ethernet)":"✅ (Solarman WiFi &amp; ethernet dongles)","rs485":"✅"}},"Huawei":{"Huawei luna 2000":{"modbus tcp (ethernet)":"✅","rs485":"✅"},"Huawei SmartLogger 3000":{"modbus tcp (ethernet)":"✅","rs485":"❌"},"Huawei SUN2000 Series Inverters":{"modbus tcp (ethernet)":"✅","rs485":"✅"}},"Sungrow":{"MVS-Series":{"modbus tcp (ethernet)":"✅","rs485":"✅"},"Powerstack":{"modbus tcp (ethernet)":"✅","rs485":"✅"},"S-Series":{"modbus tcp (ethernet)":"✅","rs485":"✅"},"SBR-Series":{"modbus tcp (ethernet)":"✅","rs485":"✅"},"SC-Series":{"modbus tcp (ethernet)":"✅","rs485":"✅"},"SG-Series":{"modbus tcp (ethernet)":"✅","rs485":"✅"},"SH-Series":{"modbus tcp (ethernet)":"✅","rs485":"✅"},"SR-Series":{"modbus tcp (ethernet)":"✅","rs485":"✅"},"ST-Series":{"modbus tcp (ethernet)":"✅","rs485":"✅"}},"Growatt":{"10000-20000 UE":{"modbus tcp (ethernet)":"✅","rs485":"✅"},"4000-6000 UE":{"modbus tcp (ethernet)":"✅","rs485":"✅"},"MIC 1000TL-X":{"modbus tcp (ethernet)":"❌","rs485":"✅"},"MIC 1500TL-X":{"modbus tcp (ethernet)":"❌","rs485":"✅"},"MIC 2000TL-X":{"modbus tcp (ethernet)":"❌","rs485":"✅"},"MIC 2500TL-X":{"modbus tcp (ethernet)":"❌","rs485":"✅"},"MIC 3000TL-X":{"modbus tcp (ethernet)":"❌","rs485":"✅"},"MIC 3300TL-X":{"modbus tcp (ethernet)":"❌","rs485":"✅"},"MIC 600TL-X":{"modbus tcp (ethernet)":"❌","rs485":"N/A"},"MIC 750TL-X":{"modbus tcp (ethernet)":"❌","rs485":"✅"},"MID 100K-TL3-H":{"modbus tcp (ethernet)":"❌","rs485":"✅"},"MID 11-30K-TL3-XH":{"modbus tcp (ethernet)":"❌","rs485":"✅"},"MIN 2500-6000TL-X":{"modbus tcp (ethernet)":"❌","rs485":"✅"},"MIN 2500-6000TL-XH":{"modbus tcp (ethernet)":"❌","rs485":"✅"},"MIN 7000-10000TL-X":{"modbus tcp (ethernet)":"❌","rs485":"✅"},"MIN 7000-10000TL-X2":{"modbus tcp (ethernet)":"❌","rs485":"✅"},"MOD 3-10K-TL3-XH":{"modbus tcp (ethernet)":"❌","rs485":"✅"},"MOD 3-15K-TL3-X":{"modbus tcp (ethernet)":"❌","rs485":"✅"},"SPA 1000-3000TL BL":{"modbus tcp (ethernet)":"N/A","rs485":"✅"},"SPA 4000-10000TL3 BH-UP":{"modbus tcp (ethernet)":"❌","rs485":"✅"},"SPH 3000-6000TL BL-UP":{"modbus tcp (ethernet)":"❌","rs485":"✅"},"SPH 4000-10000TL3 BH-UP":{"modbus tcp (ethernet)":"❌","rs485":"✅"}},"Sunwoda":{"OSP-100K-A":{"modbus tcp (ethernet)":"✅","rs485":"✅"},"OSP-100K-B":{"modbus tcp (ethernet)":"✅","rs485":"✅"},"OSP-100K-C-2":{"modbus tcp (ethernet)":"✅","rs485":"✅"},"OSP-100K-C-3":{"modbus tcp (ethernet)":"✅","rs485":"✅"},"OSP-100K-H-2":{"modbus tcp (ethernet)":"✅","rs485":"✅"},"OSP-100K-H-3":{"modbus tcp (ethernet)":"✅","rs485":"✅"},"OSP-200K-A":{"modbus tcp (ethernet)":"✅","rs485":"✅"},"OSP-200K-A2":{"modbus tcp (ethernet)":"✅","rs485":"✅"},"OSP-200K-B":{"modbus tcp (ethernet)":"✅","rs485":"✅"},"OSP-200K-B2":{"modbus tcp (ethernet)":"✅","rs485":"✅"},"OSP-200K-C":{"modbus tcp (ethernet)":"✅","rs485":"✅"},"OSP-200K-C2":{"modbus tcp (ethernet)":"✅","rs485":"✅"},"OSP-200K-H":{"modbus tcp (ethernet)":"✅","rs485":"✅"},"OSP-200K-H2":{"modbus tcp (ethernet)":"✅","rs485":"✅"},"OSP-300K-A3":{"modbus tcp (ethernet)":"✅","rs485":"✅"},"OSP-400K-A2":{"modbus tcp (ethernet)":"✅","rs485":"✅"},"OSP-400K-A4":{"modbus tcp (ethernet)":"✅","rs485":"✅"},"SunESS-10H":{"modbus tcp (ethernet)":"❌","rs485":"✅"},"SunESS-15H":{"modbus tcp (ethernet)":"❌","rs485":"✅"},"SunESS-20H":{"modbus tcp (ethernet)":"❌","rs485":"✅"},"SunESS-5H":{"modbus tcp (ethernet)":"❌","rs485":"✅"}},"Solis":{"100-125K G5":{"modbus tcp (ethernet)":"experimental","rs485":"✅"},"S5-GC(100-110)K":{"modbus tcp (ethernet)":"✅ (only with Solis data logger)","rs485":"✅"},"S5-GC(25-40)K":{"modbus tcp (ethernet)":"✅ (only with Solis data logger)","rs485":"✅"},"S5-GC(50-60)K":{"modbus tcp (ethernet)":"✅ (only with Solis data logger)","rs485":"✅"},"S5-GC80K":{"modbus tcp (ethernet)":"✅ (only with Solis data logger)","rs485":"✅"},"S5-GR3P(3-20)K":{"modbus tcp (ethernet)":"✅ (only with Solis data logger)","rs485":"✅"},"S6-GC(80-125)K":{"modbus tcp (ethernet)":"✅ (only with Solis data logger)","rs485":"✅"},"S6-GC3P(40-60)K-NV-ND":{"modbus tcp (ethernet)":"✅ (only with Solis data logger)","rs485":"✅"},"S6-GC3P150K07-NV-ND":{"modbus tcp (ethernet)":"✅ (only with Solis data logger)","rs485":"✅"},"S6-GR1P(0.7-3.6)K-M":{"modbus tcp (ethernet)":"✅ (only with Solis data logger)","rs485":"✅"},"S6-GR1P(2.5-6)K":{"modbus tcp (ethernet)":"✅ (only with Solis data logger)","rs485":"✅"},"S6-GR1P(7-8)K02-NV-YD-HC":{"modbus tcp (ethernet)":"✅ (only with Solis data logger)","rs485":"✅"},"S6-GU350K-EHV":{"modbus tcp (ethernet)":"✅ (only with Solis data logger)","rs485":"✅"},"Solis 3t10K HVES G5":{"modbus tcp (ethernet)":"experimental","rs485":"✅"},"Solis S5-EA1P3K-L":{"modbus tcp (ethernet)":"✅ (only with Solis data logger)","rs485":"✅"},"Solis S5-EH1P(3-6)K-L":{"modbus tcp (ethernet)":"✅ (only with Solis data logger)","rs485":"✅"},"Solis S5-EH1P(8-10)K-L-PLUS":{"modbus tcp (ethernet)":"✅ (only with Solis data logger)","rs485":"✅"},"Solis S6-EA1P(3.6-6)K-L":{"modbus tcp (ethernet)":"✅ (only with Solis data logger)","rs485":"✅"},"Solis S6-EH3P(12-20)K-H":{"modbus tcp (ethernet)":"✅ (only with Solis data logger)","rs485":"✅"},"Solis S6-EH3P(30-50)K-H":{"modbus tcp (ethernet)":"✅ (only with Solis data logger)","rs485":"✅"},"Solis S6-EH3P(5-10)K-H-EU":{"modbus tcp (ethernet)":"✅ (only with Solis data logger)","rs485":"✅"},"Solis S6-EH3P(5-10)K2-H":{"modbus tcp (ethernet)":"✅ (only with Solis data logger)","rs485":"✅"},"Solis S6-EH3P(8-15)K02-NV-YD-L":{"modbus tcp (ethernet)":"✅ (only with Solis data logger)","rs485":"✅"},"Solis S6-EO1P(4-5)K-48-EU":{"modbus tcp (ethernet)":"✅ (only with Solis data logger)","rs485":"✅"},"Solis-255K-EHV-5G-PLUS":{"modbus tcp (ethernet)":"✅ (only with Solis data logger)","rs485":"✅"},"Solis-80K-5G-PRO":{"modbus tcp (ethernet)":"✅ (only with Solis data logger)","rs485":"✅"}},"Autarco":{"Autarco S2.LH10000-MI":{"modbus tcp (ethernet)":"✅ (Autarco LAN-stick required)","rs485":"✅"},"Autarco S2.LH6000":{"modbus tcp (ethernet)":"✅ (Autarco LAN-stick required)","rs485":"✅"},"Autarco S2.LH6000-MII":{"modbus tcp (ethernet)":"✅ (Autarco LAN-stick required)","rs485":"✅"},"Autarco S2.LQH15000":{"modbus tcp (ethernet)":"✅ (Autarco LAN-stick required)","rs485":"✅"},"Autarco S2.LQH20000":{"modbus tcp (ethernet)":"✅ (Autarco LAN-stick required)","rs485":"✅"},"Autarco S2.MH3600":{"modbus tcp (ethernet)":"✅ (Autarco LAN-stick required)","rs485":"✅"},"S2.LD6000-MIII":{"modbus tcp (ethernet)":"✅ (only supported with an Autarco LAN-stick)","rs485":"✅"},"S2.LQ12000-MIII":{"modbus tcp (ethernet)":"✅ (only supported with an Autarco LAN-stick)","rs485":"✅"},"S2.OX110000S":{"modbus tcp (ethernet)":"✅ (only supported with an Autarco LAN-stick)","rs485":"✅"}},"FoxESS":{"GMAX":{"modbus tcp (ethernet)":"✅","rs485":"❌"},"H1":{"modbus tcp (ethernet)":"✅","rs485":"✅"},"H1-G2":{"modbus tcp (ethernet)":"✅","rs485":"✅"},"H3 (Non-Pro, Non-Smart): → ❗See note below ❗":{"modbus tcp (ethernet)":"❌","rs485":"✅"},"H3 AIO (All-In-One)":{"modbus tcp (ethernet)":"✅","rs485":"✅"},"H3-Pro":{"modbus tcp (ethernet)":"✅","rs485":"✅"},"H3-Smart":{"modbus tcp (ethernet)":"✅","rs485":"✅"},"P3-SH":{"modbus tcp (ethernet)":"✅ (experimental)","rs485":"✅ (experimental)"},"R100":{"modbus tcp (ethernet)":"✅","rs485":"✅"}},"SolarEdge":{"SolarEdge SE2200H":{"modbus tcp (ethernet)":"✅","rs485":"✅"},"SolarEdge SE3.5K - SE33.3K":{"modbus tcp (ethernet)":"✅","rs485":"❌"},"SolarEdge SE3000H":{"modbus tcp (ethernet)":"✅","rs485":"✅"},"SolarEdge SE3500H":{"modbus tcp (ethernet)":"✅","rs485":"✅"},"SolarEdge SE3680H":{"modbus tcp (ethernet)":"✅","rs485":"✅"},"SolarEdge SE4000H":{"modbus tcp (ethernet)":"✅","rs485":"✅"},"SolarEdge SE5000H":{"modbus tcp (ethernet)":"✅","rs485":"✅"},"SolarEdge SE6000H":{"modbus tcp (ethernet)":"✅","rs485":"✅"}},"HYXiPOWER":{"All In One ESS (HYX-H12K-HTA)":{"modbus tcp (ethernet)":"❌","rs485":"✅"},"All In One ESS (HYX-H15K-HTA)":{"modbus tcp (ethernet)":"❌","rs485":"✅"},"All In One ESS (HYX-H6K-HTA)":{"modbus tcp (ethernet)":"❌","rs485":"✅"},"All In One ESS (HYX-H9K-HTA)":{"modbus tcp (ethernet)":"❌","rs485":"✅"},"Hybrid inverter Inverter (HYX-H10K-HT)":{"modbus tcp (ethernet)":"❌","rs485":"✅"},"Hybrid inverter Inverter (HYX-H12K-HT)":{"modbus tcp (ethernet)":"❌","rs485":"✅"},"Hybrid inverter Inverter (HYX-H15K-HT)":{"modbus tcp (ethernet)":"❌","rs485":"✅"},"Hybrid inverter Inverter (HYX-H20K-HT)":{"modbus tcp (ethernet)":"❌","rs485":"✅"},"Hybrid inverter Inverter (HYX-H25K-HT)":{"modbus tcp (ethernet)":"❌","rs485":"✅"},"Hybrid inverter Inverter (HYX-H5K-HT)":{"modbus tcp (ethernet)":"❌","rs485":"✅"},"Hybrid inverter Inverter (HYX-H6K-HT)":{"modbus tcp (ethernet)":"❌","rs485":"✅"},"Hybrid inverter Inverter (HYX-H8K-HT)":{"modbus tcp (ethernet)":"❌","rs485":"✅"}},"Solarlog":{"Solar-Log 400e Gateway":{"modbus tcp (ethernet)":"✅","rs485":"❌"}},"Solax":{},"Marstek":{"Venus-C (2.5kWh)":{"modbus tcp (ethernet)":"❌","rs485":"✅"}},"Dyness":{"DH100F (71~100kWh)":{"modbus tcp (ethernet)":"✅","rs485":"✅"},"DH200F (100kW/215kWh)":{"modbus tcp (ethernet)":"✅","rs485":"✅"},"DH200Y (100kW/232kWh)":{"modbus tcp (ethernet)":"✅","rs485":"✅"},"EC100 (100kWh)":{"modbus tcp (ethernet)":"✅","rs485":"✅"},"LS":{"modbus tcp (ethernet)":"✅","rs485":"✅"},"HT-A":{"modbus tcp (ethernet)":"✅","rs485":"✅"},"DH800Y (testing)":{"modbus tcp (ethernet)":"⚠️","rs485":"⚠️"}},"Xantrex":{"Xantrex Inverters (Models with RS232 interface)":{"modbus tcp (ethernet)":"❌","rs485":"❌"}},"SAJ":{"SAJ AS2":{"modbus tcp (ethernet)":"✅","rs485":"❌"},"SAJ CHS2":{"modbus tcp (ethernet)":"✅","rs485":"✅"},"SAJ H2 series-5k-30k":{"modbus tcp (ethernet)":"✅","rs485":"✅"},"SAJ HS2 series-5k-10k":{"modbus tcp (ethernet)":"✅","rs485":"✅"},"eManager-C1 Pro (testing)":{"modbus tcp (ethernet)":"⚠️","rs485":"❌"}},"Angile":{"Angile (AE10K-H-T)":{"modbus tcp (ethernet)":"❌","rs485":"✅"},"Angile (AES5.1-M)":{"modbus tcp (ethernet)":"❌","rs485":"✅"},"Angile (AESCB20)":{"modbus tcp (ethernet)":"❌","rs485":"✅"}},"Victron":{"Cerbo GX":{"modbus tcp (ethernet)":"✅","rs485":"❌"},"Inverters with built in GX device":{"modbus tcp (ethernet)":"✅","rs485":"❌"},"Multiplus II":{"modbus tcp (ethernet)":"✅","rs485":"❌"},"Multiplus RS":{"modbus tcp (ethernet)":"✅","rs485":"❌"},"Other Victron devices":{"modbus tcp (ethernet)":"✅","rs485":"❌"},"Venus GX":{"modbus tcp (ethernet)":"✅","rs485":"❌"}},"ESY":{"Sunhome Hybrid inverter Inverter (single phase) (HM6)":{"modbus tcp (ethernet)":"❌","rs485":"✅"}},"Greener":{"Alfen Battery Container (250 kWh – 2 MWh)":{"modbus tcp (ethernet)":"N/A","rs485":"N/A"}},"Cellpower":{"CESS":{"modbus tcp (ethernet)":"✅","rs485":"❌"}},"EP Equipment":{},"iWell":{"iWell Cube Battery (Experimental) (Cube Series)":{"modbus tcp (ethernet)":"✅","rs485":"❌"}},"Solplanet":{"ASW HT 250-360kW":{"modbus tcp (ethernet)":"❌","rs485":"✅"},"ASW LT 125kW":{"modbus tcp (ethernet)":"❌","rs485":"✅"},"ASW LT 75-110kW":{"modbus tcp (ethernet)":"❌","rs485":"✅"},"ASW LT-G2 Pro 3-20kW":{"modbus tcp (ethernet)":"❌","rs485":"✅"},"ASW LT-G3 25-40kW":{"modbus tcp (ethernet)":"❌","rs485":"✅"},"ASW LT-G3 45-60kW":{"modbus tcp (ethernet)":"❌","rs485":"✅"}},"Kehua":{"BCS1725K-B-HUD":{"modbus tcp (ethernet)":"✅","rs485":"✅"},"BCS200K-B-HM":{"modbus tcp (ethernet)":"✅","rs485":"✅"},"NXPCS":{"modbus tcp (ethernet)":"✅","rs485":"✅"}},"APsystems":{"APstorage":{"modbus tcp (ethernet)":"✅","rs485":"✅"}},"Sunwaytech":{"Inverters":{"modbus tcp (ethernet)":"✅","rs485":"❌"}},"Jinko":{"SunGiga":{"modbus tcp (ethernet)":"✅","rs485":"❌"}},"Octave energy":{"Battery Cabinet":{"modbus tcp (ethernet)":"✅","rs485":"❌"}},"Solarwatt":{"Vision One":{"modbus tcp (ethernet)":"✅","rs485":"✅"},"Vision Three":{"modbus tcp (ethernet)":"✅","rs485":"✅"}},"Sigenergy":{"Hybrid (-)":{"modbus tcp (ethernet)":"✅","rs485":"✅"},"PV Max (-)":{"modbus tcp (ethernet)":"✅","rs485":"✅"},"SigenStor (-)":{"modbus tcp (ethernet)":"✅","rs485":"✅"}},"DET Power":{"10ft Battery ESS (322kWh)":{"modbus tcp (ethernet)":"✅","rs485":"❌"}},"Dysun":{"FlexAmp (FlexAmp One 3.6K, FlexAmp One 5K)":{"modbus tcp (ethernet)":"❌","rs485":"✅"},"Hybrid inverter (Dysun Hybrid)":{"modbus tcp (ethernet)":"✅","rs485":"✅"}},"Fronius":{"Agilo":{"modbus tcp (ethernet)":"✅","rs485":"✅"},"Eco":{"modbus tcp (ethernet)":"✅","rs485":"✅"},"GEN24":{"modbus tcp (ethernet)":"✅","rs485":"✅"},"GEN24 Plus":{"modbus tcp (ethernet)":"✅","rs485":"✅"},"Primo":{"modbus tcp (ethernet)":"✅","rs485":"✅"},"Symo":{"modbus tcp (ethernet)":"✅","rs485":"✅"},"Tauro":{"modbus tcp (ethernet)":"✅","rs485":"✅"}},"Ateps":{"Storage Control System (Exide Technologies Battery Containers)":{"modbus tcp (ethernet)":"✅","rs485":"❌"}},"MidTeQ":{"PrimePower Hybrid inverter Inverter":{"modbus tcp (ethernet)":"✅","rs485":"✅"}},"Hite":{"BCCU (standalone)":{"modbus tcp (ethernet)":"✅","rs485":"❌"},"BESS (BCCU)":{"modbus tcp (ethernet)":"✅","rs485":"❌"},"BESS (ESMU)":{"modbus tcp (ethernet)":"✅","rs485":"❌"}},"Pylontech":{"C&amp;I Container A1000-OMNI via L-EMS":{"modbus tcp (ethernet)":"✅","rs485":"❌"},"C&amp;I Container A2000-OMNI via L-EMS":{"modbus tcp (ethernet)":"✅","rs485":"❌"},"C&amp;I Container L2200-OMNI via L-EMS":{"modbus tcp (ethernet)":"✅","rs485":"❌"},"C&amp;I Container L5000-BAT via L-EMS":{"modbus tcp (ethernet)":"✅","rs485":"❌"},"C&amp;I OPTIM US A100-HY via L-EMS":{"modbus tcp (ethernet)":"✅","rs485":"❌"},"C&amp;I OPTIM US A300-HY via L-EMS":{"modbus tcp (ethernet)":"✅","rs485":"❌"},"C&amp;I OPTIM US A329-BAT via L-EMS":{"modbus tcp (ethernet)":"✅","rs485":"❌"},"C&amp;I OPTIM US L260-OMNI via L-EMS":{"modbus tcp (ethernet)":"✅","rs485":"❌"},"C&amp;I OPTIM US L417-BAT via L-EMS":{"modbus tcp (ethernet)":"✅","rs485":"❌"}},"SCU":{"Battery container":{"modbus tcp (ethernet)":"✅","rs485":"❌"}},"Elecnova":{"ECO-215WS":{"modbus tcp (ethernet)":"✅","rs485":"❌"},"ECO-E233LS":{"modbus tcp (ethernet)":"✅","rs485":"❌"}},"Sus-Power":{},"a-TroniX":{"a-TroniX (1-ph)":{"modbus tcp (ethernet)":"❌","rs485":"✅"},"a-TroniX (3-ph)":{"modbus tcp (ethernet)":"❌","rs485":"✅"}},"AlphaESS":{},"Eenovance":{"E-MATE":{"modbus tcp (ethernet)":"✅","rs485":"❌"}},"Vacon":{"Vacon Solar 8000 (Solar Inverter)":{"modbus tcp (ethernet)":"❌","rs485":"✅"}},"Hithium":{"Hithium battery cabinets (HCL-DC261kWh-0.5P / HCL-125kW/261kWh-400)":{"modbus tcp (ethernet)":"✅","rs485":"❌"}},"Chisage":{"Jup (5-10G2-LE)":{"modbus tcp (ethernet)":"❌","rs485":"✅"},"Mars (5-14G2-LE)":{"modbus tcp (ethernet)":"❌","rs485":"✅"},"Merc (N/A)":{"modbus tcp (ethernet)":"❌","rs485":"✅"}},"Energreen":{"Hybrid":{"modbus tcp (ethernet)":"✅","rs485":"✅"},"PV Max":{"modbus tcp (ethernet)":"✅","rs485":"✅"},"Stor":{"modbus tcp (ethernet)":"✅","rs485":"✅"}},"Omnipower Qualtech":{"Qualtech Battery":{"modbus tcp (ethernet)":"✅","rs485":"❌"}},"Delta":{"Delta RPI (H3/H5/H3A/H4A/H5A (not tested))":{"modbus tcp (ethernet)":"❌","rs485":"✅"},"Delta RPI (M6/M8/M10/M12/M15A/M20A/M30)":{"modbus tcp (ethernet)":"❌","rs485":"✅"},"Delta RPI (M6A/M8A/M10A/M50A/M30A (not tested))":{"modbus tcp (ethernet)":"❌","rs485":"✅"}},"Renon":{"HV":{"modbus tcp (ethernet)":"❌","rs485":"✅"}},"Goodwe":{"Energy Storage (BH)":{"modbus tcp (ethernet)":"⚠️","rs485":"✅"},"Energy Storage (BT)":{"modbus tcp (ethernet)":"⚠️","rs485":"✅"},"Energy Storage (EH)":{"modbus tcp (ethernet)":"⚠️","rs485":"✅"},"Energy Storage (ES G2)":{"modbus tcp (ethernet)":"⚠️","rs485":"✅"},"Energy Storage (ET)":{"modbus tcp (ethernet)":"⚠️","rs485":"✅"},"Energy Storage (ET G2)":{"modbus tcp (ethernet)":"⚠️","rs485":"✅"},"Energy Storage (SBP G2)":{"modbus tcp (ethernet)":"❌","rs485":"✅"},"Energy Storage (Old models) (EM)":{"modbus tcp (ethernet)":"⚠️","rs485":"✅"},"Energy Storage (Old models) (ES)":{"modbus tcp (ethernet)":"⚠️","rs485":"✅"},"Energy Storage (Old models) (ESA)":{"modbus tcp (ethernet)":"❌","rs485":"✅"},"Energy Storage (Old models) (SBP)":{"modbus tcp (ethernet)":"❌","rs485":"✅"},"Grid-Tied (DNS)":{"modbus tcp (ethernet)":"⚠️","rs485":"✅"},"Grid-Tied (MS)":{"modbus tcp (ethernet)":"⚠️","rs485":"✅"},"Grid-Tied (MT)":{"modbus tcp (ethernet)":"❌","rs485":"✅"},"Grid-Tied (MT G2)":{"modbus tcp (ethernet)":"❌","rs485":"✅"},"Grid-Tied (SDT G2)":{"modbus tcp (ethernet)":"⚠️","rs485":"✅"},"Grid-Tied (SMT)":{"modbus tcp (ethernet)":"❌","rs485":"✅"},"Grid-Tied (XS)":{"modbus tcp (ethernet)":"⚠️","rs485":"✅"},"Grid-Tied C&amp;I (GT)":{"modbus tcp (ethernet)":"❌","rs485":"✅"},"Grid-Tied C&amp;I (HT)":{"modbus tcp (ethernet)":"❌","rs485":"✅"},"Residential (DNS G3)":{"modbus tcp (ethernet)":"⚠️","rs485":"✅"},"Residential (MS G3)":{"modbus tcp (ethernet)":"❌","rs485":"✅"},"Residential (SDT G3)":{"modbus tcp (ethernet)":"⚠️","rs485":"✅"},"Residential (XS G3)":{"modbus tcp (ethernet)":"⚠️","rs485":"✅"}},"Motoma":{"Elite Inverter (8KW / 12KW)":{"modbus tcp (ethernet)":"❌","rs485":"✅"}},"DEYE":{},"Gotion":{"ESC-R100-211-CE":{"modbus tcp (ethernet)":"✅","rs485":"✅"}},"Anklous":{"Energon Series (51.2V 280AH)":{"modbus tcp (ethernet)":"✅","rs485":"❌"}},"DMEGC":{},"Schneider sunezy":{"SunEzy 2000 / 2800 / 4000 (Single-phase string inverters)":{"modbus tcp (ethernet)":"❌","rs485":"✅"},"SunEzy 400E (Transformerless single-phase inverter)":{"modbus tcp (ethernet)":"❌","rs485":"✅"},"SunEzy 600E (Transformerless inverter, triple MPP input)":{"modbus tcp (ethernet)":"❌","rs485":"✅"}},"Beauvent":{"Beauvent Inverter (Modbus TCP)":{"modbus tcp (ethernet)":"✅","rs485":"❌"}},"WattsNext":{"WattsNext All-in-one Cabinet ES232/115K-A/EU":{"modbus tcp (ethernet)":"✅","rs485":"❌"}},"Enerlution":{"HYTH 5-15kW":{"modbus tcp (ethernet)":"❌","rs485":"✅"}},"Ecosourcen":{"Risen Storage (215kWh)":{"modbus tcp (ethernet)":"✅","rs485":"❌"},"Risen Storage – Golden Electronic V2 (in validation)":{"modbus tcp (ethernet)":"⚠️","rs485":"❌"}},"Kaco":{"blueplanet TL3 (50.0 / 60.0)":{"modbus tcp (ethernet)":"✅","rs485":"❌"},"blueplanet TL3 (87.0 / 92.0 / 105.0)":{"modbus tcp (ethernet)":"✅","rs485":"❌"}},"ABB, FIMER":{"All ABB inverters that support the Aurora PowerOne protocol (-)":{"modbus tcp (ethernet)":"✅","rs485":"✅"},"All other ABB inverters that support the Modbus Sunspec protocol (-)":{"modbus tcp (ethernet)":"✅","rs485":"✅"},"PVS Series (via Modbus Sunspec) (PVS-30, PVS-50, PVS-60)":{"modbus tcp (ethernet)":"✅","rs485":"✅"}},"Power-Sonic":{"PS-PULSE-INV-10KW":{"modbus tcp (ethernet)":"❌","rs485":"✅"},"PS-PULSE-INV-12KW":{"modbus tcp (ethernet)":"❌","rs485":"✅"},"PS-PULSE-INV-6KW":{"modbus tcp (ethernet)":"❌","rs485":"✅"},"PS-PULSE-INV-8KW":{"modbus tcp (ethernet)":"❌","rs485":"✅"}},"Reitec":{"Regitec Hybrid Inverter":{"modbus tcp (ethernet)":"✅","rs485":"✅"}},"Poweroad":{"Centric (A20)":{"modbus tcp (ethernet)":"✅","rs485":"⚠️"},"Centric (L20)":{"modbus tcp (ethernet)":"✅","rs485":"⚠️"},"Flex 126 (AIO)":{"modbus tcp (ethernet)":"✅","rs485":"⚠️"},"Flex 215 (AIO)":{"modbus tcp (ethernet)":"✅","rs485":"⚠️"},"Flex 215 (AIOS)":{"modbus tcp (ethernet)":"✅","rs485":"⚠️"},"Flex 233 (AIO)":{"modbus tcp (ethernet)":"✅","rs485":"⚠️"},"Flex 372 (Liquid Cooling)":{"modbus tcp (ethernet)":"✅","rs485":"⚠️"}},"Enphase":{"Gateway IQ local API":{"modbus tcp (ethernet)":"✅","rs485":"N/A"}},"Refurb":{"Zhero CESS Plant":{"modbus tcp (ethernet)":"✅","rs485":"❌"}},"Teplore":{"Tensorpack T Battery Rack":{"modbus tcp (ethernet)":"✅","rs485":"❌"}},"Afore":{"Single Phase (1-3kW)":{"modbus tcp (ethernet)":"❌","rs485":"✅"},"Single Phase (3-6kW)":{"modbus tcp (ethernet)":"❌","rs485":"✅"},"Single Phase (7-10kW)":{"modbus tcp (ethernet)":"❌","rs485":"✅"},"Three Phase (3-25kW)":{"modbus tcp (ethernet)":"❌","rs485":"✅"},"Three Phase (30kW)":{"modbus tcp (ethernet)":"❌","rs485":"✅"},"Three Phase (36-60kW)":{"modbus tcp (ethernet)":"❌","rs485":"✅"},"Three Phase (70-110kW)":{"modbus tcp (ethernet)":"❌","rs485":"✅"}},"Schuco":{"Whitelabeled Kaco inverters from before 2014":{"modbus tcp (ethernet)":"❌","rs485":"✅"}},"Ads-tec-storage":{"StoraXe Container ESS (Modular battery storage system)":{"modbus tcp (ethernet)":"✅","rs485":"❌"}},"Danfoss":{"TLX (Solar Inverter)":{"modbus tcp (ethernet)":"❌","rs485":"✅"}},"Kostal":{"Kostal Pico Inverters":{"modbus tcp (ethernet)":"✅","rs485":"✅"}},"Sinexcel":{"Isuna":{"modbus tcp (ethernet)":"❌","rs485":"✅"},"Sinexcel":{"modbus tcp (ethernet)":"✅","rs485":"❌"}},"Enbrilion":{"KorONE 233":{"modbus tcp (ethernet)":"✅","rs485":"✅"}},"Mastervolt":{"SunMaster CS10TL":{"modbus tcp (ethernet)":"❌","rs485":"✅"},"SunMaster CS12TL":{"modbus tcp (ethernet)":"❌","rs485":"✅"},"SunMaster CS15TL":{"modbus tcp (ethernet)":"❌","rs485":"✅"},"SunMaster CS20TL":{"modbus tcp (ethernet)":"❌","rs485":"✅"},"SunMaster CS30TL":{"modbus tcp (ethernet)":"❌","rs485":"✅"},"SunMaster ES4.6":{"modbus tcp (ethernet)":"❌","rs485":"✅"},"SunMaster IS10":{"modbus tcp (ethernet)":"❌","rs485":"✅"},"SunMaster IS15":{"modbus tcp (ethernet)":"❌","rs485":"✅"},"SunMaster XL10":{"modbus tcp (ethernet)":"❌","rs485":"✅"},"SunMaster XL15":{"modbus tcp (ethernet)":"❌","rs485":"✅"},"SunMaster XS2000":{"modbus tcp (ethernet)":"❌","rs485":"✅"},"SunMaster XS3200":{"modbus tcp (ethernet)":"❌","rs485":"✅"},"SunMaster XS4300":{"modbus tcp (ethernet)":"❌","rs485":"✅"},"SunMaster XS6500":{"modbus tcp (ethernet)":"❌","rs485":"✅"}},"Socomec":{"Energy Storage (HES L IEC)":{"modbus tcp (ethernet)":"✅","rs485":"❌"},"Energy Storage (HES L SKID)":{"modbus tcp (ethernet)":"✅","rs485":"❌"},"Energy Storage (HES XXL IEC)":{"modbus tcp (ethernet)":"✅","rs485":"❌"},"Energy Storage (HES XXL SKID)":{"modbus tcp (ethernet)":"✅","rs485":"❌"}},"Tesvolt":{"Energy Manager":{"modbus tcp (ethernet)":"✅","rs485":"❌"}},"Frax":{"Pylontech (XXL)":{"modbus tcp (ethernet)":"✅","rs485":"❌"}},"Fortona":{"Fortona 48TL200 (FZSoNick) (48TL200)":{"modbus tcp (ethernet)":"❌","rs485":"✅"}},"Sessy":{"Battery":{"modbus tcp (ethernet)":"✅","rs485":"❌"}},"C-Battery":{},"Hypontech":{"Hybrid Inverter (HES 3000/3680/4000/5000/6000, HHS 3000/3680/4000/5000/6000, HHT 5000/6000/8000/10000/12000/15000)":{"modbus tcp (ethernet)":"N/A","rs485":"✅"},"PV Ongrid Inverter, 1-Phase (HPK 1000/1500/2000/2500/3000, HPS 3000D/3680D/4000D/5000D/6000D, HPS 3000P/3680P/4000P/5000P/6000P)":{"modbus tcp (ethernet)":"N/A","rs485":"✅"},"PV Ongrid Inverter, 3-Phase (HPT 3000P/4000P/5000P/6000P/8000P/10000P/12000P/15000P, HPT 15KP/20KP/25KP/30KP, HPT 15K/17K/20K/22K/25K, HPT 30K/33K/36K/40K/50K, HPT 60K/70K/80K)":{"modbus tcp (ethernet)":"N/A","rs485":"✅"}},"Zeversolar":{"Solar Inverter":{"modbus tcp (ethernet)":"N/A","rs485":"❌"}},"EnjoyPowers":{"PCS cabinet":{"modbus tcp (ethernet)":"✅","rs485":"✅"}},"Tecloman":{"HPS":{"modbus tcp (ethernet)":"✅","rs485":"❌"},"TPCS-630":{"modbus tcp (ethernet)":"✅","rs485":"❌"}},"Volstora":{"Battery Containers":{"modbus tcp (ethernet)":"✅","rs485":"❌"}},"SolarMax":{"SolarMax (Inverters that support the SolarMax protocol)":{"modbus tcp (ethernet)":"❌","rs485":"✅"}},"Ritar":{"Enercube (100kW/200kWh)":{"modbus tcp (ethernet)":"✅","rs485":"✅"}},"Ampowr":{"Ampihome (Hybrid)":{"modbus tcp (ethernet)":"✅","rs485":"✅"},"Ampihome (Single-Phase)":{"modbus tcp (ethernet)":"❌","rs485":"✅"},"Ampihome (Three-Phase)":{"modbus tcp (ethernet)":"❌","rs485":"✅"}},"Solinteg":{"INTEG MHT-(25-50)K":{"modbus tcp (ethernet)":"✅","rs485":"✅"},"INTEG MHT-(4-20)K":{"modbus tcp (ethernet)":"✅","rs485":"✅"},"Solinteg-connected grid meter":{"modbus tcp (ethernet)":"✅","rs485":"✅"}},"Diehl-Ako":{"Platinum":{"modbus tcp (ethernet)":"❌","rs485":"✅"}},"Pixii":{"PowerShaper XL":{"modbus tcp (ethernet)":"✅","rs485":"❌"}},"RCT Power":{"CESS200":{"modbus tcp (ethernet)":"✅","rs485":"❌"}},"Dunext":{"PowerHill 261 (testing)":{"modbus tcp (ethernet)":"⚠️","rs485":"❌"}},"SAV":{"Efficiency King S2 (testing)":{"modbus tcp (ethernet)":"⚠️","rs485":"❌"}}}' />

### Switched loads
<CollapsibleBrandTable overviewDataJson='{"ShellyRelay":{"Shelly Gen3 (1 (Mini), 1PM (Mini), 2PM, 1L, 2L, AZ Plug, Plug S, EM)":{"modbus tcp (ethernet)":"✅","rs485":"N/A"},"Shelly Gen4 (1 (Mini), 1PM (Mini), 2PM, Plug US, PowerStrip)":{"modbus tcp (ethernet)":"✅","rs485":"N/A"},"Shelly Plus (1 (Mini), 1PM (Mini), 2PM, Uni)":{"modbus tcp (ethernet)":"✅","rs485":"N/A"},"Shelly Plus Plug (IT, S, US, UK)":{"modbus tcp (ethernet)":"✅","rs485":"N/A"},"Shelly Pro (1, 1PM, 2, 2PM, 3, 4PM, EM)":{"modbus tcp (ethernet)":"✅","rs485":"N/A"}},"Mystrom":{"WiFi Switch":{"modbus tcp (ethernet)":"✅","rs485":"❌"}},"HomeWizard":{}}' />

### Water meters
<CollapsibleBrandTable overviewDataJson='{"Eniris":{"Generic pulse water meter":{"modbus tcp (ethernet)":"❌","rs485":"❌"}},"Keyence":{"Keyence FD‑EC Series (FD‑ECA1 / FD‑ECA1C / FD‑ECA0 (Amplifier units))":{"modbus tcp (ethernet)":"✅","rs485":"❌"}},"HomeWizard":{},"Cadis":{"AQUAVISION CONTROL Module (Monitors up to 5 water meters and 3 valves)":{"modbus tcp (ethernet)":"✅","rs485":"✅"}}}' />


</div>

# New integrations


import { BrandName, ControllerName } from '@site/src/components/customFields';
import PdfLink from '@site/src/components/PdfLink';

## Write your own Modbus driver

For installers and integrators who want to build their own device integration, the standalone [Custom Modbus drivers guide](/Controller/Devices/custom-modbus-drivers/) explains how to write a driver from the manufacturer's register map. It includes the practical video, measurements, command logic and testing.

## Request a new integration

New integrations may be considered for inclusion and added to our roadmap.

Review the requirements and submit your request through the [Eniris integration request form](https://eniris.com/knowledge/integration-request-from).

For faster integration, be sure to:
- Look up / ask the communication protocol or API documentation to the manufacturer of the device and include it in your request.
- Include the contacts of the right technical persons of the manufacturer of your device.
- Provide a test installation.
- Include how many installations you already have with this device.

If you need a new integration with high priority, please contact the sales department of your redistributor.

Eniris evaluates submitted requests against the current product roadmap and available engineering capacity.


## For devices without a protocol
We kindly invite you to implement the <BrandName /> <ControllerName /> protocol, which will work out of the box with the <BrandName /> <ControllerName />.
<PdfLink url="/docs/eniris/ENIRIS_SMARTGRIDONE_EMS_AS_MODBUS_MASTER_V4_1.xlsx">You can download the specifications through this link.</PdfLink>

> [!NOTE]
> You can request to have the <BrandName /> <ControllerName /> protocol labeled with your brand in the software.
> Please use the [Eniris integration request form](https://eniris.com/knowledge/integration-request-from).


# EME eCON++ Fluvius Telecontrole v4 Gateway


import { BrandName, ControllerName } from '@site/src/components/customFields';

<img src="/img/sgo/Logo_EME.png" alt="EME Logo" style={{ display: "block", margin: "0 auto", width: "20%"}}/>

<br/>
# EME eCON++ Fluvius Telecontrole v4 Gateway

> [!WARNING] Prefer the native Fluvius Telecontrole support
> The <BrandName /> <ControllerName /> can talk to the Fluvius Telecontrole RTU directly, without an
> EME eCON++ Gateway or any other gateway in between. That setup is recommended and easier to commission, but it
> requires a <BrandName /> <ControllerName /> with two ethernet ports, because the Fluvius RTU is connected to a
> network port of its own. Only use the integration described on this page when the installation already has an
> EME eCON++ Gateway.
> See [Adding Fluvius Telecontrole RTU](/Controller/External%20Signals/DSO/fluvius#adding-fluvius-telecontrole-rtu).

On some medium voltage installations, Fluvius Telecontrole is not wired to the <BrandName /> <ControllerName />
directly, but through an **EME eCON++ Gateway** (Electro Mechanic Equipment nv, Glabbeek). This manual describes
what that gateway does and how to configure both halves of the integration.

## How the gateway works

Fluvius does not speak Modbus. The chain looks as follows:

```
Fluvius RTU  ──IEC 60870-5-104──►  IEC104 gateway  ──Modbus TCP──►  EME eCON++ Gateway  ──Modbus TCP──►  EMS controller
                                                                     (server/slave)                       (client/master)
```

The EME eCON++ Gateway is a **Modbus TCP server**; the <BrandName /> <ControllerName /> connects to it as a client
on port 502. The gateway mirrors the Fluvius telecontrol signals onto its Modbus registers:

- The **commands** coming from Fluvius (control mode, test operation, active and reactive power setpoint) are
  published on its input registers (3x).
- The **command feedback** is expected back on its holding registers (4x). The gateway relays that feedback to
  Fluvius. Fluvius uses it to confirm that the EMS received and accepted the command — if the feedback stops, the
  DSO no longer sees a working EMS.
- The **process data** measured by Fluvius at the access point (active and reactive power, the three phase-phase
  voltages) is also published on the input registers. Fluvius refreshes this data once per minute.

> [!IMPORTANT] The device and the external signal driver always go together
> The device driver only *reads* the Fluvius commands and answers the feedback handshake. It does not curtail
> anything by itself. Translating the setpoints into actual limits is done by the **Eme Fluvius Modbus TCP**
> external signal driver. An installation with only one of the two is not functional:
> - device without external signal driver → the Fluvius setpoints are recorded but never applied;
> - external signal driver without device → it reports *"No EME Modbus Device found in site devices."*

## Step 1: Network configuration

Connect the <BrandName /> <ControllerName /> to the ethernet switch of the EME eCON++ Gateway and give it a fixed
IP address in the same subnet as the gateway. The gateway must be reachable on **TCP port 502**. The IP addresses
and the Modbus unit address are site specific; ask EME or the panel builder for the ones used in your
installation.

The link between the Fluvius RTU, the IEC104 gateway and the EME eCON++ Gateway is configured by EME and is
outside the scope of the <BrandName /> <ControllerName />.

## Step 2: Configure the grid limits

Fluvius sends its setpoints as a **percentage**, and the <BrandName /> <ControllerName /> converts them into power
limits using the grid limits of the site. All four limits below must be filled in before the external signal
driver can work.

1. Under **Settings → Grid limits**, set *Allowed grid import power* and *Allowed grid export power*
   (see [Grid limits](/Controller/Configuration%20from%20A%20to%20Z/3-grid-limits/)). These are the 100 % reference for the
   active power setpoint. They are already requested during the initial setup of the site.
2. Under **Settings → Advanced settings**, set *Enable reactive power control (Experimental)* to **True**. The two
   reactive limits only appear once this is enabled.
3. Still under **Advanced settings**, set *Allowed grid import reactive power (kVAr)* and *Allowed grid export
   reactive power (kVAr)*. These are the 100 % reference for the reactive power setpoint.

> [!WARNING] The reactive limits are not optional
> Even when Fluvius only sends active power setpoints, the external signal driver reads all four limits on every
> remote control cycle. If the two reactive limits have never been saved on the site, the external signal driver
> fails and no Fluvius setpoint is applied at all. Open **Advanced settings** and save them explicitly, also when
> you keep the proposed values.

## Step 3: Add the gateway as a device

1. Go to **Devices** and start the wizard.
2. Choose the category **Energy meter**, brand **EME**, connection **Modbus TCP**, and select
   **EME eCON++ Fluvius Telecontrole v4 Gateway**.
3. Fill in the IP address and port (502) of the gateway and its Modbus unit address (1 by default).

The device reports the Fluvius commands and the access point measurements it reads from the gateway:

| Measurement | Meaning |
| --- | --- |
| `controlMode` | 0 = undefined, 1 = local control, 2 = remote control by Fluvius |
| `testOperation` | Test operation requested by the Fluvius RTU (0 = low, 1 = high) |
| `powerSetpointPercentage` | Active power setpoint from Fluvius, −100 % … +100 % |
| `reactivePowerSetpointPercentage` | Reactive power setpoint from Fluvius, −100 % … +100 % |
| `actualPowerTot_W`, `reacPowerTot_VAr` | Active and reactive power at the access point, as measured by Fluvius |
| `voltageL1L2_V`, `voltageL2L3_V`, `voltageL3L1_V` | Phase-phase voltages at the access point |

> [!WARNING] Not a grid meter
> These measurements come from Fluvius and are only refreshed once per minute. Do not use this device as the main
> grid meter of the site — the control algorithms need a meter that is read at the normal measurement interval.

## Step 4: Add the Fluvius Telecontrole external signal driver

1. Click **External Signals** in the top menu and start the wizard.
2. Choose **Distribution system operator / grid operator**, select **Fluvius**, then select
   **Eme Fluvius Modbus TCP** as the external signal driver and click *Next*.

There is nothing to fill in: the external signal driver takes everything it needs from the device and from the
grid limits of the site. See
[Fluvius (through an EME eCON++ gateway)](/External%20Signals/DSO/fluvius-eme-econ/).

## What the <BrandName /> <ControllerName /> does with the Fluvius commands

| Fluvius command | Behaviour of the <BrandName /> <ControllerName /> |
| --- | --- |
| Control mode = 0 (undefined) or 1 (local) | No action. The site keeps running on its own strategy. |
| Control mode = 2 (remote), active setpoint = 0 % | Import and export limit are both set to 0 W, so the site stops exchanging power with the grid. A small minimum band is kept for stability. |
| Control mode = 2, active setpoint > 0 % | Import limit = setpoint % × *Allowed grid import power*. |
| Control mode = 2, active setpoint &lt; 0 % | Export limit = setpoint % × *Allowed grid export power*. |
| Control mode = 2, reactive setpoint > 0 % | Reactive power setpoint = setpoint % × *Allowed grid import reactive power*. |
| Control mode = 2, reactive setpoint &lt; 0 % | Reactive power setpoint = setpoint % × *Allowed grid export reactive power*. |

Independently of the control mode, the device answers every command with the matching feedback and mirrors the
heartbeat back to the gateway, so Fluvius keeps seeing a responsive EMS.

Fluvius allows the installation up to **3 minutes** to settle on a new setpoint after it has changed.

## Verifying the installation

1. Open the device in the commissioning interface and check that `controlMode` and the setpoint percentages are
   being read. As long as Fluvius is in local control, the control mode is 1.
2. Check the feedback message of the external signal driver under **External Signals**. It reports whether Fluvius
   is in local control, or which setpoint is being applied.
3. Ask Fluvius to perform a test operation. The gateway raises `testOperation`, and
   the <BrandName /> <ControllerName /> answers it immediately.

## Troubleshooting

| Symptom | Cause |
| --- | --- |
| The external signal driver reports *"No EME Modbus Device found in site devices."* | The gateway device is not added, or is not communicating. Add it as described in step 3. |
| Setpoints are visible on the device, but nothing is curtailed | The external signal driver is not added, or the grid limits of the site are not completely configured — including the two reactive limits of step 2. |
| Fluvius reports that the EMS does not answer | The device is not communicating with the gateway, so the command feedback is no longer written. Check the IP address, port 502 and the Modbus unit address. |


# Fluvius Telecontrol through Third Party PLC


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import ClickableImage from '@site/src/components/ClickableImage';
import PdfLink from '@site/src/components/PdfLink';

# Fluvius Telecontrol through Third Party PLC

You can add a third party PLC to the <BrandName /> <ControllerName /> for Fluvius Telecontrol. The function of this PLC is twofold:
- It directly connects to the controlled devices.
- It combines the Fluvius Telecontrol signal with the control signals from the <BrandName /> <ControllerName />.

The PLC must be programmed to allow being added as a Modbus TCP slave to the <BrandName /> <ControllerName />. See also [PLC / Datalogger / Gateway as a slave](/Devices/PLC/plc-slave-protocol/) for more details and the Modbus registers that must be provided.

<img src="/img/generic/fluvius-telecontrol-through-plc-schematic.png" alt="RS485 Converter Logo" style={{ maxWidth: '1000px', display: 'block', margin: '0 auto' }} />

> [!WARNING] Adding devices that are controlled by the PLC directly to the EMS
> Do NOT add a device that is controlled by the PLC directly to the EMS. This could lead to conflicting control signals and doubly counted power values.

# Plc


import { FolderOverview } from '@/components/FolderOverview';

# Plc

<FolderOverview folder="Controller/Devices/PLC" />


# PLC / Datalogger / Gateway as a slave


import { BrandName, ControllerName } from '@site/src/components/customFields';
import { Download } from 'lucide-react'
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import ClickableImage from '@site/src/components/ClickableImage';
import PdfLink from '@site/src/components/PdfLink';
import DownloadButton from '@site/src/components/DownloadButton';

# PLC / Datalogger / Gateway as a slave

The <BrandName /> <ControllerName /> supports adding a PLC, Datalogger, Gateway or hub as a slave device through the <BrandName /> <ControllerName /> protocol.
This function is provided for when there is a hub that has to receive control signals itself from the <BrandName /> <ControllerName />.

When your device has implemented the protocol, you can add your device through the device wizard, choosing "Solar Inverter", "Generic", "Ethernet TCP" and "PLC (Generic protocol)".

## Protocol implementation
<DownloadButton file="/docs/eniris/EnirisSmartgridOneEMSasModbusMasterV4.xlsx" label="You can download the specifications of the protocol through this link." /> 


You have two options when implementing the protocol on the hub:
1. Or you only implement the data and control registers for the totals of all PV, storage etc. They are added in the <BrandName /> <ControllerName /> as one big aggregated device (or one EV charger, one energy meter, one hybrid inverter if applicable). 
2. Or you implement the data and control registers for each individual device. Each individual device is added in the <BrandName /> <ControllerName /> separately.

> [!WARNING] Adding devices that are controlled by the PLC directly to the EMS
> Do NOT add a device that is controlled by the PLC directly to the EMS. This could lead to conflicting control signals and doubly counted power values.

> [!WARNING] Aggregate device & groups
> In case your hub only implements the totals, the <BrandName /> <ControllerName /> will treat this as one big controllable aggregated device. You can still put the aggregated device in any group, just like any other device. However, there are a few things to keep in mind if the individual devices that form up the aggregated device are in reality spread among different groups:
> - The <BrandName /> <ControllerName /> will not be able to guard properly against overload on those groups.
> - The <BrandName /> <ControllerName /> will for those groups not be able to determine the complete path of all power. This may lead to the <BrandName /> <ControllerName /> seeing production by an "unknown source" or consumption by an "unknown load" if there are energy meters on those groups. Some power might be reported double.
>
> **If the devices behind the hub are spread out over different groups, you must implement the data and control registers for each individual device.**

## Examples
### A PLC that controls PV production and wants to accept a control signal from the <BrandName /> <ControllerName />
The premise of the <BrandName /> <ControllerName /> protocol in this case is that the <BrandName /> <ControllerName /> sees the PLC itself as a controllable PV inverter.

The minimum required if you want to control PV inverters through a PLC with a signal from the <BrandName /> <ControllerName />, is that the PLC:
1. tells the <BrandName /> <ControllerName /> that there is only PV;
2. returns how much PV power is produced in total by the inverters;
3. accepts the setpoints of the <BrandName /> <ControllerName />;

For point 1:
- Input register 0, (32 bit unsigned int), must contain the fixed value "0x454E4952" (protocol identification)
- Input register 100, (16 bit unsigned int), must contain the value "0", so the <BrandName /> <ControllerName /> knows that the PLC doesn't supply grid energy measurements.
- Input register 300, (16 bit unsigned int), must contain the value "1", so the <BrandName /> <ControllerName /> knows that there is PV.
- Input register 400, (16 bit unsigned int), must contain the value "0", so the <BrandName /> <ControllerName /> knows that there is no storage.

For point 2:
- Input register 202, (32 bit signed int), contains the AC power of the inverters. Negative is towards the grid, positive is from the grid.
- Input register 303, (32 bit unsigned int), contains the total PV production power in W. (Always a positive number)

For point 3:
- Holding register 1001, (16 bit unsigned int), will be set to "1" by the <BrandName /> <ControllerName /> if it wants to apply a control setpoint, or "0" when the PLC should fall back to its own control
- Holding register 1002, (32 bit unsigned int), will be set by the <BrandName /> <ControllerName /> and contains the maximum allowed PV production power in W. (Always a positive number)

> [!WARNING] Non-implemented registers
> **IMPORTANT: ALL NON-IMPLEMENTED REGISTERS MUST CONTAIN THE NON-IMPLEMENTED VALUE OF THEIR TYPE, AS DESCRIBED IN THE PROTOCOL.**
>
> The registers above are the absolute minimum required. The <BrandName /> <ControllerName /> will assume that all the PV that is connected to the PLC behaves as if it were a single PV inverter, with power factor 1 and symmetric three phase behaviour.
>
> If enhanced control is necessary, e.g. to keep an eye on phase currents etc., it is best to implement the recommended registers as well.


# a-TroniX


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/customers/a_tronix/logo.png"
    alt="a-TroniX"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

# a-TroniX Inverters

## Supported Devices

<DeviceSupportTable
  devices={[
    {
      type: "a-TroniX",
      variants: "1-ph",
      modbusTcp: "❌",
      rs485: "✅",
        curtailment: "✅"
    },
    {
      type: "a-TroniX",
      variants: "3-ph",
      modbusTcp: "❌",
      rs485: "✅",
        curtailment: "✅"
    }
  ]}
  showVariants={true}
  showModbusTcp={true}
  showRs485={true}
  showCurtailment={true} showReactivePower={true}
/>

<ClickableImage src="/media/a_tronix/inverter.jpg" alt="Image 1" maxWidth="450px" />

## Wiring

### RS485
The inverter can be connected to the <BrandName /> <ControllerName /> via RS485. This is done through connection [J] in the image below.
<RS485ConnectionTable firstColumn={["Logger 485A / pin 1", "Logger 485B / pin 2", "N/A"]} />

<ClickableImage src="/media/a_tronix/a_tronix-cables.png" alt="Image 1" maxWidth="450px" />

## Configuration

### 1. Activation monitoring & management inverter
The control must be activated through the inverter, and the meter must be deactivated. This is done through the display in the Feature Parm menu.
First, open the Feature Parm menu as follows:
1. Go to the Menu.
<ClickableImage src="/media/a_tronix/a_tronix-menu-1.png" alt="Image 1" maxWidth="250px" />
2. Enter the password. The default is 0000.
<ClickableImage src="/media/a_tronix/a_tronix-menu-2.png" alt="Image 1" maxWidth="250px" />
3. Select Settings.
<ClickableImage src="/media/a_tronix/a_tronix-menu-2.png" alt="Image 1" maxWidth="250px" />
4. Select Feature Parm

### 2. Activating remote control
Use the display further from the Feature page to activate the control, following the steps below:
1. Select Remote control
<ClickableImage src="/media/a_tronix/a_tronix-menu-4.jpg" alt="Image 1" maxWidth="250px" />
2. Set it to Enable
<ClickableImage src="/media/a_tronix/a_tronix-menu-5.jpg" alt="Image 1" maxWidth="250px" />

### 3. Deactivating meter
The meter must be deactivated. The control will be taken over by the <BrandName /> <ControllerName />. Therefore, the meter should not be connected to the inverter but to the <BrandName /> <ControllerName />. To deactivate the meter in the settings, follow these steps:
1. Go back to the Feature page.
2. Select Meter1
<ClickableImage src="/media/a_tronix/a_tronix-menu-6.jpg" alt="Image 1" maxWidth="250px" />
3. Select Set
<ClickableImage src="/media/a_tronix/a_tronix-menu-7.jpg" alt="Image 1" maxWidth="250px" />
4. Set it to Disable
<ClickableImage src="/media/a_tronix/a_tronix-menu-8.jpg" alt="Image 1" maxWidth="250px" />

### 4. Settings inverter address
The address of the inverter can also be set through the display.
1. Go to the Settings menu as described earlier.
2. Select Communication
3. Select RS485
4. Select Device ID
5. Set the device ID to the desired address.
If you connect multiple devices to the same RS485 bus, you must give each a unique address.

<ClickableImage src="/media/a_tronix/a_tronix-menu-9.jpg" alt="Image 1" maxWidth="250px" />

> [!TIP] 
> ### Faster scanning
> The <BrandName /> <ControllerName /> starts scanning from address 1 by default. Choosing a lower address will make your inverter be found faster.

> [!WARNING] 
> ### Multiple inverters
> If you have multiple inverters then it is important to set the parallel addresses, each inverter should have a different address.


# ABB, FIMER


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';
import Details from '@theme/Details';

# ABB, Fimer inverters

<img
    src="/img/customers/abb/fimer_abb.svg"
    alt="a-TroniX"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>


## Supported Devices
The <BrandName /> <ControllerName /> supports two protocols that widely used by Fimer ABB inverters.
By looking at the the inverter's data sheet, you can determine which protocol is supported by your inverter.
Any Fimer ABB inverter supports the "Modbus Sunspec" protocol.

All Fimer ABB inverters produced after 2022 support the SunSpec protocol.
For models produced before 2022, check the data sheet to see if it supports the "SunSpec" protocol.
Most models (also the older ones) support the "SunSpec" protocol.

__If Sunspec is supported, we recommend using the Sunspec protocol.__ If Sunspec is not supported, you can use the "Aurora Power One" protocol.


<DeviceSupportTable
  devices={[
    {
      type: "PVS Series (via Modbus Sunspec)",
      variants: "PVS-30, PVS-50, PVS-60",
      modbusTcp: "✅",
      rs485: "✅",
      curtailment: "✅",
        manual: "https://www.fimer.com/sites/default/files/PVS-50_60-TL-Product%20Manual%20EN-REVB.pdf"
    },
    {
      type: "All ABB inverters that support the Aurora PowerOne protocol",
      variants: "-",
      modbusTcp: "✅",
      rs485: "✅",
      curtailment: "❌"
    },
    {
      type: "All other ABB inverters that support the Modbus Sunspec protocol",
      variants: "-",
      modbusTcp: "✅",
      rs485: "✅",
      curtailment: "✅",
    }
  ]}
  showVariants={true}
  showModbusTcp={true}
  showRs485={true}
  showCurtailment={true} showReactivePower={true}
  showManual={true}
/>

<ClickableImage src="/img/customers/abb/PVS-50-60.jpg" alt="Image 1" maxWidth="450px" />

## Configuration
You need to configure the inverter to communicate with the <BrandName /> <ControllerName />.
The first step is to ensure that the Fimer ABB is connected to the same network as the <BrandName /> <ControllerName />.
For correct ethernet wiring: Follow the [the guidelines for ethernet wiring](/Controller/wiring-best-practices/#ethernet)


The second step is to find the Fimer ABB inverter's IP address and to open that address in a web browser.
This will open the inverter's web interface:
<ClickableImage src="/img/customers/abb/0.png" alt="Image 1" maxWidth="350px" />
Log in with a user that has __admin__ rights. Admin rights are required to change communication settings. If you do not have admin rights, you will see that certain options are unavailable.

<Details summary="I forgot the username or password for my admin account">
    Choose the "Forgot password" option on the login page. Find the product key on the inverter's label and enter it in the field.
    The product key is shown on the inverter's label as "Product Key" or "PK":
    For example:
    <ClickableImage src="/img/customers/abb/pk1.png" alt="Image 1" maxWidth="350px" />
    <ClickableImage src="/img/customers/abb/pk2.png" alt="Image 1" maxWidth="350px" />
</Details>
After logging in, you reach this page:
<ClickableImage src="/img/customers/abb/1.png" alt="Image 1" maxWidth="450px" />
Please proceed to the sections Modbus TCP or RS485, depending on your choice of communication.

### Modbus TCP (Ethernet)
On the left side menu, go to the '_Modbus_' settings page:
<ClickableImage src="/img/customers/abb/tcp1.png" alt="Image 1" maxWidth="350px" />
Ensure that the '_Communication protocol server_' is set to 'Sunspec'.
If Sunspec is not available, you can select 'Aurora Power One' as a protocol, but this will not support curtailment.
<ClickableImage src="/img/customers/abb/tcp2.png" alt="Image 1" maxWidth="350px" />
Modbus TCP is now enabled. In the<BrandName /> <ControllerName />, you can find and add this inverter on the same IP address.

### RS485
On the left side menu, go to the '_RS485_' settings page:
<ClickableImage src="/img/customers/abb/rtu1.png" alt="Image 1" maxWidth="350px" />

Multiple RS485 ports can be available on the inverter, but "Modbus Sunspec" is only supported on inverter connection **RS485-2**.
By default, the  <BrandName /> <ControllerName /> first scans for devices with a baud rate of `9600` and parity `None`. __We recommended to set baud rate and parity on this page accordingly__ and also verify that the __RS485 Node Address (same as bus address) is unique and no other device on the RS485 bus has the same address__:
<ClickableImage src="/img/customers/abb/rtu2.png" alt="Image 1" maxWidth="550px" />


Wire the inverter to the <BrandName /> <ControllerName /> as shown in the wiring diagram below.
Use the same RS485 port on the inverter as configured in the last step. In the example, this is RS485-2.
<ClickableImage src="/img/customers/abb/abb-pvs-50-60-connection.png" alt="Image 1" maxWidth="450px" />
<RS485ConnectionTable firstColumn={["+T/R", "-T/R", "RTN"]} />


# ADS-Tec


import { BrandName, ControllerName } from '@site/src/components/customFields';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
  src="/img/customers/ads-tec/tec_logo.png"
  alt="ADS-Tec"
  style={{ display: "block", margin: "0 auto", width: "40%" }}
/>

# ADS-Tec StoraXe Battery

> [!NOTE]
> This integration monitors ADS-Tec StoraXe modular battery containers via Modbus TCP on the <BrandName /> <ControllerName />. It provides read-only telemetry; curtailment and dispatch are not supported.

## Supported Devices

<DeviceSupportTable
  devices={[
    {
      type: "StoraXe Container ESS",
      variants: "Modular battery storage system",
      modbusTcp: "✅",
      rs485: "❌",
      curtailment: "❌"
    }
  ]}
  showVariants
  showModbusTcp
  showRs485
  showCurtailment
  showReactivePower={true}
/>

## Wiring

- Connect the StoraXe controller (or site gateway) to the LAN with an RJ45 Ethernet cable.
- Ensure TCP port **502** is open between the ADS-Tec controller and the <BrandName /> <ControllerName />.
- Follow the [Ethernet wiring best practices](/Controller/wiring-best-practices/#ethernet).

> The driver addresses Modbus Unit ID **1**. Leave the controller at this default; other IDs are ignored.

## Configuration

1. Power up the StoraXe controller and connect it to the site LAN.
2. Reserve or note the controller’s IP address so it remains reachable.
3. In the <BrandName /> <ControllerName /> UI, open **Devices → Add device**.
4. Select **Modbus TCP**, enter the StoraXe IP address, keep the unit ID at **1**, and click **Scan**.
5. Choose “ADS-Tec StoraXe” when it appears and press **Add**.

## Driver notes

- Device discovery relies on the StoraXe toggle bit (input register 6) alternating between 0 and 1. Keep this diagnostic register enabled; disabling it will prevent the integration from finding the system.
- The controller reads the serial number from registers 203–207. If those fields are blank, the integration falls back to a generated identifier.

# Afore

## Supported Devices

import Tabs from '@theme/Tabs';
import TabItem from '@theme/TabItem';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<DeviceSupportTable
  devices={[
    {
      type: "Single Phase (1-3kW)",
      modbusTcp: "❌",
      rs485: "✅",
      curtailment: "❌"
    },
    {
      type: "Single Phase (3-6kW)",
      modbusTcp: "❌",
      rs485: "✅",
      curtailment: "❌"
    },
    {
      type: "Single Phase (7-10kW)",
      modbusTcp: "❌",
      rs485: "✅",
      curtailment: "❌"
    },
    {
      type: "Three Phase (3-25kW)",
      modbusTcp: "❌",
      rs485: "✅",
      curtailment: "❌"
    },
    {
      type: "Three Phase (30kW)",
      modbusTcp: "❌",
      rs485: "✅",
      curtailment: "❌"
    },
    {
      type: "Three Phase (36-60kW)",
      modbusTcp: "❌",
      rs485: "✅",
      curtailment: "❌"
    },
    {
      type: "Three Phase (70-110kW)",
      modbusTcp: "❌",
      rs485: "✅",
      curtailment: "❌"
    }
  ]}
  showModbusTcp={true}
  showRs485={true}
  showCurtailment={true} showReactivePower={true}
/>

### Specific Models

<DeviceSupportTable
  devices={[
    {
      type: "AF1-3.6K-SL-1",
      modbusTcp: "❌",
      rs485: "✅",
      curtailment: "❌"
    },
    {
      type: "AF3-3.6K-SL",
      modbusTcp: "❌",
      rs485: "✅",
      curtailment: "❌"
    },
    {
      type: "AF4-6K-SLP",
      modbusTcp: "❌",
      rs485: "✅",
      curtailment: "❌"
    },
    {
      type: "AF1-6K-SL-0",
      modbusTcp: "❌",
      rs485: "✅",
      curtailment: "❌"
    },
    {
      type: "AF3-9.6K-DH",
      modbusTcp: "❌",
      rs485: "✅",
      curtailment: "❌"
    },
    {
      type: "AF3-15K-MTH",
      modbusTcp: "❌",
      rs485: "✅",
      curtailment: "❌"
    },
    {
      type: "AF3-30K-TH",
      modbusTcp: "❌",
      rs485: "✅",
      curtailment: "❌"
    },
    {
      type: "AF36-50K-TH",
      modbusTcp: "❌",
      rs485: "✅",
      curtailment: "❌"
    },
    {
      type: "AF3-12K-THP",
      modbusTcp: "❌",
      rs485: "✅",
      curtailment: "❌"
    },
    {
      type: "AF3-30K-TH-0",
      modbusTcp: "❌",
      rs485: "✅",
      curtailment: "❌"
    },
    {
      type: "AF3-12K-THP-0",
      modbusTcp: "❌",
      rs485: "✅",
      curtailment: "❌"
    }
  ]}
  showModbusTcp={true}
  showRs485={true}
  showCurtailment={true} showReactivePower={true}
/>

## Configuration

### 1. Accessing the Inverter's Interface

1. **Power On the Inverter**
   - Ensure the inverter is powered and operational

2. **Navigate to the Main Menu**
   - Use the inverter's display panel to access the main menu

### 2. Locating Communication Settings

1. **Enter the Settings Menu**
   - From the main menu, select 'Settings' or 'Advanced Settings'

2. **Find Communication Options**
   - Look for options labeled 'Communication', 'RS485', or 'Modbus'

### 3. Configuring Modbus Parameters

1. **Set Communication Protocol**
   - Choose 'Modbus RTU' as the protocol

2. **Adjust Communication Parameters**

   | Parameter | Value |
   |:---------:|:-----:|
   | Baud Rate | 9600 or 19200 bps |
   | Parity | None or Even |
   | Data Bits | 8 |
   | Stop Bits | 1 |

3. **Assign Modbus Address**
   - Provide a unique slave ID (e.g., 1, 2, etc.) for the inverter


# AlphaESS


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';


<img
    src="/img/customers/alphaESS/logo.jpg"
    alt="logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

# AlphaESS Inverters

AlphaESS is a leading global energy storage solution and service provider specializing in both residential and commercial applications. Their product range includes the SMILE and STORION series, offering reliable and efficient energy storage solutions.

## Supported Devices

{/* ### STORION Series

The STORION series offers high-power hybrid inverters designed for both residential and commercial applications. */}

<DeviceSupportTable
  devices = {[
    {
      type: "Storion Series",
      variants: "Storion G1 H30",
      modbusTcp: "✅",
      rs485: "❌",
      customCol: "• 30kW output power • Built-in energy management • Advanced monitoring capabilities",
      curtailment: "❌"
    }, {
      type: "Storion Series",
      variants: "Storion G2 H30",
      modbusTcp: "✅",
      rs485: "❌",
      customCol: "• 30kW output power • Dual communication options • Enhanced grid support features",
      curtailment: "✅"
    }, {
      type: "Storion Series",
      variants: "Storion G2 H50",
      modbusTcp: "✅",
      rs485: "❌",
      customCol: "• 50kW output power • Dual communication options • Enhanced grid support features",
      curtailment: "✅"
    }, {
      type: "Storion Series",
      variants: "Storion G3 H30",
      modbusTcp: "✅",
      rs485: "❌",
      customCol: "• 30kW output power • Dual communication options • Enhanced grid support features",
      curtailment: "✅"
    }, {
      type: "Storion Series",
      variants: "Storion G3 H50",
      modbusTcp: "✅",
      rs485: "❌",
      customCol: "• 50kW output power • Dual communication options • Enhanced grid support features",
      curtailment: "✅"
    }, {
      type: "Storion Series",
      variants: "Storion TB125",
      modbusTcp: "✅",
      rs485: "❌",
      customCol: "• 125kW output power • Dual communication options • Enhanced grid support features",
      curtailment: "✅"
    }, {
      type: "Smile Series",
      variants: "SMILE-5",
      modbusTcp: "⚠️",
      rs485: "✅",
      customCol: "• 5kW output power • Compact design • Residential optimization",
      curtailment: "❌",
      instructionVideos: [{"videoId": "j-BLL461WLI", "title": "AlphaESS SMILE5 · AL200", "description": "Models: SMILE-5 (AL200xxxxxx)."}, {"videoId": "BEEDwwZPKSE", "title": "AlphaESS SMILE5 · AL701", "description": "Models: SMILE-5 (AL701xxxxxx)."}]
    }, {
      type: "Smile Series",
      variants: "SMILE-B3",
      modbusTcp: "❌",
      rs485: "✅",
      customCol: "• Battery storage focus • Enhanced backup capabilities • Smart home integration",
      curtailment: "❌"
    }, {
      type: "Smile Series",
      variants: "SMILE-T10-HV",
      modbusTcp: "✅",
      rs485: "✅",
      customCol: "• 10kW output power • Three-phase system • Advanced grid management",
      curtailment: "❌",
      instructionVideos: [{"videoId": "1fExq4MH7RM", "title": "AlphaESS SMILE-T10-HV", "description": "Models: SMILE-T10-HV."}]
    }, {
      type: "Smile Series",
      variants: "SMILE-G3-S3.6/S5/B5",
      modbusTcp: "✅",
      rs485: "✅",
      customCol: "• 3.6/5kW output power • Single-phase system • Advanced grid management",
      curtailment: "❌",
      instructionVideos: [{"videoId": "IB6N1VWvYVk", "title": "AlphaESS SMILE-G3-S3.6 / S5 / B5", "description": "Models: SMILE-G3-S3.6, SMILE-G3-S5, SMILE-G3-B5."}]
    }, {
      type: "Smile Series",
      variants: "SMILE-G3-T4/T5/T6/T8/T10/T15/T20",
      modbusTcp: "✅",
      rs485: "✅",
      customCol: "• 4/5/6/8/10/15/20kW output power • Three-phase system • Advanced grid management",
      curtailment: "❌",
      instructionVideos: [{"videoId": "pcgLbOaL30M", "title": "AlphaESS SMILE-G3-T15 / T20", "description": "Models: SMILE-G3-T15, SMILE-G3-T20."}, {"videoId": "_M9lcxBoB2c", "title": "AlphaESS SMILE-G3-T4 / T5 / T6 / T8 / T10", "description": "Models: SMILE-G3-T4, SMILE-G3-T5, SMILE-G3-T6, SMILE-G3-T8, SMILE-G3-T10."}]
    }
  ]}
  showModbusTcp
  showRs485
  showVariants
  customColumns={{ "customCol": "Key Features" }}
  showCurtailment
  showReactivePower={true}
/>

> [!WARNING]
> For Smile 5:\
> • SN starting with AL701XXXXXX → Modbus TCP supported.\
> • SN starting with AL200XXXXXX → Modbus RTU (RS485) only.

{/* ### SMILE Series

The SMILE series provides flexible solutions for residential energy storage needs. */}


## Communication Options

### Ethernet (Modbus TCP)
All AlphaESS inverters support Modbus TCP communication through their ethernet port. This provides:
- Fast and reliable communication
- Easy integration with home networks
- Remote monitoring capabilities

### RS485
Most models (except STORION-H30) support RS485 communication, offering:
- Reliable long-distance communication
- Multiple device daisy-chaining
- Industry-standard protocol support

## Wiring

### Ethernet Connection
For correct ethernet wiring, follow the [guidelines for ethernet wiring](/Controller/wiring-best-practices/#ethernet).

### RS485 Connection
For models supporting RS485:
<RS485ConnectionTable firstColumn={["RS485 A", "RS485 B", "GND"]} />
- Use shielded twisted pair cable
- Maximum cable length: 1000m
- Maintain proper polarity (A to A, B to B)

## Configuration

### Network Setup
1. Connect the inverter to your local network via ethernet cable
2. Make sure your IP address is in the same subnet as the <ControllerName/>


<ClickableImage src="/img/customers/alphaESS/AlphaESS_IP.jpg" alt="AlphaESS IP Configuration"/>




# Alpvolt


import { BrandName, ControllerName } from '@site/src/components/customFields';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';


<img
    src="/img/customers/alpvolt/Logo_Alpvolt.png"
    alt="Alpvolt"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

# Alpvolt

## Supported Devices

<DeviceSupportTable
  devices={[
    {
      type: "Powerbox 261",
      modbusTcp: "✅",
      rs485: "❌",
    }
  ]}
  showModbusTcp={true}
  showRs485={true}
  showReactivePower={true}
/>

## Configuration

### Ethernet Connection
Make sure that the Controller and the Powerbox 261 are connected to the same network.
For correct ethernet wiring, follow the [guidelines for ethernet wiring](/Controller/wiring-best-practices/#ethernet).


# Ampowr


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/sgo/Logo_Ampowr.png"
    alt="Ampowr"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

# Ampowr Inverters

## Supported Devices

<DeviceSupportTable
  devices={[
    {
      type: "Ampihome",
      variants: "Single-Phase",
      modbusTcp: "❌",
      rs485: "✅",
      curtailment: "❌"
    },
    {
      type: "Ampihome",
      variants: "Three-Phase",
      modbusTcp: "❌",
      rs485: "✅",
      curtailment: "✅"
    },
    {
      type: "Ampihome",
      variants: "Hybrid",
      modbusTcp: "✅",
      rs485: "✅",
      curtailment: "✅"
    }
  ]}
  showVariants={true}
  showModbusTcp={true}
  showRs485={true}
  showReactivePower={true}
/>

## Wiring

The <BrandName /> <ControllerName /> and the Ampihone inverters communicate via RS485 or Ethernet.

### Ethernet
For correct ethernet wiring: Follow the [the guidelines for ethernet wiring](/Controller/wiring-best-practices/#ethernet).

### RS485
<RS485ConnectionTable firstColumn={["Pin 7 (White-Brown)", "Pin 8 (Brown)", "N/A"]} />

<ClickableImage src="/media/ampowr/ampihome-single-wiring.jpg" alt="Ampihome Single Phase Wiring" maxWidth="100%" />

> [!WARNING] I can't find my Ampihome inverter
> For Ampowr hybrid inverters, the default bus addresses are 247 for Modbus RTU and 255 for Modbus TCP.
> The <BrandName /> <ControllerName /> will scan for devices on all addresses from 1 to 255.
> __Therefore, it can take a while to scan for devices.__
>
> __TIP:__ If you know the bus address of your inverter, you can set it in the <BrandName /> <ControllerName /> to speed up the scanning process.


## Configuration
### Ampihome Single-Phase

The Ampihome Single-Phase needs to be set to Slave Secondary Port:
    1. Open the ESS Link app
    2. Select "My" in the bottom-right corner
    3. Select "My Device"
    4. Select on the device's "Comm No."
    5. Select "Parameter Settings"
    6. Set "Working Mode" to "Timed Charge Mode (C&D)"
    7. Select "Advanced" in the top-right corner
    8. Set "BMS1 RS485 Multiplexing" to "Slave Secondary Port"

<ClickableImage src="/media/ampowr/ampihome-single-1.png" alt="Ampihome Settings 1" maxWidth="100%" />

<ClickableImage src="/media/ampowr/ampihome-single-2.png" alt="Ampihome Settings 2" maxWidth="100%" />

<RS485AddressNote />

# Angile


import { BrandName, ControllerName } from '@site/src/components/customFields';
import ClickableImage from '@site/src/components/ClickableImage';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/customers/angile/logo.png"
    alt="logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

## Supported Devices 

<DeviceSupportTable
  devices={[
    {
        type: "Angile",
        variants: "AE10K-H-T",
        modbusTcp: "❌",
        rs485: "✅",
        curtailment: "❌"
    },
    {
        type: "Angile",
        variants: "AESCB20",
        modbusTcp: "❌",
        rs485: "✅",
        curtailment: "❌"
    },
    {
        type: "Angile",
        variants: "AES5.1-M",
        modbusTcp: "❌",
        rs485: "✅",
        curtailment: "❌"
    }
  ]}
  showVariants={true}
  showModbusTcp={true}
  showRs485={true}
  curtailment={true}
  showReactivePower={true}
/>

## Wiring

### RS485

To connect te Angile to RS485 you need to connect it through the D-B/485 port on the inverter.

<RS485ConnectionTable firstColumn={["Pin 5 (Blue-White)", "Pin 4 (Blue)", ""]} />
<ClickableImage src="/img/customers/angile/connection.png" alt="Image" maxWidth="450px" />

## Configuration
<RS485AddressNote/>


# Anklous PV, Hybrid and Battery Inverters


import { BrandName, ControllerName } from '@site/src/components/customFields';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';


<img
    src="/img/customers/anklous/Logo_Anklous.png"
    alt="Anklous"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

# Anklous PV, Hybrid and Battery Inverters

## Supported Devices

<DeviceSupportTable
  devices={[
    {
      type: "Energon Series",
      variants: "51.2V 280AH",
      modbusTcp: "✅",
      rs485: "❌",
      curtailment: "✅",

    },
    {
      type: "Smart261kWh Liquid",
      variants: "51.2V 280AH",
      modbusTcp: "✅",
      rs485: "❌",
      curtailment: "❌",
    }
  ]}
  showVariants={true}
  showModbusTcp={true}
  showRs485={true}
  showCurtailment={true} showReactivePower={true}
/>

## Wiring
The communication between the <BrandName /> <ControllerName /> and the Anklous inverters operates via Modbus TCP.
For correct ethernet wiring: Follow the [the guidelines for ethernet wiring](/Controller/wiring-best-practices/#ethernet).

### Energon Series

No settings need to be made on the Anklous Energon Series inverters.
The Modbus TCP connection is established via the LAN port on the inverter.
After adding the battery through the <BrandName /> <ControllerName /> interface, control will be established automatically.

### Smart261L

No settings need to be made on the Anklous Smart261kWh Liquid.
The Modbus TCP connection is established via the LAN port on the inverter.
After adding the battery through the <BrandName /> <ControllerName /> interface, control will be established automatically.

# APsystems


import { BrandName, ControllerName } from '@site/src/components/customFields';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';


<img
    src="/img/customers/apsystems/Logo_APsystems.png"
    alt="APsystems"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

# APsystems

## Supported Devices

<DeviceSupportTable
  devices={[
    {
      type: "APstorage",
      modbusTcp: "✅",
      rs485: "✅",
      curtailment: "❌",
    },
    {
      type: "ECU",
      modbusTcp: "✅",
      rs485: "✅",
      curtailment: "⚠️",
    }
  ]}
  showModbusTcp={true}
  showRs485={true}
  showCurtailment={true} showReactivePower={true}
/>

## Configuration

### Ethernet Connection
Make sure that the Controller and the APstorage are connected to the same network.
For correct ethernet wiring, follow the [guidelines for ethernet wiring](/Controller/wiring-best-practices/#ethernet).

### RS485 Connection
For RS485 wiring, follow the [guidelines for RS485 wiring](/Controller/wiring-best-practices/#rs485).


# Ateps Battery


import { BrandName, ControllerName } from '@site/src/components/customFields';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
  src="/img/sgo/Logo_Ateps.png"
  alt="Ateps"
  style={{ display: "block", margin: "0 auto", width: "40%" }}
/>

# Ateps

> [!NOTE]
> This integration connects Ateps Storage Control System battery containers to the <BrandName /> <ControllerName /> via Modbus TCP. It supports monitoring and remote power control.

## Supported Devices

<DeviceSupportTable
  devices={[
    {
      type: "Storage Control System",
      variants: "Exide Technologies Battery Containers",
      modbusTcp: "✅",
      rs485: "❌",
      curtailment: "✅"
    }
  ]}
  showVariants
  showModbusTcp
  showRs485
  showCurtailment
  showReactivePower={true}
/>

## Wiring

- Connect the Ateps controller (or site gateway) to the LAN with an RJ45 Ethernet cable.
- Confirm TCP port **502** is open between the Ateps device and the <BrandName /> <ControllerName />.
- Follow the [Ethernet wiring best practices](/Controller/wiring-best-practices/#ethernet).

> The integration uses Modbus TCP only. Unit ID **1** is scanned by default.

## Configuration

### 1. Network
1. Power up the Ateps controller and connect it to the site LAN.
2. Reserve or note the controller’s IP address so it remains reachable.

### 2. Ateps settings
1. Log in to the Ateps interface with an admin account.
2. Enable the Modbus TCP server on port **502** and keep the Unit ID at **1**.
3. Save the changes (reboot if requested).

### 3. Add the device in <ControllerName />
1. In the <BrandName /> <ControllerName /> UI, open **Devices → Add device**.
2. Choose **Modbus TCP**, enter the Ateps IP address, and leave the unit ID at **1**.
3. Start the scan, select “Ateps Storage Control System” when it appears, and click **Add**.

## Remote power control (optional)

When site policies allow curtailment:

1. Enable smart grid control for the device in the <BrandName /> <ControllerName />.
2. Set the desired power target (positive values request charging, negative values request discharging).
3. To stop control, disable smart grid mode; the controller will release the battery.

## Troubleshooting

- **Device not detected:** Check IP reachability and ensure port 502 is open. Verify the Modbus TCP server is enabled.
- **No telemetry updates:** Confirm the Ateps device reports a valid state of charge (0.0–1.0). Restart the Modbus service if needed.
- **Control commands ignored:** Make sure smart grid mode is enabled and the site allows external dispatch requests.

# Autarco Hybrid Inverters


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';
import Mermaid from '@theme/Mermaid';

<img
    src="/img/customers/autarco/logo.png"
    alt="logo"
    style={{ display: "block", margin: "0 auto", width: "40%" }}
/>

# Autarco Hybrid Inverters
The Autarco hybrid inverters are designed for both solar energy generation and battery storage, providing a versatile solution for energy management. The <BrandName /> <ControllerName /> supports the Autarco hybrid inverters product line.
## Supported Devices

<ClickableImage src="/img/customers/autarco/lqh.png" alt="Image" maxWidth="450px" />

<DeviceSupportTable
  devices={[
    { type: 'Autarco S2.MH3600', manual: '/img/customers/autarco/MH.pdf', modbusTcp: '✅ (Autarco LAN-stick required)', rs485: '✅', curtailment: "✅" },
    { type: 'Autarco S2.LH6000', manual: '/img/customers/autarco/LH.pdf', modbusTcp: '✅ (Autarco LAN-stick required)', rs485: '✅', curtailment: "✅" },
    { type: 'Autarco S2.LH6000-MII',manual: '/img/customers/autarco/LH.pdf',  modbusTcp: '✅ (Autarco LAN-stick required)', rs485: '✅', curtailment: "✅" },
    { type: 'Autarco S2.LH10000-MI', manual: '/img/customers/autarco/LH.pdf', modbusTcp: '✅ (Autarco LAN-stick required)', rs485: '✅', curtailment: "✅" },
    { type: 'Autarco S2.LQH15000', manual: '/img/customers/autarco/LQH.pdf', modbusTcp: '✅ (Autarco LAN-stick required)', rs485: '✅', curtailment: "✅" },
    { type: 'Autarco S2.LQH20000', manual: '/img/customers/autarco/LQH.pdf', modbusTcp: '✅ (Autarco LAN-stick required)', rs485: '✅', curtailment: "✅" },
  ]}
  showModbusTcp={true}
  showRs485={true}
  showCurtailment={true} showReactivePower={true}
  showManual={true}
/>

> [!WARNING]
> The SmartgridOne Controller works best with communication stick firmware 100101B0.

## Wiring (Modbus TCP)
> [!NOTE]
> The information below is based on Autarco's official guidance. Check the [Autarco energy-management help center](https://help.autarco.com/en/services) for the latest instructions.
To enable TCP/IP you need the following:

- Communication: S2.LAN.STICK.D (see the [Autarco hardware help center](https://help.autarco.com/en/hardware))
- Communication stick firmware: equal to 100101B0
When the firmware is correct TCP/IP is enabled.

_How to update the firmware version?_
→ Updating the firmware version of the communication stick is currently possible via Digital O&M in Helios. Check the [Autarco software help center](https://help.autarco.com/en/software) for the latest procedure.
## Wiring (RS485)
The wiring between the <BrandName/> <ControllerName/> and the Autarco can be done with the following guides:
<table>
  <thead>
    <tr>
      <th>Model</th>
      <th>Page</th>
    </tr>
  </thead>
  <tbody>
    <tr><td>S2.MH3600</td><td><a href="/Devices/PV-hybrid-and-battery-inverters/Autarco/Hybrid/MH-series">Wiring configuration for MH-series</a></td></tr>
    <tr><td>S2.LH6000</td><td rowspan="3"><a href="/Devices/PV-hybrid-and-battery-inverters/Autarco/Hybrid/LH-series">Wiring configuration for LH-series</a></td></tr>
    <tr><td>S2.LH6000-MII</td></tr>
    <tr><td>S2.LH10000-MI</td></tr>
    <tr><td>S2.LQH15000</td><td rowspan="2"><a href="/Devices/PV-hybrid-and-battery-inverters/Autarco/Hybrid/LQH-series">Wiring configuration for LQH-series</a></td></tr>
    <tr><td>S2.LQH20000</td></tr>
  </tbody>
</table>
If your model is not listed, we refer to the manual of the Autarco inverter. It should always include a section on how to wire a rs485 communication with external EMS-systems.


# Autarco LH-series RS485 wiring

import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/customers/autarco/LH.png"
    alt="logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>
This page describes the communication with an Autarco LH-series hybrid inverter over Modbus-RTU (rs485). 
By default, the inverter is set to address 1. The RS485 interface is a 4-pin connector called "COM" located on the bottom of the inverter 
behind a protective plate. The exact position is marked in the orange box in the image below:
<ClickableImage src="/img/customers/autarco/LH-com.png" alt="Image" maxWidth="450px" />
Looking closer the port looks like this:
<ClickableImage src="/img/customers/solis/3t10K-HVES-G5-wiring.png" alt="Image" maxWidth="450px" />
An appropriate connector should be used for this 4-pin connector on the Autarco inverter to connect to the <BrandName /> <ControllerName />.
On the <BrandName /> <ControllerName />, the inverter can be connected to the RS485 port. The wiring is as follows:
<RS485ConnectionTable firstColumn={["Pin 3", "Pin 4", "N/A"]} />

<RS485AddressNote />


# Autarco LQH-series RS485 wiring

import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/customers/autarco/lqh.png"
    alt="logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>
This page describes the communication with an Autarco LqH-series hybrid inverter over Modbus-RTU (rs485). 
By default, the inverter is set to address 1. The RS485 communication happens over a RJ45 interface called located on the bottom of the inverter 
behind a protective plate. The exact position is marked in the orange box in the image below:
<ClickableImage src="/img/customers/autarco/lqh-com1.png" alt="Image" maxWidth="650px" />
The pin definition of the RS485 Port is following (EIA/TIA 568B):
- RS485A on Pin 5: blue/white
- RS485B on Pin 4: blue
<ClickableImage src="/img/customers/autarco/lqh-com2.png" alt="Image" maxWidth="250px" />


<RS485AddressNote />


After a successful RS485 connection and communication with the <BrandName /> <ControllerName /> over the Modbus-RTU protocol, 
the Autarco inverter will now show a new blue icon on its status indicator panel:
<img
    src="/img/customers/autarco/lqh-status.png"
    alt="logo"
    style={{ display: "block", margin: "0 auto", width: "80%"}}
/>

# Autarco MH-series RS485 wiring

import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/customers/autarco/MH.png"
    alt="logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>
This page describes the communication with an Autarco LH-series hybrid inverter over Modbus-RTU (rs485). 
By default, the inverter is set to address 1. The RS485 interface is a 4-pin connector called "COM" located on the bottom of the inverter 
behind a protective plate. The exact position is marked in the orange box in the image below:
<ClickableImage src="/img/customers/autarco/MH-com.png" alt="Image" maxWidth="450px" />
Looking closer the port looks like this:
<ClickableImage src="/img/customers/solis/3t10K-HVES-G5-wiring.png" alt="Image" maxWidth="450px" />
An appropriate connector should be used for this 4-pin connector on the Autarco inverter to connect to the <BrandName /> <ControllerName />.
On the <BrandName /> <ControllerName />, the inverter can be connected to the RS485 port. The wiring is as follows:
<RS485ConnectionTable firstColumn={["Pin 3", "Pin 4", "N/A"]} />

<RS485AddressNote />


# Autarco


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import ClickableImage from '@site/src/components/ClickableImage';
import ClickableVideo from '@site/src/components/ClickableVideo';

<img
    src="/img/customers/autarco/logo.png"
    alt="logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

The <BrandName /> <ControllerName /> support the Autarco solar-only and hybrid inverters product lines.
Continue to the guide for the specific product line you are interested in:

<div style={{
  display: 'flex',
  gap: '20px',
  marginTop: '2rem',
  justifyContent: 'center'
}}>
  <a href="/Controller/Devices/PV-hybrid-and-battery-inverters/Autarco/On-grid/" className="autarco-choice-button" style={{
    padding: '2rem',
    backgroundColor: '#007bff',
    borderRadius: '10px',
    textDecoration: 'none',
    color: 'white',
    flex: 1,
    maxWidth: '300px',
    textAlign: 'center',
    boxShadow: '0 2px 4px rgba(0,0,0,0.1)',
    transition: 'transform 0.2s, box-shadow 0.2s, background-color 0.2s',
    cursor: 'pointer'
  }}>
    <h3 style={{ margin: '0 0 1rem 0', color: 'white' }}>On-grid line:</h3>
    <p style={{ margin: '0', color: 'rgba(255,255,255,0.9)' }}>S2.LD6000-MIII</p>
    <p style={{ margin: '0', color: 'rgba(255,255,255,0.9)' }}>S2.OX110000S</p>
    <p style={{ margin: '0', color: 'rgba(255,255,255,0.9)' }}>S2.LQ12000-MIII</p>
  </a>
  
  <a href="/Controller/Devices/PV-hybrid-and-battery-inverters/Autarco/Hybrid/" className="autarco-choice-button" style={{
    padding: '2rem',
    backgroundColor: '#007bff',
    borderRadius: '10px',
    textDecoration: 'none',
    color: 'white',
    flex: 1,
    maxWidth: '300px',
    textAlign: 'center',
    boxShadow: '0 2px 4px rgba(0,0,0,0.1)',
    transition: 'transform 0.2s, box-shadow 0.2s, background-color 0.2s',
    cursor: 'pointer'
  }}>
    <h3 style={{ margin: '0 0 1rem 0', color: 'white' }}>Hybrid line:</h3>
    <p style={{ margin: '0', color: 'rgba(255,255,255,0.9)' }}>S2.MH3600</p>
    <p style={{ margin: '0', color: 'rgba(255,255,255,0.9)' }}>S2.LH6000</p>
    <p style={{ margin: '0', color: 'rgba(255,255,255,0.9)' }}>S2.LH6000-MII</p>
    <p style={{ margin: '0', color: 'rgba(255,255,255,0.9)' }}>S2.LH10000-MI</p>
    <p style={{ margin: '0', color: 'rgba(255,255,255,0.9)' }}>S2.LQH15000</p>
    <p style={{ margin: '0', color: 'rgba(255,255,255,0.9)' }}>S2.LQH20000</p>
  </a>
</div>

<style>
{`
  .autarco-choice-button:hover {
    transform: translateY(-2px);
    box-shadow: 0 4px 8px rgba(0,0,0,0.2);
    background-color: #0056b3 !important;
  }
`}
</style>

# Autarco On-grid Inverters


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/customers/autarco/logo.png"
    alt="logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>


# Autarco On Grid Inverters
The Autarco on grid inverters are designed for solar energy generation. The <BrandName /> <ControllerName /> supports the Autarco on-grid inverters product line.

## Supported Devices
<div style={{ display: "flex", gap: "10px", justifyContent: "left" }}>
<ClickableImage src="/img/customers/autarco/ld.webp" alt="Image" maxWidth="450px"/>
</div>


<DeviceSupportTable
  devices={[
    { type: 'S2.LD6000-MIII', manual:'/img/customers/autarco/LD-LQ.pdf', modbusTcp: '✅ (only supported with an Autarco LAN-stick)', rs485: '✅', curtailment: "✅"  },
    { type: 'S2.OX110000S', manual:'/img/customers/autarco/OX.pdf',modbusTcp: '✅ (only supported with an Autarco LAN-stick)', rs485: '✅', curtailment: "✅" },
    { type: 'S2.LQ12000-MIII', manual:'/img/customers/autarco/LD-LQ.pdf',modbusTcp: '✅ (only supported with an Autarco LAN-stick)', rs485: '✅', curtailment: "✅" },
  ]}
  showModbusTcp={true}
  showRs485={true}
  showCurtailment={true} showReactivePower={true}
  showManual={true}
/>

\* Modbus-TCP is __only__ supported with an Autarco LAN-stick. Check the [Autarco hardware help center](https://help.autarco.com/en/hardware) for the current LAN-Stick-D information.

## Wiring (Modbus TCP)
> [!NOTE]
> The information below is based on Autarco's official guidance. Check the [Autarco energy-management help center](https://help.autarco.com/en/services) for the latest instructions.
To enable TCP/IP you need the following:

- Communication: S2.LAN.STICK.D (see the [Autarco hardware help center](https://help.autarco.com/en/hardware))
- Communication stick firmware: equal to 100101B0
When the firmware is correct TCP/IP is enabled.

_How to update the firmware version?_
→ Updating the firmware version of the communication stick is currently possible via Digital O&M in Helios. Check the [Autarco software help center](https://help.autarco.com/en/software) for the latest procedure.
## Wiring (RS485)
The wiring between the <BrandName/> <ControllerName/> and the Autarco can be done with the following guides:
<table>
  <thead>
    <tr>
      <th>Model</th>
      <th>Page</th>
    </tr>
  </thead>
  <tbody>
    <tr><td>S2.LD6000-MIII</td><td><a href="/Devices/PV-hybrid-and-battery-inverters/Autarco/On-grid/LD-series">Wiring configuration for LD-series</a></td></tr>
    <tr><td>S2.LQ12000-MIII</td><td ><a href="/Devices/PV-hybrid-and-battery-inverters/Autarco/On-grid/LQ-series">Wiring configuration for LQ-series</a></td></tr>
    <tr><td>S2.OX110000S</td><td><a href="/Devices/PV-hybrid-and-battery-inverters/Autarco/On-grid/OX-series">Wiring configuration for OX-series</a></td></tr>
  </tbody>
</table>
If your model is not listed, we refer to the manual of the Autarco inverter. It should always include a section on how to wire a rs485 communication with external EMS-systems.


# Autarco LD-series RS485 wiring

import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/customers/autarco/LD.png"
    alt="logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>
This page describes the communication with an Autarco LD-series hybrid inverter over Modbus-RTU (rs485). 
By default, the inverter is set to address 1. The RS485 interface is a 4-pin connector on the bottom of the inverter 
behind a protective plate. The exact position is marked in the orange box in the image below:
<ClickableImage src="/img/customers/autarco/ld-com1.png" alt="Image" maxWidth="450px" />
Looking closer the port looks like this:
<ClickableImage src="/img/customers/solis/3t10K-HVES-G5-wiring.png" alt="Image" maxWidth="450px" />
An appropriate connector should be used for this 4-pin connector on the Autarco inverter to connect to the <BrandName /> <ControllerName />.
On the <BrandName /> <ControllerName />, the inverter can be connected to the RS485 port. The wiring is as follows:
<RS485ConnectionTable firstColumn={["Pin 3", "Pin 4", "N/A"]} />

<RS485AddressNote />


# Autarco LQ series RS485 wiring

import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/customers/autarco/LD.png"
    alt="logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>
This page describes the communication with an Autarco LQ-series hybrid inverter over Modbus-RTU (rs485). 
By default, the inverter is set to address 1. The RS485 interface is a 4-pin connector on the bottom of the inverter 
behind a protective plate. The exact position is marked in the orange box in the image below:
<ClickableImage src="/img/customers/autarco/lq-com1.png" alt="Image" maxWidth="450px" />
Looking closer the port looks like this:
<ClickableImage src="/img/customers/solis/3t10K-HVES-G5-wiring.png" alt="Image" maxWidth="450px" />
An appropriate connector should be used for this 4-pin connector on the Autarco inverter to connect to the <BrandName /> <ControllerName />.
On the <BrandName /> <ControllerName />, the inverter can be connected to the RS485 port. The wiring is as follows:
<RS485ConnectionTable firstColumn={["Pin 3", "Pin 4", "N/A"]} />

<RS485AddressNote />


# Autarco OX-series RS485 wiring

import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/customers/autarco/ox.png"
    alt="logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>
This page describes the communication with an Autarco OX-series on-grid inverter over Modbus-RTU (rs485). 
By default, the inverter is set to address 1. 

The OX inverters have the following communication ports:
- COM1: Green 4 pin connector for WiFi/Cellular datalogger.
- COM2 and COM3: Cable glands and cover with following connection points behind:
    - 2 x RJ45 connections
    - 1 x RS485 terminal bloc

Specifically for the <BrandName /> <ControllerName />, the RS485 communication happens over the 'COM2 Terminal Block' port. This marked in the orange box in the image below:
<ClickableImage src="/img/customers/autarco/ox-com1.png" alt="Image" maxWidth="550px" />
The port is an RJ45-port, used for the RS485 communication. 
A cable need to be prepared to connect the inverter to the inverter.

2. Insert the wire into the RJ45 connector then crimp the connector with the crimping tool.
3. Removethe cap nut from the waterproof cable glands labeled COM2 and COM3 at the
bottom of the inverter. Remove the plug from the fitting.
4. Insert the RJ45 connector into the RJ45 port in the inverter maintenance chamber.
5. Replace the cap nuts for COM2/3 and tighten firmly.
<ClickableImage src="/img/customers/autarco/ox-com2.png" alt="Image" maxWidth="550px" />
<RS485ConnectionTable firstColumn={["Pin 3", "Pin 4", "N/A"]} />

<RS485AddressNote />


# BatterX


# BatterX



<img
    src="/api/media/editor-uploads/Controller/Devices/PV-hybrid-and-battery-inverters/BatterX/batterX-logo-with-back-background.jpg"
    alt="batterX logo with back background"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

## Supported Devices

<DeviceSupportTable
  devices={[
    {
      type: 'C-Series',
      variants: "c30 c50",
      modbusTcp: '✅'
    },
    {
      type: 'I-Series',
      variants: "i10 i20 i30",
      modbusTcp: '✅'
    },
  ]}
  showModbusTcp={true}
  showVariants={true}
  showReactivePower={true}
/>

<div style={{ display: "flex", flexWrap: "wrap", justifyContent: "center", gap: "1rem" }}>

  <ClickableImage src="/api/media/editor-uploads/Controller/Devices/PV-hybrid-and-battery-inverters/BatterX/i10-i20-inverter.png" alt="batterX inverter" maxWidth="250px" />
  <ClickableImage src="/api/media/editor-uploads/Controller/Devices/PV-hybrid-and-battery-inverters/BatterX/i30-inverter.png" alt="batterX inverter" maxWidth="250px" />
  <ClickableImage src="/api/media/editor-uploads/Controller/Devices/PV-hybrid-and-battery-inverters/BatterX/c50-inverter.png" alt="batterX inverter" maxWidth="250px" />
</div>

The <BrandName /> <ControllerName /> communicates with the inverter through the **batterX EMX**, the batterX EMS box.

<ClickableImage src="/api/media/editor-uploads/Controller/Devices/PV-hybrid-and-battery-inverters/BatterX/EMX-EMS-Box-1.jpg" alt="batterX EMX" maxWidth="300px" />

## Connection

Install the batterX EMX according to the installation manual. You can find the document on the [batterX website](https://www.batterx.de).

Connect the EMX with an appropriate Ethernet cable at the designated port. For correct Ethernet wiring, follow the [guidelines for ethernet wiring](/Controller/wiring-best-practices/#ethernet).

<ClickableImage src="/api/media/editor-uploads/Controller/Devices/PV-hybrid-and-battery-inverters/BatterX/EMX-network-connection-1.png" alt="Network port on the batterX EMX" maxWidth="600px" />

## Configuration

After installing the batterX EMX and running through the automatic installation routine, open the batterX portal to view the system.

### Set the Modbus TCP protocol

1. Go to **System Settings** and scroll down to **Other Settings**.
2. Use the drop-down menu next to **Modbus TCP Protocol** and select **Eniris**.

<ClickableImage src="/api/media/editor-uploads/Controller/Devices/PV-hybrid-and-battery-inverters/BatterX/Settings-1.png" alt="Select Eniris as Modbus TCP Protocol" maxWidth="600px" />

3. Click the **Apply** button next to it to save this setting.

<ClickableImage src="/api/media/editor-uploads/Controller/Devices/PV-hybrid-and-battery-inverters/BatterX/Settings-2.png" alt="Apply the Modbus TCP Protocol setting" maxWidth="600px" />

### Enable remote control

1. Use the drop-down menu next to **Remote Control** and select **Enabled**.

<ClickableImage src="/api/media/editor-uploads/Controller/Devices/PV-hybrid-and-battery-inverters/BatterX/Settings-3.png" alt="Enable Remote Control" maxWidth="600px" />

2. Click the **Apply** button next to it to save this setting.

<ClickableImage src="/api/media/editor-uploads/Controller/Devices/PV-hybrid-and-battery-inverters/BatterX/Settings-4.png" alt="Apply the Remote Control setting" maxWidth="600px" />

3. Confirm your selection by clicking **OK** in the pop-up.


# Battlink


import { BrandName, ControllerName } from '@site/src/components/customFields';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';
import ClickableImage from '@site/src/components/ClickableImage';

<img
    src="/img/customers/battlink/logo.png"
    alt="logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

## Supported Devices

<DeviceSupportTable
  devices={[
    { type: 'Battlink 241kWh batteries', modbusTcp: '✅'},

  ]}
  showModbusTcp={true}
  showReactivePower={true}
/>

## Wiring Modbus TCP

- Both the battery and the <ControllerName /> should be connected to the same network.
- Allow TCP port 502 between the battery and the <ControllerName />

### Ethernet
For correct ethernet wiring: Follow the [the guidelines for ethernet wiring](/Controller/wiring-best-practices/#ethernet).

# Beauvent


import { BrandName, ControllerName } from '@site/src/components/customFields';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
  src="/img/customers/beauvent/BeauVent.png"
  alt="Beauvent"
  style={{ display: "block", margin: "0 auto", width: "40%" }}
/>

# Beauvent Inverter

> [!NOTE]
> This integration connects Beauvent PV inverters to the <BrandName /> <ControllerName /> over Modbus TCP. It provides monitoring and allows the controller to limit active power when smart grid mode is enabled.

## Supported Devices

<DeviceSupportTable
  devices={[
    {
      type: "Beauvent Inverter",
      variants: "Modbus TCP",
      modbusTcp: "✅",
      rs485: "❌",
        curtailment: "✅"
    }
  ]}
  showVariants
  showModbusTcp
  showRs485
  showCurtailment
  showReactivePower={true}
/>

## Wiring

- Connect the inverter (or site gateway) to the LAN with an RJ45 cable.
- Allow TCP port **502** between the inverter and the <BrandName /> <ControllerName />.
- Follow the [Ethernet wiring best practices](/Controller/wiring-best-practices/#ethernet).

> The Modbus server listens on Unit ID **1**. Keep this address unless the site uses a different value.


# C-Battery


<img
    src="/img/sgo/Logo_C-Battery.png"
    alt="logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>


> [!NOTE] 
> ### Supported Devices
> The following devices are supported and existing integrations remain available. However, these brands and models were integrated several years ago and are not commonly used by our current customers. If you require support or assistance with these devices, please contact us for further guidance.


# Cellpower


import { BrandName, ControllerName } from '@site/src/components/customFields';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import RS485AddressNote from '@site/src/components/RS485AddressNote';

<img
    src="/img/customers/cellpower/Logo_Cellpower.png"
    alt="logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

# Cellpower

## Supported Devices


<DeviceSupportTable
  devices={[
    { type: 'CESS 209-104', modbusTcp: '✅', rs485: '❌'},
    { type: 'CESS 233-116', modbusTcp: '✅', rs485: '❌'},
    { type: 'CESS 261-125', modbusTcp: '✅', rs485: '❌'},
    { type: 'CESS 280-125', modbusTcp: '✅', rs485: '❌'},
    { type: 'CESS 314-125', modbusTcp: '✅', rs485: '❌'},
  ]}
  showModbusTcp={true}
  showRs485={true}
  showReactivePower={true}
/>

## Wiring

The <BrandName /> <ControllerName /> and the Cellpower CESS communicate via Ethernet.

### Ethernet
For correct ethernet wiring: Follow the [the guidelines for ethernet wiring](/Controller/wiring-best-practices/#ethernet).

# Chisage


import { BrandName, ControllerName } from '@site/src/components/customFields';
import ClickableImage from '@site/src/components/ClickableImage';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/customers/chisage/chisage-logo.png"
    alt="Chisage Logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

# Chisage Inverters

Chisage is a manufacturer of PV-hybrid and battery inverters for residential and commercial applications. Their product line includes both single-phase (Jup series) and three-phase (Mars series) hybrid inverters, as well as grid-tie inverters. Chisage inverters support operation with both solar panels and battery storage.

## Supported Devices

<DeviceSupportTable
  devices={[
    {
      type: "Jup",
      variants: "5-10G2-LE",
      modbusTcp: "❌",
      rs485: "✅",
      curtailment: "❌"
    },
    {
      type: "Mars",
      variants: "5-14G2-LE",
      modbusTcp: "❌",
      rs485: "✅",
      curtailment: "✅"
    },
        {
      type: "Merc",
      variants: "N/A",
      modbusTcp: "❌",
      rs485: "✅",
      curtailment: "N/A"
    }
  ]}
  showVariants={true}
  showModbusTcp={true}
  showRs485={true}
  showReactivePower={true}
/>

<ClickableImage src="/img/customers/chisage/chisage-wallbox.jpg" alt="Chisage Mars Wallbox" maxWidth="450px" />


## Wiring

The <BrandName /> <ControllerName /> and the Chisage inverters communicate via RS485.

### RS485

To connect the Chisage inverter to RS485, use the D-B/485 port on the inverter. The specific pinout may vary, so consult the inverter's manual for the exact connections. A typical RS485 connection table is shown below:

<RS485ConnectionTable firstColumn={["RS485 A", "RS485 B", "GND"]} />

Consult the specific manual for your Chisage inverter model for detailed wiring diagrams and instructions.

## Configuration

The following steps provide a general overview of configuring Chisage inverters. Consult the specific user manual for your inverter model for detailed instructions and safety precautions.

1.  **Initial Setup:** Upon initial startup, configure essential system settings such as the grid standard, language, and time zone.
2.  **Parameter Settings:** Access the parameter setting menu, typically through the inverter's LCD touch screen or a dedicated mobile app. Navigate through the menu using the provided buttons or touch controls.
3.  **Battery Settings:** Configure battery parameters to match your battery type and specifications. This includes settings such as battery capacity, charging voltage limits, and discharging voltage limits.
4.  **Grid Settings:** Configure grid parameters to comply with local grid regulations. This includes settings such as voltage limits, frequency limits, and power factor.
5.  **Smart Load Settings (if applicable):** Configure settings related to smart load power, such as the conditions for enabling or disabling power to the smart load based on battery SOC or voltage.

For more information about specific models, visit [Chisage manuals](https://chisagess.com/download/solar-inverter-2/).

<RS485AddressNote />

# Danfoss


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/sgo/Logo_Danfoss.png"
    alt="logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>


## Supported Devices

<DeviceSupportTable
  devices={[
    {  
      type: "TLX (Solar Inverter)",
      modbusTcp: "❌",
      rs485: "✅",
      curtailment: "❌"
    },
  ]}
  showModbusTcp={false}
  showRs485={true}
  showCurtailment={true} showReactivePower={true}
  showFirmwareVersion={false}
/>

> [!NOTE] 
> ### Supported Devices
> The above devices are supported and existing integrations remain available. However, these brands and models were integrated several years ago and are not commonly used by our current customers. If you require support or assistance with these devices, please contact us for further guidance.


# Delta


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/customers/delta/logo.svg"
    alt="logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

# Delta Inverters

## Supported Devices

<DeviceSupportTable
  devices={[
    {
      type: "Delta RPI",
      variants: " M6/M8/M10/M12/M15A/M20A/M30",
      modbusTcp: "❌",
      rs485: "✅",
      curtailment: "✅"
    },
    {
    type: "Delta RPI",
    variants: "H3/H5/H3A/H4A/H5A (not tested)",
    modbusTcp: "❌",
    rs485: "✅",
    curtailment: "✅"
    },
    {
    type: "Delta RPI",
    variants: "M6A/M8A/M10A/M50A/M30A (not tested)",
    modbusTcp: "❌",
    rs485: "✅",
    curtailment: "✅"
    }
  ]}
  showVariants={true}
  showModbusTcp={true}
  showRs485={true}
  showCurtailment={true} showReactivePower={true}
/>


## Wiring

The <BrandName /> <ControllerName /> and the Delta inverters communicate via RS485.

### RS485

<ClickableImage src="/media/delta/delta_wiring.png" alt="Delta Wiring" maxWidth="350px" />

| Setting  | options  |
|---|---|
| Baudrate  | 2400 / 4800 / 9600 / 19200 (default) / 38400  |
| Data bits  |  8 |
| Parity  | None  |
| Stop bits | 1 |


## Configuration


<RS485AddressNote />

# DET Power PV, Hybrid and Battery Inverters


import { BrandName, ControllerName } from '@site/src/components/customFields';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/customers/det_power/Logo_DET Power.png"
    alt="DET Power"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

# DET Power PV, Hybrid and Battery Inverters

## Supported Devices

<DeviceSupportTable
  devices={[
    {
      type: "10ft Battery ESS",
      variants: "322kWh",
      modbusTcp: "✅",
      rs485: "❌",
      curtailment: "✅"
    }
  ]}
  showVariants={true}
  showModbusTcp={true}
  showRs485={true}
  showCurtailment={true} showReactivePower={true}
/>


## Connection

The communication between the <BrandName /> <ControllerName /> and the DET Power inverters operates via Modbus TCP.
For correct ethernet wiring: Follow the [the guidelines for ethernet wiring](/Controller/wiring-best-practices/#ethernet).

### 10ft Battery ESS

No settings need to be made on the DET Power 10ft Battery ESS.
The Modbus TCP connection is established via the LAN port on the inverter.
After adding the battery through the <BrandName /> <ControllerName /> interface, control will be established automatically.

# DEYE


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/customers/deye/logo.png"
    alt="logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>


## Supported Devices

<DeviceSupportTable
  devices={ [
    {
      type: "Single Phase LV Hybrid Inverters (SG0XLP1-EU)",
      variants: "SUN-3/3.6/5/6/7/7.6/8/10/12K",
      modbusTcp: "❌",
      rs485: "✅",
      curtailment: "❌",
      instructionVideos: [{"videoId": "fNtczOqy208", "title": "Deye SUN-3/3.6/5/6K-SG04LP1-EU · Modbus"}, {"videoId": "N7_pxOwF6-8", "title": "Deye SG04LP1-EU-SM1/SM2 · 3–6 kW"}, {"videoId": "PyUc4j6cD3s", "title": "Deye SG05LP1-EU-AM2-P · 3.6–10 kW"}, {"videoId": "rTnKeDST5T4", "title": "Deye SG05LP1-EU-SM2/SM2-P · 3.6–10 kW"}, {"videoId": "UqVUnFtQqos", "title": "Deye SG06LP1-EU-BM1/BM2 · 3–6 kW"}, {"videoId": "7ylNXVjLrj0", "title": "Deye SG06LP1-EU-CM1/CM2 · 3–6 kW"}, {"videoId": "78tRTJOxX1o", "title": "Deye SG06LP1-EU-BM3 · 7–12 kW"}, {"videoId": "REg4YY_4HgA", "title": "Deye SG06LP1-EU-CM3 · 7–12 kW"}, {"videoId": "U6jKaKiMehY", "title": "Deye SG02LP1-EU-AM2/AM3(-P) · 5–12 kW"}, {"videoId": "kS0xN8BF4-o", "title": "Deye SUN-12K-SG01LP1-EU"}, {"videoId": "mcULwDVBXok", "title": "Deye SUN-12K-SG01LP1-EU-AM3-P"}]
    }, {
      type: "Three Phase LV Hybrid Inverters (SG0XLP3-EU)",
      variants: "SUN-3/4/5/6/8/10/12/14/15/16/18/20K",
      modbusTcp: "❌",
      rs485: "✅",
      curtailment: "❌",
      instructionVideos: [{"videoId": "un0Jz1e1vgw", "title": "Deye SG04LP3-EU / AM2-P · 5–12 kW"}, {"videoId": "FIMS30Y7v1A", "title": "Deye SG05LP3-EU-SM2 · 3–12 kW"}, {"videoId": "a0K0o7UBY9Q", "title": "Deye SG05LP3-EU-SM2 · 14–20 kW"}, {"videoId": "2raeNVZieeY", "title": "DEYE SG06LP3-EU-BM2 · 3–8 kW", "description": "Models: SUN-3K-SG06LP3-EU-BM2, SUN-4K-SG06LP3-EU-BM2, SUN-5K-SG06LP3-EU-BM2, SUN-6K-SG06LP3-EU-BM2, SUN-8K-SG06LP3-EU-BM2."}, {"videoId": "qM1Y_KEEAms", "title": "DEYE SG06LP3-EU-CM2 · 3–8 kW", "description": "Models: SUN-3K-SG06LP3-EU-CM2, SUN-4K-SG06LP3-EU-CM2, SUN-5K-SG06LP3-EU-CM2, SUN-6K-SG06LP3-EU-CM2, SUN-8K-SG06LP3-EU-CM2."}]
    }, {
      type: "Three Phase HV Hybrid Inverters (SG0XHP3-EU)",
      variants: "SUN-5/6/8/10/12/15/20/25/29.9/30/35/40/50/60/70/75/80K",
      modbusTcp: "❌",
      rs485: "✅",
      curtailment: "❌",
      instructionVideos: [{"videoId": "UmnqV60Xdak", "title": "DEYE SG01HP3-EU-AM2 · 5–25 kW", "description": "Models: SUN-5K-SG01HP3-EU-AM2, SUN-6K-SG01HP3-EU-AM2, SUN-8K-SG01HP3-EU-AM2, SUN-10K-SG01HP3-EU-AM2, SUN-12K-SG01HP3-EU-AM2, SUN-15K-SG01HP3-EU-AM2, SUN-20K-SG01HP3-EU-AM2, SUN-25K-SG01HP3-EU-AM2."}, {"videoId": "iG5vCi_OYIo", "title": "DEYE SG01HP3-EU-BM3/BM4 · 29,9–50 kW", "description": "Models: SUN-29.9K-SG01HP3-EU-BM3, SUN-30K-SG01HP3-EU-BM3, SUN-35K-SG01HP3-EU-BM3, SUN-40K-SG01HP3-EU-BM4, SUN-50K-SG01HP3-EU-BM4."}, {"videoId": "V3iklQ3FVZ0", "title": "DEYE SG01HP3-EU-DM2 · 5–12 kW", "description": "Models: SUN-5K-SG01HP3-EU-DM2, SUN-6K-SG01HP3-EU-DM2, SUN-8K-SG01HP3-EU-DM2, SUN-10K-SG01HP3-EU-DM2, SUN-12K-SG01HP3-EU-DM2."}, {"videoId": "rA6GGHpfOH4", "title": "DEYE SG02HP3-EU-AM3 · 25–30 kW", "description": "Models: SUN-25K-SG02HP3-EU-AM3, SUN-29.9K-SG02HP3-EU-AM3, SUN-30K-SG02HP3-EU-AM3."}, {"videoId": "9RaOmk_Mvg4", "title": "DEYE SG02HP3-EU-BM3/BM4-P · 29,9–50 kW", "description": "Models: SUN-29.9K-SG02HP3-EU-BM3-P, SUN-30K-SG02HP3-EU-BM3-P, SUN-35K-SG02HP3-EU-BM3-P, SUN-40K-SG02HP3-EU-BM4-P, SUN-50K-SG02HP3-EU-BM4-P."}, {"videoId": "q3Lv_HSXHH0", "title": "DEYE SG02HP3-EU-EM6 · 60–80 kW", "description": "Models: SUN-60K-SG02HP3-EU-EM6, SUN-70K-SG02HP3-EU-EM6, SUN-75K-SG02HP3-EU-EM6, SUN-80K-SG02HP3-EU-EM6."}]
    }, {
      type: "Single Phase String Inverters (G0XP1-EU)",
      variants: "SUN-1/1.5/2/2.2/2.5/2.7/3/3.3/3.6/4/4.2/4.6/5/5.2/6/6.2/7/7.5/8/9/10/10.5K",
      modbusTcp: "❌",
      rs485: "✅",
      curtailment: "❌"
    }, {
      type: "Three Phase String Inverters (G0XP3-EU)",
      variants: "SUN-3/4/5/6/7/8/9/10/12/15/18/20/22/23/25/30/35/36/40/45/50/60/70/75/80/90/100/120/125/130/135/136K",
      modbusTcp: "❌",
      rs485: "✅",
      curtailment: "❌",
    },
  ] }
  showVariants = { true }
  showModbusTcp = { true }
  showRs485 = { true }
  showCurtailment = { true } showReactivePower={true}
/>

## Wiring

### RS485
<RS485ConnectionTable firstColumn={["Pin 1 / Modbus-485_B", "Pin 2 / Modbus-485_A", "Pin 3 / GND_485"]} />
<ClickableImage src="/img/customers/deye/deye_wiring_pt1.png" alt="Image 1" maxWidth="450px" />
<ClickableImage src="/img/customers/deye/deye_wiring_pt2.jpg" alt="Image 1" maxWidth="450px" />
<ClickableImage src="/img/customers/deye/deye_wiring_pt3.png" alt="Image 1" maxWidth="450px" />


## Configuration
<RS485AddressNote />

Go to “Main Screen” >> “System Settings” >> “Advanced Function.”
- Modbus SN should be set to any number between 1 and 247. Do not select 0!! Note that if there are multiple devices on the RS485 bus, each should be given a unique number. This is the address.
- Slave should be checked.
- Only when an additional meter is connected directly to the inverter should “EX_meter For CT” be checked. If there is only a meter in parallel with the <BrandName /> <ControllerName /> it should be unchecked.
- Make sure the following settings are all correct: "Max A Charge", "Max A Discharge", "Grid Charge Ampere"

<ClickableImage src="/img/customers/deye/deye_config_pt1.png" alt="Image 1" maxWidth="450px" />

# Diehl-Ako


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/customers/diehl_ako/logo.png"
    alt="logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>


## Supported Devices


<DeviceSupportTable
  devices={[
    {
      type: "Platinum",
      modbusTcp: "❌",
      rs485: "✅",
      curtailment: "✅"
    }
  ]}
  showModbusTcp={true}
  showRs485={true}
  showCurtailment={true} showReactivePower={true}
/>


## Wiring

### RS485
<RS485ConnectionTable firstColumn={["A", "B", "N/A"]} />
<ClickableImage src="/img/customers/diehl_ako/wiring.png" alt="Image 1" maxWidth="450px" />


## Configuration
Diehl-Ako uses a non-Modbus protocol and has automatic device recognition. It is not necessary to set individual addresses to the inverters.

# DMEGC Inverters



import DeviceSupportTable from '@site/src/components/DeviceSupportTable';


<img
    src="/img/customers/DMEGC/logo.png"
    alt="logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

# DMEGC Inverters

## Supported Devices

<DeviceSupportTable showModbusTcp showVariants devices = { [
  {
    type: 'Hybrid Inverter',
    variants: 'SPH3.6K',
    modbusTcp: '✅',
    rs485: '✅'
  }, {
    type: 'Hybrid Inverter',
    variants: 'SPH5K',
    modbusTcp: '✅',
    rs485: '✅'
  }, {
    type: 'Hybrid Inverter',
    variants: 'SPB5K',
    modbusTcp: '✅',
    rs485: '✅'
  }, {
    type: 'Hybrid Inverter',
    variants: 'SPH6K',
    modbusTcp: '✅',
    rs485: '✅'
  }, {
    type: 'Hybrid Inverter',
    variants: 'SPH8K',
    modbusTcp: '✅',
    rs485: '✅'
  }, {
    type: 'Hybrid Inverter',
    variants: 'TPH4K',
    modbusTcp: '✅',
    rs485: '✅'
  }, {
    type: 'Hybrid Inverter',
    variants: 'TPH5K',
    modbusTcp: '✅',
    rs485: '✅'
  }, {
    type: 'Hybrid Inverter',
    variants: 'TPH6K',
    modbusTcp: '✅',
    rs485: '✅'
  }, {
    type: 'Hybrid Inverter',
    variants: 'TPH8K',
    modbusTcp: '✅',
    rs485: '✅'
  }, {
    type: 'Hybrid Inverter',
    variants: 'TPH10K',
    modbusTcp: '✅',
    rs485: '✅'
  }, {
    type: 'Hybrid Inverter',
    variants: 'TPH12K',
    modbusTcp: '✅',
    rs485: '✅'
  }, {
    type: 'Hybrid Inverter',
    variants: 'TPH15K',
    modbusTcp: '✅',
    rs485: '✅'
  }
] }
  showReactivePower={true}
/>

## Wiring

### Ethernet Connection
For correct ethernet wiring, follow the [guidelines for ethernet wiring](/Controller/wiring-best-practices/#ethernet).


# Dunext


import { BrandName, ControllerName } from '@site/src/components/customFields';

# Dunext PowerHill 261

The PowerHill 261 is a battery storage system connected locally to the <BrandName /> <ControllerName /> through its Ethernet interface. The connection reads the system's power and battery information and provides a battery power setpoint.

> [!IMPORTANT] Testing
> Testing is ongoing for the PowerHill 261 connection. It requires controller software that includes this integration; it is not available in every installed software version.

## Compatibility

| Device | Ethernet / Modbus TCP | RS485 | Status | Instruction video |
| --- | --- | --- | --- | --- |
| Dunext PowerHill 261 | Port `502` | Not offered by this integration | Testing | <InstructionVideo videos={[{"videoId": "L2X4sUyde0E", "title": "PowerHill-P125-261kWh C5 · LAN3", "description": "PowerHill-P125-261kWh C5 cabinet, using LAN3. The integration remains subject to the testing and controller software requirements stated on this page."}]} /> |

This page covers the **PowerHill 261**. It does not list other Dunext models as compatible.

## Connect the system

1. Connect the PowerHill 261's Ethernet interface and the <ControllerName /> to the same local network. Follow the [Ethernet wiring guidelines](/Controller/wiring-best-practices/#ethernet).
2. Note the IP address of the PowerHill 261 system.
3. In the controller's device setup, select the battery category, manufacturer **Dunext** and device **Dunext PowerHill 261**.
4. Choose **Modbus TCP**, enter the system's IP address and port `502`, and use Modbus address `1` for this connection.
5. Add the detected system. Check that battery state of charge, voltage, current and system power update before enabling energy management.

## Measurements and control

| Part of the installation | Information provided |
| --- | --- |
| System | AC active power |
| Battery | State of charge, state of health, voltage, current and calculated battery power |
| PV, when detected | PV power |

The battery is represented with a capacity of **261 kWh**. The controller applies a battery power setpoint through the system's local interface and switches the system to remote control when energy management is active.

The presence of a PV power measurement does **not** mean that separate PV curtailment is available. This integration does not provide an independent PV power-limit command.

## If the system is not found

- Check that you selected **Dunext PowerHill 261**, rather than a similarly sized battery from another manufacturer.
- Check the system's IP address, network connection, Modbus TCP availability and port `502`.
- Use the connection address `1`. The controller handles the system's internal components as part of this connection.
- If the PowerHill 261 selection is absent, the installed controller software does not offer this connection. It cannot be added by choosing another device model.


# Dyness


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/customers/dyness/logo.png"
    alt="logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

# Dyness Inverters
> [!IMPORTANT]
> Currently, the integration is support upto a state of charge limit to 95%. This is because when the state of charge goes beyond 95%, the battery can stop listening to setpoints due to the actions of the battery management system. 
> We are working on resolving this issue with Dyness and other partners. 

## Supported Devices

<DeviceSupportTable
  devices={[
    {
      type: "EC100",
      variants: "100kWh",
      modbusTcp: "✅",
      rs485: "✅",
      curtailment: "✅"
    },
    {
      type: "DH100F",
      variants: "71~100kWh",
      modbusTcp: "✅",
      rs485: "✅",
      curtailment: "✅",
      instructionVideos: [{"videoId": "jytjRqI7qLw", "title": "Dyness DH100F", "description": "Models: DH100F-S00L01C70, DH100F-S01L01C70, DH100F-S02L01C70, DH100F-S00L01C80, DH100F-S01L01C80, DH100F-S02L01C80, DH100F-S00L01C100, DH100F-S01L01C100, DH100F-S02L01C100."}]
    },
    {
      type: "DH200F",
      variants: "100kW/215kWh",
      modbusTcp: "✅",
      rs485: "✅",
      curtailment: "✅"
    },
    {
      type: 'DH200Y',
      variants: '100kW/232kWh',
      modbusTcp: "✅",
      rs485: "✅",
      curtailment: "✅"
    },
    {
      type: 'LS',
      modbusTcp: "✅",
      rs485: "✅",
      curtailment: "✅",
      instructionVideos: [{"videoId": "q6qArjD89L4", "title": "Dyness LS 3–8 kW", "description": "Models: D3.0K-LS, D3.6K-LS, D5.0K-LS, D6.0K-LS, D8.0K-LS."}]
    },
    {
      type: 'HT-A',
      modbusTcp: "✅",
      rs485: "✅",
      curtailment: "✅",
      instructionVideos: [{"videoId": "S_bNNXBhXW8", "title": "Dyness HT-A 5–15 kW", "description": "Models: D5K-HT-A, D6K-HT-A, D8K-HT-A, D10K-HT-A, D12K-HT-A, D15K-HT-A."}]
    },
    {
      type: 'DH800Y',
      modbusTcp: "✅",
      rs485: "✅",
      curtailment: "❌"
    },
  ]}
  showVariants={true}
  showModbusTcp={true}
  showRs485={true}
  showCurtailment={true} showReactivePower={true}
/>

## Model-specific connection settings

| Model family | Modbus TCP port | RS485 settings | Modbus address range |
| --- | --- | --- | --- |
| LS and HT-A | `502` | `9600 baud, 8N1` | `1–247` |
| DH800Y | `502` | `115200 baud, 8N1` | `1–99` |

LS and HT-A are separate choices in the device wizard. Select the model installed on site rather than using a DH100F profile.

> [!IMPORTANT]
> The DH800Y connection requires controller software that includes it and is currently available in the testing software line. Its presence on this page does not mean every installed controller already offers it.

DH800Y supports a battery AC power setpoint and battery-cluster, state-of-charge, energy and alarm readings. A PV power reading does not provide separate PV curtailment: that command is not available through this integration.

Before controlling a DH800Y, open its HMI or web interface and set `Control mode → Remote mode`. The controller does not enable this setting automatically.

## Wiring

The <BrandName /> <ControllerName /> and the Dyness inverters communicate via RS485 or Ethernet.

### Ethernet
For correct ethernet wiring: Follow the [the guidelines for ethernet wiring](/Controller/wiring-best-practices/#ethernet).

### RS485

The COM6 wiring example below belongs to the cabinet-style connection. Do not reuse it as an LS or HT-A terminal diagram; use the RS485 terminal markings in the manual for that model.

<RS485ConnectionTable firstColumn={["COM6 terminal 1A", "Com6 terminal 1B", "N/A"]} />

<ClickableImage src="/media/dyness/dyness-cables.png" alt="Dyness Wiring" maxWidth="350px" />

## Configuration
### DH100F

The Dyness DH100F needs to be set to remote mode:
    1. Click the main menu icon on the upper right corner of the main interface
    2. Click "Data" in the main menu bar
    3. Click "EMS" in the sub-menu bar
    4. Click "RunSet" at the upper left of the navigation bar
    5. Set the Control Mode to "Remote"

<ClickableImage src="/media/dyness/dyness-1.png" alt="Dyness DH100F Interface" maxWidth="350px" />

<RS485AddressNote />

# Dysun Energy


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';
import RS485AddressNote from '@site/src/components/RS485AddressNote';

<img
  src="/img/customers/dysun/dysun-logo.png"
  alt="Dysun Energy"
  style={{ display: "block", margin: "0 auto", width: "40%" }}
/>


## Supported Devices

<DeviceSupportTable
  devices={[
    {
      type: "Hybrid inverter",
      variants: "Dysun Hybrid",
      modbusTcp: "✅",
      rs485: "✅",
      curtailment: "❌",
      
    },
    {
      type: "FlexAmp",
      variants: "FlexAmp One 3.6K, 5K, 8K, 10K, 12K",
      modbusTcp: "❌",
      rs485: "✅",
      curtailment: "✅",
      
    }
  ]}
  showVariants
  showModbusTcp
  showRs485
  showCurtailment
  showReactivePower={true}
/>

## Wiring

### Dysun Hybrid

#### Modbus TCP

- Connect the inverter's LAN port to your local network.
- Default port: **502**.
- The Modbus unit ID must be set between **1–247** (default **1**).

#### RS485

<RS485ConnectionTable firstColumn={["RS485-A", "RS485-B", "GND"]} />

Serial settings:

| Parameter  | Value               |
|------------|---------------------|
| Baud rate  | 9600 (default) or as configured in the inverter menu |
| Data bits  | 8                   |
| Parity     | None                |
| Stop bits  | 1                   |

---

### FlexAmp

The FlexAmp series communicates exclusively over RS485.

<RS485ConnectionTable firstColumn={["RS485-A", "RS485-B", "GND"]} />

Serial settings:

| Parameter  | Value               |
|------------|---------------------|
| Baud rate  | 9600 (default)      |
| Data bits  | 8                   |
| Parity     | None                |
| Stop bits  | 1                   |


## Configuration

<RS485AddressNote />

- Set the Modbus address (slave ID) between **1–247** in the device menu.
- Each device on the RS485 bus must have a unique address.

### FlexAmp Setup

During device scanning or manual configuration, you will be prompted:

**"What is included in the installation?"**

| Option | When to select |
|--------|----------------|
| Solar panels and battery *(default)* | Both PV and battery are installed |
| Only solar panels | No battery is present |
| Only battery | No PV is present |

Select the option that matches your installation. An incorrect selection will result in missing or incorrect measurements.


## Control

### Dysun Hybrid

The inverter supports battery control:

- **Charge mode**: Set charge current in amperes
- **Discharge mode**: Set discharge power as a percentage of nominal power
- When smart grid control is disabled, the inverter returns to autonomous operation

> [!CAUTION] Experimental
> Control features for the Dysun Hybrid have not been validated on live hardware.

---

### FlexAmp

The FlexAmp series supports **PV curtailment** — the controller can limit the maximum solar production power in real time.

- The active power limit is written as a percentage of nominal power.
- When smart grid control is disabled, the device reverts to its configured local settings (typically unrestricted output).
- Curtailment applies to the total production of all connected PV strings.

| Model            | Rated power | Max curtailment resolution |
|------------------|-------------|---------------------------|
| FlexAmp One 3.6K | 3 600 W     | 1 W                       |
| FlexAmp One 5K   | 5 000 W     | 1 W                       |
| FlexAmp One 8k   | 8 000 W     | 1 W                       |
| FlexAmp One 10k  | 10 000 W    | 1 W                       |
| FlexAmp One 12k  | 12 000 W    | 1 W                       |

# Ecosourcen


import { BrandName, ControllerName } from '@site/src/components/customFields';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/customers/ecosourcen/logo.png"
    alt="logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

# Ecosource<sup>n</sup> Storage Systems

## Supported Devices

<DeviceSupportTable
  devices={[
    { type: 'Risen Storage SU215E105LM',  modbusTcp: '✅', rs485: '❌'},
  ]}
  showModbusTcp={true}
  showRs485={true}
  showReactivePower={true}
/>

The **Risen Storage – Golden Electronic V2** connection is a separate variant. Its validation status and connection settings are described below; do not treat it as the same connection as the SU215E105LM above.

## Wiring

The <BrandName /> <ControllerName /> and the Ecosource<sup>n</sup> storage systems communicate via Ethernet.

### Ethernet
For correct ethernet wiring: Follow the [the guidelines for ethernet wiring](/Controller/wiring-best-practices/#ethernet).

## Risen Storage – Golden Electronic V2

> [!IMPORTANT] In validation
> Testing is ongoing for the Golden Electronic V2 connection, including the charge/discharge direction and battery-rack measurements. It is not listed here as a validated replacement for the SU215E105LM connection.

| Setting | Value |
| --- | --- |
| Manufacturer selection | **EcoSourcen** |
| Device selection | **Risen Storage – Golden Electronic V2** |
| Connection | Ethernet / Modbus TCP |
| TCP port | `502` |
| Modbus address | The EMS's configured address; default `1` |
| RS485 connection | Not offered by this integration |

The V2 connection is intended for a storage system with the Golden Electronic V2 EMS interface. It brings the system's PCS, battery total, detected battery racks and first grid meter into one local connection. It does not add a PV inverter.

### Connection setup for validation installations

1. Connect the EMS and the <ControllerName /> to the same local network.
2. Select **EcoSourcen**, then **Risen Storage – Golden Electronic V2** in the controller's battery setup.
3. Enter the EMS's IP address, port `502` and configured Modbus address. Keep the existing address of the EMS; the supported address range is `1`–`247`.
4. Check the detected battery total and battery racks. The connection only creates racks that return a valid state-of-health reading.
5. Check the grid-meter measurements against the installation's meter. This connection reads the first meter exposed by the EMS, not all of its possible meter slots.

### What is being validated

The connection reads system active and reactive power, battery state of charge, voltage and current, and the available rack measurements and battery limits. Its control function uses one AC active-power setpoint for the system, rather than separate setpoints per battery rack.

Verify the physical charging and discharging direction against the displayed power during commissioning. A successful network connection or a populated state-of-charge value alone does not establish that the power direction and rack readings are correct.


# Eenovance


import { BrandName, ControllerName } from '@site/src/components/customFields';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import RS485AddressNote from '@site/src/components/RS485AddressNote';

<img
    src="/img/customers/eenovance/logo.png"
    alt="logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

# Eenovance Hybrid Inverters

## Supported Devices


<DeviceSupportTable
  devices={[
    { type: 'E-MATE', modbusTcp: '✅', rs485: '❌'},
  ]}
  showModbusTcp={true}
  showRs485={true}
  showReactivePower={true}
/>

## Wiring

The <BrandName /> <ControllerName /> and the Eenovance hybrid inverters communicate via Ethernet.

### Ethernet
For correct ethernet wiring: Follow the [the guidelines for ethernet wiring](/Controller/wiring-best-practices/#ethernet).

# Elecnova


import { BrandName, ControllerName } from '@site/src/components/customFields';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import RS485AddressNote from '@site/src/components/RS485AddressNote';

<img
    src="/img/customers/elecnova/logo.png"
    alt="logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

# Elecnova Hybrid Inverters

## Supported Devices


<DeviceSupportTable
  devices={[
    { type: 'ECO-E233LS', modbusTcp: '✅', rs485: '❌',
  instructionVideos: [{"videoId": "TmjgsBc7D28", "title": "Elecnova ECO-E233LS", "description": "Models: ECO-E233LS."}]
}, { type: 'ECO-215WS', modbusTcp: '✅', rs485: '❌',
  instructionVideos: [{"videoId": "WRYcUhfHZmI", "title": "Elecnova ECO-E215WS", "description": "Models: ECO-E215WS."}]
},
    { type: 'ECO-E261LP2A', modbusTcp: '✅', rs485: '❌'},
  ]}
  showModbusTcp={true}
  showRs485={true}
  showReactivePower={true}
/>

## Wiring

The <BrandName /> <ControllerName /> and the Elecnova hybrid inverters communicate via Ethernet.

### Ethernet
For correct ethernet wiring: Follow the [the guidelines for ethernet wiring](/Controller/wiring-best-practices/#ethernet).

# Enbrilion


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/sgo/Logo_Enbrilion.png"
    alt="Enbrilion"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

# Enbrilion Inverters

## Supported Devices


<DeviceSupportTable
  devices={[
    {
      type: "KorONE 233",
      modbusTcp: "✅",
      rs485: "✅",
      curtailment: "✅"
    }
  ]}
  showModbusTcp={true}
  showRs485={true}
  showCurtailment={true} showReactivePower={true}
/>


## Wiring

The <BrandName /> <ControllerName /> and the Enbrilion inverters communicate via RS485 or Ethernet.

### Ethernet
For correct ethernet wiring: Follow the [the guidelines for ethernet wiring](/Controller/wiring-best-practices/#ethernet).

### RS485
<RS485ConnectionTable firstColumn={["A", "B", "N/A"]} />

<RS485AddressNote />

# Energreen


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/sgo/Logo_Energreen.png"
    alt="logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

# Energreen Inverters

## Supported Devices


<DeviceSupportTable
  devices={[
    {
        type: "Stor",
        modbusTcp: "✅",
        rs485: "✅",
        curtailment: "✅"
        },
        {
        type: "PV Max",
        modbusTcp: "✅",
        rs485: "✅",
        curtailment: "✅"
        },
        {
        type: "Hybrid",
        modbusTcp: "✅",
        rs485: "✅",
        curtailment: "✅"
    }
  ]}
  showModbusTcp={true}
  showRs485={true}
  showCurtailment={true} showReactivePower={true}
/>


## Wiring

The <BrandName /> <ControllerName /> and the Dyness inverters communicate via RS485 or Ethernet.

### Ethernet
For correct ethernet wiring: Follow the [the guidelines for ethernet wiring](/Controller/wiring-best-practices/#ethernet).

### RS485
<RS485ConnectionTable firstColumn={["A", "B", "N/A"]} />

## Configuration

Ensure that modbus is enabled:
    1. From the main page go to "Device"
    2. Click "Powerhouse Settings"
    3. Enable "Modbus TCP Server Enable"

<ClickableImage src="/media/sigenergy/sigenergy_modbus.png" alt="Energreen Modbus" maxWidth="100%" />

Ensure that the inverter has been set to Remote EMS Mode:
    1. From the main page go to "System"
    2. Click the three dots next to the installation namespace
    3. Click "System Settings"
    4. Click "Operational Mode"
    5. Select "Remote EMS Mode"

<ClickableImage src="/media/sigenergy/sigenergy_mode.png" alt="Energreen Mode" maxWidth="100%" />

Disable any grid limits:
    1. From the main page go to "System"
    2. Click the three dots next to the installation namespace
    3. Click "System Settings"
    4. Under "Operational Parameters" disable "Export Limitation" and "Import Limitation"
    5. Set "Grid Connection Point Reserve Power Control Method" to "Power Per Phase"

<ClickableImage src="/media/sigenergy/sigenergy_limits.png" alt="Energreen Limits" maxWidth="100%" />

<RS485AddressNote />

# Enerlution


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';


<img
    src="/img/customers/Enerlution/logo.png"
    alt="logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

# Enerlution Inverters

## Supported Devices
<DeviceSupportTable
    devices={[
        {
            type: "HYTH 5-15kW",
            modbusTcp: "❌",
            rs485: "✅",
            curtailment: "❌"
        },
    ]}
    showModbusTcp={ true}
    showRs485={ true }
    showCurtailment={ true } showReactivePower={true}
/>

## Wiring
The <BrandName /> <ControllerName /> and the Enerlution inverters communicate via RS485.

### RS485
<RS485ConnectionTable firstColumn={["RS485A (Pin 3)", "RS485B (Pin 4)", "N/A"]} />

<ClickableImage src="/img/customers/Enerlution/HYTH_wiring.png" alt="Enerlution Wiring" maxWidth="350px" />

<RS485AddressNote />



# EnjoyPowers


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';


# EnjoyPowers

> [!WARNING] EnjoyPowers in combination with a Poweroad BMS
> Starting from <BrandName /> <ControllerName /> software version 1.17.0.x, you must add the EnjoyPowers inverter and Poweroad BMS as separate devices, and dc-link them through the groups page. For more information, see: [DC-linking inverters, batteries and BMS systems](/Controller/Configuration%20from%20A%20to%20Z/11-Extra-Information/dc-linking/)

## Supported Devices

<DeviceSupportTable
  devices={[
    {
        type: "PCS cabinet",
        modbusTcp: "✅",
        rs485: "✅",
        curtailment: "✅",
      instructionVideos: [{"videoId": "91R2XnHb9A0", "title": "EnjoyPowers PCS cabinet · Remote setting", "description": "Settings demonstration for the shown EnjoyPowers PCS cabinet EMS. This video covers Remote mode, not physical cable installation or direct PCS-module compatibility."}]
    }
  ]}
  showModbusTcp={true}
  showRs485={true}
  showCurtailment={true} showReactivePower={true}
/>


## Wiring
For correct ethernet wiring: Follow the [the guidelines for ethernet wiring](/Controller/wiring-best-practices/#ethernet).

## Configuration
### 1. Set in remote control mode
1. Go to "EMS Parameter Settings"
2. Go to "Control Parameter"
3. Set "Control mode" on "Remote"

<ClickableImage src="/img/customers/enjoypowers/remoteControle.png"  alt="Image 1"  maxWidth="350px"/>

# Enphase


import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/customers/enphase/logo.svg"
    alt="logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>


## Supported Devices

<DeviceSupportTable
  devices={[
    {
      type: "Gateway IQ local API",
      localApi: "✅",
      curtailment: "❌"
    }
  ]}
  showLocalApi={true}
  showCurtailment={true} showReactivePower={true}
/>


## Configuration

To connect the Enphase Gateway IQ to the controller, you need to provide your Enphase Enlighten credentials.
If you do not have one, please create an account on [Enphase Enlighten](https://enlighten.enphaseenergy.com/).
Make sure to add the device to your account.

# EP Equipment

import { BrandName, ControllerName } from '@site/src/components/customFields';
import ClickableImage from '@site/src/components/ClickableImage';

<img
    src="/img/customers/EP Equipment/logo.png"
    alt="logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

## Supported Devices

| Device Type | Modbus TCP (Ethernet) | RS485 | Reactive power control |
| :--: | :--: | :--: | :---: |
| EPES 233 | ✅ | ❌ | — |
| EPES 261L | ✅ | ❌ | — |

## Wiring

### Ethernet
For correct ethernet wiring: Follow the [the guidelines for ethernet wiring](/Controller/wiring-best-practices/#ethernet).


# ESY Inverters


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/customers/esy/esy_logo.png"
    alt="logo"
    style={{ display: "block", margin: "0 auto", width: "400px"}}
/>

# ESY Residential Hybrid Inverters


## Supported Devices

<DeviceSupportTable
  devices={[
    { type: 'Sunhome Hybrid inverter Inverter (single phase)', variants: 'HM6', modbusTcp: '❌', rs485: '✅', curtailment: '✅' },
  ]}
  showVariants={true}
  showModbusTcp={true}
  showRs485={true}
  showCurtailment={true} showReactivePower={true}
/>

## Wiring

The <BrandName /> <ControllerName /> and the ESY inverters communicate via  RS485.

## Configuration

> [!WARNING]
> Inverters with firmware version older than the following have a minimum SoC level of 35%. 
> Starting from this version, this setting can be configured by the user.
>
> Minimum required version: MCU version 1040, DSP version 1042.

<RS485AddressNote />


# EVE


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/sgo/Logo_Eve.png"
    alt="logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>
# EVE



## Supported Devices

<DeviceSupportTable
  devices={[
    { type: 'All In One', modbusTcp: '✅', rs485: '❌'},
   ]}
  showModbusTcp={true}
  showRs485={true}
  showReactivePower={true}
/>


## Wiring
### Ethernet
For correct ethernet wiring: Follow the [the guidelines for ethernet wiring](/Controller/wiring-best-practices/#ethernet).

## Configuration

### Enable remote mode on the inverter

| Steps |
|------|
| **1**. Navigate to the local web interface of the Eve system by surfing to the IP address of the Eve system. The port of the web interface is by default 8888, so you access the web interface through http://x.x.x.x:8888 |
| **2**. Once you are logged in, go to the "Manual" tab and configure the Remote mode as Remote: <img src="/img/customers/eve/Eve_Config.png" alt="Image" maxWidth="100%"/> |


# Fairland


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@/components/RS485ConnectionTable';
import RS485AddressNote from '@/components/RS485AddressNote';
import ClickableImage from '@/components/ClickableImage';
import DeviceSupportTable from '@/components/DeviceSupportTable';

<img
    src="/img/customers/fairland/logo.png"
    alt="Fairland logo"
    style={{display:"block",background:"white",margin:"0 auto",width:"50%",height:"4%"}}
/>

## Supported Devices

<DeviceSupportTable
    devices={[
        { type: "Inverx Elite XLiT5",  modbusTcp: "❌", rs485: "✅", curtailment: "✅" },
        { type: "Inverx Elite XLiT6",  modbusTcp: "❌", rs485: "✅", curtailment: "✅" },
        { type: "Inverx Elite XLiT8",  modbusTcp: "❌", rs485: "✅", curtailment: "✅" },
        { type: "Inverx Elite XLiT10", modbusTcp: "❌", rs485: "✅", curtailment: "✅" },
    ]}
    showModbusTcp={true}
    showRs485={true}
    showCurtailment={true} showReactivePower={true}
/>

## Wiring

Connect the RS485 lines to the **ARM_485** terminal block on the inverter:

- **ARM_485_A** → D+ (positive / non-inverting)
- **ARM_485_B** → D– (negative / inverting)

<ClickableImage src="/img/customers/fairland/wiring.jpg" alt="Fairland ARM_485 terminal block" maxWidth="500px" />

<RS485ConnectionTable
    firstColumn={["ARM_485_A (D+)", "ARM_485_B (D–)", "GND"]}
/>

<RS485AddressNote />

## Configuration

### 1. Check RS485 settings on the inverter

The factory default RS485 communication parameters are:

| Parameter   | Value        |
|:------------|:-------------|
| Protocol    | Modbus RTU   |
| Baud rate   | 9600         |
| Data bits   | 8            |
| Parity      | None         |
| Stop bits   | 1            |
| Address range | 1 – 247    |

The default slave address is **1**. The address can be changed in the inverter menu if multiple devices share the same RS485 bus.



### 2. Add the device in the <BrandName /> <ControllerName />

1. Open the <BrandName /> <ControllerName /> commissioning interface.
2. Go to **Devices** → **Add device**.
3. Select the connection type **RS485**.
4. Choose **Fairland Inverx Hybrid Inverter RTU** from the device list.
5. The controller will automatically scan for the device using the default settings (9600 baud, 8N1).
6. If the device is not found automatically, set the Modbus address manually.
7. *(Optional)* Set the number of **PV strings (MPPT inputs)** connected — enter a value between 1 and 4. Leave blank to use the default (4).
8. *(Optional)* Set the number of **battery packs** installed — enter a value between 1 and 32. Leave blank to use the default (1).
9. Save and apply the configuration.

<ClickableImage src="/img/customers/fairland/config.png" alt="Adding the Fairland device in the Controller" maxWidth="500px" />

> [!NOTE]
> Setting the correct PV string count prevents the controller from polling unused MPPT inputs. If fewer strings are physically connected than the default of 4, the controller verifies each string by reading its voltage on first connection.

### 3. Verify communication

After saving, check that live data appears for:

- **Grid**: active power (import/export in W), phase voltages (L1/L2/L3), frequency
- **PV**: power per MPPT string and total PV power
- **Battery**: voltage, current, state of charge (SOC), state of health (SOH), power

> [!NOTE]
> If no battery is physically installed, the controller will display a **"No battery detected by inverter"** warning. This is expected behaviour — the inverter reports battery type code `100` (no battery) and the controller suppresses battery metrics accordingly.

## <BrandName /> / Curtailment Control

The Fairland Inverx Elite supports two control modes:

| Control mode     | Type        | Description |
|:-----------------|:------------|:------------|
| **AC export limit** | `limit`  | Limits grid feed-in power as a percentage of rated inverter power. Supports soft limit (default) and hard limit modes. |
| **Battery setpoint** | `setpoint` | Forces the battery to charge or discharge at a specific power level (W). |

### AC export limit details

- The export limit percentage is calculated from a live reading of the inverter's rated power (register 4051).
- **Soft limit**: holding register `21221` is set to `161`.
- **Hard limit**: holding register `21221` is set to `162`.
- **Disabled**: holding register `21221` is set to `85` (SmartGrid mode off).

### Battery setpoint details

- Power is written in **10 W steps** (raw value = W ÷ 10, clamped to 0 – 600,000 mW).
- **Charge**: command register `23147` = `0xAA` (170) + power register `23148` = raw value.
- **Discharge**: command register `23147` = `0xBB` (187) + power register `23148` = raw value.
- **Stop forced mode**: command register `23147` = `0xCC` (204), energy management mode register `23146` = `0`.
- Forced charge/discharge mode is activated by writing `2` to register `23146`.

## Known Issues

> [!WARNING]
> **Battery type always returns code 1080.** The inverter consistently reports battery type `1080`, which is not documented in the official Modbus protocol. This is a known hardware/firmware bug and does **not** affect operation — the controller uses voltage and SOC values to confirm battery presence instead.

> [!NOTE]
> **Per-string PV power is calculated, not measured.** There is no dedicated power register per MPPT string. Power is derived as voltage × current for each string.


# Fortona


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
  src="/img/customers/fortona/fortona_logo.png"
  alt="Fortona"
  style={{ display: "block", margin: "0 auto", width: "35%"}}
/>

# Fortona 48TL200 Battery System

## Supported Devices

<DeviceSupportTable
  devices={[
    {
      type: "Fortona 48TL200 (FZSoNick)",
      variants: "48TL200",
      modbusTcp: "❌",
      rs485: "✅",
      curtailment: "❌",
    }
  ]}
  showVariants={true}
  showModbusTcp={true}
  showRs485={true}
  showCurtailment={true} showReactivePower={true}
/>

<ClickableImage src="/img/customers/fortona/fortona.png" alt="Fortona 48TL200 Front View" maxWidth="400px" />

---

## Wiring

The <BrandName /> <ControllerName /> communicates with the Fortona 48TL200 battery system via **RS485 (Modbus RTU)**.  
Connect the RS485 lines to the RJ45 communication ports on the front panel of the battery.


<RS485ConnectionTable firstColumn={["RS485 D+", "RS485 D–", "GND"]} />

<RS485AddressNote />

---

## Configuration

### 1. Check RS485 Wiring
- Ensure that the **RS485 D+**, **RS485 D–**, and **GND** lines are correctly connected.  
- Use twisted-pair cable suitable for RS485 communication.  
- If multiple devices are connected to the same bus, terminate the last device according to RS485 best practices.  
- Verify that all devices share the same communication parameters.

> [!TIP] Communication parameters
> - **Protocol:** Modbus RTU  
> - **Baud rate:** 115200  
> - **Parity:** Odd or Even  
> - **Stop bits:** 1  
> - **Modbus address range:** 1–247 (each device must have a unique ID)

---

### 2. Configure the <BrandName /> <ControllerName />
In the <BrandName /> <ControllerName /> interface:
1. Add a new RS485 device.
2. Select **“Fortona 48TL200 Battery Modbus Protocol”**.
3. Enter the same RS485 parameters as above:
   - Baud rate: **115200**
   - Parity: **Odd** (or **Even**, depending on the system)
   - Stop bits: **1**
4. Set the correct **Modbus address** for the battery.
5. Save and apply the configuration.

> [!WARNING]
> Each Fortona 48TL200 battery must have a **unique Modbus slave ID**.  
> Avoid duplicate IDs on the same RS485 line.

---

### 3. Power On and Verify
1. Apply **54–60 VDC** to the battery system.  
2. Turn the **main switch ON**.  
3. The BMS will initialize — both LEDs on the front panel will blink during startup.  
4. Once the system is operational, both LEDs turn **solid**.  
5. The <BrandName /> <ControllerName /> should now automatically detect and read data from the battery.


> [!TIP]
> The battery automatically begins charging if the **state of charge (SOC)** is below 100%.

---



# FoxESS GMAX


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/customers/foxess/logo.png"
    alt="logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

## Supported Devices

<DeviceSupportTable
  devices={[
    {  
      type: "G-MAX",
      modbusTcp: "✅",
      rs485: "❌",
    },
    {  
      type: "G-MAX Plus",
      modbusTcp: "✅",
      rs485: "❌",
    },
    {  
      type: "T-MAX",
      modbusTcp: "✅",
      rs485: "❌",
    },
    {  
      type: "G-MAX EMU",
      modbusTcp: "✅",
      rs485: "✅",
    },
  ]}
  showModbusTcp={true}
  showRs485={true}
  showReactivePower={true}
/>



## Configuration

> [!IMPORTANT]
> Make sure that the battery and the <BrandName /> <ControllerName /> are connected to the same network /subnetwork.


# FoxESS H-Series


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/customers/foxess/logo.png"
    alt="logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

## Supported Devices

<DeviceSupportTable
  devices={[
    {  
      type: "H3 (Non-Pro, Non-Smart): → ❗See note below ❗",
      modbusTcp: "❌",
      rs485: "✅",
      curtailment: "❗(see below)",
      firmwareVersion: "Master: 2.05, Manager: 1.85 (*)"
    },
    {  
      type: "H3 AIO (All-In-One)",
      modbusTcp: "✅",
      rs485: "✅",
      curtailment: "❌",
      firmwareVersion: "Master: 1.33, Manager: 1.37 (*)"
    },
    {
      type: "H3-Smart",
      modbusTcp: "✅",
      rs485: "✅",
      curtailment: "⌛ (in development)",
      firmwareVersion: "Master: 1.25, Manager: 1.14 (*)"
    },
    {
      type: "H3-Pro",
      modbusTcp: "✅",
      rs485: "✅",
      curtailment: "⌛ (in development)",
      firmwareVersion: "Master: 1.62, Manager: 1.34 (*)"
    },
    {
      type: "H1",
      modbusTcp: "✅",
      rs485: "✅",
      curtailment: "(experimental, requires testing)",
      firmwareVersion: "Master: 1.70, Manager: 1.78 (*)"
    },
    {
      type: "H1-G2",
      modbusTcp: "✅",
      rs485: "✅",
      curtailment: "⌛ (in development)",
      firmwareVersion: "Master: 1.40, Manager: 1.54 (*)"
    },
    {
      type: "P3-SH",
      modbusTcp: "✅ (experimental)",
      rs485: "✅ (experimental)",
      curtailment: "⌛ (in development)",
      firmwareVersion: "Master: 1.62, Manager: 1.34 (*)"
    }
  ]}
  showModbusTcp={true}
  showRs485={true}
  showCurtailment={true} showReactivePower={true}
  showFirmwareVersion={true}
/>

> [!CAUTION] 
> ### H3 (Non-Pro, Non-Smart)
> The H3 (Non-Pro, Non-Smart) has different communication protocol depending on the inverter 'master version' and 'manager version'.
> Choose the corresponding integration based on the inverter's software versions.
>
> ✅ Curtailment is supported for  Firmware versions master v.2.05 and manager v.1.85 and below.
>
> ⌛ Curtailment is in development for Firmware versions master v.2.06 and manager v.1.86 and above.

> [!WARNING]
> The H3 (non-pro, non-smart) series uses a __different communication protocol__ than the H3 Pro and H3 Smart series.
> Therefore, when selecting the device type in the <BrandName /> <ControllerName />, you must be __very sure__ that you select the correct type.

> [!NOTE] 
> ### Supported Firmware versions
> (*) The integration may work for older firmware versions, but these are not tested.


<ClickableImage src="/img/customers/foxess/h3.png" alt="Image 1" maxWidth="450px" />

## Wiring


> [!WARNING]
> The default modbus address, or device ID, is 247. Keep this in mind when scanning for an inverter. 
> You can change the minimum and maximum bus addresses the controller will scan in the scan parameters.

### Ethernet
For correct ethernet wiring: Follow the [the guidelines for ethernet wiring](/Controller/wiring-best-practices/#ethernet).

> [!WARNING]
> You cannot connect it through the WiFi dongle.

### RS485
The inverter can be connected to the <BrandName /> <ControllerName /> via RS485. This is done through connection [J] in the image below.
<RS485ConnectionTable firstColumn={["Logger 485A / pin 1", "Logger 485B / pin 2", "N/A"]} />

<ClickableImage src="/img/customers/foxess/h3-cables.png" alt="Image 1" maxWidth="450px" />


#### RS485 H3 Pro
<RS485ConnectionTable firstColumn={["EMS 485A / pin 17", "EMS 485B / pin 18", "N/A"]} />
<ClickableImage src="/img/customers/foxess/h3-pro-cables.png" alt="Image 1" maxWidth="450px" />


## Configuration for H3 (Non-Pro, Non-Smart) and H1-G2

### 1. Activation monitoring & management inverter
The control must be activated through the inverter, and the meter must be deactivated. This is done through the display in the Feature Parm menu.
First, open the Feature Parm menu as follows:
1. Go to the Menu.
<ClickableImage src="/img/customers/foxess/h3-menu-1.png" alt="Image 1" maxWidth="250px" />
2. Enter the password. The default is 0000.
<ClickableImage src="/img/customers/foxess/h3-menu-2.png" alt="Image 1" maxWidth="250px" />
3. Select Settings.
<ClickableImage src="/img/customers/foxess/h3-menu-2.png" alt="Image 1" maxWidth="250px" />
4. Select Feature Parm.

### 2. Activating remote control
Use the display further from the Feature page to activate the control, following the steps below:
1. Select Remote control.
<ClickableImage src="/img/customers/foxess/h3-menu-4.jpg" alt="Image 1" maxWidth="250px" />
2. Set it to Enable.
<ClickableImage src="/img/customers/foxess/h3-menu-5.jpg" alt="Image 1" maxWidth="250px" />

### 3. Deactivating meter
The meter must be deactivated. The control will be taken over by the <BrandName /> <ControllerName />. Therefore, the meter should not be connected to the inverter but to the <BrandName /> <ControllerName />. To deactivate the meter in the settings, follow these steps:
1. Go back to the Feature page.
2. Select Meter1.
<ClickableImage src="/img/customers/foxess/h3-menu-6.jpg" alt="Image 1" maxWidth="250px" />
3. Select Set.
<ClickableImage src="/img/customers/foxess/h3-menu-7.jpg" alt="Image 1" maxWidth="250px" />
4. Set it to Disable.
<ClickableImage src="/img/customers/foxess/h3-menu-8.jpg" alt="Image 1" maxWidth="250px" />

### 4. Settings inverter address
The address of the inverter can also be set through the display.
1. Go to the Settings menu as described earlier.
2. Select Communication.
3. Select RS485.
4. Select Device ID.
5. Set the device ID to the desired address.
If you connect multiple devices to the same RS485 bus, you must give each a unique address.

<ClickableImage src="/img/customers/foxess/h3-menu-9.jpg" alt="Image 1" maxWidth="250px" />

> [!TIP] 
> ### Faster scanning
> The <BrandName /> <ControllerName /> starts scanning from address 1 by default. Choosing a lower address will make your inverter be found faster.

> [!WARNING] 
> ### Multiple inverters
> If you have multiple inverters then it is important to set the parallel addresses, each inverter should have a different address.

## Configuration for H3-smart and H3-Pro

Remote control is activated by default, you do not need to change any settings.

Changing the inverter address (or device ID) can be done in the smae way as the H3 (see above).


# FoxESS R-Series


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/customers/foxess/logo.png"
    alt="logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

## Supported Devices

<DeviceSupportTable
  devices={[
    {  
      type: "R100",
      modbusTcp: "✅",
      rs485: "✅",
      curtailment: "✅",
    }
      ]}
  showModbusTcp={true}
  showRs485={true}
  showCurtailment={true} showReactivePower={true}
/>

## Wiring

The <BrandName /> <ControllerName /> and the FoxESS R Series solar inverters communicate via RS485 or Ethernet.

### Ethernet
For correct ethernet wiring: Follow the [the guidelines for ethernet wiring](/Controller/wiring-best-practices/#ethernet).

### RS485
<RS485ConnectionTable firstColumn={["A", "B", "GND (if available)"]} />

# Foxess


import { FolderOverview } from '@/components/FolderOverview';

# Foxess

<FolderOverview folder="Controller/Devices/PV-hybrid-and-battery-inverters/FoxESS" />


# Frax


import { BrandName, ControllerName } from '@site/src/components/customFields';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/customers/frax/logo.png"
    alt="logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

## Supported Devices

<DeviceSupportTable
  devices={[
    {
        type: "Pylontech",
        variants: "XXL",
        modbusTcp: "✅",
        rs485: "❌",
        curtailment: "❌"
    }
  ]}
  showVariants={true}
  showModbusTcp={true}
  showRs485={true}
  curtailment={true}
  showReactivePower={true}
/>

## Wiring

### Ethernet
For correct ethernet wiring: Follow the [the guidelines for ethernet wiring](/Controller/wiring-best-practices/#ethernet).

> [!TIP]
> Make note of the Modbus TCP port number in the TCP/IP Configuration menu. The default is typically port 502, but this may vary depending on your inverter's firmware version.


# Fronius


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

![logo](/img/customers/fronius/logo.png)

# Fronius

## Supported Devices

<DeviceSupportTable
  devices={[
{ type: 'GEN24', modbusTcp: '✅', rs485: '✅', curtailment: '✅' },
{ type: 'GEN24 Plus', modbusTcp: '✅', rs485: '✅', curtailment: '✅' },
{ type: 'Symo', modbusTcp: '✅', rs485: '✅', curtailment: '✅' },
{ type: 'Primo', modbusTcp: '✅', rs485: '✅', curtailment: '✅' },
{ type: 'Tauro', modbusTcp: '✅', rs485: '✅', curtailment: '✅' },
{ type: 'Eco', modbusTcp: '✅', rs485: '✅', curtailment: '✅' },
{ type: 'Agilo', modbusTcp: '✅', rs485: '✅', curtailment: '✅' },
{ type: 'Verto', modbusTcp: '✅', rs485: '✅', curtailment: '✅' },
{ type: 'Verto Plus', modbusTcp: '✅', rs485: '✅', curtailment: '✅' },
]}
  showModbusTcp={true}
  showRs485={true}
  showCurtailment={true} showReactivePower={true}
/>

## Wiring

For correct ethernet wiring: Follow the [the guidelines for ethernet wiring](/Controller/wiring-best-practices/#ethernet).

## Configuration

### 1. Modbus TCP must be enabled.

Activate Modbus TCP/IP in the inverter's interface: see the
link below for instructions on how to connect to the
inverter.
[https://www.youtube.com/watch?v\=T25omrhcroU](https://www.youtube.com/watch?v=T25omrhcroU)

1. Select the menu Communication > Modbus
2. Activate Slave as Modbus TCP
3. Choose SunSpec Model Type "Float"
4. Enable Inverter Control via Modbus
5. Save your settings by clicking Save

<img alt="Image" maxwidth="100%" src="/img/customers/fronius/fronius-Modbus.png" />

# GoodWe


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/customers/goodwe/logo.png"
    alt="logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

## Supported Devices

<DeviceSupportTable
  showVariants showModbusTcp showRs485 showCurtailment
  devices={[
    {
        type: 'Energy Storage',
        variants: "EH",
        modbusTcp: "⚠️",
        rs485: "✅",
        curtailment: "✅",
      instructionVideos: [{"videoId": "Q2VJp6JDkq0", "title": "GoodWe EH / EH PLUS+ / BH — plate with four cable glands"}]
    }, {
        type: 'Energy Storage',
        variants: "ET",
        modbusTcp: "⚠️",
        rs485: "✅",
        curtailment: "✅",
      instructionVideos: [{"videoId": "iHsh-xsXaVk", "title": "GoodWe ET / ET PLUS+ / BT — EMS on the plate with two cable glands"}, {"videoId": "XNwGj1ORKoc", "title": "GoodWe ET / ET PLUS+ / BT — 18PIN"}, {"videoId": "GeEp4XcxpKw", "title": "GoodWe ET 12–30 kW — COM2"}, {"videoId": "IItv90JCMFc", "title": "GoodWe ET 40–50 kW (-10) — EMS 22/23"}, {"videoId": "P9yyTgBCZxU", "title": "GoodWe ET 50–100 / BT 75–100 G10 — E1/E2"}]
    }, {
        type: 'Energy Storage',
        variants: "ET G2",
        modbusTcp: "⚠️",
        rs485: "✅",
        curtailment: "✅",
      instructionVideos: [{"videoId": "oWFOJlocZbA", "title": "GoodWe ET G2 — COM1"}]
    }, {
        type: 'Energy Storage',
        variants: 'BH',
        modbusTcp: '⚠️',
        rs485: '✅',
        curtailment: "✅",
      instructionVideos: [{"videoId": "Q2VJp6JDkq0", "title": "GoodWe EH / EH PLUS+ / BH — plate with four cable glands"}]
    }, {
        type: 'Energy Storage',
        variants: "BT",
        modbusTcp: "⚠️",
        rs485: "✅",
        curtailment: "✅",
      instructionVideos: [{"videoId": "iHsh-xsXaVk", "title": "GoodWe ET / ET PLUS+ / BT — EMS on the plate with two cable glands"}, {"videoId": "XNwGj1ORKoc", "title": "GoodWe ET / ET PLUS+ / BT — 18PIN"}, {"videoId": "P9yyTgBCZxU", "title": "GoodWe ET 50–100 / BT 75–100 G10 — E1/E2"}]
    }, {
        type: 'Energy Storage',
        variants: "ES G2",
        modbusTcp: "⚠️",
        rs485: "✅",
        curtailment: "✅",
      instructionVideos: [{"videoId": "1JzPyyQuRUg", "title": "GoodWe ES G2 / SBP G2 — COM2"}]
    }, {
        type: 'Energy Storage',
        variants: "SBP G2",
        modbusTcp: "⚠️",
        rs485: "✅",
        curtailment: "✅",
      instructionVideos: [{"videoId": "1JzPyyQuRUg", "title": "GoodWe ES G2 / SBP G2 — COM2"}]
    }, {
        type: 'Energy Storage (Old models)',
        variants: "EM",
        modbusTcp: "❌",
        rs485: "✅",
        curtailment: "🛠️",
      instructionVideos: [{"videoId": "AeXAbOU-7Uk", "title": "GoodWe EM"}]
    }, {
        type: 'Energy Storage (Old models)',
        variants: "ES",
        modbusTcp: "❌",
        rs485: "✅",
        curtailment: "🛠️",
      instructionVideos: [{"videoId": "T9a_JufCnU8", "title": "GoodWe ES"}]
    }, {
        type: 'Energy Storage (Old models)',
        variants: "ESA",
        modbusTcp: "❌",
        rs485: "✅",
        curtailment: "🛠️"
    }, {
        type: 'Energy Storage (Old models)',
        variants: "SBP",
        modbusTcp: "❌",
        rs485: "✅",
        curtailment: "🛠️",
      instructionVideos: [{"videoId": "IQO61FpSYYU", "title": "GoodWe SBP"}]
    }, {
        type: 'Residential',
        variants: 'MS G3',
        modbusTcp: '❌',
        rs485: '✅',
        curtailment: '🛠️',
      instructionVideos: [{"videoId": "5xUOwHTb0sg", "title": "GoodWe MS G3"}]
    }, {
        type: 'Residential',
        variants: 'XS G3',
        modbusTcp: '❌',
        rs485: '✅',
        curtailment: '🛠️',
      instructionVideos: [{"videoId": "Boyq_SlZimU", "title": "GoodWe XS G3"}]
    }, {
        type: 'Residential',
        variants: 'DNS G3',
        modbusTcp: '❌',
        rs485: '✅',
        curtailment: '🛠️',
      instructionVideos: [{"videoId": "R5QxNmAA5A0", "title": "GoodWe DNS G3"}]
    }, {
        type: 'Residential',
        variants: 'SDT G3',
        modbusTcp: '❌',
        rs485: '✅',
        curtailment: '🛠️',
      instructionVideos: [{"videoId": "dhzRVAYDyp4", "title": "GoodWe SDT G3 — COM A (GW40K-SDT-C30)"}, {"videoId": "CcPUwIzAPAA", "title": "GoodWe SDT G3 — COM B (GW50K-SDT-C30)"}, {"videoId": "IT8xDuL_LFI", "title": "GoodWe SDT G3 — COM C (GW20K-SDT-AU30)"}, {"videoId": "HzQvGhXxNzg", "title": "GoodWe SDT G3 — COM D (GW10K-SDT-30)"}]
    }, {
        type: 'Grid-Tied',
        variants: 'MT',
        modbusTcp: '❌',
        rs485: '✅',
        curtailment: '✅',
      instructionVideos: [{"videoId": "OvBAbsMB0kI", "title": "GoodWe MT / MT G2 — 264 mm, legacy 6-pin connection"}, {"videoId": "Vz0PGSUhy58", "title": "GoodWe MT / MT G2 — 267 mm, legacy 6-pin connection"}]
    }, {
        type: 'Grid-Tied',
        variants: 'MT G2',
        modbusTcp: '❌',
        rs485: '✅',
        curtailment: '✅',
      instructionVideos: [{"videoId": "OvBAbsMB0kI", "title": "GoodWe MT / MT G2 — 264 mm, legacy 6-pin connection"}, {"videoId": "Vz0PGSUhy58", "title": "GoodWe MT / MT G2 — 267 mm, legacy 6-pin connection"}]
    }, {
        type: 'Grid-Tied',
        variants: 'SMT',
        modbusTcp: '❌',
        rs485: '✅',
        curtailment: '✅',
      instructionVideos: [{"videoId": "0JjN0xiyOo0", "title": "GoodWe SMT — 12–36 kW, 6-pin connection"}, {"videoId": "pzwPW6xMrxQ", "title": "GoodWe SMT — 12–36 kW, 5-pin connection"}, {"videoId": "yGWFFoMRVps", "title": "GoodWe SMT — 30–60 kW, large enclosure, 6-pin connection"}, {"videoId": "Pgwek82QGAA", "title": "GoodWe SMT — 30–60 kW, large enclosure, 5-pin connection"}, {"videoId": "ZLoT0BUXY8s", "title": "GoodWe SMT — 50/60 kW EU, 5-pin connection"}]
    }, {
        type: 'Grid-Tied',
        variants: 'SDT G2',
        modbusTcp: '❌',
        rs485: '✅',
        curtailment: '✅',
      instructionVideos: [{"videoId": "3MCOijC3sbw", "title": "GoodWe SDT G2 — 4–6 kW, compact enclosure, 6-pin connection"}, {"videoId": "MOyKY1BebBw", "title": "GoodWe SDT G2 — 4–6 kW, compact enclosure, 2-pin connection"}, {"videoId": "IGw5FKElyWE", "title": "GoodWe SDT G2 — 8–10 kW, compact enclosure, 6-pin connection"}, {"videoId": "loBg31UNqdE", "title": "GoodWe SDT G2 — 8–10 kW, compact enclosure, 2-pin connection"}, {"videoId": "fxKiRA76eLg", "title": "GoodWe SDT G2 — 12–15 kW, compact enclosure, 6-pin connection"}, {"videoId": "2amjdJVhm30", "title": "GoodWe SDT G2 — 12–15 kW, compact enclosure, 2-pin connection"}, {"videoId": "LrIheopVpY0", "title": "GoodWe SDT G2 — KT/AU, 415 mm enclosure, 6-pin connection"}, {"videoId": "VZlObbbObAU", "title": "GoodWe SDT G2 — KT/AU, 415 mm enclosure, 2-pin connection"}, {"videoId": "ygqJp9iQEG8", "title": "GoodWe SDT G2 — 8–10 kW -20, 415 mm enclosure, 6-pin connection"}, {"videoId": "wAFC91pWPp0", "title": "GoodWe SDT G2 — 8–10 kW -20, 415 mm enclosure, 2-pin connection"}, {"videoId": "5Tw65Rp4Y2U", "title": "GoodWe SDT G2 — 12–20 kW -20, deep enclosure, 6-pin connection"}, {"videoId": "jqY7v0Gl6qI", "title": "GoodWe SDT G2 — 12–20 kW -20, deep enclosure, 2-pin connection"}]
    }, {
        type: 'Grid-Tied',
        variants: 'MS',
        modbusTcp: '❌',
        rs485: '✅',
        curtailment: '✅',
      instructionVideos: [{"videoId": "EFmPDGd_iQA", "title": "GoodWe MS — 4-pin connection"}]
    }, {
        type: 'Grid-Tied',
        variants: 'DNS',
        modbusTcp: '❌',
        rs485: '✅',
        curtailment: '✅',
      instructionVideos: [{"videoId": "vn-r-bXrUbU", "title": "GoodWe DNS — 6-pin connection"}]
    }, {
        type: 'Grid-Tied',
        variants: 'XS',
        modbusTcp: '❌',
        rs485: '✅',
        curtailment: '✅',
      instructionVideos: [{"videoId": "616S9VfmSp4", "title": "GoodWe XS / XS PLUS+ — 8-pin connection"}]
    }, {
        type: 'Grid-Tied C&I',
        variants: 'GT',
        modbusTcp: '❌',
        rs485: '✅',
        curtailment: '✅',
      instructionVideos: [{"videoId": "VXOjWWQDVG8", "title": "GoodWe GT 75LV / 100–125 kW — 8-pin connection"}, {"videoId": "Es7OOayIx04", "title": "GoodWe GT G10 100/150 kW — block A"}]
    }, {
        type: 'Grid-Tied C&I',
        variants: 'HT',
        modbusTcp: '❌',
        rs485: '✅',
        curtailment: '✅',
      instructionVideos: [{"videoId": "fUtyPldqvIQ", "title": "GoodWe HT 73–136 kW — COM2"}, {"videoId": "t_rdYq1RE38", "title": "GoodWe HT 225/250 kW — COM2"}]
    }
  ]}
  showReactivePower={true}
/>

> [!WARNING]
> Modbus TCP is only available using a **Wi-Fi/Lan kit**

## Configuration

 ### 1: Connecting the RS485
 <img src="/img/customers/goodwe/goodwe_scheme.png" alt="Image" maxWidth="100%" />
 

### 2: SolarGo Settings 
| Step | Image |
|------|-------|
| **2a**. Connect to the inverter’s WiFi and open the **SolarGo** app. | <img src="/img/customers/goodwe/GoodweWifi.png" alt="Image" maxWidth="100%" /> |
| **2b**. Click **More**. | <img src="/img/customers/goodwe/more.png" alt="Image" maxWidth="100%" />|
| **2c**. Click **Advanced Setting** (you can find the password in the **SolarGo manual**). | <img src="/img/customers/goodwe/advancedsettings.png" alt="Image" maxWidth="100%" /> |
| **2d**. Select **Grid Parameter Setting**. | <img src="/img/customers/goodwe/Grid_parameter_settings.png" alt="Image" maxWidth="100%" /> |
| **2e**. Turn off **Power Limit** (If it is on, power from the battery cannot be fed into the grid). | <img src="/img/customers/goodwe/PowerLimit.png" alt="Image" maxWidth="100%" />|
| **2f**. Go back and click **Cancel** (these settings will be saved anyway, no restart is needed). | <img src="/img/customers/goodwe/cancel.png" alt="Image" maxWidth="100%" /> |

---

### 3: Battery Settings in SolarGo.

| Step | Image |
|------|-------|
| **3a**. Select **Battery Setting**. | <img src="/img/customers/goodwe/batterysettings.png" alt="Image" maxWidth="100%" /> |
| **3b**. Turn off **SOC Protection**. | <img src="/img/customers/goodwe/socProtection.png" alt="Image" maxWidth="100%" />  |
| **3c**. Go back and click **Cancel** (these settings will be saved anyway, no restart is needed). |<img src="/img/customers/goodwe/cancel.png" alt="Image" maxWidth="100%" />  |

## Wiring
If you have multiple GoodWe devices, you can change their addresses separately or connect them in a daisy chain. Follow the [wiring guidelines](/Controller/wiring-best-practices/#wiring).


# Gotion


import { BrandName, ControllerName } from '@site/src/components/customFields';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import RS485AddressNote from '@site/src/components/RS485AddressNote';

<img
    src="/img/customers/gotion/Logo_Gotion.png"
    alt="logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

# Gotion PCS Cabinets

## Supported Devices


<DeviceSupportTable
  devices={[
    { type: 'ESC-R100-211-CE',  modbusTcp: '✅', rs485: '✅'},
  ]}
  showModbusTcp={true}
  showRs485={true}
  showReactivePower={true}
/>

## Wiring

The <BrandName /> <ControllerName /> and the Gotion storage systems communicate via Ethernet or RS485.

### Ethernet
For correct ethernet wiring: Follow the [the guidelines for ethernet wiring](/Controller/wiring-best-practices/#ethernet).

### RS485
<RS485AddressNote />


# Greener / Alfen


import DeviceSupportTable from '@site/src/components/DeviceSupportTable';
import ClickableImage      from '@site/src/components/ClickableImage';

<img
  src="/img/sgo/Logo_Greener.png"
  alt="Greener"
  style={{ display: "block", margin: "0 auto", width: "40%" }}
/>

## Supported devices

<DeviceSupportTable
  devices={[
    { type: 'Alfen Battery Container (250 kWh – 2 MWh)', api: '✅' },
  ]}
  showApi
  showReactivePower={true}
/>

---

## Configuration steps

1. **API credentials**  
   - Retrieve the *API key* and *Battery ID* in the Greener portal.  
   - They are required by the driver’s “User Inputs”.

2. **Add the device**  
   - In *Integrations → Add device* choose **Greener API for Alfen Battery Control**.  
   - Enter the API key and Battery ID exactly as provided.  
   - Confirm → the container appears with SOC and power.

3. **Optional – setpoint control**  
   When *Smart-Grid Mode* is enabled the driver sends a constant-power
   set-point (positive = charge, negative = discharge) to  
   `/control/batteries/<ID>/command/set_constant_power_setpoint`.

---

## Metrics exposed

| Key                    | Description                     | Unit |
|------------------------|---------------------------------|------|
| `actualPowerTot_W`     | Battery power (+ = discharge)   | W    |
| `stateOfCharge_frac`   | State of Charge (0–1)           | –    |
| `importedEnergyDeltaTot_Wh` | Energy charged Δ            | Wh   |
| `exportedEnergyDeltaTot_Wh` | Energy discharged Δ         | Wh   |

---

## Troubleshooting

* **401 Unauthorized** – check the API key string (no spaces, full length).  
* **404 on Battery ID** – verify the exact `GREENER_XXX` identifier.  
* **Power not updating** – Greener API provides new datapoints every ~10 s;  
  ensure outbound HTTPS (443) traffic is allowed.


# Growatt MAX Series


import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

# Growatt MAX Series

## Supported Devices

<DeviceSupportTable
  devices={[
    {
        type: "MAX 50-100KTL3 LV/MV",
        modbusTcp: "❌",
        rs485: "✅",
        curtailment: "✅"
    },
    {
        type: "MAX 175-253KTL3-X HV",
        modbusTcp: "❌",
        rs485: "✅",
        curtailment: "✅"

    },
    {
        type: "MAX 80-150KTL3-X LV/MV",
        modbusTcp: "❌",
        rs485: "✅",
        curtailment: "✅"
    },
    {
        type: "MAX 100-150KYL3-X2 LV/MV",
        modbusTcp: "❌",
        rs485: "✅",
        curtailment: "✅"
    },
    {
        type: "MAX 320-350KTL3-X",
        modbusTcp: "❌",
        rs485: "✅",
        curtailment: "✅"
    }
]}

showModbusTcp={true}
showRs485={true}
showCurtailment={true} showReactivePower={true}
/>


# Growatt


import { FolderOverview } from '@/components/FolderOverview';

# Growatt

<FolderOverview folder="Controller/Devices/PV-hybrid-and-battery-inverters/Growatt" />


# Growatt MIC Series


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/customers/growatt/logo.png"
    alt="logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

## Supported Devices

<DeviceSupportTable
  devices={[
    {
        type: "MIC 600TL-X",
        modbusTcp: "❌",
        rs485: "",
        curtailment: "✅",
      instructionVideos: [{"videoId": "E8w9BXGQt9w", "title": "Growatt MIC 600–3300TL-X", "description": "Models: MIC 600TL-X, MIC 750TL-X, MIC 1000TL-X, MIC 1500TL-X, MIC 2000TL-X, MIC 2500TL-X, MIC 3000TL-X, MIC 3300TL-X."}]
    },
    {
        type: "MIC 750TL-X",
        modbusTcp: "❌",
        rs485: "✅",
        curtailment: "✅",
      instructionVideos: [{"videoId": "E8w9BXGQt9w", "title": "Growatt MIC 600–3300TL-X", "description": "Models: MIC 600TL-X, MIC 750TL-X, MIC 1000TL-X, MIC 1500TL-X, MIC 2000TL-X, MIC 2500TL-X, MIC 3000TL-X, MIC 3300TL-X."}]
    },
    {
        type: "MIC 1000TL-X",
        modbusTcp: "❌",
        rs485: "✅",
        curtailment: "✅",
      instructionVideos: [{"videoId": "E8w9BXGQt9w", "title": "Growatt MIC 600–3300TL-X", "description": "Models: MIC 600TL-X, MIC 750TL-X, MIC 1000TL-X, MIC 1500TL-X, MIC 2000TL-X, MIC 2500TL-X, MIC 3000TL-X, MIC 3300TL-X."}]
    },
    {
        type: "MIC 1500TL-X",
        modbusTcp: "❌",
        rs485: "✅",
        curtailment: "✅",
      instructionVideos: [{"videoId": "E8w9BXGQt9w", "title": "Growatt MIC 600–3300TL-X", "description": "Models: MIC 600TL-X, MIC 750TL-X, MIC 1000TL-X, MIC 1500TL-X, MIC 2000TL-X, MIC 2500TL-X, MIC 3000TL-X, MIC 3300TL-X."}]
    },
    {
        type: "MIC 2000TL-X",
        modbusTcp: "❌",
        rs485: "✅",
        curtailment: "✅",
      instructionVideos: [{"videoId": "E8w9BXGQt9w", "title": "Growatt MIC 600–3300TL-X", "description": "Models: MIC 600TL-X, MIC 750TL-X, MIC 1000TL-X, MIC 1500TL-X, MIC 2000TL-X, MIC 2500TL-X, MIC 3000TL-X, MIC 3300TL-X."}]
    },
    {
        type: "MIC 2500TL-X",
        modbusTcp: "❌",
        rs485: "✅",
        curtailment: "✅",
      instructionVideos: [{"videoId": "E8w9BXGQt9w", "title": "Growatt MIC 600–3300TL-X", "description": "Models: MIC 600TL-X, MIC 750TL-X, MIC 1000TL-X, MIC 1500TL-X, MIC 2000TL-X, MIC 2500TL-X, MIC 3000TL-X, MIC 3300TL-X."}]
    },
    {
        type: "MIC 3000TL-X",
        modbusTcp: "❌",
        rs485: "✅",
        curtailment: "✅",
      instructionVideos: [{"videoId": "E8w9BXGQt9w", "title": "Growatt MIC 600–3300TL-X", "description": "Models: MIC 600TL-X, MIC 750TL-X, MIC 1000TL-X, MIC 1500TL-X, MIC 2000TL-X, MIC 2500TL-X, MIC 3000TL-X, MIC 3300TL-X."}]
    },
    {
        type: "MIC 3300TL-X",
        modbusTcp: "❌",
        rs485: "✅",
        curtailment: "✅",
      instructionVideos: [{"videoId": "E8w9BXGQt9w", "title": "Growatt MIC 600–3300TL-X", "description": "Models: MIC 600TL-X, MIC 750TL-X, MIC 1000TL-X, MIC 1500TL-X, MIC 2000TL-X, MIC 2500TL-X, MIC 3000TL-X, MIC 3300TL-X."}]
    }

  ]}
  showModbusTcp={true}
  showRs485={true}
  showCurtailment={true} showReactivePower={true}
/>


<ClickableImage src="/img/customers/growatt/mic.jpg" alt="Image 1" maxWidth="250px" />

## Wiring

### RS485
<RS485ConnectionTable firstColumn={["RS485 A1", "RS485 B1", "N/A"]} />

## Configuration
<RS485AddressNote />

By default, the inverter is set to address 1. This can be changed via the settings menu of the inverter. This is only necessary if several devices are connected to the RS485 communication bus.

You can change the address of the inverter via the touch control. It works as follows:

| Touch control | Impact |
|:--:|:--:|
| Touch once | Change display or number + 1 |
| Touch twice | Enter or confirm |
| Touching three times | Previous menu |
| Keep touched for 5 seconds | <ul><li>Confirm country setting or number.</li><li>Restore default value.</li></ul> |

Change the address by going to the "Set Comaddr" menu as shown in the image to the left or above. Set the address to a unique value. See Chapter 7 of the inverter manual for more information.


# Growatt MID Series


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/customers/growatt/logo.png"
    alt="logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

## Supported Devices


<DeviceSupportTable
  devices={[
    {
      type: "MID 11-30K-TL3-XH",
      manual: "https://growatt.tech/wp-content/uploads/shared-files/MID_11-30KTL3-XH_User_Manual_EN_202307.pdf",
      modbusTcp: "❌",
      rs485: "✅",
      curtailment: "✅",
      instructionVideos: [{"videoId": "tFb4tpCZEBU", "title": "Growatt MID 11–30KTL3-XH · 30-pin", "description": "Models: MID 11KTL3-XH, MID 12KTL3-XH, MID 13KTL3-XH, MID 15KTL3-XH, MID 17KTL3-XH, MID 20KTL3-XH, MID 25KTL3-XH, MID 30KTL3-XH."}]
    },
    {
      type: "MID 17-25KTL3-X;",
      modbusTcp: "❌",
      rs485: "✅",
      curtailment: "✅",
      instructionVideos: [{"videoId": "uf5vDV13nTc", "title": "Growatt MID 17–25KTL3-X · 8-pin", "description": "Models: MID 17KTL3-X, MID 20KTL3-X, MID 22KTL3-X, MID 25KTL3-X."}]
    },
    {
        type: "MID 20-30KTL3-X2;",
        modbusTcp: "❌",
        rs485: "✅",
        curtailment: "✅"
            },
    {
        type: "MID 25-30KTL3-X2 Pro/X2 Pro.E",
        modbusTcp: "❌",
        rs485: "✅",
        curtailment: "✅"
    },
    {
        type: "MID 33-50KTL3-X2/X2 Pro/X2 Pro.E",
        modbusTcp: "❌",
        rs485: "✅",
        curtailment: "✅",
      instructionVideos: [{"videoId": "7hXO832jUQA", "title": "Growatt MID 33–50KTL3-X2 · 16-pin", "description": "Models: MID 33KTL3-X2, MID 36KTL3-X2, MID 40KTL3-X2, MID 50KTL3-X2."}]
    },
    {
        type: "MID 30-40KTL3-X",
        modbusTcp: "❌",
        rs485: "✅",
        curtailment: "✅",
       instructionVideos: [{"videoId": "WHnWtzzw3vY", "title": "Growatt MID 30–40KTL3-X · 16-pin", "description": "Models: MID 30KTL3-X, MID 33KTL3-X, MID 36KTL3-X, MID 40KTL3-X."}]
     },
    {
        type: "MID 33-36KTL3-X(Pro.E)",
        modbusTcp: "❌",
        rs485: "✅",
        curtailment: "✅"
       },
      {
        type: "MID 3-33KTL3-X3",
        modbusTcp: "❌",
        rs485: "✅",
        curtailment: "✅"
      }
        
  ]}
  showManual={true}
  showModbusTcp={true}
  showRs485={true}
  showCurtailment={true} showReactivePower={true}
/>



## Wiring

### RS485 - MID 11-30K-TL3-XH

<RS485ConnectionTable firstColumn={["RS485 A1", "RS485 B1", "N/A"]} />
<ClickableImage src="/img/customers/growatt/GrowattMID-11-30K-TL3-XH.png" alt="Image" maxWidth="450px" />

# Growatt MIN Series


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/customers/growatt/logo.png"
    alt="logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

## Supported Devices



<DeviceSupportTable
  devices={[
    {
        type: "MIN 2500-6000TL-X",
        manual: "https://en.growatt.com/upload/file/20221206/b17e6c83f1a6fe0045412cf8532236b2.pdf",
        modbusTcp: "❌",
        rs485: "✅",
        curtailment: "✅",
          instructionVideos: [{"videoId": "I1KbDaqrDmw", "title": "Growatt MIN 2500–6000TL-X", "description": "Models: MIN 2500TL-X, MIN 3000TL-X, MIN 3600TL-X, MIN 4200TL-X, MIN 4600TL-X, MIN 5000TL-X, MIN 6000TL-X."}]
        },
        {
        type: "MIN 2500-6000TL-XH",
        manual: "https://en.growatt.com/upload/file/MIN_2500-6000TL-XH_User_Manual_EN_202303.pdf",
        modbusTcp: "❌",
        rs485: "✅",
        curtailment: "✅"
        },
        {
        type: "MIN 7000-10000TL-X",
        manual: "https://en.growatt.com/upload/file/20220830/ac27c1b60750ff0c62fe219715e944a3.pdf",
        modbusTcp: "❌",
        rs485: "✅",
        curtailment: "✅",
          instructionVideos: [{"videoId": "dfP7BU8JLIk", "title": "Growatt MIN 7–10K TL-X/X2 · rectangular 16-pin", "description": "Models: MIN 7000TL-X, MIN 8000TL-X, MIN 9000TL-X, MIN 10000TL-X, MIN 7000TL-X2, MIN 8000TL-X2, MIN 9000TL-X2, MIN 10000TL-X2."}, {"videoId": "otaCHLmRQm4", "title": "Growatt MIN 7–10K TL-X/X2 · round 16-pin", "description": "Models: MIN 7000TL-X, MIN 8000TL-X, MIN 9000TL-X, MIN 10000TL-X, MIN 7000TL-X2, MIN 8000TL-X2, MIN 9000TL-X2, MIN 10000TL-X2."}, {"videoId": "cye-b3GEkgc", "title": "Growatt MIN 7–10K TL-X/X2 · round 4-pin", "description": "Models: MIN 7000TL-X, MIN 8000TL-X, MIN 9000TL-X, MIN 10000TL-X, MIN 7000TL-X2, MIN 8000TL-X2, MIN 9000TL-X2, MIN 10000TL-X2."}]
        },
        {
        type: "MIN 7000-10000TL-X2",
        manual: "https://en.growatt.com/upload/file/MIN_7-10KTL-X2_User_Manual_EN.pdf",
        modbusTcp: "❌",
        rs485: "✅",
        curtailment: "✅",
  instructionVideos: [{"videoId": "dfP7BU8JLIk", "title": "Growatt MIN 7–10K TL-X/X2 · rectangular 16-pin", "description": "Models: MIN 7000TL-X, MIN 8000TL-X, MIN 9000TL-X, MIN 10000TL-X, MIN 7000TL-X2, MIN 8000TL-X2, MIN 9000TL-X2, MIN 10000TL-X2."}, {"videoId": "otaCHLmRQm4", "title": "Growatt MIN 7–10K TL-X/X2 · round 16-pin", "description": "Models: MIN 7000TL-X, MIN 8000TL-X, MIN 9000TL-X, MIN 10000TL-X, MIN 7000TL-X2, MIN 8000TL-X2, MIN 9000TL-X2, MIN 10000TL-X2."}, {"videoId": "cye-b3GEkgc", "title": "Growatt MIN 7–10K TL-X/X2 · round 4-pin", "description": "Models: MIN 7000TL-X, MIN 8000TL-X, MIN 9000TL-X, MIN 10000TL-X, MIN 7000TL-X2, MIN 8000TL-X2, MIN 9000TL-X2, MIN 10000TL-X2."}]
}
    
    ]}
    showCurtailment={true} showReactivePower={true}
  showManual={true}
  showModbusTcp={true}
  showRs485={true}
/>

## Wiring

### RS485 - MIN 2500-6000TL

<RS485ConnectionTable firstColumn={["RS485 A1", "RS485 B1", "N/A"]} />
<ClickableImage src="/img/customers/growatt/GrowattMIN2500-6000TL-X.png" alt="Image" maxWidth="450px" />

### RS485 - MIN 7000-10000TL

<RS485ConnectionTable firstColumn={["RS485 A1", "RS485 B1", "N/A"]} />
<ClickableImage src="/img/customers/growatt/GrowattMIN7000-1000TL-X4PIN.png" alt="Image" maxWidth="450px" />
<ClickableImage src="/img/customers/growatt/GrowattMIN7000-1000TL-X16PIN.png" alt="Image" maxWidth="450px" />

<RS485AddressNote />

# Growatt MOD Series


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/customers/growatt/logo.png"
    alt="logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

## Supported Devices


<DeviceSupportTable
  devices={[
    { 
      type: 'MOD 3-10K-TL3-XH', 
      manual: 'https://growatt.tech/wp-content/uploads/shared-files/MOD-3-10KTL3-XH-User-Manual-EN-202201.pdf', 
      modbusTcp: '❌', 
      rs485: '✅',
      curtailment: "✅",
      instructionVideos: [{"videoId": "JOQfFqGRrmk", "title": "Growatt MOD 3–6KTL3-XH · 30-pin", "description": "Models: MOD 3000TL3-XH, MOD 4000TL3-XH, MOD 5000TL3-XH, MOD 6000TL3-XH."}, {"videoId": "uRJADSlfn1g", "title": "Growatt MOD 7–10KTL3-XH · 30-pin", "description": "Models: MOD 7000TL3-XH, MOD 8000TL3-XH, MOD 9000TL3-XH, MOD 10KTL3-XH."}]
    },
    { 
      type: 'MOD 3-15K-TL3-X', 
      manual: 'https://growatt.tech/wp-content/uploads/shared-files/MOD-3-15KTL3-X-User-Manual-EN-202201.pdf', 
      modbusTcp: '❌', 
      rs485: '✅' ,
      curtailment: "✅",
      instructionVideos: [{"videoId": "P1hmp3gK0yk", "title": "Growatt MOD 3–6KTL3-X · 16-pin", "description": "Models: MOD 3000TL3-X, MOD 4000TL3-X, MOD 5000TL3-X, MOD 6000TL3-X."}, {"videoId": "yhzpRgt-86Y", "title": "Growatt MOD 7–15KTL3-X · 16-pin", "description": "Models: MOD 7000TL3-X, MOD 8000TL3-X, MOD 9000TL3-X, MOD 10KTL3-X, MOD 11KTL3-X, MOD 12KTL3-X, MOD 13KTL3-X, MOD 15KTL3-X."}]
    }
  ]}
  showManual={true}
  showModbusTcp={true}
  showRs485={true}
  showCurtailment={true} showReactivePower={true}
/>

## Wiring

### RS485 - MOD 3-10K-TL3-XH

<RS485ConnectionTable firstColumn={["RS485 A1", "RS485 B1", "N/A"]} />
<ClickableImage src="/img/customers/growatt/GrowattMOD-3-10K-TL3-XH.png" alt="Image" maxWidth="450px" />

### RS485 - MOD 3-15K-TL3-X

<RS485ConnectionTable firstColumn={["RS485 A1", "RS485 B1", "N/A"]} />
<ClickableImage src="/img/customers/growatt/GrowattMOD-3-15K-TL3-X.png" alt="Image" maxWidth="450px" />

<RS485AddressNote />

# Growatt SPA Series


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/customers/growatt/logo.png"
    alt="logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

## Supported Devices

<DeviceSupportTable
  devices={[
    { 
        type: 'SPA 1000-3000TL BL', 
        manual: 'https://en.growatt.com/upload/file/20220817/8c5728bb0c61ef63859f60bf54f0379f.pdf', 
        modbusTcp: '', 
        rs485: '✅',
        curtailment: "❌"
        },
        { 
        type: 'SPA 4000-10000TL3 BH-UP', 
        manual: 'https://fr.growatt.com/upload/file/20220817/56597fbaab90b8c403dbcf1e47bde775.pdf', 
        modbusTcp: '❌', 
        rs485: '✅',
        curtailment: "❌",
      instructionVideos: [{"videoId": "kUAeVlZeuGU", "title": "Growatt SPH / SPA 4–10KTL3 BH-UP", "description": "Models: SPH 4000TL3 BH-UP, SPH 5000TL3 BH-UP, SPH 6000TL3 BH-UP, SPH 7000TL3 BH-UP, SPH 8000TL3 BH-UP, SPH 10000TL3 BH-UP, SPA 4000TL3 BH-UP, SPA 5000TL3 BH-UP, SPA 6000TL3 BH-UP, SPA 7000TL3 BH-UP, SPA 8000TL3 BH-UP, SPA 10000TL3 BH-UP."}]
    }
  ]}
  showManual={true}
  showModbusTcp={true}
  showRs485={true}
  showCurtailment={true} showReactivePower={true}
/>

## Wiring

### RS485

<RS485ConnectionTable firstColumn={["RS485 A", "RS485 B", "GND"]} />
<ClickableImage src="/img/customers/growatt/GrowattSPH-3000-6000TL.png" alt="Image" maxWidth="450px" />
<RS485AddressNote />


# Growatt SPH Series


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/customers/growatt/logo.png"
    alt="logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

## Supported Devices

> [!WARNING]
>       Not all batteries are compatible with Growatt’s control systems. Before installation, confirm that your specific battery model is on the official Growatt compatibility list and that the inverter firmware supports the battery's communication requirements.

<DeviceSupportTable
  devices={[
    { 
        type: 'SPH 3000-6000TL BL-UP',
        manual: 'https://en.growatt.com/upload/file/20220817/89ff7c3b556eceec1cc400136b5b4884.pdf',
        modbusTcp: '❌',
        rs485: '✅',
        curtailment: "✅"
        },
        {
        type: 'SPH 4000-10000TL3 BH-UP',
        manual: 'https://en.growatt.com/upload/file/20220817/53cb095cf6f3ed622c14c484b3d5650d.pdf',
        modbusTcp: '❌',
        rs485: '✅',
        curtailment: "✅",
      instructionVideos: [{"videoId": "kUAeVlZeuGU", "title": "Growatt SPH / SPA 4–10KTL3 BH-UP", "description": "Models: SPH 4000TL3 BH-UP, SPH 5000TL3 BH-UP, SPH 6000TL3 BH-UP, SPH 7000TL3 BH-UP, SPH 8000TL3 BH-UP, SPH 10000TL3 BH-UP, SPA 4000TL3 BH-UP, SPA 5000TL3 BH-UP, SPA 6000TL3 BH-UP, SPA 7000TL3 BH-UP, SPA 8000TL3 BH-UP, SPA 10000TL3 BH-UP."}]
    }
  ]}
  showManual={true}
  showModbusTcp={true}
  showRs485={true}
  showCurtailment={true} showReactivePower={true}
/>

## Wiring

### RS485

<RS485ConnectionTable firstColumn={["RS485 A", "RS485 B", "GND"]} />
<ClickableImage src="/img/customers/growatt/GrowattSPH-3000-6000TL.png" alt="Image" maxWidth="450px" />
<RS485AddressNote />

# Growatt UE Series


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/customers/growatt/logo.png"
    alt="logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

## Supported Devices

<DeviceSupportTable
  devices={[
    {
      type: "4000-6000 UE",
      manual: "https://midsummerwholesale.co.uk/pdfs/growatt-4000-5000-6000-manual.pdf",
      modbusTcp: "✅",
      rs485: "✅",
      curtailment: "❌"
    },
    {
      type: "10000-20000 UE",
      manual: "https://storage.ua.prom.st/924399_growatt_12000_ue_manual.pdf",
      modbusTcp: "✅",
      rs485: "✅",
      curtailment: "❌"
    }
  ]}
  showManual={true}
  showModbusTcp={true}
  showRs485={true}
  showCurtailment={true} showReactivePower={true}
/>

> [!NOTE]
> The **UE Series** supports both RS485 (Serial) and Modbus TCP (via Ethernet dongle). Ensure you select the correct connection mode in the controller.

## Wiring

### RS485 (10000 - 20000 UE)
The 10000-20000 UE series uses a specialized **circular waterproof connector** for RS485 communication. You must disassemble this connector to wire it.

**Pin Definition:**
Inside the circular connector, the pins are numbered 1 and 2.

<RS485ConnectionTable firstColumn={["Pin 1 (RS485 A)", "Pin 2 (RS485 B)", "N/A"]} />

*Note: Consult the manual if your model uses a different connector type.*

### RS485 (4000 - 6000 UE)
For the smaller UE models, the connection is typically via the terminal block or DB9 port. Please verify with the specific manual linked above.

## Configuration
<RS485AddressNote />

To change the Modbus address on the Growatt UE LCD display:

1. Double tap the front button/screen to enter the menu.
2. Navigate to **Settings** -> **Set COM Address**.
3. Select **Set Manual**.
4. Single tap to increment the number.
5. Double tap to confirm ("Set Addr OK!").


# Growatt WIT Series


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/customers/growatt/logo.png"
    alt="logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

## Supported Devices


<DeviceSupportTable
  devices={[
    { 
        type: "WIT 100K-TL3-H",
        manual: "https://en.growatt.com/upload/file/WIT_50-100KTL3_L_User_Manual_EN202503.pdf",
        modbusTcp: "✅",
        rs485: "✅",
        curtailment: "✅"
    },
    { 
        type: "WIT 15K-HU",
        modbusTcp: "✅",
        rs485: "✅",
        curtailment: "✅"
    },
  ]}
  showManual={true}
  showModbusTcp={true}
  showRs485={true}
  showCurtailment={true} showReactivePower={true}
/>

## Wiring

### RS485 - MID 100K-TL3-H

<RS485ConnectionTable firstColumn={["RS485 A1", "RS485 B1", "N/A"]} />
<ClickableImage src="/img/customers/growatt/GrowattWIT-100K-TL3-H.png" alt="Image" maxWidth="450px" />

# Hite


import { BrandName, ControllerName } from '@site/src/components/customFields';
import ClickableImage from '@site/src/components/ClickableImage';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/customers/hite/Logo_Hite Smart Energy.png"
    alt="logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

## Supported Devices 

<DeviceSupportTable
  devices={[
    {
        type: "BESS",
        variants: "BCCU",
        modbusTcp: "✅",
        rs485: "❌",
        curtailment: "✅"
    },
    {
        type: "BESS",
        variants: "ESMU",
        modbusTcp: "✅",
        rs485: "❌",
        curtailment: "✅"
    },
    {
        type: "BCCU",
        variants: "standalone",
        modbusTcp: "✅",
        rs485: "❌",
        curtailment: "✅"
    },
  ]}
  showVariants={true}
  showModbusTcp={true}
  showRs485={true}
  curtailment={true}
  showReactivePower={true}
/>

## Wiring

### TCP
For correct ethernet wiring: Follow the [the guidelines for ethernet wiring](/Controller/wiring-best-practices/#ethernet).

## Configuration
Please consult the manual of the device to enable Modbus TCP.


# Hithium


import { BrandName, ControllerName } from '@site/src/components/customFields';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/customers/hithium/Logo_Hithium.png"
    alt="logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>


## Supported Devices

<DeviceSupportTable
  devices={[
    {
      type: "Hithium battery cabinets",
      variants: "HCL-DC261kWh-0.5P / HCL-125kW/261kWh-400",
      modbusTcp: '✅',
      rs485: '❌',
    },
  ]}
  showVariants={true}
  showModbusTcp ={true}
  showRs485 ={true}
  showReactivePower={true}
/>


## Wiring

### Ethernet
For correct ethernet wiring: Follow the [the guidelines for ethernet wiring](/Controller/wiring-best-practices/#ethernet).


# Hoymiles


import { BrandName, ControllerName } from '@site/src/components/customFields';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';


<img
    src="/img/sgo/Logo_Hoymiles.png"
    alt="Logo hoymiles"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

# Hoymiles

The <BrandName /> <ControllerName /> integrates with two Hoymiles product families: the **DTU-Pro / Pro-S**
microinverter gateway and the **HoyUltra** energy storage systems (ESS).

## Supported Devices

<DeviceSupportTable
  devices={[
    {
      type: "DTU-Pro",
      modbusTcp: "✅",
      rs485: "✅",
      curtailment: "✅"
    },
    {
      type: "DTU-Pro-S",
      modbusTcp: "✅",
      rs485: "✅",
      curtailment: "✅"
    },
    {
      type: "HoyUltra (Protocol 215)",
      modbusTcp: "✅",
      rs485: "❌",
      curtailment: "✅"
    },
    {
      type: "HoyUltra (Protocol 261)",
      modbusTcp: "✅",
      rs485: "❌",
      curtailment: "✅"
    }
  ]}
  showModbusTcp
  showRs485
  showCurtailment
  showReactivePower={true}
/>


## DTU-Pro / Pro-S (Microinverters)

The DTU-Pro/Pro-S is a gateway that collects production data from the connected microinverters and forwards
power-limit commands to all of them. Each microinverter port is read individually (voltage, current, power,
energy and temperature), while curtailment is applied to the system as a whole.

> [!NOTE]
> Curtailment is applied as a single active-power limit (in %) to **all** microinverters connected to the
> DTU simultaneously. Individual microinverters cannot be curtailed separately. The limit is clamped to a
> minimum of 2% for third-generation inverters; a setpoint of 0% switches all microinverters off.

### Ethernet Connection (Modbus TCP)
Make sure that the <ControllerName /> and the DTU are connected to the same network, and that the DTU has
Modbus TCP enabled (default port `502`).
For correct ethernet wiring, follow the [guidelines for ethernet wiring](/Controller/wiring-best-practices/#ethernet).

### RS485 Connection
For RS485 wiring, follow the [guidelines for RS485 wiring](/Controller/wiring-best-practices/#rs485).
Use the following serial settings:

| Setting   | Value |
| --------- | ----- |
| Baud rate | 9600  |
| Data bits | 8     |
| Parity    | None  |
| Stop bits | 1     |

## HoyUltra (Energy Storage)

The HoyUltra ESS consists of a Power Conversion System (PCS/EMS) and one or more battery units. The
<ControllerName /> reads system- and unit-level state of charge, state of health, power and energy, and
controls the system through an active-power setpoint.

### Ethernet Connection (Modbus TCP)
HoyUltra systems are controlled exclusively over Modbus TCP (default port `502`). Make sure the
<ControllerName /> and the HoyUltra EMS are on the same network.
For correct ethernet wiring, follow the [guidelines for ethernet wiring](/Controller/wiring-best-practices/#ethernet).

> [!IMPORTANT]
> Before commissioning, you **must contact Hoymiles ([support@hoymiles.com](mailto:support@hoymiles.com))
> to set the EMS Modbus communication timeout to 30 seconds.** If this timeout is not configured correctly,
> the EMS will repeatedly drop the connection and the <ControllerName /> will report communication errors and
> lose control of the system.


# Huawei


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/customers/huawei/logo.png"
    alt="logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

# Huawei

The <BrandName /> <ControllerName /> supports Huawei **SUN2000** inverters, **LUNA 2000**
batteries and the **SmartLogger 3000**. The controller auto-detects whether a SmartLogger is
present, so in most cases it just works. The installer should prepare the Huawei
side and then run the search wizard on the SmartLogger IP address. If no Smartlogger is placed,
run the wizard on each inverter's IP address.

This guide walks you through it:

1. [Identify your setup](#1-identify-your-setup) — SmartLogger or direct
2. [Wiring](#2-wiring)
3. [Configure the Huawei equipment](#3-configure-the-huawei-equipment)
4. [Add the system in the controller](#4-add-the-system-in-the-controller)

## Supported devices

<DeviceSupportTable
  devices={[
    {
        type: 'Huawei SmartLogger 3000',
        modbusTcp: '✅',
        rs485: '❌',
        curtailment: '✅'
    },
    {
        type: 'Huawei SUN2000 Series inverters',
        modbusTcp: '✅',
        rs485: '✅',
        curtailment: '✅',
      instructionVideos: [{"videoId": "kEU7_xwtIz4", "title": "Huawei SUN2000 L1 — round COM8 connector"}, {"videoId": "gdwclh-NuiA", "title": "Huawei SUN2000 M0 / M1 — COM16 connector"}, {"videoId": "Rlf4A0sRPTE", "title": "Huawei SUN2000 LB0 — COM10 connector"}, {"videoId": "3ApdZfWO22I", "title": "Huawei SUN2000 LC0 — COM10 connector"}, {"videoId": "1wiobM-j5_Q", "title": "Huawei SUN2000 MAP0 — COM18 connector"}, {"videoId": "z7HGrGkeJew", "title": "Huawei SUN2000 MB0 — COM16 connector"}, {"videoId": "Yo2qc3Sxp9I", "title": "Huawei SUN2000-12–20KTL-M0 — COM16 connector"}, {"videoId": "jtgPsOOVp4U", "title": "Huawei SUN2000-8–20KTL-M2 — COM16 connector"}, {"videoId": "kyGUh1F5dWg", "title": "Huawei SUN2000 M3 — passively cooled enclosure with COM16 connector"}, {"videoId": "lRT7xlP0CWg", "title": "Huawei SUN2000-50/60/65KTL-M0 — double vertical terminal block"}, {"videoId": "llTf11keWEU", "title": "Huawei SUN2000-55/60KTL HV-D1 — horizontal RS485 terminal block"}, {"videoId": "NIEbcUQ_uJI", "title": "Huawei SUN2000-50KTL / 50KTL-C1 — horizontal RS485 terminal block"}, {"videoId": "7i0Tud3vJ8E", "title": "Huawei SUN2000-29.9 / 33-A / 36 / 42KTL — service terminal block"}, {"videoId": "7nlU5KB8fQA", "title": "Huawei SUN2000-30KTL-A / 33 / 33-E001 / 40KTL — service terminal block"}, {"videoId": "OMzVTxi5MCQ", "title": "Huawei SUN2000-8–28KTL — waterproof RS485 RJ45 connector"}, {"videoId": "JCDcjsJcMfw", "title": "Huawei SUN2000-50KTL-M3 — fan-cooled enclosure with COM16 connector"}, {"videoId": "1tsAyxrV8TE", "title": "Huawei SUN2000-70/75KTL-C1 — single vertical terminal block"}, {"videoId": "XTeN0Uu41Q8", "title": "Huawei SUN2000-50/63KTL-JPM — single vertical terminal block"}, {"videoId": "MSvzj37vXMY", "title": "Huawei SUN2000-90/95/100/105KTL-H — vertical RS485 terminal block"}, {"videoId": "N7-0Zxje20Q", "title": "Huawei SUN2000-63KTL-JPH0 — vertical RS485 terminal block"}, {"videoId": "anhaTyiLeyU", "title": "Huawei SUN2000-100KTL-USH0 — vertical RS485 terminal block"}, {"videoId": "m62WY0nQgw8", "title": "Huawei SUN2000-100/110/125KTL-M — external round COM connector"}, {"videoId": "Q2OiPCMjpKs", "title": "Huawei SUN2000-175/185KTL — external round COM connector"}, {"videoId": "Y8v2DhF6wtE", "title": "Huawei SUN2000-196/200/215KTL — external round COM connector"}, {"videoId": "2KttxOVkSjY", "title": "Huawei SUN2000-50KTL-M0 India / 70KTL-INM0 — single vertical terminal block"}, {"videoId": "71MxQHHfzxE", "title": "Huawei SUN2000-125KTL-JPH0 — external round COM connector"}, {"videoId": "4WUexJD8rhY", "title": "Huawei SUN2000-196KTL-H3 — external round COM connector"}]
    },
    {
        type: 'Huawei LUNA 2000 battery',
        modbusTcp: '✅',
        rs485: '✅',
        curtailment: '—'
    }
  ]}
  showModbusTcp={true}
  showRs485={true}
  showCurtailment={true} showReactivePower={true}
/>

The **SmartLogger 1000a** is on the roadmap but not yet supported. Practically all SUN2000
inverters with a communication interface are supported (including the SUN2000L residential
range) — not every interface is present on every inverter, so check yours.

<details>
  <summary style={{ cursor: 'pointer', fontWeight: 'bold' }}>Show all supported SUN2000 models</summary>
  <ul style={{ columns: 3, fontSize: '0.85rem', marginTop: '1rem' }}>
    <li>SUN2000-100KTL-H0</li>
    <li>SUN2000-100KTL-H1</li>
    <li>SUN2000-100KTL-H2</li>
    <li>SUN2000-100KTL-INM0</li>
    <li>SUN2000-100KTL-M0</li>
    <li>SUN2000-100KTL-M1</li>
    <li>SUN2000-100KTL-USH0</li>
    <li>SUN2000-105KTL-H1</li>
    <li>SUN2000-10KTL</li>
    <li>SUN2000-10KTL-M0</li>
    <li>SUN2000-10KTL-M1</li>
    <li>SUN2000-10KTL-M2</li>
    <li>SUN2000-10KTL-USL0</li>
    <li>SUN2000-11.4KTL-USL0</li>
    <li>SUN2000-110KTL-M0</li>
    <li>SUN2000-125KTL-JPH0</li>
    <li>SUN2000-125KTL-M0</li>
    <li>SUN2000-12KTL</li>
    <li>SUN2000-12KTL-M0</li>
    <li>SUN2000-12KTL-M1</li>
    <li>SUN2000-12KTL-M2</li>
    <li>SUN2000-15KTL</li>
    <li>SUN2000-15KTL-M0</li>
    <li>SUN2000-15KTL-M2</li>
    <li>SUN2000-15KTL-M3</li>
    <li>SUN2000-168KTL-H1</li>
    <li>SUN2000-175KTL-H0</li>
    <li>SUN2000-17KTL</li>
    <li>SUN2000-17KTL-M0</li>
    <li>SUN2000-17KTL-M2</li>
    <li>SUN2000-17KTL-M3</li>
    <li>SUN2000-185KTL-H1</li>
    <li>SUN2000-185KTL-INH0</li>
    <li>SUN2000-193KTL-H0</li>
    <li>SUN2000-196KTL-H0</li>
    <li>SUN2000-196KTL-H1</li>
    <li>SUN2000-196KTL-H3</li>
    <li>SUN2000-200KTL-H2</li>
    <li>SUN2000-20KTL</li>
    <li>SUN2000-20KTL-M0</li>
    <li>SUN2000-20KTL-M2</li>
    <li>SUN2000-20KTL-M3</li>
    <li>SUN2000-215KTL-H0</li>
    <li>SUN2000-22KTL-US</li>
    <li>SUN2000-23KTL</li>
    <li>SUN2000-23KTL-M3</li>
    <li>SUN2000-24.5KTL</li>
    <li>SUN2000-24.5KTL-M3</li>
    <li>SUN2000-24.7KTL-JP</li>
    <li>SUN2000-25KTL-NAM3</li>
    <li>SUN2000-25KTL-US</li>
    <li>SUN2000-28KTL</li>
    <li>SUN2000-28KTL-M3</li>
    <li>SUN2000-29.9KTL</li>
    <li>SUN2000-29.9KTL-M3</li>
    <li>SUN2000-2KTL-L0</li>
    <li>SUN2000-2KTL-L1</li>
    <li>SUN2000-3.68KTL-L10</li>
    <li>SUN2000-3.8KTL-USL0</li>
    <li>SUN2000-30KTL-A</li>
    <li>SUN2000-30KTL-M3</li>
    <li>SUN2000-30KTL-NAM3</li>
    <li>SUN2000-30KTL-US</li>
    <li>SUN2000-33KTL</li>
    <li>SUN2000-33KTL-A</li>
    <li>SUN2000-33KTL-E001</li>
    <li>SUN2000-33KTL-JP</li>
    <li>SUN2000-33KTL-NAM3</li>
    <li>SUN2000-33KTL-NHM3</li>
    <li>SUN2000-33KTL-US</li>
    <li>SUN2000-36KTL</li>
    <li>SUN2000-36KTL-M3</li>
    <li>SUN2000-36KTL-NAM3</li>
    <li>SUN2000-36KTL-US</li>
    <li>SUN2000-3KTL-CNL0</li>
    <li>SUN2000-3KTL-L0</li>
    <li>SUN2000-3KTL-L1</li>
    <li>SUN2000-3KTL-M0</li>
    <li>SUN2000-3KTL-M1</li>
    <li>SUN2000-4.6KTL-L1</li>
    <li>SUN2000-4.95KTL-JPL0</li>
    <li>SUN2000-4.95KTL-JPL1</li>
    <li>SUN2000-40KTL</li>
    <li>SUN2000-40KTL-JP</li>
    <li>SUN2000-40KTL-M3</li>
    <li>SUN2000-40KTL-NAM3</li>
    <li>SUN2000-40KTL-NHM3</li>
    <li>SUN2000-40KTL-US</li>
    <li>SUN2000-42KTL</li>
    <li>SUN2000-42KTL-M3</li>
    <li>SUN2000-43KTL-IN-C1</li>
    <li>SUN2000-43KTL-INM3</li>
    <li>SUN2000-44KTL-M3</li>
    <li>SUN2000-45KTL-US-HV-D0</li>
    <li>SUN2000-4KTL-CNL0</li>
    <li>SUN2000-4KTL-L0</li>
    <li>SUN2000-4KTL-L1</li>
    <li>SUN2000-4KTL-M0</li>
    <li>SUN2000-4KTL-M1</li>
    <li>SUN2000-50KTL</li>
    <li>SUN2000-50KTL-C1</li>
    <li>SUN2000-50KTL-JPM0</li>
    <li>SUN2000-50KTL-JPM1</li>
    <li>SUN2000-50KTL-M0</li>
    <li>SUN2000-50KTL-M3</li>
    <li>SUN2000-55KTL-HV-D1</li>
    <li>SUN2000-55KTL-HV-D1-001</li>
    <li>SUN2000-55KTL-IN-HV-D1</li>
    <li>SUN2000-5KTL-CNL0</li>
    <li>SUN2000-5KTL-L0</li>
    <li>SUN2000-5KTL-L1</li>
    <li>SUN2000-5KTL-M0</li>
    <li>SUN2000-5KTL-M1</li>
    <li>SUN2000-5KTL-USL0</li>
    <li>SUN2000-60KTL-HV-D1</li>
    <li>SUN2000-60KTL-HV-D1-001</li>
    <li>SUN2000-60KTL-M0</li>
    <li>SUN2000-63KTL-JPH0</li>
    <li>SUN2000-63KTL-JPM0</li>
    <li>SUN2000-65KTL-M0</li>
    <li>SUN2000-6KTL-CNL0</li>
    <li>SUN2000-6KTL-L1</li>
    <li>SUN2000-6KTL-M0</li>
    <li>SUN2000-6KTL-M1</li>
    <li>SUN2000-7.6KTL-USL0</li>
    <li>SUN2000-70KTL-C1</li>
    <li>SUN2000-70KTL-INM0</li>
    <li>SUN2000-75KTL-C1</li>
    <li>SUN2000-8KTL</li>
    <li>SUN2000-8KTL-M0</li>
    <li>SUN2000-8KTL-M1</li>
    <li>SUN2000-8KTL-M2</li>
    <li>SUN2000-90KTL-H0</li>
    <li>SUN2000-90KTL-H1</li>
    <li>SUN2000-90KTL-H2</li>
    <li>SUN2000-95KTL-INH0</li>
    <li>SUN2000-95KTL-INH1</li>
    <li>SUN2000-9KTL-USL0</li>
    <li>SUN2000L-2KTL</li>
    <li>SUN2000L-3.68KTL</li>
    <li>SUN2000L-3KTL</li>
    <li>SUN2000L-3KTL-CN</li>
    <li>SUN2000L-3KTL-CN-4G</li>
    <li>SUN2000L-4.125KTL-JP</li>
    <li>SUN2000L-4.6KTL</li>
    <li>SUN2000L-4.95KTL-JP</li>
    <li>SUN2000L-4KTL</li>
    <li>SUN2000L-4KTL-CN</li>
    <li>SUN2000L-4KTL-CN-4G</li>
    <li>SUN2000L-5KTL</li>
    <li>SUN2000L-5KTL-CN</li>
    <li>SUN2000L-5KTL-CN-4G</li>
    <li>SUN8000-500KTL</li>
  </ul>
</details>

## 1. Identify your setup

The controller scans for a SmartLogger when it connects and
adapts automatically. What you *do* need to know is **which IP address to run the search wizard
on**, because that differs per setup:

| If the site has… | Run the search wizard on… | The inverters are then… |
|:--|:--|:--|
| **A SmartLogger 3000** | the **SmartLogger's IP address** (one search) | automatically added via the SmartLogger; all curtailment and/or battery control goes through the SmartLogger. |
| **No SmartLogger** | **each inverter's IP address** (one search per inverter) | controlled **directly** |

> [!IMPORTANT]
> If the site has a SmartLogger, add the system **only on the SmartLogger's IP address**. The
> SmartLogger already exposes every inverter and meter connected to it, so they are all found in
> one go. **Do not add the inverters one by one on their individual IP addresses** — this is the
> most common setup mistake.

Routing all control through the SmartLogger (instead of the individual inverters) is intentional:
it prevents two systems from controlling the same inverters. **You still get the measurements of
every inverter individually** — "monitoring-only" means control is centralised through the
SmartLogger, not that any data is lost. This works over both Ethernet (Modbus-TCP) and RS485.

### SmartLogger with both a battery and solar inverters

> [!WARNING]
> If a battery **and** solar inverters are both connected to the SmartLogger for control, remove
> the solar inverters from the SmartLogger and add them directly to the <BrandName /> <ControllerName />.
> The SmartLogger can become unstable when it is commanded to control both the battery and the
> solar inverters.

On such a site, the SmartLogger controls only the battery:

1. Remove the solar inverters from the SmartLogger. Leave the battery, and the inverter it sits
   behind, on the SmartLogger.
2. Prepare each solar inverter for a direct connection, as described in
   [Without a SmartLogger](#without-a-smartlogger-direct-to-each-inverter).
3. Run the search wizard on the **SmartLogger's IP address** and choose **Only battery**.
4. Run the search wizard on **each solar inverter's IP address** and choose **Only solar**.

## 2. Wiring

**Ethernet** — follow the [guidelines for ethernet wiring](/Controller/wiring-best-practices/#ethernet).

<details>
  <summary style={{ cursor: 'pointer', fontWeight: 'bold' }}>RS485 wiring (only when using RS485 on SUN2000 / LUNA 2000!)</summary>
  <div style={{ marginTop: '1rem' }}>
    <RS485ConnectionTable firstColumn={["", "", ""]} />
  </div>
</details>

## 3. Configure the Huawei equipment

We recommend doing a **factory reset of the inverter** before adding it — this gives a clean
initial connection and avoids many issues. Then follow the section that matches your setup.

### With a SmartLogger 3000

<ClickableImage src="/img/customers/huawei/smartlogger3000.jpg" alt="Huawei SmartLogger 3000" maxWidth="250px" />

The SmartLogger reads and controls all of the energy meters, inverters and batteries connected
to it. Configure it in its web interface (browse to its IP address, default password "Changeme").

#### a. Enable Modbus
1. Change "Link setting" to **Enable (Unlimited)**.
2. Set "Address mode" to **Communication address**.
3. Choose the Modbus address of the logger — make it **different** from the inverter addresses (see the next step).
4. Click submit.

<ClickableImage src="/img/customers/huawei/smartlogger3000_config_pt1.png" alt="SmartLogger link settings" maxWidth="600px" />
<ClickableImage src="/img/customers/huawei/smartlogger3000_config_pt2.png" alt="SmartLogger Modbus settings" maxWidth="600px" />

#### b. Give every device a unique Modbus address
The SmartLogger connects inverters and meters across 3 COM ports. **Every Modbus address must be
unique.** It is easiest to first set non-overlapping address ranges per COM port, then re-add any
clashing devices with a free address.

<ClickableImage src="/img/customers/huawei/smartlogger3000_config_pt3.png" alt="Device Modbus addresses" maxWidth="600px" />
<ClickableImage src="/img/customers/huawei/smartlogger3000_config_pt4.png" alt="Address range per COM port" maxWidth="600px" />
<ClickableImage src="/img/customers/huawei/smartlogger3000_config_pt5.png" alt="Re-adding devices with unique addresses" maxWidth="600px" />

#### c. Enable remote communication scheduling
This is **required for curtailment / power limiting**. Without it the controller and SmartLogger
report no errors, but the inverters keep producing at full power.

Go to Settings > Power Adjustment > Active Power Control and configure exactly like in the screenshot.
- Active power control mode: Remote communication scheduling
- Schedule strategy: Strategy 1
- Adjustment coefficient: 1.000
- Time for communication exception detection: 300
- Automatic startup upon communication recovery: Enable

<ClickableImage src="/img/customers/huawei/smartlogger3000_remote_communication_schedule.png" alt="Enable Remote communication scheduling" maxWidth="700px" />

#### d. Enable remote power scheduling on every inverter
This is **required for curtailment / power limiting**. Without it the controller and SmartLogger
report no errors, but the inverters keep producing at full power. Do this for **every** inverter:

1. Select an inverter in the device tree on the left (e.g. `Inverter(COM2-11)`).
2. Go to **Monitoring → Running Param. → Power Adjustment**.
3. Set **Remote power schedule** to **Enable** and click **Submit**.
4. Repeat for every inverter in the tree (`COM2-11`, `COM2-12`, …).

<ClickableImage src="/img/customers/huawei/smartlogger3000_remote_power_schedule.png" alt="Enable Remote power schedule on each inverter" maxWidth="700px" />

### Without a SmartLogger (direct to each inverter)

Configure each inverter from the **FusionSolar app**.

#### a. Install the FusionSolar app

| Smartphone OS | Installation instructions |
|:--|:--|
| iOS | Search the App Store for FusionSolar and download the app. |
| Android | [Download the app here](https://intl.fusionsolar.huawei.com/fusionsolarapp). |
| Huawei Phone | Search FusionSolar in the Huawei App Gallery. |

#### b. Connect to the inverter
Make sure the AC or DC side of the inverter is powered, then connect your phone to it. Pick the
method that suits the inverter:

<ClickableImage src="/img/customers/huawei/sun2000_config_pt1.png" alt="Choose connection method" maxWidth="450px" />

- **WLAN** — plug the WLAN module into the USB port at the bottom of the inverter, enable WLAN/Bluetooth on your phone, and stay within 5 m.
- **Bluetooth** — open the app, tap connect, then scan the QR/bar code or select Bluetooth → "Search for Device". With USB Adapter2000-B the device name is "last 8 characters of the serial number + HWAPP".
- **USB** — connect the inverter's USB port to your phone (the screen shows 'Connected to USB Accessory'), open the app, tap connect, select USB and allow access.

#### c. Enable Modbus-TCP
1. On the home page, go to **Settings → Communication configuration**.
<ClickableImage src="/img/customers/huawei/sun2000_config_pt2.png" alt="Communication configuration" maxWidth="450px" />
2. Open **Dongle parameter settings**.
<ClickableImage src="/img/customers/huawei/sun2000_config_pt3.png" alt="Dongle parameter settings" maxWidth="450px" />
3. Select **Modbus-TCP** and set Connection to **Enable (unrestricted)**. If there is no Modbus-TCP option, [the inverter must be updated](https://support.huawei.com/enterprise/en/fusionsolar/sun2000l-pid-22027611?category=installation-upgrade).
<ClickableImage src="/img/customers/huawei/sun2000_config_pt4.png" alt="Enable Modbus-TCP" maxWidth="450px" />
4. Still in Dongle parameter settings, change the **starting address for automatic address allocation** to any other value — the connection only activates once this has changed. (This is not the Modbus address the controller talks to, just a starting value.)
<ClickableImage src="/img/customers/huawei/sun2000_config_pt6.png" alt="Change starting address" maxWidth="450px" />

#### d. Enable remote power control
Required for curtailment: on the home page go to **Power adjustment → Grid-tied point control →
Active power**, and set the Control mode to **Remote output control**.

<ClickableImage src="/img/customers/huawei/sun2000_config_pt5.png" alt="Active power remote output control" maxWidth="450px" />

### LUNA 2000 battery

<ClickableImage src="/img/customers/huawei/Luna.png" alt="Huawei LUNA 2000" maxWidth="250px" />

The LUNA 2000 needs no separate connection steps — it is read and controlled through the inverter
or SmartLogger it sits behind. Just choose **Both solar and battery** or **Only battery** in the
wizard (next step) so the controller adds it.

## 4. Add the system in the controller

Run the search wizard on the [correct IP address](#1-identify-your-setup) — the **SmartLogger's
IP** if there is one, otherwise **each inverter's IP**. During the wizard you choose whether an
**energy meter** is connected (so the controller can read grid data) and **what is connected to
the inverter** (solar, battery, or both). That's it — the controller discovers and adds the rest.

If a battery and solar inverters are both connected to the SmartLogger, follow
[SmartLogger with both a battery and solar inverters](#smartlogger-with-both-a-battery-and-solar-inverters)
instead.

## Advanced: curtailing a subset of inverters (bypass mode)

By default, when a SmartLogger is present, **all** curtailment goes through the SmartLogger's own
aggregate registers — the SmartLogger is the only system writing to the inverters, and the
controller sends it one fleet-wide power limit. This is the normal, recommended setup, and the
reason all control is routed through the SmartLogger in the first place (see
[step 1](#1-identify-your-setup)).

Some counterparties we integrate with (for example **Yuso Solar**) require the ability to curtail
or shut off a **subset** of inverters rather than the whole installation. The SmartLogger's
aggregate registers cannot do this — they only expose one plant-wide percentage/setpoint, with no
way to target or exclude individual inverters. For this specific requirement only, the SmartLogger
device has a manual action, **"Enable/Disable the smartlogger bypass"**, that writes curtailment
setpoints directly to each inverter's own register instead of through the SmartLogger. Once
enabled, every SUN2000 inverter behind the SmartLogger becomes independently controllable — you'll
find a separate manual test entry for each inverter instead of one for "PV of all SUN2000s
combined".

> [!WARNING]
> Only enable this if a subset of inverters genuinely needs to be curtailed independently. In every
> other case, leave it disabled and let the SmartLogger do the controlling.
>
> Enabling bypass mode on the controller is **not enough by itself**. As long as the SmartLogger's
> own active power control is still active, it keeps writing its own setpoint to every inverter on
> its own schedule too — with two systems writing to the same inverter, whichever writes most
> recently wins, causing brief production spikes. **Step b below (setting the SmartLogger's own
> Active power control mode to "No limit") is what stops the SmartLogger from doing this — both
> steps are required together, step a alone is not enough.**

**Do not continue with the steps below unless you can confirm all of the following:**
- You understand *why* bypass mode is needed for this specific installation (a counterparty
  requires curtailing/shutting off a subset of inverters — this is not a general-purpose
  curtailment mode, and enabling it "just in case" or to work around an unrelated issue is wrong).
- You will complete **both** steps below (a and b) — enabling bypass without also setting the
  SmartLogger to "No limit" causes the production spikes described above.
- You have explained this to the customer/installer responsible for the site.

If you cannot confirm all three, stop here and use the SmartLogger's normal aggregate control
instead.

### a. Enable bypass mode on the controller

1. On the SmartLogger's device row, click **Other actions**.

<ClickableImage src="/img/customers/huawei/smartgridone_bypass_step1_other_actions.jpg" alt="Open Other actions on the SmartLogger device row" maxWidth="700px" />

2. Select **"Enable/Disable the smartlogger bypass"** and click **Execute action**.

<ClickableImage src="/img/customers/huawei/smartgridone_bypass_step2_enable_toggle.jpg" alt="Select and execute the smartlogger bypass action" maxWidth="600px" />

3. Confirm it worked: open **Test / manual override** for the SmartLogger. You should now see one
   entry per SUN2000 inverter (each with its own maximum production power field), instead of a
   single "PV of all SUN2000s combined" entry.

<ClickableImage src="/img/customers/huawei/smartgridone_bypass_step3_per_inverter_test_forms.jpg" alt="Test / manual override now shows one form per SUN2000 inverter" maxWidth="700px" />

### b. Set the SmartLogger's own active power control to "No limit"

This step is required, not optional — see the warning above. It stops the SmartLogger from also
writing its own setpoint to the inverters, which is what causes the production spikes when only
step a has been done.

In the SmartLogger's own web interface (**Settings → Power Adjustment → Active Power Control**),
set **Active power control mode** to **No limit** and submit.

<ClickableImage src="/img/customers/huawei/smartlogger3000_bypass_step4_active_power_no_limit.jpg" alt="Set Active power control mode to No limit on the SmartLogger" maxWidth="700px" />

> [!IMPORTANT]
> Only change this SmartLogger setting when **all** of the following are true: you use a
> SmartLogger, you need inverter-individual curtailment, and you have already enabled the
> smartlogger bypass setting in the controller (step a above). Changing it in any other situation
> disables curtailment for this SmartLogger entirely.

## Troubleshooting

**Curtailment / power limiting has no effect.**
The inverters are almost certainly missing the remote-scheduling setting. Re-check that
**Remote power schedule** is enabled on *every* inverter (SmartLogger setup,
[step 3d](#d-enable-remote-power-scheduling-on-every-inverter)) — the controller will report no
error even when this is the cause.

**Devices won't connect, values can't be read, or the SmartLogger reports 0 power.**
First, update firmware. In **FusionSolar**, check for and install updates for **both** the Huawei
software (SmartLogger / dongle) **and** each inverter, keeping them on matching versions —
outdated or mismatched firmware is a common cause of missing registers, unreadable values and
ignored commands. If the SmartLogger still reports 0 power after enabling Modbus, contact Huawei.


# Hypontech


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';


<img
    src="/img/customers/Hypontech/logo.png"
    alt="logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

# Hypontech Inverters

## Supported Devices
<DeviceSupportTable
    devices={[
        {
            type: "PV Ongrid Inverter, 1-Phase",
            variants: "HPK 1000/1500/2000/2500/3000, HPS 3000D/3680D/4000D/5000D/6000D, HPS 3000P/3680P/4000P/5000P/6000P",
            rs485: "✅",
        },
        {
            type: "PV Ongrid Inverter, 3-Phase",
            variants: "HPT 3000P/4000P/5000P/6000P/8000P/10000P/12000P/15000P, HPT 15KP/20KP/25KP/30KP, HPT 15K/17K/20K/22K/25K, HPT 30K/33K/36K/40K/50K, HPT 60K/70K/80K",
            rs485: "✅",
        },
        {
            type: "Hybrid Inverter",
            variants: "HES 3000/3680/4000/5000/6000, HHS 3000/3680/4000/5000/6000, HHT 5000/6000/8000/10000/12000/15000",
            rs485: "✅",
        },
    ]}
    showRs485={ true }
    showVariants={ true }
  showReactivePower={true}
/>

> [!NOTE]
> This integration has not been tested with all the devices listed above, however, since they all use the same communication protocol, they should work without issues.

## Wiring
The <BrandName /> <ControllerName /> and the Hypontech inverters communicate via RS485.

### RS485
<RS485ConnectionTable firstColumn={["RS485A (Pin 3)", "RS485B (Pin 4)", "N/A"]} />

<ClickableImage src="/img/customers/Hypontech/HYTH_wiring.png" alt="Hypontech Wiring" maxWidth="350px" />

<RS485AddressNote />



# All In One ESS


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src='/img/customers/HYXiPOWER/Logo_HYXiPOWER.png'
    alt='logo'
    style={{ display: 'block', margin: '0 auto', width: '40%'}}
/>

## Supported Devices

<DeviceSupportTable
  devices={[
    { 
      type: 'All In One ESS',
      variants: 'HYX-H6K-HTA', 
      manual: 'https://webfile.hyxipower.com/soft/20250527/UM_HYX-H(6-15)K-HTA_User-manual_V1.8-2025_EU.pdf', 
      modbusTcp: '❌', 
      rs485: '✅',
      curtailment: '✅'
    }, { 
      type: 'All In One ESS',
      variants: 'HYX-H9K-HTA', 
      manual: 'https://webfile.hyxipower.com/soft/20250527/UM_HYX-H(6-15)K-HTA_User-manual_V1.8-2025_EU.pdf', 
      modbusTcp: '❌', 
      rs485: '✅',
      curtailment: '✅'
    }, { 
      type: 'All In One ESS',
      variants: 'HYX-H12K-HTA', 
      manual: 'https://webfile.hyxipower.com/soft/20250527/UM_HYX-H(6-15)K-HTA_User-manual_V1.8-2025_EU.pdf', 
      modbusTcp: '❌', 
      rs485: '✅',
      curtailment: '✅'
    }, { 
      type: 'All In One ESS',
      variants: 'HYX-H15K-HTA', 
      manual: 'https://webfile.hyxipower.com/soft/20250527/UM_HYX-H(6-15)K-HTA_User-manual_V1.8-2025_EU.pdf', 
      modbusTcp: '❌', 
      rs485: '✅',
      curtailment: '✅'
    }
  ]}
  showManual={true}
  showModbusTcp={true}
  showRs485={true}
  showCurtailment={true} showReactivePower={true}
  showVariants={true}
/>

## Wiring

### RS485
For RS485 Wiring, use the COM port (N° 5) on the inverter.

<RS485ConnectionTable firstColumn={["RS485 A (Pin 5)", "RS485 B (Pin 6)", "N/A"]} />
<RS485AddressNote />


# Hybrid Inverters


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src='/img/customers/HYXiPOWER/Logo_HYXiPOWER.png'
    alt='logo'
    style={{ display: 'block', margin: '0 auto', width: '40%'}}
/>

## Supported Devices

<DeviceSupportTable
  devices={[
    { 
      type: 'Hybrid inverter Inverter',
      variants: 'HYX-H5K-HT', 
      manual: 'https://webfile.hyxipower.com/soft/20240717/UM_HYX-H12K-HT_V1.2-202407_EU.PDF', 
      modbusTcp: '❌', 
      rs485: '✅',
      curtailment: '✅'
    }, { 
      type: 'Hybrid inverter Inverter',
      variants: 'HYX-H6K-HT', 
      manual: 'https://webfile.hyxipower.com/soft/20240717/UM_HYX-H12K-HT_V1.2-202407_EU.PDF', 
      modbusTcp: '❌', 
      rs485: '✅',
      curtailment: '✅'
    }, { 
      type: 'Hybrid inverter Inverter',
      variants: 'HYX-H8K-HT', 
      manual: 'https://webfile.hyxipower.com/soft/20240717/UM_HYX-H12K-HT_V1.2-202407_EU.PDF', 
      modbusTcp: '❌', 
      rs485: '✅',
      curtailment: '✅'
    }, { 
      type: 'Hybrid inverter Inverter',
      variants: 'HYX-H10K-HT', 
      manual: 'https://webfile.hyxipower.com/soft/20240717/UM_HYX-H12K-HT_V1.2-202407_EU.PDF', 
      modbusTcp: '❌', 
      rs485: '✅',
      curtailment: '✅'
    }, { 
      type: 'Hybrid inverter Inverter',
      variants: 'HYX-H12K-HT', 
      manual: 'https://webfile.hyxipower.com/soft/20240717/UM_HYX-H12K-HT_V1.2-202407_EU.PDF', 
      modbusTcp: '❌', 
      rs485: '✅',
      curtailment: '✅'
    }, { 
      type: 'Hybrid inverter Inverter',
      variants: 'HYX-H15K-HT', 
      manual: 'https://webfile.hyxipower.com/soft/20250603/UM_HYX-H(15-25)K-HT_User-Manual_V1.0-2025_EN.pdf', 
      modbusTcp: '❌', 
      rs485: '✅',
      curtailment: '✅'
    }, { 
      type: 'Hybrid inverter Inverter',
      variants: 'HYX-H20K-HT', 
      manual: 'https://webfile.hyxipower.com/soft/20250603/UM_HYX-H(15-25)K-HT_User-Manual_V1.0-2025_EN.pdf', 
      modbusTcp: '❌', 
      rs485: '✅',
      curtailment: '✅'
    }, { 
      type: 'Hybrid inverter Inverter',
      variants: 'HYX-H25K-HT', 
      manual: 'https://webfile.hyxipower.com/soft/20250603/UM_HYX-H(15-25)K-HT_User-Manual_V1.0-2025_EN.pdf', 
      modbusTcp: '❌', 
      rs485: '✅',
      curtailment: '✅'
    }
  ]}
  showManual={true}
  showModbusTcp={true}
  showRs485={true}
  showCurtailment={true} showReactivePower={true}
  showVariants={true}
/>

## Wiring

### RS485
For RS485 Wiring, use the Reserved Communication port (N° 14) on the inverter.

<RS485ConnectionTable firstColumn={["RS485 A (Pin 5)", "RS485 B (Pin 6)", "N/A"]} />
<RS485AddressNote />


# Hyxipower


import { FolderOverview } from '@/components/FolderOverview';

# Hyxipower

<FolderOverview folder="Controller/Devices/PV-hybrid-and-battery-inverters/HYXiPOWER" />


# Pv Hybrid And Battery Inverters


import { FolderOverview } from '@/components/FolderOverview';

# Pv Hybrid And Battery Inverters

<FolderOverview folder="Controller/Devices/PV-hybrid-and-battery-inverters" />


# iWell


import { BrandName, ControllerName } from '@site/src/components/customFields';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';

<img
  src="/img/customers/iwell/iwell-logo.png"
  alt="iWell"
  style={{ display: "block", margin: "0 auto", width: "35%"}}
/>

# iWell Cube Battery 

## Supported Devices

<DeviceSupportTable
  devices={[
    {
      type: "iWell Cube Battery (Experimental)",
      variants: "Cube Series",
      modbusTcp: "✅",
      rs485: "❌",
      curtailment: "✅",
    }
  ]}
  showVariants={true}
  showModbusTcp={true}
  showRs485={true}
  showCurtailment={true} showReactivePower={true}
/>

<ClickableImage src="/img/customers/iwell/iwell-cube-battery.png" alt="iWell Cube Battery" maxWidth="400px" />

---

## Wiring

The <BrandName /> <ControllerName /> communicates with the iWell Cube battery system using **Modbus TCP (Ethernet)**.  
Connect the Ethernet (LAN) port of the battery system to the same network as the <BrandName /> <ControllerName />.

<RS485ConnectionTable firstColumn={["Ethernet (TCP/IP) Port", "Port Number", "Connection Type"]} secondColumn={["LAN", "1025", "Modbus TCP"]} />

> [!TIP]
> Ensure both the <BrandName /> <ControllerName /> and the iWell Cube battery are in the **same IP subnet**  
> (e.g. 192.168.1.xxx) and can communicate over port **1025**.

> [!WARNING]
> The iWell Cube Modbus TCP interface is active only when the battery system is powered on and initialized.  
> Do **not** connect to inactive units or during firmware updates.

---



# Jinko


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';


<img
    src="/img/customers/jinko/Logo_Jinko.png"
    alt="logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

## Supported Devices

<DeviceSupportTable
  devices={[
    {
        type: "SunGiga",
        modbusTcp: "✅",
        rs485: "❌",
        curtailment: "❌"
    }
  ]}

  showModbusTcp={true}
  showRs485={true}
  showCurtailment={true} showReactivePower={true}
/>

## Configuration

### 1: Connecting the LAN (Ethernet) to the Inverter

    **1a**. Connect the **LAN (Ethernet cable)** to the **RJ45 port** on the Jinko SunGiga.

### 2: Jinko SunGiga Configuration
| Steps |
|------|
| **2a**. Open the Jinko SunGiga web interface by entering the IP address of the system in a web browser. |
| **2b**. Make sure **High priority local control** and **Enable total active power setting** are configured as **Close**: <img src="/img/customers/jinko/JinkoInstruction1.png" alt="Image" maxWidth="100%"/> |
| **2c**. Make sure **Remote/Local** is configured as **Remote**: <img src="/img/customers/jinko/JinkoInstruction2.png" alt="Image" maxWidth="100%"/> |

# Kaco


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/customers/kaco/kaco_logo.svg"
    alt="logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

# KACO Inverters

## Supported Devices

<DeviceSupportTable
  devices={[
    { type: 'blueplanet TL3', variants: '50.0 / 60.0', modbusTcp: '✅', rs485: '❌', curtailment: "✅" },
    { type: 'blueplanet TL3', variants: '87.0 / 92.0 / 105.0', modbusTcp: '✅', rs485: '❌', curtailment: "🔶 (specific software required)" }
  ]}
  showVariants={true}
  showModbusTcp={true}
  showRs485={true}
  showCurtailment={true} showReactivePower={true}
/>

> [!WARNING]
> Curtailment of the blueplanet TL3 87.0 / 92.0 / 105.0 inverters is only possible with software version V03-59-REL-03aaf518 or newer.
> You can check the software version of the inverter under the "info" tab.
>
> <ClickableImage src="/media/kaco/KACO_interface_software_version.png" alt="KACO software version" maxWidth="600px" />

## Wiring

The <BrandName /> <ControllerName /> and the Kaco inverters communicate via Ethernet.

### Ethernet
For correct ethernet wiring: Follow the [the guidelines for ethernet wiring](/Controller/wiring-best-practices/#ethernet).


## Configuration
### blueplanet 50.0 / 60.0 TL3

Modbus Write access must be enabled in the settings of the inverter:
    1. Log in to the interface of the inverter on the local Network 
    <ClickableImage src="/media/kaco/KACO_interface1_login.png" alt="KACO blueplanet 50.0/60.0 Interface login" maxWidth="500px" />
    2. Go to Interfaces and Network Services 
    <ClickableImage src="/media/kaco/KACO_interface1_menu.png" alt="KACO blueplanet 50.0/60.0 Interface menu" maxWidth="350px" />
    3. Enable the "Modbus TCP Write access" setting
    <ClickableImage src="/media/kaco/KACO_interface1_setting.png" alt="KACO blueplanet 50.0/60.0 Interface setting" maxWidth="500px" />

### blueplanet 92.0 / 105.0 TL3

Modbus Write access must be enabled in the settings of the inverter:
    1. Log in to the interface of the inverter on the local Network 
    2. Go to Interfaces and then Network Services 
    3. Enable both the "Modbus TCP/UDP Read access" and "Modbus TCP/UDP Write access" settings
    <ClickableImage src="/media/kaco/KACO_interface2.png" alt="KACO blueplanet 92.0 / 105.0 Interface setting" maxWidth="600px" />



# Kehua


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import ClickableImage from '@site/src/components/ClickableImage';

<img
    src="/img/customers/kehua/logo.png"
    alt="Logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

# Kehua

## Supported Devices

<DeviceSupportTable
  devices={[
    {
      type: 'BCS1725K-B-HUD',
      modbusTcp: '✅',
      rs485: '✅'
    },
    {
      type: 'NXPCS',
      modbusTcp: '✅',
      rs485: '✅'
    },
    {
      type: 'BCS200K-B-HM',
      modbusTcp: '✅',
      rs485: '✅'
    },
    {
      type: 'SPI three-phase string PV series (SPI8000/12K/23K/33K-B X2, SPI125K-B, SPI250K/320K-B-H)',
      modbusTcp: '❌',
      rs485: '✅'
    }
  ]}
  showModbusTcp={ true }
  showVariants={ false }
  showRs485={ true }
  showReactivePower={true}
/>


## Wiring
For correct ethernet wiring: Follow the [the guidelines for ethernet wiring](/Controller/wiring-best-practices/#ethernet).

# RS485

## PCS models (BCS1725K-B-HUD, NXPCS, BCS200K-B-HM)

To establish communication between the PCS and <ControllerName />, use the RS485 interface available on the external wiring terminal bar, as shown below. This terminal provides dedicated ports for RS485 communication, which is used for both PC and BMS connections.

<img
    src="/img/customers/kehua/Wiring_bar.png"
    alt="Wiring bar"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

<RS485ConnectionTable firstColumn={["RS485 A (Pin 5)", "RS485 B (Pin 6)", "N/A"]}/>

<img
    src="/img/customers/kehua/Wiring_details.png"
    alt="Wiring details"
    style={{ display: "block", margin: "0 auto", width: "80%"}}
/>

## SPI string PV inverters

The SPI string PV inverters use a different physical RS485 connection than the PCS models above. The serial settings are the same for all SPI models:

| Setting | Value |
| --- | --- |
| Protocol | Modbus RTU |
| Baud rate | 9600 (default), configurable to 2400 / 4800 / 19200 / 38400 / 115200 |
| Parity | None |
| Data bits | 8 |
| Stop bits | 1 |
| Modbus address | 1 - 247 |

### SPI-B X2 series (SPI8000-B-X2 up to SPI33K-B X2)

The **COM.** port (a waterproof RJ45 plug, ③ in the figure below) is the only wired RS485 interface on these models. It must be configured as RS485 communication port (not as DRM port). Pins 7 and 8 of the RJ45 plug are the RS485 A and B lines.

<img
    src="/img/customers/kehua/SPI_bottom_view.png"
    alt="Bottom view of the SPI inverter with the COM. port (item 3)"
    style={{ display: "block", margin: "0 auto", width: "60%"}}
/>

<img
    src="/img/customers/kehua/SPI_COM_RJ45_pins.png"
    alt="Pin definition of the RJ45 plug of the COM. port"
    style={{ display: "block", margin: "0 auto", width: "80%"}}
/>

<RS485ConnectionTable firstColumn={["RS485 A (RJ45 pin 7, white-brown)", "RS485 B (RJ45 pin 8, brown)", "N/A"]}/>

**Important — verify on site:** the Kehua user manuals label pins 7 and 8 as **METER:A** / **METER:B** and only describe them for the smart-meter (zero-export) function. Kehua's northbound Modbus protocol (V2.11) does list these models as supporting RS485 monitoring, and this RJ45 is the only wired RS485 interface they have, but Kehua's documentation does not explicitly confirm that monitoring uses these pins. Verify this connection on site or with Kehua support before relying on it. Also note that if the zero-export smart-meter function is in use, this port is occupied by the meter and cannot be used for monitoring at the same time.

The Modbus address and baud rate of these models are set with the Kehua monitoring software (default baud rate 9600). Multiple inverters can be daisy-chained on the same RS485 bus.

### Larger SPI models (SPI125K-B, SPI250K-B-H, SPI320K-B-H)

These models have a dedicated RS485 port on the communication board inside the wiring box; the Kehua user manual confirms this port "is mainly used for LAN monitoring, which can realize the background remote monitoring". Connect the RS485 wires to that port and route them separately from the AC and DC power wiring to avoid communication interference.

<RS485ConnectionTable firstColumn={["RS485 A", "RS485 B", "N/A"]}/>

- On the SPI 75K-150K models (e.g. SPI125K-B), the Modbus address is set in binary with the SW1 dial switch on the communication board (e.g. `000001` = address 1). The baud rate is set with the Kehua WiseEnergy software (default 9600).
- On the SPI-B-H models (SPI250K-B-H, SPI320K-B-H), the RS485 connection is located in the **COM.** wiring box, next to the (optional) Ethernet connection.


# Kostal


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';
import Details from '@theme/Details';

<img
    src="/img/sgo/Logo_Kostal.png"
    alt="Kostal Logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

# Kostal Inverters

## Supported Devices

The <BrandName /> <ControllerName /> supports Kostal Pico inverters that use the "Kostal Pico protocol". This includes many inverters from the PIKO series.

<DeviceSupportTable
  devices={[
    {
      type: "Kostal Pico Inverters",
      modbusTcp: "✅",
      rs485: "✅",
      curtailment: "❌"
    }
  ]}
  showVariants={false}
  showModbusTcp={true}
  showRs485={true}
  showCurtailment={true} showReactivePower={true}
/>

> [!NOTE] Curtailment
> While these inverters support active power control and feed-in limitation, the protocol driver used by the <BrandName /> <ControllerName /> does not currently support sending curtailment commands.

## Configuration

Kostal inverters can be connected to the <BrandName /> <ControllerName /> via Modbus TCP (Ethernet) or RS485.

### Modbus TCP (Ethernet)

1.  Connect the inverter to the same local network as the <BrandName /> <ControllerName /> using an Ethernet (RJ45) cable.
2.  The <BrandName /> <ControllerName /> communicates with the inverter on **TCP Port 81**.
3.  The inverters are typically configured for DHCP by default, meaning they will get an IP address automatically from your network router.
4.  You can access the inverter's built-in web server by typing its IP address into a web browser.

### RS485

<RS485AddressNote />

The default RS485 bus address is often **1**. If you have more than one inverter on the bus, you must assign a unique address to each one. This can typically be done via the inverter's display menu or web server.

#### Wiring

The physical RS485 connection varies by inverter model. Please consult your specific inverter's installation manual for the correct terminals and pinout.

* **Common Connection Types:** Inverters may have either **RJ45 sockets** (for easy daisy-chaining) or a **terminal block** for the RS485 connection.
* **Required Signals:** You will need to identify and connect the **Data A**, **Data B**, and **Ground (GND)** signals to the corresponding ports on the <BrandName /> <ControllerName />.

Connect the inverter's RS485 terminals to the <BrandName /> <ControllerName /> as follows:

<RS485ConnectionTable
  firstColumn={["Data A", "Data B", "Ground"]}
  />

# KSTAR C&I Hybrid Inverters


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/customers/kstar/logo.jpeg"
    alt="logo"
    style={{ display: "block", margin: "0 auto", width: "400px"}}
/>

# KSTAR C&I Hybrid Inverters


## Supported Devices

<DeviceSupportTable
  devices={[
    { type: 'BluePulse Hybrid Inverter', variants: 'KAC50DP-BC100DE', modbusTcp: '✅', rs485: '✅', curtailment: '✅', firmwareVersion: 'V000B060D000' },
    { type: 'BluePulse Hybrid Inverter', variants: 'KAC50DP-BC107DE / KAC50DP-BC107DE2', modbusTcp: '✅', rs485: '✅', curtailment: '✅', firmwareVersion: 'V000B060D000' },
    { type: 'BluePulse Hybrid Inverter', variants: 'KAC50DP-BC197DE / KAC50DP-BC197DE2', modbusTcp: '✅', rs485: '✅', curtailment: '✅', firmwareVersion: 'V000B060D000' },
  ]}
  showVariants={true}
  showModbusTcp={true}
  showRs485={true}
  showCurtailment={true} showReactivePower={true}
  showFirmwareVersion={true}
/>

<ClickableImage src="/img/customers/kstar/kstar_BC100DE_battery_cabinet.png" alt="BC100DE battery cabinet" maxWidth="300px" />

<ClickableImage src="/img/customers/kstar/kstar_BC70DE2_battery_cabinet.png" alt="BC70DE2/BC89DE2/BC107DE2 battery cabinet" maxWidth="300px" />

<ClickableImage src="/img/customers/kstar/kstar_BC197DE2_battery_cabinet.png" alt="BC197DE2/BC215DE2/BC233DE2 battery cabinet" maxWidth="300px" />


## Wiring

The <BrandName /> <ControllerName /> and the KSTAR inverters communicate via Ethernet or RS485.

### Ethernet

<ClickableImage src="/img/customers/kstar/kstar_ci_connection_diagram_tcp.png" alt="TCP connection diagram" maxWidth="550px" />

For correct ethernet wiring: Follow the [the guidelines for ethernet wiring](/Controller/wiring-best-practices/#ethernet).

### RS485

<ClickableImage src="/img/customers/kstar/kstar_ci_connection_diagram_rs485.png" alt="RS485 connection diagram" maxWidth="550px" />

## Configuration
<RS485AddressNote />


# KSTAR BluE-S Series (Gen 1)


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/customers/kstar/logo.jpeg"
    alt="logo"
    style={{ display: "block", margin: "0 auto", width: "400px"}}
/>

# KSTAR BluE-S Series (Gen 1)

## Supported Devices

<DeviceSupportTable
  devices={[
    { type: 'BluE-S (1st Gen) Single-Phase', variants: 'BluE-S 3680D/5000D/6000D-M1', modbusTcp: '❌', rs485: '✅', curtailment: '✅' , firmwareVersion: 'ARM v2.7.08 or higher'},
    { type: 'BluE-S (1st Gen) Three-Phase', variants: 'E4KT/E5KT/E6KT/E8KT/E10KT/E12KT', modbusTcp: '❌', rs485: '✅', curtailment: '✅' , firmwareVersion: 'ARM v1.5.00 or higher'},
  ]}
  showVariants={true}
  showModbusTcp={true}
  showRs485={true}
  showCurtailment={true} showReactivePower={true}
  showFirmwareVersion={true}
/>

> [!WARNING]
> Official KSTAR documentation confirms that Modbus TCP (Ethernet) is **not supported** for third-party control on these devices.
> We recommend connecting the KSTAR battery and the <ControllerName /> using **RS485**.

## Wiring

The <BrandName /> <ControllerName /> and the KSTAR inverters communicate via RS485.

### Single-Phase Wiring (BluE-S 3680D/5000D/6000D-M1)
Connect the <ControllerName /> to the **CT/METER** Port using an RS-485 cable.
* **RS485-A:** PIN 3
* **RS485-B:** PIN 4

<ClickableImage src="/img/customers/kstar/kstar_blueseries_connection_diagram_single_phase.png" alt="KSTAR connection diagram for single phase systems" maxWidth="550px" />

### Three-Phase Wiring (E4KT...E12KT)
Connect the <ControllerName /> to the **METER/DRY** Port (specifically the CT/METER pins).
* **RS485-A:** PIN 6
* **RS485-B:** PIN 5

<ClickableImage src="/img/customers/kstar/kstar_blueseries_connection_diagram_three_phase.png" alt="KSTAR connection diagram for three-phase systems" maxWidth="550px" />

## Configuration

<RS485AddressNote />

To ensure the <ControllerName /> can control the inverter, the following settings must be configured on the inverter via the Screen or App.

### 1. Work Mode Settings
For VPP control to function reliably, you must configure the following:
1.  Set **Work Mode** to **Self-Consumption**.
2.  Set **Charge from Grid** to **Disable** (inside the Self-Consumption menu).

### 2. Disable Conflicting Modes
The following modes have higher priority than remote control and must be **Disabled**:
* **Force Charge/Discharge** (Set to "Invalid" or 0)
* **Generator Mode**

### 3. Port Configuration
Ensure the communication port is set correctly:
* **CT/Meter Selection:** Set to **CT** (Default).
* **Baud Rate:** 9600.

> [!NOTE]
> Restart the battery inverter after changing the settings.

<br/>

> [!CAUTION]
> Because the battery goes into **sleep mode** at **10% SoC**, we recommend setting the **minimum state of charge** level to at least **12%**.
> When the battery goes into sleep mode, it **cannot be controlled** by the <BrandName /> <ControllerName />.


# KSTAR BlueSpark Series (Gen 2)


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/customers/kstar/logo.jpeg"
    alt="logo"
    style={{ display: "block", margin: "0 auto", width: "400px"}}
/>

# KSTAR BlueSpark Series (Gen 2)

## Supported Devices

<DeviceSupportTable
  devices={[
    { type: 'BlueSpark (2nd Gen) Single-Phase', variants: 'E(3.68/5/6)KS-D22', modbusTcp: '✅', rs485: '✅', curtailment: '✅' , firmwareVersion: 'ARM v1.3.00 or higher'},
    { type: 'BlueSpark (2nd Gen) Three-Phase', variants: 'E(4/5/6/8/10/12)KT-D22', modbusTcp: '✅', rs485: '✅', curtailment: '✅' , firmwareVersion: 'All versions'},
  ]}
  showVariants={true}
  showModbusTcp={true}
  showRs485={true}
  showCurtailment={true} showReactivePower={true}
  showFirmwareVersion={true}
/>

## Wiring

The <BrandName /> <ControllerName /> and the KSTAR inverters communicate via RS485 or TCP.

### RS485 Wiring

#### Single-Phase Wiring (E..KS-D22)
Connect the <ControllerName /> to the **CT/METER** Port using an RS-485 cable.
* **RS485-A:** PIN 6
* **RS485-B:** PIN 5

<ClickableImage src="/img/customers/kstar/kstar-bluespark-single-phase-wiring.png" alt="KSTAR RS485 connection diagram for single phase systems" maxWidth="550px" />

#### Three-Phase Wiring (E..KT-D22)
Connect the <ControllerName /> to the **METER/DRY** Port (specifically the CT/METER pins).
* **RS485-A:** PIN 6
* **RS485-B:** PIN 5

<ClickableImage src="/img/customers/kstar/kstar-bluespark-three-phase-wiring.png" alt="KSTAR RS485 connection diagram for three-phase systems" maxWidth="550px" />

### TCP Wiring

Connecting the <BrandName /> <ControllerName /> to the KSTAR inverter via TCP is possible by using the KSTAR Logger.

Connect the KSTAR WiFi/LAN dongle to the COM port. Connect both the KSTAR WiFi/LAN dongle and the <BrandName /> <ControllerName /> to the same network.

The <ControllerName /> communicates with the KSTAR Logger via Modbus TCP on port **502**.

#### Single-Phase TCP Wiring (E..KS-D22)

<ClickableImage src="/api/media/agent-uploads/Controller/Devices/PV-hybrid-and-battery-inverters/KSTAR/BlueSparkSeries/kstar-bluespark-single-phase-wiring-tcp.png" alt="KSTAR TCP connection diagram for single phase systems" maxWidth="550px" />

#### Three-Phase TCP Wiring (E..KT-D22)

<ClickableImage src="/api/media/agent-uploads/Controller/Devices/PV-hybrid-and-battery-inverters/KSTAR/BlueSparkSeries/kstar-bluespark-three-phase-wiring-tcp.png" alt="KSTAR TCP connection diagram for three-phase systems" maxWidth="550px" />

## Configuration

<RS485AddressNote />

To ensure the <ControllerName /> can control the inverter, the following settings must be configured on the inverter via the Screen or App.

### 1. Work Mode Settings
For VPP control to function reliably, you must configure the following:
1.  Set **Work Mode** to **Self-Consumption**.
2.  Set **Charge from Grid** to **Disable** (inside the Self-Consumption menu).

### 2. Disable Conflicting Modes
The following modes have higher priority than remote control and must be **Disabled**:
* **Force Charge/Discharge** (Set to "Invalid" or 0)
* **Generator Mode**

### 3. Port Configuration
Ensure the communication port is set correctly:
* **CT/Meter Selection:** Set to **CT** (Default).
* **Baud Rate:** 9600.

> [!NOTE]
> Restart the battery inverter after changing the settings.
> BlueSpark E12KT-D22: This model features a simplified installation architecture that completely eliminates the need for an external parallel box

<br/>

> [!CAUTION]
> Because the battery goes into **sleep mode** at **10% SoC**, we recommend setting the **minimum state of charge** level to at least **12%**.
> When the battery goes into sleep mode, it **cannot be controlled** by the <BrandName /> <ControllerName />.

# Kstar


import { FolderOverview } from '@/components/FolderOverview';

# Kstar

<FolderOverview folder="Controller/Devices/PV-hybrid-and-battery-inverters/KSTAR" />


# KSTAR KSG Inverters


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/customers/kstar/logo.jpeg"
    alt="logo"
    style={{ display: "block", margin: "0 auto", width: "400px"}}
/>

# KSTAR KSG Inverters


## Supported Devices

<DeviceSupportTable
  devices={[
    { type: 'KSG Inverter', variants: '1-250K', modbusTcp: '❌', rs485: '✅', curtailment: '✅' },
  ]}
  showVariants={true}
  showModbusTcp={true}
  showRs485={true}
  showCurtailment={true} showReactivePower={true}
/>

## Wiring

The <BrandName /> <ControllerName /> and the KSTAR inverters communicate via RS485.


## Configuration
<RS485AddressNote />


# Libattion


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

# Libattion

<img
  src="/img/customers/libattion/Logo_Libattion.png"
  alt="Libattion"
  style={{ display: "block", margin: "0 auto", width: "40%" }}
/>

## Supported Devices

<div
  style={{
    display: "flex",
    justifyContent: "center",
    alignItems: "flex-start",
    gap: "24px",
    flexWrap: "wrap",
    marginBottom: "2rem",
  }}
>
  <div style={{ flex: "1", minWidth: "300px", maxWidth: "500px" }}>
    <ClickableImage src="/img/controller/devices/pv-hybrid-and-battery-inverters/libattion/e-rack-V2-18-and-24.png" />
  </div>

  <div style={{ flex: "1", minWidth: "300px", maxWidth: "500px" }}>
    <ClickableImage src="/img/controller/devices/pv-hybrid-and-battery-inverters/libattion/e-Cabinet-440-05P-Rendering.png" />
  </div>
</div>

<DeviceSupportTable
  devices={[
    {
      type: 'MBMS',
      modbusTcp: '✅',
      rs485: '❌'
    },
    {
      type: 'e-Rack v2-18 + Inverter (85 kW / 97 kWh)',
      modbusTcp: '✅',
      rs485: '❌'
    },
    {
      type: 'e-Cabinet 232 (115 kW / 232 kWh)',
      modbusTcp: '✅',
      rs485: '❌'
    },
    {
      type: 'e-Cabinet 440 (220 kW / 440 kWh)',
      modbusTcp: '✅',
      rs485: '❌'
    },
    {
      type: 'e-Container X (AC-Block) (0.7–2.8 MW / 2.1–5.6 MWh)',
      modbusTcp: '✅',
      rs485: '❌'
    }
  ]}
  showModbusTcp={true}
  showRs485={true}
  showReactivePower={true}
/>

## Wiring

Connecting an External EMS or Plant Controller

Connect Port A of the Libattion system to the external third-party EMS or plant controller and ensure that the system has access to the internet.

There are two possible configurations:

Option A – Connection via an Ethernet switch

Connect both the Libattion Controller and the external third-party EMS or plant controller to an Ethernet switch. The switch should be connected to a router providing internet access.

Option B – Direct connection

Connect the Libattion Controller directly to the external third-party EMS or plant controller. In this configuration, the connected system must provide internet access to the Libattion Controller.

Network requirements

In both configurations, the Libattion Controller must receive an IP address from a DHCP server on the local network.

If firewall rules are configured to restrict outgoing connections, the firewall requirements for the customer's local network must be respected to ensure proper communication and connectivity.

### Connecting an External EMS or Plant Controller

Connect **Port A** of the Libattion system to the external third-party EMS or Plant Controller and ensure that the system has access to the internet.

There are two possible configurations:

#### Option A – Connection via an Ethernet Switch

Connect both the Libattion Controller and the external third-party EMS or Plant Controller to an Ethernet switch. The switch should be connected to a router providing internet access.

#### Option B – Direct Connection

Connect the Libattion Controller directly to the external third-party EMS or Plant Controller. In this configuration, the connected system must provide internet access to the Libattion Controller.

### Network Requirements

For both configurations, the Libattion Controller must receive an IP address from a **DHCP server** on the local network.

If firewall rules are configured to restrict outgoing connections, ensure that the firewall requirements for the customer's local network are respected to allow proper communication and connectivity.

### Ethernet Connection

Make sure that the <ControllerName /> and the Libattion system are connected to the same network.

For general Ethernet wiring best practices, see the [Ethernet wiring guidelines](/Controller/wiring-best-practices/#ethernet).

#### Commissioning
The Libattion Controller will boot automatically once connected to power.
Contact the Libattion Service Team for the comissioning beforehand.

#### Commissioning

The Libattion Controller will boot automatically once connected to power.

Please contact the Libattion Service Team before commissioning the installation.

# LONGi


import { BrandName, ControllerName } from '@site/src/components/customFields';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/customers/longi/logo.png"
    alt="LONGi logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

# LONGi

The <BrandName /> <ControllerName /> integrates with the LONGi **PCS cabinet integrated energy storage
system** over Modbus TCP. Both single units and multi-unit installations (up to 10 devices) are supported.

<ClickableImage src="/img/customers/longi/devices.png" alt="LONGi supported devices" maxWidth="700px" />

## Supported Devices

<DeviceSupportTable
  devices={[
    { type: "OmniCube-A215", form: "Single", modbus: "✅" },
    { type: "OmniCube-A215", form: "Multiple (up to 10)", modbus: "✅" },
    { type: "OmniCube-L233", form: "Single", modbus: "✅" },
    { type: "OmniCube-L233", form: "Multiple (up to 10)", modbus: "✅" },
    { type: "Hi MO ONE PRO-L261", form: "Single", modbus: "✅" },
    { type: "Hi MO ONE PRO-L261", form: "Multiple (up to 10)", modbus: "✅" },
    { type: "PotisCabinet-D9", form: "Cabinet", modbus: "✅" }
  ]}
  customColumns={{ form: "Form", modbus: "Modbus TCP" }}
  showReactivePower={true}
/>

## Connection Guide

### Modbus TCP

The EMS controller can be connected to the <ControllerName /> via an RJ45 Ethernet cable, as shown in the
diagram below.

> [!NOTE]
> Please use the **LAN5** port to connect to the <ControllerName />.

<ClickableImage src="/img/customers/longi/setup-1.png" alt="LONGi Modbus TCP connection diagram showing the LAN5 port" maxWidth="700px" />

For correct ethernet wiring, follow the [guidelines for ethernet wiring](/Controller/wiring-best-practices/#ethernet).

## Setup and Query Guide

1. The LAN5 port of a factory-default EMS controller usually has the default IP address
   `192.168.189.36`. Connect a laptop to the LAN5 port with a network cable, then enter the URL
   `http://192.168.189.36:10180` in the browser to access the EMS page.

<ClickableImage src="/img/customers/longi/setup2.png" alt="eEMS energy management system page" maxWidth="700px" />

2. Click on **eEMS** on the left side of the interface to reveal the login button. Enter your username and
   password to log into the system.

<ClickableImage src="/img/customers/longi/setup3.png" alt="eEMS login dialog" maxWidth="700px" />

3. Click on **eEMS**, go to **System Settings**, scroll down and click **Network Settings**. There you can
   see the IP address corresponding to each network port.

<ClickableImage src="/img/customers/longi/setup4.png" alt="Network Settings showing the IP address for each network port" maxWidth="700px" />


# Marstek


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import ClickableImage from '@site/src/components/ClickableImage';
import PdfLink from '@site/src/components/PdfLink';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/customers/marstek/logo.png"
    alt="logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

# Marstek Inverters

## Supported Devices
> [!NOTE] Device Compatibility
> Please update your inverter to the latest firmware version to enable modbusTCP, this is supported from v144 onwards.

<DeviceSupportTable
  devices={[
    {
      type: "Venus-C",
      variants: "2.5kWh",
      modbusTcp: "✅",
      rs485: "✅",
      curtailment: "❌"
    },
    {
      type: "Venus-E",
      variants: "5.1kWh",
      modbusTcp: "✅",
      rs485: "✅",
      curtailment: "❌"
    }
  ]}
  showVariants={true}
  showModbusTcp={true}
  showRs485={true}
  showCurtailment={true} showReactivePower={true}
/>

> [!NOTE] Device Compatibility
> This integration was tested with Venus C device. However, other devices using the same communication protocol, such as Venus E, may also be compatible.
> If you have such a device, it is likely to work, but we are awaiting official confirmation from the manufacturer.

For the configuration of the device, please follow the guide:
<PdfLink url="/media/marstek/installatiehandleiding-marstek-venus-e-v30.pdf">Marstek official guide</PdfLink>

## Wiring

The <BrandName /> <ControllerName /> and the Marstek inverters communicate via RS485.
From the V3 version of Marstek, there is native Modbus TCP support that can be used to connect directly through the LAN cable.

### RS485
The RS485 port can be found in the following diagram and the cabling is depending on the version of the device.
<ClickableImage src="/media/marstek/schema.png" alt="Marstek schema" maxWidth="450px" />
The A and B cables are different for V2 and V3.
Below you can see the connection for V2.
<ClickableImage src="/media/marstek/rs485v2.png" alt="Marstek V2 cabling for RS485" maxWidth="350px" />
For V3 the cables 1 and 2 represent B and A respectively, while cables 4-5 are connecting to VCC amd 7-8 to GND.
Once connected, the cable will be as such:
<ClickableImage src="/media/marstek/connection.png" alt="Marstek connection" maxWidth="350px" />

<RS485ConnectionTable firstColumn={["A", "B", "GND"]} />

<RS485AddressNote />

# Mastervolt


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/customers/mastervolt/logo.png"
    alt="logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

## Supported Devices

<DeviceSupportTable
  devices={[
    {  
      type: "SunMaster ES4.6",
      modbusTcp: "❌",
      rs485: "✅",
      curtailment: "❌",
    },
    {
      type: "SunMaster XS2000",
      modbusTcp: "❌",
      rs485: "✅",
      curtailment: "❌",
    },
    {
      type: "SunMaster XS3200",
      modbusTcp: "❌",
      rs485: "✅",
      curtailment: "❌",
    },
    {
      type: "SunMaster XS4300",
      modbusTcp: "❌",
      rs485: "✅",
      curtailment: "❌",
    },
    {
      type: "SunMaster XS6500",
      modbusTcp: "❌",
      rs485: "✅",
      curtailment: "❌",
    },
    {
      type: "SunMaster CS10TL",
      modbusTcp: "❌",
      rs485: "✅",
      curtailment: "❌",
    },
    {
      type: "SunMaster CS12TL",
      modbusTcp: "❌",
      rs485: "✅",
      curtailment: "❌",
    },
    {
      type: "SunMaster CS15TL",
      modbusTcp: "❌",
      rs485: "✅",
      curtailment: "❌",
    },
    {
      type: "SunMaster CS20TL",
      modbusTcp: "❌",
      rs485: "✅",
      curtailment: "❌",
    },
    {
      type: "SunMaster CS30TL",
      modbusTcp: "❌",
      rs485: "✅",
      curtailment: "❌",
    },
    {
      type: "SunMaster IS10",
      modbusTcp: "❌",
      rs485: "✅",
      curtailment: "❌",
    },
    {
      type: "SunMaster IS15",
      modbusTcp: "❌",
      rs485: "✅",
      curtailment: "❌",
    },
    {
      type: "SunMaster XL10",
      modbusTcp: "❌",
      rs485: "✅",
      curtailment: "❌",
    },
    {
      type: "SunMaster XL15",
      modbusTcp: "❌",
      rs485: "✅",
      curtailment: "❌",
    },
  ]}
  showModbusTcp={true}
  showRs485={true}
  showCurtailment={true} showReactivePower={true}
/>


## Wiring


### RS485
For RS485 wiring, follow the [guidelines for RS485 wiring](/Controller/wiring-best-practices/#rs485).

# MidTeQ


import { BrandName, ControllerName } from '@site/src/components/customFields';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';
import ClickableImage from '@site/src/components/ClickableImage';

<img
    src="/img/customers/MidTeQ/logo-midteq.png"
    alt="logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

The MidTeQ inverter is all-in-one hybrid inverter that can be used with the <BrandName /> <ControllerName /> to monitor and
control your solar power and battery system. It supports both Modbus TCP and Modbus RTU (RS485) communication protocols.
## Supported Devices

<DeviceSupportTable
  devices={[
    { type: 'PrimePower Hybrid inverter Inverter', modbusTcp: '✅', rs485: '✅', curtailment: "✅" },
  ]}
  showModbusTcp={true}
  showRs485={true}
  showCurtailment={true} showReactivePower={true}
/>

The MidTeQ inverter has a nominal power output of 10 kW, regardless of the battery energy capacity.
Make sure to configure the inverter correctly in the <BrandName /> <ControllerName /> to match your system's specifications.
However, the maximum charge and discharge power depends on the battery energy capacity. See the table below for the correct settings.
__If the maximum charge and discharge power of your MidTeQ inverter is not set to correctly in the <BrandName /> <ControllerName />, it leads to unstable operation of the inverter.__

| Battery energy capacity    | Maximum charge and discharge power |
| -------- | ------- |
| 5 kWh system  | 🟠  __2.6 kW charge and 2.6 kW discharge__ to be configured in the device settings.|
| 10 kWh system  | 🟠  __2.6 kW charge & 5.2 kW discharge__ to be configured in the device settings.|
| 15 kWh system  | 🟠  __5.2 kW charge & 7.6 kW discharge__ to be configured in the device settings.|
| 20 kWh system  | 🟠  __7.6 kW charge & 10 kW discharge__ to be configured in the device settings.|
| 15 kWh until 75 kWh | ✅ 10 kW  (no limit needed)  |

> [!WARNING] I can't find my MidTeQ
> The MidTeQ default bus addresses are 247 for Modbus RTU and 255 for Modbus TCP.
> The <BrandName /> <ControllerName /> will scan for devices on all addresses from 1 to 255.
> __Therefore, it can take a while to scan for devices.__
>
> __TIP:__ If you know the bus address of your MidTeQ inverter, you can set it in the <BrandName /> <ControllerName /> to speed up the scanning process. See the section "Speed up scan process (TCP/RTU)" below.



## Modbus TCP
Connect the MidTeQ inverter to your network using an Ethernet cable and the COM-adapter that is provided with the inverter:
<ClickableImage
  src="/img/customers/MidTeQ/modbus-tcp.png"
  alt="Wiring"
  maxWidth="50%"
/>
Check in the MidTeQ app or monitoring portal that the inverter is connected to your network and has an IP address assigned.


Modbus TCP is by default enabled on the MidTeQ inverters. No additional configuration is required.
The default bus address for Modbus TCP is 255.
Other common bus addresses for Modbus TCP are 1, 8, 247.

## Speed up scan process (TCP)
If you know the bus address of your MidTeQ inverter, you can set it in the <BrandName /> <ControllerName /> to speed up the scanning process.
The example below is for a MidTeQ connected using Modbus TCP with bus address 255. By changing the min. bus address to 254, we tell the
<BrandName /> <ControllerName /> to only scan for devices on bus addresses 254 and 255 and to skip the other addresses.
<ClickableImage
  src="/img/customers/Solinteg/1.png"
  alt="Wiring"
  maxWidth="100%"
/>

## Modbus RTU (RS485)
Crimp an RJ45 plug on one end of an Ethernet cable according to the T568B wiring standard.
Insert the crimped RJ45 plug into the <BrandName /> <ControllerName />.

On the other end of the Ethernet cable, connect the blue/white wire to connector pin 13 and the solid blue wire to pin 14.

Finally, connect the USB end of the dongle to an available USB port on the <BrandName /> <ControllerName />.

<ClickableImage
  src="/img/generic/solingtechVerbinding.png"
  alt="Wiring"
  maxWidth="70%"
/>

The default modbus bus address or RTU is 247.


# Motoma


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import ClickableImage from '@site/src/components/ClickableImage';

<img
    src="/img/sgo/Logo_Motoma.png"
    alt="Logo"
    style={{ display: "block", margin: "0 auto", width: "40%" , paddingBottom: "40px"}}
/>

## Supported Devices

<DeviceSupportTable
  devices={[
    {
      type: 'Elite Inverter',
      variants: '8KW / 12KW',
      modbusTcp: '❌',
      rs485: '✅',
      curtailment: '✅',
    },
  ]}
  showModbusTcp={ true }
  showVariants={ true }
  showRs485={ true }
  showCurtailment= { true } showReactivePower={true}
/>


## Wiring
You need to connect the battery tothe inverter, for that plug the red and black cables in the red and black battery port on the inverter, then you need to connect the two via the black cable as follow : 
<ClickableImage src="/img/customers/motoma/Inverter connection.jpg" alt="Inverter connection" maxWidth="350px" />
<ClickableImage src="/img/customers/motoma/Battery connection.jpg" alt="Battery connection" maxWidth="350px" />

### RS485
To connect the <BrandName /> <ControllerName /> controller to the inverter you will need a Modbus Card, put it in the intelligent slot of the inverter (you may need to remove the cache by unscrewing the two black plates, see the picture below).
Configure the Modbus Card according to the current documentation in the manufacturer's [communication downloads](https://nextups.eu/category/communication/).
<ClickableImage src="/img/customers/motoma/Inverter cache.jpg" alt="Inverter cache" maxWidth="350px" />
<RS485AddressNote />
Once the Modbus Card is well configured, you can plug the cables into the controller, for that strip one end of your RS485 cable and take the cables corresponding to the pins 4 (usually blue) and 5 (usually blue and white).
Then plug the pin 4 into the RS485B port of the controller and the pin 5 in the RS485A port of the controller.
<ClickableImage src="/img/customers/motoma/Controller connection.jpg" alt="Controller connection" maxWidth="350px" />
## Connection to the Controller

You then need to connect the device to the controller, for that follow this guide : [Adding a device](/Controller/Configuration%20from%20A%20to%20Z/11-Extra-Information/adding-device/).



# Octave Energy


import { BrandName, ControllerName } from '@site/src/components/customFields';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/customers/octave/logo.jpg"
    alt="logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>


## Supported Devices

<DeviceSupportTable
  devices={[
    {
      type: "Battery Cabinet",
      modbusTcp: '✅',
      rs485: '❌',
      curtailment: '✅',
    },
  ]}
  showModbusTcp ={true}
  showRs485 ={true}
  showCurtailment ={true} showReactivePower={true}
/>


## Wiring

### Ethernet
For correct ethernet wiring: Follow the [the guidelines for ethernet wiring](/Controller/wiring-best-practices/#ethernet).


## Configuration

> [!WARNING] Port 5021
> Unlike standard Modbus devices which typically use port 502, the Octave Energy Battery Cabinet uses **TCP Port 5021**.
> Please ensure you configure this specific port in the device settings when adding it to the <ControllerName />.

# OmniPower


import { BrandName, ControllerName } from '@site/src/components/customFields';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';
import ClickableImage from '@site/src/components/ClickableImage';

<img
    src="/img/sgo/Logo_OmniPower.png"
    alt="logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

# OmniPower

The OmniPower Qualtech Battery is a high-voltage battery cabinet that communicates directly via Modbus TCP.

## Supported Devices

<DeviceSupportTable
  devices={[
    {
      type: 'Qualtech Battery',
      modbusTcp: '✅',
      rs485: '❌',
      curtailment: '❌',
    },
  ]}
  showModbusTcp={true}
  showRs485={true}
  showCurtailment={true} showReactivePower={true}
/>

> [!NOTE] Features
> While active power curtailment is not supported, the driver does support **remote restarting** of the battery system via the <ControllerName /> interface.

## Wiring

### Ethernet
For correct ethernet wiring: Follow the [the guidelines for ethernet wiring](/Controller/wiring-best-practices/#ethernet).

## Configuration

To configure the OmniPower Qualtech Battery in the <ControllerName />, you need to provide specific network settings and system details.

> [!WARNING] Port 2404
> Unlike standard Modbus devices which typically use port 502, the OmniPower Qualtech Battery communicates on **TCP Port 2404**.
> Please ensure you configure this specific port in the device settings when adding it to the <ControllerName />.



# OX-Power


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/customers/ox-power/logo.svg"
    alt="logo"
    style={{ display: "block", margin: "0 auto", width: "20%"}}
/>

## Supported Devices

<DeviceSupportTable
  devices={[
    {
      type: 'Energy B-OX XL',
      modbusTcp: '✅',
      rs485: '❌',
    },
  ]}
  showModbusTcp={true}
  showRs485={true}
  showReactivePower={true}
/>

## Wiring

### Ethernet
For correct ethernet wiring: Follow the [the guidelines for ethernet wiring](/Controller/wiring-best-practices/#ethernet).


# Pixii


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/customers/pixii/Pixii_Logo.png"
    alt="logo"
    style={{ display: "block", margin: "0 auto", width: "40%" , paddingBottom: "40px"}}
/>

<DeviceSupportTable
  devices={[
    {
        type: "PowerShaper XL",
        modbusTcp: "✅",
        rs485: "❌",
        curtailment: "❌"
    }
  ]}

  showModbusTcp={true}
  showRs485={true}
  showCurtailment={true} showReactivePower={true}
/>

> [!NOTE] Device Compatibility
> This integration was tested with Powershaper XL device. However, other devices using the same communication protocol, such as Powershaper, Powershaper 2, may also be compatible.
> If you have such a device, it is likely to work, but we are awaiting official confirmation from the manufacturer.


## Configuration
Make sure that the Controller and the Pixii PowerShaper are connected to the same network.

### Ethernet Connection
For correct ethernet wiring, follow the [guidelines for ethernet wiring](/Controller/wiring-best-practices/#ethernet).

### 2: Pixii PowerShaper Configuration
| Steps |
|------|
| **2a**. Open the Pixii PowerShaper web interface by entering the IP address of the system in a web browser. |
| **2b**. To allow communication make sure the **Enabled** checkbox is checked and the **Type** is set to the appropriate type <img src="/img/customers/pixii/PowerShaperInstruction.png" alt="Image" maxWidth="100%"/> |

# Power-Sonic


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/customers/power-sonic/logo.png"
    alt="logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>


## Supported Devices

<DeviceSupportTable
  devices={[
    { type: 'PS-PULSE-INV-6KW', modbusTcp: '❌', rs485: '✅', curtailment: "❌" },
    { type: 'PS-PULSE-INV-8KW', modbusTcp: '❌', rs485: '✅', curtailment: "❌" },
    { type: 'PS-PULSE-INV-10KW', modbusTcp: '❌', rs485: '✅', curtailment: "❌" },
    { type: 'PS-PULSE-INV-12KW', modbusTcp: '❌', rs485: '✅', curtailment: "❌" }
  ]}
  showModbusTcp={true}
  showRs485={true}
  showCurtailment={true} showReactivePower={true}
/>


## Wiring

### RS485
<RS485ConnectionTable firstColumn={["", "", ""]} />
<ClickableImage src="/img/customers/power-sonic/wiring.png" alt="Image 1" maxWidth="450px" />

## Configuration
<RS485AddressNote />

1. Set the working mode to Self Consume.
<ClickableImage src="/img/customers/power-sonic/config_pt1.png" alt="Image 1" maxWidth="450px" />

2. Set Zero Export to Disable.
<ClickableImage src="/img/customers/power-sonic/config_pt2.png" alt="Image 1" maxWidth="450px" />

3. Set Remote Control to Enable.
<ClickableImage src="/img/customers/power-sonic/config_pt3.png" alt="Image 1" maxWidth="450px" />

4. Set the RS485 address. The default baudrate is 9600, if not, set it to 9600.
<ClickableImage src="/img/customers/power-sonic/config_pt4.png" alt="Image 1" maxWidth="450px" />

5. Set the charge current.
Set the charge current.
> [!WARNING] IMPORTANT!
> For a 5KT set it to 100
> For 10KT set it to 160
<ClickableImage src="/img/customers/power-sonic/config_pt5.png" alt="Image 1" maxWidth="450px" />

6. Set AC Couple to Enable.
<ClickableImage src="/img/customers/power-sonic/config_pt6.png" alt="Image 1" maxWidth="450px" />


# Poweroad


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import ClickableImage from '@site/src/components/ClickableImage';

<img
    src="/img/customers/poweroad/logo.png"
    alt="Logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

# Poweroad

> [!WARNING] Sinexcel and EnjoyPowers inverters in combination with a Poweroad BMS
> Starting from <BrandName /> <ControllerName /> software version 1.17.0.x, you must add the inverter and Poweroad BMS as separate devices, and dc-link them through the groups page. For more information, see: [DC-linking inverters, batteries and BMS systems](/Controller/Configuration%20from%20A%20to%20Z/11-Extra-Information/dc-linking/)

## Supported Devices

<DeviceSupportTable
  devices={[
    {
      type: 'Flex 126',
      variants: 'AIO',
      modbusTcp: '✅',
      rs485: '⚠️'
    },
    {
      type: 'Flex 215',
      variants: 'AIO',
      modbusTcp: '✅',
      rs485: '⚠️'
    },
    {
      type: 'Flex 215',
      variants: 'AIOS',
      modbusTcp: '✅',
      rs485: '⚠️'
    },
    {
      type: 'Flex 233',
      variants: 'AIO',
      modbusTcp: '✅',
      rs485: '⚠️'
    },
    {
      type: 'Flex 372',
      variants: 'Liquid Cooling',
      modbusTcp: '✅',
      rs485: '⚠️'
    },
    {
      type: 'Centric',
      variants: 'L20',
      modbusTcp: '✅',
      rs485: '⚠️'
    },
    {
      type: 'Centric',
      variants: 'A20',
      modbusTcp: '✅',
      rs485: '⚠️'
    }
  ]}
  showModbusTcp={ true }
  showVariants={ true }
  showRs485={ true }
  showReactivePower={true}
/>


## Wiring
For correct ethernet wiring: Follow the [the guidelines for ethernet wiring](/Controller/wiring-best-practices/#ethernet).

RS485 connection is possible but may need an update from Poweroad.
Please contact Poweroad support for more information.

## Configuration
Modbus TCP is enabled by default on Poweroad devices, no extra configuration is needed.


# Pylontech


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';
import Mermaid from '@theme/Mermaid';

<img
    src="/img/customers/pylontech/pylontech_logo.png"
    alt="logo"
    style={{ display: "block", margin: "0 auto", width: "40%" }}
/>

# Pylontech battery systems
The <BrandName /> <ControllerName /> supports Pylontech containerized systems via the L-EMS protocol over Modbus TCP.

## Supported Devices

<ClickableImage src="/img/customers/pylontech/a100.png" alt="Image" maxWidth="450px" />


<DeviceSupportTable
  devices={[
    { type: 'C&I OPTIM US A100-HY via L-EMS', modbusTcp: '✅', rs485: '❌', curtailment: "❌" },
    { type: 'C&I OPTIM US L417-BAT via L-EMS', modbusTcp: '✅', rs485: '❌', curtailment: "❌" },
    { type: 'C&I OPTIM US A300-HY via L-EMS', modbusTcp: '✅', rs485: '❌', curtailment: "❌" },
    { type: 'C&I OPTIM US A329-BAT via L-EMS', modbusTcp: '✅', rs485: '❌', curtailment: "❌" },
    { type: 'C&I OPTIM US L260-OMNI via L-EMS', modbusTcp: '✅', rs485: '❌', curtailment: "❌" },
    { type: 'C&I Container A1000-OMNI via L-EMS', modbusTcp: '✅', rs485: '❌', curtailment: "❌" },
    { type: 'C&I Container L5000-BAT via L-EMS', modbusTcp: '✅', rs485: '❌', curtailment: "❌" },
    { type: 'C&I Container A2000-OMNI via L-EMS', modbusTcp: '✅', rs485: '❌', curtailment: "❌" },
    { type: 'C&I Container L2200-OMNI via L-EMS', modbusTcp: '✅', rs485: '❌', curtailment: "❌" },
    { type: 'C&I Container-connected grid meter', modbusTcp: '✅', rs485: '❌', curtailment: "❌" },
  ]}
  showModbusTcp={true}
  showRs485={true}
  showCurtailment={false} showReactivePower={true}
/>

> [!NOTE]
> The Pylontech integration currently only supports communication via Modbus TCP using the L-EMS protocol.
> This protocol is available on Pylontech devices with a 'recent' firmware version. Please refer to the Pylontech
> support or documentation to check if your device supports the L-EMS protocol.


## Configuration
1. Open the front panel of the cabinet:
   <ClickableImage src="/img/customers/pylontech/0.jpeg" alt="Image 1" maxWidth="300px" />
2. Focus on the market area in the picture below:
   <ClickableImage src="/img/customers/pylontech/1.png" alt="Image 1" maxWidth="300px" />
3. Connect `LAN2` with a RJ45 cable to a network switch exposed to the internet.
   <ClickableImage src="/img/customers/pylontech/2.jpeg" alt="Image 1" maxWidth="500px" />
4. (Optional, but recommended): Connect a grid meter to the Pylontech. This allows the <BrandName /> <ControllerName /> to do an improved, more accurate, self-consumption on this device.
    This should be connected to __meter input 2__.
5. Inside the Pylontech web interface, check for the following:
    - If it can be reached and the system is healthy.
    - __IMPORTANT__: That the fallback mode is set to self-consumption.
6. The Pylontech is now ready to be controlled via the <BrandName /> <ControllerName />.


# RCT Power


import { BrandName, ControllerName } from "@site/src/components/customFields";
import DeviceSupportTable from "@site/src/components/DeviceSupportTable";

<img
  src="/img/customers/RCTPower/rct-power-logo.png"
  alt="RCT Power"
  style={{ display: "block", margin: "0 auto", width: "40%" }}
/>

# RCT Power

## Supported Devices

<DeviceSupportTable
  devices={[
    {
      type: "CESS 200",
      variants: "Modbus TCP",
      modbusTcp: "✅",
      rs485: "❌",
    },
  ]}
  showModbusTcp={true}
  showRs485={true}
  showCurtailment={true} showReactivePower={true}
/>

## Wiring
The communication between the <BrandName /> <ControllerName /> and the Tesvolt system operates via Modbus TCP.
For correct ethernet wiring: Follow the [the guidelines for ethernet wiring](/Controller/wiring-best-practices/#ethernet).

## Configuration

### Network Setup
1. Connect the inverter to your local network via ethernet cable
2. Make sure your IP address is in the same subnet as the <ControllerName/>

### Device Setup
Make sure to allow external signals in the device settings. This can't be managed from the Eniris controller.


# Refurb


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/sgo/Logo_Refurb.png"
    alt="logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>
# Refurb

## Supported Devices

<DeviceSupportTable
  devices={[
    { type: 'Zhero CESS Plant', modbusTcp: '✅', rs485: '❌', curtailment: "❌" },
   ]}
  showModbusTcp={true}
  showRs485={true}
  showCurtailment={true} showReactivePower={true}
/>


## Wiring
### Ethernet
For correct ethernet wiring: Follow the [the guidelines for ethernet wiring](/Controller/wiring-best-practices/#ethernet).


## Configuration
If you are connecting through TCP, be sure that the device is configured to communicate with port <b>502</b>.




# Regitec


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

# Regitec Inverters

<img
    src="/img/customers/Regitec/regitec-logo.png"
    alt="Regitec"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

## Supported Devices

The <BrandName /> <ControllerName /> supports Regitec Hybrid inverters via both Modbus TCP (Ethernet) and Modbus RTU (RS485).

<DeviceSupportTable
  devices={[
    { 
      type: 'Regitec Hybrid Inverter', 
      modbusTcp: '✅', 
      rs485: '✅' 
    }
  ]}
  showModbusTcp={true}
  showRs485={true}
  showReactivePower={true}
/>

## Wiring

### Ethernet
For correct ethernet wiring: Follow the [the guidelines for ethernet wiring](/Controller/wiring-best-practices/#ethernet).

### RS485
<RS485ConnectionTable firstColumn={["A", "B", "GND"]} />

> [!NOTE]
> Ensure the termination resistor is set correctly if the inverter is at the end of the RS485 bus.




> [!WARNING]
> The Regitec driver is strictly configured for a **Baud Rate of 9600**. Ensure the inverter is not set to 19200 or 115200, as this will prevent communication.

# Renon


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/sgo/Logo_Renon.png"
    alt="logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>
# Renon Power

> [!CAUTION] 
> ### LIMITED FUNCTIONALITY
> Renon inverters are not able to sell to the grid


## Supported Devices

<DeviceSupportTable
  devices={[
    { type: 'HV', modbusTcp: '❌', rs485: '✅'},
   ]}
  showModbusTcp={true}
  showRs485={true}
  showReactivePower={true}
/>


## Wiring
### Ethernet
For correct ethernet wiring: Follow the [the guidelines for ethernet wiring](/Controller/wiring-best-practices/#ethernet).


# Ritar


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/sgo/Logo_Ritar.png"
    alt="Ritar"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

## Supported Devices

<DeviceSupportTable
  devices={[
    { type: 'Enercube', variants: '100kW/200kWh', modbusTcp: '✅', rs485: '✅', curtailment: "✅"}
  ]}
  showVariants={true}
  showModbusTcp={true}
  showRs485={true}
  showCurtailment={true} showReactivePower={true}
/>

## Connection

The communication between the <BrandName /> and the battery operates via Modbus TCP.

### Ethernet
For correct ethernet wiring: Follow the [the guidelines for ethernet wiring](/Controller/wiring-best-practices/#ethernet).

### RS485
<RS485ConnectionTable firstColumn={["A", "B", "N/A"]} />

<RS485AddressNote />

# SAJ


import { BrandName, ControllerName } from "@site/src/components/customFields";
import DeviceSupportTable from "@site/src/components/DeviceSupportTable";

<img src="/img/customers/saj/sajLogo.jpeg" alt="logo" style={{ display: "block", margin: "0 auto", width: "40%" }} />

# SAJ

## Supported Devices

<DeviceSupportTable
  devices={[
    { type: "SAJ AS2", modbusTcp: "✅", rs485: "❌", curtailment: "✅",
  instructionVideos: [{"videoId": "GhhUQrzu2eU", "title": "SAJ AS2 3–6K-S-X · side port", "description": "X revision with the 354 mm top module and active EMS/METER pins 7 and 8."}, {"videoId": "wKH0awx8LY8", "title": "SAJ AS2 5–10K-T · legacy 450 mm · active EMS pins 7/8", "description": "Earlier 450 mm top module from manual V0.2, with active EMS/METER pins 7 and 8. This does not cover revisions where those pins are marked NC."}]
},
    { type: "SAJ H1", modbusTcp: "✅", rs485: "❌", curtailment: "✅" },
    { type: "SAJ H2 series-5k-30k", modbusTcp: "✅", rs485: "❌", curtailment: "✅",
  instructionVideos: [{"videoId": "YaZbHU-S27w", "title": "SAJ H2 5–6K-S2 · EMS/METER", "description": "EU manual revision with EMS/METER and active pins 7 and 8; this video covers the 5–6 kW models."}, {"videoId": "V3mVV7UnMzQ", "title": "SAJ H2 5–10K-S3 · EMS/METER", "description": "Models: H2-5K-S3, H2-6K-S3, H2-7K-S3, H2-8K-S3, H2-10K-S3."}, {"videoId": "V_ubyZ7UrJs", "title": "SAJ H2 5–10K-T2 · separate RS485", "description": "Physical revision with a separate port marked RS485, as shown in the Australian manual. This does not cover the EMS/METER port revision."}, {"videoId": "IAmCMVtnwck", "title": "SAJ H2 10–30K-T2/T3 · EMS", "description": "Models: H2-10K-T3, H2-12K-T3, H2-15K-T2, H2-15K-T3, H2-20K-T2, H2-20K-T3, H2-25K-T3-BE, H2-25K-T3, H2-30K-T3-DE, H2-30K-T3."}]
},
    { type: "SAJ HS2 series-5k-10k", modbusTcp: "✅", rs485: "❌", curtailment: "✅",
  instructionVideos: [{"videoId": "H9DA2Igjp8A", "title": "SAJ HS2 5–6K-S2-X · side port", "description": "X revision with the 354 mm top module and active EMS/METER pins 7 and 8."}, {"videoId": "q-aT9zB8XyQ", "title": "SAJ HS2 5–10K-T2 · legacy 450 mm · active EMS pins 7/8", "description": "Earlier 450 mm top module from manual V0.2, with active EMS/METER pins 7 and 8. This does not cover revisions where those pins are marked NC."}]
},
    { type: "SAJ AS3", modbusTcp: "✅", rs485: "❌", curtailment: "✅",
  instructionVideos: [{"videoId": "JpGv3Q-1zRc", "title": "SAJ AS3 3–6K-S · COMM", "description": "Top inverter module with the COMM insert, 20 numbered terminals and two RJ45 ports. The separate round EMS RJ45 port is LAN and is not the connection shown here."}, {"videoId": "3NxXQvO84iA", "title": "SAJ AS3 3–12K-T · COMM", "description": "Top inverter module with the COMM insert, 20 numbered terminals and two RJ45 ports. The separate round EMS RJ45 port is LAN and is not the connection shown here."}]
},
    { type: "SAJ HS3", modbusTcp: "✅", rs485: "❌", curtailment: "✅",
  instructionVideos: [{"videoId": "ift7wFgEPQc", "title": "SAJ HS3 3–6K-S2 · COMM", "description": "Top inverter module with the COMM insert, 20 numbered terminals and two RJ45 ports. The separate round EMS RJ45 port is LAN and is not the connection shown here."}, {"videoId": "rEqtYctOXws", "title": "SAJ HS3 3–12K-T2 · COMM", "description": "Top inverter module with the COMM insert, 20 numbered terminals and two RJ45 ports. The separate round EMS RJ45 port is LAN and is not the connection shown here."}]
},
    { type: "SAJ CHS2", modbusTcp: "✅", rs485: "❌", curtailment: "✅" },
    { type: "SAJ CM2", modbusTcp: "✅", rs485: "❌", curtailment: "✅" },
  ]}
  showModbusTcp={true}
  showRs485={false}
  showCurtailment={true} showReactivePower={true}
/>

For a site connected through a **SAJ eManager-C1 Pro**, use the separate [eManager connection](#saj-emanager-c1-pro) below instead of selecting an individual inverter model.

## SAJ eManager-C1 Pro

The eManager is a local gateway for the inverters connected to it. This connection reads the combined installation through the eManager rather than opening a separate connection to every inverter.

> [!IMPORTANT] Testing
> The eManager connection is currently in testing and requires controller software that includes it. This is a separate connection from the direct SAJ inverter integrations listed above.

| Setting | Value |
| --- | --- |
| Manufacturer and device selection | **SAJ → eManager** |
| Connection | Ethernet / Modbus TCP |
| TCP port | `502` |
| Modbus address | The eManager's configured address; default `1` |
| Inverter count | The number of inverters connected to the eManager, from `1` to `255` |

### Connect the eManager

1. Connect the eManager and the <ControllerName /> to the same local network. Follow the [Ethernet wiring guidelines](/Controller/wiring-best-practices/#ethernet).
2. Open the controller's device setup and select **SAJ**, then **eManager**.
3. Enter the eManager's IP address, TCP port `502` and configured Modbus address. This connection uses Ethernet, not the RS485 settings for other SAJ equipment.
4. Fill in **How many inverters are connected to the eManager?** with the actual number connected to this gateway.
5. Add the connection and check the displayed system power, battery state of charge, grid measurements, phase voltages and frequency before enabling energy management.

### Why the inverter count matters

The eManager combines readings from its connected inverters. The controller uses the inverter count to convert the combined voltage and frequency readings back to meaningful values. For example, four connected inverters can return a combined frequency reading of `200 Hz`; an inverter count of `4` produces the expected `50 Hz` display.

If voltage or frequency appears to be a multiple of the expected value, correct **Inverter count**. Do not compensate by changing the electrical installation settings. The power readings represent the combined system and are not divided by this count.

The connection provides an AC active-power setpoint for the combined system. It does not provide independent setpoints for every inverter behind the eManager, or a separate PV power-limit command.

## Configuration

### 1: Physical Connection Setup

#### For Ethernet Connection:

1. Locate the communication interface on your SAJ inverter
2. Connect an ethernet cable between the inverter and your local network
3. Follow the [ethernet wiring guidelines](/Controller/wiring-best-practices/#ethernet) for proper installation

#### For RS485 Connection:

1. Locate the RS485 port on your SAJ inverter
2. Connect the RS485 cable according to the following pinout:
   - PIN A: RS485+
   - PIN B: RS485-
   - GND: Ground (if available)

### 2: Network Configuration

1. By default, the inverter is set to obtain an IP address automatically via DHCP
2. If using a static IP configuration:
   - Access the inverter's web interface
   - Navigate to Network Settings
   - Configure the IP address, subnet mask, and gateway as needed

### 3: Communication Settings

For optimal performance, ensure the following communication parameters:

- Modbus TCP port: 502 (default)
- RS485 baud rate: 9600
- Data bits: 8
- Stop bits: 1
- Parity: None

## Wiring

### Ethernet Connection

- Use CAT5e or CAT6 ethernet cable
- Maximum cable length: 100 meters
- Follow [the guidelines for ethernet wiring](/Controller/wiring-best-practices/#ethernet)

### RS485 Connection

- Use shielded twisted pair cable
- Maximum cable length: 1000 meters
- Connect the shield to ground at one end only
- Maintain proper RS485 bus topology

## eSAJ Home settings

|                                               Step                                                |                                                          Image                                                           |
| :-----------------------------------------------------------------------------------------------: | :----------------------------------------------------------------------------------------------------------------------: |
|                            Open ESAJ Home and connect to the inverter                             |                                                                                                                          |
|                  Select SAJ in battery settings and click Save after the change                   | <img src="/img/customers/saj/Afbeelding4.png" alt="image1" style={{ display: "block", margin: "0 auto", width: "90%"}}/> |
|                       Click initialization and select grid for the country                        | <img src="/img/customers/saj/Afbeelding2.png" alt="image2" style={{ display: "block", margin: "0 auto", width: "90%"}}/> |
| Disable Export limitation (if it is enabled power from the inverter cannot be fed into the grid). | <img src="/img/customers/saj/Afbeelding3.png" alt="image3" style={{ display: "block", margin: "0 auto", width: "90%"}}/> |

## Troubleshooting

Common issues and solutions:

1. No Communication
   - Check physical connections
   - Verify network settings
   - Ensure proper Modbus address configuration

2. Intermittent Connection
   - Check cable quality and connections
   - Verify there's no electromagnetic interference
   - Ensure proper cable routing


# Sav


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';
import ClickableImage from '@/components/ClickableImage'


<img
    src="/img/customers/sav/Logo_Sav.png"
    alt="logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>



## Supported Devices

<DeviceSupportTable
  devices={[
    {
        type: "Storage Elf L1",
        modbusTcp: "❌",
        rs485: "✅",
        curtailment: "❌"
    },
    {
        type: "Efficiency King S2",
        modbusTcp: "⚠️",
        rs485: "❌",
        curtailment: "❌"
    }
  ]}

  showModbusTcp={true}
  showRs485={true}
  showCurtailment={true} showReactivePower={true}
/>

> ⚠️ Testing is ongoing for this device

<ClickableImage src="/img/controller/devices/pv-hybrid-and-battery-inverters/sav/L1-1-.png" alt="SAV Storage Elf L1" maxWidth="100" />



## Configuration

### RS485

For RS485 wiring, follow the [guidelines for RS485 wiring](/Controller/wiring-best-practices/#rs485).

# Schneider SunEzy


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';
import RS485AddressNote from '@site/src/components/RS485AddressNote';

<img
  src="/img/customers/schneider-electric/logo.png"
  alt="Schneider Electric SunEzy"
  style={{ display: "block", margin: "0 auto", width: "40%" }}
/>

# Schneider Electric SunEzy Inverters



---

## Supported Devices

<DeviceSupportTable
  devices={[
    {
      type: "SunEzy 2000 / 2800 / 4000",
      variants: "Single-phase string inverters",
      modbusTcp: "❌",
      rs485: "✅",
      curtailment: "❌",
      manual: "/media/manuals/ITMPV0001A.pdf"
    },
    {
      type: "SunEzy 400E",
      variants: "Transformerless single-phase inverter",
      modbusTcp: "❌",
      rs485: "✅",
      curtailment: "❌",
      manual: "/media/manuals/ITMPV0002A-1.pdf"
    },
    {
      type: "SunEzy 600E",
      variants: "Transformerless inverter, triple MPP input",
      modbusTcp: "❌",
      rs485: "✅",
      curtailment: "❌",
      manual: "/media/manuals/ITMPV0003A.pdf"
    }
  ]}
  showVariants
  showModbusTcp
  showRs485
  showCurtailment
  showManual
  showReactivePower={true}
/>

---

## Wiring


### RS485 Connection

For most SunEzy models (2000 / 2800 / 4000 / 400E / 600E):


<RS485ConnectionTable
  firstColumn={[
    "RS485 A (+)",
    "RS485 B (-)",
    "Shield / GND (optional)"
  ]}
/>



> [!NOTE]
> SunEzy inverters using RS232 (DB9 interface) can be connected via an RS232-to-RS485 converter when required.

---



# Schuco



import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/customers/schuco/logo_schuco.png"
    alt="logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

# Schuco Inverters

## Supported Devices

<DeviceSupportTable
  devices={[
    { type: 'Whitelabeled Kaco inverters from before 2014', modbusTcp: '❌', rs485: '✅', curtailment: "❌" }
  ]}
  showModbusTcp={true}
  showRs485={true}
  showCurtailment={true} showReactivePower={true}
/>

Whitelabeled Kaco inverters from before 2014 are supported for monitoring only.

# SCU


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/customers/scu/Logo_SCU.png"
    alt="logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

# SCU Battery Container

<DeviceSupportTable
  devices={[
    { type: 'BRESS 150/240',     variants: '', modbusTcp: '✅', rs485: '❌', curtailment: "✅" },
    { type: 'Battery container', variants: '', modbusTcp: '✅', rs485: '❌', curtailment: "✅" },
    { type: 'Battery container', variants: '', modbusTcp: '✅', rs485: '❌', curtailment: "✅" },
    { type: 'GRES-300-200',      variants: '', modbusTcp: '✅', rs485: '❌', curtailment: "✅" },
  ]}
  showVariants={true}
  showModbusTcp={true}
  showRs485={true}
  showCurtailment={true} showReactivePower={true}
/>

## Configuration
### SCU Battery Container
In the SCU interface:
1. Go to "Maintenance"
2. Go to "Comm Settings"
3. Go to "PCS"
4. Under "BMS: Number of devices" -> Set this to the amount of batteries / BMS systems that are connected.

### GRES-300-200
The GRES-300-200 is a battery container with its own inverter. The <ControllerName /> connects to it over a single Modbus TCP connection, to the container's industrial PC.

In the SCU interface:
1. Go to "Maintenance" → "Comm Settings" → "PCS"
2. Under **"BMS: Number of devices"**, set the number of battery modules that are connected (up to 10)
3. Set the PCS control mode to **Remote**. In any other mode the <ControllerName /> cannot steer the container, and the device reports "Remote control is not enabled on the GRES-300-200".

When adding the device to the <ControllerName />:
- Choose **SCU Protocol For GRES-300-200**
- Modbus TCP port: `502`
- Modbus address: `1`

Good to know:
- The <ControllerName /> steers the container as one unit, with a single power setpoint. The container divides that power over its battery modules itself. The modules are shown separately in the app, but they cannot be charged or discharged separately.
- PV connected to the container through PDMD modules is not supported.


# Sessy



import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/customers/sessy/sessy.png"
    alt="logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

## Supported Devices

<DeviceSupportTable
  devices={[
    { type: 'Battery', modbusTcp: '✅', rs485: '❌' }
  ]}
  showModbusTcp={true}
  showRs485={true}
  showCurtailment={false} showReactivePower={true}
/>

You'll need to input your Sessy battery dongle username and password when connecting your battery.



# Sigenergy


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/sgo/Logo_Sigenergy.png"
    alt="logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

# Sigenergy Inverters

## Supported Devices

<DeviceSupportTable
  devices={[
    { type: 'SigenStor', variants: '-', modbusTcp: '✅', rs485: '✅', curtailment: "✅" },
    { type: 'PV Max', variants: '-', modbusTcp: '✅', rs485: '✅', curtailment: "✅" },
    { type: 'Hybrid', variants: '-', modbusTcp: '✅', rs485: '✅', curtailment: "✅" }
  ]}
  showVariants={true}
  showModbusTcp={true}
  showRs485={true}
  showCurtailment={true} showReactivePower={true}
/>

## Wiring

The <BrandName /> <ControllerName /> and the Dyness inverters communicate via RS485 or Ethernet.

### Ethernet
For correct ethernet wiring: Follow the [the guidelines for ethernet wiring](/Controller/wiring-best-practices/#ethernet).

### RS485
<RS485ConnectionTable firstColumn={["A", "B", "N/A"]} /> 

## Configuration

Ensure that modbus is enabled:
    1. From the main page go to "Device"
    2. Click "Powerhouse Settings"
    3. Enable "Modbus TCP Server Enable"

<ClickableImage src="/media/sigenergy/sigenergy_modbus.png" alt="Sigenergy Modbus" maxWidth="100%" />

Ensure that the inverter has been set to Remote EMS Mode:
    1. From the main page go to "System"
    2. Click the three dots next to the installation namespace
    3. Click "System Settings"
    4. Click "Operational Mode"
    5. Select "Remote EMS Mode"

<ClickableImage src="/media/sigenergy/sigenergy_mode.png" alt="Sigenergy Mode" maxWidth="100%" />

Disable any grid limits:
    1. From the main page go to "System"
    2. Click the three dots next to the installation namespace
    3. Click "System Settings"
    4. Under "Operational Parameters" disable "Export Limitation" and "Import Limitation"
    5. Set "Grid Connection Point Reserve Power Control Method" to "Power Per Phase"

<ClickableImage src="/media/sigenergy/sigenergy_limits.png" alt="Sigenergy Limits" maxWidth="100%" />

<RS485AddressNote />

# Sinexcel


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/customers/sinexcel/logo.png"
    alt="Logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

# Sinexcel Inverters

> [!WARNING] Sinexcel in combination with a Poweroad BMS
> Starting from <BrandName /> <ControllerName /> software version 1.17.0.x, you must add the Sinexcel inverter and Poweroad BMS as separate devices, and dc-link them through the groups page. For more information, see: [DC-linking inverters, batteries and BMS systems](/Controller/Configuration%20from%20A%20to%20Z/11-Extra-Information/dc-linking/)

## Supported Devices

<DeviceSupportTable
  devices={[
    { type: 'Sinexcel', modbusTcp: '✅', rs485: '❌' , curtailment: "✅"},
    { type: 'Isuna', modbusTcp: '❌', rs485: '✅' , curtailment: "✅"}
  ]}
  showModbusTcp={true}
  showRs485={true}
  showCurtailment={true} showReactivePower={true}
/>

{/* TODO: Confirm the models */}

<ClickableImage src="/img/customers/sinexcel/sinexcel.jpg" alt="Image" maxWidth="450px" />

## Wiring
For correct ethernet wiring: Follow the [the guidelines for ethernet wiring](/Controller/wiring-best-practices/#ethernet).

## Configuration

The external control of the inverter for modbus TCP communication has to be activated in the configuration screen of the inverter.

On the touchscreen of the inverter:
1. Go to the Login/Logout/User tab
2. Use the code "123456" to log in
<ClickableImage src="/img/customers/sinexcel/sinexcel-config_pt1.jpg" alt="Image" maxWidth="450px" />

On the touchscreen of the inverter:
1. Go to the "Ctrl mode" tab
2. Put modus on "Remote control"
> [!TIP]
> In case the mode is already on "Remote control", but the battery does not respond, put the mode first on "Local Manual" and then select again "Remote control" to reactivate the remote control function.
<ClickableImage src="/img/customers/sinexcel/sinexcel-config_pt2.jpg" alt="Image" maxWidth="450px" />

# API


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import ClickableImage from '@site/src/components/ClickableImage';
import YouTubeEmbed from '@site/src/components/YouTubeEmbed';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/customers/sma/logo.png"
    alt="Logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

> [!WARNING]
> - Control of SMA inverters is only available with the cloud <BrandName /> <ControllerName />, not with the physical devices.
> - The SMA API is paid. The API usage fees will be charged through.

## Supported Devices


<DeviceSupportTable
  devices={[
    { type: 'Inverters connected to an SMA Data Manager', api: '✅', modbusTcp: '❌' }
  ]}
  showApi={true}
  showModbusTcp={true}
  showReactivePower={true}
/>

## Configuration

To control the SMA inverters via the API, you must log in locally to the data manager. Follow the steps below to configure the SMA Data Manager for API access.
<br />

### Opening configuration wizard
Click on “Configuration” and then go to the “Grid Management” section. In the grid management section, under the “Actual Power” section, click “Go to Configuration.”
<ClickableImage src="/img/customers/sma/sma-api-config_pt1.png" alt="Image" maxWidth="650px" />

### Wizard step 1
In the wizard in the SMA data manager, no changes have to be made in step 1. Go to step 2.
<ClickableImage src="/img/customers/sma/sma-api-config_pt2.png" alt="Image" maxWidth="650px" />

### Wizard step 2
When doing curtailment, we can differentiate between curtailing to zero production or to zero export.
When choosing for zero production, the inverter will not produce any power at all.
When choosing for zero export, the inverter will produce power, but it will be consumed and nothing will be exported to the grid (best effort).
Select the first option ("Besturing") for zero production. Select the second option ("Regeling") for zero export power:
<ClickableImage src="/img/customers/sma/sma-api-config_pt3a.png" alt="Image" maxWidth="323px" />


Below, you need to click on “Direct Marketing Interface” and then on “SMA Spot”
<ClickableImage src="/img/customers/sma/sma-api-config_pt3.png" alt="Image" maxWidth="650px" />

### Wizard step 3
No changes have to be made in step 3. Go to step 4.

### Wizard step 4
Here you adjust the fallback to the converter power.
I.e., if the internet goes down between the data manager and our server, it will fall back to the preset value within 600 seconds.
<ClickableImage src="/img/customers/sma/sma-api-config_pt4.png" alt="Image" maxWidth="650px" />

# Battery


import { FolderOverview } from '@/components/FolderOverview';

# Battery

<FolderOverview folder="Controller/Devices/PV-hybrid-and-battery-inverters/SMA/Battery" />


# Sunny Boy Storage


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';


<img
    src="/img/customers/sma/logo.png"
    alt="Logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

## Supported Devices

<DeviceSupportTable
  devices = { [
    {
        type: 'Sunny Boy Storage',
        variants: 'SBS 3.7-10',
        modbusTcp: '✅',
        firmwareVersion: '04.07.31.R'
    }, {
        type: 'Sunny Boy Storage',
        variants: 'SBS 5.0-10',
        modbusTcp: '✅',
        firmwareVersion: '04.07.31.R'
    }, {
        type: 'Sunny Boy Storage',
        variants: 'SBS 6.0-10',
        modbusTcp: '✅',
        firmwareVersion: '04.07.31.R'
    }, {
        type: 'Sunny Boy Storage',
        variants: 'SBS 3.8-US-10',
        modbusTcp: '✅',
        firmwareVersion: '04.07.31.R'
    }, {
        type: 'Sunny Boy Storage',
        variants: 'SBS 5.0-US-10',
        modbusTcp: '✅',
        firmwareVersion: '04.07.31.R'
    }, {
        type: 'Sunny Boy Storage',
        variants: 'SBS 6.0-US-10',
        modbusTcp: '✅',
        firmwareVersion: '04.07.31.R'
    }
  ] }
  showModbusTcp = { true }
  showVariants = { true }
  showFirmwareVersion={true}
  showReactivePower={true}
/>

## Wiring
For correct ethernet wiring: Follow the [the guidelines for ethernet wiring](/Controller/wiring-best-practices/#ethernet).

## Configuration
1. Connect with your computer on the same LAN network as the SMA Sunny Boy Storage.
2. In your web browser, surf to the IP address of the device.
3. Log in as "Installer."
<ClickableImage src="/img/customers/sma/sunny-boy-storage-config_pt1.png" alt="Image" maxWidth="650px" />

4. Go to the device parameters tab.
<ClickableImage src="/img/customers/sma/sunny-boy-storage-config_pt2.png" alt="Image" maxWidth="650px" />

5. Click "Edit parameters."
6. Open the "External Communication" dropdown menu → "Modbus" → "TCP server."
7. Set "Activated" to "Yes" and "Port" to "502".
8. At the top of the page, click "Save all."
<ClickableImage src="/img/customers/sma/sunny-boy-storage-config_pt3.png" alt="Image" maxWidth="650px" />
<ClickableImage src="/img/customers/sma/sunny-boy-storage-config_pt4.png" alt="Image" maxWidth="650px" />

## Connection to the Controller

You then need to connect the device to the controller, for that follow this guide : [Adding a device](/Controller/Configuration%20from%20A%20to%20Z/11-Extra-Information/adding-device/).

# Sunny Island


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';


<img
    src="/img/customers/sma/logo.png"
    alt="Logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

## Supported Devices

<DeviceSupportTable
  devices = { [
    {
        type: 'Sunny Island',
        variants: 'SI 3.0M-11',
        modbusTcp: '✅',
        firmwareVersion: '03.41.01.R'
    },{
        type: 'Sunny Island',
        variants: 'SI 4.4M-11',
        modbusTcp: '✅',
        firmwareVersion: '03.41.01.R'
    },{
        type: 'Sunny Island',
        variants: 'SI 6.0H-11',
        modbusTcp: '✅',
        firmwareVersion: '03.41.01.R'
    },{
        type: 'Sunny Island',
        variants: 'SI 8.0H-11',
        modbusTcp: '✅',
        firmwareVersion: '03.41.01.R'
    },{
        type: 'Sunny Island',
        variants: 'SI 4.4M-12',
        modbusTcp: '✅',
        firmwareVersion: '03.41.01.R'
    }, {
        type: 'Sunny Island',
        variants: 'SI 6.0H-12',
        modbusTcp: '✅',
        firmwareVersion: '03.41.01.R'
    }, {
        type: 'Sunny Island',
        variants: 'SI 8.0H-12',
        modbusTcp: '✅',
        firmwareVersion: '03.41.01.R'
    }, {
        type: 'Sunny Island',
        variants: 'SI 4.4M-13',
        modbusTcp: '✅',
        firmwareVersion: '03.41.01.R'
    }, {
        type: 'Sunny Island',
        variants: 'SI 6.0H-13',
        modbusTcp: '✅',
        firmwareVersion: '03.41.01.R'
    }, {
        type: 'Sunny Island',
        variants: 'SI 8.0H-13',
        modbusTcp: '✅',
        firmwareVersion: '03.41.01.R'
    }
  ] }
  showModbusTcp = { true }
  showVariants = { true }
  showFirmwareVersion={true}
  showReactivePower={true}
/>

## Wiring
For correct ethernet wiring: Follow the [the guidelines for ethernet wiring](/Controller/wiring-best-practices/#ethernet).

## Configuration
1. Connect with your computer on the same LAN network as the SMA Sunny Island.
2. In your web browser, surf to the IP address of the device.
3. Log in as "Installer."
<ClickableImage src="/img/customers/sma/sunny-boy-storage-config_pt1.png" alt="Image" maxWidth="650px" />

4. Go to the device parameters tab.
<ClickableImage src="/img/customers/sma/sunny-boy-storage-config_pt2.png" alt="Image" maxWidth="650px" />

5. Click "Edit parameters."
6. Open the "External Communication" dropdown menu → "Modbus" → "TCP server."
7. Set "Activated" to "Yes" and "Port" to "502".
8. At the top of the page, click "Save all."
<ClickableImage src="/img/customers/sma/sunny-boy-storage-config_pt3.png" alt="Image" maxWidth="650px" />
<ClickableImage src="/img/customers/sma/sunny-boy-storage-config_pt4.png" alt="Image" maxWidth="650px" />


# Sunny Island X


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';


<img
    src="/img/customers/sma/logo.png"
    alt="Logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

## Supported Devices

<DeviceSupportTable
  devices = { [
    {
        type: 'Sunny Island X',
        variants: 'Sunny Island X 30 (SI30-20)',
        modbusTcp: '✅',
        firmwareVersion: '03.04.80.R'
    },{
        type: 'Sunny Island X',
        variants: 'Sunny Island X 50 (SI50-20)',
        modbusTcp: '✅',
        firmwareVersion: '03.04.80.R'
    },{
        type: 'Sunny Island X',
        variants: 'Sunny Island X 27 US208 (SI27-US208-20)',
        modbusTcp: '✅',
        firmwareVersion: '03.04.80.R'
    },{
        type: 'Sunny Island X',
        variants: 'Sunny Island X 40 US480 (SI40-US480-20)',
        modbusTcp: '✅',
        firmwareVersion: '03.04.80.R'
    },{
        type: 'Sunny Island X',
        variants: 'Sunny Island X 60 US480 (SI60-US480-20)',
        modbusTcp: '✅',
        firmwareVersion: '03.04.80.R'
    }
  ] }
  showModbusTcp = { true }
  showVariants = { true }
  showFirmwareVersion = { true }
  showReactivePower={true}
/>

## Wiring
For correct ethernet wiring: Follow the [the guidelines for ethernet wiring](/Controller/wiring-best-practices/#ethernet).

## Configuration
1. Connect with your computer on the same LAN network as the SMA Sunny Island X.
2. In your web browser, surf to the IP address of the device.
3. Log in as "Installer."
<ClickableImage src="/img/customers/sma/sunny-boy-storage-config_pt1.png" alt="Image" maxWidth="650px" />

4. Go to the device parameters tab.
<ClickableImage src="/img/customers/sma/sunny-boy-storage-config_pt2.png" alt="Image" maxWidth="650px" />

5. Click "Edit parameters."
6. Open the "External Communication" dropdown menu → "Modbus" → "TCP server."
7. Set "Activated" to "Yes" and "Port" to "502".
8. At the top of the page, click "Save all."
<ClickableImage src="/img/customers/sma/sunny-boy-storage-config_pt3.png" alt="Image" maxWidth="650px" />
<ClickableImage src="/img/customers/sma/sunny-boy-storage-config_pt4.png" alt="Image" maxWidth="650px" />


# Sunny Tripower Storage


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';


<img
    src="/img/customers/sma/logo.png"
    alt="Logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

## Supported Devices

<DeviceSupportTable
  devices = { [
    {
        type: 'Sunny Tripower Storage',
        variants: 'Sunny Tripower Storage 30 (STPS30-20)',
        modbusTcp: '✅',
        firmwareVersion: '03.02.33.R'
    }, {
        type: 'Sunny Tripower Storage',
        variants: 'Sunny Tripower Storage 50 (STPS50-20)',
        modbusTcp: '✅',
        firmwareVersion: '03.02.33.R'
    }, {
        type: 'Sunny Tripower Storage',
        variants: 'Sunny Tripower Storage 27 US208 (STPS27-US-20)',
        modbusTcp: '✅',
        firmwareVersion: '03.02.33.R'
    }, {
        type: 'Sunny Tripower Storage',
        variants: 'Sunny Tripower Storage 40 US480 (STPS40-US-20)',
        modbusTcp: '✅',
        firmwareVersion: '03.02.33.R'
    }, {
        type: 'Sunny Tripower Storage',
        variants: 'Sunny Tripower Storage 60 US480 (STPS60-US-20)',
        modbusTcp: '✅',
        firmwareVersion: '03.02.33.R'
    }
  ] }
  showModbusTcp = { true }
  showVariants = { true }
  showFirmwareVersion={true}
  showReactivePower={true}
/>

## Wiring
For correct ethernet wiring: Follow the [the guidelines for ethernet wiring](/Controller/wiring-best-practices/#ethernet).

## Configuration
1. Connect with your computer on the same LAN network as the SMA Sunny Tripower Storage.
2. In your web browser, surf to the IP address of the device.
3. Log in as "Installer."
<ClickableImage src="/img/customers/sma/sunny-boy-storage-config_pt1.png" alt="Image" maxWidth="650px" />

4. Go to the device parameters tab.
<ClickableImage src="/img/customers/sma/sunny-boy-storage-config_pt2.png" alt="Image" maxWidth="650px" />

5. Click "Edit parameters."
6. Open the "External Communication" dropdown menu → "Modbus" → "TCP server."
7. Set "Activated" to "Yes" and "Port" to "502".
8. At the top of the page, click "Save all."
<ClickableImage src="/img/customers/sma/sunny-boy-storage-config_pt3.png" alt="Image" maxWidth="650px" />
<ClickableImage src="/img/customers/sma/sunny-boy-storage-config_pt4.png" alt="Image" maxWidth="650px" />


# Data Manager M


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';


<img
    src="/img/customers/sma/logo.png"
    alt="Logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

## Supported Devices

<DeviceSupportTable
  devices = { [
    {
        type: 'Data Manager M',
        variants: 'EDMM-10',
        modbusTcp: '✅',
        curtailment: '✅'
    }, {
        type: 'Data Manager M',
        variants: 'EDMM-20',
        modbusTcp: '✅',
        curtailment: '✅'
    }
  ] }
  showCurtailment = { true } showReactivePower={true}
  showVariants = { true }
  showModbusTcp = { true }
/>

## Wiring
For correct ethernet wiring: Follow the [the guidelines for ethernet wiring](/Controller/wiring-best-practices/#ethernet).

## Configuration
The SMA Data Manager M only follows the power limits of the <ControllerName/> when two things are set up on it: the Modbus server, and active power control by Modbus in the grid management services. With only the Modbus server active, the <ControllerName/> can read the data but the Data Manager ignores its limits.

1. Connect with your computer on the same LAN network as the SMA Data Manager M.
2. In your web browser, surf to the IP address of the Data Manager and log in as "Installer."
3. Check that the correct country standard was selected during commissioning.
4. Activate the Modbus server on the Data Manager. Only Modbus TCP works (not UDP).
5. In the "Configuration" menu, open "Grid management services."
6. Click "Configuration and activation" in the "Active power method" row.
7. Select the operating mode "Closed loop" or "Open loop."
8. Select "Modbus" as the signal source.
9. Make the remaining settings as the grid operator specifies, and confirm each step with "Continue."
10. Click "Save."

If active power control by Modbus is not enabled, the "Control" column of the Data Manager on the devices page of the <ControllerName/> turns red with the message "Grid management services are not enabled in the SMA Data Manager, so it ignores our setpoints."


# Hybrid


import { FolderOverview } from '@/components/FolderOverview';

# Hybrid

<FolderOverview folder="Controller/Devices/PV-hybrid-and-battery-inverters/SMA/Hybrid" />


# Sunny Boy Smart Energy


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';


<img
    src="/img/customers/sma/logo.png"
    alt="Logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

## Supported Devices

<DeviceSupportTable
  devices = { [
    {
        type: 'Sunny Boy Smart Energy',
        variants: 'Sunny Boy Smart Energy 3.6 (SBSE3.6-50)',
        modbusTcp: '✅',
        curtailment: '✅',
        firmwareVersion: '03.12.17.R'
    }, {
        type: 'Sunny Boy Smart Energy',
        variants: 'Sunny Boy Smart Energy 4.0 (SBSE4.0-50)',
        modbusTcp: '✅',
        curtailment: '✅',
        firmwareVersion: '03.12.17.R'
    }, {
        type: 'Sunny Boy Smart Energy',
        variants: 'Sunny Boy Smart Energy 5.0 (SBSE5.0-50)',
        modbusTcp: '✅',
        curtailment: '✅',
        firmwareVersion: '03.12.17.R'
    }, {
        type: 'Sunny Boy Smart Energy',
        variants: 'Sunny Boy Smart Energy 6.0 (SBSE6.0-50)',
        modbusTcp: '✅',
        curtailment: '✅',
        firmwareVersion: '03.12.17.R'
    }, {
        type: 'Sunny Boy Smart Energy',
        variants: 'Sunny Boy Smart Energy 3.8 US (SBSE3.8-US-50)',
        modbusTcp: '✅',
        curtailment: '✅',
        firmwareVersion: '03.12.17.R'
    }, {
        type: 'Sunny Boy Smart Energy',
        variants: 'Sunny Boy Smart Energy 4.8 US (SBSE4.8-US-50)',
        modbusTcp: '✅',
        curtailment: '✅',
        firmwareVersion: '03.12.17.R'
    }, {
        type: 'Sunny Boy Smart Energy',
        variants: 'Sunny Boy Smart Energy 5.8 US (SBSE5.8-US-50)',
        modbusTcp: '✅',
        curtailment: '✅',
        firmwareVersion: '03.12.17.R'
    }, {
        type: 'Sunny Boy Smart Energy',
        variants: 'Sunny Boy Smart Energy 7.7 US (SBSE7.7-US-50)',
        modbusTcp: '✅',
        curtailment: '✅',
        firmwareVersion: '03.12.17.R'
    }
  ] }
  showCurtailment = { true } showReactivePower={true}
  showVariants = { true }
  showModbusTcp = { true }
  showFirmwareVersion={true}
/>

## Wiring
For correct ethernet wiring: Follow the [the guidelines for ethernet wiring](/Controller/wiring-best-practices/#ethernet).

## Configuration
1. Connect with your computer on the same LAN network as the SMA Sunny Boy Smart Energy.
2. In your web browser, surf to the IP address of the device.
3. Log in as "Installer."
<ClickableImage src="/img/customers/sma/sunny-boy-storage-config_pt1.png" alt="Image" maxWidth="650px" />

4. Go to the device parameters tab.
<ClickableImage src="/img/customers/sma/sunny-boy-storage-config_pt2.png" alt="Image" maxWidth="650px" />

5. Click "Edit parameters."
6. Open the "External Communication" dropdown menu → "Modbus" → "TCP server."
7. Set "Activated" to "Yes" and "Port" to "502".
8. At the top of the page, click "Save all."
<ClickableImage src="/img/customers/sma/sunny-boy-storage-config_pt3.png" alt="Image" maxWidth="650px" />
<ClickableImage src="/img/customers/sma/sunny-boy-storage-config_pt4.png" alt="Image" maxWidth="650px" />

## Connection to the Controller

You then need to connect the device to the controller, for that follow this guide : [Adding a device](/Controller/Configuration%20from%20A%20to%20Z/11-Extra-Information/adding-device/).


# Sunny Tripower Smart Energy


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';


<img
    src="/img/customers/sma/logo.png"
    alt="Logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

## Supported Devices

<DeviceSupportTable
  devices = { [
    {
        type: 'Sunny Tripower Smart Energy',
        variants: 'Sunny Tripower Smart Energy 5.0 (STP5.0-3SE-40)',
        modbusTcp: '✅',
        curtailment: '✅',
        firmwareVersion: '03.05.26.R'
    }, {
        type: 'Sunny Tripower Smart Energy',
        variants: 'Sunny Tripower Smart Energy 6.0 (STP6.0-3SE-40)',
        modbusTcp: '✅',
        curtailment: '✅',
        firmwareVersion: '03.05.26.R'
    }, {
        type: 'Sunny Tripower Smart Energy',
        variants: 'Sunny Tripower Smart Energy 8.0 (STP8.0-3SE-40)',
        modbusTcp: '✅',
        curtailment: '✅',
        firmwareVersion: '03.05.26.R'
    }, {
        type: 'Sunny Tripower Smart Energy',
        variants: 'Sunny Tripower Smart Energy 10.0 (STP10.0-3SE-40)',
        modbusTcp: '✅',
        curtailment: '✅',
        firmwareVersion: '03.05.26.R'
    }
  ] }
  showCurtailment = { true } showReactivePower={true}
  showVariants = { true }
  showModbusTcp = { true }
  showFirmwareVersion={true}
/>

## Wiring
For correct ethernet wiring: Follow the [the guidelines for ethernet wiring](/Controller/wiring-best-practices/#ethernet).

## Configuration
1. Connect with your computer on the same LAN network as the SMA Sunny Tripower Smart Energy.
2. In your web browser, surf to the IP address of the device.
3. Log in as "Installer."
<ClickableImage src="/img/customers/sma/sunny-boy-storage-config_pt1.png" alt="Image" maxWidth="650px" />

4. Go to the device parameters tab.
<ClickableImage src="/img/customers/sma/sunny-boy-storage-config_pt2.png" alt="Image" maxWidth="650px" />

5. Click "Edit parameters."
6. Open the "External Communication" dropdown menu → "Modbus" → "TCP server."
7. Set "Activated" to "Yes" and "Port" to "502".
8. At the top of the page, click "Save all."
<ClickableImage src="/img/customers/sma/sunny-boy-storage-config_pt3.png" alt="Image" maxWidth="650px" />
<ClickableImage src="/img/customers/sma/sunny-boy-storage-config_pt4.png" alt="Image" maxWidth="650px" />


# Sma


import { FolderOverview } from '@/components/FolderOverview';

# Sma

<FolderOverview folder="Controller/Devices/PV-hybrid-and-battery-inverters/SMA" />


# Solar


import { FolderOverview } from '@/components/FolderOverview';

# Solar

<FolderOverview folder="Controller/Devices/PV-hybrid-and-battery-inverters/SMA/Solar" />


# Sunny Boy


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';


<img
    src="/img/customers/sma/logo.png"
    alt="Logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

## Supported Devices

<DeviceSupportTable
  devices = { [
    {
        type: 'Sunny Boy',
        variants: 'Sunny Boy 1.5 (SB1.5-1VL-40)',
        modbusTcp: '✅',
        curtailment: '✅',
        firmwareVersion: '4.03.07.R'
    }, {
        type: 'Sunny Boy',
        variants: 'Sunny Boy 2.0 (SB2.0-1VL-40)',
        modbusTcp: '✅',
        curtailment: '✅',
        firmwareVersion: '4.03.07.R'
    }, {
        type: 'Sunny Boy',
        variants: 'Sunny Boy 2.5 (SB2.5-1VL-40)',
        modbusTcp: '✅',
        curtailment: '✅',
        firmwareVersion: '4.03.07.R'
    }, {
        type: 'Sunny Boy',
        variants: 'Sunny Boy 3.0 (SB3.0-1AV-40)',
        modbusTcp: '✅',
        curtailment: '✅',
        firmwareVersion: '4.03.07.R'
    }, {
        type: 'Sunny Boy',
        variants: 'Sunny Boy 3.6 (SB3.6-1AV-40)',
        modbusTcp: '✅',
        curtailment: '✅',
        firmwareVersion: '4.03.07.R'
    }, {
        type: 'Sunny Boy',
        variants: 'Sunny Boy 4.0 (SB4.0-1AV-40)',
        modbusTcp: '✅',
        curtailment: '✅',
        firmwareVersion: '4.03.07.R'
    }, {
        type: 'Sunny Boy',
        variants: 'Sunny Boy 5.0 (SB5.0-1AV-40)',
        modbusTcp: '✅',
        curtailment: '✅',
        firmwareVersion: '4.03.07.R'
    }, {
        type: 'Sunny Boy',
        variants: 'Sunny Boy 3.0 (SB3.0-1AV-41)',
        modbusTcp: '✅',
        curtailment: '✅',
        firmwareVersion: '4.03.07.R'
    }, {
        type: 'Sunny Boy',
        variants: 'Sunny Boy 3.6 (SB3.6-1AV-41)',
        modbusTcp: '✅',
        curtailment: '✅',
        firmwareVersion: '4.03.07.R'
    }, {
        type: 'Sunny Boy',
        variants: 'Sunny Boy 4.0 (SB4.0-1AV-41)',
        modbusTcp: '✅',
        curtailment: '✅',
        firmwareVersion: '4.03.07.R'
    }, {
        type: 'Sunny Boy',
        variants: 'Sunny Boy 5.0 (SB5.0-1AV-41)',
        modbusTcp: '✅',
        curtailment: '✅',
        firmwareVersion: '4.03.07.R'
    }, {
        type: 'Sunny Boy',
        variants: 'Sunny Boy 6.0 (SB6.0-1AV-41)',
        modbusTcp: '✅',
        curtailment: '✅',
        firmwareVersion: '4.03.07.R'
    },  {
        type: 'Sunny Boy',
        variants: 'Sunny Boy 3000 TL-21',
        modbusTcp: '✅',
        curtailment: '✅',
        firmwareVersion: '4.03.07.R'
    }, {
        type: 'Sunny Boy',
        variants: 'Sunny Boy 3600 TL-21',
        modbusTcp: '✅',
        curtailment: '✅',
        firmwareVersion: '4.03.07.R'
    }, {
        type: 'Sunny Boy',
        variants: 'Sunny Boy 4000 TL-21',
        modbusTcp: '✅',
        curtailment: '✅',
        firmwareVersion: '4.03.07.R'
    }, {
        type: 'Sunny Boy',
        variants: 'Sunny Boy 5000 TL-21',
        modbusTcp: '✅',
        curtailment: '✅',
        firmwareVersion: '4.03.07.R'
    }
  ] }
  showCurtailment = { true } showReactivePower={true}
  showVariants = { true }
  showModbusTcp = { true }
  showFirmwareVersion = { true }
/>

## Wiring
For correct ethernet wiring: Follow the [the guidelines for ethernet wiring](/Controller/wiring-best-practices/#ethernet).

## Configuration
1. Connect with your computer on the same LAN network as the SMA Sunny Boy.
2. In your web browser, surf to the IP address of the device.
3. Log in as "Installer."
<ClickableImage src="/img/customers/sma/sunny-boy-storage-config_pt1.png" alt="Image" maxWidth="650px" />

4. Go to the device parameters tab.
<ClickableImage src="/img/customers/sma/sunny-boy-storage-config_pt2.png" alt="Image" maxWidth="650px" />

5. Click "Edit parameters."
6. Open the "External Communication" dropdown menu → "Modbus" → "TCP server."
7. Set "Activated" to "Yes" and "Port" to "502".
8. At the top of the page, click "Save all."
<ClickableImage src="/img/customers/sma/sunny-boy-storage-config_pt3.png" alt="Image" maxWidth="650px" />
<ClickableImage src="/img/customers/sma/sunny-boy-storage-config_pt4.png" alt="Image" maxWidth="650px" />

## Connection to the Controller

You then need to connect the device to the controller, for that follow this guide : [Adding a device](/Controller/Configuration%20from%20A%20to%20Z/11-Extra-Information/adding-device/).


# Sunny Tripower


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';


<img
    src="/img/customers/sma/logo.png"
    alt="Logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

## Supported Devices

<DeviceSupportTable
  devices = { [
    {
        type: 'Sunny Tripower',
        variants: 'Sunny Tripower 3.0 (STP3.0-3AV-40)',
        modbusTcp: '✅',
        curtailment: '✅',
        firmwareVersion: '04.03.07.R'
    }, {
        type: 'Sunny Tripower',
        variants: 'Sunny Tripower 4.0 (STP4.0-3AV-40)',
        modbusTcp: '✅',
        curtailment: '✅',
        firmwareVersion: '04.03.07.R'
    }, {
        type: 'Sunny Tripower',
        variants: 'Sunny Tripower 5.0 (STP5.0-3AV-40)',
        modbusTcp: '✅',
        curtailment: '✅',
        firmwareVersion: '04.03.07.R'
    }, {
        type: 'Sunny Tripower',
        variants: 'Sunny Tripower 6.0 (STP6.0-3AV-40)',
        modbusTcp: '✅',
        curtailment: '✅',
        firmwareVersion: '04.03.07.R'
    }, {
        type: 'Sunny Tripower',
        variants: 'Sunny Tripower 8.0 (STP8.0-3AV-40)',
        modbusTcp: '✅',
        curtailment: '✅',
        firmwareVersion: '04.03.07.R'
    }, {
        type: 'Sunny Tripower',
        variants: 'Sunny Tripower 10.0 (STP10.0-3AV-40)',
        modbusTcp: '✅',
        curtailment: '✅',
        firmwareVersion: '04.03.07.R'
    }, {
        type: 'Sunny Tripower X',
        variants: 'Sunny Tripower X 12 (STP12-50)',
        modbusTcp: '✅',
        curtailment: '✅',
        firmwareVersion: '03.14.22.R'
    }, {
        type: 'Sunny Tripower X',
        variants: 'Sunny Tripower X 15 (STP15-50)',
        modbusTcp: '✅',
        curtailment: '✅',
        firmwareVersion: '03.14.22.R'
    }, {
        type: 'Sunny Tripower X',
        variants: 'Sunny Tripower X 20 (STP20-50)',
        modbusTcp: '✅',
        curtailment: '✅',
        firmwareVersion: '03.14.22.R'
    }, {
        type: 'Sunny Tripower X',
        variants: 'Sunny Tripower X 25 (STP X25)',
        modbusTcp: '✅',
        curtailment: '✅',
        firmwareVersion: '03.14.22.R'
    }, {
        type: 'Sunny Tripower TL',
        variants: 'Sunny Tripower 8000 TL-10',
        modbusTcp: '✅',
        curtailment: '✅',
        firmwareVersion: '02.65.02.R'
    }, {
        type: 'Sunny Tripower TL',
        variants: 'Sunny Tripower 10000 TL-10',
        modbusTcp: '✅',
        curtailment: '✅',
        firmwareVersion: '02.65.02.R'
    }, {
        type: 'Sunny Tripower TL',
        variants: 'Sunny Tripower 12000 TL-10',
        modbusTcp: '✅',
        curtailment: '✅',
        firmwareVersion: '02.65.02.R'
    }, {
        type: 'Sunny Tripower TL',
        variants: 'Sunny Tripower 15000 TL-10',
        modbusTcp: '✅',
        curtailment: '✅',
        firmwareVersion: '02.65.02.R'
    }, {
        type: 'Sunny Tripower TL',
        variants: 'Sunny Tripower 17000 TL-10',
        modbusTcp: '✅',
        curtailment: '✅',
        firmwareVersion: '02.65.02.R'
    }, {
        type: 'Sunny Tripower TL',
        variants: 'Sunny Tripower 5000 TL-20',
        modbusTcp: '✅',
        curtailment: '✅',
        firmwareVersion: '02.65.02.R'
    }, {
        type: 'Sunny Tripower TL',
        variants: 'Sunny Tripower 6000 TL-20',
        modbusTcp: '✅',
        curtailment: '✅',
        firmwareVersion: '02.65.02.R'
    }, {
        type: 'Sunny Tripower TL',
        variants: 'Sunny Tripower 7000 TL-20',
        modbusTcp: '✅',
        curtailment: '✅',
        firmwareVersion: '02.65.02.R'
    }, {
        type: 'Sunny Tripower TL',
        variants: 'Sunny Tripower 8000 TL-20',
        modbusTcp: '✅',
        curtailment: '✅',
        firmwareVersion: '02.65.02.R'
    }, {
        type: 'Sunny Tripower TL',
        variants: 'Sunny Tripower 9000 TL-20',
        modbusTcp: '✅',
        curtailment: '✅',
        firmwareVersion: '02.65.02.R'
    }, {
        type: 'Sunny Tripower TL',
        variants: 'Sunny Tripower 10000 TL-20',
        modbusTcp: '✅',
        curtailment: '✅',
        firmwareVersion: '02.65.02.R'
    }, {
        type: 'Sunny Tripower TL',
        variants: 'Sunny Tripower 11000 TL-20',
        modbusTcp: '✅',
        curtailment: '✅',
        firmwareVersion: '02.65.02.R'
    }, {
        type: 'Sunny Tripower TL',
        variants: 'Sunny Tripower 12000 TL-20',
        modbusTcp: '✅',
        curtailment: '✅',
        firmwareVersion: '02.65.02.R'
    }, {
        type: 'Sunny Tripower TL',
        variants: 'Sunny Tripower 15000 TL-30',
        modbusTcp: '✅',
        curtailment: '✅',
        firmwareVersion: '02.90.01.R'
    }, {
        type: 'Sunny Tripower TL',
        variants: 'Sunny Tripower 17000 TL-30',
        modbusTcp: '✅',
        curtailment: '✅',
        firmwareVersion: '02.90.01.R'
    }, {
        type: 'Sunny Tripower TL',
        variants: 'Sunny Tripower 20000 TL-30',
        modbusTcp: '✅',
        curtailment: '✅',
        firmwareVersion: '02.90.01.R'
    }, {
        type: 'Sunny Tripower TL',
        variants: 'Sunny Tripower 25000 TL-30',
        modbusTcp: '✅',
        curtailment: '✅',
        firmwareVersion: '02.90.01.R'
    },{
        type: 'Sunny Tripower TLEE',
        variants: 'Sunny Tripower 10000 TLEE-10',
        modbusTcp: '✅',
        curtailment: '✅',
        firmwareVersion: '02.50.87.R'
    }, {
        type: 'Sunny Tripower TLEE',
        variants: 'Sunny Tripower 15000 TLEE-10',
        modbusTcp: '✅',
        curtailment: '✅',
        firmwareVersion: '02.50.87.R'
    },{
        type: 'Sunny Tripower TLEE',
        variants: 'Sunny Tripower 20000 TLEE-10',
        modbusTcp: '✅',
        curtailment: '✅',
        firmwareVersion: '02.50.87.R'
    },{
        type: 'Sunny Tripower Core 1',
        variants: 'Sunny Tripower 50-40',
        modbusTcp: '✅',
        curtailment: '✅',
        firmwareVersion: '4.01.05.R'
    }, {
        type: 'Sunny Tripower Core 1',
        variants: 'Sunny Tripower 50-41',
        modbusTcp: '✅',
        curtailment: '✅',
        firmwareVersion: '4.01.05.R'
    }, {
        type: 'Sunny Tripower Core 2',
        variants: 'Sunny Tripower 110-60',
        modbusTcp: '✅',
        curtailment: '✅',
        firmwareVersion: '1.01.04.R'
    }
  ] }
  showCurtailment = { true } showReactivePower={true}
  showVariants = { true }
  showModbusTcp = { true }
  showFirmwareVersion = { true }
/>

## Wiring
For correct ethernet wiring: Follow the [the guidelines for ethernet wiring](/Controller/wiring-best-practices/#ethernet).

## Configuration
1. Connect with your computer on the same LAN network as the SMA Sunny Tripower.
2. In your web browser, surf to the IP address of the device.
3. Log in as "Installer."
<ClickableImage src="/img/customers/sma/sunny-boy-storage-config_pt1.png" alt="Image" maxWidth="650px" />

4. Go to the device parameters tab.
<ClickableImage src="/img/customers/sma/sunny-boy-storage-config_pt2.png" alt="Image" maxWidth="650px" />

5. Click "Edit parameters."
6. Open the "External Communication" dropdown menu → "Modbus" → "TCP server."
7. Set "Activated" to "Yes" and "Port" to "502".
8. At the top of the page, click "Save all."
<ClickableImage src="/img/customers/sma/sunny-boy-storage-config_pt3.png" alt="Image" maxWidth="650px" />
<ClickableImage src="/img/customers/sma/sunny-boy-storage-config_pt4.png" alt="Image" maxWidth="650px" />


# Socomec


import { BrandName, ControllerName } from '@site/src/components/customFields';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
src="/img/customers/Socomec/logo.png"
alt="logo"
style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

## Supported Devices

<DeviceSupportTable
  devices={[
    {
      type: 'Energy Storage',
      variants: 'HES L IEC',
      modbusTcp: '✅',
      rs485: '❌',
    }, {
        type: 'Energy Storage',
        variants: 'HES L SKID',
        modbusTcp: '✅',
        rs485: '❌',
    }, {
        type: 'Energy Storage',
        variants: 'HES XXL IEC',
        modbusTcp: '✅',
        rs485: '❌',
    }, {
        type: 'Energy Storage',
        variants: 'HES XXL SKID',
        modbusTcp: '✅',
        rs485: '❌',
    }
  ]}
  showVariants = { true }
  showModbusTcp = { true }
  showRs485 = { true }
  showReactivePower={true}
/>

## Wiring

### Ethernet
For correct ethernet wiring: Follow the [the guidelines for ethernet wiring](/Controller/wiring-best-practices/#ethernet).


# HYD 3000…6000-ES


{/* TODO: It looks like this is valid for more inverters? */}

import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/customers/sofar/sofar-logo.png"
    alt="logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

# Sofar HYD 3000…6000-ES Inverters

## Supported Devices

<ClickableImage src="/img/customers/sofar/hyd3000.png" alt="Image" maxWidth="450px" />


<DeviceSupportTable
  devices={[
    { type: 'Sofar HYD 3000…6000-ES', modbusTcp: '✅ (Solarman WiFi & ethernet dongles)', rs485: '✅', curtailment: "❌" }
  ]}
  showModbusTcp={true}
  showRs485={true}
    showCurtailment={true} showReactivePower={true}
/>

> [!WARNING]
> - It is recommended to use RS485, as the Solarman dongle may change firmware and lock Modbus TCP access!
> - If you use a Solarman dongle, then it is recommended to use the ethernet dongle for connection stability.

## Wiring

### Ethernet
For correct ethernet wiring: Follow the [the guidelines for ethernet wiring](/Controller/wiring-best-practices/#ethernet).

Connect the inverter to your internet network using the "Solarman dongle".
1. Install the WiFi or Ethernet dongle into the inverter and make sure it is connected to your network.
2. Write down the serial number of the dongle (see the picture on the left/above). You will need this when setting up communication with the controller.

> [!NOTE] Dongle firmware
> WiFi dongle firmware LSW3_15_FFFF_1.0.65 and ethernet dongle firmware ME_08_2701_2.06 have been tested. In case of problems you can try to put these specific firmware versions on the dongle. Please contact the supplier of your dongle for this.
<ClickableImage src="/img/customers/sofar/solarman-dongle.jpg" alt="Image" maxWidth="450px" />


### RS485
<RS485ConnectionTable firstColumn={["RS485s TX+", "RS485s TX-", "N/A"]} />
<ClickableImage src="/img/customers/sofar/hyd3000-wiring.png" alt="Image" maxWidth="450px" />

## Configuration

### Activating external battery control
External battery control must be activated in the inverter configuration menu via the LCD display. In the inverter settings:
1. Go to "Basic settings".
2. Go to "Energy Storage Mode"
3. Set this to “Set Passive Mode”
4. For more information, see the Sofar HYD 3000/4000/5000/6000-ES Owner's Manual page 26 and following.

### RS485
<RS485AddressNote />

External inverter control must be activated in the configuration menu of the inverter via the LCD screen.
1. Click shortly on the button down.
2. You'll see "1. Enter settings", press button down for 2 seconds to enter the settings.
3. Go through the settings until you see:
    - Modbus Address or
    - Set ComProtocol
4. Press button down for 2 seconds to set the address.
5. Set the Address to the wanted value.


# Sofar


import { FolderOverview } from '@/components/FolderOverview';

# Sofar

<FolderOverview folder="Controller/Devices/PV-hybrid-and-battery-inverters/Sofar/sofar-string-inverter" title="String inverter" />



<FolderOverview folder="Controller/Devices/PV-hybrid-and-battery-inverters/Sofar/sofar-hybride-inverter" title="Hybride inverter" />

# PowerMagic


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/customers/sofar/sofar-logo.png"
    alt="logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

# Sofar C&I ESS - PowerMagic

## Supported Devices

<ClickableImage src="/img/customers/sofar/powermagic/1.png" alt="Image" maxWidth="450px" />


<DeviceSupportTable
  devices={[
    { type: 'PowerMagic 400V C&I', manual: '/img/customers/sofar/powermagic/manual.pdf',  modbusTcp: '✅', rs485: '❌'}
  ]}
  showModbusTcp={true}
  showRs485={true}
  showManual={true}
  showReactivePower={true}
/>

> [!WARNING] My Sofar PowerMagic shows a warning "Status unknown"?
> <ClickableImage src="/img/customers/sofar/powermagic/3.png" alt="Image" maxWidth="650px" />
> This is a known issue with some Sofar PowerMagic inverters. It does not affect the functionality of the inverter, and can be ignored.
> A future update from Sofar should resolve this issue.
>
> __Why does this happen?__ The <BrandName /> <ControllerName /> reads the status of the inverter via Modbus TCP. The PowerMagic
> responds a code between 0 and 4 that indicates the status of the inverter. However, in some cases the PowerMagic responds with a code 5, which is not recognized by the <BrandName /> <ControllerName /> and therefore shows "Status unknown".

## Wiring

### Ethernet

Through an ethernet cable, one end is connected to the WEB port on the
BESS door board, and the other end is connected to the internet. A communication connection will be established between the BESS and the
local network.

The system is powered up (see the power-on step for details) to ensure that the
auxiliary power supply of the BESS is working properly (the 'power' indicator light on the door panel can be observed, and if the indicator light is on, it
indicates that the auxiliary power supply is working properly). After waiting for
about 1 minute:

- If the network port on your network switch indicator light flashes, it indicates that the
communication between BESS and network has been established .
- If the indicator light is not on, check the network connection

The login interface of the BESS can be entered through a browser on a computer or mobile. By default, this is http://192.168.1.100.
The initial user account is “user”. For the initial password of the user, please
contact the Sofar customer service staff
<ClickableImage src="/img/customers/sofar/powermagic/2.png" alt="Image" maxWidth="550px" />
When you can reach the login interface of the BESS, it indicates that the communication between the BESS and the network has been established.

For more tips on ethernet wiring: Follow [the guidelines for ethernet wiring](/Controller/wiring-best-practices/#ethernet).

## Configuration
Check if the PowerMagic is online and if there are no errors. This can be done in the web interface of the PowerMagic, by looking on the topology diagram:
<ClickableImage src="/img/customers/sofar/powermagic/4.png" alt="Image" maxWidth="550px" />


Modbus is enabled by default on the PowerMagic. The default Modbus TCP port is 502 and the default Modbus slave ID is 1.
When adding the device on the <BrandName /> <ControllerName />, it will automatically scan for Sofar PowerMagic devices with the default settings.

## A note on response times in standby mode
The Sofar PowerMagic has a 'Standby Mode' that it enters after a period of inactivity.
We notice when sending a (dis)charge command, the PowerMagic may take up to 2 minutes to respond while in standby mode.
Once the PowerMagic is active again, it leaves the standby mode and the response time is back to normal (1 second).


# Sofar - String inverter


import { FolderOverview } from '@/components/FolderOverview'

# Sofar - String inverter

<FolderOverview folder="https://docs.eniris.com/en/Controller/Devices/PV-hybrid-and-battery-inverters/Sofar/sofar-string-inverter" />

# TL-G3 and TLM/X-G3 Series


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

This guide covers the listed TL-G3, TLM and TLX families. Connector layouts and communication options can differ between model revisions, so verify the exact model label before wiring.

<img
    src="/img/customers/sofar/sofar-logo.png"
    alt="logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

# Sofar TL-G3 and TLM/X-G3 Series Inverters

## Supported Devices



<DeviceSupportTable
  devices={[
  { type: '1100-3300TL-G3' },
  { type: '3000-7500TLM' },
  { type: '10000-40000TL' },
  { type: '5000-80000TLX-G3' },
  { type: '100000-125000TLX-G4' },
  { type: '7000-10500TLM-G3' },
]}
  showReactivePower={true}
/>

> [!WARNING]
> - Most of the devices can communicate using modbus TCP. This is not valid for the series "SOFAR 1...40KTL"
> - Some inverters require specific firmware that is limited to certain distributors. Consult your distributor in case of doubt.

<ClickableImage src="/img/customers/sofar/tl3.png" alt="Image" maxWidth="450px" />

## Wiring

### Ethernet
Connect the inverter to your internet network using the "SOFAR SOLAR ETHERNET STICK LSE3".

For correct ethernet wiring: Follow the [the guidelines for ethernet wiring](/Controller/wiring-best-practices/#ethernet).

### RS485

#### ...TL-G3 & G1 & G2 
<RS485ConnectionTable firstColumn={["RS485s TR+", "RS485s TR-", "N/A"]} />
<ClickableImage src="/img/customers/sofar/tl-g3-wiring.png" alt="Image" maxWidth="450px" />

#### ...TLX & TLM
<RS485ConnectionTable firstColumn={["RS485s TR+ (pin 1)", "RS485s TR- (pin 3)", "N/A"]} />
<ClickableImage src="/img/customers/sofar/tlxg3-tlmg3-wiring.png" alt="Image" maxWidth="450px" />

## Configuration

### RS485
<RS485AddressNote />

External inverter control must be activated in the configuration menu of the inverter via the LCD screen.
1. Click shortly on the button down.
2. You'll see "1. Enter settings", press button down for 2 seconds to enter the settings.
3. Go through the settings until you see:
    - Modbus Address or
    - Set ComProtocol
4. Press button down for 2 seconds to set the address.
5. Set the Address to the wanted value.


# API


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';
import DownloadButton from '@site/src/components/DownloadButton';

> [!TIP]
> See [SolarEdge Cloud API](/Devices/Cloud/SolarEdge/) for more information.

> [!WARNING]
> The API is only aviable for Cloud controllers.

# Solaredge


import { FolderOverview } from '@/components/FolderOverview';

# Solaredge

<FolderOverview folder="Controller/Devices/PV-hybrid-and-battery-inverters/SolarEdge" />


# SE3.5K - SE33.3K Series


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/customers/solaredge/logo.png"
    alt="logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

# SolarEdge SE3.5K - 33.3K inverters

## Supported Devices

<ClickableImage src="/img/customers/solaredge/SE33_3K.png" alt="Image" maxWidth="450px" />


<DeviceSupportTable
  devices={[
    { type: 'SolarEdge SE3.5K - SE33.3K', modbusTcp: '✅', rs485: '❌', curtailment: "🔶 (see warning below)", firmwareVersion: "v3.0  (Tip: if the SolarEdge SetApp works, the firmware will be recent enough)" }
  ]}
  showModbusTcp={true}
  showRs485={true}
  showCurtailment={true} showReactivePower={true}
  showFirmwareVersion={true}
/>

> [!WARNING] CURTAILMENT IS ONLY SUPPORTED AFTER OBTAINING AN AGREEMENT WITH SOLAREDGE
> If curtailment is not working on your SolarEdge device, it is probably not enabled by SolarEdge.
> Reach out to SolarEdge to enable control of your devices.
> [!WARNING] SolarEdge refuses to help customers with curtailment!

## Wiring
For correct ethernet wiring: Follow the [the guidelines for ethernet wiring](/Controller/wiring-best-practices/#ethernet).

> [!WARNING] MULTIPLE SOLAR EDGE DEVICES IN A CHAIN
> Although it is theoretically possible to read out multiple SolarEdge linked via RS485 over Modbus TCP in a master-slave configuration, in practice this communication is NOT reliable.
>
> You MUST connect each inverter individually via Modbus TCP!

## Activating Modbus TCP communication

### Via the SolarEdge SetApp (may require credentials)
1. Connect the inverter to the same LAN network as the controller and make sure it is on.
2. Download the SolarEdge SetApp: https://www.solaredge.com/nl/producten/software/setapp
3. Open the SolarEdge SetApp and connect to the inverter. The app will help you do this.
4. In the app, once connected to the inverter, go to the "Communication" -> "Modbus TCP" -> "Enable" menu and enable Modbus TCP.
5. The Modbus TCP port is set to 1502 by default. Please leave it as is, and if it is set to another port, change it to port 1502. You can also use port 502 if necessary, but you will need to select the protocol for port 502 later when adding on the controller.

### Via the inverter's Web interface via the inverter's WiFi access point (no credentials required)
1. Activate the inverter's WiFi access point by switching the red toggle switch at the bottom of the inverter to the "P" position for less than 5 seconds.
<ClickableImage src="/img/customers/solaredge/SE33_3K-wifi-switch.png" alt="Image" maxWidth="450px" />

2. Connect to the WiFi access point with a smartphone or computer. The WiFi password is on the label on the inverter
<ClickableImage src="/img/customers/solaredge/SE33_3K-wifi-connection.jpg" alt="Image" maxWidth="450px" />

3. In a Web browser, surf to http://172.16.0.1
4. Go to "Site communication" -> "Modbus TCP port" -> "Modbus TCP" and set it to "Enabled".
5. The Modbus TCP port is set to 1502 by default. Please leave it as is, and if it is set to another port, change it to port 1502. You can also use port 502 if necessary, but you will need to select the protocol for port 502 later when adding on the controller.
<ClickableImage src="/img/customers/solaredge/SE33_3K-wifi-local-interface.png" alt="Image" maxWidth="650px" />



# SE50K - SE120K Synergy Series


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/customers/solaredge/logo.png"
    alt="logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

# SolarEdge SE50K - SE120K Synergy inverters

## Supported Devices

<DeviceSupportTable
  devices={[
    { type: 'SolarEdge SE50K - SE120K Synergy', modbusTcp: '✅', rs485: '❌', curtailment: "🔶 (see warning below)", firmwareVersion: "v3.0  (Tip: if the SolarEdge SetApp works, the firmware will be recent enough)" }
  ]}
  showModbusTcp={true}
  showRs485={true}
  showCurtailment={true} showReactivePower={true}
  showFirmwareVersion={true}
/>

> [!WARNING] CURTAILMENT IS ONLY SUPPORTED AFTER OBTAINING AN AGREEMENT WITH SOLAREDGE
> If curtailment is not working on your SolarEdge device, it is probably not enabled by SolarEdge.
> Reach out to SolarEdge to enable control of your devices.
> [!WARNING] SolarEdge refuses to help customers with curtailment!

## Wiring
For correct ethernet wiring: Follow the [the guidelines for ethernet wiring](/Controller/wiring-best-practices/#ethernet).

> [!WARNING] MULTIPLE SOLAR EDGE DEVICES IN A CHAIN
> Although it is theoretically possible to read out multiple SolarEdge linked via RS485 over Modbus TCP in a master-slave configuration, in practice this communication is NOT reliable.
>
> You MUST connect each inverter individually via Modbus TCP!

## Activating Modbus TCP communication

### Via the SolarEdge SetApp (may require credentials)
1. Connect the inverter to the same LAN network as the controller and make sure it is on.
2. Download the SolarEdge SetApp: https://www.solaredge.com/nl/producten/software/setapp
3. Open the SolarEdge SetApp and connect to the inverter. The app will help you do this.
4. In the app, once connected to the inverter, go to the "Communication" -> "Modbus TCP" -> "Enable" menu and enable Modbus TCP.
5. The Modbus TCP port is set to 1502 by default. Please leave it as is, and if it is set to another port, change it to port 1502. You can also use port 502 if necessary, but you will need to select the protocol for port 502 later when adding on the controller.

### Via the inverter's Web interface via the inverter's WiFi access point (no credentials required)
1. Activate the inverter's WiFi access point by switching the red toggle switch at the bottom of the inverter to the "P" position for less than 5 seconds.
<ClickableImage src="/img/customers/solaredge/SE33_3K-wifi-switch.png" alt="Image" maxWidth="450px" />

2. Connect to the WiFi access point with a smartphone or computer. The WiFi password is on the label on the inverter
<ClickableImage src="/img/customers/solaredge/SE33_3K-wifi-connection.jpg" alt="Image" maxWidth="450px" />

3. In a Web browser, surf to http://172.16.0.1
4. Go to "Site communication" -> "Modbus TCP port" -> "Modbus TCP" and set it to "Enabled".
5. The Modbus TCP port is set to 1502 by default. Please leave it as is, and if it is set to another port, change it to port 1502. You can also use port 502 if necessary, but you will need to select the protocol for port 502 later when adding on the controller.
<ClickableImage src="/img/customers/solaredge/SE33_3K-wifi-local-interface.png" alt="Image" maxWidth="650px" />


# SE2200H - SE6000H


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/customers/solaredge/logo.png"
    alt="logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

# SolarEdge SE2200H - SE6000H inverters

## Supported Devices

<ClickableImage src="/img/customers/solaredge/SE2200H.png" alt="Image" maxWidth="450px" />

<DeviceSupportTable
  devices={[
    { type: 'SolarEdge SE2200H', modbusTcp: '✅', rs485: '✅', curtailment: "🔶 (see warning below)", firmwareVersion: "v3.0  (Tip: if the SolarEdge SetApp works, the firmware will be recent enough)"},
    { type: 'SolarEdge SE3000H', modbusTcp: '✅', rs485: '✅', curtailment: "🔶 (see warning below)", firmwareVersion: "v3.0  (Tip: if the SolarEdge SetApp works, the firmware will be recent enough)" },
    { type: 'SolarEdge SE3500H', modbusTcp: '✅', rs485: '✅', curtailment: "🔶 (see warning below)", firmwareVersion: "v3.0  (Tip: if the SolarEdge SetApp works, the firmware will be recent enough)" },
    { type: 'SolarEdge SE3680H', modbusTcp: '✅', rs485: '✅', curtailment: "🔶 (see warning below)", firmwareVersion: "v3.0  (Tip: if the SolarEdge SetApp works, the firmware will be recent enough)" },
    { type: 'SolarEdge SE4000H', modbusTcp: '✅', rs485: '✅', curtailment: "🔶 (see warning below)", firmwareVersion: "v3.0  (Tip: if the SolarEdge SetApp works, the firmware will be recent enough)" },
    { type: 'SolarEdge SE5000H', modbusTcp: '✅', rs485: '✅', curtailment: "🔶 (see warning below)", firmwareVersion: "v3.0  (Tip: if the SolarEdge SetApp works, the firmware will be recent enough)" },
    { type: 'SolarEdge SE6000H', modbusTcp: '✅', rs485: '✅', curtailment: "🔶 (see warning below)", firmwareVersion: "v3.0  (Tip: if the SolarEdge SetApp works, the firmware will be recent enough)" }
  ]}
  showModbusTcp={true}
  showRs485={true}
  showCurtailment={true} showReactivePower={true}
  showFirmwareVersion={true}
/>

> [!WARNING] 
> ### CURTAILMENT IS ONLY SUPPORTED AFTER OBTAINING AN AGREEMENT WITH SOLAREDGE
> If curtailment is not working on your SolarEdge device, it is probably not enabled by SolarEdge.
> Reach out to SolarEdge to enable control of your devices.
> [!WARNING] SolarEdge refuses to help customers with curtailment!

## Wiring
For correct ethernet wiring: Follow the [the guidelines for ethernet wiring](/Controller/wiring-best-practices/#ethernet).

## Configuration

### Activating Modbus TCP communication
In the menu, navigate to "Communication" -> "LAN Conf" -> "Modbus TCP", and activate Modbus TCP.

When Modbus TCP is activated, the following status screen will be displayed:

Modbus TCP: &lt;status&gt;

IP:192.168.1.210

Port:502


# Solarlog


import { BrandName, ControllerName } from '@site/src/components/customFields';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';
import ClickableImage from '@site/src/components/ClickableImage';


<img
  src="/img/sgo/Logo_Solarlog.png"
  alt="Solar-Log"
  style={{ display: "block", margin: "0 auto", width: "40%" }}
/>

## Supported Devices

<DeviceSupportTable
  devices={[
    { type: 'Solar-Log 400e Gateway', modbusTcp: '✅', rs485: '❌', curtailment: "❌"},
  ]}
  showModbusTcp
  showRs485
  showReactivePower={true}
/>


---

## Configuration steps

> **Prerequisite:** the **Solar-Log 400e** is powered and connected to the local
> network via Ethernet (DHCP by default).

1. **Find the IP address**  
   Use your router’s DHCP list or a network scanner to locate the
   *Solar-Log 400e* on port **80**.

2. **Verify local API**  
   Open `http://<IP-address>/pc.js?min0` in a browser.  
   A plain-text JavaScript file should appear – this means the local API is
   enabled.

3. **Add the device in <BrandName/>**  
   - Go to **Integrations → Add device**.  
   - Choose **Solar-Log Gateway Local API**.  
   - Enter the IP address, keep the default port **80** and confirm.  
   - The gateway and its attached inverters will be detected automatically.

4. **(Optional) Static IP**  
   For stable operation, reserve the IP in your DHCP server or configure a
   static address in the Solar-Log web UI (**Settings → Network**).

---

## Metrics exposed

| Key                         | Description                                 | Unit |
| --------------------------- | ------------------------------------------- | ---- |
| `actualPowerTot_W`          | Instantaneous AC power of the PV plant      | W    |
| `producedEnergyDeltaTot_Wh` | Energy produced since previous read-out¹    | Wh   |
| `importedEnergyDeltaTot_Wh` | Imported energy (if the gateway measures it)| Wh   |
| `exportedEnergyDeltaTot_Wh` | Exported energy (feed-in)                   | Wh   |

¹ The driver integrates `actualPowerTot_W` over time when absolute kWh
counters are not available.

---

## Troubleshooting

* **No data / status 302** – check that `/pc.js?min0` returns HTTP 200 and
  contains the variables `Serialnr`, `Pac`, `SLTyp`, `WRTyp`.  
  A redirect or login page indicates the local API is disabled.

* **Power always zero** – firmware **< 2.1** may report `Pac=0`.  
  Update to a recent firmware from the Solar-Log support portal.

* **Multiple gateways** – be sure each Solar-Log has a unique hostname
  or static IP to avoid discovery conflicts.

---

### Useful resources

* **Solar-Log knowledge-base** –  
  [https://www.solar-log.com/en/support/faq]
* Modbus/TCP documentation – available in the “Downloads” section of the
  Solar-Log portal.


# SolarMax


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/customers/solarmax/logo.png"
    alt="SolarMax"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

# SolarMax Inverters

## Supported Devices

<DeviceSupportTable
  devices={[
    {
      type: "SolarMax",
      variants: "Inverters that support the SolarMax protocol",
      modbusTcp: "❌",
      rs485: "✅",
      curtailment: "❌"
    },
  ]}
  showVariants={true}
  showModbusTcp={true}
  showRs485={true}
  showCurtailment={true} showReactivePower={true}
/>

> [!WARNING]
> All SolarMax inverters that support the SolarMax protocol can be added. The SolarMax protocol does not allow curtailment. 

# Solarwatt


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/customers/solarwatt/logo.png"
    alt="logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

## Supported Devices

<DeviceSupportTable
  devices={[
    {  
      type: "Vision One",
      modbusTcp: "✅",
      rs485: "✅",
      curtailment: "⌛ (in development)",
      firmwareVersion: "Master: 1.62, Manager: 1.34 (*)"
    },
    {
      type: "Vision Three",
      modbusTcp: "✅",
      rs485: "✅",
      curtailment: "⌛ (in development)",
      firmwareVersion: "Master: 1.62, Manager: 1.34 (*)"
    }
  ]}
  showModbusTcp={true}
  showRs485={true}
  showCurtailment={true} showReactivePower={true}
  showFirmwareVersion={true}
/>


> [!NOTE] Supported Firmware versions
> (*) The integration may work for older firmware versions, but these are not tested.


## Wiring

### Ethernet
For correct ethernet wiring: Follow the [the guidelines for ethernet wiring](/Controller/wiring-best-practices/#ethernet).

> [!WARNING]
> You cannot connect it through the WiFi dongle.

### RS485
<RS485ConnectionTable firstColumn={["EMS 485A / pin 17", "EMS 485B / pin 18", "N/A"]} />
<ClickableImage src="/img/customers/foxess/h3-pro-cables.png" alt="Image 1" maxWidth="450px" />

# Solax


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';
import ApacheLicense from '@site/src/components/ApacheLicense';


<img
    src="/img/customers/solax/g4.jpg"
    alt="logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>


## Supported Devices


<DeviceSupportTable
  showModbusTcp showRs485 showCurtailment showFirmwareVersion
  devices={ [
    {
      type: 'Solax X1 Hybrid G4',
      modbusTcp: '✅',
      rs485: '✅',
      curtailment: '✅',
      instructionVideos: [{"videoId": "t0FXx2YI6BA", "title": "SolaX X1-Hybrid G4", "description": "Models: X1-Hybrid-3.0-D, X1-Hybrid-3.7-D, X1-Hybrid-5.0-D, X1-Hybrid-5.0K-D, X1-Hybrid-6.0-D, X1-Hybrid-7.5-D."}]
    }, {
      type: 'Solax X3 Hybrid G4',
      modbusTcp: '✅',
      rs485: '✅',
      curtailment: '✅',
      instructionVideos: [{"videoId": "9jnD8RJGM54", "title": "SolaX X3-Hybrid G4", "description": "Models: X3-Hybrid-5.0-D, X3-Hybrid-6.0-D, X3-Hybrid-8.0-D, X3-Hybrid-10.0-D, X3-Hybrid-10.0K-D, X3-Hybrid-12.0-D, X3-Hybrid-12.0K-D, X3-Hybrid-15.0-D."}]
    }, {
      type: 'Solax X3 Ultra',
      modbusTcp: '✅',
      rs485: '✅',
      curtailment: '✅',
      firmwareVersion: `ARM 026.01-000.09 | DSP 025.04 | Module 1.007.02`,
      instructionVideos: [{"videoId": "n0_FBR4Urd8", "title": "SolaX X3-Ultra / Ultra GLV", "description": "Models: X3-ULT-15KP, X3-ULT-15K, X3-ULT-19.9K, X3-ULT-20K, X3-ULT-20KP, X3-ULT-25K, X3-ULT-25KW, X3-ULT-30K, X3-ULT-10K-GLV, X3-ULT-15K-GLV."}]
    }, {
      type: 'Solax X3 Ultra GLV',
      modbusTcp: '✅',
      rs485: '✅',
      curtailment: '✅',
      instructionVideos: [{"videoId": "n0_FBR4Urd8", "title": "SolaX X3-Ultra / Ultra GLV", "description": "Models: X3-ULT-15KP, X3-ULT-15K, X3-ULT-19.9K, X3-ULT-20K, X3-ULT-20KP, X3-ULT-25K, X3-ULT-25KW, X3-ULT-30K, X3-ULT-10K-GLV, X3-ULT-15K-GLV."}]
    }, {
      type: 'Solax X1 IES',
      modbusTcp: '✅',
      rs485: '✅',
      curtailment: '✅',
      instructionVideos: [{"videoId": "h6_em8Ak_-w", "title": "SolaX X1-IES", "description": "Models: X1-IES-2.5K, X1-IES-3K, X1-IES-3.7K, X1-IES-4.6K, X1-IES-5K, X1-IES-6K, X1-IES-8K."}]
    }, {
      type: 'Solax X3 IES',
      modbusTcp: '✅',
      rs485: '✅',
      curtailment:'✅',
      instructionVideos: [{"videoId": "U-2vosReHFs", "title": "SolaX X3-IES", "description": "Models: X3-IES-4K, X3-IES-5K, X3-IES-6K, X3-IES-8K, X3-IES-10K, X3-IES-12K, X3-IES-15K."}]
    }, {
      type: 'Solax ESS-TRENE',
      modbusTcp: '✅',
      rs485: '✅',
      curtailment: '❌'
    }, {
      type: 'Solax ESS-AELIO',
      modbusTcp: '✅',
      rs485: '✅',
      curtailment: '❌'
    }, {
      type: 'EMS 1000',
      modbusTcp: '✅',
      rs485: '✅',
      curtailment: '❌'
    }
  ] }
  showReactivePower={true}
/>

## Installation

> [!NOTE]
> For the Solax X3 Hybrid G4 please make sure that the inverter has the latest firmware version installed.


### Connection methods

  - SolaX G2, SolaX G3 Hybrids, Solax ESS (TRENE and AELIO) have built in Ethernet (The Qcells Q.VOLT HYB-G3-3P is a SolaX G4 despite the G3 naming).
  - SolaX G4 and other don't have built-in Ethernet, communication is possible via serial RS485 COM port.

The RS485 interface uses only the pin4 (blue wire) and pin5 (white-blue). Polarity matters, so make sure pin4 (blue wire in typical cables) is connected to the A lead of your adapter and pin5 (white-blue wire) to the B lead of your adapter.

RS485 cables can be fairly long, so 25 meter or more is possible. You can use the blue pair of a standard cat5 or cat6 cable.

The inverter leaves the factory at 19200 baud, with 8 data bits, no parity and 1 stop bit. The baud rate can be changed on the inverter, and Solax also allows 9600, 14400, 38400, 56000, 57600 and 115200 - so check what your inverter is actually set to, and make sure the Ethernet to RS485 adapter is set to the same baud rate.
You can confirm the baud rate on the LCD screen on the front of your Inverter, within the Menu's.

The Modbus address by default is 1. Some people have reported that their Modbus address was 4.

> [!NOTE]
> There is a port marked COM on the G4 inverter, some user manuals by mistake claim that this is an Ethernet port.
>
> DO NOT CONNECT THIS COM PORT TO AN ETHERNET SWITCH - your Ethernet switch port will die if you do!!!

### RS485 to ETH 

![Waveshare connection scheme](/img/customers/solax/adaptor-rs485-eth-waveshare-b-scheme.png)

- connects through Ethernet to your home network router/switch

When configuring the SolaX Modbus integration, specify the network IP address of the converter device, not the address of the SolaX.
Do not tick the Serial RS485 flag; the serial port is ignored in this setup.

### Multiple inverters connected to one RS485 adaptor & Terminating resistors

It should be possible to connect multiple inverters to the same RS485 adapter (eg Waveshare). The inverters must have different Modbus addresses, so you need to change the Modbus addresses of the inverters first. Then configure one instance for each inverter. The configuration dialogue allows you to set the Modbus address.

The use of Terminating resistors is required when connecting multiple Inverters. Place a 120Ohm resistor accross A&B at the RS485 adaptor and place a 120Ohm resistor accross A&B on the last connected Inverter.


# Solinteg


import { BrandName, ControllerName } from '@site/src/components/customFields';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';
import ClickableImage from '@site/src/components/ClickableImage';

<img
    src="/img/customers/Solinteg/logo.webp"
    alt="logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>




## Supported Devices

The <BrandName /> <ControllerName /> supports a wide range of Solinteg inverters via Modbus TCP and Modbus RTU (RS485), because Solinteg a standardized protocol across all their inverters.
<img
    src="/img/customers/Solinteg/solinteg-inverter.png"
    alt="logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

<DeviceSupportTable
  devices={[
    { type: 'INTEG MHT-(25-50)K', modbusTcp: '✅', rs485: '✅', curtailment: "✅",
  instructionVideos: [{"videoId": "pCqoFOtXNts", "title": "Solinteg MHT 25–50 kW"}]
},
    { type: 'INTEG MHT-(4-20)K', modbusTcp: '✅', rs485: '✅', curtailment: "✅",
  instructionVideos: [{"videoId": "0L7llhD7FKU", "title": "Solinteg MHT 4–20 kW"}]
},
    { type: 'Solinteg-connected grid meter', modbusTcp: '✅', rs485: '✅', curtailment: "-" }

  ]}
  showModbusTcp={true}
  showRs485={true}
  showCurtailment={true} showReactivePower={true}
/>

## Integration versions
__On <ControllerName /> firmware version 1.22.1.1 or higher, we offer an improved Solinteg integration:__

This new version includes:
 - Faster device readout and faster finding of Solinteg inverters
 - Curtailment
 - Option to enable battery priority mode (only for hybrid inverters with both battery and solar): when enabled, the inverter will prioritize discharging the battery before exporting solar power to the grid. This is useful when the battery participates in energy trading and you want certainty about battery power availability.

The classic version is still available and can be used when choosing the 'stable' version. When facing issues with the beta version, you can always switch back to the stable version. 
<img
    src="/img/customers/Solinteg/versions.png"
    alt="logo"
    style={{ display: "block", width: "40%"}}
/>

__On <ControllerName /> firmware version 1.22.1.0 or below, we only offer the classic version of this integration:__
The classic version still supports other functionality like battery control/readout, grid meter readout, solar power measurement.


## Modbus RTU (RS485)
Crimp an RJ45 plug on one end of an Ethernet cable according to the T568B wiring standard.
Insert the crimped RJ45 plug into the <BrandName /> <ControllerName />.

On the other end of the Ethernet cable, connect the blue/white wire to connector pin 13 and the solid blue wire to pin 14.

Finally, connect the USB end of the dongle to an available USB port on the <BrandName /> <ControllerName />.

<ClickableImage
  src="/img/generic/solingtechVerbinding.png"
  alt="Wiring"
  maxWidth="70%"
/>

The default modbus bus address or RTU is 247.

## Modbus TCP
Modbus TCP is by default enabled on the Solinteg inverters. No additional configuration is required.
The default bus address for Modbus TCP is 255.
Other common bus addresses for Modbus TCP are 1, 8, 247.

## Troubleshooting

### My Solinteg is not found when scanning for devices
> [!TIP]
> __Starting from <ControllerName /> firmware version 1.22.1.1, this issue should not occur anymore, as the scanning process has been optimized.__

The Solinteg default bus addresses are 247 for Modbus RTU and 255 for Modbus TCP.
The <BrandName /> <ControllerName /> will scan for devices on all addresses from 1 to 255.
__Therefore, it can take a while to scan for devices.__



If you know the bus address of your Solinteg inverter, you can set it in the <BrandName /> <ControllerName /> to speed up the scanning process.
The example below is for a Solinteg connected using Modbus TCP with bus address 255. By changing the min. bus address to 254, we tell the
<BrandName /> <ControllerName /> to only scan for devices on bus addresses 254 and 255 and to skip the other addresses.
<ClickableImage
  src="/img/customers/Solinteg/1.png"
  alt="Wiring"
  maxWidth="100%"
/>

## Note when having two or more Solinteg inverters
If you have multiple Solinteg inverters, be aware that:
 - No master-slave configuration is supported. Each inverter must be connected individually to the <BrandName /> <ControllerName />. __Any master-slave configuration should be disabled on the inverters.__
 - The Solinteg grid meter is not supported when having multiple Solinteg inverters. When importing a Solinteg, use the following setting:
   <ClickableImage src="/img/customers/Solinteg/2.png" alt="Wiring" maxWidth="100%"/> Use a dedicated meter for grid measurements on the <BrandName /> <ControllerName />, that is not affiliated with any of the Solinteg inverters.

# Solis Grid-tied Inverters


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/customers/solis/logo.png"
    alt="logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

# Solis On Grid Inverters

## Choose a compatible datalogger

> [!IMPORTANT]
> An online Solis datalogger—whether connected to Wi-Fi or visible in SolisCloud—is not proof that a local Modbus TCP interface is available. Check the model number on the logger itself before commissioning.

| Solis datalogger | Connector | Local Modbus TCP | SmartgridOne connection |
| --- | --- | --- | --- |
| **S2-WL-ST** | 4-pin | ✅ Port 502 | Compatible and verified in the field |
| **S3-WIFI-ST** | 4-pin | ❌ Not available | Not compatible with the Modbus TCP connection described on this page |

The S2-WL-ST is a Wi-Fi/LAN logger that [officially supports Modbus TCP](https://www.solisinverters.com/us/accessories9/S2_WL_ST_nl.html). Solis also provides a [Modbus TCP setup guide for the S2-WL-ST](https://usservice.solisinverters.com/support/solutions/articles/73000670200-modbus-tcp-communication-guide-for-s2-wl-st-wi-fi-lan-logger). The S3-WIFI-ST is a Wi-Fi-only logger: it can send data to SolisCloud, but it does not expose the local Modbus TCP server required by the <ControllerName />.

If an S3-WIFI-ST is installed, replace it with an **S2-WL-ST (4-pin)** before using Modbus TCP, or connect the inverter directly through RS485 when that is suitable for the installation.

### Pre-commissioning check

1. Read the full model number from the datalogger label. Do not rely on its appearance or SolisCloud status.
2. For Ethernet communication, install an **S2-WL-ST with the 4-pin connector**.
3. Connect the datalogger and the <ControllerName /> to the same local network.
4. Give the datalogger a stable IP address, preferably through a DHCP reservation or a static configuration.
5. Confirm that the datalogger responds locally on TCP port **502**.
6. In the commissioning wizard, add a TCP connection with the datalogger IP address and port **502**, then scan the inverter's Modbus address. The factory-default address is **1**.

> [!TIP]
> If the logger is online in SolisCloud but port 502 times out, verify the logger model first. Changing the inverter address or repeating a scan will not make an S3-WIFI-ST provide Modbus TCP.

## Supported Devices
<div style={{ display: "flex", gap: "10px", justifyContent: "left" }}>
<ClickableImage src="/img/customers/solis/S5-GC50K.jpg" alt="Image" maxWidth="450px"/>
<ClickableImage src="/img/customers/solis/solis-s6-gc_25-60_k-us-front_4.jpg" alt="Image" maxWidth="274px" />
</div>


<DeviceSupportTable
  devices={[
    { type: 'S5-GR3P(3-20)K', modbusTcp: '✅ with compatible logger', rs485: '✅', curtailment: "✅"  },
    { type: 'S5-GC(25-40)K', modbusTcp: '✅ with compatible logger', rs485: '✅', curtailment: "✅" },
    { type: 'S5-GC(50-60)K', modbusTcp: '✅ with compatible logger', rs485: '✅', curtailment: "✅" },
    { type: 'S5-GC80K', modbusTcp: '✅ with compatible logger', rs485: '✅', curtailment: "✅" },
    { type: 'S5-GC(100-110)K', modbusTcp: '✅ with compatible logger', rs485: '✅', curtailment: "✅" },
    { type: 'S6-GR1P(0.7-3.6)K-M', modbusTcp: '✅ with compatible logger', rs485: '✅', curtailment: "✅" },
    { type: 'S6-GR1P(2.5-6)K', modbusTcp: '✅ with compatible logger', rs485: '✅', curtailment: "✅" },
    { type: 'S6-GR1P(7-8)K02-NV-YD-HC', modbusTcp: '✅ with compatible logger', rs485: '✅', curtailment: "✅" },
    { type: 'S6-GC3P(40-60)K-NV-ND', modbusTcp: '✅ with compatible logger', rs485: '✅', curtailment: "✅" },
    { type: 'S6-GC(80-125)K', modbusTcp: '✅ with compatible logger', rs485: '✅', curtailment: "✅" },
    { type: 'S6-GC3P150K07-NV-ND', modbusTcp: '✅ with compatible logger', rs485: '✅', curtailment: "✅" },
    { type: 'S6-GU350K-EHV', modbusTcp: '✅ with compatible logger', rs485: '✅', curtailment: "✅" },
    { type: '100-125K G5', modbusTcp: 'experimental', rs485: '✅', curtailment: "✅"  },
    { type: 'Solis-80K-5G-PRO', modbusTcp: '✅ with compatible logger', rs485: '✅', curtailment: "✅" },
    { type: 'Solis-255K-EHV-5G-PLUS', modbusTcp: '✅ with compatible logger', rs485: '✅', curtailment: "✅" },
    
  ]}
  showModbusTcp={true}
  showRs485={true}
  showCurtailment={true} showReactivePower={true}
/>

## Wiring

### RS485
<RS485AddressNote />

<table>
  <thead>
    <tr>
      <th>Model</th>
      <th>Page</th>
    </tr>
  </thead>
  <tbody>
    <tr><td>S5-GR3P(3-20)K</td><td rowspan="10"><a href="/Controller/Devices/PV-hybrid-and-battery-inverters/Solis/Grid tied line/S-series-on-grid/">Wiring configuration for S5/S6 Series</a></td></tr>
    <tr><td>S5-GC(25-40)K</td></tr>
    <tr><td>S5-GC(50-60)K</td></tr>
    <tr><td>S5-GC80K</td></tr>
    <tr><td>S5-GC(100-110)K</td></tr>
    <tr><td>S6-GR1P(0.7-3.6)K-M</td></tr>
    <tr><td>S6-GR1P(2.5-6)K</td></tr>
    <tr><td>S6-GR1P(7-8)K02-NV-YD-HC</td></tr>
    <tr><td>S6-GC3P(40-60)K-NV-ND</td></tr>
    <tr><td>S6-GU350K-EHV</td></tr>
    <tr><td>100-125K G5</td><td rowspan="3"><a href="/Controller/Devices/PV-hybrid-and-battery-inverters/Solis/Grid tied line/Large_PV/">Wiring configuration for Industrial PV installation</a></td></tr>
    <tr><td>Solis-80K-5G-PRO</td></tr>
    <tr><td>Solis-255K-EHV-5G-PLUS</td></tr>
  </tbody>
</table>

By default, the inverter is set to address 1. This can be changed via the display of the inverter. You can find the procedure in chapter 7.3.2 of the manual.


# Large PV Grid Inverters


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/customers/solis/logo.png"
    alt="logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

# Solis Large PV Grid Inverters

### RS485
<RS485ConnectionTable firstColumn={["RS485A1 IN", "RS485B1 IN", "N/A"]} />
<ClickableImage src="/img/customers/solis/100-125K-G5-wiring.png" alt="Image" maxWidth="450px" />

## Configuration

### RS485
<RS485AddressNote />

By default, the inverter is set to address 1. This can be changed via the display of the inverter. You can find the procedure in chapter 7.3.2 of the manual.

# S-Series (grid-tied)

import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/customers/solis/logo.png"
    alt="logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

# Solis S-Series (Grid-tied)

## Wiring
The RS485 connection is made via the 16-pin COM connector at the bottom of the converter.

<RS485ConnectionTable firstColumn={["RS485 IN A", "RS485 IN B", "N/A"]} />
<ClickableImage src="/img/customers/solis/S5-GC50K-wiring.png" alt="Image" maxWidth="450px" />

## Configuration

### RS485
<RS485AddressNote />

By default, the inverter is set to address 1. This can be changed via the display of the inverter. You can find the procedure in chapter 7.3.2 of the manual.

# 3t10K-HVES-G5 Wiring

import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/customers/solis/logo.png"
    alt="logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>
This page describes the communication with a Solis 3T10K over Modbus-RTU (rs485). By default, the inverter is set to address 1. This can be changed via the display of the inverter. You can find the procedure in chapter 7.3.2 of the manual. The RS485 terminals are located on the bottom of the inverter behind a protective plate.
<RS485ConnectionTable firstColumn={["Pin 3", "Pin 4", "N/A"]} />
<ClickableImage src="/img/customers/solis/3t10K-HVES-G5-wiring.png" alt="Image" maxWidth="450px" />

<RS485AddressNote />


# Solis Hybrid Inverters


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';
import Mermaid from '@theme/Mermaid';

<img
    src="/img/customers/solis/logo.png"
    alt="logo"
    style={{ display: "block", margin: "0 auto", width: "40%" }}
/>

# Solis Hybrid Inverters
## Supported Devices

<ClickableImage src="/img/customers/solis/3t10K-HVES-G5.png" alt="Image" maxWidth="450px" />


<DeviceSupportTable
  devices={[
  { type: 'Solis 3t10K HVES G5', modbusTcp: 'experimental', rs485: '✅', curtailment: '✅' },
  { type: 'Solis S5-EH1P(3-6)K-L', modbusTcp: '✅ (only with Solis data logger)', rs485: '✅', curtailment: '✅' },
  { type: 'Solis S5-EH1P(8-10)K-L-PLUS', modbusTcp: '✅ (only with Solis data logger)', rs485: '✅', curtailment: '✅' },
  { type: 'Solis S5-EA1P3K-L', modbusTcp: '✅ (only with Solis data logger)', rs485: '✅', curtailment: '✅' },
  { type: 'Solis S6-EH3P(8-15)K02-NV-YD-L', modbusTcp: '✅ (only with Solis data logger)', rs485: '✅', curtailment: '✅' },
  { type: 'Solis S6-EH3P(5-10)K-H-EU', modbusTcp: '✅ (only with Solis data logger)', rs485: '✅', curtailment: '✅' },
  { type: 'Solis S6-EH3P(5-10)K2-H', modbusTcp: '✅ (only with Solis data logger)', rs485: '✅', curtailment: '✅' },
  { type: 'Solis S6-EH3P(12-20)K-H', modbusTcp: '✅ (only with Solis data logger)', rs485: '✅', curtailment: '✅' },
  { type: 'Solis S6-EA1P(3.6-6)K-L', modbusTcp: '✅ (only with Solis data logger)', rs485: '✅', curtailment: '✅' },
  { type: 'Solis S6-EO1P(4-5)K-48-EU', modbusTcp: '✅ (only with Solis data logger)', rs485: '✅', curtailment: '✅' },
  { type: 'Solis S6-EH3P(30-50)K-H', modbusTcp: '✅ (only with Solis data logger)', rs485: '✅', curtailment: '✅' },
  {  },
]}
  showModbusTcp={true}
  showRs485={true}
  showCurtailment={true} showReactivePower={true}
/>

> [!NOTE]
> Currently, only the connection via RS485 has been tested, but you may also be able to run the inverter via Ethernet.

## Control Features

> [!CAUTION] Solis Inverter Firmware
> Ensure that you have the latest firmware installed on your Solis inverter. The functionality of external control
> features like battery control and curtailment is dependent on the firmware version.

The setup of your Solis is an important factor in which EMS-features supported:
<Mermaid
  value={`flowchart TD
    Start([Is a battery connected <br>to the Solis inverter?]) --> |Yes| Battery
    Start --> |No| NoGrid

    Battery[Is a grid meter connected <br> to the Solis inverter?]
    NoGrid[Is a grid meter connected <br> to the Solis inverter?]

    Battery --> |Yes| BatteryGridYes[✅ Battery control<br/>supported <br/> <br/>✅ Curtailment <br> supported]
    Battery --> |No| BatteryGridNo[✅ Battery control<br/>supported <br/> <br/>✅ Curtailment <br> supported]

    NoGrid --> |Yes| NoGridYes[✅ Curtailment <br> supported]
    NoGrid --> |No| NoGridNo[❌ Curtailment<br/>not supported]

    classDef question fill:#f0f8ff,stroke:#0066cc,stroke-width:2px
    classDef success fill:#e6ffe6,stroke:#28a745,stroke-width:2px
    classDef warning fill:#fffacc,stroke:#ffc107,stroke-width:2px
    classDef error fill:#ffe6e6,stroke:#dc3545,stroke-width:2px

    class Start,Battery,NoGrid question
    class BatteryGridNo,BatteryGridYes success
    class NoGridYes warning
    class NoGridNo error`}
/>

Curtailment is now supported for Solis hybrid inverters. The latest firmware version by Solis includes curtailment registers that allow external control of the inverter's output power without writing to the flash memory.
## Wiring (RS485)
The wiring between the <BrandName/> <ControllerName/> and the Solis can be done with the following guides:
<table>
  <thead>
    <tr>
      <th>Model</th>
      <th>Page</th>
    </tr>
  </thead>
  <tbody>
    <tr><td>3t10K HVES G5</td><td><a href="/Controller/Devices/PV-hybrid-and-battery-inverters/Solis/Hybrid/3t10K%20HVES%20G5">Wiring configuration for 3t10K HVES G5</a></td></tr>
    <tr><td>S5-EH1P(3-6)K-L</td><td rowspan="10"><a href="/Controller/Devices/PV-hybrid-and-battery-inverters/Solis/Hybrid/S-Series/">Wiring configuration for S5/S6 Series</a></td></tr>
    <tr><td>S5-EH1P(8-10)K-L-PLUS</td></tr>
    <tr><td>S5-EA1P3K-L</td></tr>
    <tr><td>S6-EH3P(8-15)K02-NV-YD-L</td></tr>
    <tr><td>S6-EH3P(5-10)K-H-EU</td></tr>
    <tr><td>S6-EH3P(5-10)K2-H</td></tr>
    <tr><td>S6-EH3P(12-20)K-H</td></tr>
    <tr><td>S6-EA1P(3.6-6)K-L</td></tr>
    <tr><td>S6-EO1P(4-5)K-48-EU</td></tr>
    <tr><td>S6-EH3P(30-50)K-H</td></tr>
  </tbody>
</table>
If your model is not listed, we refer to the manual of the Solis inverter. It should always include a section on how to wire a rs485 communication with external EMS-systems.


# S-Series-Hybrid


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/customers/solis/logo.png"
    alt="logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

# Solis S-Series Hybrid Inverters


## Wiring
The RS485 connection is made via the 16-pin COM connector at the bottom of the converter.

<RS485ConnectionTable firstColumn={["RS485 IN A", "RS485 IN B", "N/A"]} />
<ClickableImage src="/img/customers/solis/S5-GC50K-wiring.png" alt="Image" maxWidth="450px" />

## Configuration

### RS485
<RS485AddressNote />

By default, the inverter is set to address 1. This can be changed via the display of the inverter. You can find the procedure in chapter 7.3.2 of the manual.

# Solis


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import ClickableImage from '@site/src/components/ClickableImage';
import ClickableVideo from '@site/src/components/ClickableVideo';

The <BrandName /> <ControllerName /> supports the Solis grid-tied and hybrid inverter product lines. The two product lines use separate communication protocols.
Before we continue, we need to know in which product line your inverter is in.

> [!IMPORTANT]
> **Planning a Modbus TCP connection for a grid-tied inverter?** Check the exact datalogger model before going on site. The **S2-WL-ST (4-pin)** provides the required local Modbus TCP connection on port **502**. The **S3-WIFI-ST** is a Wi-Fi-only logger and cannot be used for this connection. See the [grid-tied Solis instructions](/Controller/Devices/PV-hybrid-and-battery-inverters/Solis/Grid%20tied%20line/#choose-a-compatible-datalogger) for the compatibility check and commissioning steps.

<div style={{
  display: 'flex',
  gap: '20px',
  marginTop: '2rem',
  justifyContent: 'center'
}}>
  <a href="/Controller/Devices/PV-hybrid-and-battery-inverters/Solis/Grid%20tied%20line/" className="solis-choice-button" style={{
    padding: '2rem',
    backgroundColor: '#007bff',
    borderRadius: '10px',
    textDecoration: 'none',
    color: 'white',
    flex: 1,
    maxWidth: '300px',
    textAlign: 'center',
    boxShadow: '0 2px 4px rgba(0,0,0,0.1)',
    transition: 'transform 0.2s, box-shadow 0.2s, background-color 0.2s',
    cursor: 'pointer'
  }}>
    <h3 style={{ margin: '0 0 1rem 0', color: 'white' }}>Grid-tied line</h3>
    <p style={{ margin: '0', color: 'rgba(255,255,255,0.9)' }}>Single and three phase grid-tied inverters</p>
  </a>
  
  <a href="/Controller/Devices/PV-hybrid-and-battery-inverters/Solis/Hybrid/" className="solis-choice-button" style={{
    padding: '2rem',
    backgroundColor: '#007bff',
    borderRadius: '10px',
    textDecoration: 'none',
    color: 'white',
    flex: 1,
    maxWidth: '300px',
    textAlign: 'center',
    boxShadow: '0 2px 4px rgba(0,0,0,0.1)',
    transition: 'transform 0.2s, box-shadow 0.2s, background-color 0.2s',
    cursor: 'pointer'
  }}>
    <h3 style={{ margin: '0 0 1rem 0', color: 'white' }}>Hybrid and off-grid line</h3>
    <p style={{ margin: '0', color: 'rgba(255,255,255,0.9)' }}>Battery storage inverters with backup capability</p>
  </a>
</div>

<details open style={{ marginTop: '2rem', padding: '1rem', border: '1px solid', borderRadius: '8px' }}>
  <summary style={{ cursor: 'pointer', fontWeight: 'bold' }}>Understanding the difference between inverter types</summary>
  <p>
    Go to the <a href="https://www.solisinverters.com/uk" target="_blank" rel="noopener noreferrer">official Solis website</a>.
    Lookup your model in either the 'Hybrid & Off Grid Inverters' or 'Grid Tie Inverters' section, marked by the blue arrows in the image below.
  </p>

  <ClickableImage src="/img/customers/solis/choose.png" alt="Solis Inverter" maxWidth="850px" />

  If your model is not listed under the 'Hybrid & Off Grid Inverters' on the Solis website, open both the <a href="/Controller/Devices/PV-hybrid-and-battery-inverters/Solis/Hybrid">Hybrid and Off-grid line</a> and <a href="/Controller/Devices/PV-hybrid-and-battery-inverters/Solis/Grid tied line">Grid-tied line</a> pages to see if your model is listed in either section.
  <div style={{ marginTop: '1rem' }}>
    <p><strong>Grid-tied Line:</strong></p>
    <ul>
      <li>Only-solar inverters that convert DC power from solar panels to AC power</li>
      <li>Only work when grid power is available</li>
      <li>No battery storage capability</li>
    </ul>
    
    <p><strong>Hybrid Line:</strong></p>
    <ul>
      <li>Hybrid inverters that can work with both solar panels and batteries</li>
      <li>Can store excess solar energy in batteries</li>
      <li>Choose this if you have (or plan to have) battery storage</li>
    </ul>
  </div>
</details>

<style>
{`
  .solis-choice-button:hover {
    transform: translateY(-2px);
    box-shadow: 0 4px 8px rgba(0,0,0,0.2);
    background-color: #0056b3 !important;
  }
`}
</style>


# Solplanet


import { BrandName, ControllerName } from '@site/src/components/customFields';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';

<img
    src="/img/customers/solplanet/logo.png"
    alt="logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

# Solplanet

## Supported Devices

<DeviceSupportTable
  devices={[
    { type: 'ASW LT 125kW', modbusTcp: '❌', rs485: '✅' , curtailment: "✅"},
    { type: 'ASW LT-G2 Pro 3-20kW', modbusTcp: '❌', rs485: '✅' , curtailment: "✅"},
    { type: 'ASW LT-G3 45-60kW', modbusTcp: '❌', rs485: '✅' , curtailment: "✅"},
    { type: 'ASW LT-G3 25-40kW', modbusTcp: '❌', rs485: '✅' , curtailment: "✅"},
    { type: 'ASW LT 75-110kW', modbusTcp: '❌', rs485: '✅' , curtailment: "✅"},
    { type: 'ASW HT 250-360kW', modbusTcp: '❌', rs485: '✅' , curtailment: "✅"},
  ]}
  showModbusTcp={true}
  showRs485={true}
  showCurtailment={true} showReactivePower={true}
/>

# Wiring

The <BrandName /> <ControllerName /> and the ASW LT-G2 Pro 3-20kW Solplanet inverter communicate via RS485.

### RS485 for the ASW LT-G2 Pro 3-20kW Solplanet inverter

<ClickableImage src="/media/solplanet/ASW-LT-G2-Pro-3-20kW-Connection.png" alt="Marstek connection" maxWidth="350px" />
<RS485ConnectionTable firstColumn={["TX_RS485A", "TX_RS485B", "GND"]} />


# Sungrow


import { FolderOverview } from '@/components/FolderOverview';

# Sungrow

<FolderOverview folder="Controller/Devices/PV-hybrid-and-battery-inverters/Sungrow" />


# Powerstack


import { BrandName, ControllerName } from '@site/src/components/customFields';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import ClickableImage from '@site/src/components/ClickableImage';

<img
    src="/img/customers/sungrow/logo.jpeg"
    alt="logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

# Sungrow Inverters

## Supported Devices


<DeviceSupportTable
  devices={[
    { type: 'Powerstack', modbusTcp: '✅', rs485: '✅'},
  ]}
  showModbusTcp={true}
  showRs485={true}
  showReactivePower={true}
/>

## Wiring

The <BrandName /> <ControllerName /> and the battery system communicate via RS485 or Ethernet.

### Ethernet
For correct ethernet wiring: Follow the [the guidelines for ethernet wiring](/Controller/wiring-best-practices/#ethernet).

### RS485
<RS485ConnectionTable firstColumn={["A", "B", "GND (if available)"]} />


## Configuration

If you want to start the steering of the battery, or if it wasn't controlled for a long time, you can reactivate it by going into other actions and select "start the device".

<ClickableImage src="/img/customers/sungrow/manualAction1.png" alt="Other action step 1" maxWidth="250px" />
<ClickableImage src="/img/customers/sungrow/manualAction2.png" alt="Other action step 2" maxWidth="250px" />

# Sungrow Inverters


import { BrandName, ControllerName } from '@site/src/components/customFields';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/customers/sungrow/logo.jpeg"
    alt="logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

# Sungrow Inverters

## Supported Devices


<DeviceSupportTable
  devices={[
    { type: 'SG-Series', modbusTcp: '✅', rs485: '✅' , curtailment: "✅"},
    { type: 'S-Series', modbusTcp: '✅', rs485: '✅' ,curtailment: "✅"},
    { type: 'SR-Series', modbusTcp: '✅', rs485: '✅', curtailment: "✅" },
    { type: 'MVS-Series', modbusTcp: '✅', rs485: '✅', curtailment: "✅" },
    { type: 'ST-Series', modbusTcp: '✅', rs485: '✅', curtailment: "✅" },
    { type: 'SH-Series', modbusTcp: '✅', rs485: '✅', curtailment: "✅" },
    { type: 'SBR-Series', modbusTcp: '✅', rs485: '✅', curtailment: "✅" },
    { type: 'SC-Series', modbusTcp: '✅', rs485: '✅', curtailment: "✅" }
  ]}
  showModbusTcp={true}
  showRs485={true}
  showCurtailment={true} showReactivePower={true}
/>

## Physical Connection

### Ethernet Connection
For correct ethernet wiring, follow the [guidelines for ethernet wiring](/Controller/wiring-best-practices/#ethernet).

### RS485 Connection
1. Locate the COM port on your Sungrow inverter
2. Connect the RS485 cable:
   - Connect A+ (typically red) to pin 1
   - Connect B- (typically black) to pin 2
   - Connect GND (typically yellow) to pin 3 if available

## Network Configuration

### For Ethernet Connection
1. Set the inverter's network settings:
   - Access the inverter's display interface
   - Navigate to Settings → Communication Parameters
   - Enable MODBUS-TCP
   - Set the communication address (default: 502)
   - Configure DHCP or static IP as needed

## Device Configuration

### Enabling Modbus Communication
1. Access the inverter's LCD screen
2. Navigate to Settings → Communication Parameters
3. Set the following:
   - Protocol: MODBUS
   - Device Address: Set a unique address (1-247)
4. For Modbus TCP:
   - Enable MODBUS-TCP
   - Port: 502 (default)
   - IP Address: Configure as per your network requirements

### Verification
1. Check the communication LED indicator:
   - Steady green: Normal communication
   - Blinking green: Data transmission in progress
   - Off: No communication
2. Verify network connectivity using ping test (for Ethernet)

### LED Status Indicators

| LED Status | Meaning | Action Required |
|:--|:--|:--|
| Steady Green | Normal operation | None |
| Blinking Green | Data transmission | Normal operation |
| Off | No communication | Check connections and settings |
| Red | Communication error | Check configuration and cables |


# Sunsynk


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/customers/sunsynk/logo.jpg"
    alt="logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>


## Supported Devices

<DeviceSupportTable
    devices={ [
        {
            type: "Three phase hybrid inverter",
            variants: "SUNSYNK-12K-SG04LP3, SUNSYNK-50K-SG01HP3-EU-BM4",
            modbusTcp: "✅",
            rs485: "✅",
            curtailment: "✅"
        },
    ] }
    showVariants = { true }
    showModbusTcp = { true }
    showRs485 = { true }
    showCurtailment = { true } showReactivePower={true}
/>

## Wiring

### RS485
<RS485ConnectionTable firstColumn={["Pin 1 / Modbus-485_B", "Pin 2 / Modbus-485_A", "Pin 3 / GND_485"]} />
<ClickableImage src="/img/customers/deye/deye_wiring_pt1.png" alt="Image 1" maxWidth="450px" />
<ClickableImage src="/img/customers/deye/deye_wiring_pt2.jpg" alt="Image 1" maxWidth="450px" />
<ClickableImage src="/img/customers/deye/deye_wiring_pt3.png" alt="Image 1" maxWidth="450px" />


## Configuration
<RS485AddressNote />

Go to “Main Screen” >> “System Settings” >> “Advanced Function.”
- Modbus SN should be set to any number between 1 and 247. Do not select 0!! Note that if there are multiple devices on the RS485 bus, each should be given a unique number. This is the address.
- Slave should be checked.
- Only when an additional meter is connected directly to the inverter should “EX_meter For CT” be checked. If there is only a meter in parallel with the <BrandName /> <ControllerName /> it should be unchecked.
- Make sure the following settings are all correct: "Max A Charge", "Max A Discharge", "Grid Charge Ampere"

<ClickableImage src="/img/customers/deye/deye_config_pt1.png" alt="Image 1" maxWidth="450px" />

# Sunwaytech


import { BrandName, ControllerName } from '@site/src/components/customFields';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';

<img
    src="/img/customers/sunwaytech/Logo_sunwaytech.png"
    alt="logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

# Sunwaytech

## Supported Devices


<DeviceSupportTable
  devices={[
    { type: 'Inverters', modbusTcp: '❌', rs485: '✅' , curtailment: "✅"},
  ]}
  showModbusTcp={true}
  showRs485={true}
  showCurtailment={true} showReactivePower={true}
/>

## Physical Connection

### RS485 Connection

The communication between the <BrandName /> <ControllerName /> and the Sunwaytech inverter is done via RS485.

<RS485ConnectionTable firstColumn={["A", "B", "GND"]} />



# Sunwoda


import { FolderOverview } from '@/components/FolderOverview';

# Sunwoda

<FolderOverview folder="Controller/Devices/PV-hybrid-and-battery-inverters/Sunwoda" />


# Sunwoda Oasis


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

# Sunwoda

## Supported Devices

<DeviceSupportTable
  devices={[
    { type: 'Oasis 180', modbusTcp: '✅', rs485: '✅', curtailment: "❌" },
    { type: 'Oasis L261 All-in-ONe', modbusTcp: '✅', rs485: '❌', curtailment: "❌" },
  ]}
  showModbusTcp={true}
  showRs485={true}
  showCurtailment={true} showReactivePower={true}
/>

## Wiring
### Ethernet
For correct ethernet wiring: Follow the [the guidelines for ethernet wiring](/Controller/wiring-best-practices/#ethernet).

### RS485
<RS485ConnectionTable firstColumn={["", "", ""]} />


## Configuration
If you are connecting through TCP, be sure that the device is configured to communicate with port <b>502</b>.
<RS485AddressNote />

# Sunwoda OSP


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/sgo/Logo_Sunwoda.png"
    alt="logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>
# Sunwoda

## Supported Devices

<DeviceSupportTable
  devices={[
    { type: 'OSP-100K-A', modbusTcp: '✅', rs485: '✅', curtailment: "❌" },
    { type: 'OSP-200K-A', modbusTcp: '✅', rs485: '✅', curtailment: "❌" },
    { type: 'OSP-200K-A2', modbusTcp: '✅', rs485: '✅', curtailment: "❌" },
    { type: 'OSP-300K-A3', modbusTcp: '✅', rs485: '✅', curtailment: "❌" },
    { type: 'OSP-400K-A2', modbusTcp: '✅', rs485: '✅', curtailment: "❌" },
    { type: 'OSP-400K-A4', modbusTcp: '✅', rs485: '✅', curtailment: "❌" },
    { type: 'OSP-100K-B', modbusTcp: '✅', rs485: '✅', curtailment: "❌" },
    { type: 'OSP-200K-B', modbusTcp: '✅', rs485: '✅', curtailment: "❌" },
    { type: 'OSP-200K-B2', modbusTcp: '✅', rs485: '✅', curtailment: "❌" },
    { type: 'OSP-100K-C-2', modbusTcp: '✅', rs485: '✅', curtailment: "❌" },
    { type: 'OSP-100K-C-3', modbusTcp: '✅', rs485: '✅', curtailment: "❌" },
    { type: 'OSP-200K-C', modbusTcp: '✅', rs485: '✅', curtailment: "❌" },
    { type: 'OSP-200K-C2', modbusTcp: '✅', rs485: '✅', curtailment: "❌" },
    { type: 'OSP-100K-H-2', modbusTcp: '✅', rs485: '✅', curtailment: "❌" },
    { type: 'OSP-100K-H-3', modbusTcp: '✅', rs485: '✅', curtailment: "❌" },
    { type: 'OSP-200K-H', modbusTcp: '✅', rs485: '✅', curtailment: "❌" },
    { type: 'OSP-200K-H2', modbusTcp: '✅', rs485: '✅', curtailment: "❌" },
  ]}
  showModbusTcp={true}
  showRs485={true}
  showCurtailment={true} showReactivePower={true}
/>
> [!CAUTION] Important for batteries larger than 100 kW
> If your battery power is rated for 100 kW or more, contact the Sunwoda support to enlargen the power limitation register.
> By default, the power limitation is set to 100 kW. This can be updated by Sunwoda support on register `0x78f6`. <BrandName /> <ControllerName /> will then be able to control the power limitation.
## Wiring
### Ethernet
For correct ethernet wiring: Follow the [the guidelines for ethernet wiring](/Controller/wiring-best-practices/#ethernet).

### RS485
<RS485ConnectionTable firstColumn={["", "", ""]} />


## Configuration
If you are connecting through TCP, be sure that the device is configured to communicate with port <b>502</b>.
<RS485AddressNote />



# Sunwoda SunESS


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';


# Sunwoda SunESS

## Supported Devices

<DeviceSupportTable
  devices={[
    { type: 'SunESS-5H', modbusTcp: '❌', rs485: '✅', curtailment: "❌" },
    { type: 'SunESS-10H', modbusTcp: '❌', rs485: '✅', curtailment: "❌" },
    { type: 'SunESS-15H', modbusTcp: '❌', rs485: '✅', curtailment: "❌" },
    { type: 'SunESS-20H', modbusTcp: '❌', rs485: '✅', curtailment: "❌" },
  ]}
  showModbusTcp={true}
  showRs485={true}
  showCurtailment={true} showReactivePower={true}
/>

## Wiring
### Ethernet
For correct ethernet wiring: Follow the [the guidelines for ethernet wiring](/Controller/wiring-best-practices/#ethernet).

### RS485
<RS485ConnectionTable firstColumn={["", "", ""]} />
---

## 1. Overview

Sunwoda SunESS-H systems support external EMS integration using the PCS communication port, which provides **RS485 (Modbus RTU)** and **CAN**.  
This document describes how to connect a SunESS system to an EMS using **RS485 RTU**.

---

## 2. Required Hardware

### 2.1 PCS Communication Port

Located on the right side of the SunESS Control Module and labeled:

**PCS Communication (RS485/CAN)**

### 2.2 RS485 Pinout (RJ45)

| Pin | Function   | Wire Color     |
|-----|------------|----------------|
| 1   | RS485 A    | Orange-white   |
| 2   | RS485 B    | Orange         |
| 3   | NC         | Green-white    |
| 4   | CANH       | Blue           |
| 5   | CANL       | Blue-white     |
| 6   | NC         | Green          |
| 7   | Wakeup +5V | Brown-white    |
| 8   | Wakeup –   | Brown          |

Only **Pin 1 (A)** and **Pin 2 (B)** are used for RS485.

---

## 3. Wiring the SunESS to an EMS (RS485)

### 3.1 RS485 Wiring

- SunESS PCS Port EMS RTU Port
- Pin 1 (A) ---------> RS485 A (D+)
- Pin 2 (B) ---------> RS485 B (D-)


### 3.2 Cable Recommendations

- Twisted pair, shielded  
- 24–18 AWG  
- Ground shield at **one side only** (typically EMS side)

---

## 4. Termination & RS485 Bus Rules

### 4.1 Termination

SunESS requires:

- **120 Ω resistor installed on COM1 port**

When used in parallel systems, termination is applied **only on the master unit**.

### 4.2 RS485 Bus Rules

- Daisy-chain only (no star topology)  
- A ↔ A and B ↔ B must be consistent across devices  
- Ensure EMS termination is set appropriately (ON or off depending on your wiring)

---

## 5. Configuring SunESS for EMS (RS485) Communication

Configuration is performed using the **PowerLite app**.

### Steps

1. Connect to SunESS using Bluetooth/Wi-Fi  
2. Enter the device settings  
3. Open **PCS Setting**  
4. Select the protocol: **Default (INV-08)**  
   - Enables SunESS standard RS485/CAN protocol

This is required for EMS communication.

---

## 6. EMS Communication Settings (Modbus RTU)

> Note: Actual SunESS register maps are not included in the manufacturer manual and must be requested from Sunwoda or inverter/EMS vendor.

Typical working defaults:

| Parameter | Value |
|----------|--------|
| Protocol | Modbus RTU |
| Baudrate | 57600 |
| Data bits | 8 |
| Parity | None |
| Stop bits | 1 |
| Slave ID | 1 |

---

## 7. Parallel SunESS Systems

Up to 3 cabinets can be connected in parallel.

### 7.1 Battery-to-Battery Communication

- **COM0 → COM1** is used for internal SunESS communication  
- Daisy-chain between cabinets

### 7.2 EMS Connection

- Only the **master SunESS** communicates with the EMS  
- Connect the EMS RS485 lines to the **master’s PCS port**

---

## 8. Startup & Verification

### 8.1 Power-Up Sequence

1. Close inverter battery switch (if installed)  
2. Close SunESS circuit breaker (MCB)  
3. Hold **Power** button for ≥3 seconds  
4. Display lights up and system boots

### 8.2 Communication Verification

EMS should:

- Poll the SunESS slave ID and receive valid Modbus responses  
- Report SOC, voltage, current, alarms, etc.

SunESS should:

- Display solid status LED (normal operation)

---

## 9. Troubleshooting

Common issues and checks:

### Issue: EMS cannot read SunESS registers

- A/B reversed → swap RS485 A/B  
- Termination missing → ensure 120 Ω installed at COM1  
- Wrong PCS protocol → select **Default (INV-08)**  
- Wrong Modbus settings → verify baud, parity, ID

### Issue: Parallel system not synchronizing

- COM0/COM1 cables not daisy-chained correctly  
- Slave cabinet not powered on  
- Incorrect master selection

---

## 10. Field Procedure (Quick Guide)

1. Wire RS485:  
   - Pin 1 → EMS A  
   - Pin 2 → EMS B  
2. Install 120 Ω resistor on COM1  
3. Configure PCS protocol = Default (INV-08)  
4. Configure EMS Modbus settings  
5. Power on SunESS  
6. Verify Modbus communication


# Sus-Power


<img
    src="/img/sgo/Logo_Sus-Power.png"
    alt="logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>


> [!NOTE] Supported Devices
> The following devices are supported and existing integrations remain available. However, these brands and models were integrated several years ago and are not commonly used by our current customers. If you require support or assistance with these devices, please contact us for further guidance.


# Tecloman


import { BrandName, ControllerName } from '@site/src/components/customFields';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/customers/tecloman/logo.png"
    alt="logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>


## Supported Devices

<DeviceSupportTable
  devices={[
    {
      type: "HPS",
      modbusTcp: "✅",
      rs485: "❌",
      curtailment: "❌"
    },
    {
      type: "TPCS-630",
      modbusTcp: "✅",
      rs485: "❌",
      curtailment: "❌"
    }
  ]}
  showModbusTcp={true}
  showRs485={true}
  showCurtailment={true} showReactivePower={true}
/>


## Connection

The communication between the <BrandName /> <ControllerName /> and the tecloman inverters operates via Modbus TCP.
For correct ethernet wiring: Follow the [the guidelines for ethernet wiring](/Controller/wiring-best-practices/#ethernet).


# Teplore


import { BrandName, ControllerName } from '@site/src/components/customFields';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/customers/teplore/logo.png"
    alt="logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>


## Supported Devices

<DeviceSupportTable
  devices={[
    {
      type: "Tensorpack T Battery Rack",
      modbusTcp: "✅",
      rs485: "❌",
    }
  ]}
  showModbusTcp={true}
  showRs485={true}
  showReactivePower={true}
/>


## Connection

The communication between the <BrandName /> <ControllerName /> and the Teplore inverters operates via Modbus TCP.
For correct ethernet wiring: Follow the [the guidelines for ethernet wiring](/Controller/wiring-best-practices/#ethernet).


# Tesvolt


import { BrandName, ControllerName } from '@site/src/components/customFields';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';
import ClickableImage from '@site/src/components/ClickableImage';



<img
    src="/img/customers/tesvolt/Logo_Tesvolt.png"
    alt="Tesvolt"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

# Tesvolt

## Supported Devices

<DeviceSupportTable
  devices={[
    {
      type: "Energy Manager",
      modbusTcp: "✅",
      rs485: "❌",
      curtailment: "✅",
    }
  ]}
  showModbusTcp={true}
  showRs485={true}
  showCurtailment={true} showReactivePower={true}
/>

## Wiring
The communication between the <BrandName /> <ControllerName /> and the Tesvolt system operates via Modbus TCP.
For correct ethernet wiring: Follow the [the guidelines for ethernet wiring](/Controller/wiring-best-practices/#ethernet).

## Energy Manager

### Tesvolt Energy Manager Configuration

| Steps |
|------|
| **1a**. Open the Tesvolt Energy Manager web interface. Request the link to the portal, and its login credentials from your installer |
| **1b**. Go to **Remote Control Signals** under **Device Settings** and press **Configure a Remote Control Signal**: <img src="/img/customers/tesvolt/TesvoltInstruction1.PNG" alt="Image" maxWidth="100%"/> |
| **1c**. Configure the device with the correct IP address(Listen Address) and slave address(Unit ID) and press **Save**: <img src="/img/customers/tesvolt/TesvoltInstruction2.PNG" alt="Image" maxWidth="100%"/> |
{/* TODO pictures don't work? */}

### Troubleshooting
Inside the Tesvolt Energy manager web interface, it's possible to check the signals that are sent by the <BrandName /> <ControllerName /> to the Tesvolt Energy Manager.
It can be reached using this way:
<ClickableImage src="/img/customers/tesvolt/troubleshoot1.png" alt="Groups example" maxWidth="750px" />

#### PV control issues:
If any issues occur related to PV control, check if the following value corresponds with the value set by the controller:
<ClickableImage src="/img/customers/tesvolt/TesvoltTroubleShooting1.PNG" alt="Groups example" maxWidth="750px" />
#### Battery control issues:
If any issues occur related to battery control, check if the following value corresponds with the value set by the controller:
<ClickableImage src="/img/customers/tesvolt/TesvoltTroubleShooting2.PNG" alt="Groups example" maxWidth="750px" />
{/* TODO pictures don't work? */}


# TWS


import { BrandName, ControllerName } from '@site/src/components/customFields';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';

<img src="/img/customers/TWS/logo.png" alt="logo"
    style={{ display: "block", margin: "0 auto", width: "40%", background: "white" }}
/>

# TWS

## Supported Devices

<DeviceSupportTable
  devices={[
    { type: 'Cabinet', modbusTcp: '✅', rs485: '❌' },
  ]}
  showModbusTcp={true}
  showRs485={true}
  showReactivePower={true}
/>

## Wiring

### Ethernet
For correct ethernet wiring: Follow the [the guidelines for ethernet wiring](/Controller/wiring-best-practices/#ethernet).

## Configuration
Make sure that the TWS Cabinet is configured this way:
<ClickableImage src="/img/customers/TWS/config.png" alt="TWS Configuration" maxWidth="450px" />


# Vacon


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';


## Supported Devices

<DeviceSupportTable
  devices={[
    {  
      type: "Vacon Solar 8000 (Solar Inverter)",
      modbusTcp: "❌",
      rs485: "✅",
      curtailment: "❌"
    }
  ]}
  showModbusTcp={false}
  showRs485={true}
  showCurtailment={true} showReactivePower={true}
  showFirmwareVersion={false}
/>

> [!NOTE] Supported Devices
> The above devices are supported and existing integrations remain available. However, these brands and models were integrated several years ago and are not commonly used by our current customers. If you require support or assistance with these devices, please contact us for further guidance.


# Victron


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';
import ClickableVideo from '@site/src/components/ClickableVideo';

<img
    src="/img/customers/victron/logo.png"
    alt="logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

# Victron

## Supported Devices

<DeviceSupportTable
  devices={[
    { type: 'Multiplus II', modbusTcp: '✅', rs485: '❌', curtailment: "✅"},
    { type: 'Multiplus RS', modbusTcp: '✅', rs485: '❌', curtailment: "✅" },
    { type: 'Cerbo GX', modbusTcp: '✅', rs485: '❌', curtailment: "✅" },
    { type: 'Venus GX', modbusTcp: '✅', rs485: '❌', curtailment: "✅" },
    { type: 'Inverters with built in GX device', modbusTcp: '✅', rs485: '❌', curtailment: "✅" },
    { type: 'Other Victron devices', modbusTcp: '✅', rs485: '❌', curtailment: "✅" }
  ]}
  showModbusTcp={true}
  showRs485={true}
  showCurtailment={true} showReactivePower={true}
/>

> [!DANGER]
> ### Important
> If you already have your PV or other devices connected to the Victron system make sure not to add them again to the <BrandName /> <ControllerName />. This can cause double measurements.

## Wiring
For correct ethernet wiring: Follow the [the guidelines for ethernet wiring](/Controller/wiring-best-practices/#ethernet).
## Video
<ClickableVideo 
  videoSrc="/img/generic/Eniris-Victron.mp4" 
  alt="Demo Video"
  maxWidth="600px"
/>
## Configuration
### 1. Modbus TCP must be enabled.

In the settings of the inverter:
1. Go to "Settings"
2. Go to "Services"
3. Go to "Modbus TCP"
4. Select "Enable Modbus/TCP."

<ClickableImage src="/img/customers/victron/config-1.png" alt="Image" maxWidth="100%" />

### 2. The ESS must be in a mode that allows steering. In the inverter settings, go to:
1. Go to "Settings"
2. Go to "ESS"
3. Select mode "Optimized (**without** BatteryLife)"

> [!DANGER]
> ### Important
> IF THIS MODE IS CHANGED, THE SYSTEM WILL NOT WORK PROPERLY!

<ClickableImage src="/img/customers/victron/config-2.png" alt="Image" maxWidth="100%" />

### 3. Disable scheduled loading
1. Go to "Settings"
2. Go to "ESS"
3. Go to "Scheduled charge levels"
4. Disable all scheduled charge levels

<ClickableImage src="/img/customers/victron/config-3.png" alt="Image" maxWidth="100%" />

### 4. Activate switch
The switch at the bottom of the inverter must be in position 1 to accept the control.
<ClickableImage src="/img/customers/victron/multiplus_II-config_pt9.png" alt="Image" maxWidth="350px" />

## Troubleshooting

#### If your inverter still is not working properly, please check the following:

1. Dynamic ESS must be disabled.
2. Are your grid limits set correctly?
3. Are your groups set correctly in the controller? (See example below)
4. If the battery is oscillating, set the scheduler run time to 5s minimum in the advanced settings.

<ClickableImage src="/img/customers/victron/groups.png" alt="Groups example" maxWidth="350px" />

#### If you experience problems with the control of the inverter, please follow these steps:

1. Before following these steps make sure to remove the Victron inverter from the <BrandName /> <ControllerName /> controller so that the controller doesn't interfere with the testing.
2. Now go to the Victron interface. Under the "Settings" tab, go to "System Setup".
<ClickableImage src="/img/customers/victron/victron_troubleshooting_1.png" alt="Groups example" maxWidth="450px" />
3. Go to "ESS".
<ClickableImage src="/img/customers/victron/victron_troubleshooting_2.png" alt="Groups example" maxWidth="450px" />
4. Press "Grid setpoint".
<ClickableImage src="/img/customers/victron/victron_troubleshooting_3.png" alt="Groups example" maxWidth="450px" />
5. Set the grid setpoint to a certain value so that the battery will start charging or discharging.
<ClickableImage src="/img/customers/victron/victron_troubleshooting_4.png" alt="Groups example" maxWidth="450px" />
6. Validate on the overview page that the battery is charging or discharging.
<ClickableImage src="/img/customers/victron/victron_troubleshooting_5.png" alt="Groups example" maxWidth="450px" />
7. If there is no response to the setpoint then this indicates there is an issue with the Victron inverter, rather than the <BrandName /> <ControllerName /> controller."

# Volstora


import { BrandName, ControllerName } from '@site/src/components/customFields';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/sgo/Logo_Volstora.png"
    alt="Volstora Logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

# Volstora

## Supported Devices

<DeviceSupportTable
  devices={[
    {
      type: "Battery Containers",
      modbusTcp: "✅",
      rs485: "❌",
      curtailment: "✅",
    }
  ]}
  showModbusTcp={true}
  showRs485={true}
  showCurtailment={true} showReactivePower={true}
/>

## Connection & Wiring

The <BrandName /> <ControllerName /> connects to the Volstora battery container using a standard Ethernet (network) cable. The communication runs on the **Modbus TCP** protocol.

> [!INFO] 
> ### Connection Details
> * **Protocol:** Modbus TCP
> * **IP Address:** You must get this from the Volstora system's network settings.
> * **Port:** The default Modbus port is **502**.
> * **Slave ID / Unit ID:** This is the Modbus address of the battery, typically 1.

For correct ethernet wiring, please follow the [guidelines for ethernet wiring](/Controller/wiring-best-practices/#ethernet).

## Configuration in the <ControllerName />

When you add the Volstora battery in the <ControllerName /> setup, you will be asked for one specific setting:

> [!DANGER]
> ### Critical Setting: Battery Size
> You **must** select the correct **"Battery Size (ft)"** from the dropdown menu.
>
> * 4ft
> * 10ft
> * 20ft
> 
> This setting is critical. The <ControllerName /> uses it to set the correct power limits for charging and discharging. **Choosing the wrong size will lead to incorrect battery control and may prevent the system from working.**

## Troubleshooting

If the <ControllerName /> cannot find the device or isn't showing any data, you can test the network connection manually.

> [!TIP]
> ### Testing Tool
> You will need a Modbus testing tool (like **Modbus Poll**) on a laptop or computer that is on the same network as the Volstora battery.

1.  Open your Modbus tool and set up a new **Modbus TCP** connection.
2.  Enter the battery's **IP Address** and the default port **502**.
3.  Set the **Slave ID** (or Unit ID) to match the battery's address (e.g., 1).
4.  Try to read **Holding Registers** (Function Code 3) at the following addresses:

    * **Register Address: 302**
        * **Quantity:** 1
        * **What it is:** State of Charge (SoC).
        * **Expected Result:** You should see an integer value representing the SoC. For example, `5000` means 50.0%.

    * **Register Address: 303**
        * **Quantity:** 2 (This is a 32-bit value)
        * **What it is:** Active Power.
        * **Expected Result:** You should see the battery's current power reading in Watts.

If you can read these values, the network connection is working. If not, double-check your IP address, port, and that the battery is on the same network.

## Status & Alarm Codes

If you see a warning or error message for the Volstora battery in the <ControllerName /> interface, that message is coming directly from the battery itself. This table shows what the most common codes mean.

| Code Range | Status | Example Messages |
| :--- | :--- | :--- |
| 1 - 49 | **Info (Operational)** | `Container is operational` (1)<br/>`Container is charging` (5)<br/>`Container is discharging` (6)<br/>`Container is balancing` (7) |
| 50 - 119 | **Warning** | `General warning reported by container` (50)<br/>`Batteries not responding` (58)<br/>`Battery cell imbalance` (65)<br/>`Cell temperature high` (84)<br/>`String imbalance` (95) |
| 120 - 150 | **Error (Fault)** | `E-stop pressed (local or remote)` (120)<br/>`Failure reported by container` (127)<br/>`Dangerously low cell voltage` (130)<br/>`Dangerously high cell temperature` (132) |


# WattsNext


import { BrandName, ControllerName } from '@site/src/components/customFields';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';
import ApacheLicense from '@site/src/components/ApacheLicense';

<img
    src="/img/customers/wattsnext/logo.png"
    alt="WattsNext logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

# WattsNext

## Supported Devices

<DeviceSupportTable
  devices={[
    {  
      type: "WattsNext All-in-one Cabinet ES232/115K-A/EU",
      modbusTcp: "✅",
      rs485: "❌",
    }
  ]}
  showModbusTcp={true}
  showRs485={true}
  showFirmwareVersion={false}
  showReactivePower={true}
/>

## Installation

### Connection

- The WattsNext cabinet connects via **Ethernet (Modbus TCP)**.  
- **Port:** 502  
- **Default Modbus address:** 1  
- Make sure the cabinet and the <BrandName /> <ControllerName /> are on the **same local network**.  
- No RS485 or serial communication is used.

> [!NOTE]
> Only one Modbus address is supported (address 1).

---

### Configuration in <BrandName /> <ControllerName />

1. Open the configuration interface.  
2. Add a new device and select **WattsNext EMS Protocol (TCP)**.  
3. Enter the **IP address** of the WattsNext cabinet.  
4. Leave the **port** as `502`.  
5. Click **Save** and restart communication.


<ApacheLicense />


# Weiheng


import { BrandName, ControllerName } from '@site/src/components/customFields';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';
import ClickableImage from '@site/src/components/ClickableImage';

<div style={{ textAlign: "center", marginBottom: "2rem" }}>
  <img
    src="/img/customers/weiheng/logo.png"
    alt="Weiheng"
    style={{ maxWidth: 520, width: "100%", height: "auto" }}
  />
</div>

# Weiheng

## Supported Devices

| Device Type | Modbus TCP (Ethernet) | RS485 | Curtailment | Reactive power control |
| --- | :---: | :---: | :---: | :---: |
| EMS100 | ✅ | ❌ | ⚠️ | — |

- **Protocol driver:** `Weiheng EMS100 Modbus TCP`
- **Default TCP port:** `502`

## Configuration

### Ethernet Connection

Make sure the Controller and the Weiheng EMS100 are connected to the **same network**.

- Connect the EMS100 Ethernet port to the same switch/router as the Controller.
- Ensure the EMS100 has a reachable IP address.
- TCP port must be **502** .


For correct ethernet wiring: Follow the [the guidelines for ethernet wiring](/Controller/wiring-best-practices/#ethernet).

### Device settings
⚠️ Make sure the device Direct power control read-only mode is off. 
If it is on we can't send commands with the EMS100.

# Hybrid Inverter 3.6-6kW

import { BrandName, ControllerName } from '@site/src/components/customFields';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import RS485AddressNote from '@site/src/components/RS485AddressNote';

<div style={{ textAlign: "center", marginBottom: "2rem" }}>
  <img
    src="/img/customers/WHES/logo.png"
    alt="WHES"
    style={{ maxWidth: 520, width: "100%", height: "auto" }}
  />
</div>

# Hybrid Inverter 3.6-6kW

## Supported Devices

<DeviceSupportTable
  devices={[
    { type: 'WH-SHC362', modbusTcp: '❌', rs485: '✅', curtailment: '⚠️' },
    { type: 'WH-SHC502', modbusTcp: '❌', rs485: '✅', curtailment: '⚠️' },
    { type: 'WH-SHC602', modbusTcp: '❌', rs485: '✅', curtailment: '⚠️' },
  ]}
  showModbusTcp
  showRs485
  showCurtailment
  showReactivePower={true}
/>

- **Protocol driver:** `WHES Single Phase Hybrid Inverter Protocol (RTU)`

## Configuration

### RS485 Connection

The <BrandName /> <ControllerName /> communicates with this device over **Modbus RTU on RS485**.
This device has **no Modbus TCP interface**, so an Ethernet connection cannot be used.

Run the communication cable directly from the **VPP 485** port of the device to an RS485 port on
the <BrandName /> <ControllerName />.

<RS485ConnectionTable firstColumn={["VPP_485A", "VPP_485B", "N/A"]}/>

The <BrandName /> <ControllerName /> supports only these serial settings for this device:

| Setting | Value |
| --- | --- |
| Protocol | Modbus RTU |
| Baud rate | 115200 |
| Parity | None |
| Data bits | 8 |
| Stop bits | 1 |
| Modbus address | 1 (default), 1 - 247 supported |

<RS485AddressNote />

### Grid meter
The meter built into this inverter measures **one phase only**. On a single-phase grid connection it can serve as the grid meter.

⚠️ On a **three-phase grid connection**, install a separate three-phase grid meter. The built-in meter only sees its own phase and misses the power on the other two.

The built-in meter reports any grid power between about -100 W and +100 W as 0 W. This dead zone is fixed in the inverter firmware and cannot be changed with a setting.


# Hybrid Inverter 5-13kW

import { BrandName, ControllerName } from '@site/src/components/customFields';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import RS485AddressNote from '@site/src/components/RS485AddressNote';

<div style={{ textAlign: "center", marginBottom: "2rem" }}>
  <img
    src="/img/customers/WHES/logo.png"
    alt="WHES"
    style={{ maxWidth: 520, width: "100%", height: "auto" }}
  />
</div>

# Hybrid Inverter 5-13kW

## Supported Devices

<DeviceSupportTable
  devices={[
    { type: 'WH-THA502', modbusTcp: '❌', rs485: '✅', curtailment: '⚠️' },
    { type: 'WH-THA602', modbusTcp: '❌', rs485: '✅', curtailment: '⚠️' },
    { type: 'WH-THA802', modbusTcp: '❌', rs485: '✅', curtailment: '⚠️' },
    { type: 'WH-THA103', modbusTcp: '❌', rs485: '✅', curtailment: '⚠️' },
    { type: 'WH-THA123', modbusTcp: '❌', rs485: '✅', curtailment: '⚠️' },
    { type: 'WH-THA133', modbusTcp: '❌', rs485: '✅', curtailment: '⚠️' },
  ]}
  showModbusTcp
  showRs485
  showCurtailment
  showReactivePower={true}
/>

- **Protocol driver:** `WHES Three Phase Hybrid Inverter Protocol (RTU)`

## Configuration

### RS485 Connection

The <BrandName /> <ControllerName /> communicates with this device over **Modbus RTU on RS485**.
This device has **no Modbus TCP interface**, so an Ethernet connection cannot be used.

Run the communication cable directly from the **VPP 485** port of the device to an RS485 port on
the <BrandName /> <ControllerName />.

<RS485ConnectionTable firstColumn={["VPP_485A", "VPP_485B", "N/A"]}/>

The <BrandName /> <ControllerName /> supports only these serial settings for this device:

| Setting | Value |
| --- | --- |
| Protocol | Modbus RTU |
| Baud rate | 115200 |
| Parity | None |
| Data bits | 8 |
| Stop bits | 1 |
| Modbus address | 1 (default), 1 - 247 supported |

<RS485AddressNote />


# WHES


import { FolderOverview } from '@/components/FolderOverview';

# WHES (WeiHeng Energy Storage Systems)

<FolderOverview folder="Controller/Devices/PV-hybrid-and-battery-inverters/WHES" />


# PC-G1 100kW/233kWh

import { BrandName, ControllerName } from '@site/src/components/customFields';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<div style={{ textAlign: "center", marginBottom: "2rem" }}>
  <img
    src="/img/customers/WHES/logo.png"
    alt="WHES"
    style={{ maxWidth: 520, width: "100%", height: "auto" }}
  />
</div>

# PC-G1 100kW/233kWh

## Supported Devices

<DeviceSupportTable
  devices={[
    { type: 'WH-TIANWU-100-233B', modbusTcp: '✅', rs485: '❌', curtailment: '⚠️' },
  ]}
  showModbusTcp
  showRs485
  showCurtailment
  showReactivePower={true}
/>

- **Protocol driver:** `Weiheng EMS100 Modbus TCP`
- **Default TCP port:** `502`

## Configuration

### Ethernet Connection

Make sure the Controller and the <BrandName /> EMS100 are connected to the **same network**.

- Connect the EMS100 Ethernet port to the same switch/router as the Controller.
- Ensure the EMS100 has a reachable IP address.
- TCP port must be **502** .


For correct ethernet wiring: Follow the [the guidelines for ethernet wiring](/Controller/wiring-best-practices/#ethernet).

### Device settings
⚠️ Make sure the device Direct power control read-only mode is off. 
If it is on we can't send commands with the <BrandName />.


# PC-G2 250kW/509kWh

import { BrandName, ControllerName } from '@site/src/components/customFields';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<div style={{ textAlign: "center", marginBottom: "2rem" }}>
  <img
    src="/img/customers/WHES/logo.png"
    alt="WHES"
    style={{ maxWidth: 520, width: "100%", height: "auto" }}
  />
</div>

# PC-G2 250kW/509kWh

## Supported Devices

<DeviceSupportTable
  devices={[
    { type: 'IA-250kW/500kWh', modbusTcp: '✅', rs485: '❌', curtailment: '⚠️' },
  ]}
  showModbusTcp
  showRs485
  showCurtailment
  showReactivePower={true}
/>

- **Protocol driver:** `Weiheng EMS100 Modbus TCP`
- **Default TCP port:** `502`

## Configuration

### Ethernet Connection

Make sure the Controller and the <BrandName /> EMS100 are connected to the **same network**.

- Connect the EMS100 Ethernet port to the same switch/router as the Controller.
- Ensure the EMS100 has a reachable IP address.
- TCP port must be **502** .


For correct ethernet wiring: Follow the [the guidelines for ethernet wiring](/Controller/wiring-best-practices/#ethernet).

### Device settings
⚠️ Make sure the device Direct power control read-only mode is off. 
If it is on we can't send commands with the <BrandName />.


# PC-mini 29.9-50kW 57-100kWh

import { BrandName, ControllerName } from '@site/src/components/customFields';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<div style={{ textAlign: "center", marginBottom: "2rem" }}>
  <img
    src="/img/customers/WHES/logo.png"
    alt="WHES"
    style={{ maxWidth: 520, width: "100%", height: "auto" }}
  />
</div>

# PC-mini 29.9-50kW 57-100kWh

## Supported Devices

<DeviceSupportTable
  devices={[
    { type: 'IA-29.9kW/100kWh-EC10', modbusTcp: '✅', rs485: '❌', curtailment: '⚠️' },
    { type: 'IA-30kW/100kWh-EC10', modbusTcp: '✅', rs485: '❌', curtailment: '⚠️' },
    { type: 'IA-40kW/100kWh-EC10', modbusTcp: '✅', rs485: '❌', curtailment: '⚠️' },
    { type: 'IA-50kW/100kWh-EC10', modbusTcp: '✅', rs485: '❌', curtailment: '⚠️' },
  ]}
  showModbusTcp
  showRs485
  showCurtailment
  showReactivePower={true}
/>

- **Protocol driver:** `Weiheng EMS100 Modbus TCP`
- **Default TCP port:** `502`

## Configuration

### Ethernet Connection

Make sure the Controller and the <BrandName /> EMS100 are connected to the **same network**.

- Connect the EMS100 Ethernet port to the same switch/router as the Controller.
- Ensure the EMS100 has a reachable IP address.
- TCP port must be **502** .


For correct ethernet wiring: Follow the [the guidelines for ethernet wiring](/Controller/wiring-best-practices/#ethernet).

### Device settings
⚠️ Make sure the device Direct power control read-only mode is off. 
If it is on we can't send commands with the <BrandName />.


# PP-S1 3.6-6kW/5.12-10.24kWh

import { BrandName, ControllerName } from '@site/src/components/customFields';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<div style={{ textAlign: "center", marginBottom: "2rem" }}>
  <img
    src="/img/customers/WHES/logo.png"
    alt="WHES"
    style={{ maxWidth: 520, width: "100%", height: "auto" }}
  />
</div>

# PP-S1 3.6-6kW/5.12-10.24kWh

## Supported Devices

<DeviceSupportTable
  devices={[
    { type: 'WH-SPHA3.6H-5.12kWh', modbusTcp: '❌', rs485: '✅', curtailment: '⚠️' },
    { type: 'WH-SPHA3.6H-10.24kWh', modbusTcp: '❌', rs485: '✅', curtailment: '⚠️' },
    { type: 'WH-SPHA5.0H-5.12kWh', modbusTcp: '❌', rs485: '✅', curtailment: '⚠️' },
    { type: 'WH-SPHA5.0H-10.24kWh', modbusTcp: '❌', rs485: '✅', curtailment: '⚠️' },
    { type: 'WH-SPHA6.0H-5.12kWh', modbusTcp: '❌', rs485: '✅', curtailment: '⚠️' },
    { type: 'WH-SPHA6.0H-10.24kWh', modbusTcp: '❌', rs485: '✅', curtailment: '⚠️' },
  ]}
  showModbusTcp
  showRs485
  showCurtailment
  showReactivePower={true}
/>

- **Protocol driver:** `WHES Single Phase Hybrid Inverter Protocol (RTU)`

## Configuration

### RS485 Connection

The <BrandName /> <ControllerName /> communicates with this device over **Modbus RTU on RS485**.
This device has **no Modbus TCP interface**, so an Ethernet connection cannot be used.

Run the communication cable directly from the **VPP 485** port of the device to an RS485 port on
the <BrandName /> <ControllerName />.

<RS485ConnectionTable firstColumn={["VPP_485A", "VPP_485B", "N/A"]}/>

The <BrandName /> <ControllerName /> supports only these serial settings for this device:

| Setting | Value |
| --- | --- |
| Protocol | Modbus RTU |
| Baud rate | 115200 |
| Parity | None |
| Data bits | 8 |
| Stop bits | 1 |
| Modbus address | 1 (default), 1 - 247 supported |

<RS485AddressNote />

### Grid meter
The meter built into this inverter measures **one phase only**. On a single-phase grid connection it can serve as the grid meter.

⚠️ On a **three-phase grid connection**, install a separate three-phase grid meter. The built-in meter only sees its own phase and misses the power on the other two.

The built-in meter reports any grid power between about -100 W and +100 W as 0 W. This dead zone is fixed in the inverter firmware and cannot be changed with a setting.


# PP-S2 3.6-10kW/4.99kWh-99.9kWh

import { BrandName, ControllerName } from '@site/src/components/customFields';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import RS485AddressNote from '@site/src/components/RS485AddressNote';

<div style={{ textAlign: "center", marginBottom: "2rem" }}>
  <img
    src="/img/customers/WHES/logo.png"
    alt="WHES"
    style={{ maxWidth: 520, width: "100%", height: "auto" }}
  />
</div>

# PP-S2 3.6-10kW/4.99kWh-99.9kWh

## Supported Devices

<DeviceSupportTable
  devices={[
    { type: 'SIA-3.6kW', modbusTcp: '❌', rs485: '✅', curtailment: '⚠️' },
    { type: 'SIA-5kW', modbusTcp: '❌', rs485: '✅', curtailment: '⚠️' },
    { type: 'SIA-6kW', modbusTcp: '❌', rs485: '✅', curtailment: '⚠️' },
    { type: 'SIA-8kW', modbusTcp: '❌', rs485: '✅', curtailment: '⚠️' },
    { type: 'SIA-10kW', modbusTcp: '❌', rs485: '✅', curtailment: '⚠️' },
  ]}
  showModbusTcp
  showRs485
  showCurtailment
  showReactivePower={true}
/>

- **Protocol driver:** `WHES Single Phase Hybrid Inverter Protocol (RTU)`

## Configuration

### RS485 Connection

The <BrandName /> <ControllerName /> communicates with this device over **Modbus RTU on RS485**.
This device has **no Modbus TCP interface**, so an Ethernet connection cannot be used.

Run the communication cable directly from the **VPP 485** port of the device to an RS485 port on
the <BrandName /> <ControllerName />.

<RS485ConnectionTable firstColumn={["VPP_485A", "VPP_485B", "N/A"]}/>

The <BrandName /> <ControllerName /> supports only these serial settings for this device:

| Setting | Value |
| --- | --- |
| Protocol | Modbus RTU |
| Baud rate | 115200 |
| Parity | None |
| Data bits | 8 |
| Stop bits | 1 |
| Modbus address | 1 (default), 1 - 247 supported |

<RS485AddressNote />

### Grid meter
The meter built into this inverter measures **one phase only**. On a single-phase grid connection it can serve as the grid meter.

⚠️ On a **three-phase grid connection**, install a separate three-phase grid meter. The built-in meter only sees its own phase and misses the power on the other two.

The built-in meter reports any grid power between about -100 W and +100 W as 0 W. This dead zone is fixed in the inverter firmware and cannot be changed with a setting.


# PP-T1 5-13kW/9.98-29.94kWh

import { BrandName, ControllerName } from '@site/src/components/customFields';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<div style={{ textAlign: "center", marginBottom: "2rem" }}>
  <img
    src="/img/customers/WHES/logo.png"
    alt="WHES"
    style={{ maxWidth: 520, width: "100%", height: "auto" }}
  />
</div>

# PP-T1 5-13kW/9.98-29.94kWh

## Supported Devices

<DeviceSupportTable
  devices={[
    { type: 'WH-TIA502', modbusTcp: '❌', rs485: '✅', curtailment: '⚠️' },
    { type: 'WH-TIA602', modbusTcp: '❌', rs485: '✅', curtailment: '⚠️' },
    { type: 'WH-TIA802', modbusTcp: '❌', rs485: '✅', curtailment: '⚠️' },
    { type: 'WH-TIA103', modbusTcp: '❌', rs485: '✅', curtailment: '⚠️' },
    { type: 'WH-TIA123', modbusTcp: '❌', rs485: '✅', curtailment: '⚠️' },
    { type: 'WH-TIA133', modbusTcp: '❌', rs485: '✅', curtailment: '⚠️' },
  ]}
  showModbusTcp
  showRs485
  showCurtailment
  showReactivePower={true}
/>

- **Protocol driver:** `WHES Three Phase Hybrid Inverter Protocol (RTU)`

## Configuration

### RS485 Connection

The <BrandName /> <ControllerName /> communicates with this device over **Modbus RTU on RS485**.
This device has **no Modbus TCP interface**, so an Ethernet connection cannot be used.

Run the communication cable directly from the **VPP 485** port of the device to an RS485 port on
the <BrandName /> <ControllerName />.

<RS485ConnectionTable firstColumn={["VPP_485A", "VPP_485B", "N/A"]}/>

The <BrandName /> <ControllerName /> supports only these serial settings for this device:

| Setting | Value |
| --- | --- |
| Protocol | Modbus RTU |
| Baud rate | 115200 |
| Parity | None |
| Data bits | 8 |
| Stop bits | 1 |
| Modbus address | 1 (default), 1 - 247 supported |

<RS485AddressNote />

# Xantrex


import { BrandName, ControllerName } from '@site/src/components/customFields';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';
import ClickableImage from '@site/src/components/ClickableImage';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';

<img
  src="/img/sgo/Logo_Xantrex.png"
  alt="Xantrex"
  style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

# Xantrex Inverters

## Supported Devices

The <BrandName /> <ControllerName /> supports Xantrex inverters that utilize the **RS232** communication protocol.

<DeviceSupportTable
  devices={[
    {
      type: "Xantrex Inverters",
      variants: "Models with RS232 interface",
      modbusTcp: "❌",
      rs485: "❌",
      curtailment: "❌"
    }
  ]}
  showVariants={true}
  showModbusTcp={true}
  showRs485={true}
  showCurtailment={true} showReactivePower={true}
/>

## Wiring

### RS232 Connection
To connect the inverter to the <BrandName /> <ControllerName />, you must use the RS232 interface. This is distinct from the RS485 connection used by many other inverters.



1.  **Port Selection:** Ensure you are connecting to the specific RS232 port on your controller (or using a supported USB-to-RS232 adapter).
2.  **Cable:** You will typically need a DB9 serial cable.

| Pin (DB9) | Function |
| :---: | :--- |
| 2 | Rx (Receive) |
| 3 | Tx (Transmit) |
| 5 | GND (Ground) |



> [!WARNING] Distance Limit
> RS232 cables are designed for short distances. The cable length should generally not exceed **15 meters**. If the inverter is located far away from the controller, this connection method may not be reliable.



# Zendure SolarFlow


import { BrandName, ControllerName } from '@site/src/components/customFields';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/customers/zendure/zendure-logo.jpg" 
    alt="Zendure Logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

## Supported Devices

This driver utilizes the **Zendure SolarFlow Local API** to provide real-time monitoring and control of the SolarFlow ecosystem.

<DeviceSupportTable
  devices={[
    {
      type: "SolarFlow Hub (2400AC)",
      api: '✅', 
      rs485: "❌",
    },
    {
      type: "SolarFlow Mix series",
      api: '✅', 
      rs485: "❌",
    },
  ]}
  showModbusTcp={false}
  showRs485={false}
  showFirmwareVersion={false}
  showApi={true}
  showReactivePower={true}
/>

<img
    src="/img/customers/zendure/2400AC.jpg" 
    alt="Zendure 2400AC image"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>


---
> [!TIP] Related Hardware
> If you are using the **Zendure P1 Smart Meter** to monitor your grid connection, please refer to the [Zendure P1 Meter Documentation](../Energy-meter/Zendure-P1-Meter).
---
## Configuration

### 1. Local Network Requirements
The Zendure Hub must be reachable via **Port 80** on your local network. 

To ensure the <ControllerName /> maintains a consistent connection, you should **assign the connection via MAC Address Reservation**.

### 2. Authentication
The driver requires a unique **Authentication Key** (Handshake Key). 
The API Key can be acquired via the app → account → **Authentication Cloud Key**. 

> [!IMPORTANT]
> This key is required for local API access. It serves as the security token for control functionallity

---

## Troubleshooting
* **Incomplete Response:** Ensure the Hub is not being polled by multiple local instances simultaneously, as the local API can be sensitive to high-frequency requests.
* **Command Failures:** Re-add the device with your current account credentials and ensure it is in a state that allows remote control (e.g., HEMS = OFF).


# Zetara


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/customers/zetara/Logo_Zetara.png" 
    alt="Zetara Logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

# Zetara Inverters

Zetara offers high-performance energy storage solutions, primarily featuring the **Inspiration-T** series. These devices are whitelabeled versions of the AlphaESS Smile series, providing robust hybrid inverter capabilities for residential and commercial energy management.

## Supported Devices

The Zetara Inspiration-T is a hybrid system supporting both PV and Battery integration.

<DeviceSupportTable
  devices = {[
    {
      type: "Inspiration-T",
      variants: "Inspiration-T Hybrid",
      modbusTcp: "✅",
      rs485: "✅",
      curtailment: "✅"
    }
  ]}
  showModbusTcp
  showRs485
  showVariants
  showCurtailment
  showReactivePower={true}
/>

>[!NOTE]
The Zetara Inspiration-T uses the AlphaESS Smile communication protocol (V1.45). When configuring the device, it may be identified as an AlphaESS-compatible unit.
>

## Communication Options

### Ethernet (Modbus TCP)
The preferred method for connecting the Inspiration-T to the <ControllerName/>. 
- **Default Port:** 502
- **Protocol:** Modbus TCP

### RS485 (Modbus RTU)
For installations where Ethernet is unavailable:
- **Protocol:** Modbus RTU
- **Baud Rate:** 9600 (default)

## Wiring

### Ethernet Connection
For correct ethernet wiring, follow the [guidelines for ethernet wiring](/Controller/wiring-best-practices/#ethernet).

### RS485 Connection
For models supporting RS485:
<RS485ConnectionTable firstColumn={["RS485 A", "RS485 B", "GND"]} />

- Use shielded twisted pair (STP) cable.
- Maintain proper polarity (A to A, B to B).

## Configuration & Commissioning

### Critical Installation Requirements

> [!IMPORTANT]
> **Grid Meter Requirement**
> A compatible **grid meter must be installed** and correctly communicating with the Zetara inverter. If the grid meter is missing or offline, the device will **not follow power setpoints** (charge/discharge commands) from the <ControllerName/>.

> [!CAUTION]
> **PV Input Detection**
> During the initial device scan, a **detectable voltage must be present** on each PV input you wish to monitor. If a PV string is not producing voltage (e.g., during night-time or if disconnected), the driver will not add that specific module to the system tree.

## Device Components
When scanned, the Inspiration-T will present as a composite device:
* **Inverter:** The primary management unit.
* **PV Total:** Aggregated data from all active strings (up to 6).
* **Battery Input:** Real-time data for SOC and battery power.

# Zeversolar


import { BrandName, ControllerName } from '@site/src/components/customFields';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/sgo/Logo_Zeversolar.png"
    alt="logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>


## Supported Devices

<DeviceSupportTable
  devices={[
    {
      type: "Solar Inverter",
      api: '✅', 
      rs485: "❌",
      curtailment: "❌"
    },
  ]}
  showModbusTcp={false}
  showRs485={true}
  showCurtailment={true} showReactivePower={true}
  showFirmwareVersion={false}
  showApi={true}
/>

> [!WARNING] 
> ### Supported Devices
> Important Notice:
> The above devices are supported and existing integrations remain available. However, please note that the manufacturer ceased operations on December 31, 2019. While we maintain the integration functionality, we can only provide limited support for these devices due to this circumstance. 

# HomeWizard


import { BrandName, ControllerName } from '@site/src/components/customFields';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/sgo/Logo_HomeWizard.png"
    alt="HomeWizard"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

## Supported Devices

<DeviceSupportTable
  devices={[
    {
        type: 'HomeWizard Wi-Fi Energy Socket (HWE-SKT)',
        localApi: '✅',
    }
  ]}
  showLocalApi={true}
  />

The **<ControllerName/>** communicates with the Energy Socket over its **Local API** (TCP/IP, port 80).
The socket and the controller must be connected to the same network.

## Configuration

To communicate with your HomeWizard device the local API must be enabled.

1. Set up the Energy Socket in the HomeWizard Energy app and connect it to the same network as the **<ControllerName/>**.
2. Open the HomeWizard Energy app.
3. Go to "Settings"
4. Go to "Meters"
5. Select the Energy Socket you want to connect to.
6. Enable the "Local API" option.

> [!NOTE]
> As long as the Local API is disabled, the socket refuses every request. The controller will then
> report that the local API must be enabled instead of showing any measurements.

## Use as switched load or as energy meter

When adding the Energy Socket to the **<ControllerName/>**, the setup wizard asks how you want to use it:

- **Switched Load**: the <ControllerName/> can switch the socket on and off for load control, and it monitors
  the power and energy consumption of the connected appliance.
- **Energy Meter**: the <ControllerName/> only monitors the power and energy consumption of the connected
  appliance. It will never switch the socket, so the appliance always stays powered.

Choose **Energy Meter** if you only want submetering — for example for an appliance that must never be
switched off.

## Switch lock

The HomeWizard Energy app has a "Switch lock" option that prevents the socket from being switched off.
When you use the socket as a **Switched Load**, this option must stay disabled — otherwise the
v cannot switch the socket off and will report that the switch lock is enabled.


# Switched Loads


import { FolderOverview } from '@/components/FolderOverview';

# Switched Loads

<FolderOverview folder="Controller/Devices/Switched-loads" />


# Mystrom


import { BrandName, ControllerName } from '@site/src/components/customFields';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/sgo/Logo_Mystrom.png"
    alt="logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>


## Supported Devices

<DeviceSupportTable
  devices={[
    {
      type: "WiFi Switch",
      modbusTcp: '✅',
      rs485: '❌',
    },
  ]}
  showModbusTcp ={true}
  showRs485 ={false}
/>

# Shelly Relay


import { BrandName, ControllerName } from '@site/src/components/customFields';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/customers/shelly/shelly_logo_blue.png"
    alt="Shelly Logo"
    style={{ display: "block", margin: "0 auto", width: "40%" }}
/>

## Supported Devices

<DeviceSupportTable
  devices={[
    {
      type: "Shelly Plus",
      variants: '1 (Mini), 1PM (Mini), 2PM, Uni',
      localApi: '✅',
    },
    {
      type: "Shelly Plus Plug",
      variants: 'IT, S, US, UK',
      localApi: '✅',
    },
    {
      type: "Shelly Pro",
      variants: '1, 1PM, 2, 2PM, 3, 4PM, EM',
      localApi: '✅',
    },
    {
      type: "Shelly Gen3",
      variants: '1 (Mini), 1PM (Mini), 2PM, 1L, 2L, AZ Plug, Plug S, EM',
      localApi: '✅',
    },
    {
      type: "Shelly Gen4",
      variants: '1 (Mini), 1PM (Mini), 2PM, Plug US, PowerStrip',
      localApi: '✅',
    },
  ]}
  showLocalApi={true}
  showRs485={false}
  showVariants={true}
/>

> [!NOTE]
> Please note: This integration has not been tested with all the devices listed above. However, since they utilize the same communication protocol, they are expected to operate seamlessly.  
> Configuration examples in this document are based on the **Shelly Pro 2** relay.

<ClickableImage src="/img/customers/shelly/shelly-pro2.png" alt="Shelly Pro 2 Relay" maxWidth="450px" />

## Wiring
The communication between the **<ControllerName/>** and the Shelly relay is established via **Local API** (over TCP/IP).
For proper Ethernet wiring, please follow the [Ethernet wiring guidelines](/Controller/wiring-best-practices/#ethernet).

## Wiring Instructions

1. **Power Supply Connections**  
   - **L (Live)**: Connect the live wire to the **L** terminal of the device.  
   - **N (Neutral)**: Connect the neutral wire to the **N** terminal of the device.

   <ClickableImage src="/img/customers/shelly/shelly-blue.png" alt="Power Connections" maxWidth="450px" />


2. **Relay Output Connections**  
   - **O1 (Relay 1)**: Connect the live wire for the first circuit to the **O1** terminal.  
   - **O2 (Relay 2)**: Connect the live wire for the second circuit to the **O2** terminal.

   <ClickableImage src="/img/customers/shelly/shelly-green.png" alt="Relay Connections" maxWidth="450px" />

3. **Device Diagram**  
   Refer to the diagram printed on the device for detailed wiring instructions. Ensure all connections match the diagram.

   <ClickableImage src="/img/customers/shelly/shelly-instructions.png" alt="Device Wiring Diagram" maxWidth="500px" />

---

## Configuration Instructions



1. **Wire the Device**  
   Ensure the device is wired according to the provided wiring diagram and connect the Ethernet cable securely.

   <ClickableImage src="/img/customers/shelly/shelly-wire-cable.jpg" alt="Shelly Wiring Example" maxWidth="450px" />

2. **Access the Shelly Interface**  
   - Using a phone or other device, connect to the Shelly relay's Wi-Fi network (e.g. **SSID: ShellyPro2-XXXXXX**).  
   - Open a browser and navigate to **http://192.168.33.1** to access the Shelly interface.

3. **Locate the Ethernet Settings**  
   - In the Shelly interface, navigate to the **Ethernet Settings** section.  
   - Here, you will find the assigned **Ethernet IP address**, which is required for connecting the device to the controller.

   <ClickableImage src="/img/customers/shelly/shelly-interface.jpg" alt="Shelly Interface Example" maxWidth="300px" />
   <ClickableImage src="/img/customers/shelly/shelly-ethernet.png" alt="Ethernet Settings Example" maxWidth="700px" />

> [!NOTE]
> **Note**: Do not modify any settings while locating the Ethernet IP address.

By following these steps, you will retrieve the required IP address for integrating the Shelly relay with the **<ControllerName/>**.
For further details and comprehensive documentation, please refer to the official [Shelly Installation Guides](https://kb.shelly.cloud/knowledge-base/installation-guides).


# Cadis


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';
import RS485AddressNote from '@site/src/components/RS485AddressNote';

<img
    src="/img/customers/cadis/cadis-logo.png"
    alt="Cadis"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

# Cadis water meter

The Cadis AQUAVISION CONTROL is a module for monitoring and leak detection. It is designed to connect to water meters that have a pulse output and can control motorized shut-off valves to automatically stop water supply in case of a large leak. The module can monitor up to 5 pipes and control up to 3 automatic shut-off valves.

The module can transmit data to a Building Management System (BMS) via Modbus TCP/IP over a computer network or via a Modbus RTU (RS485) connection.

## Supported Devices

<DeviceSupportTable
  devices={[
    {
      type: "AQUAVISION CONTROL Module",
      variants: "Monitors up to 5 water meters and 3 valves",
      modbusTcp: "✅",
      rs485: "✅",
      curtailment: "✅"
    }
  ]}
  showVariants={true}
  showModbusTcp={true}
  showRs485={true}
  showCurtailment={true}
/>

<ClickableImage src="/img/customers/cadis/cadis.png" alt="AQUAVISION CONTROL Principle Diagram" maxWidth="600px" />

## Wiring

The <BrandName /> <ControllerName /> can communicate with the AQUAVISION CONTROL module via either Ethernet (Modbus TCP) or RS485 (Modbus RTU).

### Ethernet (Modbus TCP)

Connect a standard RJ45 network cable from your network switch to the dedicated network port. This port is located on the **bottom left side** of the module housing.

For correct ethernet wiring, follow the [guidelines for ethernet wiring](/Controller/wiring-best-practices/#ethernet).

### RS485 (Modbus RTU)

If a network connection is not possible, wire the RS485 A/B lines from the <BrandName /> <ControllerName /> to the terminals on the module's main board. The connection terminals are D29 for Modbus A and D30 for Modbus B.

<RS485ConnectionTable firstColumn={["Pin 29 (Modbus A)", "Pin 30 (Modbus B)", "N/A"]} />

<ClickableImage src="/img/customers/cadis/cadis-terminal.png" alt="terminal" maxWidth="600px" />

## Configuration

### Modbus RTU

Configuration for Modbus RTU is straightforward as the main parameter is fixed:

* **Modbus Address:** The Modbus slave address is **fixed at 1** and cannot be changed.

Based on the driver, the recommended serial settings are:
* **Baud Rate:** 19200
* **Parity:** None or Even
* **Data Bits:** 8
* **Stop Bits:** 1

<RS485AddressNote />

### Modbus TCP

For Modbus TCP communication, the module must be connected to the local computer network. The module's IP address and network settings must be configured via its touchscreen to match your network.

### Water Meter Setup (Required)

For the module to register consumption correctly, you must configure the pulse ratio (K-value) for each connected water meter.

* This value represents the **liters of water per pulse**.
* The recommended K-value for a connected water meter is between **1 and 10 liters per pulse**.
* This value must be entered during the module's startup configuration.

> [!WARNING]
> You must not connect a second readout system (like a BMS) in parallel to the same water meter pulse output. If this is required, a pulse splitter (e.g., Cadis ref. CA-PULSE-SPL) must be installed first.

# Eniris


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';


<img
src="/img/sgo/Logo_Eniris.png"
alt="Eniris"
style={{ display: "block", margin: "0 auto", width: "40%" }}
/>

## Supported Devices

The integration is intended for **any water meter that offers a clean pulse
output** (normally‑open or normally‑closed contact).  Typical examples are the
popular  **ZENNER**, **Itron**, **Kamstrup**, or **Sensus** models equipped with
pulse modules – but *any* dry‑contact 1 pulse = `x l` counter will work.

<DeviceSupportTable
devices={[
{
type: 'Generic pulse water meter',
modbusTcp: '❌',
rs485: '❌',
dio: '✅',
},
]}
showModbusTcp={false}
showRs485={false}
showDio={true}
/>

## Wiring

Pulses are read via the **digital input** (DIA/DIB) of the <ControllerName /> or Smart Grid Controller.  Wire the meter’s open‑collector
or reed switch as illustrated below:

<ClickableImage src="/img/sgo/WaterMeter.png" alt="Pulse water meter" maxWidth="500px" />

* **Polarity** does not matter for dry contacts.\*  Use twisted pair cable for
  long distances (> 10 m) to minimise interference.

## Configuration in the Eniris Portal

1. Add a new device and select **“Generic Digital Input → Water Meter”**.
2. Choose the digital input (DIA or DIB) you have connected the meter to.
3. Enter the *pulses per m³* (e.g. `1000` pulses/m³ for many domestic meters).
4. Save — the driver will immediately start logging cumulative consumption
   and flow‑rate.

> **Tip :** If you see negative deltas, invert the wiring or change the input
> logic from *normally‑open* to *normally‑closed* in the device settings.

## Metrics exposed

| Key                       | Description                    | Unit |
| ------------------------- | ------------------------------ | ---- |
| `flowRate_lps`            | Instantaneous flow rate        | L/s  |
| `importedAbsWaterTot_l`   | Total volume consumed          | L    |
| `importedWaterDeltaTot_l` | Delta volume since last period | L    |

All metrics are stored in the `waterMeterMetrics` measurement and retained
with 1 s resolution by default.

## Troubleshooting

* No data? Check that the contact actually toggles using a multimeter or LED
  tester, and verify the correct digital input is selected.
* Erratic pulses? Add a 1 kΩ pull‑up resistor or enable the built‑in pull‑up in
  the controller.
* Flow too high/low? Confirm the *pulses per m³* factor from the meter
  datasheet.

---

Need help? Reach out to <BrandName /> support at **[support@eniris.io](mailto:support@eniris.io)**.


# Water Meter


import { FolderOverview } from '@/components/FolderOverview';

# Water Meter

<FolderOverview folder="Controller/Devices/Water-meter" />


# Keyence Flowmeter


import { BrandName, ControllerName } from '@site/src/components/customFields';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';
import RS485AddressNote from '@site/src/components/RS485AddressNote';

<img
  src="/img/customers/keyence/keyence-logo.png"
  alt="Keyence"
  style={{ display: "block", margin: "0 auto", width: "30%" }}
/>

# Keyence FD‑EC Flowmeter

## Supported Devices

<DeviceSupportTable
  devices={[
    {
      type: "Keyence FD‑EC Series",
      variants: "FD‑ECA1 / FD‑ECA1C / FD‑ECA0 (Amplifier units)",
      modbusTcp: "✅",
      rs485: "❌",
      curtailment: "❌",
    },
  ]}
  showVariants={true}
  showModbusTcp={true}
  showRs485={true}
  showCurtailment={true}
/>

## Wiring

The <BrandName /> <ControllerName /> communicates with the FD‑EC amplifier via **Ethernet (Modbus TCP)**.  
Connect the Ethernet cable from the amplifier unit to any free controller network port or network switch on the same LAN.

<RS485ConnectionTable firstColumn={["Ethernet connection", "TCP Port 502", "Category 5e or 6 cable"]} />

<RS485AddressNote />

---

## Software Configuration (Installer Menu)

### 1. Add the Device
1. On the <BrandName /> <ControllerName /> screen or web interface, open  
   **Settings → Devices → Add Device**.
2. Select **“Keyence Flowmeter protocol”** from the device list.
3. Choose **TCP** as the connection type.

---

### 2. Enter Connection Details
1. In the connection window, enter:
   - **IP address** – the address of the FD‑EC amplifier (for example: `192.168.1.120`).  
   - **TCP port** – `502` (default).  
   - **Slave address** – `1` (fixed value for this model).
2. Save to return to the device list.

> [!TIP]
> To find or set the amplifier’s IP address, use the **MP‑F Monitor** software or the setup menu on the amplifier display.  
> Keep your controller and the FD‑EC on the **same local subnet**.

---

### 3. Configure Data Channels
1. Open the **Keyence Flowmeter** device settings screen.  
2. Set the number of connected **flow sensors** (for example, `1` or `2`).  
3. For each sensor, enable or disable data channels such as:
   - **Flow rate (L/min)**  
   - **Total water usage (L)**  
   - **Temperature (°C)**  
   - **Heat power (kW)**  
   - **Energy consumption (kWh)**
4. Save your changes and press **Apply Configuration**.

> [!WARNING]
> Avoid polling the same FD‑EC unit from multiple controllers or software tools simultaneously.  
> Only **one active Modbus‑TCP connection** is supported at a time.



# Wind turbines, water turbines and gensets


import { BrandName, ControllerName } from '@site/src/components/customFields';

# Wind turbines, water turbines and gensets

The <BrandName /> <ControllerName /> supports wind turbines and water turbines (run-of-river hydro) as production devices, next to PV. A turbine is controlled like a PV inverter: the <BrandName /> <ControllerName /> sends it a production limit, never a consumption setpoint. The difference is that a turbine does not depend on the sun, so the <BrandName /> <ControllerName /> controls and monitors it around the clock.

This page explains how a turbine is added, how it is controlled, which external signals and alarms apply to it, and how backup power generators are handled.

> [!NOTE]
> Wind turbines, water turbines and backup power generators are supported from software version 1.32. On older versions, the device wizard and the energy meter settings do not offer them yet. The corresponding device category must also be enabled by the controller licence.

## Supported equipment at a glance

| Equipment | How to connect it | What is supported |
| --- | --- | --- |
| **Wind turbine** | A compatible energy meter, or a custom Modbus turbine integration over TCP or RS485. | Production monitoring; production limiting when the turbine integration supports control. |
| **Water turbine (hydro)** | A compatible energy meter, or a custom Modbus turbine integration over TCP or RS485. | Production monitoring; production limiting when the turbine integration supports control. |
| **Genset / backup power generator** | A compatible energy meter; add a separate relay if start/stop control is required. | Generator production monitoring and optional relay start/stop based on battery state of charge. No variable-power regulation. |

Use the sections below for [turbine connections](#adding-a-turbine), [turbine control](#control) and [backup power generators](#backup-power-generators).

## Adding a turbine

There are two ways to bring a turbine into the <BrandName /> <ControllerName />: as a device, so that it can be controlled, or through an energy meter, so that its production is measured.

### As a device

The device wizard on the "Devices" tab has a **Wind turbine** and a **Water turbine** tile (see [Adding a device](/Controller/Configuration%20from%20A%20to%20Z/11-Extra-Information/adding-device/)).

For a direct connection, use a compatible turbine integration. The **Custom Modbus drivers** module supports wind and water turbines over **Modbus TCP** or **Modbus RTU (RS485)**. It can read production measurements and, if the turbine provides a writable power-limit interface, send a maximum production power. A monitoring-only integration does not provide curtailment.

To create this connection, use the manufacturer's register map to define the measurements and supported control operations, then test the integration before adding the turbine. Follow the [Custom Modbus drivers guide](/Controller/Devices/custom-modbus-drivers/) for the editor, connection settings and testing workflow. If a new integration is needed, use [New integrations](/Controller/Devices/new-integrations/) and include the manufacturer's protocol documentation.

### With an energy meter

For production monitoring without a direct turbine connection, use a compatible energy meter on its feeder:

1. Add the energy meter like any other energy meter (see [Supported devices](/Controller/Devices/)).
2. Open the device settings of the meter and answer "What does the energy meter mainly measure?" with **Wind turbine** or **Water turbine**. Keep **Energy production** for meters that measure PV.

The production of such a meter counts as production of the site: in the production, self-consumption and export figures, and on the data analysis page of the commissioning interface, where the "Solar" labels become "Production" as soon as the site has a producer that is not PV.

An energy meter only measures. The <BrandName /> <ControllerName /> cannot limit a turbine that it only sees through a meter, the meter gets no no-production alarm of its own, and it does not count for the license. It also does not change how batteries are run at night (see [Batteries at night](#batteries-at-night)): what a meter measures is entered by hand, so only a turbine that is added as a device makes the <BrandName /> <ControllerName /> expect production at night.

### Turbines that were added as PV inverters

On older sites, a turbine whose inverter speaks the protocol of a PV inverter may have been added with a PV inverter driver. Such a device is handled as PV, not as a turbine: the around-the-clock behaviour described on this page only applies to devices that are added as a wind or water turbine. The [Negative price wind control](/Controller/Configuration%20from%20A%20to%20Z/8-local-control-modes/special-local-control-modes/negative-price-wind-control/) mode can still be applied to them.

## Device settings

Besides the name and the phase settings that many devices have (see [Device settings](/Controller/Configuration%20from%20A%20to%20Z/11-Extra-Information/device-settings/)), a wind or water turbine has one setting on the "Devices" tab:

| Setting | Explanation |
|:--|:--|
| Nominal power (kW) | Required. The maximum AC power the turbine can deliver. The production limits that the <BrandName /> <ControllerName /> sends are relative to this value, it is how an external setpoint is shared between several turbines, and it is the full-power setpoint of the negative price wind control. A wrong nominal power therefore leads to wrong limits. |

Like PV inverters, turbines have no priority setting.

## Control

### Working mode

Turbines follow the default working mode for **production devices** on the Settings page, the same one as the PV inverters (see [Setting control modes](/Controller/Configuration%20from%20A%20to%20Z/8-local-control-modes/setting-control-modes/)):

- **Don't control**: no active control.
- **Cost optimization**: production is switched off at negative purchase prices (you are then paid to consume), and limited to the consumption of the site at negative selling prices (you pay to inject your surplus). At other times, production is limited to the allowed grid export power.
- **Feed in restriction till allowed grid export power** (default): production is limited to the allowed grid export power.
- **Control exclusively through external API**: production is only limited by external control signals.

The difference with PV is the time of day. At night the <BrandName /> <ControllerName /> leaves PV inverters alone, because they do not produce. A turbine keeps being controlled at night, so the export limit and the negative prices are also respected at night.

There is no dedicated wind or water production forecast: the <BrandName /> <ControllerName /> reacts to the production that the turbine measures.

### Batteries at night

In [battery cost optimization](/Controller/Configuration%20from%20A%20to%20Z/8-local-control-modes/extra-battery-cost-optimization/), part of the battery is kept as a self-consumption variability buffer that absorbs excess production, and the setting "Preferentially store excess production immediately in the battery" charges excess production straight into the battery. On a site with only PV, both are only used by day, because there is no excess production at night. As soon as a wind or water turbine is added as a device, the <BrandName /> <ControllerName /> knows that excess production can also occur at night, and uses both around the clock: excess turbine production at night is stored the same way as excess PV production by day.

A turbine that is only measured by an energy meter does not change this, and neither does a backup power generator.

### Negative price wind control

The special local control mode [Negative price wind control](/Controller/Configuration%20from%20A%20to%20Z/8-local-control-modes/special-local-control-modes/negative-price-wind-control/) switches the selected wind turbines off while the purchase price is negative, and lets them produce at their nominal power the rest of the time. It can be applied to wind turbines and to PV inverters (for turbines that were added as PV inverters), not to water turbines.

## External signals

A turbine is only controlled by the external signals that accept it. Every other external signal cannot select turbines: they keep following the default working mode.

| External signal | Wind turbines | Water turbines |
|:--|:--|:--|
| [Live MQTT control](/Controller/External%20Signals/MQTT/eniris-mqtt/) | ✅ | ✅ |
| [Scheduled MQTT control](/Controller/External%20Signals/MQTT/eniris-schedules-mqtt/) | ✅ | ✅ |
| [DNO Relay Control](/Controller/External%20Signals/dno-relay-control/) | ✅ | ✅ |
| [Fluvius](/Controller/External%20Signals/DSO/fluvius/) (V4 and V5 Netflex Telecontrole) | ✅ | ❌ |
| [Monitoring only](/Controller/Configuration%20from%20A%20to%20Z/8-local-control-modes/special-local-control-modes/monitoring-only/) | ✅ | ✅ |
| Custom control logic (public beta) | ✅ | ✅ |
| [Negative price wind control](/Controller/Configuration%20from%20A%20to%20Z/8-local-control-modes/special-local-control-modes/negative-price-wind-control/) | ✅ | ❌ |

- **MQTT control**: wind turbines and water turbines are their own device groups, `wind` and `water`, next to `solar`. They accept the same policies as `solar`, and a group setpoint is shared between the turbines of the group in proportion to their nominal power. See [Live MQTT control](/Controller/External%20Signals/MQTT/eniris-mqtt/#wind-and-water-turbines).
- **DNO Relay Control**: when the input for curtailment is active, the PV inverters and the turbines are all limited to 0 W.
- **Fluvius**: wind turbines can be selected for both Fluvius signals. With V5, the allowed production power is shared between the PV inverters and the wind turbines in proportion to their nominal power. Water turbines cannot be selected, because Fluvius foresees no asset group for them.

## Monitoring and alarms

### No production

The e-mail alarm for missing production (see [Email alarms](/Controller/Configuration%20from%20A%20to%20Z/11-Extra-Information/email-alarms/)) is named after the producers on the site, for example "Wind is not producing energy" or "PV or wind is not producing energy", and the e-mail says which device to check. A turbine is only checked when it is added as a device and has a nominal power.

When a device counts as not producing depends on what it is:

| Device | When it counts as not producing |
|:--|:--|
| PV | From two hours after sunrise until two hours before sunset, when it does not produce while production is expected. |
| Water turbine | Around the clock, with the same sensitivity as PV. |
| Wind turbine | When it has not produced anything for more than 12 hours in a row. A calm day is normal, so a short standstill is not an alarm. The count starts again when the measurements of the turbine are interrupted for more than 10 minutes, or while the <BrandName /> <ControllerName /> itself limits the turbine to less than 8% of its nominal power, and the alarm clears as soon as the turbine produces again. |

A device counts as producing from 1% of its nominal power. As for every e-mail alarm, the problem must persist before a mail is sent.

### Following the production limit

A turbine is judged like a PV inverter by the alarm "Device not following the power setpoint or limit": the production limit is a maximum, so only producing more than the limit is reported. Producing less, for example because there is little wind, is not an error.

## Testing a turbine

The **Test / manual override** action on the "Devices" tab tests a turbine with a production limit, like a PV inverter (see [Testing and manual override](/Controller/Configuration%20from%20A%20to%20Z/11-Extra-Information/testing-and-manual-override/)). A limit can only be observed while the turbine produces: test on a moment with enough wind or water flow. When the turbine produces less than 100 W, the test page warns that there is not enough production to test curtailment. The automatic test procedure tests "Limit production to 15%" and "Limit production to 0%", and skips these tests when there is no wind or no water flow at the moment of testing.

## License

For the [license](/Controller/license/), the nominal power of a wind or water turbine counts like the nominal power of a PV inverter. Energy meters and backup power generators do not count.

## Backup power generators

Gensets are supported as **Backup power generator** production sources. To monitor a genset, add a compatible [energy meter](/Controller/Devices/Energy-meter/) on its feeder and set **What does the energy meter mainly measure?** to **Backup power generator**. The device wizard also has a **Backup power generator** category for compatible device integrations.

The generator device itself is monitoring-only: the <BrandName /> <ControllerName /> does not send it a variable-power setpoint or production limit, and the "Devices" tab shows "Control is not supported". Its nominal power only serves the site overview. **Relay start/stop is a separate function**, configured through the low-battery-state-of-charge mode linked below; it does not regulate how much power the generator produces.

- Its production counts as production of the site. On a site with a generator, the data analysis page splits the production of the site into "Solar, wind and water production" and "Generator production".
- A generator does not make the batteries expect production at night: it runs on demand, for example during an outage, not on excess production.
- A generator gets no no-production alarm and no setpoint alarm, but it is still checked for missing measurements.
- To start a generator with a relay when the batteries run low, see [Switching on a generator at low battery state of charge](/Controller/Configuration%20from%20A%20to%20Z/8-local-control-modes/special-local-control-modes/switching-generator-on-at-low-battery-soc/).


# Agrola


import { BrandName, ControllerName, CustomerName, InsightsName, InsightsUrl } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/sgo/Logo_Agrola.png"
    alt="Agrola logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

# Setting up Agrola

## Supported Devices

<DeviceSupportTable
  devices={[
    {
        type: 'Solar Inverters',
        variants: 'All',
        customCol: '⌛ (coming soon)',
    },
    {
        type: 'Storage Devices',
        variants: 'All',
        customCol: '✅'
    },
    {
        type: 'EV Chargers',
        variants: 'All',
        customCol: '❌'
    }
  ]}
    showVariants={true}
    customColumns={{ "customCol": "Supported" }}
/>

## Notifying Agrola

Agrola will require information about the <BrandName /> <ControllerName /> before they can control any assets. 

This includes the *<BrandName /> <ControllerName /> Serial Number*, and the *SiteID*, which is the same as the Serial Number with '_site_0' appended at the end.

## Add 'Agrola' External Signal
<ClickableImage src="/img/generic/add-external-datasources-en.png" alt="Image 1" maxWidth="650px" />
<ClickableImage src="/img/generic/add-external-datasources-kind-en.png" alt="Image 1" maxWidth="650px" />

In the next page, you have the option to include/exclude devices for remote control.
Ensure to mark all checkboxes of devices you'd like to include.

> [!NOTE]
> When using multiple batteries, they are aggregated into one (virtual) asset.

<ClickableImage src="/img/generic/add-external-datasources-devices-en.png" alt="Image 1" maxWidth="650px" />

'Agrola' is now set up on the <BrandName /> <ControllerName />.

# Autarco


import { BrandName, ControllerName, CustomerName, InsightsName, InsightsUrl } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/sgo/Logo_Autarco.png"
    alt="Autarco logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

> [!CAUTION] NOTE:
> Autarco external control is no longer active.
>

# Setting up Autarco (External Control)

The manual describes the steps to set up Autarco External Control on the <BrandName /> <ControllerName />.

When setting up this integration, permission is granted to Autarco to control the necessary devices.

## Supported Devices

<DeviceSupportTable
  devices={[
    {
        type: 'Solar Inverters',
        variants: 'All',
        customCol: '✅'
    },
    {
        type: 'Storage Devices',
        variants: 'All',
        customCol: '✅'
    },
    {
        type: 'EV Chargers',
        variants: 'All',
        customCol: '❌'
    }
  ]}
    showVariants={true}
    customColumns={{ "customCol": "Supported" }}
/>

## Prerequisites

### 1. Add the batteries
[Login to the commissioning interface](/Controller/Configuration%20from%20A%20to%20Z/2-accessing-commissioning-interface/) and make sure the [devices are added](/Controller/Configuration%20from%20A%20to%20Z/6-other-devices/) to the <BrandName /> <ControllerName />.

### 2. Check the grid power limits
In the settings, the grid power limits should be set correctly. Click Settings and check the highlighted setting in the image.
If necessary, adjust the settings.

## Add 'Autarco - External Control'
<ClickableImage src="/img/generic/add-external-datasources-en.png" alt="Image 1" maxWidth="650px" />
<ClickableImage src="/img/generic/add-external-datasources-kind-en.png" alt="Image 1" maxWidth="650px" />


In the next page, you have the option to include/exclude devices for remote control.
Ensure to mark all checkboxes of devices you'd like to include.

> [!NOTE]
> When using multiple batteries, they are aggregated into one (virtual) asset for Autarco.

<ClickableImage src="/img/generic/add-external-datasources-devices-en.png" alt="Image 1" maxWidth="650px" />

'Autarco' is now set up on the <BrandName /> <ControllerName />.

# Axpo


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';
import YouTubeEmbed from '@site/src/components/YouTubeEmbed';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';
import CountriesSupportTable from '@site/src/components/CountriesSupportTable';
import Details from '@theme/Details';

<img
    src="/img/sgo/Logo_Axpo.png"
    alt="Axpo logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

## Overview
> [!CAUTION] NOTE:
> Axpo decides when and how your battery should charge or discharge through their system. Our platform simply carries out these battery operation decisions.
>
> If you have any questions about how your battery is being controlled or disagree with the charging/discharging decisions, please contact Axpo directly, as we cannot modify or influence their battery management strategy.
" This service allows you, as a customer of Axpo, to use your battery on various energy markets. The manual describes how we can set this up on the <BrandName /> <ControllerName />. At the end of this manual, Axpo will have control over the battery. When setting up this integration, permission is granted to Axpo to control this battery.

## Supported Devices and countries
The following devices types are supported by the Axpo integration:
<DeviceSupportTable
  devices={[
    {
        type: 'Solar Inverters',
        variants: 'All',
        customCol: '✅',
    },
    {
        type: 'Storage Devices',
        variants: 'All',
        customCol: '✅'
    },
    {
        type: 'EV Chargers',
        variants: 'All',
        customCol: '❌'
    }
  ]}
    showVariants={true}
    customColumns={{ "customCol": "Supported" }}
/>

## Prerequisites

### 1. Add the devices
[Login to the commissioning interface](/Controller/Configuration%20from%20A%20to%20Z/2-accessing-commissioning-interface/) and make sure the [devices are added](/Controller/Configuration%20from%20A%20to%20Z/6-other-devices/) to the <BrandName /> <ControllerName />.

### 2. Check the grid power limits
In the settings, the grid power limits should be set correctly. Click Settings and check the highlighted setting in the image.
If necessary, adjust the settings.

### 3. Check the address
Make sure [the address is set correctly](/Controller/Configuration%20from%20A%20to%20Z/4-location/).

> [!WARNING]
> The integration may not work correctly if the address is not correct!

## Enabling 'Axpo'
From the commissioning interface, go to the 'External Signals' tab.
<ClickableImage src="/img/generic/add-external-datasources-en.png" alt="Image 1" maxWidth="650px" />

Click on 'Energy Markets'.
<ClickableImage src="/img/controller/external signals/types.png" alt="Image 1" maxWidth="650px" />

Select 'Axpo' and click 'Next'.

Select the control tier which is applicable to your installation.

### Tier 1 - Setpoint Follower

Setpoints received from Axpo are sent directly to the devices. No local control is done by the <BrandName /> <ControllerName />.

### Tier 2 - Delta Stacking

The <BrandName /> <ControllerName /> executes its own self-consumption algorithm, Axpo uses the battery availability to activate the battery on ancilliary markets.

### Tier 3 - Battery Splitting

Work in progress.

The battery is split into two virtual batteries. One part is controller by Axpo on various ancilliary energy markets, while the remaining portion of the battery is used for local control only.

## Device Selection

In the next page, you have the option to include/exclude devices for remote control.
Ensure to mark all checkboxes of devices you'd like to include.

> [!NOTE]
> When using multiple devices, they are aggregated into one (virtual) asset, per asset type, for Axpo.

<ClickableImage src="/img/generic/add-external-datasources-devices-en.png" alt="Image 1" maxWidth="650px" />

'Axpo' is now set up on the <BrandName /> <ControllerName />.



# BEE Energy


import { BrandName, ControllerName, CustomerName, InsightsName, InsightsUrl } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';
import CountriesSupportTable from '@site/src/components/CountriesSupportTable';

<img
    src="/img/sgo/Logo_BEE.png"
    alt="BEE logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

# Setting up BEE

The manual describes the steps to set up BEE External Control on the <BrandName /> <ControllerName />.

When setting up this integration, permission is granted to BEE to control the necessary devices.

## Supported Devices

<DeviceSupportTable
  devices={[
    {
        type: 'Solar Inverters',
        variants: 'All',
        customCol: '✅'
    },
    {
        type: 'Storage Devices',
        variants: 'All',
        customCol: '✅'
    },
    {
        type: 'EV Chargers',
        variants: 'All',
        customCol: "❌"
    }
  ]}
    showVariants={true}
    customColumns={{ "customCol": "Supported" }}
/>

## Supported Countries

<CountriesSupportTable
  countries={[
    {
        country: 'Belgium',
        customCol: '✅'
    },
    {
        country: 'Netherlands',
        customCol: '❌'
    },
  ]}
    showVariants={true}
    customColumns={{ "customCol": "Supported" }}
/>

## Prerequisites

### 1. Add the batteries
[Login to the commissioning interface](/Controller/Configuration%20from%20A%20to%20Z/2-accessing-commissioning-interface/) and make sure the [devices are added](/Controller/Configuration%20from%20A%20to%20Z/6-other-devices/) to the <BrandName /> <ControllerName />.

### 2. Check the grid power limits
In the settings, the grid power limits should be set correctly. Click Settings and check the highlighted setting in the image.
If necessary, adjust the settings.

## Add 'BEE - External Control'
<ClickableImage src="/img/generic/add-external-datasources-en.png" alt="Image 1" maxWidth="650px" />
<ClickableImage src="/img/generic/add-external-datasources-kind-en.png" alt="Image 1" maxWidth="650px" />


In the next page, you have the option to include/exclude devices for remote control.
Ensure to mark all checkboxes of devices you'd like to include.

> [!NOTE]
> When using multiple batteries, they are aggregated into one (virtual) asset for BEE.

<ClickableImage src="/img/generic/add-external-datasources-devices-en.png" alt="Image 1" maxWidth="650px" />

'BEE' is now set up on the <BrandName /> <ControllerName />.

# CKW


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';
import YouTubeEmbed from '@site/src/components/YouTubeEmbed';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';
import CountriesSupportTable from '@site/src/components/CountriesSupportTable';
import Details from '@theme/Details';

<img
    src="/img/sgo/Logo_CKW.png"
    alt="CKW logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

## Overview
> [!CAUTION] NOTE:
> CKW decides when and how your battery should charge or discharge through their system. Our platform simply carries out these battery operation decisions.
>
> If you have any questions about how your battery is being controlled or disagree with the charging/discharging decisions, please contact CKW directly, as we cannot modify or influence their battery management strategy.
" This service allows you, as a customer of CKW, to use your battery on various energy markets. The manual describes how we can set this up on the <BrandName /> <ControllerName />. At the end of this manual, CKW will have control over the battery. When setting up this integration, permission is granted to CKW to control this battery.

## Supported Devices and countries
The following devices types are supported by the CKW integration:
<DeviceSupportTable
  devices={[
    {
        type: 'Solar Inverters',
        variants: 'All',
        customCol: '✅',
    },
    {
        type: 'Storage Devices',
        variants: 'All',
        customCol: '✅'
    },
    {
        type: 'EV Chargers',
        variants: 'All',
        customCol: '❌'
    }
  ]}
    showVariants={true}
    customColumns={{ "customCol": "Supported" }}
/>

## Prerequisites

### 1. Add the devices
[Login to the commissioning interface](/Controller/Configuration%20from%20A%20to%20Z/2-accessing-commissioning-interface/) and make sure the [devices are added](/Controller/Configuration%20from%20A%20to%20Z/6-other-devices/) to the <BrandName /> <ControllerName />.

### 2. Check the grid power limits
In the settings, the grid power limits should be set correctly. Click Settings and check the highlighted setting in the image.
If necessary, adjust the settings.

### 3. Check the address
Make sure [the address is set correctly](/Controller/Configuration%20from%20A%20to%20Z/4-location/).

> [!WARNING]
> The integration may not work correctly if the address is not correct!

## Enabling 'CKW'
From the commissioning interface, go to the 'External Signals' tab.
<ClickableImage src="/img/generic/add-external-datasources-en.png" alt="Image 1" maxWidth="650px" />

Click on 'Energy Markets'.
<ClickableImage src="/img/controller/external signals/types.png" alt="Image 1" maxWidth="650px" />

Select 'CKW' and click 'Next'.

Select the control tier which is applicable to your installation.

### Tier 1 - Setpoint Follower

Setpoints received from CKW are sent directly to the devices. No local control is done by the <BrandName /> <ControllerName />.

### Tier 2 - Delta Stacking

The <BrandName /> <ControllerName /> executes its own self-consumption algorithm, CKW uses the battery availability to activate the battery on ancilliary markets.

### Tier 3 - Battery Splitting

Work in progress.

The battery is split into two virtual batteries. One part is controller by CKW on various ancilliary energy markets, while the remaining portion of the battery is used for local control only.

## Device Selection

In the next page, you have the option to include/exclude devices for remote control.
Ensure to mark all checkboxes of devices you'd like to include.

> [!NOTE]
> When using multiple devices, they are aggregated into one (virtual) asset, per asset type, for CKW.

<ClickableImage src="/img/generic/add-external-datasources-devices-en.png" alt="Image 1" maxWidth="650px" />

'CKW' is now set up on the <BrandName /> <ControllerName />.



# Companion Energy


import { BrandName, ControllerName, CustomerName, InsightsName, InsightsUrl } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';
import CountriesSupportTable from '@site/src/components/CountriesSupportTable';

<img
    src="/img/sgo/Logo_Companion.png"
    alt="Companion logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

# Setting up Companion

The manual describes the steps to set up Companion External Control on the <BrandName /> <ControllerName />.

When setting up this integration, permission is granted to Companion to control the necessary devices.

## Supported Devices

<DeviceSupportTable
  devices={[
    {
        type: 'Solar Inverters',
        variants: 'All',
        customCol: '✅'
    },
    {
        type: 'Storage Devices',
        variants: 'All',
        customCol: '✅'
    },
    {
        type: 'EV Chargers',
        variants: 'All',
        customCol: '❌'
    }
  ]}
    showVariants={true}
    customColumns={{ "customCol": "Supported" }}
/>

## Supported Countries

<CountriesSupportTable
  countries={[
    {
        country: 'Belgium',
        customCol: '✅'
    },
    {
        country: 'Netherlands',
        customCol: '❌'
    },
  ]}
    showVariants={true}
    customColumns={{ "customCol": "Supported" }}
/>

## Prerequisites

### 1. Add the batteries
[Login to the commissioning interface](/Controller/Configuration%20from%20A%20to%20Z/2-accessing-commissioning-interface/) and make sure the [devices are added](/Controller/Configuration%20from%20A%20to%20Z/6-other-devices/) to the <BrandName /> <ControllerName />.

### 2. Check the grid power limits
In the settings, the grid power limits should be set correctly. Click Settings and check the highlighted setting in the image.
If necessary, adjust the settings.

## Add 'Companion - External Control'
<ClickableImage src="/img/generic/add-external-datasources-en.png" alt="Image 1" maxWidth="650px" />
<ClickableImage src="/img/generic/add-external-datasources-kind-en.png" alt="Image 1" maxWidth="650px" />


In the next page, you have the option to include/exclude devices for remote control.
Ensure to mark all checkboxes of devices you'd like to include.

> [!NOTE]
> When using multiple batteries, they are aggregated into one (virtual) asset for Companion.

<ClickableImage src="/img/generic/add-external-datasources-devices-en.png" alt="Image 1" maxWidth="650px" />

'Companion' is now set up on the <BrandName /> <ControllerName />.

# Dynamic Energy Trading


import { BrandName, ControllerName, CustomerName, InsightsName, InsightsUrl } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';
import CountriesSupportTable from '@site/src/components/CountriesSupportTable';

<img
    src="/img/sgo/Logo_DET.png"
    alt="Dynamic Energy Trading logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

# Setting up Dynamic Energy Trading

## Supported Devices

<DeviceSupportTable
  devices={[
    {
        type: 'Solar Inverters',
        variants: 'All',
        customCol: '⌛ (coming soon)',
    },
    {
        type: 'Storage Devices',
        variants: 'All',
        customCol: '✅'
    },
    {
        type: 'EV Chargers',
        variants: 'All',
        customCol: '❌'
    }
  ]}
    showVariants={true}
    customColumns={{ "customCol": "Supported" }}
/>

## Supported Countries

<CountriesSupportTable
  countries={[
    {
        country: 'Belgium',
        customCol: '❌'
    },
    {
        country: 'Netherlands',
        customCol: '✅'
    },
  ]}
    showVariants={true}
    customColumns={{ "customCol": "Supported" }}
/>

## Notifying DET

DET will automatically be notified that the <BrandName /> <ControllerName /> is ready for steering. 

## Add 'DET' External Signal
<ClickableImage src="/img/generic/add-external-datasources-en.png" alt="Image 1" maxWidth="650px" />
<ClickableImage src="/img/generic/add-external-datasources-kind-en.png" alt="Image 1" maxWidth="650px" />

In the next page, you have the option to include/exclude devices for remote control.
Ensure to mark all checkboxes of devices you'd like to include.

> [!NOTE]
> When using multiple batteries, they are aggregated into one (virtual) asset.

<ClickableImage src="/img/generic/add-external-datasources-devices-en.png" alt="Image 1" maxWidth="650px" />

'DET' is now set up on the <BrandName /> <ControllerName />.

> [!TIP]
> When DET External Control is added, the <BrandName /> <ControllerName /> algorithm has **no control** over the battery's behaviour.

# Dexter


import { BrandName, ControllerName, CustomerName, InsightsName, InsightsUrl } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';
import CountriesSupportTable from '@site/src/components/CountriesSupportTable';

<img
    src="/img/sgo/Logo_Dexter.png"
    alt="Dexter logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

## Supported Devices

<DeviceSupportTable
  devices={[
    {
        type: 'Solar Inverters',
        variants: 'All',
        customCol: '✅'
    },
    {
        type: 'Storage Devices',
        variants: 'All',
        customCol: '❌'
    },
    {
        type: 'EV Chargers',
        variants: 'All',
        customCol: '❌'
    }
  ]}
    showVariants={true}
    customColumns={{ "customCol": "Supported" }}
/>

## Supported Countries

<CountriesSupportTable
  countries={[
        {
        country: 'Belgium',
        customCol: '❌'
    },
    {
        country: 'Netherlands',
        customCol: '✅'
    },
  ]}
    showVariants={true}
    customColumns={{ "customCol": "Supported" }}
/>

## Setting up Dexter - Curtailment

To use the Dexter integration, you need to inform Dexter that you wish to receive curtailment signals on this <BrandName /> <ControllerName />,
because a contract with Dexter is required.

In the <BrandName /> <ControllerName />, you can set up the Dexter integration to receive curtailment signals.
You can find the Dexter integration in the list of external data sources. The following screen will appear:
<ClickableImage src="/img/generic/dexter-setup.png" alt="Image 1" maxWidth="350px" />
The following fields need to be filled in:
- Username: Enter the username provided by Dexter.
- Password: Enter the password provided by Dexter.
- Refresh interval: This is the interval at which the <BrandName /> <ControllerName /> will check for new curtailment signals from Dexter. The default value is 5 seconds, but you can adjust if requested by Dexter.
- Strike price: Consult with Dexter what strike price you should use. This is the price at which the curtailment signal will be activated and will be projected against the forecasted imbalance price given by Dexter.
- Timeout: This is the time in seconds that the <BrandName /> <ControllerName /> will wait for a response from Dexter before timing out. The default value is 5 minutes, after we cancel any curtailment signal that was sent by Dexter.
- Country: Select the country where the <BrandName /> <ControllerName /> is located. This is important for Dexter to determine the correct curtailment signals.
- Version number: This is the version of the Dexter integration. Use the latest version available, which is currently 2.

# Diagnostic tests


import { BrandName, ControllerName, CustomerName, InsightsName, InsightsUrl } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';


# Diagnostics tests
The A- and D-series charge/discharge curves are diagnostic test profiles designed to validate the power control behavior, dynamic response, and sign-handling of flexible energy assets.
They are not intended to optimize energy or revenue, but to prove correct behavior under controlled, repeatable conditions.

Together, these tests answer three core questions:
- Can the asset follow a requested power setpoint accurately?
- How quickly and smoothly does it respond to changes?
- Does it behave symmetrically and safely across charge, discharge, and idle states?

## Supported Devices

<DeviceSupportTable
  devices={[
    {
        type: 'Solar Inverters',
        variants: 'All',
        customCol: '❌',
    },
    {
        type: 'Storage Devices',
        variants: 'All',
        customCol: '✅'
    },
    {
        type: 'EV Chargers',
        variants: 'All',
        customCol: '❌'
    }
  ]}
    showVariants={true}
    customColumns={{ "customCol": "Supported" }}
/>

## How to configure the diagnostic test
1. Go to 'External data sources', followed by 'External Signal'
   <ClickableImage src="/img/generic/add-external-datasources-en.png" alt="Image 1" maxWidth="650px" />
   <ClickableImage src="/img/generic/add-external-datasources-kind-en.png" alt="Image 1" maxWidth="650px" />
2. Look for the Eniris or <BrandName />-logo in the list of providers and click on it.
3. Select 'Diagnostic tests'
4. Provide these two inputs:
    - `Select the test curve to perform`: Select one of the tests from the dropdown menu.
    - `Select the start time of the test (HH:MM) in the UTC timezone`: The test will start on this timestamp. Important,
        the timestamp __must__ be given in the UTC timezone. If you are not sure what this means, go
        to https://time.is/UTC to get the UTC time, and add 5 minutes. The test will automatically start in 5 minutes.
    - `Maximum charge and discharge power in kW`: The tests maximum charge and discharge will be scaled towards this value.
       In the images below, the test is scaled to 100 kW.


## Test types
### A-curves
A-curves are short tests to do an initial (and fast) test of the system performance.
<ClickableImage src="/img/generic/diagnostic-tests/a1.png" alt="Image 1" maxWidth="600px" />
<ClickableImage src="/img/generic/diagnostic-tests/a2.png" alt="Image 1" maxWidth="600px" />
<ClickableImage src="/img/generic/diagnostic-tests/a3.png" alt="Image 1" maxWidth="600px" />

### D-curve
The D-curve is implemented by design of the Swiss TSO (Swissgrid) to mimic a prequalification test.
<ClickableImage src="/img/generic/diagnostic-tests/d.png" alt="Image 1" maxWidth="600px" />


# DNO Relay Control


import { BrandName, ControllerName, CustomerName, InsightsName, InsightsUrl } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';
import CountriesSupportTable from '@site/src/components/CountriesSupportTable';

<img
    src="/img/sgo/Logo_DNO.png"
    alt="DNO logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

# Setting up DNO Relay Control

The manual describes the steps to set up DNO Relay Control on the <BrandName /> <ControllerName />.

When setting up this integration, permission is granted to DNO to control the necessary devices.

## Supported Devices

<DeviceSupportTable
  devices={[
    {
        type: 'Solar Inverters',
        variants: 'All',
        customCol: '✅'
    },
    {
        type: 'Storage Devices',
        variants: 'All',
        customCol: '✅'
    },
    {
        type: 'EV Chargers',
        variants: 'All',
        customCol: '❌'
    }
  ]}
    showVariants={true}
    customColumns={{ "customCol": "Supported" }}
/>

## Supported Countries

<CountriesSupportTable
  countries={[
    {
        country: 'Belgium',
        customCol: '❌'
    },
    {
        country: 'Netherlands',
        customCol: '✅'
    },
  ]}
    showVariants={true}
    customColumns={{ "customCol": "Supported" }}
/>

## Prerequisites

### 1. Add the batteries and solar inverters
[Login to the commissioning interface](/Controller/Configuration%20from%20A%20to%20Z/2-accessing-commissioning-interface/) and make sure the [devices are added](/Controller/Configuration%20from%20A%20to%20Z/6-other-devices/) to the <BrandName /> <ControllerName />.

### 2. Add the Digital Inputs
This external signal operates using digital input devices which are connected to the <BrandName /> <ControllerName />.
The digital inputs can be connected using [DS1242](/Controller/Accessories/ds1242-Ethernet-Relay-module/) or other relay modules.

At least TWO digital inputs are required. These are used for battery control. A third digital input can be connected for PV-curtailment.

### 3. Check the grid power limits
In the settings, the grid power limits should be set correctly. Click Settings and check the highlighted setting in the image.
If necessary, adjust the settings.

## Add 'DNO- Relay Control'
<ClickableImage src="/img/generic/add-external-datasources-en.png" alt="Image 1" maxWidth="650px" />
<ClickableImage src="/img/generic/add-external-datasources-kind-en.png" alt="Image 1" maxWidth="650px" />


In the next page, you have the option to include/exclude devices for remote control.
Ensure to mark all checkboxes of devices you'd like to include.

> [!NOTE]
> When using multiple devices of the same type, they are aggregated into one (virtual) asset.

<ClickableImage src="/img/generic/add-external-datasources-devices-en.png" alt="Image 1" maxWidth="650px" />

'DNO Relay Control' is now set up on the <BrandName /> <ControllerName />.


# Fluvius (direct connection)


import { BrandName, ControllerName } from '@site/src/components/customFields';
import ClickableImage from '@site/src/components/ClickableImage';

<img src="/img/sgo/Logo_Fluvius.png" alt="Fluvius Logo" style={{ display: "block", margin: "0 auto", width: "20%"}}/>

<br/>
# Adding Fluvius Telecontrole RTU

The manual describes the steps to set up the Fluvius Telecontrole RTU on the <BrandName /> <ControllerName />.

## Step 1: Network configuration

Required network configuration for Fluvius on **network port 2** (this is the upper port of the two – connect this to the Fluvius RTU):

<ClickableImage src="/img/fluvius/step1-network-configuration.png" alt="Network configuration for Fluvius on Ethernet port 2" maxWidth="500px" />

## Step 2: Verify the voltages of the devices

For certain reactive power control modes, the medium voltage must be measured. If the main grid meter measures the medium voltage grid, then in the settings make sure to set this correctly:

<ClickableImage src="/img/fluvius/step2-grid-settings.png" alt="Grid system and phase-phase voltage settings" maxWidth="600px" />

If there are also lower voltage devices in the system, you must adjust their voltage settings as well in the device settings. For example:

<ClickableImage src="/img/fluvius/step2-device-voltage.png" alt="Operating voltage and nominal voltage in the device settings" maxWidth="600px" />

## Step 3: Add the Fluvius Telecontrol external signal

#### 1. Click on '**External Signals**' in the top menu and click on the 'Start wizard' button.

<ClickableImage src="/img/fluvius/step3-choose-data-source-1.png" alt="Add a new external signal" maxWidth="600px" />

#### 2. Choose '**Distribution system operator / grid operator**', select '**Fluvius**', then select '**Fluvius Telecontrole**' as the data source and click 'Next'.

<ClickableImage src="/img/fluvius/step3-choose-data-source-2.png" alt="Choose the Fluvius Telecontrole data source" maxWidth="500px" />

#### 3. Fill in the required information and click 'Submit'.

1. **Installed active power as defined by Fluvius (kW)**: The installed active power as agreed upon with Fluvius.
2. **Nominal grid voltage (kV)**: The nominal voltage of the grid to which the installation is connected.
3. **Enable reactive power control by the <BrandName /> <ControllerName />**: Whether the <ControllerName /> performs reactive power control.
4. **Local reactive operation mode**: The reactive operation mode according to the grid study of Fluvius (e.g. 'Q/P control or cos phi control').
5. **Submode of the reactive operation mode**: The submode according to the grid study of Fluvius.
6. **Timeout (seconds)**: The site default strategy is applied after the Fluvius RTU has disconnected or deactivated the connection for this time.

<ClickableImage src="/img/fluvius/step3-additional-input.png" alt="The data source requires some additional input" maxWidth="700px" />

> [!TIP]
> First test with reactive power control disabled, and then enable it. This helps separate active and reactive power control.


# Fluvius (through an EME eCON++ gateway)


import { BrandName, ControllerName } from '@site/src/components/customFields';

<img src="/img/sgo/Logo_Fluvius.png" alt="Fluvius Logo" style={{ display: "block", margin: "0 auto", width: "20%"}}/>

<br/>
# Fluvius Telecontrole through an EME eCON++ Gateway

> [!WARNING] Prefer the native Fluvius Telecontrole support
> The <BrandName /> <ControllerName /> can talk to the Fluvius Telecontrole RTU directly, without an
> EME eCON++ Gateway or any other gateway in between. That setup is recommended and easier to commission, but it
> requires a <BrandName /> <ControllerName /> with two ethernet ports, because the Fluvius RTU is connected to a
> network port of its own. Only use the external signal driver described on this page when the installation
> already has an EME eCON++ Gateway.
> See [Adding Fluvius Telecontrole RTU](/Controller/External%20Signals/DSO/fluvius#adding-fluvius-telecontrole-rtu).

This external signal driver is used when Fluvius Telecontrole v4 is not connected
to the <BrandName /> <ControllerName /> directly, but through an **EME eCON++ Gateway**.

> [!IMPORTANT] The EME eCON++ Gateway device must be added first
> This external signal driver does not talk to the gateway itself. It reads the Fluvius commands from the
> **EME eCON++ Fluvius Telecontrole v4 Gateway** device, which must already be added to the site, and it needs the
> grid limits of the site to convert the setpoint percentages into power limits. The full procedure — network,
> grid limits, device and external signal driver — is described in
> [EME eCON++ Fluvius Telecontrole v4 Gateway](/Devices/PLC/eme-econ-fluvius-telecontrole-v4/).

## Adding the external signal driver

1. Click **External Signals** in the top menu and click the *Start wizard* button.
2. Choose **Distribution system operator / grid operator**, select **Fluvius**, then select
   **Eme Fluvius Modbus TCP** as the external signal driver and click *Next*.

This external signal driver has no additional input fields: everything it needs comes from the EME eCON++ Gateway
device and from the grid limits of the site.


# DSO


import { FolderOverview } from '@/components/FolderOverview';

# DSO

<FolderOverview folder="Controller/External Signals/DSO" />


# ORES


import { BrandName, ControllerName, CustomerName, InsightsName, InsightsUrl } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img src="/img/sgo/Logo_ORES.png" alt="ORES Logo" style={{ display: "block", margin: "0 auto", width: "40%"}}/>

<br/>
# Setting up ORES (External Control)

The manual describes the steps to set up ORES External Control on the <BrandName /> <ControllerName />.

When setting up this integration, permission is granted to ORES to control the necessary devices.

## Supported Devices

<DeviceSupportTable
  devices={[
    {
        type: 'Solar Inverters',
        customCol: '✅'
    },
    {
        type: 'Storage Devices',
        customCol: '✅'
    },
    {
        type: 'EV Chargers',
        customCol: '❌'
    }
  ]}
    customColumns={{ "customCol": "Supported" }}
/>

> [!CAUTION]
> ORES RTU requires a relay and a digital input to work. Please check if your <BrandName /> <ControllerName /> has an available relay and digital input before setting up this integration.
> If not, you can use a [Relay-Ethernet Converter](/Controller/Accessories/relay-ethernet) to connect the ORES RTU to the <BrandName /> <ControllerName />.

> [!CAUTION]
> ORES RTU requires a RS485 serial port to work. Please check if your <BrandName /> <ControllerName /> has an available RS485 port before setting up this integration.
> If not, you can use a [RS485-Ethernet Converter](/Controller/Accessories/rs485-ethernet#connecting-to-the-rs485-converter) or a [RS485-USB Converter](/Controller/Accessories/rs485-usb) to connect the ORES RTU to the <BrandName /> <ControllerName />.

> [!CAUTION]
> As ORES RTU is using a RS485 serial connection, the used RS485 port on the <BrandName /> <ControllerName /> cannot be used for other devices and connections. Please check if your <BrandName /> <ControllerName /> has an available RS485 port before setting up this integration.

## Prerequisites

### 1. Add the batteries and inverters
[Login to the commissioning interface](/Controller/Configuration%20from%20A%20to%20Z/2-accessing-commissioning-interface/) and make sure the [devices are added](/Controller/Configuration%20from%20A%20to%20Z/6-other-devices/) to the <BrandName /> <ControllerName />.

### 2. Check the grid power limits
In the settings, the grid power limits should be set correctly. Click Settings and check the highlighted setting in the image. If necessary, adjust the settings.

### 3. Add 'ORES' External Signal

<br/>

#### 1. Click on '**External Signals**' in the top menu and click on the 'Start Wizard' button.

<ClickableImage src="/img/generic/add-external-datasources-devices-new-en.png" alt="Step 1" />

#### 2. Click on the '**Distribution System Operator**' button.

<ClickableImage src="/img/generic/add-external-datasources-kind-new-en.png" alt="Step 2" />

#### 3. Click on the 'ORES' button.

<br/>

#### 4. Select '**ORES RTU Telecontrol**' and click 'Next'.

<br/>

#### 5. Fill in the required information.

1. **RS485 Interface**: Select the RS485 serial port to which the ORES RTU is connected. If using a RS485-Ethernet Converter or a RS485-USB Converter, select the corresponding Ethernet or USB port.
2. **Digital Input Device**: Select the digital input device to which the ORES RTU is connected, this is used for the ORES RTU to detect if the connection with ORES is active.
3. **Relay Device**: Select the relay device to which the ORES RTU is connected, this is used for the ORES RTU to control the connection with ORES. If the relay is activated, the connection with ORES is active and ORES can control the devices. If the relay is deactivated, the connection with ORES is lost and ORES cannot control the devices.
4. **Contractual permanent power**: Fill in the contractual permanent power (in kW) that is agreed upon with the grid operator. This is used by our EMS to determine the maximum power that can be injected into the grid if we lose connection with ORES.

#### 6. Select **all the available devices**, this is required for ORES to be able to control the devices. Then click 'Submit'.

<br/>

## Application example: decoupling cabinet

For an installation with a main and back-up switch, see [ORES: decoupling cabinet and I/O expansion](/Controller/External%20Signals/DSO/ORES-decoupling-cabinet). This separate application note explains the signal connections, I/O allocation and dS1242/dS3484 expansion.


# ORES: decoupling cabinet and I/O expansion


import { BrandName, ControllerName } from '@site/src/components/customFields';
import ClickableImage from '@site/src/components/ClickableImage';

# ORES: decoupling cabinet and I/O expansion

This application note extends the [ORES setup guide](/Controller/External%20Signals/DSO/ORES) for an installation with an ORES RTU, inverter control, a decoupling cabinet and a separate back-up circuit breaker, as found in a Phoenix Pilot style arrangement. Follow the original guide to configure ORES External Control; use this page to design the additional contact interface.

The available **digital inputs and potential-free relay outputs of the <BrandName /> <ControllerName /> are used for this interface**. Digital inputs read external contacts; relay outputs switch the designated control circuits. When the available channels are insufficient, add an Ethernet I/O module such as the **dS1242 or dS3484** and configure the additional channels.

**P** means the main switch, **BU** the back-up switch, **DI** a digital input and **RO** a potential-free relay output. The diagrams below describe functions and signal directions. Terminal numbering, voltages and contact states follow the project's electrical drawings.

<span id="how-the-functions-fit-together" />

## System architecture

<ClickableImage src="/api/media/agent-uploads/Controller/External-Signals/DSO/ORES-decoupling-cabinet/ores-functional-schematic.png" alt="ORES functional signal schematic: RTU, SmartgridOne and I/O expansion, decoupling cabinet, back-up circuit breaker and independent grid protection" maxWidth="1140px" />

*Select the diagram to view it at full size.*

The example allocates **7 DI and 3 relay outputs**. DI and RO numbers identify logical functions; map them to the available controller and extension-module channels. Dashed connections represent the additional project-configured cabinet commands. The standard ORES interface uses the RTU watchdog input and controller availability relay; the protection circuits retain their independent function.

### Inverter communication and power control

The controller receives ORES power commands through the RTU interface and applies the corresponding regulation to the connected inverters. In an arrangement containing a Phoenix Pilot box, this is the inverter communication and power-control function. The RTU connection uses a dedicated RS485 interface; the inverter communication uses another interface. Keep a single controller responsible for writing the inverter control setpoints.

<span id="contact-interface-to-the-rtu-and-cabinet" />

### RTU and cabinet contact interface

This diagram shows the **7 DI / 3 RO example** detailed below. An Ethernet I/O module exchanges its channel states with the controller over Modbus TCP. Existing controller I/O and extension-module I/O are combined in the channel allocation.

The standard ORES wizard assigns **one RTU watchdog input and one controller availability relay**. The two switch-command inputs, switch-position inputs and two cabinet command outputs are additional project functions. Their signal mapping, interlocks and operating sequence must be configured for the installation; adding the ORES external signal does not automatically create this cabinet logic.

### Grid protection and tripping

The voltage/frequency protection relay, trip circuits, interlocks and back-up protection retain their electrical protection function. The controller handles power regulation and the configured contact interface. Its presence does not replace the protection relay or establish the protection timing of the installation.

<span id="why-the-cabinet-needs-so-many-connections" />

## Cabinet signals and terminal allocation

<ClickableImage src="/api/media/agent-uploads/Controller/External-Signals/DSO/ORES-decoupling-cabinet/ores-terminal-groups.png" alt="Terminal allocation: six protection-contact terminals, six position-feedback terminals and two back-up trip-coil terminals" maxWidth="1140px" />

*Select the diagram to view it at full size. The grouping shows signal functions, not electrical bridges.*

The cable cores carry several different functions: commands, actual switch positions, protection status and trip-coil power. A terminal pair is not two independent commands, and a six-terminal connector is not necessarily six inputs.

| Signal designation | Function | Terminal and I/O allocation |
| --- | --- | --- |
| **WD Relais** | Availability contact of the protection relay | One contact circuit, normally represented by two terminals. This is distinct from the controller's **Wd PLC** signal. |
| **Trip 1 / Trip 2** | Separate protection trip circuits | Two contact circuits, normally four terminals in total. Retain their individual functions in the protection design. |
| **Status P / P NO / P NC** | Main-switch common and complementary auxiliary contacts | Three terminals; two DI when both open and closed indications are monitored. |
| **Status BU / BU NO / BU NC** | Back-up-switch common and complementary auxiliary contacts | Three terminals; two DI when both indications are monitored. |
| **MX 1+ / MX 1-** | Supply circuit for the back-up trip coil | Two coil terminals; these do not count as two digital inputs. |

These groups account for **14 terminals: 6 protection-contact terminals + 6 position-contact terminals + 2 coil terminals**. They do not represent 14 controller commands. Count the actual signals that the controller must read or switch, then allocate the corresponding channels.

Reading both auxiliary contacts provides separate open and closed indications. Define which contact combinations are valid and how long a transition may take. A relay command proves that a command was issued; the switch auxiliary contacts provide the actual position feedback.

<span id="io-allocation-for-this-example" />

## I/O requirements and signal allocation

The following allocation assumes that both main and back-up switch positions are read by the controller, both RTU switch commands enter the controller, and the controller has one independent command output for each switch circuit.

| Function | DI | RO | Assignment |
| --- | ---: | ---: | --- |
| Watchdog RTU | 1 | 0 | RTU contact to the watchdog input selected in the ORES wizard |
| Wd PLC / controller availability | 0 | 1 | Controller relay contact to the RTU availability input |
| P open and P closed | 2 | 0 | Two main-switch auxiliary indications |
| BU open and BU closed | 2 | 0 | Two back-up-switch auxiliary indications |
| Switch P and Switch BU | 2 | 0 | Two separate RTU command contacts |
| P and BU command circuits | 0 | 2 | Two independent, project-configured relay outputs |
| **Example total** | **7** | **3** | Excludes additional alarms and spare capacity |
| Optional Err V and Err Fq monitoring | **+2** | **0** | Separate voltage and frequency fault indications, if provided |

With the two optional fault indications, the allocation becomes **9 DI / 3 RO**. This is the channel budget for this example, not a universal ORES requirement. The standard ORES connection remains **1 DI / 1 RO plus dedicated RS485**. If the RTU commands act directly on the cabinet and the controller does not process them, those two command inputs and two command outputs are not part of the controller's allocation.

This budget assumes any additional hardwired status reporting to the RTU is provided through suitable auxiliary contacts or isolated interfaces. If the controller must reproduce P/BU positions or fault indications through separate relay outputs to the RTU, add those outputs individually. Do not assume that one physical contact can be shared between two independently supplied input circuits.

<span id="choosing-the-io-extension" />

## I/O expansion module selection

Subtract the **unused, electrically suitable** controller channels from the budget before selecting the extension. Reserve the ORES watchdog input and availability relay as part of that calculation.

| Module | Potential-free changeover relays | Shared digital I/O configured as inputs | Interface / supply |
| --- | ---: | ---: | --- |
| **dS1242** | 2 | Up to 4 | Ethernet Modbus TCP / 12 V DC |
| **dS3484** | 4 | Up to 8 | Ethernet Modbus TCP / 12 V DC |

For the **7 DI / 3 RO** example:

- **One dS1242 plus at least 3 free controller DI and 1 free controller RO** supplies all required channels.
- **Two dS1242 modules** supply 8 DI and 4 RO when all shared I/O channels are configured as inputs.
- **One dS3484** supplies 8 DI and 4 RO, leaving 1 DI and 1 RO spare.
- For **9 DI / 3 RO**, provide at least one additional DI beyond the eight available on one dS3484 or two dS1242 modules.

The shared digital I/O channels can also operate as NPN outputs. An NPN output is not a potential-free relay contact, and using a shared channel as an output reduces the available input count. Use an electrically suitable interposing relay where a transistor output must switch an isolated contact circuit.

Follow the [dS1242 Ethernet relay module guide](/Controller/Accessories/ds1242-Ethernet-Relay-module) for the module connection and commissioning workflow. Register each required input and relay channel in the controller, using the physical channel count of the installed model. The dS1242 has two relay channels and four digital I/O channels; a longer channel list in a shared device driver does not add physical channels.

## Electrical connection and commissioning

1. **Document the signal list.** For every DI and RO, record the source, destination, common terminal, normal state, active state and loss-of-power state. Keep **Watchdog RTU**, **Wd PLC** and **WD Relais** as distinct signals.
2. **Match the electrical interfaces.** Use dry contacts with the module's specified input reference. Do not apply a 24 V or mains signal to an input specified for dry contacts. Keep separately supplied input circuits isolated where required.
3. **Design each coil circuit.** The relay switches the designated control supply. Check coil voltage, AC/DC type, inrush, inductive switching rating and pulse duration; use interposing relays or contactors where required. A resistive contact rating alone does not establish trip-coil suitability.
4. **Configure the base ORES connection.** Follow the [original setup guide](/Controller/External%20Signals/DSO/ORES), select the allocated watchdog input and availability relay, and set contractual permanent power. Configure cabinet commands and feedback as the separate project functions described above.
5. **Verify actual behaviour.** Test every input and output against the signal list, including open/closed feedback and command interlocks. Test RTU watchdog loss, controller restart, loss of the Ethernet I/O connection and protection tripping. Confirm the specified fallback and recovery behaviour and the independent operation of the protection circuit.

The standard ORES driver energises the controller availability relay during operation; this is not automatically a pulsed heartbeat. Match the RTU's expected contact behaviour. Loss of the RTU watchdog input invokes the configured contractual-power fallback. Confirm the input polarity and recovery sequence during commissioning.

See also [wiring and connectivity guidelines](/Controller/wiring-best-practices), [relay-Ethernet converters](/Controller/Accessories/relay-ethernet) and the [dS1242 module guide](/Controller/Accessories/ds1242-Ethernet-Relay-module).


# Poland — one controller for multiple PV inverters


# One central controller for multiple PV inverters in Poland

Polish distribution system operators (DSOs) are placing increasingly strict requirements on the control of PV plants. When a plant contains several inverters, the DSO may need to limit or shut down the complete installation as one system.

SmartgridOne supports this **integrator function** by forming the central connection between the DSO and all participating inverters. In this context, an integrator is the plant controller or gateway that translates one external command into the correct command for every connected inverter.

> [!IMPORTANT] Project-specific DSO approval
> Interface requirements differ between Polish DSOs and connection types. Treat the architecture below as a design pattern, not as a pre-approved configuration. Obtain the DSO's current technical requirements before engineering and commissioning the site.

## How the architecture works

<div className="not-prose my-8 rounded-2xl border border-orange-200/80 bg-gradient-to-br from-orange-50 via-white to-slate-50 p-5 shadow-sm dark:border-orange-900/60 dark:from-orange-950/25 dark:via-slate-950 dark:to-slate-900">
  <div className="mb-5 flex flex-wrap items-center justify-between gap-2">
    <strong className="text-sm text-slate-900 dark:text-slate-100">One plant-level command path</strong>
    <span className="rounded-full bg-orange-100 px-3 py-1 text-xs font-semibold text-orange-800 dark:bg-orange-950 dark:text-orange-200">Polish multi-inverter PV plant</span>
  </div>
  <div aria-label="A Polish DSO sends one command to SmartgridOne, which translates and distributes the command to multiple PV inverters" className="grid items-stretch gap-3 md:grid-cols-[minmax(0,1fr)_auto_minmax(0,1.15fr)_auto_minmax(0,1.35fr)] md:items-center">
    <div className="rounded-xl border border-slate-200 bg-white p-4 dark:border-slate-700 dark:bg-slate-900">
      <span className="text-xs font-bold uppercase tracking-wider text-slate-500 dark:text-slate-400">External command</span>
      <strong className="mt-1 block text-base text-slate-950 dark:text-white">Polish DSO</strong>
      <span className="mt-1 block text-sm leading-6 text-slate-600 dark:text-slate-300">Sends a plant limit, release, or shutdown command.</span>
    </div>
    <div aria-hidden="true" className="grid place-items-center text-2xl font-bold text-orange-600 rotate-90 md:rotate-0">→</div>
    <div className="rounded-xl border-2 border-orange-300 bg-orange-50 p-4 dark:border-orange-700 dark:bg-orange-950/40">
      <span className="text-xs font-bold uppercase tracking-wider text-orange-700 dark:text-orange-300">Central integrator</span>
      <strong className="mt-1 block text-base text-slate-950 dark:text-white">SmartgridOne</strong>
      <span className="mt-1 block text-sm leading-6 text-slate-600 dark:text-slate-300">Validates, translates, and distributes the command.</span>
    </div>
    <div aria-hidden="true" className="grid place-items-center text-2xl font-bold text-orange-600 rotate-90 md:rotate-0">→</div>
    <div className="rounded-xl border border-slate-200 bg-white p-4 dark:border-slate-700 dark:bg-slate-900">
      <span className="text-xs font-bold uppercase tracking-wider text-slate-500 dark:text-slate-400">Coordinated plant</span>
      <strong className="mt-1 block text-base text-slate-950 dark:text-white">Multiple PV inverters</strong>
      <div className="mt-3 grid grid-cols-3 gap-2 text-center text-xs font-semibold text-slate-700 dark:text-slate-200">
        <span className="rounded-lg bg-slate-100 px-2 py-2 dark:bg-slate-800">PV 01</span>
        <span className="rounded-lg bg-slate-100 px-2 py-2 dark:bg-slate-800">PV 02</span>
        <span className="rounded-lg bg-slate-100 px-2 py-2 dark:bg-slate-800">PV 03+</span>
      </div>
    </div>
  </div>
</div>

The DSO does not have to address each inverter separately. It sends one command to SmartgridOne, which applies the appropriate command to every selected inverter. This enables the complete PV plant to be:

- limited to a common power level;
- shut down completely;
- released back to normal operation;
- monitored centrally; and
- controlled against one shared setpoint.

## Support for mixed inverter fleets

PV plants do not always consist of identical inverters. Extensions in particular may combine different brands, models, nominal powers, and communication interfaces.

SmartgridOne can bring several devices and protocols together within one installation. Each inverter remains individually addressable by the controller, while the DSO sees and controls a single coordinated plant.

This architecture is suitable for:

- installations with two or more inverters;
- inverters using different Modbus addresses;
- combinations of different manufacturers;
- existing plants that are expanded later; and
- hybrid sites with PV, battery storage, and other controllable equipment.

## Communication through Modbus and SunSpec

For multi-inverter plants, Polish DSOs commonly request one shared controller. Communication with that controller is often implemented through **RS485** and the **SunSpec protocol**.

SmartgridOne acts as the central gateway: it receives the external command and converts it into the correct instructions for the connected inverters. Depending on the project, the connection may use RS485, Ethernet, or an appropriate protocol converter.

| Connection layer | Typical interface | Function |
| --- | --- | --- |
| DSO to SmartgridOne | RS485 and SunSpec, as specified by the DSO | Transfers plant-level commands and any required feedback |
| SmartgridOne to inverters | Supported local device protocol over RS485 or Ethernet | Translates and distributes the command per inverter |
| Optional legacy shutdown | Relay or contactor | Provides full on/off control where no suitable data interface exists |

The exact interface, SunSpec configuration, command set, scaling, and feedback requirements must follow the technical specification of the DSO involved in the project.

## Older inverters without external control

Not every inverter provides Modbus or another usable external-control protocol. Such devices can still be included in some projects by letting SmartgridOne operate an external relay or contactor.

> [!CAUTION]
> A relay or contactor provides **full on/off control only**. Accurate active-power limiting is possible only when the inverter supports the required command through its communication interface. The electrical shutdown circuit must be designed and installed by qualified personnel.

## Safe behaviour if communication is lost

An integrator design must define what happens when communication with the DSO or a controlled device is interrupted. SmartgridOne supports watchdog and fallback functions so that an agreed safe state can be applied when no valid control command is received within a configured time.

Depending on the DSO's requirements, the plant can be configured to:

- fall back to a predefined power level;
- reduce production to zero;
- shut down the inverters; or
- be physically disconnected through a contactor.

The selected fail-safe behaviour must be verified during engineering and tested as part of commissioning.

## Project-specific engineering

Because requirements vary by Polish DSO and connection type, Eniris reviews each integrator solution individually. The review covers at least:

- the DSO responsible for the grid connection;
- the inverter manufacturers, models, firmware versions, and quantities;
- the required SunSpec commands and feedback values;
- the necessary RS485, Ethernet, and network connections;
- the timeout and required behaviour after communication loss;
- whether an external relay or contactor is needed; and
- the acceptance tests that must be completed during commissioning.

This creates one central, coordinated, and future-ready control system for the complete PV plant.

## Prepare your project

To assess a multi-inverter project, provide Eniris with:

1. the electrical single-line diagram;
2. the make, exact model, firmware version, and nominal power of every inverter;
3. the local DSO's current interface and control specification; and
4. the planned communication path, network details, and requested commissioning date.

Submit the available technical information through the [Eniris integration request form](https://www.eniris.com/integration_request). Eniris will determine the appropriate SmartgridOne configuration and identify any project-specific engineering or hardware requirements.


# RESA


import { BrandName, ControllerName, CustomerName, InsightsName, InsightsUrl } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img src="/img/sgo/Logo_RESA.png" alt="RESA Logo" style={{ display: "block", margin: "0 auto", width: "40%"}}/>

<br/>
# Setting up RESA (External Control)

The manual describes the steps to set up RESA External Control on the <BrandName /> <ControllerName />.

When setting up this integration, permission is granted to RESA to control the necessary devices.

## Supported Devices

<DeviceSupportTable
  devices={[
    {
        type: 'Solar Inverters',
        customCol: '✅'
    },
    {
        type: 'Storage Devices',
        customCol: '✅'
    },
    {
        type: 'EV Chargers',
        customCol: '❌'
    }
  ]}
    customColumns={{ "customCol": "Supported" }}
/>

> [!CAUTION]
> RESA RTU requires a RS485 serial port to work. Please check if your <BrandName /> <ControllerName /> has an available RS485 port before setting up this integration.
> If not, you can use a [RS485-Ethernet Converter](/Controller/Accessories/rs485-ethernet#connecting-to-the-rs485-converter) or a [RS485-USB Converter](/Controller/Accessories/rs485-usb) to connect the RESA RTU to the <BrandName /> <ControllerName />.

> [!CAUTION]
> As RESA RTU is using a RS485 serial connection, the used RS485 port on the <BrandName /> <ControllerName /> cannot be used for other devices and connections. Please check if your <BrandName /> <ControllerName /> has an available RS485 port before setting up this integration.

## Prerequisites

### 1. Add the batteries and inverters
[Login to the commissioning interface](/Controller/Configuration%20from%20A%20to%20Z/2-accessing-commissioning-interface/) and make sure the [devices are added](/Controller/Configuration%20from%20A%20to%20Z/6-other-devices/) to the <BrandName /> <ControllerName />.

### 2. Check the grid power limits
In the settings, the grid power limits should be set correctly. Click Settings and check the highlighted setting in the image. If necessary, adjust the settings.

### 3. Add 'RESA' External Signal

<br/>

#### 1. Click on '**External Signals**' in the top menu and click on the 'Start Wizard' button.

<ClickableImage src="/img/generic/add-external-datasources-devices-new-en.png" alt="Step 1" />

#### 2. Click on the '**Distribution System Operator**' button.

<ClickableImage src="/img/generic/add-external-datasources-kind-new-en.png" alt="Step 2" />

#### 3. Click on the 'RESA' button.

<br/>

#### 4. Select '**RESA RTU Telecontrol**' and click 'Next'.

<br/>

#### 5. Fill in the required information.

1. **RS485 Interface**: Select the RS485 serial port to which the RESA RTU is connected. If using a RS485-Ethernet Converter or a RS485-USB Converter, select the corresponding Ethernet or USB port.
2. **M1 Energy Type**: Select the M1 Energy Type that corresponds to the devices you want to control with RESA. This should be set to 'Battery' if you want to control the storage or 'Solar' if you want to control the solar inverters.
3. **M2 Power Type**: Select the M2 Power Type that corresponds to the devices you want to control with RESA. This should be set to 'Battery' if you want to control the storage or 'Solar' if you want to control the solar inverters. This can also be set to 'N/A' if you only have one type of device.
4. **Contractual permanent power**: Fill in the contractual permanent power (in kW) that is agreed upon with the grid operator. This is used by our EMS to determine the maximum power that can be injected into the grid if we lose connection with RESA.

#### 6. Select **all the available devices**, this is required for RESA to be able to control the devices. Then click 'Submit'.

<br/>


# Switzerland — DSO telecontrol and curtailment


import { BrandName, ControllerName } from '@site/src/components/customFields';

# Swiss DSO telecontrol and curtailment

In Switzerland, a distribution system operator (DSO) may require an installation to react to remote grid-control commands. Depending on the project, these commands can arrive as relay contacts from a **ripple-control receiver** (*Rundsteuerempfänger*) or through a local or cloud gateway.

This guide explains both approaches and, most importantly, where the standard configuration ends and a project-specific telecontrol integration begins.

> [!IMPORTANT]
> Obtain the DSO's approved interface description and signal truth table before wiring or configuring the installation. Signal polarity, permitted-power levels, reactive-power requirements, feedback signals and fail-safe behaviour are project-specific.

## Choose the correct integration path

| DSO interface | Use this path | Availability |
| --- | --- | --- |
| One or two relay signals for active-power limitation | [Standard ripple-control configuration](#standard-ripple-control-configuration) | Available through the commissioning interface |
| Modbus TCP, IEC 60870-5-104 or another local gateway protocol | [Project-specific gateway integration](#project-specific-gateway-integration) | Requires a technical feasibility review and an agreed data-point list |
| Cloud API or MQTT | [Project-specific gateway integration](#project-specific-gateway-integration) | Requires a technical feasibility review and an agreed security and data model |
| Reactive-power commands (Q, cos φ or power factor) | [Active power versus reactive power](#active-power-versus-reactive-power) | Not handled by the standard Swiss DSO relay strategies |

## Standard ripple-control configuration

The <BrandName /> <ControllerName /> provides two standard Swiss DSO external-signal strategies. Both read one or two digital input devices and apply a configurable percentage of nominal active power.

| Strategy in the wizard | Controlled assets | What is limited |
| --- | --- | --- |
| **Swiss DSO Solar Peak Limiter** | Controllable solar inverters | Solar production |
| **Swiss DSO Power Limiter** | Controllable batteries, EV chargers and heat pumps | Active power of the selected devices |

You can add both strategies at a mixed site when the DSO must control solar production and controllable consumption. Configure and test the applicable assets separately.

> [!NOTE]
> A configured percentage is the **permitted active power as a percentage of the device's nominal power**. It is not the percentage that must be subtracted. A value of `0%` therefore means a zero-active-power command, while `30%` permits up to 30% of nominal power.

### Digital input encoding

With one digital input, the strategy provides binary control:

| DI1 | Result |
| --- | --- |
| `0` | No DSO limit |
| `1` | Configured limit level 1 |

With two digital inputs, four states are available:

| DI1 | DI2 | Result |
| --- | --- | --- |
| `0` | `0` | No DSO limit |
| `0` | `1` | Configured limit level 1 |
| `1` | `0` | Configured limit level 2 |
| `1` | `1` | Configured limit level 3 |

This supports a common four-stage requirement such as `100% / 60% / 30% / 0%`, but the order must come from the DSO's truth table. Enter the permitted-power percentage for each asserted state exactly as approved by the DSO. Do not assume that every receiver uses the same contact order or polarity.

### Hardware and wiring

The OM1 controller has two onboard digital inputs. They accept **5–50 Vdc**. A passive dry contact can be wired using the controller's 12 V wetting supply as shown in the [digital-input wiring guidelines](/Controller/wiring-best-practices/#digital-inputs--relay-outputs).

If the controller has no available onboard inputs, use a supported external input module such as the [dS1242 Ethernet relay module](/Controller/Accessories/ds1242-Ethernet-Relay-module/). The module or channel must appear as an eligible **External Input** in the commissioning wizard.

> [!WARNING]
> Wiring must be carried out by a qualified installer. Never apply an AC signal or a voltage outside the controller or input module rating. Check whether the DSO receiver provides a dry contact or an active voltage output before connecting it.

Do not assume that a generic smart relay is a drop-in replacement. It can only be used when its input channels are supported and appear as selectable External Input devices in the commissioning interface.

### Step 1: add the digital input devices

1. [Open the commissioning interface](/Controller/Configuration%20from%20A%20to%20Z/2-accessing-commissioning-interface/).
2. Open **Devices** and select **Start device wizard**.
3. For an onboard input, choose **Energy Meter → Generic → Relay → Digital Input Device** and select the connected controller input.
4. Repeat this for the second input when four-state control is required.
5. For an external module, add that module first and verify that each required input channel is visible as an External Input device.
6. Change the receiver contacts one at a time and verify that the displayed input states follow the approved truth table.

### Step 2: add the Swiss DSO external signal

1. Open **External Signals** and select **Start wizard**.
2. Choose **Distribution system operator / grid operator**.
3. Select provider **SwissDSO**.
4. Select **Swiss DSO Solar Peak Limiter** for PV curtailment or **Swiss DSO Power Limiter** for batteries, EV chargers and heat pumps.
5. Select **Digital input 1** and enter the permitted-power percentage for limit level 1.
6. Enable the second digital input when four states are required. Select **Digital input 2** and enter the percentages for levels 2 and 3.
7. Select all controllable devices to which the signal must apply.
8. Finish the wizard and confirm that the external signal reports a connected state.

The selected devices must be controllable and must have their nominal power configured. The strategy derives each power limit from that nominal value.

### Step 3: commission every state

Coordinate the acceptance test with the installer and, where required, the DSO.

1. Activate every receiver state separately.
2. Confirm the two digital input values in the commissioning interface.
3. Confirm that the external-signal status shows the expected percentage.
4. Verify the resulting active-power command and the response of every selected asset.
5. Return the receiver to its no-limit state and verify that normal control resumes.
6. Interrupt the receiver or input-module connection and verify the agreed fail-safe behaviour.
7. Record the accepted truth table, polarity, limit values and test result in the commissioning dossier.

## Active power versus reactive power

The standard **Swiss DSO Solar Peak Limiter** and **Swiss DSO Power Limiter** control active power only. Additional relay contacts do not automatically add reactive-power control.

If the DSO requires Q, cos φ, power-factor setpoints or a larger command matrix, first verify that the inverter or other controlled asset supports the required reactive-power commands. The interface must then be designed as a project-specific telecontrol integration. The required protocol, input hardware and feedback path depend on the DSO data-point list and the capabilities of the controlled devices.

## Project-specific gateway integration

A DSO gateway or SCADA connection is not configured through the standard Swiss relay wizard. Possible architectures include a local **Modbus TCP** or **IEC 60870-5-104** connection, or a cloud connection through **API** or **MQTT**. The actual choice, protocol role and data points must be agreed for each project.

Before the technical review, collect:

- the DSO's complete command and feedback data-point list;
- the required active- and reactive-power functions;
- protocol and role on both sides, for example Modbus client/server;
- register addresses, data types, byte order, scaling, units and valid ranges;
- network addressing, VLAN and firewall requirements;
- command validity, acknowledgement, watchdog, timeout and fail-safe behaviour;
- the exact brands, models and communication protocols of the controlled assets;
- the controller model and serial number;
- the planned commissioning date and responsible technical contacts.

The current intake asks you to confirm a telecontrol-capable controller with two onboard Ethernet ports, such as an applicable OM1 telecontrol, OM2 or Ultra model. Submit the [Telecontrol Request](https://media.eniris.be/telecontrole?lang=en) before fixing the commissioning date. Eniris will review device support, reactive-power capability, protocols and planning.

> [!IMPORTANT]
> Do not assume a Modbus register map, client/server role or IEC implementation before the technical review. A DSO data-point list is an input to the design, not proof that the interface is already available on the controller.

## Troubleshooting

### No digital input is available in the Swiss DSO wizard

Add the onboard input or external input module through the device wizard first. The Swiss DSO wizard only lists devices that are registered as eligible External Input devices.

### The wrong limit is applied

Check all of the following:

- whether the configured value is **permitted power**, not reduction percentage;
- the DI1/DI2 state and receiver polarity;
- the DSO truth table and the configured value for each level;
- the nominal power configured on every controlled asset.

### A selected device does not react

Verify that the device is online, controllable, included in the external signal and supports the requested active-power command. An EV charger without a connected vehicle may correctly report that no limit can currently be applied.

### Reactive power does not change

This is expected with the standard Swiss DSO relay strategies: they control active power only. Use the project-specific gateway process when Q or cos φ must also be controlled.

### Normal operation does not resume

Verify that the receiver has returned to the configured no-limit state and that both digital inputs display the expected values. Then check the external-signal status before investigating the local control strategy.


# Edmij


import { BrandName, ControllerName, CustomerName, InsightsName, InsightsUrl } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';
import CountriesSupportTable from '@site/src/components/CountriesSupportTable';

<img
    src="/img/sgo/Logo_Edmij.png"
    alt="Edmij logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

# Edmij

## Supported Devices

<DeviceSupportTable
  devices={[
    {
        type: 'Solar Inverters',
        variants: 'All',
        customCol: '✅'
    },
    {
        type: 'Storage Devices',
        variants: 'All',
        customCol: '❌'
    },
    {
        type: 'EV Chargers',
        variants: 'All',
        customCol: '❌'
    }
  ]}
    showVariants={true}
    customColumns={{ "customCol": "Supported" }}
/>

## Supported Countries

<CountriesSupportTable
  countries={[
    {
        country: 'Belgium',
        customCol: '❌'
    },
    {
        country: 'Netherlands',
        customCol: '✅'
    },
  ]}
    showVariants={true}
    customColumns={{ "customCol": "Supported" }}
/>

## Setup
To use the Edmij integration, you must inform Edmij that you wish to receive curtailment signals on this <BrandName /> <ControllerName />. This may require a contract with Edmij.

In your communication with Edmij, provide the following ID for a physical <BrandName /> <ControllerName />:
- [SERIAL NUMBER]_site_0
- Example: OM1230330XSQE4D1921_site_0

For cloud controllers you must provide the ID of the site to which the Edmij curtailment signal applies.

### Add 'Edmij' External Signal
<ClickableImage src="/img/generic/add-external-datasources-en.png" alt="Image 1" maxWidth="650px" />
<ClickableImage src="/img/generic/add-external-datasources-kind-en.png" alt="Image 1" maxWidth="650px" />

#### Edmij - Imbalance control (v2)
You will be asked if you want to reserve a part of your battery capacity to only do peak-shaving.
If you choose "Yes, I want peak shaving" new fields will appear and you will need to fill them.
<ClickableImage src="/img/customers/edmij/edmij-soc-limit-1.png" alt="Image 1" maxWidth="650px" />
<ClickableImage src="/img/customers/edmij/edmij-soc-limit-2.png" alt="Image 1" maxWidth="650px" />
> [!NOTE]
> You need to be careful when choosing the values, because below the specified state of charge all of Edmij signals will be ignored (due to peak shaving only).

In the next page, you have the option to include/exclude devices for remote control.
Ensure to mark all checkboxes of devices you'd like to include.
You must also go through the steps of the "External data sources" wizard on the <BrandName /> <ControllerName /> to indicate to which inverters the curtailment signal applies.

# Energy Flexibility Solutions (EFS)


import { BrandName, ControllerName, CustomerName, InsightsName, InsightsUrl } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';
import CountriesSupportTable from '@site/src/components/CountriesSupportTable';

<img
    src="/img/sgo/Logo_EFS.png"
    alt="EFS logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

# Setting up EFS

The manual describes the steps to set up EFS External Control on the <BrandName /> <ControllerName />.

When setting up this integration, permission is granted to EFS to control the necessary devices.

## Supported Devices

<DeviceSupportTable
  devices={[
    {
        type: 'Solar Inverters',
        variants: 'All',
        customCol: '✅'
    },
    {
        type: 'Storage Devices',
        variants: 'All',
        customCol: '✅'
    },
    {
        type: 'EV Chargers',
        variants: 'All',
        customCol: '❌'
    }
  ]}
    showVariants={true}
    customColumns={{ "customCol": "Supported" }}
/>

## Supported Countries

<CountriesSupportTable
  countries={[
    {
        country: 'Belgium',
        customCol: '❌'
    },
    {
        country: 'Netherlands',
        customCol: '✅'
    },
  ]}
    showVariants={true}
    customColumns={{ "customCol": "Supported" }}
/>

## Prerequisites

### 1. Add the batteries
[Login to the commissioning interface](/Controller/Configuration%20from%20A%20to%20Z/2-accessing-commissioning-interface/) and make sure the [devices are added](/Controller/Configuration%20from%20A%20to%20Z/6-other-devices/) to the <BrandName /> <ControllerName />.

### 2. Check the grid power limits
In the settings, the grid power limits should be set correctly. Click Settings and check the highlighted setting in the image.
If necessary, adjust the settings.

## Add 'EFS - External Control'
<ClickableImage src="/img/generic/add-external-datasources-en.png" alt="Image 1" maxWidth="650px" />
<ClickableImage src="/img/generic/add-external-datasources-kind-en.png" alt="Image 1" maxWidth="650px" />


In the next page, you have the option to include/exclude devices for remote control.
Ensure to mark all checkboxes of devices you'd like to include.

> [!NOTE]
> When using multiple batteries, they are aggregated into one (virtual) asset for EFS.

<ClickableImage src="/img/generic/add-external-datasources-devices-en.png" alt="Image 1" maxWidth="650px" />

'EFS' is now set up on the <BrandName /> <ControllerName />.

# Elia


import { BrandName, ControllerName, CustomerName, InsightsName, InsightsUrl } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';
import CountriesSupportTable from '@site/src/components/CountriesSupportTable';

<img
    src="/img/sgo/Logo_Elia.png"
    alt="Elia logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

# Setting up Elia

The manual describes the steps to set up 'Elia - Imbalance' on the <BrandName /> <ControllerName />.

## Supported Devices

<DeviceSupportTable
  devices={[
    {
        type: 'Solar Inverters',
        variants: 'All',
        customCol: '✅'
    },
    {
        type: 'Storage Devices',
        variants: 'All',
        customCol: '❌'
    },
    {
        type: 'EV Chargers',
        variants: 'All',
        customCol: '❌'
    }
  ]}
    showVariants={true}
    customColumns={{ "customCol": "Supported" }}
/>

## Supported Countries

<CountriesSupportTable
  countries={[
    {
        country: 'Belgium',
        customCol: '❌'
    },
    {
        country: 'Netherlands',
        customCol: '✅'
    },
  ]}
    showVariants={true}
    customColumns={{ "customCol": "Supported" }}
/>

## Prerequisites

### 1. Add the batteries
[Login to the commissioning interface](/Controller/Configuration%20from%20A%20to%20Z/2-accessing-commissioning-interface/) and make sure the [devices are added](/Controller/Configuration%20from%20A%20to%20Z/6-other-devices/) to the <BrandName /> <ControllerName />.

### 2. Check the grid power limits
In the settings, the grid power limits should be set correctly. Click Settings and check the highlighted setting in the image.
If necessary, adjust the settings.

### 3. Custom Fields

The following information must be known before adding the Control Signal:

- Curtailment Threshold
    - The imbalance price threshold at which curtailment begins.

- Curtailment Depth
    - The percentage of nominal inverter power to be curtailed during curtailment periods.
    - A value of 100 means 0% production during curtailment periods.

- Curtailment Strategy
    - Limit the power of inverters (recommended).
    - Switch off a subset of inverters (less accurate; only necessary if inverters do not support setpoint control).

- Timeout
    - If the connection with the servers is lost, this defines how long we continue using the last received value before reverting to local control.

- Daily Overrides
    - The values above can be adjusted on specific days of the week (e.g., Sunday) if needed.
    - Use the format: `weekday (integer); start time (hh:mm); duration in minutes (integer); threshold; curtailment depth`.

## Add 'Elia - Imbalance'
<ClickableImage src="/img/generic/add-external-datasources-en.png" alt="Image 1" maxWidth="650px" />
<ClickableImage src="/img/generic/add-external-datasources-kind-en.png" alt="Image 1" maxWidth="650px" />


In the next page, you have the option to include/exclude devices for remote control.
Ensure to mark all checkboxes of devices you'd like to include.

> [!NOTE]
> When using multiple batteries, they are aggregated into one (virtual) asset for Elia.

<ClickableImage src="/img/generic/add-external-datasources-devices-en.png" alt="Image 1" maxWidth="650px" />

'Elia' is now set up on the <BrandName /> <ControllerName />.


# Dynamic Contracts


import { BrandName, ControllerName, CustomerName, InsightsName, InsightsUrl } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';
import CountriesSupportTable from '@site/src/components/CountriesSupportTable';

<img
    src="/img/sgo/Logo_Elindus.png"
    alt="Elindus logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

# Setting up Elindus

The manual describes the steps to set up Elindus on the <BrandName /> <ControllerName />.

## Supported Countries

<CountriesSupportTable
  countries={[
    {
        country: 'Belgium',
        customCol: '✅'
    },
    {
        country: 'Netherlands',
        customCol: '❌'
    },
  ]}
    showVariants={true}
    customColumns={{ "customCol": "Supported" }}
/>

## Prerequisites

### 1. Choosing the Price Configuration
In the <BrandName /> App, select Settings.
<ClickableImage src="/img/generic/app_settings.png" alt="Image 1" maxWidth="200px" />

Select Elindus as the Price Configuration
<ClickableImage src="/img/generic/elindus-ean.png" alt="Image 1" maxWidth="650px" />

Enter your two EAN numbers.

## Functionality

Elindus will provide <BrandName /> with a formula for the day-ahead market. This formula will be applied to local control algorithms.


# Imbalance Control


import { BrandName, ControllerName, CustomerName, InsightsName, InsightsUrl } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';
import CountriesSupportTable from '@site/src/components/CountriesSupportTable';

<img
    src="/img/sgo/Logo_Elindus.png"
    alt="Elindus logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

# Setting up Elindus

The manual describes the steps to set up Elindus External Control on the <BrandName /> <ControllerName />.

When setting up this integration, permission is granted to Elindus to control the necessary devices.

Only installations greater than 100kVA qualify for imbalance control.

## Supported Devices

<DeviceSupportTable
  devices={[
    {
        type: 'Solar Inverters',
        variants: 'All',
        customCol: '✅'
    },
    {
        type: 'Storage Devices',
        variants: 'All',
        customCol: '✅'
    },
    {
        type: 'EV Chargers',
        variants: 'All',
        customCol: '❌'
    }
  ]}
    showVariants={true}
    customColumns={{ "customCol": "Supported" }}
/>

## Supported Countries

<CountriesSupportTable
  countries={[
    {
        country: 'Belgium',
        customCol: '✅'
    },
    {
        country: 'Netherlands',
        customCol: '❌'
    },
  ]}
    showVariants={true}
    customColumns={{ "customCol": "Supported" }}
/>

## Prerequisites

### 1. Add the batteries
[Login to the commissioning interface](/Controller/Configuration%20from%20A%20to%20Z/2-accessing-commissioning-interface/) and make sure the [devices are added](/Controller/Configuration%20from%20A%20to%20Z/6-other-devices/) to the <BrandName /> <ControllerName />.

### 2. Check the grid power limits
In the settings, the grid power limits should be set correctly. Click Settings and check the highlighted setting in the image.
If necessary, adjust the settings.

## Add 'Elindus - External Control'
<ClickableImage src="/img/generic/add-external-datasources-en.png" alt="Image 1" maxWidth="650px" />
<ClickableImage src="/img/generic/add-external-datasources-kind-en.png" alt="Image 1" maxWidth="650px" />


In the next page, you have the option to include/exclude devices for remote control.
Ensure to mark all checkboxes of devices you'd like to include.

> [!NOTE]
> When using multiple batteries, they are aggregated into one (virtual) asset for Elindus.

<ClickableImage src="/img/generic/add-external-datasources-devices-en.png" alt="Image 1" maxWidth="650px" />

'Elindus' is now set up on the <BrandName /> <ControllerName />.


# Elindus


import { FolderOverview } from '@/components/FolderOverview';

# Elindus

<FolderOverview folder="Controller/External Signals/Elindus" />


# Enervalis


import { BrandName, ControllerName, CustomerName, InsightsName, InsightsUrl } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';

<img
    src="/img/sgo/Logo_Enervalis.png"
    alt="Enervalis logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

The <BrandName /> <ControllerName /> supports receiving imbalance control signals from Scholt NL through local Enervalis Gateways, using Modbus TCP.

Please contact Scholt NL and Enervalis (now ABB) on how to set up this imbalance control.


# Engie


import { BrandName, ControllerName, CustomerName, InsightsName, InsightsUrl } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';
import CountriesSupportTable from '@site/src/components/CountriesSupportTable';

<img
    src="/img/sgo/Logo_Engie.png"
    alt="Engie logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

# Setting up Engie

The manual describes the steps to set up Engie External Control on the <BrandName /> <ControllerName />.

When setting up this integration, permission is granted to Engie to control the necessary devices.

## Supported Devices

<DeviceSupportTable
  devices={[
    {
        type: 'Solar Inverters',
        variants: 'All',
        customCol: '✅'
    },
    {
        type: 'Storage Devices',
        variants: 'All',
        customCol: '✅'
    },
    {
        type: 'EV Chargers',
        variants: 'All',
        customCol: '❌'
    }
  ]}
    showVariants={true}
    customColumns={{ "customCol": "Supported" }}
/>

## Supported Countries

<CountriesSupportTable
  countries={[
    {
        country: 'Belgium',
        customCol: '✅'
    },
    {
        country: 'Netherlands',
        customCol: '❌'
    },
  ]}
    showVariants={true}
    customColumns={{ "customCol": "Supported" }}
/>

## Prerequisites

### 1. Add the batteries
[Login to the commissioning interface](/Controller/Configuration%20from%20A%20to%20Z/2-accessing-commissioning-interface/) and make sure the [devices are added](/Controller/Configuration%20from%20A%20to%20Z/6-other-devices/) to the <BrandName /> <ControllerName />.

### 2. Check the grid power limits
In the settings, the grid power limits should be set correctly. Click Settings and check the highlighted setting in the image.
If necessary, adjust the settings.

## Add 'Engie - External Control'
<ClickableImage src="/img/generic/add-external-datasources-en.png" alt="Image 1" maxWidth="650px" />
<ClickableImage src="/img/generic/add-external-datasources-kind-en.png" alt="Image 1" maxWidth="650px" />


In the next page, you have the option to include/exclude devices for remote control.
Ensure to mark all checkboxes of devices you'd like to include.

> [!NOTE]
> When using multiple batteries, they are aggregated into one (virtual) asset for Engie.

<ClickableImage src="/img/generic/add-external-datasources-devices-en.png" alt="Image 1" maxWidth="650px" />

'Engie' is now set up on the <BrandName /> <ControllerName />.

# Plan-ahead API


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';
import PdfLink from '@site/src/components/PdfLink';

> [!CAUTION] NOTE:
> The Plan-ahead API is no longer supported. For external control, see [Live MQTT control](/Controller/External%20Signals/mqtt/eniris-mqtt/) instead.


# EPEX Spot Solar


import { BrandName, ControllerName, CustomerName, InsightsName, InsightsUrl } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';
import CountriesSupportTable from '@site/src/components/CountriesSupportTable';

<img
    src="/img/sgo/Logo_EPEX SPOT.png"
    alt="EPEX SPOT logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

# Setting up EPEX Spot Solar

The manual describes the steps to set up EPEX Spot Solar on the <BrandName /> <ControllerName />.

When setting up this integration, the default control modes are overwritten for all selected PV devices. Batteries are **NOT** included.

## Supported Devices

<DeviceSupportTable
  devices={[
    {
        type: 'Solar Inverters',
        variants: 'All',
        customCol: '✅',
    },
    {
        type: 'Storage Devices',
        variants: 'All',
        customCol: '❌'
    },
    {
        type: 'EV Chargers',
        variants: 'All',
        customCol: '❌'
    }
  ]}
    showVariants={true}
    customColumns={{ "customCol": "Supported" }}
/>

## Supported Countries

<CountriesSupportTable
  countries={[
    {
        country: 'Belgium',
        customCol: '✅'
    },
    {
        country: 'Netherlands',
        customCol: '✅'
    },
  ]}
    showVariants={true}
    customColumns={{ "customCol": "Supported" }}
/>

## Prerequisites

### 1. Add the PV inverters
[Login to the commissioning interface](/Controller/Configuration%20from%20A%20to%20Z/2-accessing-commissioning-interface/) and make sure the [devices are added](/Controller/Configuration%20from%20A%20to%20Z/6-other-devices/) to the <BrandName /> <ControllerName />.

### 2. Check the grid power limits
In the settings, the grid power limits should be set correctly. Click Settings and check the highlighted setting in the image.
If necessary, adjust the settings.


## Add 'EPEX Spot Solar'
<ClickableImage src="/img/generic/add-external-datasources-en.png" alt="Image 1" maxWidth="650px" />
<ClickableImage src="/img/generic/add-external-datasources-kind-en.png" alt="Image 1" maxWidth="650px" />
<ClickableImage src="/img/generic/datasource-epex-parameters.png" alt="Image 1" maxWidth="650px" />

There are four available parameters:

1. Curtailment Threshold

    When the Day-Ahead EPEX Price falls under this threshold, the PV inverters will be curtailed.

2. Market

    Select the EPEX Market in Belgium or Netherlands

3. Days on which curtailment takes place

    If curtailment must not take place every day of the week (e.g. excluding weekends), specific days can be selected.

4. Curtailment strategy

    Curtailment entails either zero production, or zero injection. Zero production will shut off inverters during curtailment periods, whereas zero injection will ensure inverters produce enough to compensate for self-consumption.

In the next page, you have the option to include/exclude devices for remote control.
Ensure to mark all checkboxes of devices you'd like to include.

<ClickableImage src="/img/generic/add-external-datasources-devices-en.png" alt="Image 1" maxWidth="650px" />

'EPEX Spot Solar' is now set up on the <BrandName /> <ControllerName />.


# European Commodities


import { BrandName, ControllerName, CustomerName, InsightsName, InsightsUrl } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';

<img
    src="/img/sgo/Logo_European Commodities.png"
    alt="European Commodities logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

> [!NOTE]
> Work In Progress

# Fleco Power


import { BrandName, ControllerName, CustomerName, InsightsName, InsightsUrl } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';
import CountriesSupportTable from '@site/src/components/CountriesSupportTable';

<img
    src="/img/sgo/Logo_Flecopower.png"
    alt="Fleco Power logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

# Setting up Fleco Power

The manual describes the steps to set up Fleco Power External Control on the <BrandName /> <ControllerName />.

When setting up this integration, permission is granted to Fleco Power to control the necessary devices.

## Supported Devices

<DeviceSupportTable
  devices={[
    {
        type: 'Solar Inverters',
        variants: 'All',
        customCol: '✅'
    },
    {
        type: 'Storage Devices',
        variants: 'All',
        customCol: '✅'
    },
    {
        type: 'EV Chargers',
        variants: 'All',
        customCol: '❌'
    }
  ]}
    showVariants={true}
    customColumns={{ "customCol": "Supported" }}
/>

## Supported Countries

<CountriesSupportTable
  countries={[
    {
        country: 'Switzerland',
        customCol: '✅'
    },
  ]}
    showVariants={true}
    customColumns={{ "customCol": "Supported" }}
/>

## Prerequisites

### 1. Add the batteries
[Login to the commissioning interface](/Controller/Configuration%20from%20A%20to%20Z/2-accessing-commissioning-interface/) and make sure the [devices are added](/Controller/Configuration%20from%20A%20to%20Z/6-other-devices/) to the <BrandName /> <ControllerName />.

### 2. Check the grid power limits
In the settings, the grid power limits should be set correctly. Click Settings and check the highlighted setting in the image.
If necessary, adjust the settings.

## Add 'Fleco Power - External Control'
<ClickableImage src="/img/generic/add-external-datasources-en.png" alt="Image 1" maxWidth="650px" />
<ClickableImage src="/img/generic/add-external-datasources-kind-en.png" alt="Image 1" maxWidth="650px" />


In the next page, you have the option to include/exclude devices for remote control.
Ensure to mark all checkboxes of devices you'd like to include.

> [!NOTE]
> When using multiple batteries, they are aggregated into one (virtual) asset for Fleco Power.

<ClickableImage src="/img/generic/add-external-datasources-devices-en.png" alt="Image 1" maxWidth="650px" />

'Fleco Power' is now set up on the <BrandName /> <ControllerName />.

# Flower


import { BrandName, ControllerName, CustomerName, InsightsName, InsightsUrl } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';
import CountriesSupportTable from '@site/src/components/CountriesSupportTable';

<img
    src="/img/sgo/Logo_Flower.png"
    alt="Flower logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

> [!NOTE]
> Flower is not yet fully integrated.
>

# Setting up Flower

The manual describes the steps to set up Flower External Control on the <BrandName /> <ControllerName />.

When setting up this integration, permission is granted to Flower to control the battery and/or solar inverters.

## Supported Devices

<DeviceSupportTable
  devices={[
    {
        type: 'Solar Inverters',
        variants: 'All',
        customCol: '✅',
    },
    {
        type: 'Storage Devices',
        variants: 'All',
        customCol: '✅'
    },
    {
        type: 'EV Chargers',
        variants: 'All',
        customCol: '❌'
    }
  ]}
    showVariants={true}
    customColumns={{ "customCol": "Supported" }}
/>

## Supported Countries

<CountriesSupportTable
  countries={[
    {
        country: 'Belgium',
        customCol: '❌'
    },
    {
        country: 'Netherlands',
        customCol: '❌'
    },
    {
        country: 'Sweden',
        customCol: '✅'
    },
  ]}
    showVariants={true}
    customColumns={{ "customCol": "Supported" }}
/>

## Prerequisites

### 1. Add the batteries
[Login to the commissioning interface](/Controller/Configuration%20from%20A%20to%20Z/2-accessing-commissioning-interface/) and make sure the [devices are added](/Controller/Configuration%20from%20A%20to%20Z/6-other-devices/) to the <BrandName /> <ControllerName />.

### 2. Check the grid power limits
In the settings, the grid power limits should be set correctly. Click Settings and check the highlighted setting in the image.
If necessary, adjust the settings.

### 3. Flower API Credentials
Flower will provide the following credentials, which must be used when adding the External Signal:
1. API Username
2. API Password
3. Partner ID (generally the same as the API Username)
4. MQTT Client ID

Alongside these credentials, select the devices and meters which exist and can be controller by Flower. This includes batteries, solar panels (or both), and grid meters.
Finally, the correct bidding zone of the asset must be selected.


## Add 'Flower - External Control'
<ClickableImage src="/img/generic/add-external-datasources-en.png" alt="Image 1" maxWidth="650px" />
<ClickableImage src="/img/generic/add-external-datasources-kind-en.png" alt="Image 1" maxWidth="650px" />


In the next page, you have the option to include/exclude devices for remote control.
Ensure to mark all checkboxes of devices you'd like to include.

> [!NOTE]
> When using multiple batteries or solar inverters, they are aggregated into one (virtual) asset for Flower.

<ClickableImage src="/img/generic/add-external-datasources-devices-en.png" alt="Image 1" maxWidth="650px" />

'Flower' is now set up on the <BrandName /> <ControllerName />.

# Frank Energie


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';
import YouTubeEmbed from '@site/src/components/YouTubeEmbed';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';
import CountriesSupportTable from '@site/src/components/CountriesSupportTable';
import Details from '@theme/Details';

<img
    src="/img/sgo/Logo_Frank Energie.png"
    alt="Frank Energie logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

## Table of Contents

- [Overview](#overview)
- [Prerequisites](#prerequisites)
- [Enabling 'Frank Energie - Slim Handelen'](#enabling-frank-energie---slim-handelen)
- [Troubleshooting](#troubleshooting)
- [Background information](#background-information)
  - [Frank Energie Control Modes](#frank-energie-control-modes)
  - [‘Onboarding’ process](#onboarding-process)
  - [Underperforming battery](#underperforming-battery)
  - [Offline <BrandName /> <ControllerName /> or unresponsive battery](#offline---or-unresponsive-battery)
  - [Minimum state of charge at 20%](#minimum-state-of-charge-at-20)

## Overview
> [!CAUTION] NOTE:
> Frank Energie decides when and how your battery should charge or discharge through their system. Our platform simply carries out these battery operation decisions.
>
> If you have any questions about how your battery is being controlled or disagree with the charging/discharging decisions, please contact Frank Energie directly, as we cannot modify or influence their battery management strategy.
" Slim Handelen " by Frank Energie is a service that allows you as a customer of Frank Energie to use your battery on the imbalance market. The manual describes how we can set this up on the <BrandName /> <ControllerName />. At the end of this manual, Frank Energie will have control over the battery and the battery will be shown in the Frank Energie app. When setting up this integration, permission is granted to Frank Energie to control this battery.


<YouTubeEmbed videoId="R44LHhF-X70"/>

## Supported Devices and countries
The following devices types are supported by the Frank Energie - Slim Handelen integration:
<DeviceSupportTable
  devices={[
    {
        type: 'Solar Inverters',
        variants: 'All',
        customCol: '⌛ (coming soon)',
    },
    {
        type: 'Storage Devices',
        variants: 'All',
        customCol: '✅'
    },
    {
        type: 'EV Chargers',
        variants: 'All',
        customCol: '❌'
    }
  ]}
    showVariants={true}
    customColumns={{ "customCol": "Supported" }}
/>
The Frank Energie - Slim Handelen integration is currently supported in the following countries:
<CountriesSupportTable
  countries={[
    {
        country: 'Belgium',
        customCol: '✅'
    },
    {
        country: 'Netherlands',
        customCol: '✅'
    },
  ]}
    showVariants={true}
    customColumns={{ "customCol": "Supported" }}
/>


## Prerequisites

### 1. Add the batteries
[Login to the commissioning interface](/Controller/Configuration%20from%20A%20to%20Z/2-accessing-commissioning-interface/) and make sure the [devices are added](/Controller/Configuration%20from%20A%20to%20Z/6-other-devices/) to the <BrandName /> <ControllerName />.

### 2. Check the grid power limits
In the settings, the grid power limits should be set correctly. Click Settings and check the highlighted setting in the image.
If necessary, adjust the settings.

### 3. Check the address
Make sure [the address is set correctly](/Controller/Configuration%20from%20A%20to%20Z/4-location/).

> [!WARNING]
> The integration may not work correctly if the address is not correct!

### 4. Find the customer number
Ask the end customer to look up the customer number (of Frank Energie) and pass it on. The customer can look this up in the Frank Energie app.
<ClickableImage src="/img/generic/frank-energie-app.jpg" alt="Image 1" maxWidth="350px" />


## Enabling 'Frank Energie - Slim Handelen'
From the commissioning interface, go to the 'External Signals' tab.
<ClickableImage src="/img/generic/add-external-datasources-en.png" alt="Image 1" maxWidth="650px" />
Click on 'External signal'.
<ClickableImage src="/img/generic/add-external-datasources-kind-en.png" alt="Image 1" maxWidth="650px" />
Select 'Frank Energie - Slim Handelen' and click 'Next'.
<ClickableImage src="/img/generic/add-external-datasources-frank-energie-en.png" alt="Select Frank Energie" maxWidth="650px" />

Enter the Frank Energie contract number and the company name.
The company name will reflect in the Frank Energie app. The default (blank) value is Eniris.

<ClickableImage src="/img/generic/add-external-datasources-frank-energie-parameters-en.png" alt="Frank Energie Input Parameters" maxWidth="650px" />

In the next page, you have the option to include/exclude devices for remote control.
Ensure to mark all checkboxes of devices you'd like to include.

> [!NOTE]
> When using multiple batteries, they are aggregated into one (virtual) asset for Frank Energie.

<ClickableImage src="/img/generic/add-external-datasources-devices-en.png" alt="Image 1" maxWidth="650px" />

'Frank Energie - Slim Handelen' is now set up on the <BrandName /> <ControllerName />.

[//]: # (<ClickableImage src="/img/generic/frank-energie-finished.jpg" alt="Image 1" maxWidth="450px" />)


## Troubleshooting
> [!NOTE] Troubleshooting
> This section only includes troubleshooting steps specific to the Frank Energie integration. For issues with your inverter or battery, please refer to the appropriate section based on your connection type:
>     - With RS485 connection follow this [link](/Controller/Troubleshooting/device-communication/#rs485)
>     - With TCP connection follow this [link](/Controller/Troubleshooting/device-communication/#ethernet)

Issues related to Frank Energie integration can often be identified by checking the status page of the external signels on the <BrandName /> <ControllerName />.
Here you can find information about the last received signal, setpoints, and any errors encountered. The example image below shows a successful connection with Frank Energie, but if there are issues, error messages will be displayed here.
<ClickableImage src="/img/generic/frank_energie_status.png" alt="Image 1" maxWidth="650px" />

<Details summary="I see 'No signal received. Applying default policy.'">
This can happen if the grid energy meter is wired in reverse. You can tell the <BrandName /> <ControllerName /> that the meter is connected in reverse through the device settings in the "Devices tab" of the commissioning interface. See also [Reversing energy meter readings](/Controller/Configuration%20from%20A%20to%20Z/11-Extra-Information/reversing-energy-meter/).
<b>Important</b>: Double check if your grid meter readings are effectively reversed. If they are not, and you faultly reverse them in the settings of the energy meter, this can make the control system unstable.
</Details>

<Details summary="I see 'Could not resolve DNS. Check your DNS configuration.'">
This error is related to a misconfiguration of your network or firewall. Verify that none of the [required ports are blocked by the local firewall](/Controller/network-configuration/).
</Details>

<Details summary="In the app, I do not see any battery activity, even though Frank Energie control is active.">
    Frank Energie will <b>not always</b> send a command for the battery. When there is no imbalance opportunity, Frank Energie will allow the battery to do self-consumption. During these moments, 'data gap' in graphs and visualizations can show. Note that this is not an issue.
</Details>

Frank Energie will NOT always send a setpoint. When self-consumption is active, a setpoint is not required, causing a 'data gap' in graphs and visualizations. Note that this is not an issue.

## Background information

### Frank Energie Control Modes
When Frank Energie is added, the <BrandName /> <ControllerName /> algorithm has **no control** over the battery's behaviour.
Instead, in the Frank Energie App, two different control modes can be selected: Self-Consumption+ and Handling.

__Self Consumption+:__
When Self-Consumption+ has been selected, Frank Energie will fully control the battery at all times. However, Frank Energie will authorize the <BrandName /> <ControllerName /> to follow its own self-consumption algorithm during certain periods.

__Handling:__
The handling control mode also gives Frank Energie full control of the battery. There will **not** be any self-consumption active. All energy will go to and from the grid, depending on the market prices at the time.

### 'Onboarding' process
When a new 'Frank Energie - Slim Handelen' external signal is added to the <BrandName /> <ControllerName />, we forward information to Frank Energie. We call this 'onboarding'.
During onboarding, we share:
- The address of the installation (to match with the Frank Energie customer account)
- The maximum charge and discharge power of the battery (to ensure safe operation within limits). This is automatically retrieved from the battery-specific settings in the commissioning interface. When the maximum charge/discharge power are not set, the nominal power of the battery is used.
- The contract id of the customer (to link the battery to the correct Frank Energie account)
- The identifier of the <BrandName /> <ControllerName /> (to uniquely identify the battery installation)

Besides the initial onboarding when adding the external signal, we will notifiy Frank Energie in the following cases:
- When the address of the installation is changed
- When the contract id is changed
- When the maximum charge, discharge power or nominal power of the battery is changed

In the above cases, you might receive a notification from the Frank Energie app that a battery has been added/removed or updated, which is normal.
We will not notify Frank Energie about updates in any other cases.

### Underperforming battery
During onboarding, we share the maximum charge and discharge power of the battery with Frank Energie.
It may occur that these values are overoptimistic, leading to Frank Energie requesting charge/discharge powers that the battery cannot deliver.
This results in low (or zero) revenues on the imbalance market for the end customer.
To avoid this, please ensure that the __realistic__ maximum charge and discharge power of the battery are set correctly in the commissioning interface.
If these values are not set, the nominal power of the battery is used, which may be different from the actual maximum charge/discharge power.

Frank Energie does a regular evaluation of the battery performance on the imbalance market. If they detect that the battery is underperforming, they lower the powers in their system to a more realistic value based on observations in the past.
This is undone, when the installer adjusts the maximum charge/discharge power settings again, triggering a re-onboarding (see above).

### Offline <BrandName /> <ControllerName /> or unresponsive battery
Frank Energie expects a battery to be online and responsive at all times. If the battery is offline for a prolonged period, Frank Energie contacts the installer to investigate the issue.
If the battery remains unresponsive, Frank Energie and the team behind <BrandName /> may decide to remove the battery from their system to avoid negative impacts on their operations.
Frank Energie shares a list of unresponsive batteries with us on a regular basis.

If your battery has been removed due to unresponsiveness, please check the communication of your <BrandName /> <ControllerName /> and battery, and re-add the 'Frank Energie - Slim Handelen' external signal to the <BrandName /> <ControllerName /> once the issue is resolved.

### Minimum state of charge at 20%
Frank Energie will account for a minimum state of charge of 20% in their control strategy. This means that Frank Energie will not request discharging the battery below 20% state of charge. 
__When you configure a different minimum state of charge in the commissioning interface, Frank Energie will still only consider 20% as the minimum state of charge for their control strategy.__


# Fusebox


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';
import CountriesSupportTable from '@site/src/components/CountriesSupportTable';

<img
    src="/img/sgo/Logo_Fusebox.png"
    alt="Fusebox logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

> [!NOTE]
> Fusebox is not yet fully integrated.
>

# Setting up Fusebox

The manual describes the steps to set up Fusebox External Control on the <BrandName /> <ControllerName />.

When setting up this integration, permission is granted to Fusebox to control this battery.

## Supported Devices

<DeviceSupportTable
  devices={[
    {
        type: 'Solar Inverters',
        variants: 'All',
        customCol: '❌',
    },
    {
        type: 'Storage Devices',
        variants: 'All',
        customCol: '✅'
    },
    {
        type: 'EV Chargers',
        variants: 'All',
        customCol: '❌'
    }
  ]}
    showVariants={true}
    customColumns={{ "customCol": "Supported" }}
/>

## Supported Countries

<CountriesSupportTable
  countries={[
    {
        country: 'Belgium',
        customCol: '❌'
    },
    {
        country: 'Netherlands',
        customCol: '❌'
    },
    {
        country: 'Estonia',
        customCol: '✅'
    },
  ]}
    showVariants={true}
    customColumns={{ "customCol": "Supported" }}
/>

## Prerequisites

### 1. Add the batteries
[Login to the commissioning interface](/Controller/Configuration%20from%20A%20to%20Z/2-accessing-commissioning-interface/) and make sure the [devices are added](/Controller/Configuration%20from%20A%20to%20Z/6-other-devices/) to the <BrandName /> <ControllerName />.

### 2. Check the grid power limits
In the settings, the grid power limits should be set correctly. Click Settings and check the highlighted setting in the image.
If necessary, adjust the settings.

### 3. Fusebox Credentials
Fusebox will provide a username/device identifier and password for each new installation. This **must** be used when adding the external signal driver.

## Add 'Fusebox - External Control'
<ClickableImage src="/img/generic/add-external-datasources-en.png" alt="Image 1" maxWidth="650px" />
<ClickableImage src="/img/generic/add-external-datasources-kind-en.png" alt="Image 1" maxWidth="650px" />


In the next page, you have the option to include/exclude devices for remote control.
Ensure to mark all checkboxes of devices you'd like to include.

> [!NOTE]
> When using multiple batteries, they are aggregated into one (virtual) asset for Fusebox.

<ClickableImage src="/img/generic/add-external-datasources-devices-en.png" alt="Image 1" maxWidth="650px" />

'Fusebox' is now set up on the <BrandName /> <ControllerName />.

### Set/Modify the measurement update period

If you want to change the interval between measurements to avoid granularity issues you can go in <i>Settings > Advanced Settings</i> and modify :
<ul>
<li><b>Data reading period :</b> How often the data is read out from the devices. You should set this to 0, which means as fast as possible.</li>
<li><b>Scheduler run period :</b> How much seconds there must be at least between two consecutive control loop executions. Less excecutions mean less data usage, but come at the cost of slower and less accurate control.</li>
</ul>

# Greenchoice


import { BrandName, ControllerName, CustomerName, InsightsName, InsightsUrl } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';
import CountriesSupportTable from '@site/src/components/CountriesSupportTable';

<img
    src="/img/sgo/Logo_Greenchoice.png"
    alt="Greenchoice logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

# Setting up Greenchoice

## Supported Devices

<DeviceSupportTable
  devices={[
    {
        type: 'Solar Inverters',
        variants: 'All',
        customCol: '✅'
    },
    {
        type: 'Storage Devices',
        variants: 'All',
        customCol: '✅'
    },
    {
        type: 'EV Chargers',
        variants: 'All',
        customCol: '❌'
    }
  ]}
    showVariants={true}
    customColumns={{ "customCol": "Supported" }}
/>

## Supported Countries

<CountriesSupportTable
  countries={[
    {
        country: 'Belgium',
        customCol: '❌'
    },
    {
        country: 'Netherlands',
        customCol: '✅'
    },
  ]}
    showVariants={true}
    customColumns={{ "customCol": "Supported" }}
/>

## Prerequisites
To use the Greenchoice integration, you must receive a contract number from Greenchoice, which will be entered when adding the External Control Signal.

### 1. Add the batteries
[Login to the commissioning interface](/Controller/Configuration%20from%20A%20to%20Z/2-accessing-commissioning-interface/) and make sure the [devices are added](/Controller/Configuration%20from%20A%20to%20Z/6-other-devices/) to the <BrandName /> <ControllerName />.

### 2. Check the grid power limits
In the settings, the grid power limits should be set correctly. Click Settings and check the highlighted setting in the image.
If necessary, adjust the settings.

## Add 'Greenchoice - External Control'
<ClickableImage src="/img/generic/add-external-datasources-en.png" alt="Image 1" maxWidth="650px" />
<ClickableImage src="/img/generic/add-external-datasources-kind-en.png" alt="Image 1" maxWidth="650px" />


In the next page, you have the option to include/exclude devices for remote control.
Ensure to mark all checkboxes of devices you'd like to include.

> [!NOTE]
> When using multiple batteries, they are aggregated into one (virtual) asset for Greenchoice.

<ClickableImage src="/img/generic/add-external-datasources-devices-en.png" alt="Image 1" maxWidth="650px" />

'Greenchoice' is now set up on the <BrandName /> <ControllerName />.

# Gridual


import { BrandName, ControllerName, CustomerName, InsightsName, InsightsUrl } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/sgo/Logo_Gridual.png"
    alt="Gridual logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

# Setting up Gridual

The manual describes the steps to set up Gridual - Imbalance Control on the <BrandName /> <ControllerName />.

When setting up this integration, permission is granted to Gridual to control the necessary devices.

## Supported Devices

<DeviceSupportTable
  devices={[
    {
        type: 'Solar Inverters',
        variants: 'All',
        customCol: '✅'
    },
    {
        type: 'Storage Devices',
        variants: 'All',
        customCol: '✅'
    },
    {
        type: 'EV Chargers',
        variants: 'All',
        customCol: '❌'
    }
  ]}
    showVariants={true}
    customColumns={{ "customCol": "Supported" }}
/>

## Notifying Gridual

Gridual will require information about the <BrandName /> <ControllerName /> before they can control any assets.

This includes the *<BrandName /> <ControllerName /> Serial Number*, and the *SiteID*, which is the same as the Serial Number with '_site_0' appended at the end.

## Add 'Gridual - Imbalance control' External Signal
<ClickableImage src="/img/generic/add-external-datasources-en.png" alt="Image 1" maxWidth="650px" />
<ClickableImage src="/img/generic/add-external-datasources-kind-en.png" alt="Image 1" maxWidth="650px" />

In the next page, you have the option to include/exclude devices for remote control.
Ensure to mark all checkboxes of devices you'd like to include.

> [!NOTE]
> When using multiple batteries, they are aggregated into one (virtual) asset for Gridual.

<ClickableImage src="/img/generic/add-external-datasources-devices-en.png" alt="Image 1" maxWidth="650px" />

'Gridual' is now set up on the <BrandName /> <ControllerName />.

> [!TIP]
> When Gridual External Control is added, the <BrandName /> <ControllerName /> algorithm has **no control** over the battery's behaviour.

### Default Fallback

If no signal is received from Gridual for 2 minutes, control falls back to the local algorithm.


# Hallostroom


import { BrandName, ControllerName, CustomerName, InsightsName, InsightsUrl } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/sgo/Logo_Hallostroom.png"
    alt="Hallostroom logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

> [!CAUTION] NOTE:
> Hallostroom is no longer active. Please refer to [Next Energy](/Controller/External%20Signals/next-energy/) for more information.
>

# Setting up Hallostroom

The manual describes the steps to set up Hallostroom External Control on the <BrandName /> <ControllerName />.

When setting up this integration, permission is granted to Companion to control the necessary devices.

## Supported Devices

<DeviceSupportTable
  devices={[
    {
        type: 'Solar Inverters',
        variants: 'All',
        customCol: '✅'
    },
    {
        type: 'Storage Devices',
        variants: 'All',
        customCol: '✅'
    },
    {
        type: 'EV Chargers',
        variants: 'All',
        customCol: '❌'
    }
  ]}
    showVariants={true}
    customColumns={{ "customCol": "Supported" }}
/>

## Prerequisites

### 1. Add the batteries
[Login to the commissioning interface](/Controller/Configuration%20from%20A%20to%20Z/2-accessing-commissioning-interface/) and make sure the [devices are added](/Controller/Configuration%20from%20A%20to%20Z/6-other-devices/) to the <BrandName /> <ControllerName />.

### 2. Check the grid power limits
In the settings, the grid power limits should be set correctly. Click Settings and check the highlighted setting in the image.
If necessary, adjust the settings.

## Add 'Hallostroom - External Control'
<ClickableImage src="/img/generic/add-external-datasources-en.png" alt="Image 1" maxWidth="650px" />
<ClickableImage src="/img/generic/add-external-datasources-kind-en.png" alt="Image 1" maxWidth="650px" />


In the next page, you have the option to include/exclude devices for remote control.
Ensure to mark all checkboxes of devices you'd like to include.

> [!NOTE]
> When using multiple batteries, they are aggregated into one (virtual) asset for Hallostroom.

<ClickableImage src="/img/generic/add-external-datasources-devices-en.png" alt="Image 1" maxWidth="650px" />

'Hallostroom' is now set up on the <BrandName /> <ControllerName />.

# Hive Power


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';
import YouTubeEmbed from '@site/src/components/YouTubeEmbed';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';
import CountriesSupportTable from '@site/src/components/CountriesSupportTable';
import Details from '@theme/Details';

<img
    src="/img/sgo/Logo_HivePower.png"
    alt="Hive Power logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

## Overview
> [!CAUTION] NOTE:
> Hive Power decides when and how your battery should charge or discharge through their system. Our platform simply carries out these battery operation decisions.
>
> If you have any questions about how your battery is being controlled or disagree with the charging/discharging decisions, please contact Hive Power directly, as we cannot modify or influence their battery management strategy.
" This service allows you, as a customer of Hive Power, to use your battery on various energy markets. The manual describes how we can set this up on the <BrandName /> <ControllerName />. At the end of this manual, Hive Power will have control over the battery. When setting up this integration, permission is granted to Hive Power to control this battery.

## Supported Devices and countries
The following devices types are supported by the Hive Power integration:
<DeviceSupportTable
  devices={[
    {
        type: 'Solar Inverters',
        variants: 'All',
        customCol: '✅',
    },
    {
        type: 'Storage Devices',
        variants: 'All',
        customCol: '✅'
    },
    {
        type: 'EV Chargers',
        variants: 'All',
        customCol: '❌'
    }
  ]}
    showVariants={true}
    customColumns={{ "customCol": "Supported" }}
/>

## Prerequisites

### 1. Add the devices
[Login to the commissioning interface](/Controller/Configuration%20from%20A%20to%20Z/2-accessing-commissioning-interface/) and make sure the [devices are added](/Controller/Configuration%20from%20A%20to%20Z/6-other-devices/) to the <BrandName /> <ControllerName />.

### 2. Check the grid power limits
In the settings, the grid power limits should be set correctly. Click Settings and check the highlighted setting in the image.
If necessary, adjust the settings.

### 3. Check the address
Make sure [the address is set correctly](/Controller/Configuration%20from%20A%20to%20Z/4-location/).

> [!WARNING]
> The integration may not work correctly if the address is not correct!

## Enabling 'Hive Power'
From the commissioning interface, go to the 'External Signals' tab.
<ClickableImage src="/img/generic/add-external-datasources-en.png" alt="Image 1" maxWidth="650px" />

Click on 'Energy Markets'.
<ClickableImage src="/img/controller/external signals/types.png" alt="Image 1" maxWidth="650px" />

Select Hive Power and click 'Next'.

Select the control tier which is applicable to your installation.

### Tier 1 - Setpoint Follower

Setpoints received from Hive Power are sent directly to the devices. No local control is done by the <BrandName /> <ControllerName />.

### Tier 2 - Delta Stacking

The <BrandName /> <ControllerName /> executes its own self-consumption algorithm, Hive Power uses the battery availability to activate the battery on ancilliary markets.

### Tier 3 - Battery Splitting

Work in progress.

The battery is split into two virtual batteries. One part is controller by Hive Power on various ancilliary energy markets, while the remaining portion of the battery is used for local control only.

## Device Selection

In the next page, you have the option to include/exclude devices for remote control.
Ensure to mark all checkboxes of devices you'd like to include.

> [!NOTE]
> When using multiple devices, they are aggregated into one (virtual) asset, per asset type, for Hive Power.

<ClickableImage src="/img/generic/add-external-datasources-devices-en.png" alt="Image 1" maxWidth="650px" />

'Hive Power' is now set up on the <BrandName /> <ControllerName />.



# Imby


import { BrandName, ControllerName, CustomerName, InsightsName, InsightsUrl } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';
import CountriesSupportTable from '@site/src/components/CountriesSupportTable';

<img
    src="/img/sgo/Logo_Imby.png"
    alt="Imby logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

# Setting up Imby

The manual describes the steps to set up Imby External Control on the <BrandName /> <ControllerName />.

When setting up this integration, permission is granted to Imby to control the necessary devices.

## Supported Devices

<DeviceSupportTable
  devices={[
    {
        type: 'Solar Inverters',
        variants: 'All',
        customCol: '✅'
    },
    {
        type: 'Storage Devices',
        variants: 'All',
        customCol: '✅'
    },
    {
        type: 'EV Chargers',
        variants: 'All',
        customCol: '❌'
    }
  ]}
    showVariants={true}
    customColumns={{ "customCol": "Supported" }}
/>

## Supported Countries

<CountriesSupportTable
  countries={[
    {
        country: 'Belgium',
        customCol: '✅'
    },
    {
        country: 'Netherlands',
        customCol: '❌'
    },
  ]}
    showVariants={true}
    customColumns={{ "customCol": "Supported" }}
/>

## Prerequisites

### 1. Add the batteries
[Login to the commissioning interface](/Controller/Configuration%20from%20A%20to%20Z/2-accessing-commissioning-interface/) and make sure the [devices are added](/Controller/Configuration%20from%20A%20to%20Z/6-other-devices/) to the <BrandName /> <ControllerName />.

### 2. Check the grid power limits
In the settings, the grid power limits should be set correctly. Click Settings and check the highlighted setting in the image.
If necessary, adjust the settings.

## Add 'Imby - External Control'
<ClickableImage src="/img/generic/add-external-datasources-en.png" alt="Image 1" maxWidth="650px" />
<ClickableImage src="/img/generic/add-external-datasources-kind-en.png" alt="Image 1" maxWidth="650px" />


In the next page, you have the option to include/exclude devices for remote control.
Ensure to mark all checkboxes of devices you'd like to include.

> [!NOTE]
> When using multiple batteries, they are aggregated into one (virtual) asset for Imby.

<ClickableImage src="/img/generic/add-external-datasources-devices-en.png" alt="Image 1" maxWidth="650px" />

'Imby' is now set up on the <BrandName /> <ControllerName />.

# External Signals


# Supported External Control Integrations

import CollapsibleExternalSignalsTable from "@site/src/components/CollapsibleExternalSignalsTable";

This page provides an overview of all external control integrations supported by the controller.

<div className="device-table-container">

<CollapsibleExternalSignalsTable
  overviewData={{
    Agrola: {
      Agrola: {
        "Solar Inverters": "⌛ (coming soon)",
        "Storage Devices": "✅",
        "EV Chargers": "❌",
      },
    },
    Autarco: {
      "Autarco External Control": {
        "Solar Inverters": "✅",
        "Storage Devices": "✅",
        "EV Chargers": "❌",
      },
    },
    BEE: {
      BEE: {
        "Solar Inverters": "✅",
        "Storage Devices": "✅",
        "EV Chargers": "❌",
      },
    },
    CKW: {
      CKW: {
        "Solar Inverters": "✅",
        "Storage Devices": "✅",
        "EV Chargers": "❌",
      },
    },
    Companion: {
      Companion: {
        "Solar Inverters": "✅",
        "Storage Devices": "✅",
        "EV Chargers": "❌",
      },
    },
    DET: {
      "Dynamic Energy Trading": {
        "Solar Inverters": "⌛ (coming soon)",
        "Storage Devices": "✅",
        "EV Chargers": "❌",
      },
    },
    Dexter: {
      Dexter: {
        "Solar Inverters": "✅",
        "Storage Devices": "❌",
        "EV Chargers": "❌",
      },
    },
    "Diagnostic Tests": {
      "Diagnostic Tests": {
        "Solar Inverters": "❌",
        "Storage Devices": "✅",
        "EV Chargers": "❌",
      },
    },
    DNO: {
      "DNO Relay Control": {
        "Solar Inverters": "✅",
        "Storage Devices": "✅",
        "EV Chargers": "❌",
      },
    },
    Edmij: {
      Edmij: {
        "Solar Inverters": "✅",
        "Storage Devices": "❌",
        "EV Chargers": "❌",
      },
    },
    EFS: {
      EFS: {
        "Solar Inverters": "✅",
        "Storage Devices": "✅",
        "EV Chargers": "❌",
      },
    },
    Elia: {
      Elia: {
        "Solar Inverters": "✅",
        "Storage Devices": "❌",
        "EV Chargers": "❌",
      },
    },
    Elindus: {
      "Elindus Imbalance": {
        "Solar Inverters": "✅",
        "Storage Devices": "✅",
        "EV Chargers": "❌",
      },
    },
    Enervalis: {
      "Enervalis Imbalance": {
        "Solar Inverters": "✅",
        "Storage Devices": "✅",
        "EV Chargers": "❌",
      },
    },
    Engie: {
      Engie: {
        "Solar Inverters": "✅",
        "Storage Devices": "✅",
        "EV Chargers": "❌",
      },
    },
    Eniris: {
      "Eniris Modbus TCP Slave": {
        "Solar Inverters": "✅",
        "Storage Devices": "✅",
        "EV Chargers": "⌛ (coming soon)",
      },
    },
    "EPEX Spot": {
      "EPEX Spot Solar": {
        "Solar Inverters": "✅",
        "Storage Devices": "❌",
        "EV Chargers": "❌",
      },
    },
    "Fleco Power": {
      "Fleco Power": {
        "Solar Inverters": "✅",
        "Storage Devices": "✅",
        "EV Chargers": "❌",
      },
    },
    Flower: {
      Flower: {
        "Solar Inverters": "✅",
        "Storage Devices": "✅",
        "EV Chargers": "❌",
      },
    },
    "Frank Energie": {
      "Frank Energie": {
        "Solar Inverters": "⌛ (coming soon)",
        "Storage Devices": "✅",
        "EV Chargers": "❌",
      },
    },
    Fusebox: {
      "Fusebox Control": {
        "Solar Inverters": "❌",
        "Storage Devices": "✅",
        "EV Chargers": "❌",
      },
    },
    Greenchoice: {
      Greenchoice: {
        "Solar Inverters": "✅",
        "Storage Devices": "✅",
        "EV Chargers": "❌",
      },
    },
    HalloStroom: {
      HalloStroom: {
        "Solar Inverters": "✅",
        "Storage Devices": "✅",
        "EV Chargers": "❌",
      },
    },
    "Hive Power": {
      "Hive Power": {
        "Solar Inverters": "✅",
        "Storage Devices": "✅",
        "EV Chargers": "❌",
      },
    },
    Imby: {
      Imby: {
        "Solar Inverters": "✅",
        "Storage Devices": "✅",
        "EV Chargers": "❌",
      },
    },
    "KratTrade": {
      "KratTrade": {
        "Solar Inverters": "❌",
        "Storage Devices": "✅",
        "EV Chargers": "❌",
      },
    },
    "Next Energy": {
      "Next Energy External Control": {
        "Solar Inverters": "✅",
        "Storage Devices": "✅",
        "EV Chargers": "❌",
      },
    },
    Pleevi: {
      Pleevi: {
        "Solar Inverters": "❌",
        "Storage Devices": "❌",
        "EV Chargers": "✅",
      },
    },
    Powernaut: {
      Powernaut: {
        "Solar Inverters": "✅",
        "Storage Devices": "✅",
        "EV Chargers": "❌",
      },
    },
    Repowered: {
      Repowered: {
        "Solar Inverters": "⌛ (coming soon)",
        "Storage Devices": "✅",
        "EV Chargers": "❌",
      },
    },
    "Scholt Energy": {
      "Scholt Energy": {
        "Solar Inverters": "⌛ (coming soon)",
        "Storage Devices": "✅",
        "EV Chargers": "❌",
      },
    },
    Trevion: {
      Trevion: {
        "Solar Inverters": "✅",
        "Storage Devices": "❌",
        "EV Chargers": "❌",
      },
    },
    "VGT Energy": {
      "VGT Energy": {
        "Solar Inverters": "⌛ (coming soon)",
        "Storage Devices": "✅",
        "EV Chargers": "❌",
      },
    },
    vZEV: {
      "vZEV - Energy Community": {
        "Solar Inverters": "✅",
        "Storage Devices": "✅",
        "EV Chargers": "❌",
      },
    },
    Yuso: {
      Yuso: {
        "Solar Inverters": "❌",
        "Storage Devices": "✅",
        "EV Chargers": "❌",
      },
    },
    "Yuso Solar": {
      "Yuso Solar": {
        "Solar Inverters": "✅",
        "Storage Devices": "❌",
        "EV Chargers": "❌",
      },
    },
  }}
/>

</div>


# KratTrade


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';
import CountriesSupportTable from '@site/src/components/CountriesSupportTable';

<img
    src="/img/sgo/Logo_KratTrade.png"
    alt="KratTrade logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

> [!NOTE]
> KratTrade is not yet fully integrated.
>

# Setting up KratTrade

The manual describes the steps to set up KratTrade External Control on the <BrandName /> <ControllerName />.

When setting up this integration, permission is granted to KratTrade to control the battery.

## Supported Devices

<DeviceSupportTable
  devices={[
    {
        type: 'Solar Inverters',
        variants: 'All',
        customCol: '❌',
    },
    {
        type: 'Storage Devices',
        variants: 'All',
        customCol: '✅'
    },
    {
        type: 'EV Chargers',
        variants: 'All',
        customCol: '❌'
    }
  ]}
    showVariants={true}
    customColumns={{ "customCol": "Supported" }}
/>

## Supported Countries

<CountriesSupportTable
  countries={[
    {
        country: 'Belgium',
        customCol: '❌'
    },
    {
        country: 'Netherlands',
        customCol: '❌'
    },
    {
        country: 'Estonia',
        customCol: '✅'
    },
  ]}
    showVariants={true}
    customColumns={{ "customCol": "Supported" }}
/>

## Prerequisites

### 1. Add the batteries
[Login to the commissioning interface](/Controller/Configuration%20from%20A%20to%20Z/2-accessing-commissioning-interface/) and make sure the [devices are added](/Controller/Configuration%20from%20A%20to%20Z/6-other-devices/) to the <BrandName /> <ControllerName />.

### 2. Check the grid power limits
In the settings, the grid power limits should be set correctly. Click Settings and check the highlighted setting in the image.
If necessary, adjust the settings.

### 3. KratTrade Configuration

KratTrade will provide a Client ID and a Device ID, which must be entered ast the beginning of the configuration.

The files are typically provided in a zip archive file. Unzip the files before proceeding.
- Certificate (file with .pem.crt extension)
- Private key (file with .pem.key extension)
- Root key (file with .pem extension)


## Add 'KratTrade - External Control'
<ClickableImage src="/img/generic/add-external-datasources-en.png" alt="Image 1" maxWidth="650px" />
<ClickableImage src="/img/generic/add-external-datasources-kind-en.png" alt="Image 1" maxWidth="650px" />


In the next page, you have the option to include/exclude devices for remote control.
Ensure to mark all checkboxes of devices you'd like to include.

> [!NOTE]
> When using multiple batteries, they are aggregated into one (virtual) asset for KratTrade.

<ClickableImage src="/img/generic/add-external-datasources-devices-en.png" alt="Image 1" maxWidth="650px" />

'KratTrade' is now set up on the <BrandName /> <ControllerName />.

# Modbus TCP Slave


import { BrandName, ControllerName } from '@site/src/components/customFields';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

# Modbus TCP Slave

With the **<BrandName /> Modbus TCP Slave** external signal, an external controller (a PLC, a SCADA system, a third-party EMS, ...) can read the measurements of the site and send control signals to the <BrandName /> <ControllerName /> over Modbus TCP.

The <BrandName /> <ControllerName /> is the Modbus slave (server). The external controller is the Modbus master (client). Only Modbus TCP is supported.

This page describes version **0.0.5** of the protocol.

> [!NOTE] Registers that are not yet available
> Some registers of the protocol are not served by the current firmware yet. They are marked **Not yet available** in the tables below.

## Supported Devices

<DeviceSupportTable
  devices={[
    {
        type: 'Solar Inverters',
        variants: 'All',
        customCol: '✅'
    },
    {
        type: 'Storage Devices',
        variants: 'All',
        customCol: '✅'
    },
    {
        type: 'EV Chargers',
        variants: 'All',
        customCol: '⌛ (coming soon)'
    }
  ]}
    showVariants={true}
    customColumns={{ "customCol": "Supported" }}
/>

## Prerequisites

### 1. Add the devices
[Log in to the commissioning interface](/Controller/Configuration%20from%20A%20to%20Z/2-accessing-commissioning-interface/) and make sure the [devices are added](/Controller/Configuration%20from%20A%20to%20Z/6-other-devices/) to the <BrandName /> <ControllerName />.

### 2. Check the grid power limits
The [grid limits](/Controller/Configuration%20from%20A%20to%20Z/3-grid-limits/) in the settings of the <BrandName /> <ControllerName /> always apply. Limits written over Modbus can only make them stricter.

### 3. Check the network
The external controller must reach the <BrandName /> <ControllerName /> on the local network, on TCP port 502. Make sure the <BrandName /> <ControllerName /> always gets the same IP address (see [Fixed IP addresses](/Controller/network-configuration/#fixed-ip-addresses)).

## Add 'Eniris Modbus TCP Slave'

1. Go to the 'External signals' tab of the commissioning interface and start the wizard (see [External control signals](/Controller/Configuration%20from%20A%20to%20Z/10-external-control-signals/)).
2. Choose **Remote control** as the kind of control signal, then **Eniris** as the provider and **Eniris Modbus TCP Slave** as the signal.
3. Select the devices that the external controller may control.

<ClickableImage src="/img/generic/add-external-datasources-en.png" alt="Add an external signal" maxWidth="650px" />
<ClickableImage src="/img/generic/add-external-datasources-kind-en.png" alt="Choose the kind of external signal" maxWidth="650px" />
<ClickableImage src="/img/generic/add-external-datasources-devices-en.png" alt="Select the devices" maxWidth="650px" />

> [!WARNING] Add all assets
> Only the devices selected here are controlled by the signal. For grid power setpoint control, make sure **all** controllable assets are added to the external signal.

> [!NOTE]
> Devices of the same type are controlled together, as one (virtual) asset. A battery setpoint is shared out over the batteries in proportion to their nominal power.

The Modbus TCP server of the <BrandName /> <ControllerName /> is now running. The Status column of the 'External signals' tab shows the state of the signal.

<ClickableImage src="/img/generic/external-signals-feedback-en.png" alt="Status of the external signal" maxWidth="650px" />

## Connection settings

| Setting | Value |
|:--|:--|
| Protocol | Modbus TCP |
| IP address | IP address of the <BrandName /> <ControllerName /> on the local network |
| TCP port | 502 |
| Modbus ID (unit ID) | 1 |
| Register addressing | Starts at 0 |
| Byte order | Big endian. For 32-bit and 64-bit values, the most significant register comes first. |
| Read only registers | Read Input Registers (0x04) |
| Read/write registers | Read Holding Registers (0x03), Write Single Holding Register (0x06), Write Multiple Holding Registers (0x10) |

> [!TIP] Register numbering
> The addresses on this page start at 0. If your Modbus tool numbers registers from 1 (for example the 30001 / 40001 notation), add 1 to every address.

> [!TIP] Writing 32-bit values
> Write a 32-bit value with one Write Multiple Holding Registers (0x10) request covering both registers. For example, a battery setpoint of 5000 W is written as `0x0000 0x1388` to registers 1214-1215, and -5000 W as `0xFFFF 0xEC78`.

### Data types

| Type | Size (registers) | Not implemented value |
|:--|:--|:--|
| UINT16 (16-bit unsigned integer) | 1 | `0xFFFF` |
| INT16 (16-bit signed integer) | 1 | `0x8000` |
| UINT32 (32-bit unsigned integer) | 2 | `0xFFFFFFFF` |
| INT32 (32-bit signed integer) | 2 | `0x80000000` |
| UINT64 (64-bit unsigned integer) | 4 | `0xFFFFFFFFFFFFFFFF` |
| INT64 (64-bit signed integer) | 4 | `0x8000000000000000` |
| STRING (UTF-8, padded with `0x00`) | 16 | - |

- A data register that is not implemented contains the not implemented value of its type.
- Write registers that are not implemented can still be written. No error is raised.
- Addresses between the blocks of the register map are not mapped. A read request that covers them is answered with exception 02 (Illegal Data Address), so read every block separately.
- The accuracy of the measurements and setpoints depends on the devices and energy meters of the installation.

## How control works

### Enabling remote control
Active and reactive power remote control are enabled separately:

| | Active power | Reactive power |
|:--|:--|:--|
| Enable remote control | 1001 = 1 | 1002 = 1 |
| Control mode | 1003 | 1004 |
| Mode 0: Storage & PV setpoint control | Storage registers 1201, 1214 and PV registers 1301, 1303 | Storage registers 1202, 1216 and PV registers 1302, 1310 |
| Mode 1: Grid setpoint control | Grid power setpoint 1101 | Grid reactive power setpoint 1103 |

When remote control is disabled (0), the <BrandName /> <ControllerName /> uses its own local control modes.

> [!WARNING] Active and reactive power control together
> Active and reactive power remote control are not executed at the same time. When both 1001 and 1002 are 1, only the active power control is executed if 1003 = 0, and only the reactive power control if 1003 = 1. Enable only the one you need.

> [!NOTE] Reactive power control
> Not every battery or PV inverter supports reactive power control. Check with our [support team](https://eniris.io/support) first.

### Watchdog
Register 1000 is a fallback counter in seconds. It decreases by 1 every second. When it reaches 0, the <BrandName /> <ControllerName /> stops applying the remote control signal and falls back to its local control modes, until the counter is written again.

- Write the counter regularly, well before it reaches 0. For example, write 60 every 10 seconds.
- Valid values are 0 to 32400 seconds (9 hours), or -1 to disable the watchdog. With -1, the last received command is applied for as long as remote control is enabled.
- After the signal starts, the counter is **120 seconds**.
- The grid import and export limits (1010, 1012) keep applying when the counter reaches 0.

### Limits and setpoints
- Active and reactive power limits are dynamic limits. They always stay within the limits set in the settings of the <BrandName /> <ControllerName />, and the most restrictive limit applies. For example, if you write an export limit of 20 kW while the settings allow 5 kW of export, the export is limited to 5 kW. If you then write 2 kW, the export is limited to 2 kW.
- The grid import and export limits (1010, 1012) apply as soon as they are written, also when remote control is disabled. Write the not implemented value (`0xFFFFFFFF`) to remove them.
- Setpoints that are not allowed are ignored or only partly executed. For example, a battery cannot be discharged below its minimum state of charge, or charged with more power than its nominal power.
- If a control mode needs a setpoint or thresholds that still hold the not implemented value, the Status column of the 'External signals' tab shows an error, and the remote control signal is not applied completely.

> [!WARNING] Write setpoints and limits continuously
> Setpoints and limits are not guaranteed to be kept after a restart of the <BrandName /> <ControllerName /> or of the signal. Write them continuously. Control modes, setpoints and thresholds only apply while remote control is enabled and the watchdog has not expired.

### Examples

**Charge the batteries at 5 kW**
1. 1000 = 60 (watchdog)
2. 1003 = 0 (Storage & PV setpoint control)
3. 1201 = 1 (storage setpoint mode)
4. 1214-1215 = 5000 W
5. 1001 = 1 (enable active power remote control)
6. Repeat steps 1 and 4 every 10 seconds.

**Keep the grid power at 0 W**
1. 1000 = 60 (watchdog)
2. 1003 = 1 (grid setpoint control)
3. 1101-1102 = 0 W
4. 1001 = 1 (enable active power remote control)
5. Repeat steps 1 and 3 every 10 seconds.

**Limit the PV production to 10 kW**
1. 1000 = 60 (watchdog)
2. 1003 = 0 (Storage & PV setpoint control)
3. 1301 = 1 (PV setpoint mode)
4. 1303-1304 = 10000 W
5. 1001 = 1 (enable active power remote control)
6. Repeat steps 1 and 4 every 10 seconds.

**Do not export to the grid**
1. 1012-1013 = 0 W (grid export limit). No remote control needs to be enabled for this.

## Read only registers
Supported Modbus function: Read Input Registers (0x04).

### Device identification

| Address | Type | Size | Unit | Name | Description |
|:--|:--|:--|:--|:--|:--|
| 0 | UINT32 | 2 | - | Magic number | Always `0x454E4952` (ASCII "ENIR"). Identifies a device that follows this protocol. |
| 2 | STRING | 16 | - | Manufacturer | Padded with `0x00`. |
| 18 | STRING | 16 | - | Serial number | Serial number of the <BrandName /> <ControllerName />. Padded with `0x00`. |
| 34 | UINT16 | 1 | - | Total / single device | 0 or `0xFFFF` = the registers hold the totals of all connected inverters, EV chargers and loads, and the energy meter (if any) is the grid meter. 1 = the registers hold the data of a single inverter, EV charger, load or energy meter. The <BrandName /> <ControllerName /> always reports totals (0). |
| 35 | UINT16 | 1 | - | Protocol version major number | 0 for this version of the protocol. |
| 36 | UINT16 | 1 | - | Protocol version minor number | 0 for this version of the protocol. |
| 37 | UINT16 | 1 | - | Protocol version patch number | 5 for this version of the protocol. The current firmware still reports version 0.0.1 in registers 35-37. |
| 38 | STRING | 16 | - | Model name | Padded with `0x00`. |

### Grid energy meter
Sign convention: for active power, negative is towards the grid and positive is towards the installation. For reactive power, negative is capacitive behaviour of the installation and positive is inductive behaviour.

| Address | Type | Size | Unit | Name | Description |
|:--|:--|:--|:--|:--|:--|
| 100 | UINT16 | 1 | - | Energy meter presence | 0 = no grid energy meter, 1 = there is a grid energy meter. Without a grid energy meter, the registers below can hold the not implemented value. |
| 101 | INT32 | 2 | W | Total active power | |
| 103 | UINT16 | 1 | 0.1 A | Current L1 | |
| 104 | UINT16 | 1 | 0.1 A | Current L2 | |
| 105 | UINT16 | 1 | 0.1 A | Current L3 | |
| 106 | UINT16 | 1 | 0.1 A | Current N | |
| 107 | UINT16 | 1 | V | Voltage L1-N | |
| 108 | UINT16 | 1 | V | Voltage L2-N | |
| 109 | UINT16 | 1 | V | Voltage L3-N | |
| 110 | UINT16 | 1 | V | Voltage L1-L2 | |
| 111 | UINT16 | 1 | V | Voltage L2-L3 | |
| 112 | UINT16 | 1 | V | Voltage L3-L1 | |
| 113 | UINT16 | 1 | mHz (0.001 Hz) | Frequency | |
| 114 | INT32 | 2 | W | Active power L1 | |
| 116 | INT32 | 2 | W | Active power L2 | |
| 118 | INT32 | 2 | W | Active power L3 | |
| 120 | INT32 | 2 | VAr | Total reactive power | |
| 122 | INT32 | 2 | VAr | Reactive power L1 | |
| 124 | INT32 | 2 | VAr | Reactive power L2 | |
| 126 | INT32 | 2 | VAr | Reactive power L3 | |
| 128 | UINT64 | 4 | 0.1 kWh | Total import active energy | |
| 132 | UINT64 | 4 | 0.1 kWh | Total export active energy | |
| 136 | UINT64 | 4 | 0.1 kVArh | Total inductive reactive energy | |
| 140 | UINT64 | 4 | 0.1 kVArh | Total capacitive reactive energy | |

### Total power data

| Address | Type | Size | Unit | Name | Description |
|:--|:--|:--|:--|:--|:--|
| 200 | UINT32 | 2 | W | Total PV produced active power | Positive only. |
| 202 | INT32 | 2 | W | Total battery active power | Negative is towards the grid (discharging), positive is towards the installation (charging). |
| 204 | INT32 | 2 | W | Total EV active power | Negative is towards the grid (V2G), positive is towards the installation (charging). |
| 206 | UINT32 | 2 | W | Total on/off load power | Relays, boilers, HVAC. Positive only. |
| 208 | INT32 | 2 | W | Total uncontrolled load power | Negative is towards the grid (export), positive is towards the installation (import). Can be negative if some production devices have not been added to the <BrandName /> <ControllerName />. |
| 210 | INT32 | 2 | VAr | Total PV reactive power | Negative is capacitive behaviour of the installation, positive is inductive behaviour. |
| 212 | UINT16 | 1 | 0.1 % | Total battery state of charge (SoC) | Positive only. |
| 213 | INT32 | 2 | VAr | Total battery reactive power | Negative is capacitive behaviour of the installation, positive is inductive behaviour. **Not yet available:** reads 0. |
| 220 | UINT64 | 4 | 0.1 kWh | Total PV produced energy | |
| 224 | UINT64 | 4 | 0.1 kWh | Total battery charged energy | |
| 228 | UINT64 | 4 | 0.1 kWh | Total battery discharged energy | |
| 232 | UINT64 | 4 | 0.1 kWh | Total EV consumed energy | **Not yet available:** reads 0. |
| 240 | UINT32 | 2 | 0.1 kWh | Battery rated energy | **Not yet available:** not mapped yet. |
| 242 | UINT32 | 2 | 0.1 kWh | Battery available charge energy | **Not yet available:** not mapped yet. |
| 244 | UINT32 | 2 | 0.1 kWh | Battery available discharge energy | **Not yet available:** not mapped yet. |
| 250 | UINT32 | 2 | W | Total PV nominal power | Positive only. |
| 252 | UINT32 | 2 | W | Total storage nominal power | Positive only. |

### Feedback data

| Address | Type | Size | Unit | Name | Description |
|:--|:--|:--|:--|:--|:--|
| 300 | UINT32 | 2 | W | Applied grid import power limit | The grid import limit the <BrandName /> <ControllerName /> actually applies, after margins and safety factor. Can be lower than the written limit while a grid setpoint is active, because a grid setpoint is applied by adjusting the grid limits. |
| 302 | UINT32 | 2 | W | Applied grid export power limit | The grid export limit the <BrandName /> <ControllerName /> actually applies, after margins and safety factor. Can be lower than the written limit while a grid setpoint is active, because a grid setpoint is applied by adjusting the grid limits. |
| 310 | INT32 | 2 | W | Applied storage active setpoint | |
| 312 | UINT32 | 2 | W | Applied PV active setpoint | |
| 320 | INT32 | 2 | VAr | Applied storage reactive setpoint | |
| 322 | INT32 | 2 | VAr | Applied PV reactive setpoint | |
| 350 | UINT32 | 2 | W | Available storage charge power | Absolute value: the present battery power is not taken into account. |
| 352 | UINT32 | 2 | W | Available storage discharge power | Absolute value: the present battery power is not taken into account. |

## Read/write registers
Supported Modbus functions: Read Holding Registers (0x03), Write Single Holding Register (0x06), Write Multiple Holding Registers (0x10).

### General

| Address | Type | Size | Unit | Initial value | Name | Description |
|:--|:--|:--|:--|:--|:--|:--|
| 1000 | INT16 | 1 | s | 120 | Watchdog fallback counter | -1 = watchdog disabled, the last received command is always applied. 0 to 32400 = number of seconds the last received command is applied. Other values are invalid. Decreases by 1 every second until it reaches 0. See [Watchdog](#watchdog). |
| 1001 | UINT16 | 1 | - | 0 | Active power remote control enabled | 0 = disabled, the <BrandName /> <ControllerName /> falls back to local control. 1 = enabled. |
| 1002 | UINT16 | 1 | - | 0 | Reactive power remote control enabled | 0 = disabled, the <BrandName /> <ControllerName /> falls back to local control. 1 = enabled. |
| 1003 | UINT16 | 1 | - | 0 | Active power control mode | 0 = Storage & PV active power setpoint control. 1 = Grid active power setpoint control. |
| 1004 | UINT16 | 1 | - | 0 | Reactive power control mode | 0 = Storage & PV reactive power setpoint control. 1 = Grid reactive power setpoint control. |
| 1010 | UINT32 | 2 | W | `0xFFFFFFFF` | Grid import power limit | Maximum grid import power. Still applied when the watchdog counter reaches 0. |
| 1012 | UINT32 | 2 | W | `0xFFFFFFFF` | Grid export power limit | Maximum grid export power. Still applied when the watchdog counter reaches 0. |

### Grid power control

| Address | Type | Size | Unit | Initial value | Name | Description |
|:--|:--|:--|:--|:--|:--|:--|
| 1100 | UINT16 | 1 | - | 0 | Limit time base | Reserved for future use: the time scale in which the limits apply (instantaneous, quarter hour, ...). |
| 1101 | INT32 | 2 | W | `0x80000000` | Grid power setpoint | Positive is import, negative is export. Used when 1001 = 1 and 1003 = 1. |
| 1103 | INT32 | 2 | VAr | `0x80000000` | Grid reactive power setpoint | Positive is inductive / imported reactive power, negative is capacitive / exported reactive power. Used when 1002 = 1 and 1004 = 1. |

### Storage control

| Address | Type | Size | Unit | Initial value | Name | Description |
|:--|:--|:--|:--|:--|:--|:--|
| 1200 | UINT16 | 1 | - | 0 | Control granularity | 0 = control all assets together. 1 = control assets individually (reserved for future use, not available). |
| 1201 | UINT16 | 1 | - | 0 | Active power control mode | 0 = local control. 1 = setpoint (1214). 2 = self-consumption optimisation. 3 = cost optimisation. 4 = peak shaving (1218 to 1224). |
| 1202 | UINT16 | 1 | - | 0 | Reactive power control mode | 0 = local control. 1 = setpoint (1216). 2 = peak shaving (reserved for future use, not available). |
| 1203 | UINT32 | 2 | W | `0xFFFFFFFF` | Charge power limit | Maximum battery charge power (positive number). **Not yet available:** accepted but ignored. |
| 1205 | UINT32 | 2 | W | `0xFFFFFFFF` | Discharge power limit | Maximum battery discharge power (positive number). **Not yet available:** accepted but ignored. |
| 1207 | UINT32 | 2 | VAr | `0xFFFFFFFF` | Inductive reactive power limit | Maximum inductive / consumed reactive power. Reserved for future use, not available. |
| 1209 | UINT32 | 2 | VAr | `0xFFFFFFFF` | Capacitive reactive power limit | Maximum capacitive / exported reactive power. Reserved for future use, not available. |
| 1211 | UINT16 | 1 | A | `0xFFFF` | Current limit | Maximum current (positive number). **Not yet available:** accepted but ignored. |
| 1212 | UINT16 | 1 | 0.1 % | 50 | Min. SoC | Minimum state of charge. The most restrictive of this value and the device settings applies: if 20 % is configured in the device settings and 10 % is written over Modbus, the minimum SoC is 20 %. **Not yet available:** accepted but ignored, the device settings apply. |
| 1213 | UINT16 | 1 | 0.1 % | 1000 | Max. SoC | Maximum state of charge. The most restrictive of this value and the device settings applies: if 95 % is configured in the device settings and 100 % is written over Modbus, the maximum SoC is 95 %. **Not yet available:** accepted but ignored, the device settings apply. |
| 1214 | INT32 | 2 | W | `0x80000000` | Battery active power setpoint | Positive is charging, negative is discharging. Used when 1201 = 1. |
| 1216 | INT32 | 2 | VAr | `0x80000000` | Battery reactive power setpoint | Positive is inductive / consumed reactive power, negative is capacitive / exported reactive power. Used when 1202 = 1. |
| 1218 | INT32 | 2 | W | `0x80000000` | Start discharging above (peak shaving) | Grid power above which the battery starts discharging. The grid power is tuned down to this value while discharging. |
| 1220 | INT32 | 2 | W | `0x80000000` | Stop discharging below (peak shaving) | Grid power below which a discharging battery stops discharging. |
| 1222 | INT32 | 2 | W | `0x80000000` | Stop charging above (peak shaving) | Grid power above which a charging battery stops charging. |
| 1224 | INT32 | 2 | W | `0x80000000` | Start charging below (peak shaving) | Grid power below which the battery starts charging. The grid power is tuned to this value while charging. |

For peak shaving (1201 = 4), all four thresholds 1218 to 1224 must be written. The grid power is positive for import and negative for export. See [Peak shaving](/Controller/Configuration%20from%20A%20to%20Z/8-local-control-modes/extra-peak-shaving-battery/) for an example of the thresholds.

### PV control

| Address | Type | Size | Unit | Initial value | Name | Description |
|:--|:--|:--|:--|:--|:--|:--|
| 1300 | UINT16 | 1 | - | 0 | Control granularity | 0 = control all assets together. 1 = control assets individually (reserved for future use, not available). |
| 1301 | UINT16 | 1 | - | 0 | Active power control mode | 0 = local control. 1 = setpoint (1303). 2 = cost optimisation. 3 = feed-in restriction up to the allowed grid export limit. |
| 1302 | UINT16 | 1 | - | 0 | Reactive power control mode | 0 = local control. 1 = setpoint (1310). 2 = peak shaving (reserved for future use, not available). |
| 1303 | UINT32 | 2 | W | `0xFFFFFFFF` | PV production power limit | Maximum PV production power (positive number). Used when 1301 = 1. |
| 1305 | UINT32 | 2 | VAr | `0xFFFFFFFF` | Inductive reactive power limit | Maximum inductive / consumed reactive power. Reserved for future use, not available. |
| 1307 | UINT32 | 2 | VAr | `0xFFFFFFFF` | Capacitive reactive power limit | Maximum capacitive / exported reactive power. Reserved for future use, not available. |
| 1309 | UINT16 | 1 | A | `0xFFFF` | Current limit | Maximum current (positive number). Reserved for future use, not available. |
| 1310 | INT32 | 2 | VAr | 0 | PV reactive power setpoint | Positive is inductive / consumed reactive power, negative is capacitive / exported reactive power. Used when 1302 = 1. |

### Heat pump / airco / boiler control
**Not yet available.** These registers can be written, but are ignored.

| Address | Type | Size | Unit | Initial value | Name | Description |
|:--|:--|:--|:--|:--|:--|:--|
| 1400 | UINT16 | 1 | - | 0 | Control granularity | 0 = control all assets together. 1 = control assets individually (reserved for future use). |
| 1401 | UINT16 | 1 | - | 0 | Active power control mode | 0 = local control. 1 = setpoint. 2 = self-consumption optimisation. 3 = cost optimisation. 4 = peak shaving (discretely controlled assets) / load balancing (continuously controlled assets). |
| 1402 | UINT16 | 1 | - | 0 | Discrete setpoint signal | 0 = autonomous operation (normal operation). 1 = encouraged on. 2 = forced on. 3 = forced off. Whether to heat or cool is left to the heat pump / airco / boiler. Ignored by continuously controlled devices. |
| 1403 | UINT32 | 2 | W | 0 | Power setpoint | Always positive. Whether to heat or cool is left to the heat pump / airco / boiler. Ignored by discretely controlled devices. |
| 1405 | INT32 | 2 | W | 0 | Forced off grid power threshold (peak shaving) | Discrete control: above this grid power, the asset is forced off. Ignored by continuously controlled devices. |
| 1407 | INT32 | 2 | W | 0 | Encouraged on grid power threshold (peak shaving) | Discrete control: below this grid power, the asset is encouraged to be on. Must be at least the nominal power below the forced off threshold. Ignored by continuously controlled devices. |
| 1409 | INT32 | 2 | W | 0 | Forced on grid power threshold (peak shaving) | Discrete control: below this grid power, the asset is forced on. Must be at least the nominal power below the forced off threshold, and below the encouraged on threshold. Ignored by continuously controlled devices. |

### On/off load control
**Not yet available.** These registers can be written, but are ignored.

| Address | Type | Size | Unit | Initial value | Name | Description |
|:--|:--|:--|:--|:--|:--|:--|
| 1500 | UINT16 | 1 | - | 0 | Control granularity | 0 = control all assets together. 1 = control assets individually (reserved for future use). |
| 1501 | UINT16 | 1 | - | 0 | Active power control mode | 0 = local control. 1 = setpoint. 2 = self-consumption optimisation. 3 = cost optimisation. 4 = peak shaving. |
| 1502 | UINT16 | 1 | - | 0 | Discrete setpoint signal | 0 = off. 1 = on. The asset can be kept on or off for a minimum time, even if the signal changes, to prevent continuous switching. |
| 1503 | INT32 | 2 | W | 0 | Off grid power threshold (peak shaving) | Discrete control: above this grid power, the asset is switched off. |
| 1505 | INT32 | 2 | W | 0 | On grid power threshold (peak shaving) | Discrete control: below this grid power, the asset is switched on. |

### Backup power control
**Not yet available.** These registers can be written, but are ignored.

| Address | Type | Size | Unit | Initial value | Name | Description |
|:--|:--|:--|:--|:--|:--|:--|
| 1600 | UINT16 | 1 | - | 0 | Control granularity | 0 = control all assets together. 1 = control assets individually (reserved for future use). |
| 1601 | UINT16 | 1 | - | 0 | Active power control mode | 0 = local control. 1 = setpoint. 2 = battery support. |
| 1602 | UINT16 | 1 | - | 0 | Discrete setpoint | 0 = switch the backup generator off. 1 = switch the backup generator on. The generator can be kept on for a minimum time to prevent wear; switching off is ignored during that time. |
| 1603 | UINT16 | 1 | 1 % | 0 | Battery SoC switch-on threshold | The backup generator switches on when the total battery state of charge is below this value. |
| 1604 | UINT16 | 1 | 1 % | 100 | Battery SoC switch-off threshold | The backup generator switches off when the total battery state of charge is above this value. Must be higher than the switch-on threshold. |

### EV charger control
**Not yet available.** These registers can be written, but are ignored.

| Address | Type | Size | Unit | Initial value | Name | Description |
|:--|:--|:--|:--|:--|:--|:--|
| 1700 | UINT16 | 1 | - | 0 | Control granularity | 0 = control all assets together. 1 = control assets individually (reserved for future use). |
| 1701 | UINT16 | 1 | - | 0 | Active power control mode | 0 = local control. 1 = setpoint (charge limit). 2 = self-consumption optimisation. 3 = cost optimisation. 4 = load balancing. |
| 1702 | UINT16 | 1 | 0.1 A | 0 | Total AC charge current limit | Used when 1701 = 1. The limit applies to all connectors of the EV chargers together. |

## Version history

| Date | Version | Changes |
|:--|:--|:--|
| 13/06/2025 | 0.0.1 | Initial draft of the protocol. |
| 20/04/2026 | 0.0.2 | Added the available storage charge and discharge power registers (350, 352). |
| 28/04/2026 | 0.0.3 | Added the battery state of charge register (212) and the nominal power registers (250, 252). |
| 07/08/2026 | 0.0.4 | Fixed the description of the total battery active power. Added the battery reactive power register (213). |
| 31/08/2026 | 0.0.5 | Added the battery energy registers (240, 242, 244). |


# Monitoring


import { FolderOverview } from '@/components/FolderOverview';

# Monitoring

<FolderOverview folder="Controller/External Signals/Monitoring" />


# Monitoring API Signal


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';
import DownloadButton from '@site/src/components/DownloadButton';

# External Monitoring API

## Goal

For integrators requiring real-time visibility, polling our Telemetry API introduces delays and introduces overhead both on the end of the integrator and on the end of <BrandName />.
To solve this, the controller can be configured to send telemetry to a designated endpoint which is provided by the integrator.
This 'webhook mechanism' enables live data streams with near-zero latency, bypassing the limitations of traditional API polling.

## First-time Configuration (Starting point for new users)

### 1. Check your network
Ensure that your <BrandName /> <ControllerName /> has an active network connection.

### 2. Add your devices
[Login to the commissioning interface](/Controller/Configuration%20from%20A%20to%20Z/2-accessing-commissioning-interface/) and make sure the [devices are added](/Controller/Configuration%20from%20A%20to%20Z/6-other-devices/) to the <BrandName /> <ControllerName />.

### 3. Configure the webhook via 'external data sources'
<ClickableImage src="/img/generic/add-external-datasources-en.png" alt="Image 1" maxWidth="650px" />
<ClickableImage src="/img/generic/add-external-datasources-kind-en.png" alt="Image 1" maxWidth="650px" />
<ClickableImage src="/img/generic/add-external-datasources-brand-en.png" alt="Image 1" maxWidth="650px" />

### 4. Enter the parameters

1. The URL and endpoint of the API

2. The bearer authorization token used for the API request. To prevent a compromised controller from being used to falsify data from other devices, we strongly recommend using unique tokens per controller and binding each token to a specific location in your implementation.

3. The frequency at which data is pushed (in seconds, default is 60s)

4. Select which data should be pushed:
    - Device level data contains all the data fields specified below, per individual node connected to the <BrandName /> <ControllerName />.
    - Device type level contains aggregated data on device type level (e.g. solar, storage, fixed)

After, select to include all devices.

<ClickableImage src="/img/generic/add-external-datasources-devices-en.png" alt="Image 1" maxWidth="650px" />

## Endpoint Data

The endpoint should accept a **HTTP POST request** with the following data:

If the device type level has been selected:

```json
{
    "time": "<Unix Timestamp>",
    "siteNodeId": "<Site NodeID>",
    "grid": "<Grid Fields>",
    "solar": "<Solar Fields>",
    "storage": "<Storage Fields>",
    "heat_pump": "<Heat Pump Fields>",
    "switched_load": "<Switched Load Fields>",
    "variable_power_load": "<Variable Power Load Fields>",
}
```

If the device level has been selected:
```json
{
    "time": "<Unix Timestamp>",
    "siteNodeId": "<Site NodeID>",
    "nodeId1": "<Node Fields>",
    "nodeId2": "<Node Fields>",
    ...
}
```

More information about the individual fields can be found here: [Feedback Payload Structure](/Controller/External%20Signals/MQTT/eniris-mqtt#mqtt-feedback-payload-structure).


# Baselines


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';
import DownloadButton from '@site/src/components/DownloadButton';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

# Baselines

> [!CAUTION] NOTE:
> Baselines are not supported on all controllers. Please contact support for more information.

Before continuing, make sure your network and devices are ready by following the [MQTT Setup](/Controller/External%20Signals/MQTT/setup/) guide.

The Eniris MQTT credentials used by the baseline client must be requested through the [Eniris webshop](https://webshop.eniris.com/).

## 1. Supported Devices

<DeviceSupportTable
  devices={[
    {
        type: 'Solar Inverters',
        variants: 'All',
        customCol: '❌'
    },
    {
        type: 'Storage Devices',
        variants: 'All',
        customCol: '✅'
    },
    {
        type: 'EV Chargers',
        variants: 'All',
        customCol: '❌'
    }
  ]}
    showVariants={true}
    customColumns={{ "customCol": "Supported" }}
/>

## 2. Setup

This guide will help you configure Baselining Predictions on your <BrandName /> <ControllerName />.

## What you need
1. <BrandName /> <ControllerName /> with internet connectivity.
2. MQTT setup. Please refer to the main MQTT page for more information: [MQTT Setup](/Controller/External%20Signals/MQTT/eniris-mqtt/#first-time-configuration-starting-point-for-new-users)

### 1. Add your devices
[Login to the commissioning interface](/Controller/Configuration%20from%20A%20to%20Z/2-accessing-commissioning-interface/) and make sure the [devices are added](/Controller/Configuration%20from%20A%20to%20Z/6-other-devices/) to the <BrandName /> <ControllerName />.

### 2. Add the Baseline External Signal
<ClickableImage src="/img/generic/add-external-datasources-en.png" alt="Image 1" maxWidth="650px" />
<ClickableImage src="/img/generic/add-external-datasources-kind-en.png" alt="Image 1" maxWidth="650px" />
<ClickableImage src="/img/generic/add-external-datasources-brand-en.png" alt="Image 1" maxWidth="650px" />

### 3. Fill in the parameters

The following parameters are customisable:

#### 3.1 Interval Length
Type: integer

The length of the interval indicates the frequency of a new prediction point.
This is generally set to 15 minutes or one hour, depending on the energy market.

#### 3.2 Number of intervals
Type: integer

The number of intervals of the length set above.
E.g. If 96 intervals of 15 minutes are created, we have predictions for the next 24 hours.

#### 3.3 Creation format

The baselines can be created daily or at a fixed interval.
These two formats have different use cases.

**3.3.1 Daily**

The baselines are created once a day, at a specific hour.
This format allows you to select an activation hour- which is how long after creation the baseline becomes active.

E.g. A baseline is created at 9AM but only active on the next day, so the activation hour is set to 15h.

***3.3.1.1 Creation Hour***

Type: integer

The hour at which the baseline is created every day.

***3.3.1.2 Activation Hour***

Type: integer

The numer of hours after the creation hour the baseline is activated.

**3.3.2 Fixed Interval**

Baselines are generated at a fixed interval.
Baselines are generated shortly before their activation time, and activated immediately.
E.g. The baseline for the next hour is generated at :59.

***3.3.2.1 Refresh Interval***
Type: integer

How often the baseline is regenerated. 
This is commonly set to 15 minutes, or one hour.

#### 3.4 Refresh Parameter
Type: integer

A constant which specifies how long before the activation time we generate the baseline. Generally set to one or two minutes.

#### 3.5 Follow Baselines
Type: boolean

If set to true, the devices follow the baseline that is generated.
If set to false, the baselines are not followed directly. The baselines are instead used as a prediction, and followed as closely as possible. The device actions can deviate from the generated baseline, depending on uncontrollable realtime variables, such as PV prediction, uncontrollable loads and EV charging periods.

#### 3.6 Custom Predictors (W.I.P.)

Customised prediction algorithms are used to create the baselines.

### 4. Enable the Baseline signal
Select all devices that you'd wish to include in MQTT Remote Control.

<ClickableImage src="/img/generic/add-external-datasources-devices-en.png" alt="Image 1" maxWidth="650px" />

### 5. Baseline signal is added
The Baseline interface has now been activated on the <BrandName /> <ControllerName />.

We are now ready to continue. The Status column will raise any potential errors during setup.

## 3. Baseline Collection

Baselines can be fetched from the controller using MQTT.

The following topic is used to send a request to fetch the baselines:
```
standard1/rp_one_s/remoteBaselineMetrics/'controller SN'
```
where ```<Controller SN>``` should be replaced with the serial number of the <BrandName /> <ControllerName /> that is sending the feedback.

The following message format should be used to fetch baselines:
```json
{
    "extraTags": {
        "nodeId": <Controller SN>_site_0>
    },
    "time": <Unix Timestamp>,
    "fields": {}
}
```

The following topic is used to receive baseline data:
```
standard1/outbound/remoteBaselineMetrics/feedback/<Controller SN>
```
where ```<Controller SN>``` should be replaced with the serial number of the <BrandName /> <ControllerName /> that is sending the feedback.

Baseline feedback is sent in the following format:
```json
{
    "time": <Unix Timestamp>,
    "data": {
        "baseline": {
            "<Device Node ID>": [
                {
                    "endTimeUnix": "",
                    "power_W": ""
                },
            ],
        },
        "nextBaseline": {
            "<Device Node ID>": [
                {
                    "endTimeUnix": "",
                    "power_W": ""
                },
            ],
        },
        "error": {
            <Errors occured during execution>
        }
        "response_code": <Response Code>
    },
    "fields": {},
    "requestTime": <Unix Timestamp>,
    "time": <Unix Timestamp>,
    "siteNodeId": <Controller SN>_site_0>
}
```

## 4. Python demo script

Please download the file below in your preferred Python IDE. Fill in your serial number and the MQTT credentials requested through the [Eniris webshop](https://webshop.eniris.com/), then execute the script:
<DownloadButton file="/docs/eniris/mqtt-demo-baselines-2026-04-28.zip" label="Download Tutorial Files" />


# Live MQTT control


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';
import DownloadButton from '@site/src/components/DownloadButton';

# Live MQTT Control

> [!TIP]
> The Live MQTT control is meant for live control. For sending schedules ahead of time, see [Scheduled MQTT Control](/Controller/External%20Signals/MQTT/eniris-schedules-mqtt/) instead.

This guide will help you configure MQTT on your <BrandName /> <ControllerName /> to remotely control and monitor battery and solar panel installations.

## First-time Configuration (Starting point for new users)
I have a <BrandName /> <ControllerName /> that I'd like to setup for MQTT Remote Control.

Before continuing, make sure your network and devices are ready by following the [MQTT Setup](/Controller/External%20Signals/MQTT/setup/) guide.

Request the required Eniris MQTT username and password through the [Eniris webshop](https://webshop.eniris.com/) before starting the configuration. Support tickets and SmartgridX/Insights are not provisioning channels for new MQTT credentials.

### 1. Add the MQTT external signal
<ClickableImage src="/img/generic/add-external-datasources-en.png" alt="Image 1" maxWidth="650px" />
<ClickableImage src="/img/generic/add-external-datasources-kind-en.png" alt="Image 1" maxWidth="650px" />
<ClickableImage src="/img/generic/add-external-datasources-brand-en.png" alt="Image 1" maxWidth="650px" />
<ClickableImage src="/img/generic/add-external-datasources-mqtt-en.png" alt="Image 1" maxWidth="650px" />

### 2. Enable MQTT remote signal
The fallback mechanism timeout tells the <BrandName /> <ControllerName /> how long it should wait for new commands. When the <BrandName /> <ControllerName /> stops receiving commands, it automatically picks up the default strategy after this timeout.

After, select all devices that you'd wish to include in MQTT Remote Control.

<ClickableImage src="/img/generic/mqtt-user-inputs-en.png" alt="Image 1" maxWidth="650px" />
<ClickableImage src="/img/generic/add-external-datasources-devices-en.png" alt="Image 1" maxWidth="650px" />

### 3. Remote signal is added
The MQTT Remote Control interface has now been activated on the <BrandName /> <ControllerName />.

We are now ready to send some basics commands using a simple example. The Status column tells you if any command is active.

<ClickableImage src="/img/generic/external-signals-feedback-en.png" alt="Image 1" maxWidth="650px" />


## Python demo script
A good first starting point would be to test your newly setup integration with a simple example.

This test code does a simple job of continuously sending the following commands:
- Battery: Charge at 5 kW
- Solar: Set power to 0 kW

The <BrandName /> <ControllerName /> continuously responds with a 'feedback' message containing the observed grid and asset power values. This feature is also included in this example.

Please download the file below in your preferred Python IDE. Fill in your serial number and the MQTT credentials requested through the [Eniris webshop](https://webshop.eniris.com/), then execute the script:
<DownloadButton file="/docs/eniris/mqtt_demo_25-03-21.zip" label="Download Tutorial Files" />

When the above is successful, you can continue with sending other type of commands. All commands are described in our MQTT Remote Control Documentation.


## MQTT Documentation for Sending Commands
This section details the MQTT messaging format and payload requirements for remotely controlling power policies on devices within the <BrandName /> <ControllerName />'s network.

### MQTT Topic
The MQTT topic used for sending commands is structured as follows:
```
standard1/rp_one_s/remoteControlMetrics/'controller SN'
```
Where 'controller SN' should be replaced with the actual serial number of the <BrandName /> <ControllerName /> you intend to control.

### MQTT Payload Structure
Commands are sent as JSON payloads. The payload structure is designed to specify various power management policies and setpoints for different components of the smart grid system. The following examples use fictional identifiers and illustrative limits. Replace the site node ID, timestamp and values with those appropriate for your installation:

```json
{
    "extraTags": {
        "nodeId": "DEMO_CONTROLLER_SiteA"
    },
    "time": 1791547200,
    "fields": {
        "storage_policy": "setpoint",
        "storage_power_setpoint_w": 5000,
        "site_policy": "limit",
        "site_import": 25000
    }
}
```

#### Fields description

> [!TIP]
> Multiple device types (e.g. batteries + solar) can be controlled at the same time.

- extraTags (Object):
    - nodeId (String): A unique identifier for the node within the <BrandName /> <ControllerName />'s network. Use the actual site node ID from the installation. It may differ from the serial number followed by '_site_0'; do not assume that suffix.
- time (Integer): Unix timestamp in seconds indicating the time when the message is sent.
- fields (Object):
    - `<Component>_policy` (String): Policy type for the component. If omitted, a previous group policy can remain active until its original timeout. Use an explicit `fallback` policy to relinquish control.
    - `<Component>_power_setpoint_w` (Float): Desired power setpoint in watts for the component. This is optional and only relevant if a corresponding policy is specified.


#### Components and Policies

> [!NOTE]
> Assets of the same type (e.g. two batteries) will be combined as one component. For example, when two 5 kWh batteries are installed, it will be treated as one 10 kWh battery.

Each component in the **fields** object can include a policy and a power setpoint. The following components can be controlled:
- **solar_policy** and **solar_power_setpoint_w**:
    - Controls the solar power generation policy and setpoint. Supported policies:
        - Policy setpoint: Set the maximum power produced by all connected solar installations combined. Field solar_power_setpoint_w should be set to the production power limit in watts.
        - Policy feed-in-restriction: Produce at full power, following current grid limits.
        - Policy cost: Enables day-ahead price (EPEX Spot market) cost minimization on the solar production. When negative injection prices occur, we curtail production to own consumption. When both the offtake and injection price are negative, we switch off all solar installations. Field solar_power_setpoint_w is ignored.
        - Policy off: Disables all interaction for all solar assets. Warning: limits are not being guarded in this mode. Field solar_power_setpoint_w is ignored.

- **storage_policy** and **storage_power_setpoint_w**:
    - Controls the energy storage system policy and power discharge or charge rate.
        - Policy setpoint: Set the total charge power (positive setpoint) or discharge power (negative setpoint) for the group of batteries. When multiple batteries are attached, then the setpoint is split up by available charge/discharge power to equally stress the batteries. Field storage_power_setpoint_w is set to the desired battery power.
        - Policy peak-shaving-only: Enables peak shaving optimisation pn the battery. This must be combined with four peak-shaving parameters on site-level.
        - Policy cost: Enables day-ahead price (EPEX Spot market) cost optimization on the batteries, by charging it on the cheap hours and using the energy in the expensive hours. Field storage_power_setpoint_w is ignored.
        - Policy self-consumption Enables a simple self-consumption algorithm on the batteries. Excess solar production is stored to the battery during, and when the sun is down, energy is taken from the battery. Field storage_power_setpoint_w is ignored.
        - Policy off: Disables all interaction for all battery assets. Warning: limits are not being guarded in this mode. Field storage_power_setpoint_w is ignored.

- **heat_pump_policy**:
    - Toggles on/off heatpump systems. The minimum and maximum on times will always be respected.
        - Policy cost: Enables day-ahead price (EPEX Spot market) cost optimization on the heat pumps. The local dynamic pricing algorithm decides the best on-time periods
        - Policy self-consumption Turns on the heat pumps if an excess of solar energy is produced.
        - Policy power_off: Power off the heat pumps.
        - Policy power_on: Power on the heat pumps.

- **switched_load_policy**:
    - Toggles on/off relay-controlled systems. This could be the built-in relay or network-connected relays.
        - Policy cost: Enables day-ahead price (EPEX Spot market) cost optimization on the relay.
        - Policy self-consumption Turns on the relay if an excess of solar energy is produced.
        - Policy power_off
        - Policy power_on

- **variable_power_load_policy** and **variable_power_load_power_setpoint_w**:
    - Manages the electric vehicle power consumption policy and setpoint.
        - Policy setpoint: Set the total charge power for the group of EVs. Field variable_power_load_power_setpoint_w is set to the desired charge power.
        - Policy cost: Enables day-ahead price (EPEX Spot market) cost optimization on the batteries, by charging it on the cheap hours. Field variable_power_load_power_setpoint_w is ignored.
        - Policy self-consumption Enables charging if an excess of solar energy is produced. Field variable_power_load_power_setpoint_w is ignored.
        - Policy off: Disables all interaction for all EV assets. Field variable_power_load_power_setpoint_w is ignored.

#### Power Limits

Instead of setting control strategies and setpoint, power limits can also be set for storage and solar devices.

For example:

```json
{
    "extraTags": {
        "nodeId": "DEMO_CONTROLLER_SiteA"
    },
    "time": 1791547200,
    "fields": {
        "storage_policy": "limit",
        "storage_maxChargePower_W": 10000,
        "storage_maxDischargePower_W": 10000,
        "solar_policy": "limit",
        "solar_maxProductionPower_W": 15000
    }
}
```

The field prefix is `storage`, `solar` or the applicable device node ID. Include the corresponding `limit` policy when sending limits-only commands, as above. Command limit values are non-negative magnitudes: for example, `storage_maxDischargePower_W: 10000` means a discharge limit of 10 kW. This differs from feedback, where `max_discharge_power_W` is negative or zero.

#### Site Control

The site can be controlled seperately. The following site commands can be sent to the controller:

- `default` or `fallback`
        Remove any active site commands
- `export`
        Set the site export limit
- `import`
        Set the site import limit
- `setpoint`
        A site setpoint can vary up to 5% in both directions
- `setpoint_A`
        Not yet implemented

The following variables are peak-shaving parameters, and will only be applied when the battery strategy is set to peak-shaving.

- `startChargeBelow_W`
- `stopChargeAbove_W`
- `startDischargeAbove_W`
- `stopDischargeBelow_W`

A site setpoint is *NOT* compatible with an import/export limit.

For example:

```json
{
    "extraTags": {
        "nodeId": "DEMO_CONTROLLER_SiteA"
    },
    "time": 1791547200,
    "fields": {
        "storage_policy": "self-consumption",
        "site_policy": "limit",
        "site_export": 10000,
        "site_import": 25000
    }
}
```

#### Device Control

Specific devices can also be controlled, instead of groups of devices based on their types. The message is identically structured:

- **`nodeId`_policy** and **`nodeId`_power_setpoint_w**

> [!NOTE]
> When two commands are sent to the same asset (e.g. one device-specific command to a solar inverter, and a command to all solar devices), the **device-specific control** method will take preference over the device type control.

### Fallback behaviour
Omitting a group policy is not an immediate cancellation: a previously received group command can remain active until its original configured timeout. Use an explicit `fallback` command for the group or device when you want to relinquish remote control. Device-specific commands are not preserved by the same group-command cache; see the empty-command warning below.

If no command is being send at all, after 60 seconds (or configured timeout period), the default policies for assets will be reactivated.

### Cancel existing commands and falling back to local control modes
An active command can be cancelled by sending a **fallback command** message.

#### Fallback Command
A fallback command will **cancel** the existing command *immediately* and the <BrandName /> <ControllerName /> will take over control of the installation. The executed policy depends on what is set in the <BrandName /> <ControllerName /> Settings.

This can also be used in cases where a secondary control signal, such as a schedule, is used as a fallback.

Message examples:
```json
{
    "extraTags": {
        "nodeId": "DEMO_CONTROLLER_SiteA"
    },
    "time": 1791547200,
    "fields": {
        "storage_policy": "fallback"
    }
}
```

#### Empty Command
An empty command returns aggregate site feedback, but it is not a read-only status request. It replaces the latest received message and can remove earlier device-specific commands. Still-valid group policies may be reused until their original fallback timeout expires. Do not use this as polling while expecting device-specific control to remain unchanged.

The empty command is structured as follows:
```json
{
    "extraTags": {
        "nodeId": "DEMO_CONTROLLER_SiteA"
    },
    "time": 1791547200,
    "fields": {}
}
```

### Example payload
Below is an example of a payload to set various policies and setpoints:

```json
{
    "extraTags": {
        "nodeId": "DEMO_CONTROLLER_SiteA"
    },
    "time": 1714652046,
    "fields": {
        "solar_policy": "setpoint",
        "solar_power_setpoint_w": 5000,
        "storage_policy": "setpoint",
        "storage_power_setpoint_w": -5000
    }
}
```

In this example, solar production is limited to 5000 watts and the negative storage setpoint requests 5000 watts of discharge. A positive storage setpoint would request charging. Omitting a group policy does not necessarily cancel its earlier command; use an explicit `fallback` policy when you want to return that group to local control.


## MQTT Documentation for Receiving feedback

### MQTT Feedback Topic

Subscribe to the feedback topic to read the site's state and the result of a processed command:

```text
standard1/outbound/remoteControlMetrics/feedback/<Controller SN>
```

Replace `<Controller SN>` with the controller serial number. The serial number in the topic and the site's `siteNodeId` are different identifiers: always use the actual site node ID, which does not necessarily end in `_site_0`.

### When feedback is sent

The standard live-control connection returns a state snapshot when it accepts a command and triggers control processing. This is not a confirmation that the physical device has already reached the new setpoint.

An empty command with `"fields": {}` also returns aggregate state, but it is **not side-effect-free polling**: it replaces the latest message and can remove previously targeted device-specific commands. Earlier group policies can remain active only within their original fallback timeout. Do not use empty commands to poll while expecting device-specific control to remain unchanged.

Some provider-specific MQTT connections also publish unsolicited feedback approximately every 30 seconds. This periodic publishing is connection-specific, not a guaranteed interval for every MQTT integration. Periodic snapshots and replies to empty commands do not include individual-device state.

### Machine-readable feedback specification

Use the JSON Schema to validate feedback payloads, or the AsyncAPI document to describe the controller's feedback channel. Both describe **feedback**, not the complete command interface or provider-specific extensions.

<DownloadButton file="/docs/eniris/mqtt-feedback.schema.json" label="Download feedback JSON Schema" />

<DownloadButton file="/docs/eniris/mqtt-feedback.asyncapi.json" label="Download feedback AsyncAPI" />

<span id="mqtt-feedback-payload-structure"></span>
<span id="fields-description-1"></span>

### Message envelope

| Field | Type | Meaning |
| --- | --- | --- |
| `time` | Integer | Feedback timestamp, in Unix seconds. |
| `requestTime` | Integer | Timestamp copied from the command's integer `time` value. It is `0` when that value is absent or not an integer. Periodic integrations can use the snapshot timestamp here, so do not assume an unsolicited snapshot has a matching command. |
| `siteNodeId` | String | Actual node ID of the site sending feedback. Do not construct it from the serial number. |
| `fields` | Object | Empty object in feedback messages. |
| `data.responseCode` | Integer | `0` for a successfully constructed feedback response; `1` for a processing error. The spelling and capitalization are significant. |
| `data.state` | Object | State grouped by asset type. Present on success, absent on error. |
| `data.errors` | String | Error/status text returned with successful feedback; `""` when there is none. This is not an object or array. |
| `data.error` | String | Error text returned with `responseCode: 1`, instead of `state` and `errors`. |

`responseCode: 0` does not prove that every device reached its requested setpoint. Read measured power, executed setpoints, constraint labels and device error codes as well.

#### Successful response

This illustrative snapshot uses fictional identifiers and a deliberately small selection of measurements. Other available fields are described below.

```json
{
  "time": 1791547201,
  "requestTime": 1791547200,
  "siteNodeId": "DEMO_CONTROLLER_SiteA",
  "fields": {},
  "data": {
    "responseCode": 0,
    "errors": "",
    "state": {
      "load": { "load_power_W": 12000 },
      "grid": { "active_power_W": 7000, "import_limit_W": 25000 },
      "storage": {
        "active_power_W": -5000,
        "mean_soc_perc": 60,
        "max_charge_power_W": 10000,
        "max_discharge_power_W": -10000,
        "dynamic_max_charge_power_W": 8000,
        "dynamic_max_discharge_power_W": -9000,
        "executed_power_W": -5000,
        "executed_policy": ["setpoint"],
        "errorCodes": {},
        "nr_devices": 1
      }
    }
  }
}
```

#### Error response

On a processing error, do not try to read `data.state`:

```json
{
  "time": 1791547201,
  "requestTime": 1791547200,
  "siteNodeId": "DEMO_CONTROLLER_SiteA",
  "fields": {},
  "data": {
    "responseCode": 1,
    "error": "Command could not be processed"
  }
}
```

### Reading aggregate state

The section names are `grid`, `load`, `storage`, `solar`, `heat_pump`, `switched_load` and `variable_power_load`. Each asset section combines devices of that type. For example, two solar devices with a capacity of 3 kW each give an aggregate capacity of 6 kW.

`solar` and `storage` can be empty objects (`{}`) when there are no matching devices. The heat-pump, switched-load and variable-power-load sections retain zero counts, empty arrays/maps and applicable nullable power values in that situation.

Treat a missing field or `null` as **unavailable**, not as zero. Many measurements are omitted when unknown; some fields explicitly contain `null`. A total can contain only the devices for which a value is available. Do not infer complete measurement coverage from `nr_devices` alone.

The following common fields apply to `storage`, `solar`, `heat_pump`, `switched_load` and `variable_power_load`:

| Field | Aggregate type | Meaning |
| --- | --- | --- |
| `executed_policy` | Array of strings and/or `null` entries | Distinct policies reported by the devices. The array can contain `null` for an unknown policy; its order does not identify devices. |
| `constraint_ph0_label` | Array of strings, optional | One label per device that reports a constraint. Labels can repeat. The key is omitted if no device reports one. Use individual-device feedback to attribute a label. |
| `errorCodes` | Object | Maps node IDs to arrays of device error/status entries: `{ "DEMO_BATTERY_1": [...] }`. It is `{}` when no such entries are reported. |
| `nr_devices` | Integer | Number of devices represented by this section, not the number with valid measurements. |
| `individual_devices` | Object, conditional | Per-device feedback, keyed by node ID; see [Individual-device feedback](#individual-device-feedback). |

#### Grid

Every measurement or limit in `state.grid` is optional and is omitted when unknown. Values are numbers; power is in watts, energy in watt-hours and current in amperes.

| Field | Meaning |
| --- | --- |
| `active_power_W` | Grid active power. Positive means import; negative means export. |
| `import_limit_W` | Present grid import limit. |
| `export_limit_W` | Present grid export limit. |
| `nominal_current_A` | Nominal current configured for the site's electrical protection. |
| `today_imported_energy_Wh` | Energy imported today, when available. |
| `today_exported_energy_Wh` | Energy exported today, when available. |
| `total_imported_energy_Wh` | Cumulative imported energy. |
| `total_exported_energy_Wh` | Cumulative exported energy. |
| `today_produced_energy_Wh` | Production energy today, for a meter/site that provides production readings. |
| `total_produced_energy_Wh` | Cumulative production energy, when provided. |

#### Site load

`state.load.load_power_W` is a number or `null`. It reports other site consumption, excluding separately accounted EV charging and heat-pump consumption. It is not total site consumption or another name for grid power.

#### Storage

| Field | Type / availability | Meaning |
| --- | --- | --- |
| `energy_capacity_Wh` | Number, optional | Combined available battery capacity metadata. |
| `energy_stored_Wh` | Number, optional | Current stored energy. |
| `mean_soc_perc` | Number, optional | Capacity-weighted state of charge in percent. A 10 kWh battery at 20% and a 20 kWh battery at 50% give 40%. |
| `mean_min_soc_perc` | Number, optional | Capacity-weighted minimum state-of-charge limit in percent. |
| `mean_max_soc_perc` | Number, optional | Capacity-weighted maximum state-of-charge limit in percent. |
| `active_power_W` | Number, optional | Measured battery power: positive for charging, negative for discharging. |
| `max_charge_power_W` | Number | Combined static charge limit, positive or zero. |
| `max_discharge_power_W` | Number | Combined static discharge limit, **negative or zero**. For example, `-53000` represents up to 53 kW of discharge. |
| `dynamic_max_charge_power_W` | Number | Estimated present charge capability, positive or zero, accounting for available device limits and state-of-charge headroom. |
| `dynamic_max_discharge_power_W` | Number | Estimated present discharge capability, **negative or zero**, accounting for available device limits and state-of-charge headroom. |
| `executed_power_W` | Number, optional | Combined power setpoint sent to the battery devices, rather than measured power. |
| `today_charged_Wh` | Number, optional | Energy charged into the batteries today. |
| `today_discharged_Wh` | Number, optional | Energy discharged from the batteries today. |
| `total_charged_Wh` | Number, optional | Cumulative energy charged. |
| `total_discharged_Wh` | Number, optional | Cumulative energy discharged. |

Use `dynamic_max_charge_power_W` and `dynamic_max_discharge_power_W` for the current feedback format. They replace the former `realised_charge_power_W` and `realised_discharge_power_W` fields. Dynamic capability is an estimate, not a guarantee that every requested setpoint can be executed; site and device constraints still apply.

#### Solar

These numeric fields are omitted when unavailable:

| Field | Meaning |
| --- | --- |
| `active_power_W` | Measured solar-device power. |
| `capacity_W` | Combined nominal solar capacity. |
| `executed_power_W` | Combined power setpoint sent to the solar devices. |
| `today_energy_Wh` | Energy produced today. |
| `total_energy_Wh` | Cumulative energy produced. |

#### Heat pumps

| Field | Type | Meaning |
| --- | --- | --- |
| `active_power_W` | Number or `null` | Combined measured heat-pump power; `null` when unavailable. |
| `executed_power_W` | Number or `null` | Combined expected/requested heat-pump power; `null` when unavailable. |
| `operation_modes` | Array of modes or `null` entries | Distinct reported operating modes, such as blocking, boosting or self-control. Can contain `null` when a mode is unknown. |

#### Switched loads

| Field | Type / availability | Meaning |
| --- | --- | --- |
| `active_power_W` | Number, optional | Combined measured switched-load power. |
| `devices_on` | Integer | Number of devices reporting an on state. |
| `devices_off` | Integer | Number counted as off; an unknown on/off state is counted as off. |
| `executed_power_W` | Number, optional | Combined expected/requested switched-load power. |

#### EV chargers and variable-power loads

The section is named `variable_power_load`, not `variable_load`.

| Field | Type / availability | Meaning |
| --- | --- | --- |
| `active_power_W` | Number, optional | Combined EV/variable-load power, **not grid power**. |
| `ev_charging` | Integer | Devices reporting that an EV **requires charge**. This does not mean that current is actually flowing. |
| `ev_not_charging` | Integer | Devices not reporting a need to charge, including chargers without a connected vehicle. |
| `executed_power_W` | Number or `null` | Combined power setpoint; `null` when unavailable. |
| `currentL1_A`, `currentL2_A`, `currentL3_A` | Number, optional | Combined measured current on each phase. Each phase field can be omitted independently. |
| `executed_current_A` | Number, optional | Combined requested current. |

Charging energy counters, current limits, pause support and charging sessions belong to **individual devices**, not this aggregate section.

### Individual-device feedback

To include a device's state, the command must contain its `<nodeId>_policy` field and target a recognized device. A device-specific setpoint on its own does not request individual-device feedback. Neither an empty command nor a periodic snapshot includes it.

The location is:

```text
data.state.<section>.individual_devices.<nodeId>
```

For example, a command containing both `"DEMO_BATTERY_1_policy": "setpoint"` and `"DEMO_BATTERY_1_power_setpoint_w": -5000` can produce this fragment at `data.state.storage`:

```json
{
  "executed_policy": ["setpoint"],
  "errorCodes": {},
  "nr_devices": 1,
  "individual_devices": {
    "DEMO_BATTERY_1": {
      "active_power_W": -5000,
      "executed_power_W": -5000,
      "executed_policy": "setpoint",
      "constraint_ph0_label": null,
      "nr_devices": 1
    }
  }
}
```

Per-device policy, mode and constraint fields are **single values**, not aggregate lists. Unknown measurements can be `null`. The device's `errorCodes` is an array of error/status entries and is included only when that device reports entries; it is not another node-ID map.

| Device type | Fields available in its individual state |
| --- | --- |
| Solar | `active_power_W`, `today_energy_Wh`, `total_energy_Wh`, `capacity_W`, `executed_power_W`, `executed_policy`, `constraint_ph0_label`, `nr_devices`. |
| Storage | `energy_capacity_Wh`, `mean_soc_perc`, `energy_stored_Wh`, `max_charge_power_W`, `max_discharge_power_W`, `dynamic_max_charge_power_W`, `dynamic_max_discharge_power_W`, `mean_min_soc_perc`, `mean_max_soc_perc`, `active_power_W`, `executed_power_W`, `executed_policy`, `constraint_ph0_label`, `today_charged_Wh`, `today_discharged_Wh`, `total_charged_Wh`, `total_discharged_Wh`, `nr_devices`. |
| Heat pump | `active_power_W`, `operation_modes`, `executed_power_W`, `executed_policy`, `constraint_ph0_label`, `nr_devices`. Despite its plural name, `operation_modes` is a single mode here. |
| Switched load | `active_power_W`, `devices_on`, `devices_off`, `executed_power_W`, `executed_policy`, `constraint_ph0_label`, `nr_devices`. The on/off counts are `0` or `1`. |
| EV / variable-power load | `active_power_W`, `ev_requiring_charge`, `executed_power_W`, `today_charged_Wh`, `today_discharged_Wh`, `total_charged_Wh`, `total_discharged_Wh`, `currentL1_A`, `currentL2_A`, `currentL3_A`, `executed_current_A`, `executed_policy`, `min_charge_current_A`, `max_charge_current_A`, `allow_zero_current`, `current_charging_session`, `previous_charging_session`, `constraint_ph0_label`, `nr_devices`. |
| Site, where exposed by the connection | The available fields from the grid reference above, under `state.site.individual_devices`. Power-meter feedback uses the same field definitions where an integration exposes it; the ordinary live-control connection does not provide general direct addressing of power meters. |

> [!IMPORTANT]
> In the current per-device battery response, `mean_soc_perc` contains a **fraction** despite its name: `0.6` means 60%. The aggregate `storage.mean_soc_perc` contains a percentage: `60` means 60%. The per-device minimum and maximum SoC fields remain percentages. Do not apply the same conversion to both levels.

#### EV-only individual fields

| Field | Type | Meaning |
| --- | --- | --- |
| `ev_requiring_charge` | Boolean | Whether this device reports an EV that requires charge. |
| `today_charged_Wh`, `total_charged_Wh` | Number or `null` | Energy charged into the vehicle today / cumulatively. |
| `today_discharged_Wh`, `total_discharged_Wh` | Number or `null` | Energy discharged from the vehicle today / cumulatively, when supported. |
| `min_charge_current_A`, `max_charge_current_A` | Number or `null` | Configured minimum and maximum charging current. |
| `allow_zero_current` | Boolean or `null` | Whether pausing with zero charging current is allowed; `null` if unknown. |
| `current_charging_session` | Object | Current session, or `{}` when unavailable. The key is singular. |
| `previous_charging_session` | Object | Previous session, or `{}` when unavailable. |

A populated charging-session object contains:

| Field | Type | Meaning |
| --- | --- | --- |
| `pluginTime` | String | Plug-in time as an ISO 8601 date-time. |
| `endTime` | String or `null` | Session end time, if known. |
| `firstChargingStartTime` | String or `null` | First charging start time, if known. |
| `isFull` | Boolean | Whether the session reports the vehicle as full. |
| `chargedEnergy_Ws` | Number | Energy charged during this session in **watt-seconds**. Divide by 3600 for watt-hours. |
| `usedPhases` | Array of strings or `null` | Phases used during charging, if known. |
| `historicMaxChargeCurrent_A` | Number | Highest charging current recorded during the session. |

### Separate VPP connections

`vpp_id` belongs to a separately configured VPP connection. Do not add it to ordinary live MQTT configuration or commands; the standard feedback state does not require it. Provider-specific additions must not be treated as part of the general live-control interface.


### Storage Constraint Labels

The setpoints sent by an external signal can be internally limited by the EMS. The table below gives an overview of possible constraints for the `constraint_ph0_label` feedback field.

| Label                                            | Node Types        | Description                                                                                |
|--------------------------------------------------|-------------------|--------------------------------------------------------------------------------------------|
| `breaker_current`                                | Site              | Site level breaker current                                                                 |
| `max_charge_current` (EV)                        | EV                | Maximum charge current limit.                                                              |
| `min_charge_current`                             | EV                | Minimum charge current limit.                                                              |
| `nom_current`                                    | EV                | Device nominal current limit.                                                              |
| `max_export_power`                               | Site              | Site export limit                                                                          |
| `max_import_power`                               | Site              | Site import limit                                                                          |
| `max_charge_power`                               | EV, Storage       | Maximum charge power limit.                                                                |
| `max_discharge_power`                            | Storage           | Maximum discharge power limit.                                                             |
| `nom_charge_power`                               | EV, Storage       | Nominal charge power limit.                                                                |
| `nom_discharge_power`                            | Storage           | Nominal discharge power limit.                                                             |
| `nom_production_power`                           | PV                | Nominal production power limit.                                                            |
| `device_reported_max_charge_power`               | Storage           | Device maximum charge power limit.                                                         |
| `device_reported_max_charge_current`             | Storage           | Device maximum charge current limit.                                                      |
| `device_reported_max_discharge_power`            | Storage           | Device maximum discharge power limit.                                                     |
| `device_reported_max_discharge_current`          | Storage           | Device maximum charge current limit.                                                      |
| `ev_charging_suspended`                          | EV                | EV Charging is paused                                                                      |
| `setpoint_power`                                 | All               | The setpoint is the limiting factor - no internal constraints.                            |
| `high_soc_limit_charge_power`                    | Storage           | Charging is limited by the high battery SOC.                                              |
| `low_soc_limit_discharge_power`                  | Storage           | Discharging is limited by the low battery SOC.                                            |
| `soc_power_curve_max_charge_power`               | Storage           | Charging is limited by the SOC power curve.                                               |
| `soc_power_curve_max_discharge_power`            | Storage           | Discharging is limited by the SOC power curve.                                            |
| `too_low_soc_force_charge_power`                 | Storage           | Minimum charging power due to a too low SOC.                                              |
| `peakshaving_charge_threshold`                   | Storage           | Charge due to peak-shaving-parameters.                                                     |
| `peakshaving_discharge_threshold`                | Storage           | Discharge due to peak-shaving-parameters.                                                  |
| `self_consumption_charge_power`                  | EV, Storage       | Charge due to the self-consumption strategy.                                              |
| `self_consumption_discharge_power`               | EV, Storage       | Discharge due to the self-consumption strategy.                                           |
| `self_consumption_load_power`                    | Switched Load     | Consume due to the self-consumption strategy.                                             |
| `external_signal_device_power_consumption_limit` | EV, Switched Load | External signal limits the device consumption.                                            |
| `external_signal_device_power_production_limit`  | PV                | External signal limits the device production.                                             |
| `external_signal_battery_charge_power_limit`     | Storage           | External signal limits the battery charging power.                                        |
| `external_signal_battery_discharge_power_limit`  | Storage           | External signal limits the battery discharging power.                                     |
| `setpoint_current`                               | EV                | Current Setpoint limit.                                                                    |
| `observed_max_current_demand`                    | EV                | Observed max current used by EV.                                                          |
| `near_fully_charged`                             | EV                | Current limited by a nearly full EV.                                                      |
| `fully_charged`                                  | EV                | The EV is fully charged                                                                    |
| `dynamic_derated_min_power`                      | Storage           | Setpoint is limited due to the device not being able to reach the expected setpoint power. |
| `dynamic_derated_max_power`                      | Storage           | Setpoint is limited due to the device not being able to reach the expected setpoint power. |


### MQTT Error Codes

Error codes are grouped into ranges that indicate the general category of the problem:

| Range  | Category                                                                    |
|--------|-----------------------------------------------------------------------------|
| `-200`  | **Connection errors**                                                      |
| `-300`  | **Response errors**                                                        |
| `-500`  | **Driver errors**                                                          |
| `-600`  | **Control errors**                                                         |

The individual error codes are listed below.

#### Connection errors (200)

Connection issues between the EMS and the device.

| Code   | Label                | Additional Fields |
|--------|----------------------|-------------------|
| `-204` | Connection Refused   |                   |
| `-209` | No Route To Host     |                   |
| `-210` | No IP For MAC Address |                  |

#### Response errors (300)

The device is connected, but its responses are invalid.

| Code   | Label                    | Additional Fields |
|--------|--------------------------|-------------------|
| `-300` | Device Unavailable Error |                   |
| `-310` | No Response Error         |                  |
| `-402` | Device Status Error      | `Message`         |

#### Control errors (600)

| Code   | Label                  | Additional Fields |
|--------|------------------------|-------------------|
| `-600` | Setpoint Ignored Error |                   |
| `-602` | Setpoint Rejected Error |                  |

#### Measurement & setpoint errors (1000)

| Code    | Label                 | Additional Fields                                |
|---------|-----------------------|--------------------------------------------------|
| `-1000` | No Measurements       |                                                  |
| `-1001` | No Power Measurements |                                                  |
| `-1003` | No Power Setpoint     |                                                  |
| `-1005` | Setpoints Not Followed | `nomPowerDeviation_frac`, `setpointDeviation_frac` |
| `-1006` | Limits Not Followed   |                                                  |

## Supported MQTT Versions and Behavior on Unauthorized Topics
When using MQTT, it is important to consider the differences in specifications between versions 3.1, 3.1.1, and 5.0, particularly regarding the broker’s behavior when clients publish to unauthorized topics.

According to the MQTT 3.1.1 specification (see OASIS MQTT 3.1.1 Specification, section MQTT-3.3.5-2), a broker must terminate the connection as soon as a client sends a PUBLISH to a topic for which it does not have permission. This behavior can lead to unexpected disconnections for clients attempting to publish to misconfigured or unauthorized topics.

In MQTT 3.1, this requirement is not present. When a client publishes to an unauthorized topic under this version, the broker typically ignores the message (silent drop) without terminating the connection. This makes MQTT 3.1 in some cases more suitable when robustness against configuration errors or temporarily missing permissions is more important than strict security enforcement.

Although MQTT 5.0 introduces the ability to work with reason codes (such as PUBACK with a refusal reason), this requires support on both the client and server sides. Migrating to MQTT 5.0 therefore involves additional implementation effort.

__Consequences of Ignoring Compatibility:__
If a client connects using MQTT 3.1.1 and attempts to publish messages to unauthorized topics, the broker will abruptly terminate the session. This may lead to instability, loss of connectivity, or increased load due to repeated reconnect attempts.

__Recommended Approach:__
For systems where clients may (temporarily) attempt to publish to unauthorized topics, or where error handling is not strictly implemented, we recommend using MQTT 3.1. This ensures more stable connections and avoids unintended disconnects during runtime.


# Scheduled MQTT control


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';
import DownloadButton from '@site/src/components/DownloadButton';

# Scheduled MQTT Control

> [!TIP]
> The Scheduled MQTT control is meant for scheduled messages ahead of time. For live control, see [Live MQTT Control](/Controller/External%20Signals/MQTT/eniris-mqtt/) instead.

This guide will help you configure MQTT on your <BrandName /> <ControllerName /> to remotely control and monitor battery and solar panel installations.

This guide will help you configure MQTT on your <BrandName /> <ControllerName /> to remotely control and monitor battery and solar panel installations.

## First-time Configuration (Starting point for new users)
I have a <BrandName /> <ControllerName /> that I'd like to setup for MQTT Remote Control.

Before continuing, make sure your network and devices are ready by following the [MQTT Setup](/Controller/External%20Signals/MQTT/setup/) guide.

Request the required Eniris MQTT username and password through the [Eniris webshop](https://webshop.eniris.com/) before starting the configuration.

### 1. Add the MQTT external signal
<ClickableImage src="/img/generic/add-external-datasources-en.png" alt="Image 1" maxWidth="650px" />
<ClickableImage src="/img/generic/add-external-datasources-kind-en.png" alt="Image 1" maxWidth="650px" />
<ClickableImage src="/img/generic/add-external-datasources-brand-en.png" alt="Image 1" maxWidth="650px" />

### 2. Enable MQTT remote signal
Select all devices that you'd wish to include in MQTT Remote Control.

<ClickableImage src="/img/generic/add-external-datasources-devices-en.png" alt="Image 1" maxWidth="650px" />

### 3. Remote signal is added
The MQTT Remote Control interface has now been activated on the <BrandName /> <ControllerName />.

We are now ready to send some basics commands using a simple example. The Status column tells you if any command is active.

## Python demo script
A good first starting point would be to test your newly setup integration with a simple example.

This test code does a simple job of continuously sending the following schedule:
- Battery: Charge at 5 kW for 15 minutes in 10 minutes
- Solar: Set power to 0 kW for an hour in 30 minutes

The <BrandName /> <ControllerName /> responds with an acknowledgement message containing the unique schedule identifier, or an error message.

We then fetch the next schedule for both device types, confirming that the command was successful. 

Please download the file below in your preferred Python IDE. Fill in your serial number and the MQTT credentials requested through the [Eniris webshop](https://webshop.eniris.com/), then execute the script:
<DownloadButton file="/docs/eniris/mqtt_schedule_demo_10-04-25.zip" label="Download Tutorial Files" />

When the above is successful, you can continue with sending other type of messages. All messages are described below.

## MQTT Documentation for Sending Commands
This section details the MQTT messaging format and payload requirements for setting up scheduled control of devices within the <BrandName /> <ControllerName />'s network.

### MQTT Topics
- Subscribe Topic: `standard1/rp_one_s/remoteScheduleMetrics/<controller SN>`
- Feedback Topic: `standard1/outbound/remoteScheduleMetrics/feedback/<controller SN>`

Where `<controller SN>` should be replaced with the actual serial number of the <BrandName /> <ControllerName /> you intend to control.

### MQTT Message Types

#### 1. Set Schedule (`set_schedule`)
Creates a new schedule for a device type.

```json
{
    "extraTags": {
        "nodeId": "<Controller SN>_site_0"
    },
    "time": <Unix Timestamp>,
    "message_type": "set_schedule",
    "fields": {
        "device_type": "<Device Type>",
        "node_id": "<Node ID>" (Optional),
        "start_time": <Unix Timestamp>,
        "end_time": <Unix Timestamp>,
        "policy": "<Policy>",
        "power_setpoint_w": <Setpoint in watts>,
        "site_import": <Site Import in Watts>,
        "site_export": <Site Export in Watts>,
        "remove_overlap": <True/False> (Optional) (default=False),
        "tag": <Tag String> (Optional) (default=None),
    }
}
```

Response (Success):
```json
{
    "requestTime": <Unix Timestamp>,
    "time": <Unix Timestamp>,
    "siteNodeId": "<Controller SN>_site_0",
    "data": {
        "message_type": "set_schedule_ack",
        "state": {
            "schedule_id": <Schedule ID>,
            "deleted_ids": <Schedulde IDs deleted if remove_overlap=True>
            "tag": <Tag String> (default=None),
        },
        "responseCode": 0
    }
}
```

#### 2. Set Schedules (`set_schedules`)
Creates multiple new schedules.

```json
{
    "extraTags": {
        "nodeId": "<Controller SN>_site_0"
    },
    "time": <Unix Timestamp>,
    "message_type": "set_schedules",
    "fields": 
        "0": "{
            "device_type": "<Device Type>",
            "node_id": "<Node ID>" (Optional),
            "start_time": <Unix Timestamp>,
            "end_time": <Unix Timestamp>,
            "policy": "<Policy>",
            "power_setpoint_w": <Setpoint in watts>,
            "site_import": <Site Import in Watts>,
            "site_export": <Site Export in Watts>,
            "remove_overlap": <True/False> (Optional) (default=False),
        }",
        "1": "{
            "device_type": "<Device Type>",
            "node_id": "<Node ID>" (Optional),
            "start_time": <Unix Timestamp>,
            "end_time": <Unix Timestamp>,
            "policy": "<Policy>",
            "power_setpoint_w": <Setpoint in watts>,
            "site_import": <Site Import in Watts>,
            "site_export": <Site Export in Watts>,
            "remove_overlap": <True/False> (Optional) (default=False),
        }",
        ...
}
```

Response (Success):
```json
{
    "requestTime": <Unix Timestamp>,
    "time": <Unix Timestamp>,
    "siteNodeId": "<Controller SN>_site_0",
    "data": {
        "message_type": "set_schedules_ack",
        "state": {
            "schedule_ids": <Schedule IDs>,
            "deleted_ids": <Schedulde IDs deleted if remove_overlap=True>
        },
        "responseCode": 0
    }
}
```

#### 3. Get Schedule (`get_schedule`)
Retrieves a specific schedule by ID.

```json
{
    "extraTags": {
        "nodeId": "<Controller SN>_site_0"
    },
    "time": <Unix Timestamp>,
    "message_type": "get_schedule",
    "fields": {
        "id": <Schedule ID>
    }
}
```

Response:
```json
{
    "requestTime": <Unix Timestamp>,
    "time": <Unix Timestamp>,
    "siteNodeId": "<Controller SN>_site_0",
    "data": {
        "message_type": "get_schedule_ack",
        "state": <Schedule>,
        "responseCode": 0
    }
}
```

#### 4. Get Active Schedule (`get_active_schedule`)
Retrieves the currently active schedule for a device type.

```json
{
    "extraTags": {
        "nodeId": "<Controller SN>_site_0"
    },
    "time": <Unix Timestamp>,
    "message_type": "get_active_schedule",
    "fields": {
        "device_type": "<Device Type>",
        "node_id": "<Node ID>" (Optional),
    }
}
```

Response (Success):
```json
{
    "requestTime": <Unix Timestamp>,
    "time": <Unix Timestamp>,
    "siteNodeId": "<Controller SN>_site_0",
    "data": {
        "message_type": "get_active_schedule_ack",
        "state": <Schedule>,
        "responseCode": 0
    }
}
```

#### 5. Get Next Schedule (`get_next_schedule`)
Retrieves the next upcoming schedule for a device type.

```json
{
    "extraTags": {
        "nodeId": "<Controller SN>_site_0"
    },
    "time": <Unix Timestamp>,
    "message_type": "get_next_schedule", 
    "fields": {
        "device_type": "<Device Type>",
        "node_id": "<Node ID>" (Optional),
    }
}
```

Response (Success):
```json
{
    "requestTime": <Unix Timestamp>,
    "time": <Unix Timestamp>,
    "siteNodeId": "<Controller SN>_site_0",
    "data": {
        "message_type": "get_next_schedule_ack",
        "state": <Schedule>,
        "responseCode": 0
    }
}
```

#### 6. Get Schedules (`get_schedules`)
Retrieves all schedules for a specific date.

```json
{
    "extraTags": {
        "nodeId": "<Controller SN>_site_0"
    },
    "time": <Unix Timestamp>,
    "message_type": "get_schedules",
    "fields": {
        "date": "<Date String of Format dd/mm/yyyy>"
    }
}
```

Response (Success):
```json
{
    "requestTime": <Unix Timestamp>,
    "time": <Unix Timestamp>,
    "siteNodeId": "<Controller SN>_site_0",
    "data": {
        "message_type": "get_schedules_ack",
        "state": {
            "schedules": [<Schedule>, ...]
        },
        "responseCode": 0
    }
}
```

#### 7. Get Future Schedules (`get_future_schedules`)
Retrieves all future schedules.

```json
{
    "extraTags": {
        "nodeId": "<Controller SN>_site_0"
    },
    "time": <Unix Timestamp>,
    "message_type": "get_future_schedules",
    "fields": {}
}
```

Response (Success):
```json
{
    "requestTime": <Unix Timestamp>,
    "time": <Unix Timestamp>,
    "siteNodeId": "<Controller SN>_site_0",
    "data": {
        "message_type": "get_future_schedules_ack",
        "state": {
            "schedules": [<Schedule>, ...]
        },
        "responseCode": 0
    }
}
```

#### 8. Remove Schedule (`remove_schedule`)
Removes a specific schedule by ID.

```json
{
    "extraTags": {
        "nodeId": "<Controller SN>_site_0"
    },
    "time": <Unix Timestamp>,
    "message_type": "remove_schedule",
    "fields": {
        "id": <Schedule ID>
    }
}
```

Response (Success):
```json
{
    "requestTime": <Unix Timestamp>,
    "time": <Unix Timestamp>,
    "siteNodeId": "<Controller SN>_site_0",
    "data": {
        "message_type": "remove_schedule_ack",
        "state": "Schedule <Schedule ID> removed successfully",
        "responseCode": 0
    }
}
```

#### 9. Get Site Feedback (`get_feedback`)
Retrieves detailed feedback on the state of the system.

```json
{
    "extraTags": {
        "nodeId": "<Controller SN>_site_0"
    },
    "time": <Unix Timestamp>,
    "message_type": "get_feedback",
    "fields": {
        "device": <Device (node) level>
    }
}
```

Response (Success): 

[Feedback Payload Structure](/Controller/External%20Signals/MQTT/eniris-mqtt/#mqtt-feedback-payload-structure)

#### 10. Site Topology (`get_toplogy`)
Gets the topology of the site.

```json
{
    "extraTags": {
        "nodeId": "<Controller SN>_site_0"
    },
    "time": <Unix Timestamp>,
    "message_type": "get_topology",
    "fields": {}
}
```

Response (Success):
```json
{
    "requestTime": <Unix Timestamp>,
    "time": <Unix Timestamp>,
    "siteNodeId": "<Controller SN>_site_0",
    "data": {
        "message_type": "get_topology_ack",
        "state": {
            "nodeId": <nodeId>,
            "isControllable": <boolean>,
            "nodeType": <nodeType>,
            "nomCurrent": <nominalCurrent>
            "children": [{<ChildObject>}]
            },
        "responseCode": 0
    }
}
```

#### Standard Schedule Response Format

```json
{
    "id": <Schedule ID>,
    "device_type": "<Device Type>",
    "node_id": "<Node ID>" (Optional),
    "start_time": <Unix Timestamp>,
    "end_time": <Unix Timestamp>,
    "policy": "<Schedule Policy>",
    "power_setpoint_w": <Setpoint in watts>,
    "created_at": <Unix Timestamp>
}
```

### Component Types and Policies
For details about available components and policies that can be scheduled, refer to the [MQTT Components and Policies](/Controller/External%20Signals/MQTT/eniris-mqtt/#components-and-policies) section in the Live MQTT Control documentation.

Device-specific schedules can be sent using the optional `node_id` field, referring to the node ID of the controllable device.

### Error Handling
All messages can return an error response with `responseCode: 1` when an error occurs:

```json
{
    "requestTime": <Unix Timestamp>,
    "time": <Unix Timestamp>,
    "siteNodeId": "<Controller SN>_site_0",
    "data": {
        "message_type": "<Message Type>_ack",
        "error": <Error Body>,
        "responseCode": 1
    }
}
```

When an unrelated error occurs, the message type will be (`general_error`).

Common errors include:
- Schedule overlap with existing schedules
- Invalid time range
- Device type not found
- Schedule ID not found
- Invalid policy for device type

### Schedule Management Rules
1. Overlap Rules
    - Schedules cannot overlap for the same device type
    - Schedules cannot overlap for the same device 
    - Schedules for the same device and device type cannot overlap
    - Existing, overlapping schedules will be deleted if the `remove_overlap` variable is set to `True` when creating a new schedule.
2. Each schedule must have:
   - A valid device type
   - A start time (Unix timestamp)
   - An end time (Unix timestamp)
   - A policy (matching the device type's available policies)
   - A power setpoint (for policies that require it)
3. Start time must be before end time
4. If the start time is in the past, it is automatically changed to start now
5. Schedules can only be deleted if they have not started yet. **Active schedules cannot be deleted.**
6. Schedules can be set for different device types independently
7. The system automatically applies the appropriate policy when a schedule becomes active


# FCR


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';
import YouTubeEmbed from '@site/src/components/YouTubeEmbed';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';
import CountriesSupportTable from '@site/src/components/CountriesSupportTable';
import Details from '@theme/Details';

# FCR

This guide will help you configure FCR on your <BrandName /> <ControllerName /> to remotely control and monitor battery installations.

Before continuing, make sure your network and devices are ready by following the [MQTT Setup](/Controller/External%20Signals/MQTT/setup/) guide.

Request the Eniris MQTT credentials used for FCR communication through the [Eniris webshop](https://webshop.eniris.com/). Certification and project approval are separate from credential provisioning.

## Overview
> [!CAUTION] NOTE:
> FCR overrides the original functionality of the controller.
>

## Supported Devices

<DeviceSupportTable
  devices={[
    {
        type: 'Solar Inverters',
        variants: 'All',
        customCol: '❌'
    },
    {
        type: 'Storage Devices',
        variants: 'All',
        customCol: '✅'
    },
    {
        type: 'EV Chargers',
        variants: 'All',
        customCol: '❌'
    }
  ]}
    showVariants={true}
    customColumns={{ "customCol": "Supported" }}
/>

## Supported Countries

<CountriesSupportTable
  countries={[
    {
        country: 'Belgium',
        customCol: '❌'
    },
    {
        country: 'Netherlands',
        customCol: '❌'
    },
    {
        country: 'Switzerland',
        customCol: '✅'
    },
  ]}
    showVariants={true}
    customColumns={{ "customCol": "Supported" }}
/>

## Prerequisites

> [!NOTE]
> Only specific installations can be set up via FCR. Please verify that the installation is certified.

### 1. Add the devices
[Login to the commissioning interface](/Controller/Configuration%20from%20A%20to%20Z/2-accessing-commissioning-interface/) and make sure the [devices are added](/Controller/Configuration%20from%20A%20to%20Z/6-other-devices/) to the <BrandName /> <ControllerName />.

### 2. Check the grid power limits
In the settings, the grid power limits should be set correctly. Click Settings and check the highlighted setting in the image.
If necessary, adjust the settings.

### 3. Check the address
Make sure [the address is set correctly](/Controller/Configuration%20from%20A%20to%20Z/4-location/).

> [!WARNING]
> The integration may not work correctly if the address is not correct!

## Enabling FCR

From the commissioning interface, go to the 'External Signals' tab.
<ClickableImage src="/img/generic/add-external-datasources-en.png" alt="Image 1" maxWidth="650px" />

Click on 'Energy Markets'.
<ClickableImage src="/img/controller/external signals/types.png" alt="Image 1" maxWidth="650px" />

Select Eniris, select FCR and click 'Next'.

## FCR operation

Frequency Containment Reserve (FCR) is the fastest automatic reserve used to keep the grid frequency close to its nominal value (50 Hz in Europe). The grid frequency is a direct measure of the balance between production and consumption: when consumption exceeds production the frequency drops below 50 Hz, and when production exceeds consumption it rises above 50 Hz. FCR reacts to these deviations within seconds to restore the balance.

As the EMS, the <BrandName /> <ControllerName /> continuously **measures the grid frequency** locally and **charges or discharges the battery** based on the frequency, following a predefined **droop curve**:

- **Frequency below 50 Hz** (shortage of power on the grid): the battery **discharges**, injecting power to help raise the frequency back to nominal.
- **Frequency above 50 Hz** (surplus of power on the grid): the battery **charges**, absorbing power to help bring the frequency back down.
- **Frequency at 50 Hz** (balanced grid): the battery stays idle within the dead band.

The **droop curve** defines how much power the battery delivers for a given frequency deviation. A small **deadband**, usually 10mHz, around 50 Hz avoids reacting to tiny fluctuations, and the response scales linearly with the deviation up to the maximum reserve power at the edge of the operating band. In the European FCR market, full activation is reached at a deviation of ±200 mHz (i.e. at 49.8 Hz and 50.2 Hz).

Because the controller measures the frequency itself and applies the droop curve autonomously, the battery responds automatically and in real time to grid frequency changes — no external setpoint is required to activate the reserve.

The **grid operator** controls the participation via [MQTT messages](#fcr-mqtt-messages) (specified below). These messages determine:

- **Whether FCR is active or not** — the grid operator enables or disables the reserve. When FCR is inactive, the controller does not respond to frequency deviations.
- **The allocated capacity** — the amount of reserve power the battery must provide. This allocated capacity can differ from the battery's nominal power (nompower); the droop curve is scaled to this allocated capacity rather than to the full nominal power of the battery.

## FCR MQTT Messages

FCR is driven by MQTT messages sent to the <BrandName /> <ControllerName />. For everything related to connecting to the MQTT broker — network requirements and credentials — follow the [Live MQTT Control](/Controller/External%20Signals/MQTT/eniris-mqtt/) guide first. FCR uses the same broker and connection, but its own dedicated topics described below.

### MQTT Topics

FCR uses a separate set of topics from the standard remote control. Replace `<Controller SN>` with the serial number of the <BrandName /> <ControllerName /> you intend to control.

| Topic | Direction | Purpose |
|-------|-----------|---------|
| `standard1/rp_one_s/remoteFCRMetrics/<Controller SN>` | To the controller | **Incoming topic** — used to send the FCR command (the JSON message below). |
| `standard1/outbound/remoteFCRMetrics/ack/<Controller SN>` | From the controller | **Ack topic** — the controller acknowledges here that the command has been received and saved. |
| `standard1/outbound/remoteFCRMetrics/feedback/<Controller SN>` | From the controller | **Feedback topic** — the controller publishes feedback here every second. |

### Message format

The FCR message has the following structure:

```json
{
    "time": 1714652046,
    "extraTags": {
        "nodeId": "<Controller SN>_site_0"
    },
    "fields": {
        "fcr": {
            "active": true,
            "capacity_kW": 100.0,
            "start_time": 1714652046,
            "end_time": 1714655646
        },
        "management": {
            "setpoint_W": -5000.0,
            "start_time": 1714652046,
            "end_time": 1714655646
        },
        "test": {
            "mode": "frequency_injection",
            "ramp": {
                "f_start_Hz": 50.0,
                "f_target_Hz": 49.8,
                "duration_s": 30.0,
                "t_start": 1714652046
            }
        }
    }
}
```

### Fields description

- **time** (Integer): Unix timestamp in seconds indicating when the message was sent.
- **extraTags** (Object):
    - **nodeId** (String): Unique identifier of the site node. This is your serial number followed by `_site_0` for most <BrandName /> <ControllerName /> devices.
- **fields** (Object): Contains the FCR instruction, split into the `fcr`, `management` and `test` blocks below. Each block is optional; only include the ones that apply.

#### fcr

Defines the actual FCR participation. This is the main block that determines whether the reserve is active and how the [droop curve](#fcr-operation) is scaled.

- **active** (Boolean): Whether FCR is active. When `true`, the controller responds to frequency deviations following the droop curve. When `false`, FCR is disabled and the controller does not react to the grid frequency.
- **capacity_kW** (Float): The allocated reserve capacity, in kilowatts, that the battery must provide. The droop curve is scaled to this value. As noted above, this can differ from the battery's nominal power (nompower).
- **start_time** (Integer): Unix timestamp in seconds at which this FCR instruction becomes active.
- **end_time** (Integer): Unix timestamp in seconds at which this FCR instruction expires.

#### management

Applies an explicit power setpoint on top of, or in place of, the FCR response — for example to steer the battery's state of charge back into a workable range while participating in FCR.

- **setpoint_W** (Float): Desired power setpoint in watts. A positive value charges the battery, a negative value discharges it.
- **start_time** (Integer): Unix timestamp in seconds at which the management setpoint becomes active.
- **end_time** (Integer): Unix timestamp in seconds at which the management setpoint expires.

#### test

Used to run a qualification or verification test on the installation. Only include this block when performing a test.

- **mode** (String): The test to perform. One of:
    - `"frequency_injection"`: Simulate a frequency deviation by ramping the frequency signal, to verify the droop response. Requires the `ramp` object below.
    - `"usable_energy"`: Verify the usable energy of the battery.
- **ramp** (Object): Only used when `mode` is `"frequency_injection"`. Describes the simulated frequency ramp:
    - **f_start_Hz** (Float): Frequency at the start of the ramp, in hertz.
    - **f_target_Hz** (Float): Frequency to ramp towards, in hertz.
    - **duration_s** (Float): Duration of the ramp, in seconds.
    - **t_start** (Integer): Unix timestamp in seconds at which the ramp starts.
- **target_soc** (Float): Only used when `mode` is `"usable_energy"`. The target state of charge, as a value from 20 to 100, that the battery should reach during the usable-energy test. The controller charges or discharges the battery towards this state of charge, measuring the energy transferred to verify the battery's usable energy.

### Acknowledgement message

After a command is received on the incoming topic, the <BrandName /> <ControllerName /> publishes an acknowledgement on the [ack topic](#mqtt-topics). The acknowledgement reports whether the command was accepted and saved, or rejected. It comes in one of the following two formats.

When the command received:

```json
{
    "requestTime": "<Unix Timestamp>",
    "time": "<Unix Timestamp>",
    "siteNodeId": "<Controller SN>_site_0",
    "data": {
        "status": "accepted" or "rejected",
        "error": "<error message>"
    },
    "fields": {}
}
```

#### Fields description

- **requestTime** (Integer): Unix timestamp in seconds of the original command being acknowledged. This matches the `time` field of the command that was sent, allowing you to correlate the acknowledgement with the request.
- **time** (Integer): Unix timestamp in seconds at which the acknowledgement was sent.
- **siteNodeId** (String): The `nodeId` of the site sending the acknowledgement.
- **data** (Object):
    - **status** (String): Either `"accepted"` when the command was received and saved, or `"rejected"` when it could not be applied.
    - **error** (String): Only present when `status` is `"rejected"`. Describes why the command was rejected.
- **fields** (Object): Empty object.

### Feedback message

While FCR is running, the <BrandName /> <ControllerName /> publishes a feedback message on the [feedback topic](#mqtt-topics) **every second**. This lets you monitor the live state of the installation and the FCR response in real time.

```json
{
    "time": "<Unix Timestamp>",
    "siteNodeId": "<Controller SN>_site_0",
    "data": {
        "fcr_active": <bool>,
        "frequency_Hz": <float>,
        "actualPowerTot_W": <float>,
        "setpoint_W": <float>,
        "fcrSetpoint_W": <float>,
        "managementSetpoint_W": <float>,
        "min_soc_perc": <float>,
        "max_soc_perc": <float>,
        "soc_perc": <float>,
        "droop_perc": <float>  
    }
}
```

#### Fields description

- **time** (Integer): Unix timestamp in seconds at which the feedback message was sent.
- **siteNodeId** (String): The `nodeId` of the site sending the feedback.
- **data** (Object):
    - **fcr_active** (Boolean): Whether FCR is currently active.
    - **frequency_Hz** (Float): The local grid frequency measured by the controller, in hertz.
    - **actualPowerTot_W** (Float): The actual active power of the battery, in watts. A positive value indicates charging, a negative value discharging.
    - **setpoint_W** (Float): The current total power setpoint, in watts. This is the sum of `fcrSetpoint_W` and `managementSetpoint_W` below. A positive value charges the battery, a negative value discharges it.
    - **fcrSetpoint_W** (Float): The FCR contribution to the power setpoint, in watts. This is the part of the setpoint resulting from the frequency deviation and the [droop curve](#fcr-operation).
    - **managementSetpoint_W** (Float): The management contribution to the power setpoint, in watts. This is the part of the setpoint coming from the [`management`](#management) charge/discharge signal, applied on top of the FCR response.
    - **min_soc_perc** (Float): The minimum allowed state of charge, as a percentage. Below this level the battery stops discharging to keep enough energy in reserve for FCR.
    - **max_soc_perc** (Float): The maximum allowed state of charge, as a percentage. Above this level the battery stops charging to keep enough headroom in reserve for FCR.
    - **soc_perc** (Float): The mean state of charge of the battery, as a percentage.
    - **droop_perc** (Float): The active droop, as a percentage — the share of the allocated FCR capacity currently being delivered in response to the frequency deviation.


# Mqtt


import { FolderOverview } from '@/components/FolderOverview';

# Mqtt

All credentials for connecting to the **Eniris MQTT broker** must be requested through the [Eniris webshop](https://webshop.eniris.com/). Credentials for a local MQTT broker built into a third-party device are supplied by that manufacturer and are identified separately in the relevant device guide.

<FolderOverview folder="Controller/External Signals/MQTT" />


# Onboarding Flow


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';
import DownloadButton from '@site/src/components/DownloadButton';

# External Signal Onboarding Flow

> [!TIP]
> The Onboarding guideline is meant for new integrations using the Eniris MQTT Protocol.

Before implementing the integration, request its Eniris MQTT credentials through the [Eniris webshop](https://webshop.eniris.com/). The onboarding API does not create broker credentials.

A drawback of the MQTT protocol is that there is no notification or data transfer when a new installation is added. Therefore it is recommended to include the following steps before fully integrating with the <BrandName /> <ControllerName />.

## Setup

The following will be required to set up an onboarding flow

1. External API
    - A public API is required

2. At least two endpoints
    - Onboarding endpoint
        The onboarding endpoint can be used by the <BrandName /> <ControllerName /> to send a signal indicating that the installation is ready to be controlled. Additional info may include contract numbers entered by users, installation address, device info
    - Offboarding endpoint
        The offboarding endpoint can be used to indicate that the external control signal has been removed from the <BrandName /> <ControllerName />, and control is no longer possible.
    - Status/healthcheck endpoint
        The healthcheck endpoint can be polled regularly by the <BrandName /> <ControllerName /> to provide a status update of the devices, or the system as a whole.

## Example

1. A new user adds the external signal in the <BrandName /> <ControllerName />. The Onboarding endpoint will be called to indicate that the <BrandName /> <ControllerName /> is ready to be listening for commands.

2. The <BrandName /> <ControllerName /> has lost connection with the battery. The healthcheck endpoint will contain an error message.

3. A contract number is required to link a <BrandName /> <ControllerName /> serial number to a customer. A contract number can be included in the onboarding flow, reducing back-and-forth communication between external signals and end customers.


# MQTT Setup


import { BrandName, ControllerName } from '@site/src/components/customFields';
import DownloadButton from '@site/src/components/DownloadButton';

# MQTT Setup

## What you need
1. <BrandName /> <ControllerName /> with internet connectivity.
2. Eniris MQTT credentials. These **must be requested through the [Eniris webshop](https://webshop.eniris.com/)** before commissioning. Do not request new MQTT credentials through a support ticket or create them in SmartgridX/Insights.
3. Python development environment (or any other MQTT client). This guide uses a basic example written in Python to get you started with MQTT and sending commands. We recommend to use Python for the ease of use, but any other MQTT client is supported.

> [!IMPORTANT]
> The webshop request is the provisioning request for the Eniris MQTT broker. Keep the issued username and password in an approved password manager and never include them in documentation, screenshots or ordinary email.

## Extra information
MQTT is a fast communication protocol over the internet. It is a publish/subscribe message systems, which allows for a direct connection between your machine and the <BrandName /> <ControllerName />. Your assets are classified into solar, battery, EV, and HVAC groups.

## First-time Configuration (Starting point for new users)
I have a <BrandName /> <ControllerName /> that I'd like to setup for MQTT Remote Control.

### 1. Check your network
Ensure that your network allows mqtt network traffic over port 1883. You can do this using command:

```
nc -zv mqtt.eniris.be 1883
```

When this command is not available, you can alternatively download and execute the python code:

<DownloadButton file="/docs/eniris/port_check.py" label="Download port_check.py" />

When in in doubt, consult your network engineer or temporarily use your phone's 4G/5G hotspot when connection errors occur.

> [!NOTE]
> When port 1883 is not accessible from your network, we offer a backup at port 80. This can be configured in your MQTT-client at a later step in this manual.

### 2. Add your devices
[Login to the commissioning interface](/Controller/Configuration%20from%20A%20to%20Z/2-accessing-commissioning-interface/) and make sure the [devices are added](/Controller/Configuration%20from%20A%20to%20Z/6-other-devices/) to the <BrandName /> <ControllerName />.


# Virtual Power Plant


import { BrandName, ControllerName, CustomerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';
import DownloadButton from '@site/src/components/DownloadButton';

# Virtual Power Plants

> [!TIP]
> The VPP Protocol is based on the Live MQTT Protocol. Please refer to this page before this. See [Live MQTT Control](/Controller/External%20Signals/MQTT/eniris-mqtt/).

> [!TIP]
> The initial VPP setup **MUST** be done by <CustomerName />. Please contact <CustomerName /> before following the next steps.

The MQTT username and password for the Eniris broker must be requested through the [Eniris webshop](https://webshop.eniris.com/). The VPP ID and project configuration are handled separately during VPP onboarding.

## Connecting to the MQTT Broker

Before continuing, make sure your network and devices are ready by following the [MQTT Setup](/Controller/External%20Signals/MQTT/setup/) guide.

## VPP Functionality

The VPP is designed to receive one setpoint/strategy per device group (e.g. Solar, Storage), and aggregate the setpoint between the controllers connected to the VPP.

Whereas the Live MQTT Protocol would send a command to a single controller, the VPP allows the user to send one command to a *group* of controllers.

<ClickableImage src="/img/generic/vpp.png" alt="Image 1" maxWidth="650px" />

### Adding Controllers to the VPP

<ClickableImage src="/img/generic/add-external-datasources-en.png" alt="Image 1" maxWidth="650px" />
<ClickableImage src="/img/generic/add-external-datasources-kind-en.png" alt="Image 1" maxWidth="650px" />
<ClickableImage src="/img/generic/add-external-datasources-brand-en.png" alt="Image 1" maxWidth="650px" />
<ClickableImage src="/img/generic/add-external-datasources-mqtt-en.png" alt="Image 1" maxWidth="650px" />

When adding the <CustomerName /> MQTT Signal, a `VPP ID` field is shown. Enter the **VPP ID** received here.

<ClickableImage src="/img/generic/mqtt-vpp-input.png" alt="Enter VPP ID" maxWidth="650px" />
<ClickableImage src="/img/generic/add-external-datasources-devices-en.png" alt="Image 1" maxWidth="650px" />

### Aggregation Algorithm

The setpoint are aggregated based on the capacity of the devices falling under the individual controllers. 

## MQTT Topics

Once the initial setup is complete, use the **VPP ID** from the VPP onboarding and the **MQTT username and password requested through the Eniris webshop**.

### Incoming Topic

Topic: `standard1/outbound/remoteVppMetrics/command/{MQTT Username}/{VPP ID}`

Topic (deprecated): `vpp/{MQTT Username}/{VPP ID}`

This topic is used by the user to send an aggregated command to the VPP.

#### Live VPP

Body:
```json
{
    "msg_id": <Incremental message id>(int),
    "vpp_id": <VPP ID>(str)
    "time": "<Unix Timestamp>(int)",
    "fields": {
        "<Component Policy>": "<Policy Type>",
        "<Component Power Setpoint>": <Setpoint in watts>
    }
}
```
The component policies and setpoints can be found here: [MQTT Components and Policies](/Controller/External%20Signals/MQTT/eniris-mqtt/#components-and-policies)

#### Scheduled VPP

Body:
```json
{
    "msg_id": <Incremental message id>(int),
    "vpp_id": <VPP ID>(str)
    "time": "<Unix Timestamp>(int)",
    "message_type": "<Type of message>(str)",
    "fields": {
        "<Component Policy>": "<Policy Type>",
        "<Component Power Setpoint>": <Setpoint in watts>
    }
}
```
The component policies and setpoints can be found here: [MQTT Components and Policies](/Controller/External%20Signals/MQTT/eniris-schedules-mqtt/#mqtt-message-types)


### Acknowledgement Topic

Topic: `standard1/outbound/remoteVppMetrics/acknowledgement/{MQTT Username}/{VPP ID}`

Topic (deprecated): `vpp/{MQTT Username}/{VPP ID}/acknowledgement`

After a command has been sent, the VPP will respond with an acknowledgement, indicating whether the command was successfully received or not.

Body:
```json
{
    "payload": {
        "fields": {
            "responseCode": <Success/Failure Code>(int),
            "ack": <Acknowledgement Message>(str)
        },
        "target": <VPP ID>(str)
    },
    "message_type": <Type of Message>(str)
}
```

### Feedback Topic

Topic: `standard1/outbound/remoteVppMetrics/feedback/{MQTT Username}/{VPP ID}`

Topic (deprecated): `vpp/{MQTT Username}/{VPP ID}/feedback`

The Feedback Topic contains the feedback returned by the individual controllers.

Body:
```json
{
    "payload": {
        "updated_on": <Unix Timestamp of the data>(str)
        "feedback_dict": {
            <Feedback Dict>(dict)
        },
        "target": <Site Node ID>(str)
    },
    "message_type": <Type of Message>(str)
}
```

The feedback dict structure can be found here: [MQTT Feedback Payload Structure](/Controller/External%20Signals/MQTT/eniris-mqtt/#mqtt-feedback-payload-structure)

### Aggregated Feedback Topic

Topic: `standard1/outbound/remoteVppMetrics/aggregatedFeedback/{MQTT Username}/{VPP ID}`

Topic (deprecated): `vpp/{MQTT Username}/{VPP ID}/aggregated_feedback`

The VPP aggregates the feedback received by each individual controller.

Body:
```json
{
    "payload": {
        "updated_on": <Unix Timestamp of the data>(str)
        "feedback_dict": {
            <Aggregated Feedback Dict>(dict)
        },
    },
    "message_type": <Type of Message>(str)
}
```

The aggregated feedback dictionary is structured similarly to the [MQTT Feedback Payload Structure](/Controller/External%20Signals/MQTT/eniris-mqtt/#mqtt-feedback-payload-structure).
However, string values, such as executed strategies, cannot be aggregated, and are therefore not included. 

### Dispatched Commands Topic

Topic: `standard1/outbound/remoteVppMetrics/dispatched/{MQTT Username}/{VPP ID}`

Topic (deprecated): `vpp/{MQTT Username}/{VPP ID}/dispatched_commands`

When commands are sent to the controllers by the VPP, this is reported using this topic.

Body:
```json
{
    "payload": {
        "aggregated": {
            <Component Name>(str): <CommandPower Value>(float)...
        },
        "dispatched_commands": [
            <List of individual commands sent to the controllers>
        ],
    },
    "message_type": <Type of Message>(str)
}
```

The payload structure of the individual commands sent can be found here: [MQTT Feedback Payload Structure](/Controller/External%20Signals/MQTT/eniris-mqtt/#example-payload).

### Warning Topic

Topic: `standard1/outbound/remoteVppMetrics/warning/{MQTT Username}/{VPP ID}`

Topic (deprecated): `vpp/{MQTT Username}/{VPP ID}/warning`

If an error or warning occurs in the VPP, a message will be sent over this MQTT topic.

Body:
```json
{
    "payload": {
        "fields": {
            <Field Dictionary>(dict)
        },
        "target": <VPP ID>(str)
    },
    "message_type": <Type of Message>(str)
}
```


# New integrations

New integrations may be considered for inclusion and added to our roadmap.

Review the requirements and submit your request through the [Eniris integration request form](https://eniris.com/knowledge/integration-request-from).

Eniris evaluates submitted requests against the current product roadmap and available engineering capacity.


# Next Energy


import { BrandName, ControllerName, CustomerName, InsightsName, InsightsUrl } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/sgo/Logo_NextEnergy.png"
    alt="Next Energy logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

# Setting up Next Energy

The manual describes the steps to set up Next Energy External Control on the <BrandName /> <ControllerName />.

When setting up this integration, permission is granted to Next Energy to control the necessary devices.

## Supported Devices

<DeviceSupportTable
  devices={[
    {
        type: 'Solar Inverters',
        variants: 'All',
        customCol: '✅'
    },
    {
        type: 'Storage Devices',
        variants: 'All',
        customCol: '✅'
    },
    {
        type: 'EV Chargers',
        variants: 'All',
        customCol: '❌'
    }
  ]}
    showVariants={true}
    customColumns={{ "customCol": "Supported" }}
/>

## Prerequisites

### 1. Add the batteries
[Login to the commissioning interface](/Controller/Configuration%20from%20A%20to%20Z/2-accessing-commissioning-interface/) and make sure the [devices are added](/Controller/Configuration%20from%20A%20to%20Z/6-other-devices/) to the <BrandName /> <ControllerName />.

### 2. Check the grid power limits
In the settings, the grid power limits should be set correctly. Click Settings and check the highlighted setting in the image.
If necessary, adjust the settings.

### 3. Enter your address
Ensure that your address is entered correctly before adding the external signal.
Click Settings and navigate to address.

### 3. Find the contract number
Request the contract number from the end customer or Next Energy. This number is necessary to add Next Energy as an external control partner.

If no contract number is available, you can provide your contact information instead. 
This information will be shared with Next Energy so they can reach out to you to arrange a contract.
The following fields must be entered:
- First Name
- Last Name
- Phone Number
- E-mail address

## Add 'Next Energy - External Control'
<ClickableImage src="/img/generic/add-external-datasources-en.png" alt="Image 1" maxWidth="650px" />
<ClickableImage src="/img/generic/add-external-datasources-kind-en.png" alt="Image 1" maxWidth="650px" />


In the next page, you have the option to include/exclude devices for remote control.
Ensure to mark all checkboxes of devices you'd like to include.

> [!NOTE]
> When using multiple batteries, they are aggregated into one (virtual) asset for Next Energy.

<ClickableImage src="/img/generic/add-external-datasources-devices-en.png" alt="Image 1" maxWidth="650px" />

'Next Energy' is now set up on the <BrandName /> <ControllerName />.

### Common Errors

#### Onboarding Failure

An error can occur when registering the site due to the following: 

1. The input fields were not filled in correctly.

2. The contract number does not exist or is incorrect.

3. The controller address is not set

Verify this when an error occurs.


# Opinum


import { BrandName, ControllerName, CustomerName, InsightsName, InsightsUrl } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';

<img
    src="/img/sgo/Logo_Opinum.png"
    alt="Opinum logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>
*Work In Progress*

# Paragraph 14a Integration


import { BrandName, ControllerName, CustomerName, InsightsName, InsightsUrl } from '@site/src/components/customFields';
import Details from '@theme/Details';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

> [!TIP]
> This integration is specifically for German users under the rules of EnWG Paragraph 14a, which allows grid operators to temporarily limit power consumption of controllable loads during peak periods.

This guide will help you configure your <BrandName /> <ControllerName /> to integrate with the SmartMeterGateway (SMGW) for Paragraph 14a compliance in Germany.

## Supported Devices

<DeviceSupportTable
  devices={[
    {
        type: 'Storage Devices',
        variants: 'Charging Only',
        customCol: '⚠️'
    },
    {
        type: 'EV Chargers',
        variants: 'All',
        customCol: '✅'
    },
    {
        type: 'Heatpumps',
        variants: 'All',
        customCol: '✅'
    },
    {
        type: 'Cooling Devices',
        variants: 'All',
        customCol: '❌'
    }
  ]}
    showVariants={true}
    customColumns={{ "customCol": "Supported" }}
/>

## What you need

1. <BrandName /> <ControllerName /> with internet connectivity.
2. Connection to a SmartMeterGateway (SMGW) with digital output signals.
3. For standard controllers:
   - Direct connection from the SMGW to the Digital Input (DI) pins on your controller.
4. For lite controllers or controllers without DI pins:
   - SG-ready relay module (DS1242)
   - Ethernet connection from the controller to the relay module
   - Connection from the SMGW to the DI pins on the relay module

## How it works

The Paragraph 14a integration enables your system to respond to grid management signals from your distribution system operator (DSO). When the grid is under strain, your SmartMeterGateway will send a signal to your <BrandName /> <ControllerName />, which will temporarily limit the power consumption of connected devices to 4.2kW by default.

## Configuration Process

The setup consists of two main parts:
1. Adding the Digital Input Device
2. Configuring the Paragraph 14a external signal

### Part 1: Add the Digital Input Device

1. Log in to [the commissioning interface](/Controller/Configuration%20from%20A%20to%20Z/2-accessing-commissioning-interface/).

2. Go to the "Devices" tab and click "Start device wizard".
<ClickableImage src="/img/generic/add-device-en.jpg" alt="Device wizard button" maxWidth="550px" />

3. Based on your controller type, follow one of these paths:

   **For Standard Controllers:**
   - Choose "Energy Meter" as the device type
   - Select "Generic" as the brand
   - Select "Relay" as the connection type
   - Select "Digital Input Device" as the model

   **For Lite Controllers:**
   - Choose "Energy Meter" as the device type
   - Select "Generic" as the brand
   - Select "Ethernet TCP to relay converter" as the connection type
   - Select "DS1242" as the model
   
4. Complete the device wizard by following the on-screen prompts:
   - Enter any requested additional inputs
   - For Ethernet connections, select the device by MAC address (recommended) or IP address
   - Adjust scan parameters if needed (default values are typically fine)
   - Wait for the device to be found and save it
   
   For detailed instructions on adding a device, see our [Adding a Device](/Controller/Configuration%20from%20A%20to%20Z/11-Extra-Information/adding-device/) guide.

### Part 2: Add the External Signal for Paragraph 14a

1. Go to the "External Data Sources" tab and click "Start Wizard".
<ClickableImage src="/img/generic/add-external-datasources-en.png" alt="External data sources button" maxWidth="650px" />

2. Select "External Signal" as the kind of data source.
<ClickableImage src="/img/generic/add-external-datasources-kind-en.png" alt="External signal selection" maxWidth="650px" />

3. Navigate to and select "Paragraph 14a" from the available external signals.

4. Configure the Paragraph 14a integration:
   - Choose all devices for which this signal should apply
   - The default power limit is set to 4.2kW, which is the standard for Paragraph 14a compliance
   - You can adjust this value if your agreement with the grid operator specifies a different limit

5. Complete the wizard by clicking "Save" or "Finish".

6. You should now see the Paragraph 14a signal added to your external signals list.

## Technical Details

The §14a formula is used to calculate the allowed grid import limit for all controllable devices.
The limit differs based on the number of devices, and it can be affected by total nominal power per device type.

When a §14a signal is received:

1. The <BrandName /> <ControllerName /> immediately limits the power consumption of selected devices
2. The §14a limit applies at the **grid connection point**.
3. Essential services remain unaffected:
   - Household / non-controllable loads are **not** part of the §14a restriction.
   - PV production and battery discharge may still be used behind the meter.
   - Battery **discharging** is not restricted by the §14a grid-import limit.
4. Normal operation resumes automatically when the signal ends

> [!WARNING] External Signal Priority
> The §14a signal has priority over local control modes and external signals. When active, it will limit power to controllables and then the local moode will have effect.

### Direct Control

Direct control is not implemented, as this allows the grid operator to send device-specific setpoints (or limits). This does not require the use of an EMS.

### EMS Control

EMS Control is enforced by calculating the consumption limit for all controllable devices on each individual location. The overall limit is dependent on the type an number of devices behind the grid meter.

The following formula is used to determine the limit per site:

<ClickableImage src="/img/generic/P14a.1.png" alt="Image 1" maxWidth="650px" />

If the sum of the grid connection power of heatpumps or coolers is larger than 11kW, we use the following formula:

<ClickableImage src="/img/generic/P14a.2.png" alt="Image 1" maxWidth="650px" />

The number of devices is counted as follows:
- Batteries are counted individually.
- EVs are counted individually.
- Devices with a connection capacity lower than 4.2kW are not included
   - Only heatpumps with a connection capacity lower than 4.2kW are included, if the overall connection capacity for all heatpumps is larger than 4.2kW. Then, we count all heatpumps as one device.

The simultaneity factor is determined using the following table.

| Number of Devices   | GZF  |
|---------------------|------|
| 1                   | 1    |
| 2                   | 0.8  |
| 3                   | 0.75 |
| 4                   | 0.7  |
| 5                   | 0.65 |
| 6                   | 0.6  |
| 7                   | 0.55 |
| 8                   | 0.5  |
| 9+                  | 0.45 |

In addition to the controllable consumption limit, the following formula is used to set the overall grid limit, to compensate for production power:

<ClickableImage src="/img/generic/P14a.3.png" alt="Image 1" maxWidth="650px" />

### Use Cases

#### Case 1.1

- An installation with five heatpumps of 2kW each is activated, and three batteries of 2kW.

   - If the batteries are charging:
      - The heatpump consumption limit is 4.2kW.
   - If the batteries are discharging:
      - The heatpump consumption limit from the grid is 4.2kW. The battery power can be used for the heatpumps, increasing their consumption limit to the maximum of 10kW.
   - The batteries are ignored because their connection capacity is smaller than 4.2kW each.

#### Case 1.2

- An installation with five heatpumps of 3kW each, an EV charger of 10kW and a battery of 7kW is activated.

   - If the battery is charging:
      - The controllable consumption limit from the grid is 12.3kW (6kW for the heatpumps, and 6.3kW for the EV and battery).
   - If the battery is discharging:
      - The controllable consumption limit from the grid is 12.3kW. The overall consumption limit can be increased to 19.3kW by the discharging battery.

#### Case 1.3

- An installation with five heatpumps of 3kW each is activated, and PV is producing 2kW.

- The controllable consumption limit is 8kW, and the net limit is 6kW.

#### Case 1.4

- An installation with five heatpumps of 3kW each is activated, there is 4kW uncontrollable load and PV is producing 2kW.

- The controllable consumption limit is 6kW, and the net limit is 8kW.

#### Case 1.5

- An installation with five heatpumps of 3kW each is activated, there is 2kW uncontrollable load and PV is producing 4kW.

- The controllable consumption limit is 8kW, and the net limit is 4kW (we are taking 6kW from the grid for controllable loads and injecting 2kW).


# Pleevi


import { BrandName, ControllerName, CustomerName, InsightsName, InsightsUrl } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';
import CountriesSupportTable from '@site/src/components/CountriesSupportTable';

<img
    src="/img/sgo/Logo_Pleevi.png"
    alt="Pleevi logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

# Setting up Pleevi

The manual describes the steps to set up Pleevi External Control on the <BrandName /> <ControllerName />.

When setting up this integration, permission is granted to Pleevi to control the necessary devices.

Before adding a new installation, please contact support@pleevi.ai to finalsie the setup.

## Supported Devices

<DeviceSupportTable
  devices={[
    {
        type: 'Solar Inverters',
        variants: 'All',
        customCol: '❌'
    },
    {
        type: 'Storage Devices',
        variants: 'All',
        customCol: '❌'
    },
    {
        type: 'EV Chargers',
        variants: 'All',
        customCol: '✅'
    }
  ]}
    showVariants={true}
    customColumns={{ "customCol": "Supported" }}
/>

## Supported Countries

<CountriesSupportTable
  countries={[
    {
        country: 'Belgium',
        customCol: '✅'
    },
    {
        country: 'Netherlands',
        customCol: '❌'
    },
  ]}
    showVariants={true}
    customColumns={{ "customCol": "Supported" }}
/>

## Prerequisites

### 1. Add the EV Chargers
[Login to the commissioning interface](/Controller/Configuration%20from%20A%20to%20Z/2-accessing-commissioning-interface/) and make sure the [devices are added](/Controller/Configuration%20from%20A%20to%20Z/6-other-devices/) to the <BrandName /> <ControllerName />.

### 2. Check the grid power limits
In the settings, the grid power limits should be set correctly. Click Settings and check the highlighted setting in the image.
If necessary, adjust the settings.

## Add 'Pleevi - External Control'
<ClickableImage src="/img/generic/add-external-datasources-en.png" alt="Image 1" maxWidth="650px" />
<ClickableImage src="/img/generic/add-external-datasources-kind-en.png" alt="Image 1" maxWidth="650px" />


In the next page, you have the option to include/exclude devices for remote control.
Ensure to mark all checkboxes of devices you'd like to include.

> [!NOTE]
> When using multiple batteries, they are aggregated into one (virtual) asset for Pleevi.

<ClickableImage src="/img/generic/add-external-datasources-devices-en.png" alt="Image 1" maxWidth="650px" />

'Pleevi' is now set up on the <BrandName /> <ControllerName />.


# Powernaut


import { BrandName, ControllerName, CustomerName, InsightsName, InsightsUrl } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';
import CountriesSupportTable from '@site/src/components/CountriesSupportTable';

<img
    src="/img/sgo/Logo_Powernaut.png"
    alt="Powernaut logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

# Setting up Powernaut

The manual describes the steps to set up Powernaut External Control on the <BrandName /> <ControllerName />.

When setting up this integration, permission is granted to Powernaut to control the necessary devices.

## Supported Devices

<DeviceSupportTable
  devices={[
    {
        type: 'Solar Inverters',
        variants: 'All',
        customCol: '✅'
    },
    {
        type: 'Storage Devices',
        variants: 'All',
        customCol: '✅'
    },
    {
        type: 'EV Chargers',
        variants: 'All',
        customCol: '❌'
    }
  ]}
    showVariants={true}
    customColumns={{ "customCol": "Supported" }}
/>

## Supported Countries

<CountriesSupportTable
  countries={[
    {
        country: 'Belgium',
        customCol: '✅'
    },
    {
        country: 'Netherlands',
        customCol: '❌'
    },
  ]}
    showVariants={true}
    customColumns={{ "customCol": "Supported" }}
/>

## Prerequisites

### 1. Add the devices
[Login to the commissioning interface](/Controller/Configuration%20from%20A%20to%20Z/2-accessing-commissioning-interface/) and make sure the [devices are added](/Controller/Configuration%20from%20A%20to%20Z/6-other-devices/) to the <BrandName /> <ControllerName />.

### 2. Check the grid power limits
In the settings, the grid power limits should be set correctly. Click Settings and check the highlighted setting in the image.
If necessary, adjust the settings.

## Add 'Powernaut'
From the commissioning interface, go to the 'External Signals' tab.
<ClickableImage src="/img/generic/add-external-datasources-en.png" alt="Image 1" maxWidth="650px" />

Click on 'Energy Markets'.
<ClickableImage src="/img/controller/external signals/types.png" alt="Image 1" maxWidth="650px" />

Select 'Powernaut' and click 'Next'.

## Device Selection

In the next page, you have the option to include/exclude devices for remote control.
Ensure to mark all checkboxes of devices you'd like to include.

> [!NOTE]
> When using multiple batteries, they are aggregated into one (virtual) asset for Powernaut.

<ClickableImage src="/img/generic/add-external-datasources-devices-en.png" alt="Image 1" maxWidth="650px" />

'Powernaut' is now set up on the <BrandName /> <ControllerName />.


# Repowered


import { BrandName, ControllerName, CustomerName, InsightsName, InsightsUrl } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';
import CountriesSupportTable from '@site/src/components/CountriesSupportTable';

<img
    src="/img/sgo/Logo_Repowered.png"
    alt="Repowered logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

# Setting up Repowered

## Supported Devices

<DeviceSupportTable
  devices={[
    {
        type: 'Solar Inverters',
        variants: 'All',
        customCol: '⌛ (coming soon)',
    },
    {
        type: 'Storage Devices',
        variants: 'All',
        customCol: '✅'
    },
    {
        type: 'EV Chargers',
        variants: 'All',
        customCol: '❌'
    }
  ]}
    showVariants={true}
    customColumns={{ "customCol": "Supported" }}
/>

## Supported Countries

<CountriesSupportTable
  countries={[
    {
        country: 'Belgium',
        customCol: '❌'
    },
    {
        country: 'Netherlands',
        customCol: '✅'
    },
  ]}
    showVariants={true}
    customColumns={{ "customCol": "Supported" }}
/>

## Notifying Repowered

Repowered will require information about the <BrandName /> <ControllerName /> before they can control any assets. 

This includes the *<BrandName /> <ControllerName /> Serial Number*, and the *SiteID*, which is the same as the Serial Number with '_site_0' appended at the end.

## Add 'Repowered' External Signal
<ClickableImage src="/img/generic/add-external-datasources-en.png" alt="Image 1" maxWidth="650px" />
<ClickableImage src="/img/generic/add-external-datasources-kind-en.png" alt="Image 1" maxWidth="650px" />

In the next page, you have the option to include/exclude devices for remote control.
Ensure to mark all checkboxes of devices you'd like to include.

> [!NOTE]
> When using multiple batteries, they are aggregated into one (virtual) asset.

<ClickableImage src="/img/generic/add-external-datasources-devices-en.png" alt="Image 1" maxWidth="650px" />

'Repowered' is now set up on the <BrandName /> <ControllerName />.

> [!TIP]
> When Repowered External Control is added, the <BrandName /> <ControllerName /> algorithm has **no control** over the battery's behaviour.

# Scholt


import { BrandName, ControllerName, CustomerName, InsightsName, InsightsUrl } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';
import CountriesSupportTable from '@site/src/components/CountriesSupportTable';

<img
    src="/img/sgo/Logo_Scholt.png"
    alt="Scholt logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

# Setting up Scholt

## Supported Devices

<DeviceSupportTable
  devices={[
    {
        type: 'Solar Inverters',
        variants: 'All',
        customCol: '⌛ (coming soon)',
    },
    {
        type: 'Storage Devices',
        variants: 'All',
        customCol: '✅'
    },
    {
        type: 'EV Chargers',
        variants: 'All',
        customCol: '❌'
    }
  ]}
    showVariants={true}
    customColumns={{ "customCol": "Supported" }}
/>

## Supported Countries

<CountriesSupportTable
  countries={[
    {
        country: 'Belgium',
        customCol: '✅'
    },
    {
        country: 'Netherlands',
        customCol: '✅'
    },
  ]}
    showVariants={true}
    customColumns={{ "customCol": "Supported" }}
/>

## Notifying Scholt

Scholt will require information about the <BrandName /> <ControllerName /> before they can control any assets. 

This includes the *<BrandName /> <ControllerName /> Serial Number*, and the *SiteID*, which is the same as the Serial Number with '_site_0' appended at the end.

## Add 'Scholt' External Signal
<ClickableImage src="/img/generic/add-external-datasources-en.png" alt="Image 1" maxWidth="650px" />
<ClickableImage src="/img/generic/add-external-datasources-kind-en.png" alt="Image 1" maxWidth="650px" />

In the next page, you have the option to include/exclude devices for remote control.
Ensure to mark all checkboxes of devices you'd like to include.

> [!NOTE]
> When using multiple batteries, they are aggregated into one (virtual) asset.

<ClickableImage src="/img/generic/add-external-datasources-devices-en.png" alt="Image 1" maxWidth="650px" />

'Scholt' is now set up on the <BrandName /> <ControllerName />.

> [!TIP]
> When Scholt External Control is added, the <BrandName /> <ControllerName /> algorithm has **no control** over the battery's behaviour.

### Control Modes

Scholt can send three different control strategies, based on the energy markets.

1. Charging/Discharging on Imbalance Costs- 
    When imbalance prices are favourable, Scholt will instruct the batteries to charge/discharge at maximum capacity.

2. Idle- 
    Scholt can instruct the battery to be idle (Setpoint zero).

3. Self-Consumption-
    Scholt can instruct the battery to follow an adapted self-consumption algorithm, usign excess PV power to charge the battery.
    This differs from normal self-consumption, as the battery will not discharge to on-site consumption.
    The battery will charge as usual using excess PV power, and it will not charge from the grid.
    However, unlike with a normal self-consumption strategy, the battery will not discharge when we are importing power from the grid.
    Instead, it will only discharge when we are importing from the grid at our power limit, in order to prevent exceeding the grid limits.

#### Default Fallback

If no signal is received from Scholt, the batteries will fall back to a local peak-shaving algorithm.


# Trevion


import { BrandName, ControllerName, CustomerName, InsightsName, InsightsUrl } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';
import CountriesSupportTable from '@site/src/components/CountriesSupportTable';

<img alt="Trevion logo" src="/img/sgo/Logo_Trevion.png" />

# Setting up Trevion

The manual describes the steps to set up 'Trevion - Imbalance' on the <BrandName /> <ControllerName />.

## Supported Devices

<DeviceSupportTable
  devices={[
  { type: 'Solar Inverters', variants: 'All', customCol: '✅' },
  { type: 'Storage Devices', variants: 'All', customCol: '✅' },
  { type: 'EV Chargers', variants: 'All', customCol: '❌' },
]}
  showVariants={true}
  customColumns={{ "customCol": "Supported" }}
/>

## Supported Countries

<CountriesSupportTable
  countries={[
  {
      country: 'Belgium',
      customCol: '✅'
  },
  {
      country: 'Netherlands',
      customCol: '❌'
  },
]}
  showVariants={true}
  customColumns={{ "customCol": "Supported" }}
/>

## Prerequisites

### 1. Add the batteries

[Login to the commissioning interface](/Controller/Configuration%20from%20A%20to%20Z/2-accessing-commissioning-interface/) and make sure the [devices are added](/Controller/Configuration%20from%20A%20to%20Z/6-other-devices/) to the <BrandName /> <ControllerName />.

### 2. Check the grid power limits

In the settings, the grid power limits should be set correctly. Click Settings and check the highlighted setting in the image.
If necessary, adjust the settings.

### 3. Custom Fields

The following information must be known before adding the Control Signal:

* Curtailment Threshold
  * The imbalance price threshold at which curtailment begins.
* Curtailment Depth
  * The percentage of nominal inverter power to be curtailed during curtailment periods.
  * A value of 100 means 0% production during curtailment periods.
* Curtailment Strategy
  * Limit the power of inverters (recommended).
  * Switch off a subset of inverters (less accurate; only necessary if inverters do not support setpoint control).
* Timeout
  * If the connection with the servers is lost, this defines how long we continue using the last received value before reverting to local control.
* Daily Overrides
  * The values above can be adjusted on specific days of the week (e.g., Sunday) if needed.
  * Use the format: `weekday (integer); start time (hh:mm); duration in minutes (integer); threshold; curtailment depth`.

## Add 'Trevion - Imbalance'

<ClickableImage src="/img/generic/add-external-datasources-en.png" alt="Image 1" maxWidth="650px" />

<ClickableImage src="/img/generic/add-external-datasources-kind-en.png" alt="Image 1" maxWidth="650px" />

In the next page, you have the option to include/exclude devices for remote control.
Ensure to mark all checkboxes of devices you'd like to include.

> [!NOTE]
>   When using multiple batteries, they are aggregated into one (virtual) asset for Trevion.

<ClickableImage src="/img/generic/add-external-datasources-devices-en.png" alt="Image 1" maxWidth="650px" />

'Trevion' is now set up on the <BrandName /> <ControllerName />.


# VGT Energy


import { BrandName, ControllerName, CustomerName, InsightsName, InsightsUrl } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';

<img
    src="/img/sgo/Logo_VGTEnergy.png"
    alt="VGT logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

# Setting up VGT Energy

## Supported Devices

<DeviceSupportTable
  devices={[
    {
        type: 'Solar Inverters',
        variants: 'All',
        customCol: '✅)',
    },
    {
        type: 'Storage Devices',
        variants: 'All',
        customCol: '✅'
    },
    {
        type: 'EV Chargers',
        variants: 'All',
        customCol: '❌'
    }
  ]}
    showVariants={true}
    customColumns={{ "customCol": "Supported" }}
/>

## Notifying VGT Energy
This includes the *<BrandName /> <ControllerName /> Serial Number*, and the *SiteID*, which is the same as the Serial Number with '_site_0' appended at the end.

## Add 'VGT Energy' External Signal
<ClickableImage src="/img/generic/add-external-datasources-en.png" alt="Image 1" maxWidth="650px" />
<ClickableImage src="/img/generic/add-external-datasources-kind-en.png" alt="Image 1" maxWidth="650px" />

In the next page, you have the option to include/exclude devices for remote control.
Ensure to mark all checkboxes of devices you'd like to include.

> [!NOTE]
> When using multiple batteries, they are aggregated into one (virtual) asset.

<ClickableImage src="/img/generic/add-external-datasources-devices-en.png" alt="Image 1" maxWidth="650px" />

'VGT Energy' is now set up on the <BrandName /> <ControllerName />.

# vZEV - Energy Community


import { BrandName, ControllerName } from '@site/src/components/customFields';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';
import CountriesSupportTable from '@site/src/components/CountriesSupportTable';
import Details from '@theme/Details';

# vZEV - Energy Community

**vZEV** (*Zusammenschluss zum Eigenverbrauch*) lets multiple, separately-metered sites - each with their
own <BrandName /> <ControllerName /> - pool their grid import/export into one shared "virtual" energy
community. Instead of every site optimizing its own self-consumption in isolation, a site with a battery
automatically reacts to what the *whole community* is doing on the grid right now, not just its own
consumption/production - so one participant's surplus can be absorbed by another participant's battery,
and vice versa.

Typical use case: a group of neighbouring buildings (e.g. an apartment block, a business park, a few
households on the same street) that want to share their solar production and battery capacity instead of
each optimizing on their own.

## Supported Devices

<DeviceSupportTable
  devices={[
  {
      type: 'Solar Inverters',
      variants: 'All',
      customCol: '✅',
  },
  {
      type: 'Storage Devices',
      variants: 'All',
      customCol: '✅'
  },
  {
      type: 'EV Chargers',
      variants: 'All',
      customCol: '❌'
  }
]}
  showVariants={true}
  customColumns={{ "customCol": "Supported" }}
/>

> [!NOTE]
>   Solar inverters are not curtailed for the community's benefit - instead, once a site joins with a solar
>   inverter, that inverter is kept at **full production** for as long as the site participates, so the
>   community always gets the maximum available solar rather than having a battery elsewhere compensate for
>   production that was curtailed for the site's own economics.

## Supported Countries

<CountriesSupportTable
  countries={[
  {
      country: 'Switzerland',
      customCol: '✅'
  },
]}
  showVariants={true}
  customColumns={{ "customCol": "Supported" }}
/>

> [!NOTE]
>   vZEV is currently only offered to sites whose configured **address** is in Switzerland. **If you can't
>   find the "Setup vZEV" option on a site, check that site's configured address first** - that's the only
>   gate. See [Prerequisites](#prerequisites) below.

## What it's for

* **Community self-consumption.** Multiple sites share their solar surplus and battery capacity instead of
  each buying/selling independently.
* **No extra hardware or cloud contract.** Participants only need a grid energy meter that's already added
  to the <BrandName /> <ControllerName />; the community itself needs no separate subscription or gateway.
* **Live, automatic balancing.** No manual scheduling - a site with a battery reacts to the community's
  current net exchange with the grid, in real time.

## Prerequisites

Before setting up vZEV on a site, make sure:

* The site's configured **address is in Switzerland** (see [Supported Countries](#supported-countries)
  above) - otherwise the "Setup vZEV" option won't appear.
* The site has a **grid energy meter** added and configured. Without one, the setup wizard will stop and
  offer you a shortcut to add one.
* Any battery or solar inverter that should participate is already
  [added to the controller](/Controller/Configuration%20from%20A%20to%20Z/6-other-devices/) beforehand.
  There is no separate device-selection step during vZEV setup - **every compatible battery and solar
  inverter already on the site joins the community automatically**. You'll be shown the list of devices
  that will participate before you confirm.

## Setting up vZEV

On the **Settings** page (also shown on the **Home** page), sites in Switzerland that aren't part of a
community yet show a "Setup vZEV (Energy Community)" button. This starts a short wizard:

1. A short introduction screen explaining what vZEV is.
2. Choose whether you want to **create a new community** or **join an existing one**.

### Creating a new community

Use this for the *first* site of a new community.

1. Choose a **unique energy community ID** - this is shared with everyone you invite, so pick something
   recognizable (e.g. based on the street or building name) but not easily guessable by strangers.
2. Review the list of devices that will participate (every battery/solar inverter already on the site).
3. Confirm. You'll immediately be shown a **join token** - see [The join token](#the-join-token) below.
   You must save this before continuing; it is never shown again.

### Joining an existing community

Use this for every site *after* the first one.

1. Enter the **energy community ID** and the **join token**, both provided by whoever created the
   community (or by a previous participant who still has them).
2. Review the list of devices that will participate.
3. Confirm - the site joins immediately, no token of its own is generated.

## The join token

The join token is a one-time secret generated when a community is **created**. Think of it as the
community's password:

* Anyone with the **energy community ID + join token** can add a new site to the community.
* It is shown **exactly once**, right after creation. Save it somewhere secure immediately (e.g. a
  password manager) - **it cannot be retrieved again afterwards**, by anyone, including support.
* If the token is lost, existing participants keep working normally, but **no new site can be added** to
  that community until you create a new one instead (see [Difficulties](#known-difficulties-and-limitations)).

## Commissioning multiple participants

To set up a community of several sites:

1. Pick one site to go first. On its controller, run through **Setup vZEV → Create a new community**,
   choose the community ID, and save the join token securely (e.g. share it with your team through a
   password manager, not through plain chat/email if you can avoid it).
2. For every other site: on *that* site's own controller, run through **Setup vZEV → Join an existing
   community**, and enter the same community ID and join token from step 1.
3. Repeat for as many sites as should participate. There's no fixed limit on the number of participants.
4. A site does **not** need a battery to join - a site with only a grid meter (and optionally solar) still
   contributes its consumption/production to the community and benefits from it, it just isn't steered
   itself. A site with a battery actively helps balance the whole community.

Each site's setup is independent and self-service - there's no central dashboard where one installer
manages every participant's controller. Every participant needs someone with access to that specific
controller to run the join step there.

## Viewing the community

Once set up, the Settings/Home page shows the community ID and how many other participants are known,
with a **"View community overview"** button. This opens the **vZEV Map**: a live diagram of the power
currently flowing between the grid, this site (highlighted, broken down into its own devices), and every
other participant, plus a chart of every participant's net energy exchanged since the start of the current
15-minute interval. On a well-balanced community, the community-wide line on that chart stays close to
zero.

## Removing vZEV from a site

On the Settings page, the vZEV panel has a **"Remove vZEV"** button. Removing vZEV only affects the site
you're on - it stops that site's own participation (reporting and, if applicable, battery steering) and
returns you to the Settings page. It does not affect any other participant, and does not delete the
community itself.

## Features overview

* Pools multiple independently-metered sites into one shared, live-balanced energy community.
* Automatic, real-time battery steering that reacts to the whole community's net grid exchange, not just
  the local site's.
* A slower, periodic correction that keeps nudging the community's net exchange back toward zero over time,
  on top of the fast, live reaction - so small moment-to-moment mismatches don't add up over an interval.
* Automatically respects each site's own grid connection limits - a site is never asked to charge/discharge
  its battery harder than its own grid connection safely allows, even if the community needs more.
* Solar production is kept uncurtailed for participating sites, so the community benefits from the maximum
  available solar rather than losing it to price-based curtailment.
* Passive participation for sites without a battery - they still contribute and benefit, without being
  steered.
* A software-version safety check: if a participant's controller software falls behind the rest of the
  community, it automatically stops steering its battery and shows a clear on-screen message until it's
  updated, instead of silently behaving differently from everyone else.
* A live map and historical chart to visualize how the community is doing.

## Known difficulties and limitations

* **Switzerland only**, for now.
* The join token is shown once and **cannot be recovered or regenerated**. Losing it doesn't break the
  community, but blocks adding new participants until a new community is created.
* There is currently **no way to remove another participant** - removal is self-service only, done by that
  participant on their own controller. If a participant becomes unreachable or should be excluded, that
  needs to be arranged with whoever manages that site directly.
* If a participant is removed or permanently goes offline, other participants may keep showing its
  last-known contribution for a while rather than immediately reflecting its absence.
* All compatible batteries and solar inverters on a site join automatically - there is currently no way to
  select only some of a site's devices to participate.
* A site can only be part of **one** vZEV community at a time.
* The battery reaction is purely live/reactive (plus the periodic correction above) - it does not forecast
  or pre-schedule charging/discharging ahead of time.

## Troubleshooting

<Details summary="I can't find the 'Setup vZEV' option on a site.">
  * Check that the site's configured address is in Switzerland - this is the only requirement that gates
    visibility of the option (see [Prerequisites](#prerequisites)).
  * Check that the site isn't already part of a community - the option is replaced by the community's status
    once set up.
</Details>

<Details summary="The setup wizard tells me a grid meter is required.">
  * Add and configure a grid energy meter on the site first, then restart the vZEV setup. The wizard offers a
    shortcut button straight to adding one.
</Details>

<Details summary="A participant's status shows 'Update this controller to participate in the energy community.'">
  * This means that controller's software is behind at least one other participant in the same community.
  * The battery on that site is **not being steered** while this message is shown (same as a site without a
    battery) - it will resume automatically once the controller is updated to a version that's no longer
    behind, no manual reset needed.
</Details>

<Details summary="A participant's net energy on the vZEV Map / chart stays stuck at 0 kWh, even though that site is clearly consuming or producing.">
  * The site's grid meter is reporting live power correctly, but not real cumulative imported/exported
    energy. Check that site's grid meter configuration and connection - if the meter itself looks healthy and
    this persists, contact support.
</Details>

<Details summary="A battery isn't reacting even though the community clearly has a surplus/deficit.">
  * Check the general checklist under ["Control problems"](/Controller/Troubleshooting/control-malfunctioning/) first
    (device online, remote control enabled, no active faults, no other higher-priority external signal
    overriding vZEV).
  * Check that the battery still has room to charge/discharge - the community can't ask more of a battery
    than its own state of charge and grid connection limits allow at that moment.
</Details>

<Details summary="I lost the join token for our community.">
  * It cannot be recovered by support or anyone else. Existing participants are unaffected and keep working
    normally, but no new site can join that community. To add more participants going forward, create a new
    community and have every site join that one instead.
</Details>


# Yuso - Battery Control


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';
import CountriesSupportTable from '@site/src/components/CountriesSupportTable';

<img
    src="/img/sgo/Logo_Yuso.png"
    alt="Yuso logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

## Supported Devices

<DeviceSupportTable
  devices={[
    {
        type: 'Solar Inverters',
        variants: 'All',
        customCol: '❌',
    },
    {
        type: 'Storage Devices',
        variants: 'All',
        customCol: '✅'
    },
    {
        type: 'EV Chargers',
        variants: 'All',
        customCol: '❌'
    }
  ]}
    showVariants={true}
    customColumns={{ "customCol": "Supported" }}
/>

## Supported Countries

<CountriesSupportTable
  countries={[
    {
        country: 'Belgium',
        customCol: '✅'
    },
    {
        country: 'Netherlands',
        customCol: '✅'
    },
  ]}
    showVariants={true}
    customColumns={{ "customCol": "Supported" }}
/>

## Getting started
### Get the configuration files and 'client id' from Yuso

The files are typically provided in a zip archive file. Unzip the files before proceeding.
- Certificate (file with .pem.crt extension)
- Private key (file with .pem.key extension)
- Root key (file with .pem extension)
- Yuso Client ID (a unique identifier for your installation)
- Yuso Thing name

> [!NOTE]
> A Yuso Client ID is a short identifier in the following format:
>
> ```<Yuso Thing name>-<secret string>```

All these things are needed to configure the Yuso external signal in the <BrandName /> <ControllerName />.
You should have received these files from Yuso. If you haven't received them yet, please contact Yuso support.
### Add your devices
[Login to the commissioning interface](/Controller/Configuration%20from%20A%20to%20Z/2-accessing-commissioning-interface/) and make sure the [devices are added](/Controller/Configuration%20from%20A%20to%20Z/6-other-devices/) to the <BrandName /> <ControllerName />.

### Check the grid power limits
In the settings, the grid power limits should be set correctly. Click Settings and check the highlighted setting in the image.
If necessary, adjust the settings.

<ClickableImage src="/img/generic/grid-power-limits-en.png" alt="Image 1" maxWidth="650px" />

### Optional step: if battery losses need to be accounted for
Some batteries don't give the energy and power values on the AC-side of the inverter. This can be a potential loss in revenue during negative imbalance moments. We provide a simple solution in which a dedicated meter can be assigned to a battery. Instead of reading out the battery power, we read out the power of the dedicated meter.

If you want to enabled this:
1. Make sure the energy meter is added
2. In the meter settings, switch the measurement target to measuring batteries.
<ClickableImage src="/img/generic/energy-meter-for-storage-en.png" alt="Image 1" maxWidth="650px" />
3. Assign the meter to the battery. Navigate to the 'Groups' page and click on 'Advanced', scroll down and link the battery to the battery.
> [!WARNING]
> In case of multiple batteries or battery containers:
> Yuso steers the batteries as one virtually aggregated BESS. For correct configuration please select the group in which the batteries are located.
> It is crucial that all batteries in this group are controlled by Yuso. There must be no other devices or batteries in the group.
> [!NOTE]
> See also "[grouping devices](/Controller/Configuration%20from%20A%20to%20Z/7-grouping-devices/)".
<ClickableImage src="/img/generic/group-energy-meter-en.png" alt="Image 1" maxWidth="650px" />

### Add the Yuso external signal
<ClickableImage src="/img/generic/add-external-datasources-en.png" alt="Image 1" maxWidth="650px" />
<ClickableImage src="/img/generic/add-external-datasources-kind-en.png" alt="Image 1" maxWidth="650px" />
<ClickableImage src="/img/generic/add-external-datasources-yuso-en.png" alt="Image 1" maxWidth="650px" />

## Background information

Yuso uses a cloud-based platform that enables communication with <BrandName /> <ControllerName />. This is done via the MQTT communication protocol, monitoring and controlling various parameters. 

### Yuso Steering Modes
Basically, every minute, Yuso sends a signal (steering modus) to be executed by the <BrandName /> <ControllerName />. Every minute, Yuso algorithms computes the best steering modus for that bess at that point in time.\
There are three steering modi, which are mutually exclusive:

1. **Active Modus = standby.**\
    In this modus, the state of charge is kept constant. This means that, if for a long time a battery is idling, the state of charge can drop by one percent, and the battery will be charged at 400 W to the state of charge again. This way, the battery is kept ready for action when needed.

[//]: # (    :::note Technical note by Yuso:)

[//]: # (    This is the default modus for standalone BESS. In this modus, the SOC is kept constant &#40;losses can be covered from the grid to keep the SOC as constant as possible&#41;)

[//]: # (    The Yuso’s setpoint &#40;`activePowerReq`&#41; to the EMS in this modus is zero.)

[//]: # (    The reported `activePower` at the Service Point will be possibly non-zero due to keeping the SOC constant.)

[//]: # ()
[//]: # (    In this modus, all energy exchanged with the grid is settled at day Ahead price.)

[//]: # (    :::)

2. **Active Modus = self-supply  (or during communication failure)**\
    Yuso sends a self-supply signal to the <BrandName /> <ControllerName /> when there are no opportunities to trade on
    imbalance market. This is also the mode being applied when communication with the internet or with Yuso is lost.

    _Software version 1.18.0.3 or older:_ In this modus, Yuso asks the <BrandName /> <ControllerName /> to steer 'self-supply' on the meter. The <BrandName /> <ControllerName /> follow the mode configured as default mode (e.g. "Self-consumption") in the <BrandName /> <ControllerName />, which can be configured in the [settings of the controller](/Controller/Configuration%20from%20A%20to%20Z/8-local-control-modes/setting-control-modes/).

    _Software version 1.18.0.4 or newer:_ In this modus, Yuso asks the <BrandName /> <ControllerName /> to steer towards 0 on the meter. The battery will be used for self-consumption __when the grid limits are not exceeded__. This means that the battery will charge when there is excess production and discharge when there is local demand.

[//]: # (    :::note Technical note by Yuso:)

[//]: # (    This is the default modus for PV connected BESS.)

[//]: # ()
[//]: # (    The Yuso’s setpoint &#40;`activePowerReq`&#41; to the EMS is indicative and should be translated to an actual `ActivePowerExec` setpoint to be executed, considering all site constraints.)

[//]: # ()
[//]: # (    The reported `activePower` at the Service Point will be non-zero due to local demand or excess production of the site.)

[//]: # ()
[//]: # (    Only the energy exchanged with the grid is settled at day Ahead price.)

[//]: # (    :::)
3. **Active Modus = direct**\
    Yuso sends a power-setpoint to the <BrandName /> <ControllerName />, which in practice results in a high-power (dis)charge command on your battery, for the benefit of the imbalance market.
    The <BrandName /> <ControllerName /> can adjust the setpoint to ensure safe operation of the battery and compliance with grid limits.

[//]: # (    :::note Technical note by Yuso:)

[//]: # (    This is the overruling modus, as sent by Yuso when opportunities are detected to trade on imbalance market.)

[//]: # (    The desired parameter `activePowerReq` is indicative and should be translated to an actual `ActivePowerExec` setpoint to be delivered to the asset for execution.)

[//]: # (    This executable setpoint must be calculated such that safe operation is guaranteed and in compliance with the Synergrid guidelines.)

[//]: # (    In settlement, the energy exchanged during overruling is split in two buckets:)

[//]: # (    - all energy exchanged with the BESS is settled at Imbalance price &#40;E_BESS&#41;)

[//]: # (    - all other energy exchanged with the site is settled at Day Ahead price. &#40;E_SITE&#41;)

[//]: # (    Measuring E_BESS via the controller, and receiving E_GRID via the regular market processes &#40;ATRIAS&#41;, Yuso can calculate `E_SITE` as `E_GRID - E_BESS`)

[//]: # ()
[//]: # (    It is allowed to ignore the Overruling signal. The executed steering modus must then also be reported via the Yuso Standard Interface as "self-supply" instead of "direct".)

[//]: # (    In that case, if the Yuso overruling signal is not followed, it is not allowed to control the battery with a power greater than the power that is locally net requested or injected by the rest of the site &#40;excl. battery&#41;.)

[//]: # (    An exception is made for limited grid connections where the access power is less than 60% of the nominal power of the battery.)

[//]: # (    :::)

### Information on signal overruling
We strongly discourage setting up another external signal besides the Yuso signal. The <BrandName /> <ControllerName /> can only
handle one external signal at a time. If you set up another external signal, it will override the Yuso signal if the other signal has a higher priority assigned.
This means that the Yuso signal will not be executed, and the battery will not be controlled by Yuso.

If you proceed with setting up another external signal, please be aware of the following:
- The <BrandName /> <ControllerName /> will send policy 'self-supply' to the Yuso platform in case of overruling the Yuso signal.
- The <BrandName /> <ControllerName /> will show the following warning at the Yuso-signal: \
  _"Warning: found override by higher priority signal. This is not allowed by Yuso, unless arranged otherwise with Yuso."_
- Be compliant with this rule:\
    _"It is allowed to ignore the Overruling signal. The executed steering modus must then also be reported via the Yuso Standard Interface as "self-supply" instead of "direct".
    In that case, if the Yuso overruling signal is not followed, it is not allowed to control the battery with a power greater than the power that is locally net requested or injected by the rest of the site (excl. battery)."_

### Information on doing Yuso PV-curtailment and battery control at the same time
The <BrandName /> <ControllerName /> supports two Yuso services:
- Yuso solar curtailment
- Yuso battery control

At the moment it is __not__ possible to use both Yuso products __at the same time__. If you want to use Yuso battery control, you need to disable Yuso PV-curtailment.
If you want to use Yuso PV-curtailment, you need to disable Yuso battery control.

However, it is possible to use [any local control mode](/Controller/Configuration%20from%20A%20to%20Z/8-local-control-modes/setting-control-modes/) (e.g. cost optimization) on the solar panels and Yuso battery control at the same time.
But be aware that it can lead to contradicting behaviour of your solar inverter and battery: when the solar panels are controlled by a [local control mode cost optimization](/Controller/Configuration%20from%20A%20to%20Z/8-local-control-modes/setting-control-modes/#production-devices),
it might curtail while Yuso is discharing the battery.

Yuso is working on a solution to use both Yuso services at the same time. We will update this page when this is possible.

# Yuso - Solar Curtailment


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';
import DeviceSupportTable from '@site/src/components/DeviceSupportTable';
import CountriesSupportTable from '@site/src/components/CountriesSupportTable';

<img
    src="/img/sgo/Logo_Yuso.png"
    alt="Yuso logo"
    style={{ display: "block", margin: "0 auto", width: "40%"}}
/>

## Supported Devices

<DeviceSupportTable
  devices={[
    {
        type: 'Solar Inverters',
        variants: 'All',
        customCol: '✅'
    },
    {
        type: 'Storage Devices',
        variants: 'All',
        customCol: '❌'
    },
    {
        type: 'EV Chargers',
        variants: 'All',
        customCol: '❌'
    }
  ]}
    showVariants={true}
    customColumns={{ "customCol": "Supported" }}
/>

## Supported Countries

<CountriesSupportTable
  countries={[
    {
        country: 'Belgium',
        customCol: '✅'
    },
    {
        country: 'Netherlands',
        customCol: '✅'
    },
  ]}
    showVariants={true}
    customColumns={{ "customCol": "Supported" }}
/>

## Getting started
### Get the configuration files and 'client id' from Yuso

The files are typically provided in a zip archive file. Unzip the files before proceeding.
- Certificate (file with .pem.crt extension)
- Private key (file with .pem.key extension)
- Root key (file with .pem extension)
- Yuso Client ID (a unique identifier for your installation)
- Yuso Thing name

> [!NOTE]
> A Yuso Client ID is a short identifier in the following format:
>
> ```<installation name>_Battery_XXXXXXXXXXXXXXXXXXXX```

All these things are needed to configure the Yuso external signal in the <BrandName /> <ControllerName />.
You should have received these files from Yuso. If you haven't received them yet, please contact Yuso support.
### Add your devices
[Login to the commissioning interface](/Controller/Configuration%20from%20A%20to%20Z/2-accessing-commissioning-interface/) and make sure the [inverters are added](/Controller/Configuration%20from%20A%20to%20Z/6-other-devices/) to the <BrandName /> <ControllerName />.


### Add the Yuso external signal
First, find the Yuso external signal:
<ClickableImage src="/img/generic/add-external-datasources-en.png" alt="Image 1" maxWidth="650px" />
<ClickableImage src="/img/generic/add-external-datasources-kind-en.png" alt="Image 1" maxWidth="650px" />
<ClickableImage src="/img/generic/add-external-datasources-yuso-en.png" alt="Image 1" maxWidth="650px" />
Fill in the Yuso Thing name and the Yuso Client ID, and upload the certificate, private key, and root key files you received from Yuso.
> [!WARNING]
> Use the '_minimum power setpoint percentage_' __only__ if you experience a slow ramp up time. Some inverters go to sleep when being curtailed to zero power, and when uncurtailed, it takes some time to wake up again.
> This setting will ensure that the inverter is always kept awake by sending a small setpoint, typically resulting in a faster ramp up time.
<ClickableImage src="/img/customers/yuso/yuso-curtailment-1.png" alt="Image 1" maxWidth="650px" />
Select all inverters that should participate in the Yuso solar curtailment. If you have multiple inverters, you can select them all at once.
__Important:__ Make sure that you also include the inverter that you'd like to use for calculating the baseline production. This inverter will not be curtailed, but it will be used to calculate the baseline production. This is important for the Yuso solar curtailment service to work correctly.
<ClickableImage src="/img/customers/yuso/yuso-curtailment-2.png" alt="Image 1" maxWidth="650px" />
Now select the inverter(s) that you want to use for calculating the baseline production. You can select multiple inverters, but at least one inverter must be selected.
We recommend to select a single inverter that is the smallest inverter on your site, as the 'curtailment-loss' will be kept to a minimum. Further on, we will refer to this inverter as the 'reference inverter(s)'.
<ClickableImage src="/img/customers/yuso/yuso-curtailment-3.png" alt="Image 1" maxWidth="650px" />

## Background information

Yuso uses a cloud-based platform that enables communication with <BrandName /> <ControllerName />. This is done via the MQTT communication protocol, monitoring and controlling various parameters.
### Calculating curtailed production and the _baseline power_
To estimate curtailed production, we designate one inverter (out of, say, 10 identical 4 kW inverters) as a reference inverter, which is never curtailed and always runs at full power, while the others may be curtailed; we assume that all inverters could produce similarly to the reference, so if it outputs 2 kW, we scale it up to the total system size. If the full system is 40 kW and the reference inverter is only 3 kW nominal, we multiply by 40 / 3 ≈ 13.33 to get an uncorrected baseline of 26.7 kW. To improve accuracy, we apply a correction factor based on a rolling 60-minute comparison between the actual production of the curtailed inverters and what we would have expected based on the reference inverter during that same period—this accounts for any under- or overperformance of the reference inverter compared to the fleet. The curtailed production is then the difference between this corrected baseline and the actual measured output of the curtailed inverters. The baseline power is then the power it would have produced if it had not been curtailed, corrected for the performance of the reference inverter.
### Yuso Steering Modes
Basically, every minute, Yuso sends a signal (steering modus) to be executed by the <BrandName /> <ControllerName />. Every minute, Yuso algorithms computes the best steering modus for that bess at that point in time.\
There are three steering modi, which are mutually exclusive:

1. **Active Modus = standby.**\
    Yuso sends a standby signal to the <BrandName /> <ControllerName />. The <BrandName /> <ControllerName /> allows to all inverters to fully produce (no curtailment).
2. **Active Modus = self-supply  (or during communication failure)**\
    Yuso sends a self-supply signal to the <BrandName /> <ControllerName />. The <BrandName /> <ControllerName /> will then try to limit the production to the local consumption, while not exporting back to the grid.
    This is also called 'zero export'.
3. **Active Modus = direct**\
    Yuso sends a power-setpoint to the <BrandName /> <ControllerName />, which tells us how much the inverters should produce. In practise however, it results in turning off the inverters.

### Information on signal overruling
We strongly discourage setting up another external signal besides the Yuso signal. The <BrandName /> <ControllerName /> can only
handle one external signal at a time. If you set up another external signal, it will override the Yuso signal if the other signal has a higher priority assigned.
This means that the Yuso signal will not be executed, and the battery will not be controlled by Yuso.

If you proceed with setting up another external signal, please be aware of the following:
- The <BrandName /> <ControllerName /> will send policy 'self-supply' to the Yuso platform in case of overruling the Yuso signal.
- The <BrandName /> <ControllerName /> will show the following warning at the Yuso-signal: \
  _"Warning: found override by higher priority signal. This is not allowed by Yuso, unless arranged otherwise with Yuso."_

### Information on doing Yuso PV-curtailment and battery control at the same time
The <BrandName /> <ControllerName /> supports two Yuso services:
- Yuso solar curtailment
- Yuso battery control

At the moment it is __not__ possible to use both Yuso products __at the same time__. If you want to use Yuso battery control, you need to disable Yuso PV-curtailment.
If you want to use Yuso PV-curtailment, you need to disable Yuso battery control.

However, it is possible to use [any local control mode](/Controller/Configuration%20from%20A%20to%20Z/8-local-control-modes/setting-control-modes/) (e.g. cost optimization) on the solar panels and Yuso battery control at the same time.
But be aware that it can lead to contradicting behaviour of your solar inverter and battery: when the solar panels are controlled by a [local control mode cost optimization](/Controller/Configuration%20from%20A%20to%20Z/8-local-control-modes/setting-control-modes/#production-devices),
it might curtail while Yuso is discharing the battery.

Yuso is working on a solution to use both Yuso services at the same time. We will update this page when this is possible.



# Start here


import { ChapterLanding } from '@/components/ChapterLanding';
import { FolderOverview } from '@/components/FolderOverview';

<ChapterLanding
  chapter="controller"
  introductionLabel="Chapter introduction"
  eyebrow="Hardware & energy management"
  title="SmartgridOne controller"
  description="Install, configure, and operate your controller with confidence. Start with the essentials, connect your energy devices, and fine-tune local control for every site."
  highlightOne="Installation"
  highlightTwo="Device integrations"
  highlightThree="Troubleshooting"
/>

## Explore the controller documentation

<FolderOverview folder="Controller" />


# Installation


import { BrandName, ControllerName } from '@site/src/components/customFields';

# Installation of the hardware

> [!NOTE]
> During the installation process you must at all times take the provisions of [the safety, maintenance and legal notices](/Controller/Configuration%20from%20A%20to%20Z/11-Extra-Information/battery-maintenance-charge/) into account.

## Model OM1

### Hardware Installation

#### Wall-mounted

<div style={{ display: "flex", gap: "16px", justifyContent: "center" }}>
    <img src="/img/eniris/wall-mounting-pt1.png" alt="Image 1" style={{ height: "100%" }} />
    <img src="/img/eniris/wall-mounting-pt2.png" alt="Image 2" style={{ height: "100%" }} />
</div>


 1. Accurately measure the hole pattern for the mounting points.

> [!TIP]
>
>     The <BrandName /> <ControllerName /> has a hole pattern of 80mm x 63mm (W x H).\
>     The screw head should not exceed a diameter of 7mm (e.g., a universal screw of 4 x 40mm is recommended).\
>     *For a flush mount, ensure the screws protrude no more than 8mm from the wall.*
>

 2. Insert the required screws into the surface where the <BrandName /> <ControllerName /> will be mounted, ensuring they are securely fastened.
 3. Carefully align the <BrandName /> <ControllerName /> with the installed screws and slide it into place. Ensure it is securely mounted.

#### DIN-rail mount

<div style={{ display: "flex", gap: "16px", justifyContent: "center" }}>
    <img src="/img/eniris/din-rail-mounting-pt1.png" alt="Image 1" style={{ height: "100%" }} />
    <img src="/img/eniris/din-rail-mounting-pt2.png" alt="Image 2" style={{ height: "100%" }} />
</div>

 1. Attach the DIN-rail mount to the <BrandName /> <ControllerName /> using the provided screw holes.
 2. Carefully attach the <BrandName /> <ControllerName /> to the DIN-rail. Ensure it is securely mounted.
 
> [!NOTE]
>
>     DIN-rail mounts need to be ordered seperately.
>

### Electrical Installation

#### Power Supply

The <BrandName /> <ControllerName />  requires a 12V (2A) DC power supply connected via a 5.5mm jack. The required power adapter is included in the delivery package.

#### Connecting the interfaces
See [the supported device guides](/Controller/Devices) and the [wiring & connectivity guidelines](/Controller/wiring-best-practices/) for the connection of devices.

#### Network Connection

The <BrandName /> <ControllerName />  must always be connected to a wired (RJ45) network interface to ensure reliable communication and functionality. See also the [wiring & connectivity guidelines](/Controller/wiring-best-practices/).

## Model M2S

### Electrical Installation

#### Power Supply

The <BrandName /> <ControllerName /> requires a 12V DC power supply connected to the **DC IN** terminal block (**+** and **GND**).

#### Connecting the interfaces
The <BrandName /> <ControllerName /> has one RS485 port. See [the supported device guides](/Controller/Devices) and the [wiring & connectivity guidelines](/Controller/wiring-best-practices/) for the connection of devices.

#### Network Connection

The <BrandName /> <ControllerName /> must always be connected to a wired (RJ45) network interface through its **LAN** port to ensure reliable communication and functionality. See also the [wiring & connectivity guidelines](/Controller/wiring-best-practices/).


# Installation checklist


import { BrandName, ControllerName, InsightsLink } from '@site/src/components/customFields';
import { ChecklistDecoration } from '@site/src/components/ChecklistDecoration';

# <BrandName /> <ControllerName /> installation checklist

Use this checklist with the customer before the site visit. It helps identify account, network, device, and cabling issues before the installer arrives. Complete sections 1 through 6 in advance and use section 7 during commissioning.

<ChecklistDecoration
  ariaLabel="Checklist overview"
  eyebrow="Before the site visit"
  title="Prepare once. Commission smoothly."
  description="Seven practical checks for a controller that is ready to install."
/>

> [!IMPORTANT]
> Items marked **Belgium only** apply to installations using a Fluvius digital meter. Always check the latest model-specific documentation before the site visit.

## 1. Account and licence

- [ ] The installer has an active installer account in <InsightsLink />, or the organisation owner has already registered one.
- [ ] The [controller licence](/Controller/license/) has been purchased and is available.
  - Licences can be purchased in bulk and assigned to a controller serial number after installation.
- [ ] The controller serial number and verification code are available so the controller can be claimed in <InsightsLink />.

## 2. Site and devices

- [ ] The controller model has been confirmed: SmartgridOne Pro (EDS), SmartgridOne Light (M1S) or SmartgridOne Home (M2S).
  - Wiring and mounting requirements differ by model. Check the [specifications](/Controller/specifications/) and [installation instructions](/Controller/installation/).
- [ ] The required cabling has been determined for every connected device.
  - See the [network requirements](/Controller/network-configuration/) and [wiring and connectivity guidelines](/Controller/wiring-best-practices/).
- [ ] Every inverter, battery, EV charger, heat pump, meter, or other device to be connected appears in the list of [supported device integrations](/Controller/Devices).
- [ ] A working, supported grid meter is available, such as a P1 meter, A1 meter, or another supported grid measurement.
  - For P1 or A1, plan a direct connection to the digital meter.
- [ ] **Belgium only:** the P1 user port of the digital meter has been activated through [Mijn Fluvius](https://mijn.fluvius.be/poortbeheer/).
  - Measurements may take several hours to appear after activation, so activate the port in advance.

## 3. Network

- [ ] A fixed, wired internet connection with an RJ45 socket is available at the controller mounting location.
  - A wired connection is the required and recommended connection for the controller.
- [ ] The network cable has been tested with a laptop to confirm that it provides internet access before connecting it to the controller.
- [ ] If a 5G router is used, its subscription provides at least 5 GB per month, plus 1 GB for every device above five devices.
  - A data-saving mode is available to reduce usage where necessary.
- [ ] CAT5e cable or better is available.
  - Use shielded cable in commercial or industrial environments.
  - Keep each Ethernet run at or below 100 m; use a network switch or repeater for longer distances.
- [ ] The controller and all communicating devices are on the same subnet.
  - For example, `192.168.1.10` and `192.168.1.25` are on the same `192.168.1.x` subnet. A device on `192.168.200.x` cannot normally communicate with a controller on `192.168.1.x`.
- [ ] The building owner or network administrator has confirmed whether fixed IP addresses are required.
  - DHCP is the default and recommended configuration. Use a fixed IP address only when unavoidable and record the assigned address.
- [ ] The outbound firewall rules allow the required connections:
  - TCP 80 and 443 for general internet communication.
  - TCP 1194, or TCP 1192 / 35000-40000, for updates, diagnostics, and remote support.
  - TCP 1883 and 8883 for MQTT when live external control signals are used.
  - UDP 123 for NTP time synchronisation.
- [ ] The customer's IT team knows that no inbound ports or port forwarding are required.
  - Port forwarding is unnecessary and creates a security risk.
- [ ] If the customer network uses a domain allowlist, `*.eniris.be`, `*.eniris.io`, and `*.eniris.com` have been allowed.
- [ ] It has been decided whether the installation will use a dedicated VLAN.
  - A VLAN is optional. All devices that communicate with the controller must use the same VLAN.
- [ ] If Ethernet cabling is unavailable, powerline adapters have been considered and the relevant power sockets have been checked for compatibility.
  - Powerline adapters generally need sockets on the same electrical phase.

For the complete and most recent port and domain requirements, see [Advanced network settings](/Controller/network-configuration/).

## 4. RS485 wiring, when applicable

- [ ] Shielded twisted-pair cable is used, with one pair for RS485 A and B and a characteristic impedance of 100-120 ohm.
- [ ] Devices are wired in a daisy chain.
  - Do not use a star topology and do not connect the same bus to multiple controller ports.
- [ ] Every device on the bus has a unique address.
  - Start with low addresses so devices can be discovered more quickly.
- [ ] Termination and biasing have been configured for the controller model and bus topology.
  - Use 120 ohm termination at the ends of the daisy chain. Some controller models provide configurable termination through DIP switches; other models require external termination resistors.
- [ ] The cable shield is grounded at one end only, using the electrical earth of the installation rather than signal ground.
- [ ] Approximately five devices or fewer are planned per RS485 bus for optimal performance.
  - The absolute maximum is 20 supported unit-load devices. Use an [RS485 expansion accessory](/Controller/Accessories) or additional available buses when more capacity is required.

See the [RS485 wiring guidelines](/Controller/wiring-best-practices/#rs485) for model-specific wiring, termination, and biasing instructions.

## 5. Power and mounting

- [ ] The mounting location has been selected for wall or DIN-rail mounting, depending on the controller model, and is accessible for power and network cabling.
- [ ] A power socket is within reach of the mounting location.
  - Eniris supplies the AC wall adapter as standard; the customer only needs to provide a suitable socket.
- [ ] The accessories included in the order have been checked.
  - A P1-to-USB cable, DIN-rail kit, and RS485-to-USB adapter are not always included as standard.
- [ ] The power circuit and socket are externally protected by a miniature circuit breaker (MCB) and residual-current circuit breaker (RCCB) in accordance with local regulations.
- [ ] The mounting location meets the environmental requirements.
  - Do not install the controller outdoors, in direct sunlight, near flammable or explosive materials, gas pipes, radiators, or unventilated lead-acid batteries.
  - Do not install it in a damp, flood-prone, or vibration-prone location.
- [ ] The controller will not be mounted on its side and at least 1 cm of clearance is available around it.
- [ ] The controller enclosure will not be intentionally connected to electrical earth.
  - This does not affect the separate RS485 cable-shield grounding requirement in section 4.
- [ ] Strain relief is provided wherever cables may be exposed to mechanical stress.

Review the [safety, maintenance, and legal notices](/Controller/safety-maintenance/) before installation.

## 6. Prepare the controller

- [ ] Power the controller and leave it connected for at least 10 minutes so it can download the latest software updates.
- [ ] [Claim the controller](/Controller/quick-start/#3-install-and-commission) in <InsightsLink />.
- [ ] Complete the initial configuration wizard and enter the essential installation information.
- [ ] The installer knows how to contact Eniris Support.
  - Create a ticket first at [eniris.com/support](https://eniris.com/support).
  - Telephone support is available at +32 9 377 12 58 after a ticket has been created.

## 7. Installation day and commissioning

- [ ] Connect and configure the devices through the commissioning wizard.
- [ ] A stable internet connection is available throughout commissioning.
  - The connection is required for automatic firmware updates and allows Eniris Support to assist remotely when necessary.
- [ ] The end user's email address is available so they can be added as a user in <InsightsLink /> after installation.

> [!NOTE]
> This checklist is based on the official Eniris SmartgridOne Controller documentation. Always review the latest documentation for model-specific changes before visiting the site.


# License


import { BrandName, ControllerName } from '@site/src/components/customFields';
import ClickableImage from '@/components/ClickableImage';

# How to activate your <ControllerName /> license

> [!NOTE]
> You can order the hardware without a license, and only purchase the software seperately (using our price calculator/order form) when the hardware is put into service.<br/><br />
> You have 60 days to assign the license to an active EMS. After that, the EMS may no longer operate correctly without a license.<br/><br />
> Licenses can only be purchase by <b>installers or wholesalers.</b> End customers are not able to buy licenses directly from us.

### 1. Configure

Use the [Webshop](https://webshop.eniris.com/) to configure both your hardware and software components.

### 2. Place the Order

Once the order is placed with software included, your license code is generated instantly.

### 3. Receive License Code & Invoice

- The license code will be sent to your email immedately after the order is placed.
- The invoice will be created and sent to your email immedately after the order is placed.

### 4. Link the License to your <ControllerName />

Go to the settings in the app and scroll down to **"Licenses"**.

<ClickableImage src="/img/eniris/insights-settings.png" alt="Insights settings" maxWidth="250px" />

Use the **license code** you received by email and enter it to claim the license.

Once the license is claimed, it will appear in the **claimed license overview**, where you can see:

- All claimed license keys
- The **activation date**
- The **deactivation date**
- If the license is currently active or not

## Q&A

### Can I purchase residential or business licenses without them being liked in advance to a specific EMS?

Yes, you can purchase licenses without linking them to a specific EMS serial number. After the EMS has been installed, the installer can then select and assign a license to sthat EMS. This allows you to buy licenses in bulk and activate them at a later stage.

# Network


import { BrandName, ControllerName, CustomerName, InsightsName, InsightsUrl } from '@site/src/components/customFields';
import PdfLink from '@site/src/components/PdfLink';

# Advanced network settings

## Data usage
> [!TIP]
> See [Data usage](/Controller/Configuration%20from%20A%20to%20Z/11-Extra-Information/data-usage/) for more information about the data usage of the <BrandName /> <ControllerName />.
>
> For troubleshooting high data usage, see also [Troubleshooting - Data usage](/Controller/Troubleshooting/data-usage/)

## Wiring
See [wiring & connectivity guidelines](/Controller/wiring-best-practices/) for wiring the Ethernet network.

## Security policy
Security policy: <PdfLink url="/docs/eniris/Security-Policy-Statement.pdf"/>.

## Firewall

### Network ports for outbound connections
> [!TIP]
> Most home and small business networks allow all outbound connections by default. You do not have to do anything in this case.

The following ports are used for **outbound connections** from the <BrandName /> <ControllerName />. Which ports are required depends on the features in use; the remote service connection is optional for normal operation.

- TCP port 80 & 443: General Internet connection port. Without this port, the <BrandName /> <ControllerName /> cannot function. Some monitored & controlled devices use port 80 locally for communication, but this port is not generally used for internet communication.
- TCP port 1194: Remote service connection for remote commissioning, diagnostic services and support. The <BrandName /> <ControllerName /> can operate without this connection, but remote access through it will be unavailable. Enabling it is recommended when remote service is needed. You can change this port in the <BrandName /> <ControllerName /> configuration to TCP port 1192 or any TCP port in the range 35000 to 40000 if needed. Allow the configured port; opening every alternative port is not necessary.
- UDP port 1193: VPN connection where this port is used. Port 1193 uses **UDP, not TCP**. Allow it only when the VPN connection in use requires it; it is not a separate requirement for normal customer operation.
- TCP port 1883 and 8883: Used for MQTT; required in case the <BrandName /> <ControllerName /> must be able to receive live control signals (e.g. when coupled to the imbalance / FCR energy markets!)
- UDP port 123: NTP Port (Clock). Without this port, the <BrandName /> <ControllerName /> cannot update its internal clock. This is important for proper communication.

### Network ports for inbound connections
The <BrandName /> <ControllerName /> does not require opening any network ports for inbound connections.

> [!WARNING]
> It is strongly discouraged and NOT necessary to configure your firewall to port forward or allow incoming TCP and UDP connections on the listed ports above! This is a serious security risk.

### Domain whitelist
To avoid connectivity issues after future updates, it is **recommended to whitelist all the eniris.be, eniris.io and eniris.com domains** with a wildcard:
- ***.eniris.be**
- ***.eniris.io**
- ***.eniris.com**
- **a2j3w1vc0ecyne-ats.iot.us-east-1.amazonaws.com** (Only when using Yuso) 

The following <CustomerName /> domains are used by the <BrandName /> <ControllerName />, depending on the enabled features:
- api.eniris.be - (telemetry & energy measurements) - TCP port 443: 
- authentication.eniris.be - (authentication) - TCP port 443
- public-health.eniris.be - (device health monitoring system) - TCP port 443
- mqtt.eniris.be - (MQTT) - TCP ports 1883 & 8883
- neoregistry.eniris.be - (device update system) - TCP port 443
- neodata-ingress.eniris.be - (data ingress api) - TCP port 443
- driver-store.eniris.com - (device driver store) - TCP port 443
- vpn.eniris.be - (optional remote service / VPN) - TCP ports 1194 (default), 1192 or a configured port in the range 35000-40000; UDP port 1193 where used. Match the firewall rule to the protocol and port of the connection in use.
- ntp.eniris.be - (clock synchronization) - UDP port 123 

> [!NOTE] Legacy Mender service
> `mender.eniris.be` and `public-mender.eniris.be` refer to the outdated Mender update service and are not required for current customer installations. Mender is shielded from the public Internet, so it is expected that it cannot be reached from an external network. This alone does not indicate a fault in the customer's firewall or controller. Existing outbound allowlist entries for these legacy endpoints do not need to be removed solely because the service is unreachable; do not add firewall openings to make it reachable.

### Checking VPN connectivity

A TCP port scan cannot determine whether **UDP port 1193** is reachable. A closed TCP port 1193 is therefore not evidence that the VPN is blocked. Check the protocol and port actually used by the VPN connection, test that connection and inspect the firewall logs. A UDP probe without a reply is inconclusive on its own.

The optional VPN connection enables remote service. Its absence does not by itself prevent normal customer operation; the other network requirements for the features in use still apply. No inbound port forwarding is needed.

## Fixed IP addresses
The <BrandName /> <ControllerName /> is by default configured to use DHCP. You can change this to a fixed IP address in the 'Settings' tab of the commissioning interface.

> [!TIP] Only configure a fixed IP address in the <BrandName /> <ControllerName /> if you have no other choice. **It is recommended to always use DHCP, and configure your router to always assign the same IP address to the <BrandName /> <ControllerName /> instead!**

> [!WARNING] **Write down the IP address you configure. You will need this if the <BrandName /> <ControllerName /> would become inaccessible after changing the IP address!**

> [!NOTE] Lost access to the commissioning interface
> If you lose access to the commissioning interface after setting a fixed IP address, then check out [the troubleshooting section](/Controller/Troubleshooting/device-communication/#access-to-the-commissioning-interface).

## VLAN
> [!TIP]
> As an optional security measure, the <BrandName /> <ControllerName />  can be placed within a dedicated VLAN. When implementing this configuration, ensure that all devices requiring communication with the controller are assigned to the same VLAN.


# Quick Start


import { BrandName, ControllerName } from '@site/src/components/customFields';
import InsightsLink from '@site/src/components/InsightsLink';
import Details from '@theme/Details';
import {
  QuickStartAccessoryCard,
  QuickStartAccessoryGrid,
  QuickStartHero,
  QuickStartModelCard,
  QuickStartModelGrid,
  QuickStartRequirements,
  QuickStartStep,
  QuickStartSteps,
  QuickStartWebshopLink,
} from '@site/src/components/QuickStartGuide';

<QuickStartHero
  eyebrow="Controller setup"
  title="Quick Start"
  description="Go from unboxing to a working site in three clear stages. Check your hardware, connect the essentials, and complete commissioning online."
  essentialsLabel="Quick start essentials"
  networkLabel="Wired network"
  accountLabel="Installer account"
  measurementLabel="Grid measurement"
/>

## 1. Check your box

Start with the controller model on your order. The current Pro and Light models do not use exactly the same accessories.

<QuickStartModelGrid>
  <QuickStartModelCard
    title="SmartgridOne Pro"
    model="Current EDS model"
    image="/img/controller/quick-start/controller-pro.png"
    imageWidth={236}
    imageHeight={223}
    included={['Controller', 'AC power adapter', 'DIN-rail clip']}
    includedLabel="In the box"
    note="Use the optional wall-mount bracket when no DIN rail is available."
  />
  <QuickStartModelCard
    title="SmartgridOne Light"
    model="M1S model"
    image="/img/controller/quick-start/controller-light.png"
    imageWidth={508}
    imageHeight={352}
    included={['Controller', 'AC power adapter']}
    includedLabel="In the box"
    note="Add an RS485-to-USB converter when you need a direct RS485 connection."
  />
</QuickStartModelGrid>

> [!NOTE]
> Package contents can differ for older controller models and order-specific bundles. Compare the delivered hardware with your order confirmation before travelling to site.

## Choose the accessories you actually need

Accessories are not required for every installation. Match them to the meter, communication method, controller model, and mounting location.

<QuickStartAccessoryGrid>
  <QuickStartAccessoryCard
    title="P1-port / A1-port cable"
    badge="Meter connection"
    image="/img/controller/quick-start/p1-a1-cable.png"
    imageWidth={245}
    imageHeight={245}
    description="Connect the controller directly to the user port of a compatible smart or digital meter."
    compatibility="SmartgridOne Pro and Light"
    href="/Controller/Accessories/p1-cable/"
    linkLabel="Read the accessory guide"
  />
  <QuickStartAccessoryCard
    title="RS485-to-USB converter"
    badge="Light only"
    image="/img/controller/quick-start/rs485-usb-converter.png"
    imageWidth={631}
    imageHeight={477}
    description="Give a SmartgridOne Light a direct RS485 interface for nearby Modbus RTU devices."
    compatibility="SmartgridOne Light"
    href="/Controller/Accessories/rs485-usb/"
    linkLabel="Read the accessory guide"
  />
  <QuickStartAccessoryCard
    title="RS485-to-TCP/IP converter"
    badge="Network extension"
    image="/img/controller/quick-start/rs485-tcp-converter.png"
    imageWidth={512}
    imageHeight={316}
    description="Bring an RS485 device onto the local network when a direct serial cable is impractical."
    compatibility="SmartgridOne Pro and Light"
    href="/Controller/Accessories/rs485-ethernet/"
    linkLabel="Read the accessory guide"
  />
  <QuickStartAccessoryCard
    title="Wall-mount bracket"
    badge="Pro EDS only"
    image="/img/controller/quick-start/pro-eds-wall-mount.png"
    imageWidth={695}
    imageHeight={576}
    description="Mount the current Pro EDS model to a wall when the standard DIN-rail clip cannot be used."
    compatibility="SmartgridOne Pro, model EDS"
  />
</QuickStartAccessoryGrid>

<QuickStartWebshopLink
  title="Missing an accessory?"
  description="Order compatible SmartgridOne accessories from Eniris."
  linkLabel="Open the webshop"
/>

## 2. Prepare the site

Complete these checks before mounting or powering the controller.

<QuickStartRequirements
  requirements={[
    { title: "Supported devices", text: "Confirm that every inverter, meter, battery, charger, or heat pump is supported." },
    { title: "Installer access", text: "Use an installer account that can claim and configure the controller." },
    { title: "Wired internet", text: "Prepare a live Ethernet connection with DHCP and the required outbound ports." },
    { title: "Grid measurement", text: "Provide a supported grid meter or an active P1/A1 user port." },
  ]}
/>

Use the [supported device guides](/Controller/Devices) to confirm the required interface, wiring, and device settings. To claim and configure the controller, you also need an installer account for <InsightsLink />.

> [!NOTE]
> For accurate grid measurements, connect directly to the P1/A1 user port of the digital meter whenever possible. An energy meter already connected to another device, such as a hybrid inverter, generally cannot also be used by the controller.

> [!WARNING]
> **Installations in Belgium:** the P1 user port of a Fluvius digital meter is disabled by default. Activate it through [Mijn Fluvius](https://mijn.fluvius.be/poortbeheer/). It can take several hours after activation before measurements become available.

## 3. Install and commission

Work through these stages in order. Do not start configuration until the controller has power, a wired network connection, and internet access.

<QuickStartSteps>
  <QuickStartStep
    number={1}
    stepLabel="Step"
    title="Install the hardware"
    summary="Mount the controller and connect every physical interface before applying power."
  >

  - Mount the <BrandName /> <ControllerName /> securely in its intended location.
  - Connect the required meter, device, and accessory cables to the correct interfaces.
  - Connect the controller to the local network with an Ethernet cable.
  - Connect the supplied power adapter and wait for the controller to start.

  </QuickStartStep>

  <QuickStartStep
    number={2}
    stepLabel="Step"
    title="Claim and configure"
    summary="Add the controller to your installer account and complete the built-in commissioning wizard."
  >

  - Sign in to <InsightsLink /> and select **Add controller**.
  - Enter the serial number and verification code printed on the controller, then claim it.
  - Open **Settings**, select the new controller under **Current Site**, and go to **Controller Configuration**.
  - Follow the quick-start wizard in the controller interface to add and test the connected devices.

  </QuickStartStep>

  <QuickStartStep
    number={3}
    stepLabel="Step"
    title="Hand over to the end user"
    summary="Give the customer access only after commissioning and functional checks are complete."
  >

  - Open **User Management** in <InsightsLink />.
  - Search for the installed controller by serial number.
  - Add the end user's email address and confirm that the invitation is sent to the right person.

  </QuickStartStep>
</QuickStartSteps>

## Troubleshooting

<Details summary='The controller appears offline in "Controller Configuration"'>

- Test the Ethernet cable with a computer and confirm that it provides internet access.
- Scan the local network for the <BrandName /> <ControllerName /> with an IP scanner.
- Ask the building owner or network administrator whether fixed IP addresses are required. The controller uses DHCP by default. Connect it to a DHCP network first before changing it to a fixed address.
- Confirm that [the required outbound network ports are allowed](/Controller/network-configuration#network-ports-for-outbound-connections).

</Details>


# Safety, maintenance and legal notices


import { BrandName, ControllerName, CustomerName, InsightsName, InsightsUrl } from '@site/src/components/customFields';

# Safety, maintenance and legal notices

## Safety & maintenance instructions
- Installation, maintenance & servicing of the <BrandName /> <ControllerName /> must be performed only by qualified personnel per the applicable local regulations. Unauthorized installation and modifications make the manufacturer warranty void.
- Do not use if the enclosure or power supply is broken, cracked, opened, or shows any indication of damage. Please contact your distributor. 
- Do not use cleaning solvents on any part of the <BrandName /> <ControllerName />. Use a clean, dry cloth to remove dust and dirt. 
- Do not open the <BrandName /> <ControllerName />. 
- Take appropriate precautions with electronic medical implants. 
- Use the <BrandName /> <ControllerName /> under the operation parameters and within normal ambient conditions specified in the General specifications. 
- Do not install the <BrandName /> <ControllerName /> outside or in a position that has direct sunlight. 
- The <BrandName /> <ControllerName /> is intended to be installed in vibration free environments.

## Simplified EU declaration of conformity.
Hereby, <CustomerName /> declares that the equipment (<BrandName /> <ControllerName />) is in compliance with Directive 2014/53/EU, Directive 2014/30/EU and Directive 2014/35/EU. The full text of the EU declaration of conformity is available at the following internet address: [open EU declaration of conformity](/Controller/certificates/).

## Safety recommendations
- Follow all the safety and installation instructions carefully.
- Failure to follow instructions may be a safety hazard and/or cause equipment malfunction. 
- Any resulting damage due to disregard or actions contrary to the instructions in this manual is excluded from the product warranty.

## Installation instructions 
- Do not install the <BrandName /> <ControllerName /> outside, in direct sunlight, or near flammable, explosive or combustible materials, chemicals or solvents, gas pipes or steam outlets, radiators, lead acid batteries in an unventilated space, and areas prone to flooding, high humidity and running water. 
- The casing of the <BrandName /> <ControllerName /> may not be connected to the electrical earth of the installation on purpose. 
- The insulation between the <BrandName /> <ControllerName /> and circuits connected to the mains or earth must comply with all requirements for class II insulation (IEC 60364-4-41) 
- Strain reliefs must be used on the cables attached to the <BrandName /> <ControllerName /> where mechanical strain is to be expected. 
- Do not install the <BrandName /> <ControllerName /> sideways. 
- Do not wire the I/O’s while the <BrandName /> <ControllerName /> is on. 
- Leave at least 1cm surrounding space around all sides of the <BrandName /> <ControllerName />.

## Electrical protection
- The <BrandName /> <ControllerName />'s power supply must be electrically protected by installing externally a Miniature Circuit Breaker (MCB) and a Residual Current Circuit Breaker (RCCB) as required by the local regulations for the wall outlet or circuit that the <BrandName /> <ControllerName />'s power supply is connected to.

## Disposal advice
<div style={{ display: "flex", alignItems: "center", gap: "16px" }}>
    <img
        src="/img/eniris/waste-disposal.png"
        alt="Waste Disposal Symbol"
        style={{ height: "80px", height: "auto", flexShrink: 0 }}
    />
    <span style={{ display: "flex", alignItems: "center" }}>
        In accordance with Directive 2012/19/EC, at the end of its useful life, the <BrandName /> <ControllerName /> should not be disposed of as urban waste. It should be taken to a collection center or to a distributor that provides disposal of special and differentiated waste.
    </span>
</div>



## Limited Warranty
- <CustomerName /> warrants this product against defects in materials and workmanship for a period of 2 years from the date of purchase. 
- During this period, at its discretion, <CustomerName /> will either repair or replace any defective product at no charge to the owner. 
- Replacement products or repaired parts will be guaranteed for only the unexpired portion of the original warranty or six months, whichever is greater. 
- Any defect resulting from any accident, misuse, improper maintenance, or normal wear and tear is not covered by the limited warranty. 
- Subsitution or incorporation of any part by the client will be considered as incorrect usage. 
- Except to the extent permitted by applicable law, the terms of this limited warranty do not exclude, restrict, or modify, and are in addition to the mandatory statutory rights applicable to the sale of the product to you. If you believe your product is defective, contact <CustomerName /> for instructions on where to send or bring it for repair.

## Legal notice
- Any information in this manual may be changed without prior notice and does not represent any obligation on the part of the manufacturer. Images in this manual are for illustration purposed only and might differ from the delivered product.


# Specifications


import { BrandName, ControllerName, CustomerName, InsightsName, InsightsUrl, ModelPro, ModelHome, ModelLite, ModelConnect } from '@site/src/components/customFields';
import Details from '@theme/Details';
import ClickableImage from '@site/src/components/ClickableImage';
import Tabs from '@theme/Tabs';
import TabItem from '@theme/TabItem';

# Specifications

> [!TIP]
>   Additional I/O's
>   All <BrandName /> models are extendible with additionaly I/O's through the accessories. See [accessories](/Controller/accessories) for more information.

<Tabs
  defaultValue="om1"
  values={[
  { label: 'Model OM1', value: 'om1' },
  { label: 'Model EDS', value: 'eds' },
  { label: 'Model M1S', value: 'm1s' },
  { label: 'Model ULT', value: 'ult' },
]}
>
  <TabItem value="om1">
    ## <BrandName /> <ModelPro /> (Model OM1)

    <ClickableImage src="/img/eniris/model-OM1.webp" srcWhitelabeled="/img/whitelabeled/ModelOM1.png" alt="Model OM1" maxWidth="350px" border="" />

    | Property               | Value                                                                                                                                                                                                                                                |
    | :--------------------- | :--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
    | Casing material        | Aluminum                                                                                                                                                                                                                                             |
    | Dimensions             | 135mm x 125mm x 50mm                                                                                                                                                                                                                                 |
    | Weight                 | 615g                                                                                                                                                                                                                                                 |
    | Ambient temperature    | -10°C to +60°C                                                                                                                                                                                                                                       |
    | Humidity               | 5% - 95% non-condensing                                                                                                                                                                                                                              |
    | Power supply           | 12Vdc, 2A via 230Vac adaptor                                                                                                                                                                                                                         |
    | Interfaces             | <ul style={{ textAlign: "left", paddingLeft: "20px" }}><li>1x RS485</li><li>2x Digital input (5-50Vdc) suitable for S0 pulse counting</li><li>1x 12Vdc out, max. 60mA</li><li>2x Relay (max 1A, 50Vdc/30Vac)</li><li>RJ45 gigabit ethernet</li></ul> |
    | Supported device types | <ul style={{ textAlign: "left", paddingLeft: "20px" }}><li>EV charging stations</li><li>Energy meters</li><li>Battery systems</li><li>PV inverters</li><li>Heat pumps and Switched loads</li></ul>                                                   |
    | Appliance class        | IEC 61140 class III appliance                                                                                                                                                                                                                        |
    | Pollution degree       | IEC 60664 pollution degree 3                                                                                                                                                                                                                         |
    | Altitude               | 0 – 2000m                                                                                                                                                                                                                                            |
    | IP rating              | IP2X                                                                                                                                                                                                                                                 |
  </TabItem>

  <TabItem value="eds">
    ## <BrandName /> <ModelPro /> (Model EDS)

    <ClickableImage src="/img/eniris/model-EDS.png" srcWhitelabeled="/img/whitelabeled/ModelM1.png" alt="Model EDS" maxWidth="350px" border="" />

    | Property               | Value                                                                                                                                                                                              |
    | :--------------------- | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
    | Casing material        | Aluminum                                                                                                                                                                                           |
    | Dimensions             | 102mm x 73mm x 35.2mm (DIN-rail bracket and antenna not included)                                                                                                                                  |
    | Weight                 | 500g                                                                                                                                                                                               |
    | Ambient temperature    | -25°C to +60°C                                                                                                                                                                                     |
    | Humidity               | 5% - 95% non-condensing                                                                                                                                                                            |
    | Power supply           | 12V/2A power adaptor                                                                                                                                                                               |
    | Interfaces             | <ul style={{ textAlign: "left", paddingLeft: "20px" }}><li>4x RS485</li><li>2x USB port</li><li>RJ45 gigabit ethernet</li></ul>                                                                    |
    | Supported device types | <ul style={{ textAlign: "left", paddingLeft: "20px" }}><li>EV charging stations</li><li>Energy meters</li><li>Battery systems</li><li>PV inverters</li><li>Heat pumps and Switched loads</li></ul> |
    | Appliance class        | IEC 61140 class III appliance                                                                                                                                                                      |
    | Pollution degree       | IEC 60664 pollution degree 3                                                                                                                                                                       |
    | Altitude               | 0 – 2500m                                                                                                                                                                                          |
    | IP rating              | IP3X                                                                                                                                                                                               |
  </TabItem>

  <TabItem value="m1s">
    ## <BrandName /> <ModelLite /> (Model M1S)

    <ClickableImage src="/img/eniris/model-M1S.png" alt="Model M1S" maxWidth="500px" border="" />

    | Property               | Value                                                                                                                                                                                              |
    | :--------------------- | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
    | Casing material        | Plastic                                                                                                                                                                                            |
    | Dimensions             | 120mm x 90mm x 30mm                                                                                                                                                                                |
    | Weight                 | 150g                                                                                                                                                                                               |
    | Ambient temperature    | -20°C to +70°C                                                                                                                                                                                     |
    | Humidity               | 10% - 90% non-condensing                                                                                                                                                                           |
    | Power supply           | 5V/3A power adaptor                                                                                                                                                                                |
    | Interfaces             | <ul style={{ textAlign: "left", paddingLeft: "20px" }}><li>2x USB port</li><li>RJ45 gigabit ethernet</li></ul>                                                                                     |
    | Supported device types | <ul style={{ textAlign: "left", paddingLeft: "20px" }}><li>EV charging stations</li><li>Energy meters</li><li>Battery systems</li><li>PV inverters</li><li>Heat pumps and Switched loads</li></ul> |
    | Appliance class        | IEC 61140 class III appliance                                                                                                                                                                      |
    | Pollution degree       | IEC 60664 pollution degree 3                                                                                                                                                                       |
    | Altitude               | 0 – 2500m                                                                                                                                                                                          |
    | IP rating              | IP3X                                                                                                                                                                                               |
  </TabItem>

  <TabItem value="ult">
    ## <BrandName /> Ultra (Model ULT)

    The Ultra brings battery storage, PV inverters, EV charging stations and energy meters together in one local energy system for commercial, industrial and utility sites. It coordinates connected assets and connects the site to external energy platforms.

    <ClickableImage src="/api/media/controller/specifications/placeholder-ultra.png" alt="Ultra controller (Model ULT)" maxWidth="350px" border="" />

    ### Computing platform

    | Property | Value |
    | :--- | :--- |
    | Processor | Intel Core i3-1115G4E, 2 cores; 2.2 GHz, turbo up to 3.9 GHz |
    | Memory | 8 GB DDR4-3200 |
    | Storage interfaces | M.2 2280 NVMe and M.2 2242 SATA. The installed SSD depends on the supplied configuration. |
    | Hardware security and supervision | TPM 2.0; programmable watchdog |

    ### Interfaces

    | Interface | Specification |
    | :--- | :--- |
    | Ethernet | 3 x RJ45: 2 x Gigabit and 1 x 2.5 Gigabit |
    | Serial communication | 4 x RS-232/422/485 via terminal blocks; 2,500 VDC galvanic isolation |
    | Digital inputs | 8 x DI; dry or wet contact; isolated |
    | Digital outputs | 8 x DO; sink type; 5-30 VDC; maximum 500 mA per channel |
    | USB | 3 x USB 3.2 Gen 2 and 1 x USB 2.0 |
    | Display outputs | 2 x DisplayPort |

    > [!IMPORTANT]
    > **Digital outputs are not relay contacts.** The Ultra's sink-type outputs switch their terminal to digital ground. An external 5-30 VDC supply and a load in series are required. Do not exceed 500 mA per channel.

    ### Power, enclosure and environment

    | Property | Value |
    | :--- | :--- |
    | Power input | 12-36 VDC via a 2-pin terminal block; accepts 24 VDC |
    | Power consumption | 31 W typical / 55 W maximum (manufacturer specification for the base unit) |
    | Casing material | Aluminium |
    | Dimensions | 45 x 140 x 200 mm (width x depth x height) |
    | Weight | 1.3 kg |
    | Mounting | Vertical DIN-rail mounting |
    | IP rating | IP20 |
    | Operating ambient temperature | -20 to +60 °C with 0.7 m/s airflow (hardware rating) |
    | Storage temperature | -40 to +85 °C |
    | Relative humidity | 95% RH at 40 °C, non-condensing |
    | Operating altitude | Not specified; manufacturer confirmation is required. |

    ### Installation and cooling

    - Mount the unit vertically and keep its ventilation openings clear.
    - Allow at least 50 mm of free space around the unit where possible.
    - Select cabinet ventilation and SSD cooling to suit the ambient conditions and system load. The operating-temperature rating above requires 0.7 m/s airflow.

    ### Connected energy assets

    Supported device types include EV charging stations, energy meters, battery systems, PV inverters, heat pumps and switched loads. See [supported devices](/Controller/Devices) for the individual integration guides.
  </TabItem>
</Tabs>


# Status LEDs


import { BrandName, ControllerName, CustomerName, InsightsName, InsightsUrl, ModelPro, ModelHome, ModelLite, ModelConnect } from '@site/src/components/customFields';
import Details from '@theme/Details';
import ClickableImage from '@site/src/components/ClickableImage';
import Tabs from '@theme/Tabs';
import TabItem from '@theme/TabItem';

<Tabs
  defaultValue="om1"
  values={[
    { label: 'Model OM1', value: 'om1' },
    { label: 'Model EDS', value: 'eds' },
    { label: 'Model M1S', value: 'm1s' },
    { label: 'Model M2S', value: 'm2s' },
  ]}
>
  <TabItem value="om1">
    ## <BrandName /> <ModelPro /> (Model OM1)

    <ClickableImage src="/img/eniris/model-OM1.webp" alt="Model OM1" maxWidth="350px" border="" />
> [!WARNING]
>       The status LED is not available on version 1.15.0.9 and earlier.

    | LED Color | Behavior |
    |-----------|----------|
    | Off | The <BrandName /> <ControllerName /> is not powered on |
    | Green / blue | The <BrandName /> <ControllerName /> is booting |
    | Green | The <BrandName /> <ControllerName /> is operating as normal |
    | Purple (heartbeat blinking) | The <BrandName /> <ControllerName /> has no internet |
    | Alternating blue and green (every half second) | A software update is in progress |
    | Red / yellow (blinking) | The reset button is pressed |
    | Red | The reset button has been held for 5 seconds and the factory reset has started, or the <BrandName /> <ControllerName /> is in error state |

  </TabItem>

  <TabItem value="eds">
    ## <BrandName /> <ModelPro /> (Model EDS)

    <ClickableImage src="/img/eniris/model-EDS.png" alt="Model OM1" maxWidth="350px" border="" />

    ### Power LED (Red)
    | Power LED | Behavior |
    |-----------|----------|
    | Off | The <BrandName /> <ControllerName /> is not powered on |
    | On | The <BrandName /> <ControllerName /> is powered on |

    ### Status LED (Green)
    | Status LED | Behavior |
    |-----------|----------|
    | Erratic on/off | The <BrandName /> <ControllerName /> is booting |
    | Continuously on | The <BrandName /> <ControllerName /> is operating as normal |
    | Heartbeat blinking | The <BrandName /> <ControllerName /> has no internet |
    | Slow blinking (on and off, about once per second) | A software update is in progress |
    | Three fast blinks followed by three slow blinks | The <BrandName /> <ControllerName /> is in error state |

  </TabItem>

  <TabItem value="m1s">
    ## <BrandName /> <ModelLite /> (Model M1S)

    <ClickableImage src="/img/eniris/model-M1S.png" alt="Model M1S" maxWidth="500px" border="" />

    The <BrandName /> <ModelLite /> does not have status LEDs.

  </TabItem>

  <TabItem value="m2s">
    ## <BrandName /> <ModelHome /> (Model M2S)

    <ClickableImage src="/api/media/controller/model-m2s/model-M2S-unbranded.webp" alt="Model M2S" maxWidth="350px" border="" />

> [!NOTE]
> The <BrandName /> <ModelHome /> (Model M2S) is supported from software version 2.0.

    The <BrandName /> <ModelHome /> has one multi-colour status LED. Once the software is running, it uses the same colours as the Model OM1.

    | LED Color | Behavior |
    |-----------|----------|
    | Off | The <BrandName /> <ControllerName /> is not powered on |
    | Blue | The <BrandName /> <ControllerName /> is booting |
    | Green | The <BrandName /> <ControllerName /> is operating as normal |
    | Purple (heartbeat blinking) | The <BrandName /> <ControllerName /> has no internet |
    | Alternating blue and green (every half second) | A software update is in progress |
    | Red / yellow (blinking) | The reset button is pressed |
    | Red | The reset button has been held for 5 seconds: release it now to start the factory reset. Red is also shown when the <BrandName /> <ControllerName /> has crashed |

> [!IMPORTANT]
> On the <BrandName /> <ModelHome /> the factory reset starts when you **release** the reset button, not while you hold it. Release the button as soon as the LED turns red. If you release it earlier, nothing is reset. After the reset the <BrandName /> <ControllerName /> reboots: the LED turns blue while it starts and green when it is ready.

  </TabItem>
</Tabs>


# Controllers Toolbox

import { ToolboxGuard } from '@/components/ToolboxGuard';
import ClickableImage from '@/components/ClickableImage';
import { GithubAlert } from '@/components/GithubAlert';

<ToolboxGuard>

# Controllers Toolbox

## Update Controller

1. Go to the Controllers tab in the Toolbox.
2. Click on the view controller updates.
3. Select the controller you want to update.
4. Select the artifact (version) you want to update to.
5. Confirm the deployment.
6. Press the create deployment button.

<ClickableImage 
  src="/img/generic/ControllerUpdate.png" 
  alt="Controller Update" 
  maxWidth="80%" 
/>

## Controller Online

1. Go to the Controllers tab in the Toolbox.
2. Click on the controller you want to view.
3. Click on the ping controller button.

<ClickableImage 
  src="/img/generic/ControllerOffline.png" 
  alt="Controller Online" 
  maxWidth="80%" 
/>

<GithubAlert variant="info" title="When ping fails please check the following:">

- Is the cabling correct?
- Are the ports from the firewall open? [the network guide](/Controller/network-configuration)

</GithubAlert>

</ToolboxGuard>

# Toolbox


import { FolderOverview } from '@/components/FolderOverview';

# Toolbox

<FolderOverview folder="Controller/Toolbox" />


# App & Portal


import { BrandName, ControllerName, CustomerName, InsightsName, InsightsUrl, RegistrationUrl } from '@site/src/components/customFields';
import Details from '@theme/Details';
import Checkbox from '@site/src/components/CheckBox';

# App & Portal

<Details summary="I don't have an account for the app.">
- For end users: ask your installer to give you access to the <BrandName /> <ControllerName />. After he/she gives you access, you will receive an e-mail with login credentials.
- For installers: you can request an account through <RegistrationUrl /> by clicking the 'Register your business' button and following the steps.
</Details>

<Details summary="I cannot login to the app.">
- Reset your password using the "I forgot my password" link in the app login screen.
</Details>

<Details summary="I don't get live data in the app / I don't have data.">
- Check if the <BrandName /> <ControllerName /> is online.
</Details>

<Details summary="There is energy coming from the 'house' icon in the app.">
The 'house' contains the difference between the grid energy meter and the powers of all the devices connected to the <BrandName /> <ControllerName /> - in other words, the remaining power. In most cases this will correspond to the consumption of the other loads in the building. If a battery or solar inverter is not added to the <BrandName /> <ControllerName />, then the <BrandName /> <ControllerName /> will also place it here.

If you have production coming from the 'house', and all batteries and inverters are added to the <BrandName /> <ControllerName />, then check:
- If they are still communicating with the <BrandName /> <ControllerName />
- If there are no energy meters wired in reverse (you can revert the direction in the device settings of the energy meter in the <BrandName /> <ControllerName /> if needed. See also [Reversing energy meter readings](/Controller/Configuration%20from%20A%20to%20Z/11-Extra-Information/reversing-energy-meter/).)
- If there are inverters that have no communication possibilities, you can as an alternative add an energy meter that measures those inverters and mark in the device settings of the energy meter that it is used to measure energy production. Its power will then also be placed under the 'solar panel' icon in the app.
</Details>

<Details summary="My solar production is counted double.">
- Check if you have an energy meter that measures your solar panels. In the groups, it should be indicated that it measures the solar panels. See also [Assigning an energy meter to a group or device](/Controller/Configuration%20from%20A%20to%20Z/7-grouping-devices/#assigning-an-energy-meter-to-a-group-or-device)
</Details>

<Details summary="The app shows import from the grid while there is actually export, and vice versa export when there is actually import.">
- This can happen if the grid energy meter is wired in reverse. You can tell the <BrandName /> <ControllerName /> that the meter is connected in reverse through the device settings in the "Devices tab" of the commissioning interface. See also [Reversing energy meter readings](/Controller/Configuration%20from%20A%20to%20Z/11-Extra-Information/reversing-energy-meter/).
- CAUTION: Double check if your grid meter readings are effectively reversed. If they are not, and you faultly reverse them in the settings of the energy meter, this can make the control system unstable.
</Details>

<Details summary="The energy measurements from the EMS and the manufacturers portal are different for my inverter / device.">
The manufacturer may use a different method for registering the energy production or consumption of a device. In many cases accurate energy readings are not available, in which case the <BrandName /> <ControllerName /> will base the energy measurements on the power values it reads out. In any case, this does not affect the performance of the control algorithms of the <BrandName /> <ControllerName />.
</Details>

# Configuration


import { BrandName, ControllerName, CustomerName, InsightsName, InsightsUrl } from '@site/src/components/customFields';
import Details from '@theme/Details';

# Troubleshooting during configuration

## Address / location
<Details summary="When validating the address, the controller doesn't find it.">
Try using the name of a nearby town or city instead. The address is only used to retrieve weather forecasts, and a nearby population center will work fine.
</Details>



# Control issues


import { BrandName, ControllerName, CustomerName, InsightsName, InsightsUrl } from '@site/src/components/customFields';
import Details from '@theme/Details';
import Checkbox from '@site/src/components/CheckBox';

# Control problems

## Always check this first

> [!TIP]
> You can check off the boxes. 

<Checkbox label="Is the controlled device online?" />
<Checkbox label="Is the controlled device operating correctly on its own? Check for fault and error messages on the device." />
<Checkbox label="Is the grid energy meter still connected to the EMS?" />
<Checkbox label="Is the internet connection ok?" />
<Checkbox label="Is the local control mode set correctly? Is it enabled?" />
<Checkbox label="Are there no external control signals active? (they take priority over the local control modes)" />
<Checkbox label="Are the device settings correct (e.g. nominal power not too high, battery capacity correct)?" />
<Checkbox label="Are the grid limits not too restrictive?" />
<Checkbox label="Is remote control enabled in the device configuration?" />
<Checkbox label="For cost optimization: are the price parameters correct?" />
<Checkbox label="For self consumption, especially in winter: is there recent excess PV production?" /> 
<Checkbox label="For batteries: is the minimum state of charge not too high?" />

&nbsp;
> [!NOTE]
> See also "[Setting local control modes](/Controller/Configuration%20from%20A%20to%20Z/8-local-control-modes/setting-control-modes/)" and "[Device configuration](/Controller/Devices)".

## External control integrations / external signals
<Details summary="The EMS doesn't follow the external control signal.">
- Check if the external control signal is enabled.
- Check if you have a valid contract with the provider of the external signal, and if you entered the right information during the configuration of the external signal.
- Check if the device is configured to allow remote control.
- Check if the device has no active faults/errors.
- Check if the device allows 'exporting to the grid' in its configuration.
</Details>

## Local control
<Details summary="The EMS doesn't follow the local control mode.">
- Check if there is an external control signal enabled (Frank Energie, Yuso, ...). External control signals take priority over local control modes.
- Check if the device is configured to allow remote control.
- Check if the device has no active faults/errors.
- Check if the device allows 'exporting to the grid' in its configuration.
</Details>

## Grid limits / circuit breaker
<Details summary='My circuit breaker trips'>
- Check if solar production is also controlled. Uncontrolled solar production can be prone to heavy power fluctuations (up to 80%) when clouds fly over. Controlling the solar production prevents that the solar production rises too fast and beyond the limits.
- If it is not possible to control the solar production, set a safe production ramp up rate of 25%/min.
</Details>

<Details summary='I have an export power limit of 100kW, but my solar production is always limited to 90kW.'>
By default, a safety factor of 90% is applied, meaning that the <BrandName /> <ControllerName /> controls everything, including solar production, to be within 90% of the set grid limits. You can change this in the "Advanced Settings" menu (all the way to the bottom of the "Settings" menu).
This safety factor helps safeguarding against exceeding the limits, by leaving some room for the controller to react to power fluctuations (e.g. clouds flying over can make the PV production dip by as much as 80%). If you have a combination of consumers and producers, then it is recommended to leave this to 90%. Only set this to 100% if you are sure that there is no risk of tripping breakers or big fluctuations leading to exceeding the limits.
</Details>

## Batteries
<Details summary='I use cost optimization and my battery (dis)charges at the wrong moments.'>
- Check if the local battery control mode is effectively set to cost optimization.
- Check if there are no external control signals enabled (Frank Energie, Yuso, ...). External control signals take priority over local control modes.
- Check if the device is configured to allow remote control.
- Check if the device has no active faults/errors.
- Check if [the price settings are correct](/Controller/Configuration%20from%20A%20to%20Z/8-local-control-modes/complete-explanation#pricing-parameters).
- [Reset the prediction model](/Controller/Configuration%20from%20A%20to%20Z/8-local-control-modes/complete-explanation#risk-profile).
</Details>

<Details summary='I use cost optimization and my battery did something else than what was in the planning earlier.'>
- The planning of the <BrandName /> <ControllerName /> is updated continuously and adapts to changing situations. It is possible that the <BrandName /> <ControllerName /> estimates that something that was a good action before is no longer a good action later on.
- Check if the local battery control mode is effectively set to cost optimization.
- Check if there are no external control signals enabled (Frank Energie, Yuso, ...). External control signals take priority over local control modes.
- Check if the device is configured to allow remote control.
- Check if [the price settings are correct](/Controller/Configuration%20from%20A%20to%20Z/8-local-control-modes/complete-explanation#pricing-parameters).
- [Reset the prediction model](/Controller/Configuration%20from%20A%20to%20Z/8-local-control-modes/complete-explanation#risk-profile).
- Disable "allow energy trading".
</Details>

<Details summary='I use cost optimization and my battery is not doing anything.'>
- The planning of the <BrandName /> <ControllerName /> is updated continuously and adapts to changing situations. It is possible that the <BrandName /> <ControllerName /> estimates that something that was a good action before is no longer a good action later on.
- Check if the local battery control mode is effectively set to cost optimization.
- Check if there are no external control signals enabled (Frank Energie, Yuso, ...). External control signals take priority over local control modes.
- Check if the device is configured to allow remote control.
- Check if [the price settings are correct](/Controller/Configuration%20from%20A%20to%20Z/8-local-control-modes/complete-explanation#pricing-parameters).
- Check if the price spread (difference between the maximum price and minimum price of the day) is too low. If yes, you may want to change Settings by decreasing the value of _Minimum price difference for storage when control mode is "Minimize costs"_. Do not set this value lower than 0.02€/kWh.
</Details>

<Details summary='I use self consumption and the grid power consumption is not exactly zero.'>
This can happen because of several factors:
- Many battery inverters have a limited accuracy, typically 1%. Some inverters perform worse if their power is very low.
- The <BrandName /> <ControllerName /> has to track the grid power and continuously control it towards zero. It takes some time before batteries react on changing control signals, which in case of fast fluctuating energy consumption may result in a grid power close to zero, but not exactly zero, or fluctuating slightly around zero.

A combined accuracy of 2% of the biggest device's nominal power may typically be expected.
</Details>

<Details summary='The power of my battery oscillates up and down.'>
- Check if the energy meter is not installed in reverse. You can virtually invert the direction of the energy meter from the device settings in the "Devices tab" of the commissioning interface. See also [Reversing energy meter readings](/Controller/Configuration%20from%20A%20to%20Z/11-Extra-Information/reversing-energy-meter/).
- The measurements of the grid meter and the battery are not synchronous. This can happen if one of the two is slow in communication or updating its measurements.
{/* TODO: Add a link to the advanced settings to change the settling check. */}
</Details>

<Details summary='My inverter has a nominal power of 20kW, but my batteries never (dis)charge faster than 10kW.'>
There are several reasons why the batteries may not (dis)charge at the same power as the inverter:
1. There may be charge/discharge limits in place (check the settings of the battery inverter in the commissioning interface).
2. The nominal power of the battery may be less than the nominal power of the battery inverter.
3. The battery is outside its optimal operating temperature, and operates at limited power.
4. The battery cells may be out of balance. [Charge the battery completely to balance the cells](/Controller/Configuration%20from%20A%20to%20Z/11-Extra-Information/battery-maintenance-charge).

What you can check too:
- Check if the device allows 'exporting to the grid' in its configuration.
</Details>

<Details summary='The state of charge of my battery changes very suddenly or drops to zero unexpectedly.'>
This is an indication of an unbalance between the cells of the batteries. This issue is often solved by force charging the battery to 100% for several hours. To balance the battery cells:
- For a one-time balance, use the [Testing and manual override](/Controller/Configuration%20from%20A%20to%20Z/11-Extra-Information/testing-and-manual-override/) function to charge the battery for 24 hours.
- For a weekly maintenance charge, active the [Battery maintenance charge](/Controller/Configuration%20from%20A%20to%20Z/11-Extra-Information/battery-maintenance-charge/) function.
</Details>

<Details summary='I have set a minimum state of charge of 5%, but the battery stops discharging at 6%.'>
The <BrandName /> <ControllerName /> stops discharging at 1% above the minimum state of charge. This is because of the following protection mechanism that is used to prevent the battery from completely draining due to self discharging:
The <BrandName /> <ControllerName /> will send a signal to the battery to charge at a small amount as soon as the state of charge drops to 1% below the minimum state of charge due to self discharge of the battery. This charge signal is maintained until the battery is at 1% above the minimum state of charge. The <BrandName /> <ControllerName /> charges the battery 2% and not 1%, to prevent that an unstable measurement of the state of charge would cause continuous switchovers between charging and not charging. (If your battery is in reality at 4.99%, then it might report as 4%, which would cause charging, and quickly it would go to 5.00%, stop charging, drop back to 4.99% in a small time, start charging again, and so on.)
</Details>

## Solar inverters

<Details summary='I have a specific feed in limit set, but there is more power fed into the grid than the limit.'>
Settings to check:
- Check if the "Allowed grid export power (kW)" is set to the right limit. (See also [Grid limits](/Controller/Configuration%20from%20A%20to%20Z/3-grid-limits/))
- Check if the local control mode for solar is set to "Feed in restriction till allowed grid export power". (See also [Grid limits](/Controller/Configuration%20from%20A%20to%20Z/8-local-control-modes/setting-control-modes/))
- Check if the device is configured to allow remote control.
- Check if all the solar inverters of the installation are connected to the <BrandName /> <ControllerName /> and listens to the curtailment commands. (See also [Testing/manual override](/Controller/Configuration%20from%20A%20to%20Z/11-Extra-Information/testing-and-manual-override/))
- If you only have batteries and solar inverters that are not connected to the <BrandName /> <ControllerName />, then the battery might have been full. You must add the inverter too.
- If you have a hybrid inverter, then make sure during the adding of the device you chose to add both PV and the battery (if requested during the adding).
</Details>

<Details summary='I have an export power limit of 100kW, but my solar production is always limited to 90kW.'>
By default, a safety factor of 90% is applied, meaning that the <BrandName /> <ControllerName /> controls everything, including solar production, to be within 90% of the set grid limits. You can change this in the "Advanced Settings" menu (all the way to the bottom of the "Settings" menu).
This safety factor helps safeguarding against exceeding the limits, by leaving some room for the controller to react to power fluctuations (e.g. clouds flying over can make the PV production dip by as much as 80%). If you have a combination of consumers and producers, then it is recommended to leave this to 90%. Only set this to 100% if you are sure that there is no risk of tripping breakers or big fluctuations leading to exceeding the limits.
</Details>

## Electric vehicles
<Details summary='My EV always charges at low power, as soon as I plug it in.'>
- For many charging pole - EV combinations it is not possible to completely suspend charging, or the EV goes into fault. They often need at least 6A of charging current.
- In the device settings in the commissioning interface, try setting "Allow suspending charging" to true. This indicates to the <BrandName /> <ControllerName /> that this EV - charging station combination supports suspending charging.
- Check if the device is configured to allow remote control.
- Check if the charging stations is communicating correctly with the <BrandName /> <ControllerName />. Charging stations that are not communicating correctly may go to a low current fallback mode.
</Details>

<Details summary='My EV always goes into fault.'>
- For many charging pole - EV combinations it is not possible to completely suspend charging, or the EV goes into fault. They often need at least 6A of charging current.
- In the device settings in the commissioning interface, try setting "Allow suspending charging" to false/disabled. This indicates to the <BrandName /> <ControllerName /> that this EV - charging station combination does not support suspending charging.
</Details>

<Details summary="I have an EV and a battery, and I don't want the battery to discharge for charging my EV.">
- You can configure individual EV charging sockets to not use energy from the battery. [Check this page for more information](/Controller/Configuration%20from%20A%20to%20Z/11-Extra-Information/battery-and-ev/).
</Details>

<Details summary="My EV doesn't charge at full power, even if there is enough power available.">
EV charging stations only accept maximum charging currents. Most likely the <BrandName /> <ControllerName /> does send full power as the maximum charge current, but the EV might decide on its own not to use this. The effective charging speed is especially likely to be lower if the EV is almost full.
</Details>

## Energy meters
<Details summary='My energy meter is not reporting the right values.'>
- Check if the energy meter is installed in the right direction. You can virtually invert the direction of the energy meter from the device settings in the "Devices tab" of the commissioning interface. See also [Reversing energy meter readings](/Controller/Configuration%20from%20A%20to%20Z/11-Extra-Information/reversing-energy-meter/).
- Check if the energy meter is calibrated correctly. If you have a three-phase energy meter, check if the three phases are connected to the right wires.
</Details>

## Relays / ON-OFF Loads
<Details summary='What does the default state of a relay mean?'>
The default states of the relay are:
- **Switched ON**: In this state, your relay will be running and using power, except when the EMS decides to block it.
- **Switched OFF**: By default, your relay will not be running or using power, except when the EMS decides it’s the right time to turn it on.

Please note that this only sets what the relay does by default. Relay control always stays active.
</Details>


## Other
<Details summary='I want to implement my own control algorithm. Can I do this?'>
Yes, you can use [the external API](/Controller/External%20Signals/Monitoring/monitoring-api#external-monitoring-api) for this purpose.
</Details>


# Data usage


import { BrandName, ControllerName, CustomerName, InsightsName, InsightsUrl } from '@site/src/components/customFields';
import Details from '@theme/Details';
import Checkbox from '@site/src/components/CheckBox';

<Details summary='The EMS has a high data usage'>
    Steps to undertake:
    - Check if the data saver is active. See also [Data saver](/Controller/Configuration%20from%20A%20to%20Z/11-Extra-Information/data-usage/).
    - If you use external signals (see the tab "External data sources" in the <BrandName /> <ControllerName />), then the data usage might be higher than usual, depending on the data source. This is a side effect of the fact that most external signals are live and require a constant connection.
    - If the <BrandName /> <ControllerName /> is on a 4G/5G connection, check if the data bundle is large enough. See also [Data saver](/Controller/Configuration%20from%20A%20to%20Z/11-Extra-Information/data-usage/).
    - Check if there are no other devices on the same 4G/5G connection that might use a lot of data.
</Details>

# Device communication


import { BrandName, ControllerName, CustomerName, InsightsName, InsightsUrl } from '@site/src/components/customFields';
import Details from '@theme/Details';

# Device communication problems

## Access to the commissioning interface
<Details summary='When I go to "Controller Configuration" in the app or online portal, it says that the controller is offline.'>
    Steps to undertake:
    - Check the internet connection of the <BrandName /> <ControllerName />. Check with your computer if you have internet on the ethernet cable attached to the <BrandName /> <ControllerName />.
    - Try scanning on the local network for the <BrandName /> <ControllerName /> with an IP scanner (see also "[Accessing the commissioning interface](/Controller/Configuration%20from%20A%20to%20Z/2-accessing-commissioning-interface#option-2-access-locally-through-mdns)").
    - Check with the building owner (residential) or network administrator (commercial) if this is a network with fixed IP addresses. The <BrandName /> <ControllerName /> is by default configured to use DHCP. If you need to change it to a fixed IP address, first connect it to a DHCP network, and change the IP address from there to the necessary fixed IP address.
    - Check if communication over the right outbound network ports is allowed. (See also "[Firewall guidelines](/Controller/network-configuration/#firewall)")
    - Verify if the [Ethernet wiring guidelines](/Controller/wiring-best-practices/#ethernet) have been followed.
    - If the <BrandName /> <ControllerName /> is on a 4G connection:
        - Check the 4G reception of the router. (Note, it can be on another mobile network than your phone).
        - Place the router or 4G antenna on another location.
        - Check if there is enough data in the 4G connection bundle. It is recommended to have 5GB/month available for up to three devices, plus 500Mb per additional device
</Details>

<Details summary='When I can open the commissioning interface, but my login/password is refused when logging in.'>
    - Check if the <BrandName /> <ControllerName /> is claimed in the app. See [linking the <BrandName /> <ControllerName /> to your account](/Controller/Configuration%20from%20A%20to%20Z/1-link-to-your-account/)
    - Check if the account with which you try to login has access rights for the <BrandName /> <ControllerName />. See [user management](/Controller/Configuration%20from%20A%20to%20Z/11-Extra-Information/user-management/)
    - If the <BrandName /> <ControllerName /> is not online, and you don't know the password for local login: contact your distributor to obtain the recovery password.
</Details>

<Details summary='I configured a fixed IP address in the controller, and now I cannot access the commissioning interface any more.'>
    **If you know the fixed IP address:**\
    Configure your computer to have a fixed IP address in the same subnet (but on a different address) than the <BrandName /> <ControllerName />. Connect your computer directly with an ethernet cable to the <BrandName /> <ControllerName />. Do not use a switch or router. In a webbrowser, surf to the fixed IP address of the <BrandName /> <ControllerName />. You should now be able to access the <BrandName /> <ControllerName />.\
    \
    **If you do not know the fixed IP address:**
    - You can retrieve the IP address through mDNS. See also Option 3.2 of [Accessing the commissioning interface](/Controller/Configuration%20from%20A%20to%20Z/2-accessing-commissioning-interface#option-32-find-the-ip-address-with-mdns-also-works-if-the--does-not-have-a-good-network-configuration).
    - Or [reset the <BrandName /> <ControllerName />](/Controller/Configuration%20from%20A%20to%20Z/11-Extra-Information/reset/).
</Details>


## Ethernet
<Details summary='I cannot find the device I want to add (ethernet).'>
    Steps to undertake:
    - Check the network connection of the device. Check with your computer if you have internet on the ethernet cable attached to the device.
    - Try scanning on the local network for the device with an IP scanner. (see also "[Accessing the commissioning interface](/Controller/Configuration%20from%20A%20to%20Z/2-accessing-commissioning-interface#option-2-access-locally-through-mdns)").
    - Check with the building owner (residential) or network administrator (commercial) if this is a network with fixed IP addresses and if the device has the right IP address set.
    - Check if the <BrandName /> <ControllerName /> and the device are in the same subnet (e.g. a <BrandName /> <ControllerName /> in subnet 192.168.1.x can generally not talk with a device in subnet 192.168.200.x).
    - Verify if the [Ethernet wiring guidelines](/Controller/wiring-best-practices/#ethernet) have been followed.
    - If you use a VLAN, make sure the device you want to add is in the same VLAN as the <BrandName /> <ControllerName />.
</Details>

<Details summary='I can find the device I want to add in the commissioning interface, but the controller does not connect to it.'>
    Steps to undertake:
    - Check if remote communication and control have to be enabled on the device. See the [specific device configuration page](/Controller/Devices) for more information.
</Details>

<Details summary='My device stopped communicating.'>
    Steps to undertake:
    - Check if the <BrandName /> <ControllerName /> is online.
    - Check if the device is still online on your network.
    - Make sure if the device uses WiFi that it has good WiFi reception and that the WiFi password is up to date.
    - If the <BrandName /> <ControllerName /> is on a 4G connection:
        - Check the 4G reception of the router. (Note, it can be on another mobile network than your phone).
        - Place the router or 4G antenna on another location.
        - Check if there is enough data in the 4G connection bundle. It is recommended to have 5GB/month available for up to three devices, plus 500Mb per additional device
</Details>

## RS485
<Details summary='I cannot find any device on the RS485 bus.'>
    Steps to undertake:
    - Check if each device on the serial bus has a unique address. See the [specific device configuration page](/Controller/Devices) for more information.
    - Check if the wiring polarity is correct. See the [specific device configuration page](/Controller/Devices) for more information.
    - Verify if the [RS485 wiring guidelines](/Controller/wiring-best-practices/#rs485) have been followed.
    - Check if remote communication and control have to be enabled on the device. See the [specific device configuration page](/Controller/Devices) for more information.
    - Check if the device addresses are set to high values. Some devices default to e.g. address 255, while the <BrandName /> <ControllerName /> starts searching from 1 - so it can take a while before the device is found.
</Details>

<Details summary='I can find some but not all devices on the RS485 bus.'>
    Steps to undertake:
    - Check if each device on the serial bus has a unique address. See the [specific device configuration page](/Controller/Devices) for more information.
    - Check if the wiring polarity is correct. See the [specific device configuration page](/Controller/Devices) for more information.
    - Verify if the [RS485 wiring guidelines](/Controller/wiring-best-practices/#rs485) have been followed.
    - Check if remote communication and control have to be enabled on the device. See the [specific device configuration page](/Controller/Devices) for more information.
    - Check if the device addresses are set to high values. Some devices default to e.g. address 255, while the <BrandName /> <ControllerName /> starts searching from 1 - so it can take a while before the device is found.
</Details>

<Details summary='My device stopped communicating.'>
    Steps to undertake:
    - Check for loose wiring.
    - If the <BrandName /> <ControllerName /> is on a 4G connection:
        - Check the 4G reception of the router. (Note, it can be on another mobile network than your phone).
        - Place the router or 4G antenna on another location.
        - Check if there is enough data in the 4G connection bundle. It is recommended to have 5GB/month available for up to three devices, plus 500Mb per additional device
</Details>

<Details summary='I get the error "I/O error: read/write to disk, serial port or network failed".'>
    Steps to undertake:
    - Check if this error persists after rebooting the controller.
</Details>

## P1 Meters
<Details summary="I see 'not available' when selecting my p1-connection">
    Steps to undertake:
    - Check on the digital meter if the cable is in P1 and not connected to the similar S1 port.
    - Is the USB connection on the controller inserted all the way.
</Details>

<Details summary='I get the error "I/O error: read/write to disk, serial port or network failed".'>
    Steps to undertake:
    - Check if this error persists after rebooting the controller.
</Details>


# Device integrations


import { BrandName, ControllerName, CustomerName, InsightsName, InsightsUrl } from '@site/src/components/customFields';
import Details from '@theme/Details';
import Checkbox from '@site/src/components/CheckBox';

# Device integrations

<Details summary="My device integration is missing.">
Read more about [New Integrations](/Controller/Devices/new-integrations/)
</Details>

# Energy Prices Information


import { BrandName, ControllerName, CustomerName, InsightsName, InsightsUrl } from '@site/src/components/customFields';
import Details from '@theme/Details';

# Price Settings

## Day-ahead Prices
<Details summary='Details'>
    The hourly energy price for your country via EPEX Spot.
</Details>


# Troubleshooting


import { FolderOverview } from '@/components/FolderOverview';

# Troubleshooting

<FolderOverview folder="Controller/Troubleshooting" />


# MAC-address Troubelshooting


import { BrandName, ControllerName } from '@site/src/components/customFields';
import ClickableImage from '@site/src/components/ClickableImage';
import Details from '@theme/Details';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import RS485AddressNote from '@site/src/components/RS485AddressNote';

# MAC-address Reachability Troubleshooting

> [!INFO]
> Make sure to follow the instructions for adding a device [here](/Controller/Configuration%20from%20A%20to%20Z/11-Extra-Information/adding-device/)

## Network Reachability

### Same subnet?
Make sure your laptop/PC and the controller are on the same IP subnet.

### Correct interface?
If your laptop has both Wi-Fi and Ethernet active, disable Wi-Fi so discovery packets aren’t sent to the wrong interface.

### VPN enabled?
VPNs often break local discovery. Disable VPN during commissioning.

### Firewall blocking?
Local firewalls (Windows Defender, antivirus suites) may block discovery packets. Temporarily allow or disable to test.

### Switches/routers with isolation?
Guest Wi-Fi, client isolation, or VLANs may prevent devices from being seen.

---

## Device-side issues

### Powered on?
Check status LEDs for power and heartbeat.

### Correct firmware?
Older firmware may not support the discovery method (mDNS/UDP broadcast).

### Factory reset needed?
If LEDs show error states (red/yellow blinking), reset to defaults.

### Wrong port plugged?
Ensure Ethernet cable is in the correct LAN port.

---

## Label vs reality

### Reading MAC correctly?
Common misreads:
- `O` vs `0` (letter O vs zero)  
- `I` vs `1` (capital i vs one)

### Serial vs MAC?
Double-check that you’re entering the MAC, not the serial number.

---

## Network services

> [!INFO]
> More info about network troubleshooting can be found [here](/Controller/Troubleshooting/device-communication/)
:::

### DHCP available?
If DHCP is missing, the controller may not grab an IP. Either set a DHCP reservation or try fixed IP.

### mDNS vs MAC discovery
Some OS versions resolve devices better with mDNS (`hostname.local`).  
Try:  
- `ping <device>.local`  
- `Resolve-DnsName` in PowerShell

### Ports blocked upstream?
Outbound ports required:  
- 80  
- 443  
- 1194  
- 1883/8883  
- 123  

No inbound needed. If blocked, devices won’t appear.

---

## Commissioning tool side

### Browser caching?
Refresh or restart commissioning tool.

### Wrong environment selected?
Ensure you’re logged in to the correct customer/project environment.

### Old scan result?
Force a rescan (not relying on cached discovery).

---

## Hardware / cabling

### Faulty EMS-controller?
Test with another controller to confirm whether the current one is defective.

### Ethernet cable faulty?
Swap with a known good cable.

### Switch port issue?
Try another port or bypass managed switch.

### PoE expectation?
If controller doesn’t support PoE, make sure external power supply is connected.

---

## Last-resort checks

- Scan with **nmap** or **Advanced IP Scanner** to see if the MAC is visible at network level.  
- Add by IP manually (only if you can discover it outside the tool).  
- Contact support if still not visible — possible hardware fault.


# Netwerk Troubelshooting


import { BrandName, ControllerName } from '@site/src/components/customFields';
import ClickableImage from '@site/src/components/ClickableImage';
import Details from '@theme/Details';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import RS485AddressNote from '@site/src/components/RS485AddressNote';

# Network Troubleshooting

## How to get a connection to your controller after a static IP was set.
Situation: You changed the network configuration on the controller and can’t connect to it or detect it in the network. <br/>
Goal: Reconnect the controller to the network.<br/>
Physical topology:<br/>
Connect a CAT5 or CAT6 cable with RJ45 connectors between the Network Interface Card (NIC) of the Controller and the laptop / computer.<br/>
On both ends the LEDS be on. Depending on your NIC, you have 1 or 2 LEDs.<br/>
Configuration:<br/>
Change the network configuration of your ethernet port on your laptop / computer to the network settings that corresponds with the current network configuration of the controller.<br/>
For example the network configuration on the controller has been set to<br/>
IP 192.168.37.53<br/>
Subnet Mask 255.255.192.0<br/>
Gateway 192.168.37.1<br/>
With this information, you may set the network configuration on your computer to e.g.:<br/>
IP 192.168.37.20<br/>
Subnet mask 255.255.192.0<br/>
The Gateway may be left blank, as their’s no gateway in this topology of the direct connection.<br/>


You may change these settings from the Network Settings on your devices. For example in Windows 11 this flow may be used:

    - Open the settings and o to Network & internet
<ClickableImage src="/img/generic/NetwerkSettingsWindows11.png" alt="Network Settings Windows 11" maxWidth="50%" />

    - Click on “Edit”, change the IP address setting to Manuel and turn on the IPv4 setting.
<ClickableImage src="/img/generic/NetworkSettingsWindows11Manual.png" alt="Network Settings Windows 11 Manual" maxWidth="50%" />
With these changes, you should be able to reach the address of the controller from your browser.

    1. 	We need an Ethernet cable that is connected to the controller and not to a switch or to a router.
    2. 	The controller was set to a fixed IP earlier, such as the following:
        1. 	The controller should be connected directly to the ethernet of the computer. To be certain of the state, I did a factory reset on the controller from the button. 
        2. 	The adapter's address should be changed to one that is within the subnet of the address and the netmask we have. (As in this case of my test, 192.168.37.53  255.255.255.192) 
        3. 	The subnet mask decides the range of your address. We can see the possible subnets from here for example (https://www.calculator.net/ip-subnet-calculator.html) Since we have an address on the first of the possible subnets in this example , we can set our address to any other within the .1-.62 range.
<ClickableImage src="/img/generic/NetworkConfiguration.png" alt="Network Settings Windows 11 Subnet" maxWidth="50%" />
    This can also be seen on the following table  /26 -- 4 Subnets -- 62 Hosts/Subnet 

| Network # | IP Range | Broadcast |
|---|---|---|
| .0 | .1-.62 | .63 |
| .64 | .65-.126 | .127 |
| .128 | .129-.190 | .191 |
| .192 | .193-.254 | .255 |

1. 	(Taken from  https://www.aelius.com/njh/subnet_sheet.html )
2. 	Then, on my browser I opened the fixed IP of the controller, which I had set before starting the test in step 2.
3. 	You should be now able to reach the control panel of the local page. 


    The login details will be visible on the screen, as the controller is not connected to the cloud at the moment, your insights credentials might not work.
1. 	Once you login, if you have a screen for the configuration of the controller, you can click on the skip button as we will perform a full factory reset.
2. 	The next step is to go to Settings, and then click on the Factory reset and proceed.
3. 	Once the controller has finished the restarting process and the light is no longer blue, you can disconnect the cable from the computer and connect it back to the network (e.g. directly to the router).
4. 	You should be able to connect now directly from the Toolbox and the VPN webpage and the LED light shall be green.


> [!WARNING]
> Dont forget to change the network settings back to dhcp or automatic IP address.


# Software version


import { BrandName, ControllerName, CustomerName, InsightsName, InsightsUrl } from '@site/src/components/customFields';
import Details from '@theme/Details';

<Details summary='Where can I find what is in the release versions of the software?'>
    - In the <BrandName /> <ControllerName />, in the tab "Settings" --> "About" --> "Changelog" you can find the complete changelogs of the controller.
    - If you have access to https://toolbox.eniris.be, you can check the changelogs here too.
    - You can subscribe to our newsletter via https://eniris.io/ to remain up to date about new software releases.  
</Details>

<Details summary='How can I update the software of the EMS?'>
    - If in the tab 'Settings' --> 'Check for updates' the option 'Enable automatic updates' is on, the EMS software will update as soon as new software is available.
    - You can check for software updates in the tab 'Settings' --> 'Check for updates'.
    - Through the toolbox (subject to additional fees). Here you can manage specific software updates on specific controllers.
</Details>

> [!WARNING]
> If you restrict the software to certain versions and disable 'automatic updates', you may miss out on critical bug fixes and security updates. Damages that incur due to not updating the software may not be covered. Please check the contract with your distributor.

<Details summary='If there is an update, do I have to recall all non-installed EMS systems to update them first?'>
    - No, updates will be installed when the <BrandName /> <ControllerName /> connects to the server during installation.
</Details>

# Video tutorials


import { BrandName, ControllerName, CustomerName, InsightsName, InsightsUrl } from '@site/src/components/customFields';
import Details from '@theme/Details';
import YouTubeEmbed from '@site/src/components/YouTubeEmbed';

# Video tutorials (Dutch only)

## 1. Controller hardware instellen
<YouTubeEmbed videoId="6z06RFiRKpc" />

## 2. Connecteren met de <BrandName /> <ControllerName />
<YouTubeEmbed videoId="8avpJ3SD7pM" />

## 3. Praktijkvoorbeeld IP Scanner en eerste stappen commissioning
<YouTubeEmbed videoId="a3Gl3R023F8" />

## 4. Praktijkvoorbeeld toevoegen van slimme meter / digitale meter
<YouTubeEmbed videoId="aVjsXH9nenc" />

## 5. Praktijkvoorbeeld toevoegen van modbus energiemeter
<YouTubeEmbed videoId="H6cIoMxEqLw" />

## 6. Eenvoudig Groeperen
<YouTubeEmbed videoId="1WlwQk38SsU" />

## 7. Andere voorbeelden van groeperen
<YouTubeEmbed videoId="6Ip8N8T2oyw" />

## 8. Status LED <BrandName /> <ControllerName />
<YouTubeEmbed videoId="k-HFJWWGqb0" />

## 9. Update <BrandName /> <ControllerName /> software
<YouTubeEmbed videoId="r5Zb3neyhNU" />

## 10. Custom Control Logic — volledige walkthrough

Learn how to open the logic editor in the commissioning interface, build a custom control request, use measurements and schedules, and check the program before saving it. Dutch walkthrough, 41 minutes.

<YouTubeEmbed videoId="dTNQ3z2aek4" />

[Read the Custom control logic guide](/Controller/Configuration%20from%20A%20to%20Z/8-local-control-modes/special-local-control-modes/#custom-control-logic).

## 11. Custom Modbus drivers: zelf een toestel integreren

Integrate a Modbus device with SmartgridOne yourself using the controller's commissioning interface. This 30-minute Dutch walkthrough covers opening the editor, a practical Playground example, measurements, control commands, testing, saving and adding the device.

[Read the standalone Custom Modbus drivers guide](/Controller/Devices/custom-modbus-drivers/).

<YouTubeEmbed videoId="_ubfcC7j34c" title="SmartgridOne Custom Modbus drivers: zelf een toestel integreren" />


# Wiring & connectivity guidelines


import { BrandName, ControllerName, CustomerName, InsightsName, InsightsUrl, ModelPro, ModelHome, ModelLite, ModelConnect } from '@site/src/components/customFields';
import Details from '@theme/Details';
import ClickableImage from '@site/src/components/ClickableImage';
import Tabs from '@theme/Tabs';
import TabItem from '@theme/TabItem';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import { GithubAlert } from '@/components/GithubAlert'

# Wiring & connectivity guidelines

> [!NOTE]
>   The insulation class of the cables must be suitable for the intended signal voltage. Ensure that the cables used comply with the appropriate safety and operational standards for the specific voltage levels in the system.

# Ethernet

The following guidelines apply:

* **Cable type**: You must use CAT5e or higher cables for optimal performance. In commercial and industrial settings, it is recommended to use shielded cables.
* **Network connection**: Check with your computer if you have internet on the ethernet cable before connecting it to the <BrandName /> <ControllerName /> or device.
* **Maximum distance**: The individual cable length is limited to 100 meters. For longer distances you need a signal booster or switch.
* **Subnet**: The <BrandName /> <ControllerName /> and the devices have to be on the same subnet to be able to communicate (e.g. a <BrandName /> <ControllerName /> in subnet 192.168.1.x can generally not talk with a device in subnet 192.168.200.x).
* **Outbound ports**: See [network configuration](/Controller/network-configuration/) on firewall configurations.

> [!NOTE]
>   ### Powerline adapters
>
>   For places in residential settings that have no ethernet cabling installed, you may consider Powerline adapters. Please note that only wall sockets that are on the same phase can be used with most powerline adapters.

# Other interfaces

> [!TIP]
>   ### Additional I/O's
>
>   All <BrandName /> models are extendible with additionaly I/O's through the accessories. See accessories for more information.

<Tabs
  defaultValue="om1"
  values={[
  { label: 'Model OM1', value: 'om1' },
  { label: 'Model EDS', value: 'eds' },
  { label: 'Model ULT', value: 'ult' },
  { label: 'Model M2S', value: 'm2s' },
]}
>
  <TabItem value="om1">
    ## <BrandName /> <ModelPro /> (Model OM1)

    <ClickableImage src="/img/eniris/model-OM1.webp" srcWhitelabeled="/img/whitelabeled/ModelOM1.png" alt="Model OM1" maxWidth="350px" border="" />

    <ClickableImage src="/img/generic/Electrical schematic OM1.svg" srcWhitelabeled="/img/generic/Electrical schematic OM1.svg" alt="Electrical schematic model OM1" maxWidth="600px" border="" />

    The permissible wire cross-section for the connectors is as follows:

    | Type                      | Section (AWG) | Section (mm²) |
    | :------------------------ | :------------ | :------------ |
    | Solid Wires               | 26-16 AWG     | 0,129-1,31    |
    | Stranded (Flexible) Wires | 26-16 AWG     | 0,129-1,31    |

    ## Digital inputs & relay outputs

    <GithubAlert variant="warning" kind="warning">
      You MUST respect the voltage & current ratings from [the Specifications](/Controller/specifications/).
      Using the device outside of its rated values is dangerous and may lead to damage and injuries.

      | Interface     | Voltage (V)        | Current (A) |
      | :------------ | :----------------- | :---------- |
      | Relay         | Max. 30Vac / 50Vdc | 1.0 A       |
      | Digital input | 5-50Vdc            | N/A         |
    </GithubAlert>

    <GithubAlert variant="tip" kind="tip">
      If you need the switch higher voltages or currents than what the relay is rated for, then use the relay of the <BrandName /> <ControllerName /> to switch another relay that has the voltage or current rating that you need.

      <ClickableImage src="/img/generic/relay.png" alt="Image" maxWidth="450px" />
    </GithubAlert>

    The following guidelines apply:

    * **Cable type**: It is recommended to use **shielded** cables with **twisted pairs** for optimal performance.

    ### Wiring S0 Pulse Meters

    <ClickableImage src="/img/generic/Digital inputs wiring.png" alt="Passive S0 Meter Wiring Diagram" maxWidth="350px" />

    **Scenario 1 (left example): Active Meter (Voltage Output)**
    Use this wiring if the meter generates its own voltage pulse.

    **Scenario 2 (right example): Passive Meter (Dry Contact)**
    Use this wiring if the meter acts as a relay/switch. The controller provides the wetting voltage (12V).

    ## RS485

    ### Wiring

    <GithubAlert variant="tip" kind="tip">
      The color of the wires does not matter. You may choose this, as long as both the A and B are from a single twisted pair.
    </GithubAlert>

    The following guidelines apply:

    * **Cable type**:
      * You must use **shielded** cables with **twisted pairs** for optimal performance.
      * **Use a single pair** for a RS485 connection. One cable of this pair is used for RS485-A and the other one for RS485-AB. Do not split A and B over different pairs). If there is a ground wire, use another pair for the ground wire.
      * For short distances, a twisted pair from a network cable (minimum CAT5e) can be used.
      * Avoid using SVV cables or alarm cables, as they are not suitable for these purposes.
      * The cable must have a characteristic impedance of 100 to 120 ohm.

    #### Signal Mapping

    Different manufacturers use different naming conventions (A/B, +/-, D1/D0). Use this table to match your device's signals to the <BrandName /> controller.

    <RS485ConnectionTable firstColumn={["", "", ""]} />

    * **Connecting multiple devices**: The cable must be **daisy-chained** from device to device. Place the <BrandName /> <ControllerName /> like the picture below.

    <ClickableImage src="/img/eniris/wiring_Eniris.png" alt="Image 1" maxWidth="650px" />

    * **Maximum number of devices**: The absolute maximum number of devices that the <BrandName /> <ControllerName /> supports on the same RS485 bus is 20 (provided that each device has 1/4th unit load on the RS485 bus, which almost all devices do).
    * **Maximum distance**: The total cable length is limited to 1000 meters - but it is recommended to limit the maximum to 100m.
    * **Long Distances**:
      * <BrandName /> <ControllerName /> model OM1: It is recommended to activate the **termination resistor** on the <BrandName /> <ControllerName /> (already active by default from the factory), and install a 120Ω termination resistor at the opposite end of the daisy chain.
      * Other <BrandName /> <ControllerName /> models: Install a 120Ω termination resistor at the both ends of the daisy chain.
    * **Grounding the cable shield**: If the cable is shielded, then you must connect the shield to the electrical earth of the installation at one end of the cable.

    <GithubAlert variant="tip" kind="tip">
      ### In case of many devices

      * If you have many devices on the RS485 bus, the control system gets slower. This is because over an RS485 bus only one device can communicate at a time.
      * For this reason we recommend connecting no more than 5 devices on the same RS485 bus.
      * If you have more devices, it is recommended to use one of the [RS485 expansion accessories](/Controller/accessories).
    </GithubAlert>

    <GithubAlert variant="warning" kind="warning">
      Grounding shielded cables

      * Ground the shield at a single end of the cable only. Do not ground the shield at multiple points along the cable, not even the other end of the cable. If you use a daisy chain, then ground each individual cable at a single end (you may use the shield of another cable as the grounding point at the end of the cable, but this is not recommended).
      * Ground the shield to the earth ground of the electrical installation. Do not ground it to the signal ground.
    </GithubAlert>

    ### Termination resistor & bias resistors

    To the left of the I/O connections on the <BrandName /> <ControllerName />, there are three DIP switches for terminating and biasing the RS485 communication bus.

    The correct configuration depends on the topology of the RS485 bus. In most cases, activating all resistors is the recommended choice. Do this if you are unsure. This is different if the <BrandName /> <ControllerName /> is not at the end of the communication bus or if another device has active bias resistors.

    <ClickableImage src="/img/generic/om1-dip-switches.png" alt="Image 1" maxWidth="650px" />

    Whether the resistors are active or not depends on the position of the DIP switches. To do this, you need to consider the production date of the <BrandName /> <ControllerName />. You can deduce this from the serial number. The serial number starts with production code OM1, followed by six digits representing the production date. E.g. OM1240315 was produced on 15/03/2024.

    **If your  is manufactured before 1 August 2024:**
    (These devices have white switches coming from a black component).

    * The termination resistor is active when the corresponding DIP switch is in the down position.
    * The bias resistors are active when the corresponding DIP switches are in the down position.

    **If your  is manufactured after 1 August 2024:**
    (These devices have white switches coming from a red component).

    * The termination resistor is active when the corresponding DIP switch is in the up position.
    * The bias resistors are active when the corresponding DIP switches are in the up position.

    ### Addresses

    <GithubAlert variant="warning" kind="warning">
      You MUST give each device on the RS485 bus a unique address.
    </GithubAlert>

    <GithubAlert variant="tip" kind="tip">
      Use lower addresses first (1, 2, ...), because the <BrandName /> <ControllerName /> will find them faster!
    </GithubAlert>

    <GithubAlert variant="tip" kind="tip">
      Stick with the factory default baud rate, parity and stop bits. The <BrandName /> <ControllerName /> will scan on those first.
    </GithubAlert>
  </TabItem>

  <TabItem value="eds">
    ## <BrandName /> <ModelPro /> (Model EDS)

    <ClickableImage src="/img/eniris/model-EDS.png" srcWhitelabeled="/img/whitelabeled/ModelM1.png" alt="Model EDS" maxWidth="350px" border="" />

    The permissible wire cross-section for the connectors is as follows:

    | Type                      | Section (AWG) | Section (mm²) |
    | :------------------------ | :------------ | :------------ |
    | Solid Wires               | 26-18 AWG     | 0,129-1       |
    | Stranded (Flexible) Wires | 26-18 AWG     | 0,129-1       |

    ## RS485

    ### Wiring

    <GithubAlert variant="tip" kind="tip">
      The color of the wires does not matter. You may choose this, as long as both the A and B are from a single twisted pair.
    </GithubAlert>

    The following guidelines apply:

    * **Cable type**:
      * You must use **shielded** cables with **twisted pairs** for optimal performance.
      * **Use a single pair** for the RS485 A and B wires (do not split them over different pairs). If there is a ground wire, use another pair for the ground wire.
      * For short distances, a twisted pair from a network cable (minimum CAT5e) can be used.
      * Avoid using SVV cables or alarm cables, as they are not suitable for these purposes.
      * The cable must have a characteristic impedance of 100 to 120 ohm.

    #### Signal Mapping

    Different manufacturers use different naming conventions (A/B, +/-, D1/D0). Use this table to match your device's signals to the <BrandName /> controller.

    <RS485ConnectionTable firstColumn={["", "", ""]} />

    * **Connecting multiple devices**: The cable must be **daisy-chained** from device to device. Place the <BrandName /> <ControllerName /> like the picture below.

    <ClickableImage src="/img/eniris/wiring_Eniris.png" alt="Image 1" maxWidth="650px" />

    * **Maximum number of devices**: The absolute maximum number of devices that the <BrandName /> <ControllerName /> supports on the same RS485 bus is 20 (provided that each device has 1/4th unit load on the RS485 bus, which almost all devices do).
    * **Maximum distance**: The total cable length is limited to 1000 meters - but it is recommended to limit the maximum to 100m.
    * **Long Distances**: Install a 120Ω termination resistor at the both ends of the daisy chain.
    * **Grounding the cable shield**: If the cable is shielded, then you must connect the shield to the electrical earth of the installation at one end of the cable.

    <GithubAlert variant="tip" kind="tip">
      TIP: In case of many devices

      * If you have many devices on the RS485 bus, the control system gets slower. This is because over an RS485 bus only one device can communicate at a time.
      * For this reason we recommend connecting no more than 5 devices on the same RS485 bus.
      * If you have more devices, it is recommended to use multiple RS485 ports.
    </GithubAlert>

    <GithubAlert variant="warning" kind="warning">
      Grounding shielded cables

      * Ground the shield at a single end of the cable only. Do not ground the shield at multiple points along the cable, not even the other end of the cable. If you use a daisy chain, then ground each individual cable at a single end (you may use the shield of another cable as the grounding point at the end of the cable, but this is not recommended).
      * Ground the shield to the earth ground of the electrical installation. Do not ground it to the signal ground.
    </GithubAlert>

    <GithubAlert variant="warning" kind="warning">
      Multiple ports
      Do not connect the same RS485 bus to multiple ports on the <BrandName />. This will introduce interference.
    </GithubAlert>

    ### Termination resistors

    You must install 120 ohm termination resistors on both ends of the serial communication bus. The <BrandName /> does not have an integrated termination resistor.

    ### Addresses

    <GithubAlert variant="warning" kind="warning">
      You MUST give each device on the RS485 bus a unique address.
    </GithubAlert>

    <GithubAlert variant="tip" kind="tip">
      Use lower addresses first (1, 2, ...), because the <BrandName /> <ControllerName /> will find them faster!
    </GithubAlert>

    <GithubAlert variant="tip" kind="tip">
      Stick with the factory default baud rate, parity and stop bits. The <BrandName /> <ControllerName /> will scan on those first.
    </GithubAlert>
  </TabItem>

  <TabItem value="ult">
    ## <BrandName /> Ultra (Model ULT)

    <img height="271" width="362" src="/api/media/controller/wiring-best-practices/placeholder-ultra.png" />

    ## Ethernet

    The Ultra has three ethernet ports, labelled **A**, **B** and **C** on the enclosure. Port A is 2.5 gigabit, ports B and C are gigabit.

    All three ports are bridged together out of the box, so the Ultra behaves as a three port switch: it keeps the same IP address whichever port you plug into, and a device connected to any port can reach it. If you need a port on a separate network, you can take it out of the bridge in the network settings of the <BrandName /> <ControllerName />.

    ## Digital inputs & outputs

    <GithubAlert variant="warning" kind="warning">
      You MUST respect the voltage & current ratings from [the Specifications](/Controller/specifications/).
      Using the device outside of its rated values is dangerous and may lead to damage and injuries.

      | Interface      | Voltage (V) | Current (A)            |
      | :------------- | :---------- | :--------------------- |
      | Digital output | 5-30Vdc     | Max. 0.5 A per channel |
      | Digital input  | Max. 30Vdc  | N/A                    |
    </GithubAlert>

    The eight digital inputs and the eight digital outputs share one 20-pin terminal block, together with the **PCOM** and **DGND** terminals.



    ![](/api/media/controller/wiring-best-practices/Screenshot-2026-09-23-143427.png)



    <GithubAlert variant="warning" kind="warning">
      DGND is isolated
      The digital I/O section is isolated from the rest of the controller (2500Vdc). Do not connect DGND to the earth of the installation, nor to the ground of the <BrandName /> <ControllerName /> itself: that defeats the isolation which protects the controller.
    </GithubAlert>

    ### Digital outputs

    <GithubAlert variant="warning" kind="warning">
      The outputs are not relay contacts
      Unlike the relay outputs of the other models, the digital outputs of the Ultra are **sink type**. They only switch their terminal to DGND and they do not supply any voltage of their own. Every channel needs an external 5-30Vdc supply and a **load in series**.

      Connecting a supply directly to an output without a load in series short circuits that supply through the output and destroys the channel.
    </GithubAlert>



    <img height="375" width="562" src="/api/media/controller/wiring-best-practices/Screenshot-2026-09-23-143711.png" />



    Wire each output as follows:

    * The **positive** of the external supply goes to **PCOM** and to one side of the load.
    * The other side of the load goes to the **output terminal** of the channel you are using.
    * The **negative** of the external supply goes to **DGND**.

    <GithubAlert variant="tip" kind="tip">
      If you need to switch a higher voltage or current than the output is rated for, or if you need a potential free contact, use the digital output to switch an external relay that has the rating you need.
    </GithubAlert>

    ### Digital inputs

    The inputs can be used as a **dry contact** or as a **wet contact**. The mode is selected with an internal switch S3, by default it is set as a wet contact.

    | Mode        | S3 state | How to wire it                                      | Reads as activated when   |
    | :---------- | :------- | :-------------------------------------------------- | :------------------------ |
    | Dry contact | 1        | A potential free contact between the input and DGND | the contact is **closed** |
    | Wet contact | 3        | An external voltage between the input and DGND      | **10-30Vdc** is applied   |

    ![](/api/media/controller/wiring-best-practices/Screenshot-2026-09-23-144029.png)

    ![](/api/media/controller/wiring-best-practices/Screenshot-2026-09-23-144242.png)

    ## RS485

    The Ultra has four serial ports, delivered configured as RS-485 and isolated to 2500Vdc. They sit on **two** terminal blocks with two ports each: COM1 and COM2 share the first block, COM3 and COM4 the second. In RS-485 mode a port uses three of its pins: **D-**, **D+** and **GND**.



    ![](/api/media/controller/wiring-best-practices/Screenshot-2026-09-23-150156.png)

    ### Wiring

    The following guidelines apply:

    * **Cable type**:
      * You must use **shielded** cables with **twisted pairs** for optimal performance.
      * **Use a single pair** for the RS485 A and B wires (do not split them over different pairs). If there is a ground wire, use another pair for the ground wire.
      * For short distances, a twisted pair from a network cable (minimum CAT5e) can be used.
      * Avoid using SVV cables or alarm cables, as they are not suitable for these purposes.
      * The cable must have a characteristic impedance of 100 to 120 ohm.

    #### Signal Mapping

    Different manufacturers use different naming conventions (A/B, +/-, D1/D0). Use this table to match your device's signals to the <BrandName /> controller.

    <RS485ConnectionTable firstColumn={["", "", ""]} />

    * **Connecting multiple devices**: The cable must be **daisy-chained** from device to device. Place the <BrandName /> <ControllerName /> like the picture below.

    <ClickableImage src="/img/eniris/wiring_Eniris.png" alt="Image 1" maxWidth="650px" />

    * **Maximum number of devices**: The absolute maximum number of devices that the <BrandName /> <ControllerName /> supports on the same RS485 bus is 20 (provided that each device has 1/4th unit load on the RS485 bus, which almost all devices do).
    * **Maximum distance**: The total cable length is limited to 1000 meters - but it is recommended to limit the maximum to 100m.
    * **Long Distances**: Install a 120Ω termination resistor at the both ends of the daisy chain.
    * **Grounding the cable shield**: If the cable is shielded, then you must connect the shield to the electrical earth of the installation at one end of the cable.

    <GithubAlert variant="tip" kind="tip">
      In case of many devices

      * If you have many devices on the RS485 bus, the control system gets slower. This is because over an RS485 bus only one device can communicate at a time.
      * For this reason we recommend connecting no more than 5 devices on the same RS485 bus.
      * The Ultra has four ports, so spread the devices over the ports instead of putting them all on one bus.
    </GithubAlert>

    <GithubAlert variant="warning" kind="warning">
      Grounding shielded cables

      * Ground the shield at a single end of the cable only. Do not ground the shield at multiple points along the cable, not even the other end of the cable. If you use a daisy chain, then ground each individual cable at a single end (you may use the shield of another cable as the grounding point at the end of the cable, but this is not recommended).
      * Ground the shield to the earth ground of the electrical installation. Do not ground it to the signal ground.
    </GithubAlert>

    <GithubAlert variant="warning" kind="warning">
      Multiple ports
      Do not connect the same RS485 bus to multiple ports on the <BrandName />. This will introduce interference.
    </GithubAlert>

    ### Termination resistors

    The termination resistors of the Ultra sit on internal switches on the mainboard and are switched on by default.

    ### Addresses

    <GithubAlert variant="warning" kind="warning">
      You MUST give each device on the RS485 bus a unique address.
    </GithubAlert>

    <GithubAlert variant="tip" kind="tip">
      Use lower addresses first (1, 2, ...), because the <BrandName /> <ControllerName /> will find them faster!
    </GithubAlert>

    <GithubAlert variant="tip" kind="tip">
      Stick with the factory default baud rate, parity and stop bits. The <BrandName /> <ControllerName /> will scan on those first.
    </GithubAlert>
  </TabItem>

  <TabItem value="m2s">
    ## <BrandName /> <ModelHome /> (Model M2S)

    <ClickableImage src="/api/media/controller/model-m2s/model-M2S-unbranded.webp" alt="Model M2S" maxWidth="350px" border="" />

    The <BrandName /> <ModelHome /> has the following connections:

    | Connection | Use |
    | :--------- | :-- |
    | **RS485** (B, A, GND) | One RS485 port for Modbus RTU devices |
    | **DC IN** (GND, +) | 12 V DC power supply |
    | **LAN** | Ethernet connection to the local network and the internet |
    | **USB** (2x) | USB ports |

    The <BrandName /> <ModelHome /> has no digital inputs, digital outputs or relays.

    <ClickableImage src="/api/media/controller/model-m2s/model-M2S-rs485-dc-panel.webp" alt="RS485 and DC IN connectors of the Model M2S" maxWidth="550px" />

    <ClickableImage src="/api/media/controller/model-m2s/model-M2S-usb-lan-panel.webp" alt="USB and LAN connectors of the Model M2S" maxWidth="550px" />

    ## RS485

    The <BrandName /> <ModelHome /> has one RS485 port, on the terminal block marked **RS485** with the pins **B**, **A** and **GND**.


    ### Wiring

    <GithubAlert variant="tip" kind="tip">
      The color of the wires does not matter. You may choose this, as long as both the A and B are from a single twisted pair.
    </GithubAlert>

    The following guidelines apply:

    * **Cable type**:
      * You must use **shielded** cables with **twisted pairs** for optimal performance.
      * **Use a single pair** for the RS485 A and B wires (do not split them over different pairs). If there is a ground wire, use another pair for the ground wire.
      * For short distances, a twisted pair from a network cable (minimum CAT5e) can be used.
      * Avoid using SVV cables or alarm cables, as they are not suitable for these purposes.
      * The cable must have a characteristic impedance of 100 to 120 ohm.

    #### Signal Mapping

    Different manufacturers use different naming conventions (A/B, +/-, D1/D0). Use this table to match your device's signals to the <BrandName /> controller.

    <RS485ConnectionTable firstColumn={["", "", ""]} />

    * **Connecting multiple devices**: The cable must be **daisy-chained** from device to device. Place the <BrandName /> <ControllerName /> like the picture below.

    <ClickableImage src="/img/eniris/wiring_Eniris.png" alt="Image 1" maxWidth="650px" />

    * **Maximum number of devices**: The <BrandName /> <ModelHome /> supports at most 5 devices on its RS485 bus.
    * **Maximum distance**: The total cable length is limited to 1000 meters - but it is recommended to limit the maximum to 100m.
    * **Termination**: The <BrandName /> <ModelHome /> has an internal 120Ω termination resistor. Place it at one end of the daisy chain and install a 120Ω termination resistor only at the other end.
    * **Grounding the cable shield**: If the cable is shielded, then you must connect the shield to the electrical earth of the installation at one end of the cable.

    <GithubAlert variant="tip" kind="tip">
      TIP: In case of many devices

      * If you have many devices on the RS485 bus, the control system gets slower. This is because over an RS485 bus only one device can communicate at a time.
      * The <BrandName /> <ModelHome /> has one RS485 port. Connect devices that also support Modbus TCP over Ethernet instead, to keep the RS485 bus short.
    </GithubAlert>

    <GithubAlert variant="warning" kind="warning">
      Grounding shielded cables

      * Ground the shield at a single end of the cable only. Do not ground the shield at multiple points along the cable, not even the other end of the cable. If you use a daisy chain, then ground each individual cable at a single end (you may use the shield of another cable as the grounding point at the end of the cable, but this is not recommended).
      * Ground the shield to the earth ground of the electrical installation. Do not ground it to the signal ground.
    </GithubAlert>

    ### Termination resistors

    The <BrandName /> <ModelHome /> has an internal 120 ohm termination resistor, so its end of the RS485 bus is already terminated. Install a 120 ohm termination resistor only at the other end of the daisy chain.

    ### Addresses

    <GithubAlert variant="warning" kind="warning">
      You MUST give each device on the RS485 bus a unique address.
    </GithubAlert>

    <GithubAlert variant="tip" kind="tip">
      Use lower addresses first (1, 2, ...), because the <BrandName /> <ControllerName /> will find them faster!
    </GithubAlert>

    <GithubAlert variant="tip" kind="tip">
      Stick with the factory default baud rate, parity and stop bits. The <BrandName /> <ControllerName /> will scan on those first.
    </GithubAlert>
  </TabItem>
</Tabs>


# Data protection and privacy policy


# Data protection and privacy policy
You are reading version 2025-04-14.

> [!WARNING] NOTICE: When you buy from a reseller
> A reseller of the products and services of Eniris may have a different privacy policy. Nevertheless, at Eniris we apply the principles as described in this privacy policy when it comes to your data on the devices manufactured by Eniris and the servers of Eniris. A different privacy policy by a reseller only relates to the actions that your reseller itself takes with regard to your data, outside of the services and products of Eniris.

## Our commitment
> [!TIP] 
> ### Our commitment
> At Eniris, we are committed to protecting your privacy and handling your data with care and transparency. This Data Protection and Privacy Policy outlines how we collect, store, and use data in relation to our Energy Management System (EMS), app and monitoring portal.

## Key principles
- You remain the **owner** of your data at all times.
- We only store the **minimum data** required for the working of the services and products you bought, technical support and billing.
- Your data is **stored inside the EU** and **protected** according to **EU regulations**.
- Your data is stored and transmitted with modern **industry standard security practices**, such as encryption at rest, SSL secured connections, hashing and pseudonimisation.
- Eniris **only accesses your data to deliver to you the services that the EMS and Online Portal are meant for**, to provide **technical support**, for **invoicing**, and to **improve our services and products**.
- Your **data can be shared with the resellers** in the distribution chain up to and including the reseller whom you bought the services and/or products from. This data is only shared with the intention that each party can install the EMS, monitor your sites on your behalf for performance and faults etc., provide technical support and do invoicing of the services. Resellers that are not in the direct chain towards you, the end user, cannot access your data. Please refer to the privacy policy and data protection documents you received from the reseller when contracting their service or buying the product for more details.
- The **EMS may send data back to third party providers of external control signals that you have contracted** (e.g. imbalance services, ...). Eniris has no control over what the third party provider does with this data - please refer to the privacy policy and data protection documents you received from the third party when contracting their service. The EMS does not send data to third party providers of external control signals that have not been configured in the EMS.
- Eniris uses servers hosted by Hetzner ([DPA](https://www.hetzner.com/AV/DPA_en.pdf)), OVH Cloud ([Compliance](https://www.ovhcloud.com/en/compliance/)), Vultr ([Data center compliance](https://www.vultr.com/legal/compliance/#dc-compliance)) and Digital Ocean ([Security](https://www.digitalocean.com/security)). We only use servers in the EU and services that are GDPR compliant.
- Your data is **not intentionally shared with any other party**.
- Your data is **never sold** intentionally by Eniris.
- We perform **regular security checks** and submit our systems to **pentesting** by independent cybersecurity companies.

Our commercial agreements request that every one of our distributors and installers complies with the same commitments as we do, and that the terms under which they sell our products request the same of their clients, all the way until you, the end user. Likewise, each of our employees and contractors is bound by confidentiality agreements. We do not authorize that your data is shared or used for other purposes than delivering the service you bought, billing and technical support.

## How does Eniris comply with the EU general data protection regulation (GDPR)?
See https://www.canva.com/design/DAEnQSB5Qlw/view?utm_content=DAEnQSB5Qlw&utm_campaign=designshare&utm_medium=embeds&utm_source=link.

## Which data are we talking about?
### Data that is stored in the cloud
We only store data in the cloud that is needed for providing you with the app and monitoring portal, billing and technical support.

- Data of the devices you add to the EMS or portal. This is mostly energy data, but also e.g. serial numbers for identification of the device.
- The name your installer or you give to your site.
- The address where the EMS is installed. This used for weather forecasts, but may also be required if certain energy providers or external control signals are configured.
- E-mail adresses, so you can have a login for the app and monitoring portal.
- Logs of login attempts, the change of settings and configurations - to safeguard authenticity.
- The energy price formula you enter in the app or portal.
- Metadata of the devices added, such as settings, driver parameters etc.
- Diagnostic data such as internet usage of the EMS, crash logs, etc.

### Data that does not leave the EMS
- The EMS searches locally for devices on the network it is installed in - to facilitate adding them to the EMS. This data is NOT stored in the cloud. The EMS does also not access devices that are not added to it - it only searches for IP and MAC adresses so that the installer can more easily find the devices he needs to connect.
- Credentials required to access the API of certain devices. All credentials are encrypted with a key that is only known to the EMS. The encrypted credentials are synced with the server as part of device metadata, but the encryption key is not. Hence, even in case of a data breach, these credentials are safe.

## I don't want that Eniris, a distributor or an installer has access to my data
Without any access to your data, it is not possible to provide you with an app and online portal. The EMS can theoretically function standalone, but you will only be able to check it's data from your local network in a limited fashion, and the performance may be affected.

## How is the EMS added to my account? Can it be added by anyone?
- The EMS can be claimed by a distributor or installer account, and they give the end user access through a user account.
- For claiming the EMS, the installer needs to know the serial number and verification code, which requires (having had) physical access to the device.
- The EMS cannot be claimed again until the installer gives permission to do so.
- Exceptions may exist to this rule for certain distributors. Please check the terms and conditions of your reseller.

### What if I switch installer or my installer no longer exists?
Please contact your distributor or Eniris, and we will provide a suitable solution in accordance with the terms and conditions with which the device was bought.

## What about remote access to the EMS commissioning interface?
- The EMS and monitoring portal dispose of a remote configuration function, to assist in technical support and commissioning.
- You can disable the remote service connection entirely, however, this makes it impossible to provide technical support and manual updates. Depending on the terms and conditions of the sales contract with your installer and the terms of use, this may mean you will not get technical support at all.

### Is remote access to the commissioning interface safe?
Yes. Double authentication is used:
1. Remote access is done through the app or portal, so this can only be done from accounts that have access to your EMS.
2. For logging in remotely, the user must login again with his app credentials on the EMS. The EMS then verifies that the user has access rights.

It is possible to further secure remote access with two factor authentication.

Furthermore, all logins and configuration changes are logged, so in case of suspicion of malicious activity it is possible to trace the source.

### Does remote access grant access to the rest of my network?
No. Remote access only gives access to the EMS commissioning interface. Nevertheless the commissioning interface shows IP addresses and MAC addresses of the devices in your network, so that the installer can identify which devices to add to the EMS.

### Does the EMS communicate with other devices on my network?
The EMS only communicates with devices that have been added to it and it searches for the IP addresses and MAC addresses of the devices on your network (for identification of the devices that may have to be added).

## How can I download my data?
All of the graphs on the portal can be downloaded as csv files. You can also submit a request to info@eniris.be to obtain a download link for all of your data. The download link will be shared through the portal, so only you can access your data for downloading. This is subject to fair use, and for frequent download requests we refer to using our api.

## How can I delete my data?
Similarly as for downloading your data, you can submit a request to info@eniris.be, and a deletion link will be shared through the portal, so only you can confirm the deletion of your data. This is subject to fair use, and for frequent deletion requests we refer to using our api. Deletion will be done within 30 days after confirmation of the request and cannot be undone.

## How long is my data retained?
Your data is retained for at most ten years or 30 days after you cease to use the service and give notice of a deletion request. Upon non-renewal of software licenses (see the terms and conditions of sales with your reseller), the data is deleted within 90 days after the expiry of the license.

Eniris uses retention policies and automatic agreggation, so the level of detail in your data reduces over time.

## How is the EMS kept secure?
The EMS receives updates automatically, provided automatic updates are switched on in the configuration. This includes security updates.
Furthermore, no unnecessary software is installed on the EMS, to reduce the potential attack service.
The EMS configuration interface is password secured, and two factor authentication can be enabled.
Serial consoles and HDMI interfaces are blocked (on the hardware versions that allow this).

## What does all this mean for our distributors and installers?
1. Our commercial agreements request that every one of our distributors and installers complies with the same commitments as we do, and that the terms under which they sell our products request the same of their clients, all the way until the end user.

2. However, we understand that you as a distributor or installer want to focus on delivering the products and services to your clients. Hence, we provide a standard data protection agreement (DPA) and set of documents that you are free to use with your clients.




# Start here


import { ChapterLanding } from '@/components/ChapterLanding';
import { FolderOverview } from '@/components/FolderOverview';

<ChapterLanding
  chapter="legal"
  introductionLabel="Chapter introduction"
  eyebrow="Policies & agreements"
  title="Legal"
  description="Find the policies and agreements that govern Eniris products and services, including privacy information, service commitments, and the terms that apply to your use."
  highlightOne="Terms"
  highlightTwo="Privacy"
  highlightThree="Service levels"
/>

## Legal documents

This section brings together the five legal documents that define how Eniris products and services are provided and used. You can find our data protection and privacy policy, the optional EMS Service Level Agreement, the terms that apply when an EMS is installed, the contractual terms and conditions for the platform and EMS, and the terms governing their use.

Choose the document that best matches your question:

<FolderOverview folder="Legal" columns={2} />


# EMS Service Level Agreement


import CustomerOnly from '@/components/CustomerOnly';
import { CustomerDocumentNotice } from '@/components/CustomerDocument';
import { LegalDocument } from '@/components/LegalDocument';

# EMS Service Level Agreement

The Service Level Agreement is a contractual annex covering maintenance, support, incident priorities, response targets, and platform availability.

> [!NOTE]
> This Service Level Agreement applies only after internal agreement and after the associated SLA premium has been paid upfront.

<CustomerDocumentNotice
  locale="en"
  returnPath="/en/Legal/SLA"
  title="the Service Level Agreement"
  description="The full contractual text is protected. Sign in with a customer contact that has Documentation access to open it."
/>




# EMS terms of installation


import { BrandName, ControllerName, CustomerName, InsightsName, InsightsUrl } from '@site/src/components/customFields';
import Details from '@theme/Details';
import PdfLink from '@site/src/components/PdfLink';
import DownloadButton from '@site/src/components/DownloadButton';

# <BrandName /> <ControllerName /> terms of installation

Consult the terms of installation of the <BrandName /> <ControllerName /> below:
<DownloadButton file="/docs/eniris/Terms of installation version 2025-04-22.pdf" label="Download PDF File" />


# Platform & EMS terms of use


import { BrandName, ControllerName, CustomerName, InsightsName, InsightsUrl } from '@site/src/components/customFields';
import Details from '@theme/Details';
import PdfLink from '@site/src/components/PdfLink';
import DownloadButton from '@site/src/components/DownloadButton';

# Platform & <BrandName /> <ControllerName /> terms of use

Consult the terms of use of the platform and the <BrandName /> <ControllerName /> below:
<DownloadButton file="/docs/eniris/Terms of Use version 2025-04-22.pdf" label="Download PDF File" />


# Platform & EMS terms and conditions


import { BrandName, ControllerName, CustomerName, InsightsName, InsightsUrl } from '@site/src/components/customFields';
import Details from '@theme/Details';
import PdfLink from '@site/src/components/PdfLink';
import DownloadButton from '@site/src/components/DownloadButton';

# Platform & <BrandName /> <ControllerName /> terms of conditions

Consult the terms of conditions of the platform and the <BrandName /> <ControllerName /> below:
<DownloadButton file="/docs/eniris/Eniris - Algemene Voorwaarden (Gepubliceerd).pdf" label="Download PDF File" />


# Start here


import { ChapterLanding } from '@/components/ChapterLanding';
import { FolderOverview } from '@/components/FolderOverview';

<ChapterLanding
  chapter="smartgridx"
  introductionLabel="Chapter introduction"
  eyebrow="Monitoring & insights"
  title="SmartgridX - Monitoring"
  description="Operate an entire energy portfolio from one place. Follow live and historical performance, investigate assets in detail, alert the right people, automate reports, and turn technical data into insight that customers can understand."
  highlightOne="Portfolio operations"
  highlightTwo="Live & historical data"
  highlightThree="Alarms & reports"
/>

SmartgridX Monitoring brings installations, devices, measurements, users, and operational workflows together in one portal. Instead of checking every manufacturer platform separately, you can move from a portfolio-wide overview to one installation, one device, and finally the measurement that explains what is happening.

<Callout type="info" title="Your portal is configured for your organisation">
  The pages, measurements, and actions you see depend on your licence, connected assets, integrations, user role, and dashboard configuration. An administrator may therefore see more management options than an installer or end customer.
</Callout>

## What you can do

<Cards>
  <Card
    title="Monitor a complete portfolio"
    description="Group installations by site type, search across assets, switch between organisations, and use table or tile views to spot the sites that need attention."
    href="./Web%20portal/homepage"
  />
  <Card
    title="Investigate an installation"
    description="Open the device hierarchy, follow a site from its main meter down to inverters, strings, batteries, sensors, or other connected equipment, and inspect the relevant telemetry."
    href="./Web%20portal/installations"
  />
  <Card
    title="Turn exceptions into action"
    description="Create Advanced alarms rules, inspect the evidence behind each result, and notify the appropriate people when a condition opens or resolves."
    href="./Web%20portal/management/alarms"
  />
  <Card
    title="Generate repeatable reports"
    description="Use report templates for selected installations and periods, configure recipients and access, preview the result, and generate a consistent PDF."
    href="./Web%20portal/features/reports"
  />
  <Card
    title="Build public energy displays"
    description="Combine charts, values, text, and images into reusable slide templates and assign a site-specific version to a public display controller."
    href="./Web%20portal/features/infographics"
  />
  <Card
    title="Connect different data sources"
    description="Bring manufacturer platforms, meters, controllers, APIs, and uploaded historical data into the same monitoring structure."
    href="./Integrations"
  />
</Cards>

## From portfolio to measurement

The portal follows the physical structure of an energy project. This makes it possible to start with an operational question and progressively narrow the scope until you find the technical explanation.

| Level | What you learn | Typical actions |
| --- | --- | --- |
| **Portfolio** | Which sites are active, unavailable, or performing differently from the rest? | Search, filter by site type, change the table or tile layout, and open an installation. |
| **Installation** | How are production, consumption, storage, grid exchange, and other device groups interacting? | Read the site overview or synoptic diagram, check the latest refresh time, and open a device group. |
| **Device** | Which inverter, meter, battery, charger, sensor, or subsystem explains the site behaviour? | Navigate the device tree, inspect status and KPIs, and review descendants, alarms, notes, documents, and settings where available. |
| **Measurement** | When did the behaviour start and which signal changed? | Select a time range and study the available live or historical time series. |

<Callout type="idea" title="A useful investigation pattern">
  Start broad and only add detail when it answers the next question: **portfolio anomaly → installation flow → device KPI → historical signal**. This keeps a technical investigation focused and prevents a single unusual data point from being interpreted without its site context.
</Callout>

## Measurements that explain performance

SmartgridX Monitoring can present far more than a single production total. The exact selection depends on the connected hardware, but the application contains dedicated views for measurements and KPIs such as:

- active and reactive power, voltage, current, and active energy;
- battery state of charge and charge or discharge behaviour;
- irradiation, radiant exposure, and performance ratio for solar installations;
- uptime and data availability;
- temperatures, pressures, flow, and other process or environmental signals;
- energy prices, grid limits, and external control signals where these are part of the project.

These signals can be shown as current values, progress indicators, line charts, periodic bar or pie charts, data tables, or schematic SVG diagrams. Dashboards can also contain maps, explanatory text, images, links, notes, and embedded content. This allows the same platform to support a technical service dashboard, a management overview, and a simplified customer view without forcing every user to interpret the same screen.

### Questions the data can answer

| Operational question | Useful evidence in SmartgridX Monitoring |
| --- | --- |
| **Is the installation producing or consuming what we expect?** | Power and energy trends, expected-production targets, performance ratio, irradiation, and site totals. |
| **Is data still arriving?** | Last refresh information, uptime, missing-data patterns, device status, and [Advanced alarms](./Web%20portal/management/alarms/advanced-alarms). |
| **Why did grid exchange change?** | Production, load, battery SoC, active power, grid limits, prices, and external signals viewed over the same period. |
| **Is the issue site-wide or device-specific?** | The installation overview followed by device-group and individual-device drill-down. |
| **Who should act?** | Alarm viewers, notification channels, user roles, assigned contacts, and report recipients. |

## Operational workflows

### Alarms and supervision

Advanced alarms has replaced alarm watchdogs. The current workflow lets you:

1. create an alarm rule for an eligible installation;
2. review its status and open **Analysis** to inspect the supporting telemetry;
3. validate the condition and confirm that it clears after recovery;
4. configure recipients and notification frequency, with email and SMS where enabled.

Use [Advanced alarms: rules and analysis](./Web%20portal/management/alarms/advanced-alarms) for setup and notifications, and [incidents](./Web%20portal/management/incidents) for incident-surveillance configuration.

### Reports and stakeholder communication

Reports turn a recurring data request into a repeatable process. A report instance combines a template with a scope, reporting period, time zone, access rules, and delivery settings. Depending on the available templates, reports can cover one installation, a portfolio overview, production and performance, or alarm history. They can be previewed in the portal and generated as PDF files, while automation can distribute recurring reports to the configured recipients.

Read the [reports guide](./Web%20portal/features/reports) to understand templates, periods, mail configuration, visual customisation, and automation.

### Public displays

Public displays translate operational data into a format suited to visitors, employees, schools, or customers. The workflow consists of three parts:

1. **Template** — design one or more slides and position chart, value, text, or image blocks on a reusable grid.
2. **Configuration** — select the installation data for the configurable blocks, choose the orientation, and preview the result.
3. **Controller** — claim a display controller with its serial number and verification code, then link it to the required display configuration.

Start with [Getting started with public displays](./Web%20portal/features/infographics/getting-started).

## Access, structure, and branding

SmartgridX Monitoring is built for organisations in which different people need different levels of detail.

- **Users and roles:** give administrators, installers, customers, and other viewers access to the appropriate part of the device hierarchy. See [User management](./Web%20portal/management/user-management).
- **Multiple organisations and views:** authorised users can switch company or portal view without leaving the application.
- **Configurable visibility:** decide which portal functions and metrics are visible for owners and visitors. See [Dashboard settings](./Web%20portal/dashboard-settings).
- **Languages and terminology:** configure portal translations so labels match your organisation and market.
- **Whitelabel presentation:** apply a logo, colours, login page, domain, and email identity. See [Whitelabeling](./Web%20portal/whitelabeling).
- **Site context:** keep notes, links, documents, contacts, location information, and production targets with the installation instead of in a separate spreadsheet or mailbox.

## A practical first route through the portal

If SmartgridX Monitoring is new to you, follow this sequence:

1. Complete the [web portal onboarding](./Web%20portal/onboarding) and sign in.
2. Learn how to read and personalise the [homepage](./Web%20portal/homepage).
3. Open an [installation](./Web%20portal/installations) and follow the hierarchy down to a device.
4. Configure [users and roles](./Web%20portal/management/user-management) before sharing access.
5. Add [alarms](./Web%20portal/management/alarms) and [reports](./Web%20portal/features/reports) once the data flow and device structure have been verified.

## Explore all SmartgridX Monitoring documentation

<FolderOverview folder="Monitoring" />


# ABB / Aurora Vision monitoring


# ABB / Aurora Vision monitoring

SmartgridX can collect PV installation and inverter measurements from ABB / Aurora Vision, including production, status and events where these are available for the installation.

## Prepare the connection

| What to provide | Purpose |
| --- | --- |
| Aurora Vision API key | Authorizes access to the platform's monitoring data |
| Dedicated platform account | Provides access to the installations to be monitored |
| Installation IDs | Defines which installations should be included |

Make sure the platform account can access the intended installations and provide their installation IDs when setting up the connection. The connection is for **monitoring**; access to the platform does not by itself enable inverter control.

## Related guides

- [Supported solar and storage monitoring connections](/Monitoring/Integrations/Battery%20or%20PV%20inverters)
- [Connection setup guides](/Monitoring/Integrations/connections)


# APsystems monitoring


# APsystems monitoring

For the local connection described here, a controller communicates with the APsystems equipment at the installation. This is different from connecting a manufacturer cloud account.

## Choose the local connection

The [APsystems device guide](/Controller/Devices/PV-hybrid-and-battery-inverters/APsystems) lists **APstorage** and **ECU** and shows their available Ethernet and RS485 connections.

| Connection | What to prepare |
| --- | --- |
| Ethernet | Connect the controller and the equipment to the same local network. |
| RS485 | Prepare the serial connection according to the controller's RS485 wiring guidelines. |

## Set up the installation

1. Identify whether the installation uses APstorage or an ECU.
2. Open the [APsystems device guide](/Controller/Devices/PV-hybrid-and-battery-inverters/APsystems) and select the connection appropriate for that equipment.
3. Follow the [Ethernet or RS485 wiring guidelines](/Controller/wiring-best-practices).
4. After commissioning, open the installation in SmartgridX and check that the connected equipment reports measurements.

This guide covers the **local controller route**. It does not describe an APsystems cloud-account connection. Monitoring and curtailment are separate capabilities; the device guide identifies the control capabilities for each listed device.


# Diehl-Ako monitoring


# Diehl-Ako monitoring

The documented connection for **Diehl-Ako Platinum** inverters is a local **RS485** connection to the controller. This is not a manufacturer cloud-account connection.

## What to prepare

| Item | Requirement |
| --- | --- |
| Inverter | Diehl-Ako Platinum, as listed in the device guide |
| Communication | RS485 wiring between the inverter installation and the controller |
| Wiring reference | The A/B terminal mapping and connection image in the device guide |

## Set up the connection

1. Follow the [Diehl-Ako wiring instructions](/Controller/Devices/PV-hybrid-and-battery-inverters/Diehl-Ako).
2. Use the Diehl-Ako connection in the controller configuration. The integration uses automatic device recognition, so individual inverter addresses do not need to be configured.
3. After commissioning, check the installation and connected inverter measurements in SmartgridX.

Diehl-Ako uses a manufacturer-specific serial protocol rather than Modbus. Do not configure this connection as a generic Modbus TCP device.

For the supported-device table and wiring image, see the [Diehl-Ako device guide](/Controller/Devices/PV-hybrid-and-battery-inverters/Diehl-Ako).


# Fronius API


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import ClickableImage from '@site/src/components/ClickableImage';

## Overview

The Fronius API integration allows you to monitor and collect data from your Fronius solar inverters. This integration supports retrieving real-time data and historical performance metrics through Fronius Solar.web.

<ClickableImage src="/img/eniris/monitoring/integrations/manufacturer-cloud-api.webp" alt="Solar inverters and a site meter sharing selected measurements through a secured manufacturer cloud API" maxWidth="1100px" />

*The cloud platform authenticates the request and exposes the selected plant and device measurements to SmartgridX.*

## Subscription Costs

Fronius Solar.web API access requires a subscription based on the number of installations:

| Number of Installations | Monthly Cost (EUR) |
|------------------------|-------------------|
| Up to 20              | 52                |
| Up to 100             | 195               |
| Up to 400             | 494               |

For more details about the data packages and pricing, visit the [Fronius Solar.web Query API](https://www.fronius.com/en/solarweb-query-api/data-packages) page.

> [!TIP] 
> ### Alternative Solution
> To avoid subscription costs, you can set up a local FTP export from your Fronius inverter. This allows direct data collection without requiring a Solar.web subscription. Contact Eniris support for guidance on setting up FTP export.

## Setup Instructions

### 1. Generate API Credentials

1. Log in to your account at [Solar.web](https://www.solarweb.com)
2. Navigate to User Settings
3. Select REST API Settings
4. Click "Create New API Key"
   - Keep your Key ID and Secret key secure
   - These credentials are required for API authentication

### 2. Integration Setup

Once you have your API credentials, create a support ticket at [eniris.io](https://eniris.io) with the following information:

- Key ID
- Secret key
- Solar.web Username
- Solar.web Password

Our support team will configure the integration and notify you once it's complete.

### 3. Verification

After receiving confirmation from Eniris support:
1. Check your dashboard for Fronius device data
2. Verify that all expected metrics are being collected
3. Contact support if you notice any missing or incorrect data



# Fronius Integration Monitoring


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import ClickableImage from '@site/src/components/ClickableImage';

<ClickableImage src="/img/customers/fronius/logo.png" alt="logo"  maxWidth="300px"/>

## With Datamanager or SnapInverter

import Tabs from '@theme/Tabs';
import TabItem from '@theme/TabItem';

<Tabs>
  <TabItem value="datamanager" label="Datamanager">
    <ClickableImage src="/img/customers/fronius/Datamanager.png" alt="Datamanager" maxWidth="450px" />
  </TabItem>
  <TabItem value="snapinverter" label="SnapInverter">
    <ClickableImage src="/img/customers/fronius/SnapINverter.jpg" alt="SnapInverter" maxWidth="300px" />
  </TabItem>
</Tabs>

### Getting Started

1. **FTP Credentials**
   - Request FTP credentials through [Eniris Support](https://eniris.io/support).

2. **Setup Instructions**
   - [Configure Fronius FTP Push](./FtpPushForFronius.mdx)

## Without Datamanager or SnapInverter

### Connect through Modbus RTU or TCP

<Tabs>
  <TabItem value="settings" label="Modbus Settings">
    <ClickableImage src="/img/customers/fronius/SettingsModbus.jpg" alt="Modbus Settings" maxWidth="450px" />
  </TabItem>
  <TabItem value="rtu" label="RTU Connection">
    <ClickableImage src="/img/customers/fronius/RTU.png" alt="RTU Connection" maxWidth="450px" />
  </TabItem>
</Tabs>

# FTP push for Fronius

import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import ClickableImage from '@site/src/components/ClickableImage';

# Fronius FTP

## Configure FTP push through WiFi connection

Via WiFi it is possible to configure the FTP push directly via the inverters. To achieve this, the following steps must be taken:

<ClickableImage src="/img/eniris/monitoring/integrations/scheduled-file-transfer.webp" alt="A data logger packaging solar measurements into files and transferring them securely to a monitoring dashboard" maxWidth="1100px" />

*A scheduled push route depends on continuous files, correct timestamps and a reachable destination.*

1. Turn on WiFi hotspot and log in
2. Surf to the web interface
3. Configure FTP push as in FTP

## Turning on WiFi hotspot and logging in

Determine which inverter is connected to the network or to the mobile router. If current production data is visible, press the return button.

Then go to the "Setup" menu and scroll to "Wifi Access Point". Activate the WiFi Access Point, the display shows the network name and password of the WiFi network of the inverter.

To log in to the inverter, search for the WiFi network, preferably using a laptop. See the network name on the display to select the correct one. Enter the password that is visible on the display, default is "12345678". When a connection has been made, a connection to the web interface can be made.

## Surf through the webinterface

Inverter data can be consulted via the web interface. In this system, all crucial data can be retrieved from the inverters in real time. You also use this web interface for various configurations such as FTP push.

Surf to http://192.168.250.181 for the web interface.

Now you can configure the system as shown in the FTP section above.

Please pay attention to push to the /files/ folder.

### 1. Pushing data

<ClickableImage src="/img/customers/fronius/FroniusPush1.png" alt="Image" maxWidth="450px" />

### 2. Pushing errors & events

<ClickableImage src="/img/customers/fronius/FroniusPush2.png" alt="Image" maxWidth="450px" />

> [!NOTE]
> Note: port 21 must not be blocked within the network.

# Fronius Integration


import { FolderOverview } from '@/components/FolderOverview';
import ClickableImage from '@site/src/components/ClickableImage';

# Fronius Integration

Use the guide that matches the data route available at the installation. A local or push connection and a manufacturer API have different credentials, network requirements, and update behaviour.

<ClickableImage src="/img/eniris/monitoring/integrations/fronius-overview.webp" alt="A Fronius-type inverter and datamanager connected through local, file and secure cloud data routes" maxWidth="1100px" />

*The installed datamanager and available interface determine whether the project uses a local, push or cloud connection.*

Before commissioning, record the exact Fronius model and firmware, verify the connection method, and compare SmartgridX power and energy values with the inverter interface. Also check the time zone and continuity of historical data before enabling reports or alarms.

<FolderOverview folder="Monitoring/Integrations/Battery or PV inverters/Fronius integration" />


# GoodWe SEMS monitoring


# GoodWe SEMS / SEMS+ monitoring

SmartgridX can collect PV installation and inverter measurements through a GoodWe SEMS or SEMS+ platform account.

## Prepare the connection

| What to provide | Purpose |
| --- | --- |
| Dedicated SEMS account | Provides access to the monitoring platform |
| Access to the intended plants | Makes their measurements available to the connection |
| Plant allow-list | Defines which plants should be included |
| Plant time zone | Keeps measurement timestamps aligned with the installation |

Confirm that the account can see the intended plants, then identify the plants that should be included. This is a **monitoring** connection: it does not establish that remote control through the same platform is available.

## Related guides

- [Supported solar and storage monitoring connections](/Monitoring/Integrations/Battery%20or%20PV%20inverters)
- [Connection setup guides](/Monitoring/Integrations/connections)


# Huawei API


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import ClickableImage from '@site/src/components/ClickableImage';
import ClickableVideo from '@site/src/components/ClickableVideo';

<div style={{ display: 'flex', justifyContent: 'center', marginBottom: '2rem' }}>
  <img src="/img/customers/huawei/logo.png" alt="Huawei Logo" width="300px"/>
</div>

# Huawei API Integration

> [!NOTE] 
> ### Data Availability
> Reading the installation via API is free, but data is available on a minute basis every 6 hours.

<div style={{ display: 'flex', justifyContent: 'center', marginBottom: '2rem' }}>
  <ClickableImage src="/img/customers/huawei/DataShart.jpg" alt="Huawei Data Flow Chart" maxWidth="450px" />
</div>

## Installation Sharing Process

### For Fusion Solar Platform

1. Navigate to the Fusion Solar platform
2. Go to **More** → **Company Management**
3. Click on **Add User**
4. Add the following email address:
   ```
   yourcompany@eniris.be
   ```

> [!NOTE]
> Make sure to properly set up user permissions when adding the account.

### Video Tutorial

<div style={{ display: 'flex', justifyContent: 'center', marginTop: '1rem' }}>
  <ClickableVideo 
    videoSrc="/img/customers/huawei/fusion_solar.mp4" 
    alt="Huawei API Integration Tutorial" 
    maxWidth="450px" 
  />
</div>


# Huawei Local Intervention Monitoring


For a new connection, follow the [datalogger setup guide](/en/Monitoring/Integrations/datalogger-ftp/huawei). The customer or installer configures export on the logger using FTP credentials supplied by Eniris. Use the issued destination and folder settings for this connection.


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import ClickableImage from '@site/src/components/ClickableImage';

> [!NOTE]
> A local intervention requires knowledge about the data logger or inverter. In this way the data can arrive every 5 minutes.

## Local Intervention with Free Data Push

### Using Huawei SmartLogger

**Step 1:** Log in via the WebUI by navigating to the IP address:

<div style={{ display: 'flex', justifyContent: 'center', marginBottom: '2rem' }}>
  <ClickableImage src="/img/customers/huawei/Login.png" alt="WebUI Login" maxWidth="450px" />
</div>

The smartlogger can export CSV-files via FTP. These CSV-files contain production and configuration data.

To send this data, go to "Settings":

Example:
<div style={{ display: 'flex', justifyContent: 'center', marginBottom: '2rem' }}>
  <ClickableImage src="/img/customers/huawei/FTPsettings.png" alt="Settings" maxWidth="450px" />
</div>

And enter the following information:

<div className="settings-table" style={{ border: '1px solid', padding: '1rem', borderRadius: '6px', marginBottom: '1rem' }}>

- **FTP server:** `ftp2.eniris.be`
- **Username & Password** (request dedicated credentials from Eniris through the agreed secure channel)
- **Remote directory:** `/files`
- **Data export:** enable
- **File format:** Format 4
- **Filename:** minYYMMDD.csv
- **Time format:** YY-MM-DD
- **Export mode:** cycle
- **Export interval:** 5 or more
- **File mode:** Accumulated

</div>

> [!CAUTION]
> Note > Port 21 must not be blocked within the network.

# Huawei Integration


import { FolderOverview } from '@/components/FolderOverview';
import ClickableImage from '@site/src/components/ClickableImage';

# Huawei Integration

Huawei installations can require a cloud/API route or local intervention, depending on the project and the supported equipment. Choose the procedure for the actual inverter, logger, firmware, and network architecture.

<ClickableImage src="/img/eniris/monitoring/integrations/huawei-overview.webp" alt="Several Huawei-type solar inverters connected to an industrial SmartLogger with local and cloud monitoring routes" maxWidth="1100px" />

*A SmartLogger can aggregate several inverters and provide a local route as well as a route through the manufacturer platform.*

After connection, validate inverter power, energy totals, status, device grouping, and timestamps in SmartgridX Monitoring. Do not assume that access to the manufacturer portal automatically provides the credentials or permissions required by an API integration.

<FolderOverview folder="Monitoring/Integrations/Battery or PV inverters/Huawei integration" />


# Solar, batteries, heat pumps & EV charging


import ClickableImage from '@site/src/components/ClickableImage';

# Solar, batteries, heat pumps & EV charging

Use this list for assets that are monitored through a manufacturer platform, shared cloud account, API, or supported file route.

<ClickableImage src="/img/eniris/monitoring/integrations/local-device-connection.webp" alt="A PV inverter, data logger, energy meter and local controller connected to a monitoring dashboard" maxWidth="1100px" />

*A local integration can combine inverter, meter and controller data before it reaches the monitoring portal.*

<Callout type="info" title="Compatibility is verified per project">
  A listed integration means that a supported data route exists. It does not guarantee every model, firmware version, measurement, alarm, history interval, region, or control function. Eniris confirms the precise scope before commissioning.
</Callout>

| Integration | Typical monitoring scope | What Eniris needs |
| --- | --- | --- |
| **ABB / Aurora Vision** | PV sites, inverters, production, status, and events where available | API key, dedicated platform credentials, and the installation IDs to include. |
| **Ampere Energy** | Battery and site telemetry | Dedicated portal account and an allow-list of installation IDs. |
| **Anexo** | Solar installation data | Dedicated platform credentials and confirmation of the installations visible to the account. |
| **Enphase Enlighten** | PV systems, microinverters, meters, production, and consumption where available | Enphase user ID, API key or approved account access, and the system IDs to include. |
| **FIMER** | PV sites, inverters, telemetry, and alarms where available | Dedicated portal credentials, portal type, site list, and inverter or logger serial numbers. |
| **SMA Sunny Portal / ennexOS** | Plants, inverters, meters, production, and events where available | Dedicated account or approved API access, access to the intended plants, and plant identifiers. |
| **SMA file export** | Recurring CSV or XML data from supported SMA loggers and portals | Compatible logger, export destination, time zone, root account or plant mapping, and installed peak power for validation. |
| **Fronius Solar.web API** | Plants, inverters, meters, power, energy, and events where available | Solar.web API access key ID and secret, dedicated Solar.web account, plant access, and plant identifiers. |
| **Fronius file export** | JSON or TXT/FTP export from supported Fronius equipment | Compatible Datamanager or logger, export credentials supplied by Eniris, time zone, folder mapping, and upload schedule. |
| **Huawei FusionSolar API** | Plants, inverters, meters, batteries, realtime values, history, and alarms where available | Dedicated FusionSolar account or installation share, correct regional portal, and a list of plants to include. |
| **Huawei SmartLogger file export** | Recurring CSV data from supported SmartLogger installations | SmartLogger access, supported export format, FTP configuration, five-minute or agreed interval, time zone, and account mapping. |
| **SolarEdge** | Sites, inverters, meters, storage telemetry, production, consumption, and fleet alerts where available | SolarEdge API key, site IDs or account scope, site time zone, and inverter serial numbers for validation. |
| **SolisCloud** | Plants, inverters, batteries, power, energy, and alarms where available | SolisCloud API key ID and secret, approved API access, plant access, and logger or inverter serial numbers. |
| **Growatt** | Plant and inverter telemetry | Growatt account name, API key, site allow-list, time zone, and device serial numbers. |
| **GoodWe SEMS / SEMS+** | PV plants and inverter data | Dedicated SEMS account, plant access, plant allow-list, and time zone. |
| **Sungrow iSolarCloud** | PV plants, inverters, meters, batteries, and alarms where available | Dedicated iSolarCloud account, correct regional portal, plant allow-list, time zone, and device serial numbers. |
| **Sungrow XML export** | Recurring XML files from supported Sungrow routes | Export destination, time zone, root account mapping, filename convention, and delivery interval. |
| **Sofar** | Supported portal or file-based PV monitoring data | Account or export access, site identifiers, serial numbers, and time zone. |
| **SolarMAN API** | Plants, loggers, inverters, meters, and batteries where exposed | SolarMAN application ID and secret, dedicated account email and password, and plant scope. |
| **SolarMAN portal connection** | Plants and inverter telemetry | Dedicated portal account, plant access, logger serial numbers, and confirmation of the sites to include. |
| **Solar-Log** | Plants, inverter telemetry, and supported historical exports | Solar-Log URL or recurring file export, dedicated credentials when required, site allow-list, time zone, and root account mapping. |
| **Sigenergy** | Energy systems, devices, batteries, PV, grid, and load data where available | Dedicated platform account, access to the required systems, and system or device identifiers. |
| **GivEnergy** | Inverter and battery telemetry | API key, installation allow-list, and inverter or battery serial numbers. |
| **PowerRouter** | Inverter and battery portal data | Dedicated portal credentials and installation or device identifiers. |
| **Studer** | Installation and inverter/battery telemetry | Account email, platform password or delegated access, and installation number. |
| **NetEco** | Huawei-associated plant and inverter data from a supported NetEco deployment | Portal base URL, dedicated account, time zone, SSL requirements, and explicit plant allow- or deny-list. |
| **eSolar** | PV plant and inverter data | Dedicated platform account and installation allow-list. |
| **ESAJ / Elekeeper** | Supported inverter and battery platform data | Dedicated platform account, site identifiers, models, firmware, and serial numbers. |
| **Enexgroup** | Supported spreadsheet-based energy data | Representative export, customer/site mapping, units, timestamp definition, and delivery schedule. |
| **iLumen** | Supported PV platform data | Dedicated account, installation identifiers, inverter serial numbers, and confirmation of the requested measurements. |
| **Flexpond** | Supported PV and storage site data | Dedicated account, site identifiers, model/serial inventory, and source time zone. |
| **Sonnen historical recovery** | Historical battery data for supported Sonnen projects | Battery/site identity, requested historical period, account or export availability, and time zone. |
| **Solora export** | Supported recurring project export | Export route, file format sample, site/device mapping, time zone, and agreed interval. |
| **Sunrock export** | Portfolio or installation CSV data | Export folder, time zone, installation allow-list, and representative files. |
| **WebdynSun** | Supported PV logger data and file exports | Logger model and firmware, data/export access, site and inverter mapping, time zone, and sample files. |
| **NIBE** | Heat-pump systems, devices, statuses, and notifications where available | Approved NIBE API credentials or authorization code, account access, system IDs, and requested signals. |
| **Panasonic** | Supported heat-pump platform data | Dedicated platform account, system/device identifiers, model, and confirmation of accessible measurements. |
| **Etrel / INCH EV charging** | Charging-station measurements through a supported local route | Exact charger model and firmware, reachable Modbus TCP endpoint, unit/device address, register version, and network access. |

## Before requesting activation

Provide the exact manufacturer and model, firmware version, source account or installation identifiers, required measurements and alarms, expected interval, time zone, and a recent source screenshot or export. Never place passwords, API secrets, private keys, or refresh tokens in a support ticket.


# Schneider SunEzy monitoring


# Schneider SunEzy monitoring

This guide covers the local controller connection for **Schneider Electric SunEzy inverters**. It is not a Schneider cloud-account integration and does not describe every Schneider product.

## Supported equipment and connection

The [SunEzy device guide](/Controller/Devices/PV-hybrid-and-battery-inverters/Schneider%20sunezy) lists:

- SunEzy 2000, 2800 and 4000;
- SunEzy 400E;
- SunEzy 600E.

These models are documented with **RS485** communication. The guide includes terminal assignments and the individual equipment manuals. For a unit with an RS232 interface, consult its connection instructions for the required RS232-to-RS485 converter.

## Set up the connection

1. Identify the exact SunEzy model and its communication interface.
2. Follow the [SunEzy wiring instructions](/Controller/Devices/PV-hybrid-and-battery-inverters/Schneider%20sunezy).
3. Configure the local controller connection and check the inverter measurements in SmartgridX after commissioning.

The listed SunEzy models provide a monitoring connection; the device guide does **not** list curtailment support for them.

## Looking for a Schneider energy meter?

Energy meters have their own model-specific instructions. Open the [Schneider energy-meter guides](/Controller/Devices/Energy-meter/Schneider) for the appropriate PM, IEM or other meter family.


# Sma Integration


import { FolderOverview } from '@/components/FolderOverview';
import ClickableImage from '@site/src/components/ClickableImage';

# SMA integration

SMA data may be delivered through a supported API, FTP/push flow, or another project-specific connection route. Start with the integration guide that corresponds to the configured source; each route has its own credentials, refresh behaviour, and commissioning checks.

<ClickableImage src="/img/eniris/monitoring/integrations/sma-overview.webp" alt="Several SMA-type inverters connected to a data manager with scheduled file and authenticated cloud routes" maxWidth="1100px" />

*The data manager can form the bridge between the plant devices, the supported transfer route and SmartgridX.*

Confirm the installation identity and time zone, then compare current power and cumulative energy with the SMA platform. For file-based data, also review upload frequency, file continuity, and duplicate or missing intervals.

<FolderOverview folder="Monitoring/Integrations/Battery or PV inverters/SMA integration" />


# FTP Push for SMA


import ClickableImage from '@site/src/components/ClickableImage';

# FTP Push for SMA

Configure recurring export on the datalogger using dedicated FTP credentials supplied by Eniris. Start with the [SMA datalogger setup guide](/en/Monitoring/Integrations/datalogger-ftp/sma) for the required customer information, model-specific settings and first-upload checks.

<ClickableImage src="/img/eniris/monitoring/integrations/scheduled-file-transfer.webp" alt="A solar data logger collecting inverter data and transferring scheduled files to a monitoring dashboard" maxWidth="1100px" />

*The logger collects plant data, creates recurring files and forwards them through the configured network path.*

Sunny WebBox with Bluetooth supports CSV export in its FTP Push settings. The legacy Sunny WebBox manual describes XML-only FTP push. Confirm the exact model and file format with Eniris before selecting a connector. See the [Bluetooth WebBox manual](https://files.sma.de/downloads/SWebBox20-BA-en-13.pdf) and [legacy WebBox manual](https://files.sma.de/downloads/SWebBox-BA-en-36.pdf).

## Key Name Reference

When configuring the SMA FTP integration, the system uses specific key naming patterns to identify different device types and data sources. Understanding these patterns can help with troubleshooting and configuration:

### Installation Level Keys
- **Sunny WebBox**: Use "Sunny WebBox" or leave empty ("")

### Inverter Level Keys
The system recognizes inverter data using any of these key name patterns:
- Keys matching pattern: `\d+_SN.*` (digits followed by underscore and "SN")
- Keys matching pattern: `^.{2}-INV.*` (two characters, dash, then "INV")
- Keys starting with (case-insensitive):
  - `sn` 
  - `stp` 
  - `wrt` 
  - `wr`
  - `omv`
  - `inv` 
  - `core`
  - `bb omv`
  - `modbus-`
  - `ond` 

### Weather Station Keys
- **Weather Station**: Use "weerstation"

> [!TIP] 
> ### Key Naming
> These key patterns are automatically recognized by the system. Ensure your device names in the SMA WebBox follow these conventions for proper data mapping and monitoring.


## Verification and support

Follow the [upload and measurement verification procedure](/en/Monitoring/Integrations/datalogger-ftp/sma#verify-the-result). Record the logger model, firmware, filename, timestamp and exact error when requesting help.


# Sma Ftp


import { FolderOverview } from '@/components/FolderOverview';
import ClickableImage from '@site/src/components/ClickableImage';

# SMA FTP and API

These guides describe the supported SMA data routes. Use the FTP procedure only for a compatible file or push setup, and use the API procedure when the required plant is available through the supported manufacturer service.

<ClickableImage src="/img/eniris/monitoring/integrations/scheduled-file-transfer.webp" alt="A solar data logger sending scheduled measurement files through a secured transfer path" maxWidth="1100px" />

*For a file-based route, verify the complete chain from logger and export schedule to received time series.*

For FTP, verify the destination credentials, upload schedule, time zone, filename convention, and continuity of received files. For API access, verify the account permissions and plant identifier. In both cases, compare a complete day of power and energy data with the SMA source after setup.

<FolderOverview folder="Monitoring/Integrations/Battery or PV inverters/SMA integration/SMA_FTP" />


# SMA Integration Monitoring


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import ClickableImage from '@site/src/components/ClickableImage';

# SMA Integration

> [!NOTE]
> Local intervention requires knowledge about the data logger or inverter. For recurring costs, please refer to the [SMA API pricing](https://developer.sma.de/api-plans.html).

## Connection Methods

### 1. Local Intervention with Free Data Push

#### Using SMA Data Logger
If you have one of these SMA data loggers:
- Sunny Webbox
- SMA Home Manager
- SMA EnnexOS Datamanager

Follow these steps:
1. Log in to the inverter using your credentials

<ClickableImage src="/img/customers/sma/LoginSunnyExplorer.jpg" alt="Sunny Explorer Login Screen" maxWidth="450px" />
<ClickableImage src="/img/customers/sma/Login2Sunny.jpg" alt="Sunny Explorer Authentication" maxWidth="450px" />
<ClickableImage src="/img/customers/sma/Login3Sunny.png" alt="Sunny Explorer Configuration" maxWidth="450px" />

> [!NOTE]
> If you've forgotten your PUK code, contact SMA support to retrieve it.

For FTP export setup, see [FTP Push for SMA](./FTP%20Push%20for%20SMA).

#### Without SMA Data Logger

If your inverter has an RJ45 port:
- Follow the same procedure as [Using SMA Data Logger](#using-sma-data-logger)

If your inverter doesn't have an RJ45 port:
- Connect to the <BrandName/> or a compatible data logger

### 2. Remote FTP Push Setup (No API Costs)

1. Log in to ennexOS
2. Select your installation
3. Click "select device" at the top and choose the data manager
4. Navigate to "configuration"
5. Access "parameters" and configure the settings

> [!NOTE]
> Request FTP credentials by creating a ticket on https://eniris.io

### 3. SMA Cluster Controller Configuration

To set up data push to Eniris Insights:

1. Access the controller via its IP address
2. Navigate to "grid management services"
3. Configure FTP settings:
   - Server: ftp2.eniris.be
   - Username & password: Available upon request at info@eniris.be




# SMA_API


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import ClickableImage from '@site/src/components/ClickableImage';

## Remote API Integration

### Sunny Portal and EnnexOS Integration

#### If Production Data is Visible in Sunny Portal

**For Installation Owners:**
1. Access user management
2. Add yourcompanyname@eniris.be as owner and administrator
3. Notify via ticket:
   - To: [eniris.io/support](https://eniris.io/support)
<ClickableImage src="/img/customers/sma/addUser.png" alt="Sunny Portal User Management" maxWidth="450px" />
**For Non-Owners:**
1. Notify via ticket:
   - To: [eniris.io/support](https://eniris.io/support)
2. Include:
   - Subject: Integration name and method (API)
   - Any additional relevant information

> [!NOTE]
> API access requests can only be sent to the installation owner
#### If Production Data is Not Visible in Sunny Portal

Verify the data logger connection and ensure data is being recorded before proceeding with integration.


# Solar Edge Integration


import { FolderOverview } from '@/components/FolderOverview';
import ClickableImage from '@site/src/components/ClickableImage';

# SolarEdge integration

The SolarEdge integration uses the supported manufacturer data route documented below. Collect the correct site identifier and credentials, confirm that the account can access the intended installation, and note the source time zone before configuration.

<ClickableImage src="/img/eniris/monitoring/integrations/solaredge-overview.webp" alt="A SolarEdge-type inverter and site meter sending measurements through a secured cloud API to a monitoring dashboard" maxWidth="1100px" />

*The cloud connection provides monitoring data after the correct site and API access have been authorized.*

After connection, compare present power, daily energy, cumulative energy, device count, and historical continuity with the SolarEdge portal. API refresh limits mean that manufacturer-cloud data should not automatically be treated as a real-time control signal.

<FolderOverview folder="Monitoring/Integrations/Battery or PV inverters/Solar Edge integration" />


# SolarEdge API Monitoring

import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import ClickableImage from '@site/src/components/ClickableImage';
import YouTubeEmbed from '@site/src/components/YouTubeEmbed';

# SolarEdge API Integration

<div style={{ display: 'flex', justifyContent: 'center', marginBottom: '2rem' }}>
  <ClickableImage src="/img/customers/solaredge/logo.png" alt="SolarEdge Logo" maxWidth="300px"/>
</div>

> [!WARNING]
> The API is only available for Cloud controllers.

## API Key Setup

**Step 1:** Create an API key in the SolarEdge portal

<div style={{ display: 'flex', justifyContent: 'center', marginBottom: '1rem' }}>
  <ClickableImage src="/img/customers/solaredge/ApiKey.png" alt="API Key Generation" maxWidth="450px"/>
</div>

> [!WARNING]
> You must save the API key in a safe place, because you can only see it once. If you lose it, you need to create a new one.

## Installation Configuration

### Single Installation Setup

<div style={{ marginBottom: '1rem' }}>
  <YouTubeEmbed videoId="jdk4jdxequw" />
</div>

#### Share the Installation
To allow us to control an installation via the cloud, you need to:

1. Add our customer email address in the user management section in the SolarEdge portal:
   - Email format: `yourcompanyname@smartgridx.io`

2. Create a ticket on https://eniris.io and provide the following information:
   - Serial numbers of the inverters
   - Installation ID
   - API key

### Multiple Installations Setup

#### Share Information
Add our account as administrator:

Create a ticket on https://eniris.io and provide the following information:
   - API key



# SolaX monitoring


# SolaX monitoring

The connection described here uses a **local controller** to communicate with supported SolaX equipment. It does not use a SolaX Cloud account.

## Choose the correct connection

The [SolaX device guide](/Controller/Devices/PV-hybrid-and-battery-inverters/Solax) lists the supported inverter and storage families, their available connections and their control capabilities.

Depending on the equipment, the connection uses built-in Ethernet or a serial RS485 interface. An Ethernet-to-RS485 adapter provides a network connection for serial equipment; in that setup, configure the adapter's IP address rather than the inverter's IP address.

> [!WARNING]
> The COM port on a SolaX G4 inverter is not an Ethernet port. Do not connect it to an Ethernet switch. Follow the model-specific pin mapping in the device guide.

## What to prepare

| Item | Why it matters |
| --- | --- |
| Exact inverter or storage model | Determines which connection instructions apply |
| Local network address | Identifies the inverter or the Ethernet-to-RS485 adapter, depending on the connection |
| Serial settings and Modbus address | Must match the inverter when using RS485 |
| Individual addresses for multiple inverters | Allows the controller to identify each inverter on a shared RS485 bus |

## Set up and check the connection

1. Open the [SolaX device guide](/Controller/Devices/PV-hybrid-and-battery-inverters/Solax) and follow the instructions for the installed equipment.
2. Configure the corresponding local controller connection.
3. Check that measurements appear for the intended installation and equipment in SmartgridX.

For multi-inverter wiring, serial settings, the adapter connection diagram and termination instructions, use the detailed device guide. Monitoring and power control are separate capabilities: the guide identifies which control functions are available for each listed family.


# Solis Integration


import { FolderOverview } from '@/components/FolderOverview';
import ClickableImage from '@site/src/components/ClickableImage';

# Solis Integration

Choose between the supported local and API procedures according to the exact installation architecture. A local connection requires reachable equipment and correct protocol settings; an API route requires the appropriate Solis account, plant, and permissions.

<ClickableImage src="/img/eniris/monitoring/integrations/solis-overview.webp" alt="A Solis-type inverter with a Wi-Fi and LAN logger connected through a local network and a secured cloud route" maxWidth="1100px" />

*The compatible logger determines whether the inverter can be read locally over the LAN or through SolisCloud.*

Validate current power, energy totals, status, device mapping, and timestamps after configuration. When the installation contains several inverters, verify each serial number individually so that devices are not silently omitted or assigned to the wrong site.

<FolderOverview folder="Monitoring/Integrations/Battery or PV inverters/Solis integration" />


# Solis Inverter Monitoring


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import ClickableImage from '@site/src/components/ClickableImage';
import ClickableVideo from '@site/src/components/ClickableVideo';

# Local intervention

Connect to the COM port of the Solis inverter with a logger.

<ClickableImage src="/img/customers/solis/SolisComPort.png" alt="Solis Inverter" maxWidth="450px" />

> [!NOTE]
> If you are working with a LAN dongle or WiFi dongle, you can read the inverter via modbus TCP.

# Connection Options

## Data Logger Connection
Connect a data logger or smartgrid controller to enable monitoring and control capabilities.

> [!NOTE]
> Please keep in hand your Data Loggers serial number. It should be starting for 7A to enable Modbus communication.
> If the S/N starts from 5A, the connection will not work.

> [!NOTE]
> The current stable version of the Solis Data Loggers does not support Modbus Communication.
> In order to enable Modbus Communication, please contact Solis Support and ask Modbus TCP and Remote Dispatch to be enabled.

## Smartgrid Controller
Connect via Modbus RTU to the COM port of the Solis inverter.

<ClickableImage src="/img/customers/solis/solisSmartgrid.png" alt="Solis Inverter" maxWidth="450px" />

# Solis API Monitoring


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import ClickableImage from '@site/src/components/ClickableImage';
import ClickableVideo from '@site/src/components/ClickableVideo';

# Solis Cloud Integration

> [!NOTE]
> Solis dongles are needed to retrieve data from Solis Cloud (Solis' monitoring portal) via API.

<ClickableImage src="/img/customers/solis/SolisDongle.png" alt="Solis Dongle" maxWidth="450px" />

## Integration Options

### Option 1: Use Existing Solis Account
1. Fill in the form to request access to the API: https://solis-service.freshdesk.com/en/support/tickets/new
<ClickableImage src="/img/customers/solis/Afbeelding1.png" alt="Solis API Request" maxWidth="450px" />
2. Ask solis for access to the API.
3. Give us access to your Solis account with the installations you want to monitor. (optional)
4. Provide us with the API key and the Secret Key.

### Option 2: Create New Solis Account
1. Create a new account with email: yourcompany@eniris.be
2. Add the installations you want to monitor to this account.
3. Ask Solis for access to the API.   
4. Give us access to this account.
5. Fill in the form to request access to the API: https://solis-service.freshdesk.com/en/support/tickets/new
<ClickableImage src="/img/customers/solis/Afbeelding1.png" alt="Solis API Request" maxWidth="450px" />
6. Provide us with the API key and the Secret Key.


# Abb API setup


import ClickableImage from '@site/src/components/ClickableImage';

# Abb API setup

Read Abb data using the provider access configured for this connector. Confirm account permissions, installation scope and the requested measurements before activation.

<ClickableImage src="/img/eniris/monitoring/connection-guides/api-authorization.webp" alt="A privacy-safe API setup flow with authorization, limited installation scope, validation and a monitoring dashboard" maxWidth="1100px" />

*A reliable API connection combines the correct authorization method, an explicitly limited installation scope and a verified first retrieval.*

Connection type: **API and platform connection**.

## What to provide

Provide your company and contact person, the intended Insights account, the source identifiers and explicit permission for the requested scope. Include a recent source example for verification.

| Information / setting | What is needed | Supplied or configured by |
| --- | --- | --- |
| API key (API_KEY) | Obtain the key from the source account owner or provider; confirm its data permissions and share it securely. | Customer / installer |
| Account username (USERNAME) | Account name with access to the requested data. | Customer / installer |
| Account password (PASSWORD) | Share the source-account password through the secure channel agreed with Eniris. | Customer / installer |
| Installation scope (INSTALLATION_IDS) | Exact installation IDs or numbers to include. Agree explicitly before including every installation. | Customer / installer |

## Set up the connection

1. Ask the provider or account owner to enable the data access required by this connector. Confirm the permitted sites/devices and requested API version.
2. Supply the exact credential types in the table through the agreed secure channel. A portal password, API token, application secret and OAuth grant are not interchangeable.
3. Choose this connector and the target Insights account in onboarding. Enter the required fields and the authorised installation scope, then review before creating.
4. Check the first retrieval against the source account. If access succeeds but no data appears, verify site permissions, API entitlements, identifiers and the availability of measurements.

## Check the result

Check that the first collection completed, then open the intended Insights account and verify the relevant measurements or metadata. Compare source IDs, timestamps and units with the original source. Check the next scheduled execution as well. An active schedule or a healthy job alone does not prove that every requested measurement was received.

For ordinary onboarding meters, creation requests an immediate first run and keeps recurring collection active. Source publication times, upload intervals and provider limits still apply; immediate collection cannot manufacture missing source data.

## If setup does not work

Provide Eniris with the connection name, account/site scope, time of the attempt and the exact error. Check source availability and access permissions before retrying. Share a source screenshot or sample without passwords or tokens.

## Access and costs

Costs are not established for this connector. Confirm provider access, export licences and any project charges with Eniris before activation.

[All connection setup guides](/en/Monitoring/Integrations/connections)


# Add Or Remove User To Roles setup


import ClickableImage from '@site/src/components/ClickableImage';

# Add Or Remove User To Roles setup

Grant or revoke user access to existing Insights roles. This changes permissions; it does not collect meter readings.

<ClickableImage src="/img/eniris/monitoring/connection-guides/workflow-automation.webp" alt="A scheduled workflow with access control, transformation, validation, execution and an audit trail" maxWidth="1100px" />

*An automation should have a defined trigger, restricted access, validation, observable execution and a usable audit trail.*

Connection type: **Internal automation**.

## What to provide

Name the responsible Eniris operator, the approved scope and the expected outcome. Configuration and service credentials stay with the internal operator.

## Set up the connection

1. Ask the Eniris owner of this automation to agree its purpose, affected records/accounts and expected changes. This entry is not a customer meter connection.
2. The Eniris operator configures the required service access and scopes. Do not request internal administrator credentials from the customer.
3. Review a bounded test scope and its expected outcome before activation. For messaging, permission, merging or CRM workflows, the first run may change records or send messages.
4. Verify the intended action in the destination system and check for unintended changes before allowing the recurring schedule.

## Check the result

Verify the expected records or actions in the target system and the execution status. A meter dashboard may not apply. Review the effects of the first run before continuing a recurring automation.

## If setup does not work

Contact the responsible Eniris operator with the job reference, expected action and observed result. Avoid repeating a write or send action without checking whether it already happened.

[All connection setup guides](/en/Monitoring/Integrations/connections)


# Aemet API setup


import ClickableImage from '@site/src/components/ClickableImage';

# Aemet API setup

Collect Aemet weather data for the scope supported by the deployed connector. Agree the stations, variables and geographic coverage before activation.

<ClickableImage src="/img/eniris/monitoring/connection-guides/weather-data.webp" alt="A location, weather variables, time zone and forecast series feeding an energy monitoring dashboard" maxWidth="1100px" />

*Select the correct location, variables, units and time zone before comparing the collected series with the weather source.*

Connection type: **Weather data**.

## What to provide

Provide your company and contact person, the intended Insights account, the source identifiers and explicit permission for the requested scope. Include a recent source example for verification.

| Information / setting | What is needed | Supplied or configured by |
| --- | --- | --- |
| API key (KEY) | Obtain the key from the source account owner or provider; confirm its data permissions and share it securely. | Customer / installer |

## Set up the connection

1. Agree stations or coordinates, required weather variables, units, forecast versus observations and source timestamps.
2. Obtain the required provider access shown in the table and confirm the permitted dataset. Supply secrets securely.
3. Enter the exposed scope and mapping settings, if any. Eniris verifies fixed source coverage where the form offers no selector.
4. Compare the first collected period with the original source, including timestamps, time zone, units and missing intervals.

## Check the result

Check that the first collection completed, then open the intended Insights account and verify the relevant measurements or metadata. Compare source IDs, timestamps and units with the original source. Check the next scheduled execution as well. An active schedule or a healthy job alone does not prove that every requested measurement was received.

For ordinary onboarding meters, creation requests an immediate first run and keeps recurring collection active. Source publication times, upload intervals and provider limits still apply; immediate collection cannot manufacture missing source data.

## If setup does not work

Provide Eniris with the connection name, account/site scope, time of the attempt and the exact error. Check source availability and access permissions before retrying. Share a source screenshot or sample without passwords or tokens.

## Access and costs

Costs are not established for this connector. Confirm provider access, export licences and any project charges with Eniris before activation.

[All connection setup guides](/en/Monitoring/Integrations/connections)


# Ampere portal connection setup


import ClickableImage from '@site/src/components/ClickableImage';

# Ampere portal connection setup

Read measurements available through the authorised Ampere portal connection monitoring account. Only installations visible to that account can be collected.

<ClickableImage src="/img/eniris/monitoring/connection-guides/portal-access.webp" alt="A privacy-safe portal setup flow with sign-in, multi-factor authentication, installation selection and monitoring" maxWidth="1100px" />

*Confirm portal access, select only the agreed installations and complete any approval or multi-factor step before validating the data.*

Connection type: **Portal connection**.

## What to provide

Provide your company and contact person, the intended Insights account, the source identifiers and explicit permission for the requested scope. Include a recent source example for verification.

| Information / setting | What is needed | Supplied or configured by |
| --- | --- | --- |
| Account username (USERNAME) | Account name with access to the requested data. | Customer / installer |
| Account password (PASSWORD) | Share the source-account password through the secure channel agreed with Eniris. | Customer / installer |
| Installation scope (INSTALLATION_ID_ALLOW_LIST) | Exact installation IDs or numbers to include. Agree explicitly before including every installation. | Customer / installer |

## Set up the connection

1. The customer signs in to the correct provider portal and checks that the requested installations and recent measurements are visible.
2. Grant the agreed account access and supply the required account details securely. Identify any login approval or multi-factor step so Eniris can complete the authorised connection.
3. Select this connector in onboarding, choose the intended Insights account and enter the fields in the table. Restrict installation scope to the agreed list where supported.
4. Create the connection and inspect the first retrieval. A successful manual portal login does not itself prove that the collection service can read data.

## Check the result

Check that the first collection completed, then open the intended Insights account and verify the relevant measurements or metadata. Compare source IDs, timestamps and units with the original source. Check the next scheduled execution as well. An active schedule or a healthy job alone does not prove that every requested measurement was received.

For ordinary onboarding meters, creation requests an immediate first run and keeps recurring collection active. Source publication times, upload intervals and provider limits still apply; immediate collection cannot manufacture missing source data.

## If setup does not work

Provide Eniris with the connection name, account/site scope, time of the attempt and the exact error. Check source availability and access permissions before retrying. Share a source screenshot or sample without passwords or tokens.

## Access and costs

Onboarding classifies this portal connection as free. This label does not establish the terms of a separate provider subscription or equipment licence.

[All connection setup guides](/en/Monitoring/Integrations/connections)


# Anexo portal connection setup


import ClickableImage from '@site/src/components/ClickableImage';

# Anexo portal connection setup

Read measurements available through the authorised Anexo portal connection monitoring account. Only installations visible to that account can be collected.

<ClickableImage src="/img/eniris/monitoring/connection-guides/portal-access.webp" alt="A privacy-safe portal setup flow with sign-in, multi-factor authentication, installation selection and monitoring" maxWidth="1100px" />

*Confirm portal access, select only the agreed installations and complete any approval or multi-factor step before validating the data.*

Connection type: **Portal connection**.

## What to provide

Provide your company and contact person, the intended Insights account, the source identifiers and explicit permission for the requested scope. Include a recent source example for verification.

| Information / setting | What is needed | Supplied or configured by |
| --- | --- | --- |
| Account username (USERNAME) | Account name with access to the requested data. | Customer / installer |
| Account password (PASSWORD) | Share the source-account password through the secure channel agreed with Eniris. | Customer / installer |
| Time zone (TIMEZONE) | Time zone of the source timestamps, for example Europe/Brussels; identify any files already using UTC. | Customer / installer |

## Set up the connection

1. The customer signs in to the correct provider portal and checks that the requested installations and recent measurements are visible.
2. Grant the agreed account access and supply the required account details securely. Identify any login approval or multi-factor step so Eniris can complete the authorised connection.
3. Select this connector in onboarding, choose the intended Insights account and enter the fields in the table. Restrict installation scope to the agreed list where supported.
4. Create the connection and inspect the first retrieval. A successful manual portal login does not itself prove that the collection service can read data.

## Check the result

Check that the first collection completed, then open the intended Insights account and verify the relevant measurements or metadata. Compare source IDs, timestamps and units with the original source. Check the next scheduled execution as well. An active schedule or a healthy job alone does not prove that every requested measurement was received.

For ordinary onboarding meters, creation requests an immediate first run and keeps recurring collection active. Source publication times, upload intervals and provider limits still apply; immediate collection cannot manufacture missing source data.

## If setup does not work

Provide Eniris with the connection name, account/site scope, time of the attempt and the exact error. Check source availability and access permissions before retrying. Share a source screenshot or sample without passwords or tokens.

## Access and costs

Onboarding classifies this portal connection as free. This label does not establish the terms of a separate provider subscription or equipment licence.

[All connection setup guides](/en/Monitoring/Integrations/connections)


# Cadis CSV setup


import ClickableImage from '@site/src/components/ClickableImage';

# Cadis CSV setup

Import the supported Cadis CSV file format. The source must deliver files in the format expected by this connector; renaming another file to CSV does not convert it.

<ClickableImage src="/img/eniris/monitoring/connection-guides/file-import.webp" alt="A data logger creating a structured file, transferring it securely and mapping its fields to a dashboard" maxWidth="1100px" />

*File onboarding is complete only after the source export, secure delivery, field mapping and recurring arrival have all been checked.*

Connection type: **File import**.

## What to provide

Provide your company and contact person, the intended Insights account, the source identifiers and explicit permission for the requested scope. Include a recent source example for verification.

| Information / setting | What is needed | Supplied or configured by |
| --- | --- | --- |
| File / folder location (CSV_FOLDER) | Agree the delivery folder and file layout. Eniris makes it accessible to the collection service; a path on the customer laptop is insufficient. | Eniris with installer |
| Time zone (TIMEZONE) | Time zone of the source timestamps, for example Europe/Brussels; identify any files already using UTC. | Customer / installer |

## Set up the connection

1. Identify the source logger or export system and supply an original sample file. Confirm model, firmware, format and time zone with Eniris.
2. Agree the delivery route. For an Eniris FTP destination, request dedicated server, protocol, port, username, password and folder settings from Eniris. Use the agreed protocol exactly.
3. The installer or source owner enables recurring delivery. Eniris configures the accessible source location and device/field mappings; creating a meter does not configure the remote source.
4. Send a test file and record its timestamp. Eniris verifies arrival before starting collection, then compares the processed measurements with the original file.

### Configure the datalogger

The installer configures export on the datalogger using FTP credentials supplied by Eniris. Follow the [Datalogger CSV and FTP setup](https://docs.eniris.com/en/Monitoring/Integrations/datalogger-ftp) for preparation, model-specific options where documented, and the test upload. Eniris must confirm the exact model and export format for this connector.

## Check the result

Check that the first collection completed, then open the intended Insights account and verify the relevant measurements or metadata. Compare source IDs, timestamps and units with the original source. Check the next scheduled execution as well. An active schedule or a healthy job alone does not prove that every requested measurement was received.

For ordinary onboarding meters, creation requests an immediate first run and keeps recurring collection active. Source publication times, upload intervals and provider limits still apply; immediate collection cannot manufacture missing source data.

## If setup does not work

If no file arrives, inspect the logger/export status, destination, authentication, network route and folder. If files arrive but no measurements appear, provide the filename, format, source identifiers and timestamp so Eniris can check parsing and mapping.

## Access and costs

Costs are not established for this connector. Confirm provider access, export licences and any project charges with Eniris before activation.

[All connection setup guides](/en/Monitoring/Integrations/connections)


# Cast4 All API setup


import ClickableImage from '@site/src/components/ClickableImage';

# Cast4 All API setup

Read Cast4 All data using the provider access configured for this connector. Confirm account permissions, installation scope and the requested measurements before activation.

<ClickableImage src="/img/eniris/monitoring/connection-guides/api-authorization.webp" alt="A privacy-safe API setup flow with authorization, limited installation scope, validation and a monitoring dashboard" maxWidth="1100px" />

*A reliable API connection combines the correct authorization method, an explicitly limited installation scope and a verified first retrieval.*

Connection type: **API and platform connection**.

## What to provide

Provide your company and contact person, the intended Insights account, the source identifiers and explicit permission for the requested scope. Include a recent source example for verification.

| Information / setting | What is needed | Supplied or configured by |
| --- | --- | --- |
| Source endpoint (BASE_URL) | Exact endpoint for this customer or deployment; confirm it is reachable by the collection service. | Customer / installer |
| Account username (USERNAME) | Account name with access to the requested data. | Customer / installer |
| Account password (PASSWORD) | Share the source-account password through the secure channel agreed with Eniris. | Customer / installer |
| Installation scope (INSTALLATION_ID_ALLOW_LIST) | Exact installation IDs or numbers to include. Agree explicitly before including every installation. | Customer / installer |

## Set up the connection

1. Ask the provider or account owner to enable the data access required by this connector. Confirm the permitted sites/devices and requested API version.
2. Supply the exact credential types in the table through the agreed secure channel. A portal password, API token, application secret and OAuth grant are not interchangeable.
3. Choose this connector and the target Insights account in onboarding. Enter the required fields and the authorised installation scope, then review before creating.
4. Check the first retrieval against the source account. If access succeeds but no data appears, verify site permissions, API entitlements, identifiers and the availability of measurements.

## Check the result

Check that the first collection completed, then open the intended Insights account and verify the relevant measurements or metadata. Compare source IDs, timestamps and units with the original source. Check the next scheduled execution as well. An active schedule or a healthy job alone does not prove that every requested measurement was received.

For ordinary onboarding meters, creation requests an immediate first run and keeps recurring collection active. Source publication times, upload intervals and provider limits still apply; immediate collection cannot manufacture missing source data.

## If setup does not work

Provide Eniris with the connection name, account/site scope, time of the attempt and the exact error. Check source availability and access permissions before retrying. Share a source screenshot or sample without passwords or tokens.

## Access and costs

Costs are not established for this connector. Confirm provider access, export licences and any project charges with Eniris before activation.

[All connection setup guides](/en/Monitoring/Integrations/connections)


# Cds API setup


import ClickableImage from '@site/src/components/ClickableImage';

# Cds API setup

Collect Cds weather data for the scope supported by the deployed connector. Agree the stations, variables and geographic coverage before activation.

<ClickableImage src="/img/eniris/monitoring/connection-guides/weather-data.webp" alt="A location, weather variables, time zone and forecast series feeding an energy monitoring dashboard" maxWidth="1100px" />

*Select the correct location, variables, units and time zone before comparing the collected series with the weather source.*

Connection type: **Weather data**.

## Before you start

Supply the requested geographic area and an example dataset. This connector documents north/west/south/east coordinate order; Eniris must check it against the active CDS request before starting a large download.

## What to provide

Provide your company and contact person, the intended Insights account, the source identifiers and explicit permission for the requested scope. Include a recent source example for verification.

| Information / setting | What is needed | Supplied or configured by |
| --- | --- | --- |
| API key (API_KEY) | Obtain the key from the source account owner or provider; confirm its data permissions and share it securely. | Customer / installer |
| Geographic area (COORDINATES) | Requested bounding box in the coordinate order specified in this guide. | Customer / installer |
| Download location (FILEPATH) | Writable working location for downloaded data, configured on the collection service. | Eniris |

## Set up the connection

1. Agree stations or coordinates, required weather variables, units, forecast versus observations and source timestamps.
2. Obtain the required provider access shown in the table and confirm the permitted dataset. Supply secrets securely.
3. Enter the exposed scope and mapping settings, if any. Eniris verifies fixed source coverage where the form offers no selector.
4. Compare the first collected period with the original source, including timestamps, time zone, units and missing intervals.

## Check the result

Check that the first collection completed, then open the intended Insights account and verify the relevant measurements or metadata. Compare source IDs, timestamps and units with the original source. Check the next scheduled execution as well. An active schedule or a healthy job alone does not prove that every requested measurement was received.

For ordinary onboarding meters, creation requests an immediate first run and keeps recurring collection active. Source publication times, upload intervals and provider limits still apply; immediate collection cannot manufacture missing source data.

## If setup does not work

Provide Eniris with the connection name, account/site scope, time of the attempt and the exact error. Check source availability and access permissions before retrying. Share a source screenshot or sample without passwords or tokens.

## Access and costs

Costs are not established for this connector. Confirm provider access, export licences and any project charges with Eniris before activation.

[All connection setup guides](/en/Monitoring/Integrations/connections)


# Ckw setup


import ClickableImage from '@site/src/components/ClickableImage';

# Ckw setup

Collect the CKW Swiss grid-price feed.

<ClickableImage src="/img/eniris/monitoring/connection-guides/market-grid-data.webp" alt="A market area, date range, resolution and units feeding electricity price and grid charts" maxWidth="1100px" />

*Market and grid data must be scoped by area, product, time range, resolution, currency and units before the first comparison.*

Connection type: **Prices and grid data**.

## What to provide

Provide your company and contact person, the intended Insights account, the source identifiers and explicit permission for the requested scope. Include a recent source example for verification.

This connector exposes no standard customer input fields. Eniris must check the configured source, supported scope and any deployment-specific access before activation. An empty form does not mean every source or device is supported.

## Set up the connection

1. Agree market areas, price product or grid dataset, resolution, currency, units and publication date. Distinguish prices from physical meter readings.
2. Eniris checks the configured source and coverage. No customer password is requested by this connector’s current form; that does not guarantee unrestricted source access.
3. Enter the exposed scope and mapping settings, if any. Eniris verifies fixed source coverage where the form offers no selector.
4. Compare the first collected period with the original source, including timestamps, time zone, units and missing intervals.

## Check the result

Check that the first collection completed, then open the intended Insights account and verify the relevant measurements or metadata. Compare source IDs, timestamps and units with the original source. Check the next scheduled execution as well. An active schedule or a healthy job alone does not prove that every requested measurement was received.

For ordinary onboarding meters, creation requests an immediate first run and keeps recurring collection active. Source publication times, upload intervals and provider limits still apply; immediate collection cannot manufacture missing source data.

## If setup does not work

Provide Eniris with the connection name, account/site scope, time of the attempt and the exact error. Check source availability and access permissions before retrying. Share a source screenshot or sample without passwords or tokens.

## Access and costs

Costs are not established for this connector. Confirm provider access, export licences and any project charges with Eniris before activation.

[All connection setup guides](/en/Monitoring/Integrations/connections)


# Cloud Gate CSV setup


import ClickableImage from '@site/src/components/ClickableImage';

# Cloud Gate CSV setup

Import CloudGate CSV files with explicit timestamp, device-ID, field and tag mappings.

<ClickableImage src="/img/eniris/monitoring/connection-guides/file-import.webp" alt="A data logger creating a structured file, transferring it securely and mapping its fields to a dashboard" maxWidth="1100px" />

*File onboarding is complete only after the source export, secure delivery, field mapping and recurring arrival have all been checked.*

Connection type: **File import**.

## What to provide

Provide your company and contact person, the intended Insights account, the source identifiers and explicit permission for the requested scope. Include a recent source example for verification.

| Information / setting | What is needed | Supplied or configured by |
| --- | --- | --- |
| File / folder location (CSV_FOLDER) | Agree the delivery folder and file layout. Eniris makes it accessible to the collection service; a path on the customer laptop is insufficient. | Eniris with installer |
| Timestamp mapping (TIME_COLUMN) | Timestamp column and exact date/time format, including whether values are Unix timestamps. | Customer / installer |
| Timestamp mapping (TIME_FORMAT) | Timestamp column and exact date/time format, including whether values are Unix timestamps. | Customer / installer |
| Time zone (TIMEZONE) | Time zone of the source timestamps, for example Europe/Brussels; identify any files already using UTC. | Customer / installer |
| Device-ID column (NODEID_COLUMN) | Column containing a stable device ID, such as its serial number. | Customer / installer |
| Measurement mapping (TAG_COLUMNS) | Provide column definitions, units and device tags; Eniris configures the mapping from a sample file. | Eniris with customer |
| Measurement mapping (FIELD_COLUMNS) | Provide column definitions, units and device tags; Eniris configures the mapping from a sample file. | Eniris with customer |
| Measurement mapping (EXTRA_TAGS) | Provide column definitions, units and device tags; Eniris configures the mapping from a sample file. | Eniris with customer |
| Column separator (SEPARATOR) | Delimiter used by the file, for example a comma or semicolon. | Customer / installer |

## Set up the connection

1. Identify the source logger or export system and supply an original sample file. Confirm model, firmware, format and time zone with Eniris.
2. Agree the delivery route. For an Eniris FTP destination, request dedicated server, protocol, port, username, password and folder settings from Eniris. Use the agreed protocol exactly.
3. The installer or source owner enables recurring delivery. Eniris configures the accessible source location and device/field mappings; creating a meter does not configure the remote source.
4. Send a test file and record its timestamp. Eniris verifies arrival before starting collection, then compares the processed measurements with the original file.

### Configure the datalogger

The installer configures export on the datalogger using FTP credentials supplied by Eniris. Follow the [Datalogger CSV and FTP setup](https://docs.eniris.com/en/Monitoring/Integrations/datalogger-ftp) for preparation, model-specific options where documented, and the test upload. Eniris must confirm the exact model and export format for this connector.

## Check the result

Check that the first collection completed, then open the intended Insights account and verify the relevant measurements or metadata. Compare source IDs, timestamps and units with the original source. Check the next scheduled execution as well. An active schedule or a healthy job alone does not prove that every requested measurement was received.

For ordinary onboarding meters, creation requests an immediate first run and keeps recurring collection active. Source publication times, upload intervals and provider limits still apply; immediate collection cannot manufacture missing source data.

## If setup does not work

If no file arrives, inspect the logger/export status, destination, authentication, network route and folder. If files arrive but no measurements appear, provide the filename, format, source identifiers and timestamp so Eniris can check parsing and mapping.

## Access and costs

Costs are not established for this connector. Confirm provider access, export licences and any project charges with Eniris before activation.

[All connection setup guides](/en/Monitoring/Integrations/connections)


# Cloud Gate FTP setup


import ClickableImage from '@site/src/components/ClickableImage';

# Cloud Gate FTP setup

Import CloudGate files from the configured delivery source. The source account contributes to device identity, so Eniris must confirm the account mapping before activation.

<ClickableImage src="/img/eniris/monitoring/connection-guides/file-import.webp" alt="A data logger creating a structured file, transferring it securely and mapping its fields to a dashboard" maxWidth="1100px" />

*File onboarding is complete only after the source export, secure delivery, field mapping and recurring arrival have all been checked.*

Connection type: **File import**.

## What to provide

Provide your company and contact person, the intended Insights account, the source identifiers and explicit permission for the requested scope. Include a recent source example for verification.

| Information / setting | What is needed | Supplied or configured by |
| --- | --- | --- |
| Time zone (TIMEZONE) | Time zone of the source timestamps, for example Europe/Brussels; identify any files already using UTC. | Customer / installer |
| File delivery source (BROWSER) | Agree the source location and transport; Eniris configures access without putting credentials in public URLs. | Eniris with installer |

## Set up the connection

1. Identify the source logger or export system and supply an original sample file. Confirm model, firmware, format and time zone with Eniris.
2. Agree the delivery route. For an Eniris FTP destination, request dedicated server, protocol, port, username, password and folder settings from Eniris. Use the agreed protocol exactly.
3. The installer or source owner enables recurring delivery. Eniris configures the accessible source location and device/field mappings; creating a meter does not configure the remote source.
4. Send a test file and record its timestamp. Eniris verifies arrival before starting collection, then compares the processed measurements with the original file.

### Configure the datalogger

The installer configures export on the datalogger using FTP credentials supplied by Eniris. Follow the [Datalogger CSV and FTP setup](https://docs.eniris.com/en/Monitoring/Integrations/datalogger-ftp) for preparation, model-specific options where documented, and the test upload. Eniris must confirm the exact model and export format for this connector.

## Check the result

Check that the first collection completed, then open the intended Insights account and verify the relevant measurements or metadata. Compare source IDs, timestamps and units with the original source. Check the next scheduled execution as well. An active schedule or a healthy job alone does not prove that every requested measurement was received.

For ordinary onboarding meters, creation requests an immediate first run and keeps recurring collection active. Source publication times, upload intervals and provider limits still apply; immediate collection cannot manufacture missing source data.

## If setup does not work

If no file arrives, inspect the logger/export status, destination, authentication, network route and folder. If files arrive but no measurements appear, provide the filename, format, source identifiers and timestamp so Eniris can check parsing and mapping.

## Access and costs

Costs are not established for this connector. Confirm provider access, export licences and any project charges with Eniris before activation.

[All connection setup guides](/en/Monitoring/Integrations/connections)


# Cme3100 setup


import ClickableImage from '@site/src/components/ClickableImage';

# Cme3100 setup

Import the supported Cme3100 file format. The source must deliver files in the format expected by this connector; renaming another file to CSV does not convert it.

<ClickableImage src="/img/eniris/monitoring/connection-guides/file-import.webp" alt="A data logger creating a structured file, transferring it securely and mapping its fields to a dashboard" maxWidth="1100px" />

*File onboarding is complete only after the source export, secure delivery, field mapping and recurring arrival have all been checked.*

Connection type: **File import**.

## What to provide

Provide your company and contact person, the intended Insights account, the source identifiers and explicit permission for the requested scope. Include a recent source example for verification.

| Information / setting | What is needed | Supplied or configured by |
| --- | --- | --- |
| File / folder location (CSV_FOLDER) | Agree the delivery folder and file layout. Eniris makes it accessible to the collection service; a path on the customer laptop is insufficient. | Eniris with installer |
| Time zone (TIMEZONE) | Time zone of the source timestamps, for example Europe/Brussels; identify any files already using UTC. | Customer / installer |

## Set up the connection

1. Identify the source logger or export system and supply an original sample file. Confirm model, firmware, format and time zone with Eniris.
2. Agree the delivery route. For an Eniris FTP destination, request dedicated server, protocol, port, username, password and folder settings from Eniris. Use the agreed protocol exactly.
3. The installer or source owner enables recurring delivery. Eniris configures the accessible source location and device/field mappings; creating a meter does not configure the remote source.
4. Send a test file and record its timestamp. Eniris verifies arrival before starting collection, then compares the processed measurements with the original file.

## Check the result

Check that the first collection completed, then open the intended Insights account and verify the relevant measurements or metadata. Compare source IDs, timestamps and units with the original source. Check the next scheduled execution as well. An active schedule or a healthy job alone does not prove that every requested measurement was received.

For ordinary onboarding meters, creation requests an immediate first run and keeps recurring collection active. Source publication times, upload intervals and provider limits still apply; immediate collection cannot manufacture missing source data.

## If setup does not work

If no file arrives, inspect the logger/export status, destination, authentication, network route and folder. If files arrive but no measurements appear, provide the filename, format, source identifiers and timestamp so Eniris can check parsing and mapping.

## Access and costs

Costs are not established for this connector. Confirm provider access, export licences and any project charges with Eniris before activation.

[All connection setup guides](/en/Monitoring/Integrations/connections)


# controller setup


import ClickableImage from '@site/src/components/ClickableImage';

# controller setup

Collect internal controller metrics for a specified node.

<ClickableImage src="/img/eniris/monitoring/connection-guides/workflow-automation.webp" alt="A scheduled workflow with access control, transformation, validation, execution and an audit trail" maxWidth="1100px" />

*An automation should have a defined trigger, restricted access, validation, observable execution and a usable audit trail.*

Connection type: **Internal automation**.

## What to provide

Name the responsible Eniris operator, the approved scope and the expected outcome. Configuration and service credentials stay with the internal operator.

## Set up the connection

1. Ask the Eniris owner of this automation to agree its purpose, affected records/accounts and expected changes. This entry is not a customer meter connection.
2. The Eniris operator configures the required service access and scopes. Do not request internal administrator credentials from the customer.
3. Review a bounded test scope and its expected outcome before activation. For messaging, permission, merging or CRM workflows, the first run may change records or send messages.
4. Verify the intended action in the destination system and check for unintended changes before allowing the recurring schedule.

## Check the result

Verify the expected records or actions in the target system and the execution status. A meter dashboard may not apply. Review the effects of the first run before continuing a recurring automation.

## If setup does not work

Contact the responsible Eniris operator with the job reference, expected action and observed result. Avoid repeating a write or send action without checking whether it already happened.

[All connection setup guides](/en/Monitoring/Integrations/connections)


# CSV setup


import ClickableImage from '@site/src/components/ClickableImage';

# CSV setup

Import supported CSV files with explicit time parsing, device identity and measurement mapping.

<ClickableImage src="/img/eniris/monitoring/connection-guides/file-import.webp" alt="A data logger creating a structured file, transferring it securely and mapping its fields to a dashboard" maxWidth="1100px" />

*File onboarding is complete only after the source export, secure delivery, field mapping and recurring arrival have all been checked.*

Connection type: **File import**.

## What to provide

Provide your company and contact person, the intended Insights account, the source identifiers and explicit permission for the requested scope. Include a recent source example for verification.

| Information / setting | What is needed | Supplied or configured by |
| --- | --- | --- |
| File / folder location (CSV_FOLDER) | Agree the delivery folder and file layout. Eniris makes it accessible to the collection service; a path on the customer laptop is insufficient. | Eniris with installer |
| Timestamp mapping (TIME_FORMAT) | Timestamp column and exact date/time format, including whether values are Unix timestamps. | Customer / installer |
| Time zone (TIMEZONE) | Time zone of the source timestamps, for example Europe/Brussels; identify any files already using UTC. | Customer / installer |
| Device identity (DEVICE_ID) | Stable source device identifier or name and its site mapping. | Customer / installer |
| Required measurements (MEASUREMENT_FROM_DEVICE_NAME) | Signals and units to collect; Eniris configures the corresponding measurement mapping. | Eniris with customer |

## Set up the connection

1. Identify the source logger or export system and supply an original sample file. Confirm model, firmware, format and time zone with Eniris.
2. Agree the delivery route. For an Eniris FTP destination, request dedicated server, protocol, port, username, password and folder settings from Eniris. Use the agreed protocol exactly.
3. The installer or source owner enables recurring delivery. Eniris configures the accessible source location and device/field mappings; creating a meter does not configure the remote source.
4. Send a test file and record its timestamp. Eniris verifies arrival before starting collection, then compares the processed measurements with the original file.

### Configure the datalogger

The installer configures export on the datalogger using FTP credentials supplied by Eniris. Follow the [Datalogger CSV and FTP setup](https://docs.eniris.com/en/Monitoring/Integrations/datalogger-ftp) for preparation, model-specific options where documented, and the test upload. Eniris must confirm the exact model and export format for this connector.

## Check the result

Check that the first collection completed, then open the intended Insights account and verify the relevant measurements or metadata. Compare source IDs, timestamps and units with the original source. Check the next scheduled execution as well. An active schedule or a healthy job alone does not prove that every requested measurement was received.

For ordinary onboarding meters, creation requests an immediate first run and keeps recurring collection active. Source publication times, upload intervals and provider limits still apply; immediate collection cannot manufacture missing source data.

## If setup does not work

If no file arrives, inspect the logger/export status, destination, authentication, network route and folder. If files arrive but no measurements appear, provide the filename, format, source identifiers and timestamp so Eniris can check parsing and mapping.

## Access and costs

Costs are not established for this connector. Confirm provider access, export licences and any project charges with Eniris before activation.

[All connection setup guides](/en/Monitoring/Integrations/connections)


# Day Ahead Price Aggregator setup


import ClickableImage from '@site/src/components/ClickableImage';

# Day Ahead Price Aggregator setup

Combine configured day-ahead price sources using source priorities, selected countries, currencies and resolutions.

<ClickableImage src="/img/eniris/monitoring/connection-guides/market-grid-data.webp" alt="A market area, date range, resolution and units feeding electricity price and grid charts" maxWidth="1100px" />

*Market and grid data must be scoped by area, product, time range, resolution, currency and units before the first comparison.*

Connection type: **Prices and grid data**.

## What to provide

Provide your company and contact person, the intended Insights account, the source identifiers and explicit permission for the requested scope. Include a recent source example for verification.

| Information / setting | What is needed | Supplied or configured by |
| --- | --- | --- |
| Time resolutions (RESOLUTIONS) | Requested output intervals in seconds. | Customer / installer |
| Input price feeds (SOURCES) | Authorised input sources, their priorities and identifiers. Eniris configures access. | Eniris |
| Currencies (CURRENCIES) | Currencies expected for the selected price feeds. | Customer / installer |
| Country / market areas (COUNTRY_CODE_LIST) | Countries or bidding-zone identifiers for the requested dataset. | Customer / installer |

## Set up the connection

1. Agree market areas, price product or grid dataset, resolution, currency, units and publication date. Distinguish prices from physical meter readings.
2. Eniris checks the configured source and coverage. No customer password is requested by this connector’s current form; that does not guarantee unrestricted source access.
3. Enter the exposed scope and mapping settings, if any. Eniris verifies fixed source coverage where the form offers no selector.
4. Compare the first collected period with the original source, including timestamps, time zone, units and missing intervals.

## Check the result

Check that the first collection completed, then open the intended Insights account and verify the relevant measurements or metadata. Compare source IDs, timestamps and units with the original source. Check the next scheduled execution as well. An active schedule or a healthy job alone does not prove that every requested measurement was received.

For ordinary onboarding meters, creation requests an immediate first run and keeps recurring collection active. Source publication times, upload intervals and provider limits still apply; immediate collection cannot manufacture missing source data.

## If setup does not work

Provide Eniris with the connection name, account/site scope, time of the attempt and the exact error. Check source availability and access permissions before retrying. Share a source screenshot or sample without passwords or tokens.

## Access and costs

Costs are not established for this connector. Confirm provider access, export licences and any project charges with Eniris before activation.

[All connection setup guides](/en/Monitoring/Integrations/connections)


# Day Ahead Price Rolling Average setup


import ClickableImage from '@site/src/components/ClickableImage';

# Day Ahead Price Rolling Average setup

Calculate a rolling average from configured day-ahead price sources for the selected countries and time window.

<ClickableImage src="/img/eniris/monitoring/connection-guides/market-grid-data.webp" alt="A market area, date range, resolution and units feeding electricity price and grid charts" maxWidth="1100px" />

*Market and grid data must be scoped by area, product, time range, resolution, currency and units before the first comparison.*

Connection type: **Prices and grid data**.

## What to provide

Provide your company and contact person, the intended Insights account, the source identifiers and explicit permission for the requested scope. Include a recent source example for verification.

| Information / setting | What is needed | Supplied or configured by |
| --- | --- | --- |
| Input price feeds (SOURCES) | Authorised input sources, their priorities and identifiers. Eniris configures access. | Eniris |
| Averaging window (WINDOW_SIZE_HOURS) | Number of hours included in the rolling average. | Customer / installer |
| Country / market areas (COUNTRY_CODE_LIST) | Countries or bidding-zone identifiers for the requested dataset. | Customer / installer |

## Set up the connection

1. Agree market areas, price product or grid dataset, resolution, currency, units and publication date. Distinguish prices from physical meter readings.
2. Eniris checks the configured source and coverage. No customer password is requested by this connector’s current form; that does not guarantee unrestricted source access.
3. Enter the exposed scope and mapping settings, if any. Eniris verifies fixed source coverage where the form offers no selector.
4. Compare the first collected period with the original source, including timestamps, time zone, units and missing intervals.

## Check the result

Check that the first collection completed, then open the intended Insights account and verify the relevant measurements or metadata. Compare source IDs, timestamps and units with the original source. Check the next scheduled execution as well. An active schedule or a healthy job alone does not prove that every requested measurement was received.

For ordinary onboarding meters, creation requests an immediate first run and keeps recurring collection active. Source publication times, upload intervals and provider limits still apply; immediate collection cannot manufacture missing source data.

## If setup does not work

Provide Eniris with the connection name, account/site scope, time of the attempt and the exact error. Check source availability and access permissions before retrying. Share a source screenshot or sample without passwords or tokens.

## Access and costs

Costs are not established for this connector. Confirm provider access, export licences and any project charges with Eniris before activation.

[All connection setup guides](/en/Monitoring/Integrations/connections)


# Dexter API setup


import ClickableImage from '@site/src/components/ClickableImage';

# Dexter API setup

Execute configured Dexter forecast queries and combine them with an agreed actuals source in the chosen environment.

<ClickableImage src="/img/eniris/monitoring/connection-guides/api-authorization.webp" alt="A privacy-safe API setup flow with authorization, limited installation scope, validation and a monitoring dashboard" maxWidth="1100px" />

*A reliable API connection combines the correct authorization method, an explicitly limited installation scope and a verified first retrieval.*

Connection type: **API and platform connection**.

## What to provide

Provide your company and contact person, the intended Insights account, the source identifiers and explicit permission for the requested scope. Include a recent source example for verification.

| Information / setting | What is needed | Supplied or configured by |
| --- | --- | --- |
| Account username (USERNAME) | Account name with access to the requested data. | Customer / installer |
| Account password (PASSWORD) | Share the source-account password through the secure channel agreed with Eniris. | Customer / installer |
| Forecast requests (FORECAST_QUERIES) | Forecast products, asset identifiers and query scope to run. | Eniris with customer |
| Actuals data source (ACTUALS_SOURCE) | Identify the authorised source of measured data and its asset mapping. Eniris prepares its configuration. | Eniris with customer |
| Environment (ENVIRONMENT) | Confirm whether the authorised connection is for staging or production. | Customer / installer |

## Set up the connection

1. Ask the provider or account owner to enable the data access required by this connector. Confirm the permitted sites/devices and requested API version.
2. Supply the exact credential types in the table through the agreed secure channel. A portal password, API token, application secret and OAuth grant are not interchangeable.
3. Choose this connector and the target Insights account in onboarding. Enter the required fields and the authorised installation scope, then review before creating.
4. Check the first retrieval against the source account. If access succeeds but no data appears, verify site permissions, API entitlements, identifiers and the availability of measurements.

## Check the result

Check that the first collection completed, then open the intended Insights account and verify the relevant measurements or metadata. Compare source IDs, timestamps and units with the original source. Check the next scheduled execution as well. An active schedule or a healthy job alone does not prove that every requested measurement was received.

For ordinary onboarding meters, creation requests an immediate first run and keeps recurring collection active. Source publication times, upload intervals and provider limits still apply; immediate collection cannot manufacture missing source data.

## If setup does not work

Provide Eniris with the connection name, account/site scope, time of the attempt and the exact error. Check source availability and access permissions before retrying. Share a source screenshot or sample without passwords or tokens.

## Access and costs

Costs are not established for this connector. Confirm provider access, export licences and any project charges with Eniris before activation.

[All connection setup guides](/en/Monitoring/Integrations/connections)


# Ealyze API setup


import ClickableImage from '@site/src/components/ClickableImage';

# Ealyze API setup

Read Ealyze data using the provider access configured for this connector. Confirm account permissions, installation scope and the requested measurements before activation.

<ClickableImage src="/img/eniris/monitoring/connection-guides/api-authorization.webp" alt="A privacy-safe API setup flow with authorization, limited installation scope, validation and a monitoring dashboard" maxWidth="1100px" />

*A reliable API connection combines the correct authorization method, an explicitly limited installation scope and a verified first retrieval.*

Connection type: **API and platform connection**.

## What to provide

Provide your company and contact person, the intended Insights account, the source identifiers and explicit permission for the requested scope. Include a recent source example for verification.

| Information / setting | What is needed | Supplied or configured by |
| --- | --- | --- |
| Connection-point identifiers (EAN_IDS) | EAN identifiers and the corresponding customer authorisation. | Customer / installer |
| API key (API_KEY) | Obtain the key from the source account owner or provider; confirm its data permissions and share it securely. | Customer / installer |

## Set up the connection

1. Ask the provider or account owner to enable the data access required by this connector. Confirm the permitted sites/devices and requested API version.
2. Supply the exact credential types in the table through the agreed secure channel. A portal password, API token, application secret and OAuth grant are not interchangeable.
3. Choose this connector and the target Insights account in onboarding. Enter the required fields and the authorised installation scope, then review before creating.
4. Check the first retrieval against the source account. If access succeeds but no data appears, verify site permissions, API entitlements, identifiers and the availability of measurements.

## Check the result

Check that the first collection completed, then open the intended Insights account and verify the relevant measurements or metadata. Compare source IDs, timestamps and units with the original source. Check the next scheduled execution as well. An active schedule or a healthy job alone does not prove that every requested measurement was received.

For ordinary onboarding meters, creation requests an immediate first run and keeps recurring collection active. Source publication times, upload intervals and provider limits still apply; immediate collection cannot manufacture missing source data.

## If setup does not work

Provide Eniris with the connection name, account/site scope, time of the attempt and the exact error. Check source availability and access permissions before retrying. Share a source screenshot or sample without passwords or tokens.

## Access and costs

Costs are not established for this connector. Confirm provider access, export licences and any project charges with Eniris before activation.

[All connection setup guides](/en/Monitoring/Integrations/connections)


# Efento API setup


import ClickableImage from '@site/src/components/ClickableImage';

# Efento API setup

Read Efento data using the provider access configured for this connector. Confirm account permissions, installation scope and the requested measurements before activation.

<ClickableImage src="/img/eniris/monitoring/connection-guides/api-authorization.webp" alt="A privacy-safe API setup flow with authorization, limited installation scope, validation and a monitoring dashboard" maxWidth="1100px" />

*A reliable API connection combines the correct authorization method, an explicitly limited installation scope and a verified first retrieval.*

Connection type: **API and platform connection**.

## What to provide

Provide your company and contact person, the intended Insights account, the source identifiers and explicit permission for the requested scope. Include a recent source example for verification.

| Information / setting | What is needed | Supplied or configured by |
| --- | --- | --- |
| API key (API_KEY) | Obtain the key from the source account owner or provider; confirm its data permissions and share it securely. | Customer / installer |

## Set up the connection

1. Ask the provider or account owner to enable the data access required by this connector. Confirm the permitted sites/devices and requested API version.
2. Supply the exact credential types in the table through the agreed secure channel. A portal password, API token, application secret and OAuth grant are not interchangeable.
3. Choose this connector and the target Insights account in onboarding. Enter the required fields and the authorised installation scope, then review before creating.
4. Check the first retrieval against the source account. If access succeeds but no data appears, verify site permissions, API entitlements, identifiers and the availability of measurements.

## Check the result

Check that the first collection completed, then open the intended Insights account and verify the relevant measurements or metadata. Compare source IDs, timestamps and units with the original source. Check the next scheduled execution as well. An active schedule or a healthy job alone does not prove that every requested measurement was received.

For ordinary onboarding meters, creation requests an immediate first run and keeps recurring collection active. Source publication times, upload intervals and provider limits still apply; immediate collection cannot manufacture missing source data.

## If setup does not work

Provide Eniris with the connection name, account/site scope, time of the attempt and the exact error. Check source availability and access permissions before retrying. Share a source screenshot or sample without passwords or tokens.

## Access and costs

Costs are not established for this connector. Confirm provider access, export licences and any project charges with Eniris before activation.

[All connection setup guides](/en/Monitoring/Integrations/connections)


# Ekz setup


import ClickableImage from '@site/src/components/ClickableImage';

# Ekz setup

Collect the EKZ Swiss grid-price feed.

<ClickableImage src="/img/eniris/monitoring/connection-guides/market-grid-data.webp" alt="A market area, date range, resolution and units feeding electricity price and grid charts" maxWidth="1100px" />

*Market and grid data must be scoped by area, product, time range, resolution, currency and units before the first comparison.*

Connection type: **Prices and grid data**.

## What to provide

Provide your company and contact person, the intended Insights account, the source identifiers and explicit permission for the requested scope. Include a recent source example for verification.

This connector exposes no standard customer input fields. Eniris must check the configured source, supported scope and any deployment-specific access before activation. An empty form does not mean every source or device is supported.

## Set up the connection

1. Agree market areas, price product or grid dataset, resolution, currency, units and publication date. Distinguish prices from physical meter readings.
2. Eniris checks the configured source and coverage. No customer password is requested by this connector’s current form; that does not guarantee unrestricted source access.
3. Enter the exposed scope and mapping settings, if any. Eniris verifies fixed source coverage where the form offers no selector.
4. Compare the first collected period with the original source, including timestamps, time zone, units and missing intervals.

## Check the result

Check that the first collection completed, then open the intended Insights account and verify the relevant measurements or metadata. Compare source IDs, timestamps and units with the original source. Check the next scheduled execution as well. An active schedule or a healthy job alone does not prove that every requested measurement was received.

For ordinary onboarding meters, creation requests an immediate first run and keeps recurring collection active. Source publication times, upload intervals and provider limits still apply; immediate collection cannot manufacture missing source data.

## If setup does not work

Provide Eniris with the connection name, account/site scope, time of the attempt and the exact error. Check source availability and access permissions before retrying. Share a source screenshot or sample without passwords or tokens.

## Access and costs

Costs are not established for this connector. Confirm provider access, export licences and any project charges with Eniris before activation.

[All connection setup guides](/en/Monitoring/Integrations/connections)


# Elekeeper portal connection setup


import ClickableImage from '@site/src/components/ClickableImage';

# Elekeeper portal connection setup

Read measurements available through the authorised Elekeeper portal connection monitoring account. Only installations visible to that account can be collected.

<ClickableImage src="/img/eniris/monitoring/connection-guides/portal-access.webp" alt="A privacy-safe portal setup flow with sign-in, multi-factor authentication, installation selection and monitoring" maxWidth="1100px" />

*Confirm portal access, select only the agreed installations and complete any approval or multi-factor step before validating the data.*

Connection type: **Portal connection**.

## Before you start

Provide the office or organisation scope as well as the plant IDs. The connector also requires searchOfficeIdArr; Eniris can help the account owner identify that value from the authorised portal session.

## What to provide

Provide your company and contact person, the intended Insights account, the source identifiers and explicit permission for the requested scope. Include a recent source example for verification.

| Information / setting | What is needed | Supplied or configured by |
| --- | --- | --- |
| Account username (USERNAME) | Account name with access to the requested data. | Customer / installer |
| Account password (PASSWORD) | Share the source-account password through the secure channel agreed with Eniris. | Customer / installer |
| Organisation / office scope (SEARCHOFFICEIDARR) | Organisation/office identifiers associated with the requested plants. | Customer / installer |
| Installation scope (INSTALLATION_ID_ALLOW_LIST) | Exact installation IDs or numbers to include. Agree explicitly before including every installation. | Customer / installer |

## Set up the connection

1. The customer signs in to the correct provider portal and checks that the requested installations and recent measurements are visible.
2. Grant the agreed account access and supply the required account details securely. Identify any login approval or multi-factor step so Eniris can complete the authorised connection.
3. Select this connector in onboarding, choose the intended Insights account and enter the fields in the table. Restrict installation scope to the agreed list where supported.
4. Create the connection and inspect the first retrieval. A successful manual portal login does not itself prove that the collection service can read data.

## Check the result

Check that the first collection completed, then open the intended Insights account and verify the relevant measurements or metadata. Compare source IDs, timestamps and units with the original source. Check the next scheduled execution as well. An active schedule or a healthy job alone does not prove that every requested measurement was received.

For ordinary onboarding meters, creation requests an immediate first run and keeps recurring collection active. Source publication times, upload intervals and provider limits still apply; immediate collection cannot manufacture missing source data.

## If setup does not work

Provide Eniris with the connection name, account/site scope, time of the attempt and the exact error. Check source availability and access permissions before retrying. Share a source screenshot or sample without passwords or tokens.

## Access and costs

Onboarding classifies this portal connection as free. This label does not establish the terms of a separate provider subscription or equipment licence.

[All connection setup guides](/en/Monitoring/Integrations/connections)


# Elex Dam setup


import ClickableImage from '@site/src/components/ClickableImage';

# Elex Dam setup

Retrieve day-ahead prices for selected countries through Elex.

<ClickableImage src="/img/eniris/monitoring/connection-guides/market-grid-data.webp" alt="A market area, date range, resolution and units feeding electricity price and grid charts" maxWidth="1100px" />

*Market and grid data must be scoped by area, product, time range, resolution, currency and units before the first comparison.*

Connection type: **Prices and grid data**.

## What to provide

Provide your company and contact person, the intended Insights account, the source identifiers and explicit permission for the requested scope. Include a recent source example for verification.

| Information / setting | What is needed | Supplied or configured by |
| --- | --- | --- |
| API key (API_KEY) | Obtain the key from the source account owner or provider; confirm its data permissions and share it securely. | Customer / installer |
| Country / market areas (DAY_AHEAD_COUNTRY_CODE_LIST) | Countries or bidding-zone identifiers for the requested dataset. | Customer / installer |

## Set up the connection

1. Agree market areas, price product or grid dataset, resolution, currency, units and publication date. Distinguish prices from physical meter readings.
2. Obtain the required provider access shown in the table and confirm the permitted dataset. Supply secrets securely.
3. Enter the exposed scope and mapping settings, if any. Eniris verifies fixed source coverage where the form offers no selector.
4. Compare the first collected period with the original source, including timestamps, time zone, units and missing intervals.

## Check the result

Check that the first collection completed, then open the intended Insights account and verify the relevant measurements or metadata. Compare source IDs, timestamps and units with the original source. Check the next scheduled execution as well. An active schedule or a healthy job alone does not prove that every requested measurement was received.

For ordinary onboarding meters, creation requests an immediate first run and keeps recurring collection active. Source publication times, upload intervals and provider limits still apply; immediate collection cannot manufacture missing source data.

## If setup does not work

Provide Eniris with the connection name, account/site scope, time of the attempt and the exact error. Check source availability and access permissions before retrying. Share a source screenshot or sample without passwords or tokens.

## Access and costs

Costs are not established for this connector. Confirm provider access, export licences and any project charges with Eniris before activation.

[All connection setup guides](/en/Monitoring/Integrations/connections)


# Elex Prediction setup


import ClickableImage from '@site/src/components/ClickableImage';

# Elex Prediction setup

Retrieve price predictions for configured Elex regions.

<ClickableImage src="/img/eniris/monitoring/connection-guides/market-grid-data.webp" alt="A market area, date range, resolution and units feeding electricity price and grid charts" maxWidth="1100px" />

*Market and grid data must be scoped by area, product, time range, resolution, currency and units before the first comparison.*

Connection type: **Prices and grid data**.

## What to provide

Provide your company and contact person, the intended Insights account, the source identifiers and explicit permission for the requested scope. Include a recent source example for verification.

| Information / setting | What is needed | Supplied or configured by |
| --- | --- | --- |
| API key (API_KEY) | Obtain the key from the source account owner or provider; confirm its data permissions and share it securely. | Customer / installer |
| Forecast regions (REGION_LIST) | Region codes, display names and time zones for predictions. | Customer / installer |

## Set up the connection

1. Agree market areas, price product or grid dataset, resolution, currency, units and publication date. Distinguish prices from physical meter readings.
2. Obtain the required provider access shown in the table and confirm the permitted dataset. Supply secrets securely.
3. Enter the exposed scope and mapping settings, if any. Eniris verifies fixed source coverage where the form offers no selector.
4. Compare the first collected period with the original source, including timestamps, time zone, units and missing intervals.

## Check the result

Check that the first collection completed, then open the intended Insights account and verify the relevant measurements or metadata. Compare source IDs, timestamps and units with the original source. Check the next scheduled execution as well. An active schedule or a healthy job alone does not prove that every requested measurement was received.

For ordinary onboarding meters, creation requests an immediate first run and keeps recurring collection active. Source publication times, upload intervals and provider limits still apply; immediate collection cannot manufacture missing source data.

## If setup does not work

Provide Eniris with the connection name, account/site scope, time of the attempt and the exact error. Check source availability and access permissions before retrying. Share a source screenshot or sample without passwords or tokens.

## Access and costs

Costs are not established for this connector. Confirm provider access, export licences and any project charges with Eniris before activation.

[All connection setup guides](/en/Monitoring/Integrations/connections)


# Elgris API setup


import ClickableImage from '@site/src/components/ClickableImage';

# Elgris API setup

Read Elgris data using the provider access configured for this connector. Confirm account permissions, installation scope and the requested measurements before activation.

<ClickableImage src="/img/eniris/monitoring/connection-guides/api-authorization.webp" alt="A privacy-safe API setup flow with authorization, limited installation scope, validation and a monitoring dashboard" maxWidth="1100px" />

*A reliable API connection combines the correct authorization method, an explicitly limited installation scope and a verified first retrieval.*

Connection type: **API and platform connection**.

## What to provide

Provide your company and contact person, the intended Insights account, the source identifiers and explicit permission for the requested scope. Include a recent source example for verification.

| Information / setting | What is needed | Supplied or configured by |
| --- | --- | --- |
| API key (API_KEY) | Obtain the key from the source account owner or provider; confirm its data permissions and share it securely. | Customer / installer |

## Set up the connection

1. Ask the provider or account owner to enable the data access required by this connector. Confirm the permitted sites/devices and requested API version.
2. Supply the exact credential types in the table through the agreed secure channel. A portal password, API token, application secret and OAuth grant are not interchangeable.
3. Choose this connector and the target Insights account in onboarding. Enter the required fields and the authorised installation scope, then review before creating.
4. Check the first retrieval against the source account. If access succeeds but no data appears, verify site permissions, API entitlements, identifiers and the availability of measurements.

## Check the result

Check that the first collection completed, then open the intended Insights account and verify the relevant measurements or metadata. Compare source IDs, timestamps and units with the original source. Check the next scheduled execution as well. An active schedule or a healthy job alone does not prove that every requested measurement was received.

For ordinary onboarding meters, creation requests an immediate first run and keeps recurring collection active. Source publication times, upload intervals and provider limits still apply; immediate collection cannot manufacture missing source data.

## If setup does not work

Provide Eniris with the connection name, account/site scope, time of the attempt and the exact error. Check source availability and access permissions before retrying. Share a source screenshot or sample without passwords or tokens.

## Access and costs

Costs are not established for this connector. Confirm provider access, export licences and any project charges with Eniris before activation.

[All connection setup guides](/en/Monitoring/Integrations/connections)


# Elli Track CSV setup


import ClickableImage from '@site/src/components/ClickableImage';

# Elli Track CSV setup

Import the supported Elli Track CSV file format. The source must deliver files in the format expected by this connector; renaming another file to CSV does not convert it.

<ClickableImage src="/img/eniris/monitoring/connection-guides/file-import.webp" alt="A data logger creating a structured file, transferring it securely and mapping its fields to a dashboard" maxWidth="1100px" />

*File onboarding is complete only after the source export, secure delivery, field mapping and recurring arrival have all been checked.*

Connection type: **File import**.

## What to provide

Provide your company and contact person, the intended Insights account, the source identifiers and explicit permission for the requested scope. Include a recent source example for verification.

| Information / setting | What is needed | Supplied or configured by |
| --- | --- | --- |
| File delivery source (BROWSER) | Agree the source location and transport; Eniris configures access without putting credentials in public URLs. | Eniris with installer |
| Time zone (TIMEZONE) | Time zone of the source timestamps, for example Europe/Brussels; identify any files already using UTC. | Customer / installer |

## Set up the connection

1. Identify the source logger or export system and supply an original sample file. Confirm model, firmware, format and time zone with Eniris.
2. Agree the delivery route. For an Eniris FTP destination, request dedicated server, protocol, port, username, password and folder settings from Eniris. Use the agreed protocol exactly.
3. The installer or source owner enables recurring delivery. Eniris configures the accessible source location and device/field mappings; creating a meter does not configure the remote source.
4. Send a test file and record its timestamp. Eniris verifies arrival before starting collection, then compares the processed measurements with the original file.

### Configure the datalogger

The installer configures export on the datalogger using FTP credentials supplied by Eniris. Follow the [Datalogger CSV and FTP setup](https://docs.eniris.com/en/Monitoring/Integrations/datalogger-ftp) for preparation, model-specific options where documented, and the test upload. Eniris must confirm the exact model and export format for this connector.

## Check the result

Check that the first collection completed, then open the intended Insights account and verify the relevant measurements or metadata. Compare source IDs, timestamps and units with the original source. Check the next scheduled execution as well. An active schedule or a healthy job alone does not prove that every requested measurement was received.

For ordinary onboarding meters, creation requests an immediate first run and keeps recurring collection active. Source publication times, upload intervals and provider limits still apply; immediate collection cannot manufacture missing source data.

## If setup does not work

If no file arrives, inspect the logger/export status, destination, authentication, network route and folder. If files arrive but no measurements appear, provide the filename, format, source identifiers and timestamp so Eniris can check parsing and mapping.

## Access and costs

Costs are not established for this connector. Confirm provider access, export licences and any project charges with Eniris before activation.

[All connection setup guides](/en/Monitoring/Integrations/connections)


# Emb2020 API setup


import ClickableImage from '@site/src/components/ClickableImage';

# Emb2020 API setup

Read Emb2020 data using the provider access configured for this connector. Confirm account permissions, installation scope and the requested measurements before activation.

<ClickableImage src="/img/eniris/monitoring/connection-guides/api-authorization.webp" alt="A privacy-safe API setup flow with authorization, limited installation scope, validation and a monitoring dashboard" maxWidth="1100px" />

*A reliable API connection combines the correct authorization method, an explicitly limited installation scope and a verified first retrieval.*

Connection type: **API and platform connection**.

## What to provide

Provide your company and contact person, the intended Insights account, the source identifiers and explicit permission for the requested scope. Include a recent source example for verification.

| Information / setting | What is needed | Supplied or configured by |
| --- | --- | --- |
| Account username (USERNAME) | Account name with access to the requested data. | Customer / installer |
| Account password (PASSWORD) | Share the source-account password through the secure channel agreed with Eniris. | Customer / installer |

## Set up the connection

1. Ask the provider or account owner to enable the data access required by this connector. Confirm the permitted sites/devices and requested API version.
2. Supply the exact credential types in the table through the agreed secure channel. A portal password, API token, application secret and OAuth grant are not interchangeable.
3. Choose this connector and the target Insights account in onboarding. Enter the required fields and the authorised installation scope, then review before creating.
4. Check the first retrieval against the source account. If access succeeds but no data appears, verify site permissions, API entitlements, identifiers and the availability of measurements.

## Check the result

Check that the first collection completed, then open the intended Insights account and verify the relevant measurements or metadata. Compare source IDs, timestamps and units with the original source. Check the next scheduled execution as well. An active schedule or a healthy job alone does not prove that every requested measurement was received.

For ordinary onboarding meters, creation requests an immediate first run and keeps recurring collection active. Source publication times, upload intervals and provider limits still apply; immediate collection cannot manufacture missing source data.

## If setup does not work

Provide Eniris with the connection name, account/site scope, time of the attempt and the exact error. Check source availability and access permissions before retrying. Share a source screenshot or sample without passwords or tokens.

## Access and costs

Costs are not established for this connector. Confirm provider access, export licences and any project charges with Eniris before activation.

[All connection setup guides](/en/Monitoring/Integrations/connections)


# Emi API setup


import ClickableImage from '@site/src/components/ClickableImage';

# Emi API setup

Read Emi data using the provider access configured for this connector. Confirm account permissions, installation scope and the requested measurements before activation.

<ClickableImage src="/img/eniris/monitoring/connection-guides/api-authorization.webp" alt="A privacy-safe API setup flow with authorization, limited installation scope, validation and a monitoring dashboard" maxWidth="1100px" />

*A reliable API connection combines the correct authorization method, an explicitly limited installation scope and a verified first retrieval.*

Connection type: **API and platform connection**.

## What to provide

Provide your company and contact person, the intended Insights account, the source identifiers and explicit permission for the requested scope. Include a recent source example for verification.

| Information / setting | What is needed | Supplied or configured by |
| --- | --- | --- |
| API key (API_KEY) | Obtain the key from the source account owner or provider; confirm its data permissions and share it securely. | Customer / installer |
| Time zone (TIMEZONE) | Time zone of the source timestamps, for example Europe/Brussels; identify any files already using UTC. | Customer / installer |
| Installation scope (INSTALLATION_ID_ALLOW_LIST) | Exact installation IDs or numbers to include. Agree explicitly before including every installation. | Customer / installer |

## Set up the connection

1. Ask the provider or account owner to enable the data access required by this connector. Confirm the permitted sites/devices and requested API version.
2. Supply the exact credential types in the table through the agreed secure channel. A portal password, API token, application secret and OAuth grant are not interchangeable.
3. Choose this connector and the target Insights account in onboarding. Enter the required fields and the authorised installation scope, then review before creating.
4. Check the first retrieval against the source account. If access succeeds but no data appears, verify site permissions, API entitlements, identifiers and the availability of measurements.

## Check the result

Check that the first collection completed, then open the intended Insights account and verify the relevant measurements or metadata. Compare source IDs, timestamps and units with the original source. Check the next scheduled execution as well. An active schedule or a healthy job alone does not prove that every requested measurement was received.

For ordinary onboarding meters, creation requests an immediate first run and keeps recurring collection active. Source publication times, upload intervals and provider limits still apply; immediate collection cannot manufacture missing source data.

## If setup does not work

Provide Eniris with the connection name, account/site scope, time of the attempt and the exact error. Check source availability and access permissions before retrying. Share a source screenshot or sample without passwords or tokens.

## Access and costs

Costs are not established for this connector. Confirm provider access, export licences and any project charges with Eniris before activation.

[All connection setup guides](/en/Monitoring/Integrations/connections)


# Enercon portal connection setup


import ClickableImage from '@site/src/components/ClickableImage';

# Enercon portal connection setup

Read measurements available through the authorised Enercon portal connection monitoring account. Only installations visible to that account can be collected.

<ClickableImage src="/img/eniris/monitoring/connection-guides/portal-access.webp" alt="A privacy-safe portal setup flow with sign-in, multi-factor authentication, installation selection and monitoring" maxWidth="1100px" />

*Confirm portal access, select only the agreed installations and complete any approval or multi-factor step before validating the data.*

Connection type: **Portal connection**.

## What to provide

Provide your company and contact person, the intended Insights account, the source identifiers and explicit permission for the requested scope. Include a recent source example for verification.

| Information / setting | What is needed | Supplied or configured by |
| --- | --- | --- |
| Account username (USERNAME) | Account name with access to the requested data. | Customer / installer |
| Account password (PASSWORD) | Share the source-account password through the secure channel agreed with Eniris. | Customer / installer |
| Turbine scope (TID_ALLOW_LIST) | Turbine identifiers and the explicit list to include or exclude. | Customer / installer |

## Set up the connection

1. The customer signs in to the correct provider portal and checks that the requested installations and recent measurements are visible.
2. Grant the agreed account access and supply the required account details securely. Identify any login approval or multi-factor step so Eniris can complete the authorised connection.
3. Select this connector in onboarding, choose the intended Insights account and enter the fields in the table. Restrict installation scope to the agreed list where supported.
4. Create the connection and inspect the first retrieval. A successful manual portal login does not itself prove that the collection service can read data.

## Check the result

Check that the first collection completed, then open the intended Insights account and verify the relevant measurements or metadata. Compare source IDs, timestamps and units with the original source. Check the next scheduled execution as well. An active schedule or a healthy job alone does not prove that every requested measurement was received.

For ordinary onboarding meters, creation requests an immediate first run and keeps recurring collection active. Source publication times, upload intervals and provider limits still apply; immediate collection cannot manufacture missing source data.

## If setup does not work

Provide Eniris with the connection name, account/site scope, time of the attempt and the exact error. Check source availability and access permissions before retrying. Share a source screenshot or sample without passwords or tokens.

## Access and costs

Onboarding classifies this portal connection as free. This label does not establish the terms of a separate provider subscription or equipment licence.

[All connection setup guides](/en/Monitoring/Integrations/connections)


# Enexgroup Xlsx setup


import ClickableImage from '@site/src/components/ClickableImage';

# Enexgroup Xlsx setup

Read Enexgroup day-ahead prices from the spreadsheet source used by this connector.

<ClickableImage src="/img/eniris/monitoring/connection-guides/market-grid-data.webp" alt="A market area, date range, resolution and units feeding electricity price and grid charts" maxWidth="1100px" />

*Market and grid data must be scoped by area, product, time range, resolution, currency and units before the first comparison.*

Connection type: **Prices and grid data**.

## What to provide

Provide your company and contact person, the intended Insights account, the source identifiers and explicit permission for the requested scope. Include a recent source example for verification.

This connector exposes no standard customer input fields. Eniris must check the configured source, supported scope and any deployment-specific access before activation. An empty form does not mean every source or device is supported.

## Set up the connection

1. Agree market areas, price product or grid dataset, resolution, currency, units and publication date. Distinguish prices from physical meter readings.
2. Eniris checks the configured source and coverage. No customer password is requested by this connector’s current form; that does not guarantee unrestricted source access.
3. Enter the exposed scope and mapping settings, if any. Eniris verifies fixed source coverage where the form offers no selector.
4. Compare the first collected period with the original source, including timestamps, time zone, units and missing intervals.

## Check the result

Check that the first collection completed, then open the intended Insights account and verify the relevant measurements or metadata. Compare source IDs, timestamps and units with the original source. Check the next scheduled execution as well. An active schedule or a healthy job alone does not prove that every requested measurement was received.

For ordinary onboarding meters, creation requests an immediate first run and keeps recurring collection active. Source publication times, upload intervals and provider limits still apply; immediate collection cannot manufacture missing source data.

## If setup does not work

Provide Eniris with the connection name, account/site scope, time of the attempt and the exact error. Check source availability and access permissions before retrying. Share a source screenshot or sample without passwords or tokens.

## Access and costs

Costs are not established for this connector. Confirm provider access, export licences and any project charges with Eniris before activation.

[All connection setup guides](/en/Monitoring/Integrations/connections)


# Eniris Electricity Excel setup


import ClickableImage from '@site/src/components/ClickableImage';

# Eniris Electricity Excel setup

Import supported electricity spreadsheet files with site-folder mapping and a defined time zone.

<ClickableImage src="/img/eniris/monitoring/connection-guides/file-import.webp" alt="A data logger creating a structured file, transferring it securely and mapping its fields to a dashboard" maxWidth="1100px" />

*File onboarding is complete only after the source export, secure delivery, field mapping and recurring arrival have all been checked.*

Connection type: **File import**.

## What to provide

Provide your company and contact person, the intended Insights account, the source identifiers and explicit permission for the requested scope. Include a recent source example for verification.

| Information / setting | What is needed | Supplied or configured by |
| --- | --- | --- |
| File delivery source (BROWSER) | Agree the source location and transport; Eniris configures access without putting credentials in public URLs. | Eniris with installer |
| Time zone (TIMEZONE) | Time zone of the source timestamps, for example Europe/Brussels; identify any files already using UTC. | Customer / installer |

## Set up the connection

1. Identify the source logger or export system and supply an original sample file. Confirm model, firmware, format and time zone with Eniris.
2. Agree the delivery route. For an Eniris FTP destination, request dedicated server, protocol, port, username, password and folder settings from Eniris. Use the agreed protocol exactly.
3. The installer or source owner enables recurring delivery. Eniris configures the accessible source location and device/field mappings; creating a meter does not configure the remote source.
4. Send a test file and record its timestamp. Eniris verifies arrival before starting collection, then compares the processed measurements with the original file.

## Check the result

Check that the first collection completed, then open the intended Insights account and verify the relevant measurements or metadata. Compare source IDs, timestamps and units with the original source. Check the next scheduled execution as well. An active schedule or a healthy job alone does not prove that every requested measurement was received.

For ordinary onboarding meters, creation requests an immediate first run and keeps recurring collection active. Source publication times, upload intervals and provider limits still apply; immediate collection cannot manufacture missing source data.

## If setup does not work

If no file arrives, inspect the logger/export status, destination, authentication, network route and folder. If files arrive but no measurements appear, provide the filename, format, source identifiers and timestamp so Eniris can check parsing and mapping.

## Access and costs

Costs are not established for this connector. Confirm provider access, export licences and any project charges with Eniris before activation.

[All connection setup guides](/en/Monitoring/Integrations/connections)


# Eniscope API setup


import ClickableImage from '@site/src/components/ClickableImage';

# Eniscope API setup

Read Eniscope data using the provider access configured for this connector. Confirm account permissions, installation scope and the requested measurements before activation.

<ClickableImage src="/img/eniris/monitoring/connection-guides/api-authorization.webp" alt="A privacy-safe API setup flow with authorization, limited installation scope, validation and a monitoring dashboard" maxWidth="1100px" />

*A reliable API connection combines the correct authorization method, an explicitly limited installation scope and a verified first retrieval.*

Connection type: **API and platform connection**.

## Before you start

The installation selection corresponds to Eniscope organisations. Include the organisation IDs and the device/channel mapping.

## What to provide

Provide your company and contact person, the intended Insights account, the source identifiers and explicit permission for the requested scope. Include a recent source example for verification.

| Information / setting | What is needed | Supplied or configured by |
| --- | --- | --- |
| API key (X-Eniscope-API) | Obtain the key from the source account owner or provider; confirm its data permissions and share it securely. | Customer / installer |
| Account username (USERNAME) | Account name with access to the requested data. | Customer / installer |
| Account password (PASSWORD) | Share the source-account password through the secure channel agreed with Eniris. | Customer / installer |
| Installation scope (INSTALLATION_ID_ALLOW_LIST) | Exact installation IDs or numbers to include. Agree explicitly before including every installation. | Customer / installer |

## Set up the connection

1. Ask the provider or account owner to enable the data access required by this connector. Confirm the permitted sites/devices and requested API version.
2. Supply the exact credential types in the table through the agreed secure channel. A portal password, API token, application secret and OAuth grant are not interchangeable.
3. Choose this connector and the target Insights account in onboarding. Enter the required fields and the authorised installation scope, then review before creating.
4. Check the first retrieval against the source account. If access succeeds but no data appears, verify site permissions, API entitlements, identifiers and the availability of measurements.

## Check the result

Check that the first collection completed, then open the intended Insights account and verify the relevant measurements or metadata. Compare source IDs, timestamps and units with the original source. Check the next scheduled execution as well. An active schedule or a healthy job alone does not prove that every requested measurement was received.

For ordinary onboarding meters, creation requests an immediate first run and keeps recurring collection active. Source publication times, upload intervals and provider limits still apply; immediate collection cannot manufacture missing source data.

## If setup does not work

Provide Eniris with the connection name, account/site scope, time of the attempt and the exact error. Check source availability and access permissions before retrying. Share a source screenshot or sample without passwords or tokens.

## Access and costs

Costs are not established for this connector. Confirm provider access, export licences and any project charges with Eniris before activation.

[All connection setup guides](/en/Monitoring/Integrations/connections)


# Ennex Os portal connection setup


import ClickableImage from '@site/src/components/ClickableImage';

# Ennex Os portal connection setup

Read measurements available through the authorised Ennex Os portal connection monitoring account. Only installations visible to that account can be collected.

<ClickableImage src="/img/eniris/monitoring/connection-guides/portal-access.webp" alt="A privacy-safe portal setup flow with sign-in, multi-factor authentication, installation selection and monitoring" maxWidth="1100px" />

*Confirm portal access, select only the agreed installations and complete any approval or multi-factor step before validating the data.*

Connection type: **Portal connection**.

## What to provide

Provide your company and contact person, the intended Insights account, the source identifiers and explicit permission for the requested scope. Include a recent source example for verification.

| Information / setting | What is needed | Supplied or configured by |
| --- | --- | --- |
| Account username (USERNAME) | Account name with access to the requested data. | Customer / installer |
| Account password (PASSWORD) | Share the source-account password through the secure channel agreed with Eniris. | Customer / installer |

## Set up the connection

1. The customer signs in to the correct provider portal and checks that the requested installations and recent measurements are visible.
2. Grant the agreed account access and supply the required account details securely. Identify any login approval or multi-factor step so Eniris can complete the authorised connection.
3. Select this connector in onboarding, choose the intended Insights account and enter the fields in the table. Restrict installation scope to the agreed list where supported.
4. Create the connection and inspect the first retrieval. A successful manual portal login does not itself prove that the collection service can read data.

## Check the result

Check that the first collection completed, then open the intended Insights account and verify the relevant measurements or metadata. Compare source IDs, timestamps and units with the original source. Check the next scheduled execution as well. An active schedule or a healthy job alone does not prove that every requested measurement was received.

For ordinary onboarding meters, creation requests an immediate first run and keeps recurring collection active. Source publication times, upload intervals and provider limits still apply; immediate collection cannot manufacture missing source data.

## If setup does not work

Provide Eniris with the connection name, account/site scope, time of the attempt and the exact error. Check source availability and access permissions before retrying. Share a source screenshot or sample without passwords or tokens.

## Access and costs

Onboarding classifies this portal connection as free. This label does not establish the terms of a separate provider subscription or equipment licence.

[All connection setup guides](/en/Monitoring/Integrations/connections)


# Enphase API setup


import ClickableImage from '@site/src/components/ClickableImage';

# Enphase API setup

Read Enphase data using the provider access configured for this connector. Confirm account permissions, installation scope and the requested measurements before activation.

<ClickableImage src="/img/eniris/monitoring/connection-guides/api-authorization.webp" alt="A privacy-safe API setup flow with authorization, limited installation scope, validation and a monitoring dashboard" maxWidth="1100px" />

*A reliable API connection combines the correct authorization method, an explicitly limited installation scope and a verified first retrieval.*

Connection type: **API and platform connection**.

## Before you start

This deployed connector asks for a user ID and API key. Enphase API v4 uses OAuth authorisation: do not assume new v4 credentials can be pasted into this older credential shape. Eniris must check the account and API version first. [Enphase developer documentation](https://developer-v4.enphase.com/docs/quickstart.html).

## What to provide

Provide your company and contact person, the intended Insights account, the source identifiers and explicit permission for the requested scope. Include a recent source example for verification.

| Information / setting | What is needed | Supplied or configured by |
| --- | --- | --- |
| User ID (USER_ID) | Provider user identifier; confirm it belongs to the account granting data access. | Customer / installer |
| API key (API_KEY) | Obtain the key from the source account owner or provider; confirm its data permissions and share it securely. | Customer / installer |
| Installation scope (INSTALLATION_ID_ALLOW_LIST) | Exact installation IDs or numbers to include. Agree explicitly before including every installation. | Customer / installer |

## Set up the connection

1. Ask the provider or account owner to enable the data access required by this connector. Confirm the permitted sites/devices and requested API version.
2. Supply the exact credential types in the table through the agreed secure channel. A portal password, API token, application secret and OAuth grant are not interchangeable.
3. Choose this connector and the target Insights account in onboarding. Enter the required fields and the authorised installation scope, then review before creating.
4. Check the first retrieval against the source account. If access succeeds but no data appears, verify site permissions, API entitlements, identifiers and the availability of measurements.

## Check the result

Check that the first collection completed, then open the intended Insights account and verify the relevant measurements or metadata. Compare source IDs, timestamps and units with the original source. Check the next scheduled execution as well. An active schedule or a healthy job alone does not prove that every requested measurement was received.

For ordinary onboarding meters, creation requests an immediate first run and keeps recurring collection active. Source publication times, upload intervals and provider limits still apply; immediate collection cannot manufacture missing source data.

## If setup does not work

Provide Eniris with the connection name, account/site scope, time of the attempt and the exact error. Check source availability and access permissions before retrying. Share a source screenshot or sample without passwords or tokens.

## Access and costs

Onboarding classifies this API route as paid. Confirm the applicable provider access and commercial agreement before activation.

[All connection setup guides](/en/Monitoring/Integrations/connections)


# Enphase portal connection setup


import ClickableImage from '@site/src/components/ClickableImage';

# Enphase portal connection setup

Read measurements available through the authorised Enphase portal connection monitoring account. Only installations visible to that account can be collected.

<ClickableImage src="/img/eniris/monitoring/connection-guides/portal-access.webp" alt="A privacy-safe portal setup flow with sign-in, multi-factor authentication, installation selection and monitoring" maxWidth="1100px" />

*Confirm portal access, select only the agreed installations and complete any approval or multi-factor step before validating the data.*

Connection type: **Portal connection**.

## What to provide

Provide your company and contact person, the intended Insights account, the source identifiers and explicit permission for the requested scope. Include a recent source example for verification.

| Information / setting | What is needed | Supplied or configured by |
| --- | --- | --- |
| Account username (USERNAME) | Account name with access to the requested data. | Customer / installer |
| Account password (PASSWORD) | Share the source-account password through the secure channel agreed with Eniris. | Customer / installer |
| Installation scope (INSTALLATION_ID_ALLOW_LIST) | Exact installation IDs or numbers to include. Agree explicitly before including every installation. | Customer / installer |

## Set up the connection

1. The customer signs in to the correct provider portal and checks that the requested installations and recent measurements are visible.
2. Grant the agreed account access and supply the required account details securely. Identify any login approval or multi-factor step so Eniris can complete the authorised connection.
3. Select this connector in onboarding, choose the intended Insights account and enter the fields in the table. Restrict installation scope to the agreed list where supported.
4. Create the connection and inspect the first retrieval. A successful manual portal login does not itself prove that the collection service can read data.

## Check the result

Check that the first collection completed, then open the intended Insights account and verify the relevant measurements or metadata. Compare source IDs, timestamps and units with the original source. Check the next scheduled execution as well. An active schedule or a healthy job alone does not prove that every requested measurement was received.

For ordinary onboarding meters, creation requests an immediate first run and keeps recurring collection active. Source publication times, upload intervals and provider limits still apply; immediate collection cannot manufacture missing source data.

## If setup does not work

Provide Eniris with the connection name, account/site scope, time of the attempt and the exact error. Check source availability and access permissions before retrying. Share a source screenshot or sample without passwords or tokens.

## Access and costs

Onboarding classifies this portal connection as free. This label does not establish the terms of a separate provider subscription or equipment licence.

[All connection setup guides](/en/Monitoring/Integrations/connections)


# Entsoe API setup


import ClickableImage from '@site/src/components/ClickableImage';

# Entsoe API setup

Collect Entsoe market or grid-reference data. Agree the market area, product, units, currency and publication period before using the values in reports.

<ClickableImage src="/img/eniris/monitoring/connection-guides/market-grid-data.webp" alt="A market area, date range, resolution and units feeding electricity price and grid charts" maxWidth="1100px" />

*Market and grid data must be scoped by area, product, time range, resolution, currency and units before the first comparison.*

Connection type: **Prices and grid data**.

## What to provide

Provide your company and contact person, the intended Insights account, the source identifiers and explicit permission for the requested scope. Include a recent source example for verification.

| Information / setting | What is needed | Supplied or configured by |
| --- | --- | --- |
| Access token (TOKEN) | Provider-issued token with access to the required data; share securely and record who maintains it. | Customer / installer |
| Country / market areas (COUNTRY_CODE_LIST) | Countries or bidding-zone identifiers for the requested dataset. | Customer / installer |

## Set up the connection

1. Agree market areas, price product or grid dataset, resolution, currency, units and publication date. Distinguish prices from physical meter readings.
2. Obtain the required provider access shown in the table and confirm the permitted dataset. Supply secrets securely.
3. Enter the exposed scope and mapping settings, if any. Eniris verifies fixed source coverage where the form offers no selector.
4. Compare the first collected period with the original source, including timestamps, time zone, units and missing intervals.

## Check the result

Check that the first collection completed, then open the intended Insights account and verify the relevant measurements or metadata. Compare source IDs, timestamps and units with the original source. Check the next scheduled execution as well. An active schedule or a healthy job alone does not prove that every requested measurement was received.

For ordinary onboarding meters, creation requests an immediate first run and keeps recurring collection active. Source publication times, upload intervals and provider limits still apply; immediate collection cannot manufacture missing source data.

## If setup does not work

Provide Eniris with the connection name, account/site scope, time of the attempt and the exact error. Check source availability and access permissions before retrying. Share a source screenshot or sample without passwords or tokens.

## Access and costs

Costs are not established for this connector. Confirm provider access, export licences and any project charges with Eniris before activation.

[All connection setup guides](/en/Monitoring/Integrations/connections)


# Entsoe File setup


import ClickableImage from '@site/src/components/ClickableImage';

# Entsoe File setup

Collect Entsoe File market or grid-reference data. Agree the market area, product, units, currency and publication period before using the values in reports.

<ClickableImage src="/img/eniris/monitoring/connection-guides/market-grid-data.webp" alt="A market area, date range, resolution and units feeding electricity price and grid charts" maxWidth="1100px" />

*Market and grid data must be scoped by area, product, time range, resolution, currency and units before the first comparison.*

Connection type: **Prices and grid data**.

## Before you start

Use the Transparency Platform account and agreed File Library data item. This is a file-library route, separate from the token-based ENTSO-E API connector.

## What to provide

Provide your company and contact person, the intended Insights account, the source identifiers and explicit permission for the requested scope. Include a recent source example for verification.

| Information / setting | What is needed | Supplied or configured by |
| --- | --- | --- |
| Account username (USERNAME) | Account name with access to the requested data. | Customer / installer |
| Account password (PASSWORD) | Share the source-account password through the secure channel agreed with Eniris. | Customer / installer |
| Country / market areas (COUNTRY_CODE_LIST) | Countries or bidding-zone identifiers for the requested dataset. | Customer / installer |
| Data product (DATA_ITEM) | Requested file-library product or dataset. | Customer / installer |

## Set up the connection

1. Agree market areas, price product or grid dataset, resolution, currency, units and publication date. Distinguish prices from physical meter readings.
2. Obtain the required provider access shown in the table and confirm the permitted dataset. Supply secrets securely.
3. Enter the exposed scope and mapping settings, if any. Eniris verifies fixed source coverage where the form offers no selector.
4. Compare the first collected period with the original source, including timestamps, time zone, units and missing intervals.

## Check the result

Check that the first collection completed, then open the intended Insights account and verify the relevant measurements or metadata. Compare source IDs, timestamps and units with the original source. Check the next scheduled execution as well. An active schedule or a healthy job alone does not prove that every requested measurement was received.

For ordinary onboarding meters, creation requests an immediate first run and keeps recurring collection active. Source publication times, upload intervals and provider limits still apply; immediate collection cannot manufacture missing source data.

## If setup does not work

Provide Eniris with the connection name, account/site scope, time of the attempt and the exact error. Check source availability and access permissions before retrying. Share a source screenshot or sample without passwords or tokens.

## Access and costs

Costs are not established for this connector. Confirm provider access, export licences and any project charges with Eniris before activation.

[All connection setup guides](/en/Monitoring/Integrations/connections)


# Envitron API setup


import ClickableImage from '@site/src/components/ClickableImage';

# Envitron API setup

Read Envitron data using the provider access configured for this connector. Confirm account permissions, installation scope and the requested measurements before activation.

<ClickableImage src="/img/eniris/monitoring/connection-guides/api-authorization.webp" alt="A privacy-safe API setup flow with authorization, limited installation scope, validation and a monitoring dashboard" maxWidth="1100px" />

*A reliable API connection combines the correct authorization method, an explicitly limited installation scope and a verified first retrieval.*

Connection type: **API and platform connection**.

## Before you start

Use your Envitron API username and password. This connection does not need a separate API key or application secret. API access must be enabled on your Envitron account; if needed, ask Envitron or your account administrator to enable it.

All installations accessible to this account will be connected. Use an account with access only to the installations your customer has authorised.

## What to provide

Provide your company and contact person, the intended Insights account, the source identifiers and explicit permission for the requested scope. Include a recent source example for verification.

| Information / setting | What is needed | Supplied or configured by |
| --- | --- | --- |
| Envitron API username | Account name with access to the requested data. | Customer / installer |
| Envitron API password | Enter the password belonging to this Envitron account in the setup form. | Customer / installer |

## Set up the connection

1. Open your personal installer link and choose **Envitron API**.
2. Read the preparation checklist. Make sure the Envitron account has API access and covers exactly the installations you are authorised to connect.
3. Continue to the connection details. Enter a recognisable installation name, your Envitron API username and password, and confirm permission to connect the account's installations.
4. Review the customer and connection, then select **Connect installation**. The first retrieval starts automatically; no manual setup by Eniris is needed.
5. Check the result shown by the wizard. After the first retrieval, automatic collection remains active according to the schedule. If sign-in fails, check the username, password and API access.

## Check the result

Check that the first collection completed, then open the intended Insights account and verify the relevant measurements or metadata. Compare source IDs, timestamps and units with the original source. Check the next scheduled execution as well. An active schedule or a healthy job alone does not prove that every requested measurement was received.

For ordinary onboarding meters, creation requests an immediate first run and keeps recurring collection active. Source publication times, upload intervals and provider limits still apply; immediate collection cannot manufacture missing source data.

## If setup does not work

Provide Eniris with the connection name, account/site scope, time of the attempt and the exact error. Check source availability and access permissions before retrying. Share a source screenshot or sample without passwords or tokens.

## Access and costs

Costs are not established for this connector. Confirm provider access, export licences and any project charges with Eniris before activation.

[All connection setup guides](/en/Monitoring/Integrations/connections)


# Epex portal connection setup


import ClickableImage from '@site/src/components/ClickableImage';

# Epex portal connection setup

Collect Epex portal connection market or grid-reference data. Agree the market area, product, units, currency and publication period before using the values in reports.

<ClickableImage src="/img/eniris/monitoring/connection-guides/market-grid-data.webp" alt="A market area, date range, resolution and units feeding electricity price and grid charts" maxWidth="1100px" />

*Market and grid data must be scoped by area, product, time range, resolution, currency and units before the first comparison.*

Connection type: **Prices and grid data**.

## What to provide

Provide your company and contact person, the intended Insights account, the source identifiers and explicit permission for the requested scope. Include a recent source example for verification.

| Information / setting | What is needed | Supplied or configured by |
| --- | --- | --- |
| Country / market areas (COUNTRY_CODE_LIST) | Countries or bidding-zone identifiers for the requested dataset. | Customer / installer |

## Set up the connection

1. Agree market areas, price product or grid dataset, resolution, currency, units and publication date. Distinguish prices from physical meter readings.
2. Eniris checks the configured source and coverage. No customer password is requested by this connector’s current form; that does not guarantee unrestricted source access.
3. Enter the exposed scope and mapping settings, if any. Eniris verifies fixed source coverage where the form offers no selector.
4. Compare the first collected period with the original source, including timestamps, time zone, units and missing intervals.

## Check the result

Check that the first collection completed, then open the intended Insights account and verify the relevant measurements or metadata. Compare source IDs, timestamps and units with the original source. Check the next scheduled execution as well. An active schedule or a healthy job alone does not prove that every requested measurement was received.

For ordinary onboarding meters, creation requests an immediate first run and keeps recurring collection active. Source publication times, upload intervals and provider limits still apply; immediate collection cannot manufacture missing source data.

## If setup does not work

Provide Eniris with the connection name, account/site scope, time of the attempt and the exact error. Check source availability and access permissions before retrying. Share a source screenshot or sample without passwords or tokens.

## Access and costs

Onboarding classifies this portal connection as free. This label does not establish the terms of a separate provider subscription or equipment licence.

[All connection setup guides](/en/Monitoring/Integrations/connections)


# Epias API setup


import ClickableImage from '@site/src/components/ClickableImage';

# Epias API setup

Read Epias data using the provider access configured for this connector. Confirm account permissions, installation scope and the requested measurements before activation.

<ClickableImage src="/img/eniris/monitoring/connection-guides/api-authorization.webp" alt="A privacy-safe API setup flow with authorization, limited installation scope, validation and a monitoring dashboard" maxWidth="1100px" />

*A reliable API connection combines the correct authorization method, an explicitly limited installation scope and a verified first retrieval.*

Connection type: **API and platform connection**.

## What to provide

Provide your company and contact person, the intended Insights account, the source identifiers and explicit permission for the requested scope. Include a recent source example for verification.

| Information / setting | What is needed | Supplied or configured by |
| --- | --- | --- |
| Account username (API_USERNAME) | Account name with access to the requested data. | Customer / installer |
| Account password (API_PASSWORD) | Share the source-account password through the secure channel agreed with Eniris. | Customer / installer |

## Set up the connection

1. Ask the provider or account owner to enable the data access required by this connector. Confirm the permitted sites/devices and requested API version.
2. Supply the exact credential types in the table through the agreed secure channel. A portal password, API token, application secret and OAuth grant are not interchangeable.
3. Choose this connector and the target Insights account in onboarding. Enter the required fields and the authorised installation scope, then review before creating.
4. Check the first retrieval against the source account. If access succeeds but no data appears, verify site permissions, API entitlements, identifiers and the availability of measurements.

## Check the result

Check that the first collection completed, then open the intended Insights account and verify the relevant measurements or metadata. Compare source IDs, timestamps and units with the original source. Check the next scheduled execution as well. An active schedule or a healthy job alone does not prove that every requested measurement was received.

For ordinary onboarding meters, creation requests an immediate first run and keeps recurring collection active. Source publication times, upload intervals and provider limits still apply; immediate collection cannot manufacture missing source data.

## If setup does not work

Provide Eniris with the connection name, account/site scope, time of the attempt and the exact error. Check source availability and access permissions before retrying. Share a source screenshot or sample without passwords or tokens.

## Access and costs

Costs are not established for this connector. Confirm provider access, export licences and any project charges with Eniris before activation.

[All connection setup guides](/en/Monitoring/Integrations/connections)


# ESolar portal connection setup


import ClickableImage from '@site/src/components/ClickableImage';

# ESolar portal connection setup

Read measurements available through the authorised ESolar portal connection monitoring account. Only installations visible to that account can be collected.

<ClickableImage src="/img/eniris/monitoring/connection-guides/portal-access.webp" alt="A privacy-safe portal setup flow with sign-in, multi-factor authentication, installation selection and monitoring" maxWidth="1100px" />

*Confirm portal access, select only the agreed installations and complete any approval or multi-factor step before validating the data.*

Connection type: **Portal connection**.

## What to provide

Provide your company and contact person, the intended Insights account, the source identifiers and explicit permission for the requested scope. Include a recent source example for verification.

| Information / setting | What is needed | Supplied or configured by |
| --- | --- | --- |
| Account username (USERNAME) | Account name with access to the requested data. | Customer / installer |
| Account password (PASSWORD) | Share the source-account password through the secure channel agreed with Eniris. | Customer / installer |
| Installation scope (INSTALLATION_ID_ALLOW_LIST) | Exact installation IDs or numbers to include. Agree explicitly before including every installation. | Customer / installer |

## Set up the connection

1. The customer signs in to the correct provider portal and checks that the requested installations and recent measurements are visible.
2. Grant the agreed account access and supply the required account details securely. Identify any login approval or multi-factor step so Eniris can complete the authorised connection.
3. Select this connector in onboarding, choose the intended Insights account and enter the fields in the table. Restrict installation scope to the agreed list where supported.
4. Create the connection and inspect the first retrieval. A successful manual portal login does not itself prove that the collection service can read data.

## Check the result

Check that the first collection completed, then open the intended Insights account and verify the relevant measurements or metadata. Compare source IDs, timestamps and units with the original source. Check the next scheduled execution as well. An active schedule or a healthy job alone does not prove that every requested measurement was received.

For ordinary onboarding meters, creation requests an immediate first run and keeps recurring collection active. Source publication times, upload intervals and provider limits still apply; immediate collection cannot manufacture missing source data.

## If setup does not work

Provide Eniris with the connection name, account/site scope, time of the attempt and the exact error. Check source availability and access permissions before retrying. Share a source screenshot or sample without passwords or tokens.

## Access and costs

Onboarding classifies this portal connection as free. This label does not establish the terms of a separate provider subscription or equipment licence.

[All connection setup guides](/en/Monitoring/Integrations/connections)


# Etrel Tcp Modpus setup


import ClickableImage from '@site/src/components/ClickableImage';

# Etrel Tcp Modpus setup

Read measurements and charger information from a supported Etrel / INCH charger over Modbus TCP.

<ClickableImage src="/img/eniris/monitoring/connection-guides/local-device.webp" alt="A meter and controller on a private network connected securely through a firewall to a monitoring dashboard" maxWidth="1100px" />

*Keep the device on the private site network and verify the supported endpoint, gateway route and secure outbound connection.*

Connection type: **Local devices**.

## What to provide

Provide your company and contact person, the intended Insights account, the source identifiers and explicit permission for the requested scope. Include a recent source example for verification.

| Information / setting | What is needed | Supplied or configured by |
| --- | --- | --- |
| Device IP address (CLIENT_IP) | Local device address and a working network route from the collection service. | Customer / installer |

## Set up the connection

1. Give Eniris the device model, firmware, identity, network location and the measurements to collect.
2. Have the site installer enable the supported data interface. Eniris verifies the required network route from the collection service; reaching the device on a customer laptop is not sufficient.
3. Enter the endpoint or device identity shown below and agree the time zone and signal mapping. Do not expose the device publicly to work around routing.
4. Start the first collection and compare a recent value and timestamp against the device itself.

## Check the result

Check that the first collection completed, then open the intended Insights account and verify the relevant measurements or metadata. Compare source IDs, timestamps and units with the original source. Check the next scheduled execution as well. An active schedule or a healthy job alone does not prove that every requested measurement was received.

For ordinary onboarding meters, creation requests an immediate first run and keeps recurring collection active. Source publication times, upload intervals and provider limits still apply; immediate collection cannot manufacture missing source data.

## If setup does not work

Provide Eniris with the connection name, account/site scope, time of the attempt and the exact error. Check source availability and access permissions before retrying. Share a source screenshot or sample without passwords or tokens.

## Access and costs

Costs are not established for this connector. Confirm provider access, export licences and any project charges with Eniris before activation.

[All connection setup guides](/en/Monitoring/Integrations/connections)


# Ewon setup


import ClickableImage from '@site/src/components/ClickableImage';

# Ewon setup

Read data through Ewon Talk2M using a device ID, access token and selected installation IDs.

<ClickableImage src="/img/eniris/monitoring/connection-guides/api-authorization.webp" alt="A privacy-safe API setup flow with authorization, limited installation scope, validation and a monitoring dashboard" maxWidth="1100px" />

*A reliable API connection combines the correct authorization method, an explicitly limited installation scope and a verified first retrieval.*

Connection type: **API and platform connection**.

## What to provide

Provide your company and contact person, the intended Insights account, the source identifiers and explicit permission for the requested scope. Include a recent source example for verification.

| Information / setting | What is needed | Supplied or configured by |
| --- | --- | --- |
| Talk2M device ID (T2M_DEV_ID) | Identifier of the authorised Ewon gateway. | Customer / installer |
| Access token (T2M_TOKEN) | Provider-issued token with access to the required data; share securely and record who maintains it. | Customer / installer |
| Installation scope (INSTALLATION_IDS) | Exact installation IDs or numbers to include. Agree explicitly before including every installation. | Customer / installer |

## Set up the connection

1. Ask the provider or account owner to enable the data access required by this connector. Confirm the permitted sites/devices and requested API version.
2. Supply the exact credential types in the table through the agreed secure channel. A portal password, API token, application secret and OAuth grant are not interchangeable.
3. Choose this connector and the target Insights account in onboarding. Enter the required fields and the authorised installation scope, then review before creating.
4. Check the first retrieval against the source account. If access succeeds but no data appears, verify site permissions, API entitlements, identifiers and the availability of measurements.

## Check the result

Check that the first collection completed, then open the intended Insights account and verify the relevant measurements or metadata. Compare source IDs, timestamps and units with the original source. Check the next scheduled execution as well. An active schedule or a healthy job alone does not prove that every requested measurement was received.

For ordinary onboarding meters, creation requests an immediate first run and keeps recurring collection active. Source publication times, upload intervals and provider limits still apply; immediate collection cannot manufacture missing source data.

## If setup does not work

Provide Eniris with the connection name, account/site scope, time of the attempt and the exact error. Check source availability and access permissions before retrying. Share a source screenshot or sample without passwords or tokens.

## Access and costs

Costs are not established for this connector. Confirm provider access, export licences and any project charges with Eniris before activation.

[All connection setup guides](/en/Monitoring/Integrations/connections)


# EWTDirect Wind portal connection setup


import ClickableImage from '@site/src/components/ClickableImage';

# EWTDirect Wind portal connection setup

Read measurements available through the authorised EWTDirect Wind portal connection monitoring account. Only installations visible to that account can be collected.

<ClickableImage src="/img/eniris/monitoring/connection-guides/portal-access.webp" alt="A privacy-safe portal setup flow with sign-in, multi-factor authentication, installation selection and monitoring" maxWidth="1100px" />

*Confirm portal access, select only the agreed installations and complete any approval or multi-factor step before validating the data.*

Connection type: **Portal connection**.

## Before you start

The account email/password and the deployment-specific WebSocket URL are all required. Verify the requested turbines are visible to that account.

## What to provide

Provide your company and contact person, the intended Insights account, the source identifiers and explicit permission for the requested scope. Include a recent source example for verification.

| Information / setting | What is needed | Supplied or configured by |
| --- | --- | --- |
| Account email (EMAIL) | Email address of the authorised source account. | Customer / installer |
| Account password (PASSWORD) | Share the source-account password through the secure channel agreed with Eniris. | Customer / installer |
| WebSocket endpoint (WEBSOCKET_URL) | Deployment-specific WebSocket address supplied by the platform owner. | Customer / installer |

## Set up the connection

1. The customer signs in to the correct provider portal and checks that the requested installations and recent measurements are visible.
2. Grant the agreed account access and supply the required account details securely. Identify any login approval or multi-factor step so Eniris can complete the authorised connection.
3. Select this connector in onboarding, choose the intended Insights account and enter the fields in the table. Restrict installation scope to the agreed list where supported.
4. Create the connection and inspect the first retrieval. A successful manual portal login does not itself prove that the collection service can read data.

## Check the result

Check that the first collection completed, then open the intended Insights account and verify the relevant measurements or metadata. Compare source IDs, timestamps and units with the original source. Check the next scheduled execution as well. An active schedule or a healthy job alone does not prove that every requested measurement was received.

For ordinary onboarding meters, creation requests an immediate first run and keeps recurring collection active. Source publication times, upload intervals and provider limits still apply; immediate collection cannot manufacture missing source data.

## If setup does not work

Provide Eniris with the connection name, account/site scope, time of the attempt and the exact error. Check source availability and access permissions before retrying. Share a source screenshot or sample without passwords or tokens.

## Access and costs

Onboarding classifies this portal connection as free. This label does not establish the terms of a separate provider subscription or equipment licence.

[All connection setup guides](/en/Monitoring/Integrations/connections)


# File setup


import ClickableImage from '@site/src/components/ClickableImage';

# File setup

Read a measurement value from a file and attach the agreed measurement type and tags.

<ClickableImage src="/img/eniris/monitoring/connection-guides/file-import.webp" alt="A data logger creating a structured file, transferring it securely and mapping its fields to a dashboard" maxWidth="1100px" />

*File onboarding is complete only after the source export, secure delivery, field mapping and recurring arrival have all been checked.*

Connection type: **File import**.

## What to provide

Provide your company and contact person, the intended Insights account, the source identifiers and explicit permission for the requested scope. Include a recent source example for verification.

| Information / setting | What is needed | Supplied or configured by |
| --- | --- | --- |
| File / folder location (PATH) | Agree the delivery folder and file layout. Eniris makes it accessible to the collection service; a path on the customer laptop is insufficient. | Eniris with installer |
| Required measurements (MEASUREMENT) | Signals and units to collect; Eniris configures the corresponding measurement mapping. | Eniris with customer |
| Measurement mapping (TAGS) | Provide column definitions, units and device tags; Eniris configures the mapping from a sample file. | Eniris with customer |

## Set up the connection

1. Identify the source logger or export system and supply an original sample file. Confirm model, firmware, format and time zone with Eniris.
2. Agree the delivery route. For an Eniris FTP destination, request dedicated server, protocol, port, username, password and folder settings from Eniris. Use the agreed protocol exactly.
3. The installer or source owner enables recurring delivery. Eniris configures the accessible source location and device/field mappings; creating a meter does not configure the remote source.
4. Send a test file and record its timestamp. Eniris verifies arrival before starting collection, then compares the processed measurements with the original file.

## Check the result

Check that the first collection completed, then open the intended Insights account and verify the relevant measurements or metadata. Compare source IDs, timestamps and units with the original source. Check the next scheduled execution as well. An active schedule or a healthy job alone does not prove that every requested measurement was received.

For ordinary onboarding meters, creation requests an immediate first run and keeps recurring collection active. Source publication times, upload intervals and provider limits still apply; immediate collection cannot manufacture missing source data.

## If setup does not work

If no file arrives, inspect the logger/export status, destination, authentication, network route and folder. If files arrive but no measurements appear, provide the filename, format, source identifiers and timestamp so Eniris can check parsing and mapping.

## Access and costs

Costs are not established for this connector. Confirm provider access, export licences and any project charges with Eniris before activation.

[All connection setup guides](/en/Monitoring/Integrations/connections)


# Fimer portal connection setup


import ClickableImage from '@site/src/components/ClickableImage';

# Fimer portal connection setup

Read measurements available through the authorised Fimer portal connection monitoring account. Only installations visible to that account can be collected.

<ClickableImage src="/img/eniris/monitoring/connection-guides/portal-access.webp" alt="A privacy-safe portal setup flow with sign-in, multi-factor authentication, installation selection and monitoring" maxWidth="1100px" />

*Confirm portal access, select only the agreed installations and complete any approval or multi-factor step before validating the data.*

Connection type: **Portal connection**.

## What to provide

Provide your company and contact person, the intended Insights account, the source identifiers and explicit permission for the requested scope. Include a recent source example for verification.

| Information / setting | What is needed | Supplied or configured by |
| --- | --- | --- |
| Account username (USERNAME) | Account name with access to the requested data. | Customer / installer |
| Account password (PASSWORD) | Share the source-account password through the secure channel agreed with Eniris. | Customer / installer |

## Set up the connection

1. The customer signs in to the correct provider portal and checks that the requested installations and recent measurements are visible.
2. Grant the agreed account access and supply the required account details securely. Identify any login approval or multi-factor step so Eniris can complete the authorised connection.
3. Select this connector in onboarding, choose the intended Insights account and enter the fields in the table. Restrict installation scope to the agreed list where supported.
4. Create the connection and inspect the first retrieval. A successful manual portal login does not itself prove that the collection service can read data.

## Check the result

Check that the first collection completed, then open the intended Insights account and verify the relevant measurements or metadata. Compare source IDs, timestamps and units with the original source. Check the next scheduled execution as well. An active schedule or a healthy job alone does not prove that every requested measurement was received.

For ordinary onboarding meters, creation requests an immediate first run and keeps recurring collection active. Source publication times, upload intervals and provider limits still apply; immediate collection cannot manufacture missing source data.

## If setup does not work

Provide Eniris with the connection name, account/site scope, time of the attempt and the exact error. Check source availability and access permissions before retrying. Share a source screenshot or sample without passwords or tokens.

## Access and costs

Onboarding classifies this portal connection as free. This label does not establish the terms of a separate provider subscription or equipment licence.

[All connection setup guides](/en/Monitoring/Integrations/connections)


# Flexpond portal connection setup


import ClickableImage from '@site/src/components/ClickableImage';

# Flexpond portal connection setup

Read measurements available through the authorised Flexpond portal connection monitoring account. Only installations visible to that account can be collected.

<ClickableImage src="/img/eniris/monitoring/connection-guides/portal-access.webp" alt="A privacy-safe portal setup flow with sign-in, multi-factor authentication, installation selection and monitoring" maxWidth="1100px" />

*Confirm portal access, select only the agreed installations and complete any approval or multi-factor step before validating the data.*

Connection type: **Portal connection**.

## What to provide

Provide your company and contact person, the intended Insights account, the source identifiers and explicit permission for the requested scope. Include a recent source example for verification.

| Information / setting | What is needed | Supplied or configured by |
| --- | --- | --- |
| Account username (USERNAME) | Account name with access to the requested data. | Customer / installer |
| Account password (PASSWORD) | Share the source-account password through the secure channel agreed with Eniris. | Customer / installer |
| Site resources (SITES_RESOURCES) | Source-specific site/resource identifiers to collect. | Customer / installer |

## Set up the connection

1. The customer signs in to the correct provider portal and checks that the requested installations and recent measurements are visible.
2. Grant the agreed account access and supply the required account details securely. Identify any login approval or multi-factor step so Eniris can complete the authorised connection.
3. Select this connector in onboarding, choose the intended Insights account and enter the fields in the table. Restrict installation scope to the agreed list where supported.
4. Create the connection and inspect the first retrieval. A successful manual portal login does not itself prove that the collection service can read data.

## Check the result

Check that the first collection completed, then open the intended Insights account and verify the relevant measurements or metadata. Compare source IDs, timestamps and units with the original source. Check the next scheduled execution as well. An active schedule or a healthy job alone does not prove that every requested measurement was received.

For ordinary onboarding meters, creation requests an immediate first run and keeps recurring collection active. Source publication times, upload intervals and provider limits still apply; immediate collection cannot manufacture missing source data.

## If setup does not work

Provide Eniris with the connection name, account/site scope, time of the attempt and the exact error. Check source availability and access permissions before retrying. Share a source screenshot or sample without passwords or tokens.

## Access and costs

Onboarding classifies this portal connection as free. This label does not establish the terms of a separate provider subscription or equipment licence.

[All connection setup guides](/en/Monitoring/Integrations/connections)


# Fluvius API setup


import ClickableImage from '@site/src/components/ClickableImage';

# Fluvius API setup

Collect authorised Fluvius metering data using the configured customer-reference flow. Eniris manages the API environment; the customer supplies consent and connection-point scope.

<ClickableImage src="/img/eniris/monitoring/connection-guides/api-authorization.webp" alt="A privacy-safe API setup flow with authorization, limited installation scope, validation and a monitoring dashboard" maxWidth="1100px" />

*A reliable API connection combines the correct authorization method, an explicitly limited installation scope and a verified first retrieval.*

Connection type: **API and platform connection**.

## What to provide

Provide your company and contact person, the intended Insights account, the source identifiers and explicit permission for the requested scope. Include a recent source example for verification.

| Information / setting | What is needed | Supplied or configured by |
| --- | --- | --- |
| Authorisation reference (REFERENCE_NUMBER) | Reference identifying the customer consent/access flow. | Customer / installer |
| Exclusions (DISALLOW_LIST) | IDs that must not be processed; Eniris checks the identifier type used by this connector. | Customer / installer |

## Set up the connection

1. Ask the provider or account owner to enable the data access required by this connector. Confirm the permitted sites/devices and requested API version.
2. Supply the exact credential types in the table through the agreed secure channel. A portal password, API token, application secret and OAuth grant are not interchangeable.
3. Choose this connector and the target Insights account in onboarding. Enter the required fields and the authorised installation scope, then review before creating.
4. Check the first retrieval against the source account. If access succeeds but no data appears, verify site permissions, API entitlements, identifiers and the availability of measurements.

## Check the result

Check that the first collection completed, then open the intended Insights account and verify the relevant measurements or metadata. Compare source IDs, timestamps and units with the original source. Check the next scheduled execution as well. An active schedule or a healthy job alone does not prove that every requested measurement was received.

For ordinary onboarding meters, creation requests an immediate first run and keeps recurring collection active. Source publication times, upload intervals and provider limits still apply; immediate collection cannot manufacture missing source data.

## If setup does not work

Provide Eniris with the connection name, account/site scope, time of the attempt and the exact error. Check source availability and access permissions before retrying. Share a source screenshot or sample without passwords or tokens.

## Access and costs

Costs are not established for this connector. Confirm provider access, export licences and any project charges with Eniris before activation.

[All connection setup guides](/en/Monitoring/Integrations/connections)


# Fluvius Nps CSV setup


import ClickableImage from '@site/src/components/ClickableImage';

# Fluvius Nps CSV setup

Import Fluvius NPS meter files for selected contracts from an agreed delivery location.

<ClickableImage src="/img/eniris/monitoring/connection-guides/file-import.webp" alt="A data logger creating a structured file, transferring it securely and mapping its fields to a dashboard" maxWidth="1100px" />

*File onboarding is complete only after the source export, secure delivery, field mapping and recurring arrival have all been checked.*

Connection type: **File import**.

## What to provide

Provide your company and contact person, the intended Insights account, the source identifiers and explicit permission for the requested scope. Include a recent source example for verification.

| Information / setting | What is needed | Supplied or configured by |
| --- | --- | --- |
| File delivery source (BROWSER) | Agree the source location and transport; Eniris configures access without putting credentials in public URLs. | Eniris with installer |
| Contract scope (CONTRACT_ID_ALLOW_LIST) | Contract identifiers and permission to collect their data. | Customer / installer |

## Set up the connection

1. Arrange the authorised Fluvius file delivery and contract scope. These files come from the grid-operator workflow; do not configure a customer datalogger for this route.
2. Agree the delivery route. For an Eniris FTP destination, request dedicated server, protocol, port, username, password and folder settings from Eniris. Use the agreed protocol exactly.
3. The installer or source owner enables recurring delivery. Eniris configures the accessible source location and device/field mappings; creating a meter does not configure the remote source.
4. Send a test file and record its timestamp. Eniris verifies arrival before starting collection, then compares the processed measurements with the original file.

## Check the result

Check that the first collection completed, then open the intended Insights account and verify the relevant measurements or metadata. Compare source IDs, timestamps and units with the original source. Check the next scheduled execution as well. An active schedule or a healthy job alone does not prove that every requested measurement was received.

For ordinary onboarding meters, creation requests an immediate first run and keeps recurring collection active. Source publication times, upload intervals and provider limits still apply; immediate collection cannot manufacture missing source data.

## If setup does not work

If no file arrives, inspect the logger/export status, destination, authentication, network route and folder. If files arrive but no measurements appear, provide the filename, format, source identifiers and timestamp so Eniris can check parsing and mapping.

## Access and costs

Costs are not established for this connector. Confirm provider access, export licences and any project charges with Eniris before activation.

[All connection setup guides](/en/Monitoring/Integrations/connections)


# Fluvius NPSCsv Meter Deprecated setup


import ClickableImage from '@site/src/components/ClickableImage';

# Fluvius NPSCsv Meter Deprecated setup

Import the legacy Fluvius NPS CSV format for a contract. This is a deprecated route; agree migration to the current NPS connector before a new installation.

<ClickableImage src="/img/eniris/monitoring/connection-guides/file-import.webp" alt="A data logger creating a structured file, transferring it securely and mapping its fields to a dashboard" maxWidth="1100px" />

*File onboarding is complete only after the source export, secure delivery, field mapping and recurring arrival have all been checked.*

Connection type: **File import**.

## What to provide

Provide your company and contact person, the intended Insights account, the source identifiers and explicit permission for the requested scope. Include a recent source example for verification.

| Information / setting | What is needed | Supplied or configured by |
| --- | --- | --- |
| File / folder location (CSV_FOLDER) | Agree the delivery folder and file layout. Eniris makes it accessible to the collection service; a path on the customer laptop is insufficient. | Eniris with installer |
| Contract scope (CONTRACT_ID) | Contract identifiers and permission to collect their data. | Customer / installer |

## Set up the connection

1. Arrange the authorised Fluvius file delivery and contract scope. These files come from the grid-operator workflow; do not configure a customer datalogger for this route.
2. Agree the delivery route. For an Eniris FTP destination, request dedicated server, protocol, port, username, password and folder settings from Eniris. Use the agreed protocol exactly.
3. The installer or source owner enables recurring delivery. Eniris configures the accessible source location and device/field mappings; creating a meter does not configure the remote source.
4. Send a test file and record its timestamp. Eniris verifies arrival before starting collection, then compares the processed measurements with the original file.

## Check the result

Check that the first collection completed, then open the intended Insights account and verify the relevant measurements or metadata. Compare source IDs, timestamps and units with the original source. Check the next scheduled execution as well. An active schedule or a healthy job alone does not prove that every requested measurement was received.

For ordinary onboarding meters, creation requests an immediate first run and keeps recurring collection active. Source publication times, upload intervals and provider limits still apply; immediate collection cannot manufacture missing source data.

## If setup does not work

If no file arrives, inspect the logger/export status, destination, authentication, network route and folder. If files arrive but no measurements appear, provide the filename, format, source identifiers and timestamp so Eniris can check parsing and mapping.

## Access and costs

Costs are not established for this connector. Confirm provider access, export licences and any project charges with Eniris before activation.

[All connection setup guides](/en/Monitoring/Integrations/connections)


# Frank Energie API setup


import ClickableImage from '@site/src/components/ClickableImage';

# Frank Energie API setup

Collect Frank Energie market or grid-reference data. Agree the market area, product, units, currency and publication period before using the values in reports.

<ClickableImage src="/img/eniris/monitoring/connection-guides/market-grid-data.webp" alt="A market area, date range, resolution and units feeding electricity price and grid charts" maxWidth="1100px" />

*Market and grid data must be scoped by area, product, time range, resolution, currency and units before the first comparison.*

Connection type: **Prices and grid data**.

## What to provide

Provide your company and contact person, the intended Insights account, the source identifiers and explicit permission for the requested scope. Include a recent source example for verification.

| Information / setting | What is needed | Supplied or configured by |
| --- | --- | --- |
| Country / market areas (COUNTRY_CODE_LIST) | Countries or bidding-zone identifiers for the requested dataset. | Customer / installer |

## Set up the connection

1. Agree market areas, price product or grid dataset, resolution, currency, units and publication date. Distinguish prices from physical meter readings.
2. Eniris checks the configured source and coverage. No customer password is requested by this connector’s current form; that does not guarantee unrestricted source access.
3. Enter the exposed scope and mapping settings, if any. Eniris verifies fixed source coverage where the form offers no selector.
4. Compare the first collected period with the original source, including timestamps, time zone, units and missing intervals.

## Check the result

Check that the first collection completed, then open the intended Insights account and verify the relevant measurements or metadata. Compare source IDs, timestamps and units with the original source. Check the next scheduled execution as well. An active schedule or a healthy job alone does not prove that every requested measurement was received.

For ordinary onboarding meters, creation requests an immediate first run and keeps recurring collection active. Source publication times, upload intervals and provider limits still apply; immediate collection cannot manufacture missing source data.

## If setup does not work

Provide Eniris with the connection name, account/site scope, time of the attempt and the exact error. Check source availability and access permissions before retrying. Share a source screenshot or sample without passwords or tokens.

## Access and costs

Costs are not established for this connector. Confirm provider access, export licences and any project charges with Eniris before activation.

[All connection setup guides](/en/Monitoring/Integrations/connections)


# Fronius JSON setup


import ClickableImage from '@site/src/components/ClickableImage';

# Fronius JSON setup

Import Fronius JSON files from the agreed delivery location.

<ClickableImage src="/img/eniris/monitoring/connection-guides/file-import.webp" alt="A data logger creating a structured file, transferring it securely and mapping its fields to a dashboard" maxWidth="1100px" />

*File onboarding is complete only after the source export, secure delivery, field mapping and recurring arrival have all been checked.*

Connection type: **File import**.

## What to provide

Provide your company and contact person, the intended Insights account, the source identifiers and explicit permission for the requested scope. Include a recent source example for verification.

| Information / setting | What is needed | Supplied or configured by |
| --- | --- | --- |
| File delivery source (BROWSER) | Agree the source location and transport; Eniris configures access without putting credentials in public URLs. | Eniris with installer |
| Time zone (TIMEZONE) | Time zone of the source timestamps, for example Europe/Brussels; identify any files already using UTC. | Customer / installer |

## Set up the connection

1. Identify the source logger or export system and supply an original sample file. Confirm model, firmware, format and time zone with Eniris.
2. Agree the delivery route. For an Eniris FTP destination, request dedicated server, protocol, port, username, password and folder settings from Eniris. Use the agreed protocol exactly.
3. The installer or source owner enables recurring delivery. Eniris configures the accessible source location and device/field mappings; creating a meter does not configure the remote source.
4. Send a test file and record its timestamp. Eniris verifies arrival before starting collection, then compares the processed measurements with the original file.

## Check the result

Check that the first collection completed, then open the intended Insights account and verify the relevant measurements or metadata. Compare source IDs, timestamps and units with the original source. Check the next scheduled execution as well. An active schedule or a healthy job alone does not prove that every requested measurement was received.

For ordinary onboarding meters, creation requests an immediate first run and keeps recurring collection active. Source publication times, upload intervals and provider limits still apply; immediate collection cannot manufacture missing source data.

## If setup does not work

If no file arrives, inspect the logger/export status, destination, authentication, network route and folder. If files arrive but no measurements appear, provide the filename, format, source identifiers and timestamp so Eniris can check parsing and mapping.

## Access and costs

Costs are not established for this connector. Confirm provider access, export licences and any project charges with Eniris before activation.

[All connection setup guides](/en/Monitoring/Integrations/connections)


# Fronius portal connection setup


import ClickableImage from '@site/src/components/ClickableImage';

# Fronius portal connection setup

Read installations and measurements visible to the supplied Fronius Solar.web account.

<ClickableImage src="/img/eniris/monitoring/connection-guides/portal-access.webp" alt="A privacy-safe portal setup flow with sign-in, multi-factor authentication, installation selection and monitoring" maxWidth="1100px" />

*Confirm portal access, select only the agreed installations and complete any approval or multi-factor step before validating the data.*

Connection type: **Portal connection**.

## What to provide

Provide your company and contact person, the intended Insights account, the source identifiers and explicit permission for the requested scope. Include a recent source example for verification.

| Information / setting | What is needed | Supplied or configured by |
| --- | --- | --- |
| Account username (USERNAME) | Account name with access to the requested data. | Customer / installer |
| Account password (PASSWORD) | Share the source-account password through the secure channel agreed with Eniris. | Customer / installer |
| Time zone (TIMEZONE) | Time zone of the source timestamps, for example Europe/Brussels; identify any files already using UTC. | Customer / installer |
| Installation scope (INSTALLATION_ID_ALLOW_LIST) | Exact installation IDs or numbers to include. Agree explicitly before including every installation. | Customer / installer |

## Set up the connection

1. The customer signs in to the correct provider portal and checks that the requested installations and recent measurements are visible.
2. Grant the agreed account access and supply the required account details securely. Identify any login approval or multi-factor step so Eniris can complete the authorised connection.
3. Select this connector in onboarding, choose the intended Insights account and enter the fields in the table. Restrict installation scope to the agreed list where supported.
4. Create the connection and inspect the first retrieval. A successful manual portal login does not itself prove that the collection service can read data.

## Check the result

Check that the first collection completed, then open the intended Insights account and verify the relevant measurements or metadata. Compare source IDs, timestamps and units with the original source. Check the next scheduled execution as well. An active schedule or a healthy job alone does not prove that every requested measurement was received.

For ordinary onboarding meters, creation requests an immediate first run and keeps recurring collection active. Source publication times, upload intervals and provider limits still apply; immediate collection cannot manufacture missing source data.

## If setup does not work

Provide Eniris with the connection name, account/site scope, time of the attempt and the exact error. Check source availability and access permissions before retrying. Share a source screenshot or sample without passwords or tokens.

## Access and costs

Onboarding classifies this portal connection as free. This label does not establish the terms of a separate provider subscription or equipment licence.

[All connection setup guides](/en/Monitoring/Integrations/connections)


# Fronius Txt setup


import ClickableImage from '@site/src/components/ClickableImage';

# Fronius Txt setup

Import Fronius TXT files from the agreed delivery location.

<ClickableImage src="/img/eniris/monitoring/connection-guides/file-import.webp" alt="A data logger creating a structured file, transferring it securely and mapping its fields to a dashboard" maxWidth="1100px" />

*File onboarding is complete only after the source export, secure delivery, field mapping and recurring arrival have all been checked.*

Connection type: **File import**.

## What to provide

Provide your company and contact person, the intended Insights account, the source identifiers and explicit permission for the requested scope. Include a recent source example for verification.

| Information / setting | What is needed | Supplied or configured by |
| --- | --- | --- |
| File delivery source (BROWSER) | Agree the source location and transport; Eniris configures access without putting credentials in public URLs. | Eniris with installer |
| Time zone (TIMEZONE) | Time zone of the source timestamps, for example Europe/Brussels; identify any files already using UTC. | Customer / installer |

## Set up the connection

1. Identify the source logger or export system and supply an original sample file. Confirm model, firmware, format and time zone with Eniris.
2. Agree the delivery route. For an Eniris FTP destination, request dedicated server, protocol, port, username, password and folder settings from Eniris. Use the agreed protocol exactly.
3. The installer or source owner enables recurring delivery. Eniris configures the accessible source location and device/field mappings; creating a meter does not configure the remote source.
4. Send a test file and record its timestamp. Eniris verifies arrival before starting collection, then compares the processed measurements with the original file.

## Check the result

Check that the first collection completed, then open the intended Insights account and verify the relevant measurements or metadata. Compare source IDs, timestamps and units with the original source. Check the next scheduled execution as well. An active schedule or a healthy job alone does not prove that every requested measurement was received.

For ordinary onboarding meters, creation requests an immediate first run and keeps recurring collection active. Source publication times, upload intervals and provider limits still apply; immediate collection cannot manufacture missing source data.

## If setup does not work

If no file arrives, inspect the logger/export status, destination, authentication, network route and folder. If files arrive but no measurements appear, provide the filename, format, source identifiers and timestamp so Eniris can check parsing and mapping.

## Access and costs

Costs are not established for this connector. Confirm provider access, export licences and any project charges with Eniris before activation.

[All connection setup guides](/en/Monitoring/Integrations/connections)


# Fudura API setup


import ClickableImage from '@site/src/components/ClickableImage';

# Fudura API setup

Read Fudura data using the provider access configured for this connector. Confirm account permissions, installation scope and the requested measurements before activation.

<ClickableImage src="/img/eniris/monitoring/connection-guides/api-authorization.webp" alt="A privacy-safe API setup flow with authorization, limited installation scope, validation and a monitoring dashboard" maxWidth="1100px" />

*A reliable API connection combines the correct authorization method, an explicitly limited installation scope and a verified first retrieval.*

Connection type: **API and platform connection**.

## What to provide

Provide your company and contact person, the intended Insights account, the source identifiers and explicit permission for the requested scope. Include a recent source example for verification.

| Information / setting | What is needed | Supplied or configured by |
| --- | --- | --- |
| API key (API_KEY) | Obtain the key from the source account owner or provider; confirm its data permissions and share it securely. | Customer / installer |

## Set up the connection

1. Ask the provider or account owner to enable the data access required by this connector. Confirm the permitted sites/devices and requested API version.
2. Supply the exact credential types in the table through the agreed secure channel. A portal password, API token, application secret and OAuth grant are not interchangeable.
3. Choose this connector and the target Insights account in onboarding. Enter the required fields and the authorised installation scope, then review before creating.
4. Check the first retrieval against the source account. If access succeeds but no data appears, verify site permissions, API entitlements, identifiers and the availability of measurements.

## Check the result

Check that the first collection completed, then open the intended Insights account and verify the relevant measurements or metadata. Compare source IDs, timestamps and units with the original source. Check the next scheduled execution as well. An active schedule or a healthy job alone does not prove that every requested measurement was received.

For ordinary onboarding meters, creation requests an immediate first run and keeps recurring collection active. Source publication times, upload intervals and provider limits still apply; immediate collection cannot manufacture missing source data.

## If setup does not work

Provide Eniris with the connection name, account/site scope, time of the attempt and the exact error. Check source availability and access permissions before retrying. Share a source screenshot or sample without passwords or tokens.

## Access and costs

Costs are not established for this connector. Confirm provider access, export licences and any project charges with Eniris before activation.

[All connection setup guides](/en/Monitoring/Integrations/connections)


# Fusion Solar Alarms setup


import ClickableImage from '@site/src/components/ClickableImage';

# Fusion Solar Alarms setup

Collect FusionSolar alarms for the permitted installations. Use an appropriate metrics connector as well if power and energy readings are required.

<ClickableImage src="/img/eniris/monitoring/connection-guides/api-authorization.webp" alt="A privacy-safe API setup flow with authorization, limited installation scope, validation and a monitoring dashboard" maxWidth="1100px" />

*A reliable API connection combines the correct authorization method, an explicitly limited installation scope and a verified first retrieval.*

Connection type: **API and platform connection**.

## What to provide

Provide your company and contact person, the intended Insights account, the source identifiers and explicit permission for the requested scope. Include a recent source example for verification.

| Information / setting | What is needed | Supplied or configured by |
| --- | --- | --- |
| Account username (USERNAME) | Account name with access to the requested data. | Customer / installer |
| Account password (PASSWORD) | Share the source-account password through the secure channel agreed with Eniris. | Customer / installer |
| Portal region (REGION) | Region or portal instance in which the requested installations exist. | Customer / installer |
| Installation scope (INSTALLATION_ID_ALLOW_LIST) | Exact installation IDs or numbers to include. Agree explicitly before including every installation. | Customer / installer |

## Set up the connection

1. Ask the provider or account owner to enable the data access required by this connector. Confirm the permitted sites/devices and requested API version.
2. Supply the exact credential types in the table through the agreed secure channel. A portal password, API token, application secret and OAuth grant are not interchangeable.
3. Choose this connector and the target Insights account in onboarding. Enter the required fields and the authorised installation scope, then review before creating.
4. Check the first retrieval against the source account. If access succeeds but no data appears, verify site permissions, API entitlements, identifiers and the availability of measurements.

## Check the result

Check that the first collection completed, then open the intended Insights account and verify the relevant measurements or metadata. Compare source IDs, timestamps and units with the original source. Check the next scheduled execution as well. An active schedule or a healthy job alone does not prove that every requested measurement was received.

For ordinary onboarding meters, creation requests an immediate first run and keeps recurring collection active. Source publication times, upload intervals and provider limits still apply; immediate collection cannot manufacture missing source data.

## If setup does not work

Provide Eniris with the connection name, account/site scope, time of the attempt and the exact error. Check source availability and access permissions before retrying. Share a source screenshot or sample without passwords or tokens.

## Access and costs

Costs are not established for this connector. Confirm provider access, export licences and any project charges with Eniris before activation.

[All connection setup guides](/en/Monitoring/Integrations/connections)


# Fusion Solar API Historical Metric setup


import ClickableImage from '@site/src/components/ClickableImage';

# Fusion Solar API Historical Metric setup

Collect historical FusionSolar metrics for the permitted installations.

<ClickableImage src="/img/eniris/monitoring/connection-guides/api-authorization.webp" alt="A privacy-safe API setup flow with authorization, limited installation scope, validation and a monitoring dashboard" maxWidth="1100px" />

*A reliable API connection combines the correct authorization method, an explicitly limited installation scope and a verified first retrieval.*

Connection type: **API and platform connection**.

## What to provide

Provide your company and contact person, the intended Insights account, the source identifiers and explicit permission for the requested scope. Include a recent source example for verification.

| Information / setting | What is needed | Supplied or configured by |
| --- | --- | --- |
| Account username (USERNAME) | Account name with access to the requested data. | Customer / installer |
| Account password (PASSWORD) | Share the source-account password through the secure channel agreed with Eniris. | Customer / installer |
| Installation scope (INSTALLATION_ID_ALLOW_LIST) | Exact installation IDs or numbers to include. Agree explicitly before including every installation. | Customer / installer |

## Set up the connection

1. Ask the provider or account owner to enable the data access required by this connector. Confirm the permitted sites/devices and requested API version.
2. Supply the exact credential types in the table through the agreed secure channel. A portal password, API token, application secret and OAuth grant are not interchangeable.
3. Choose this connector and the target Insights account in onboarding. Enter the required fields and the authorised installation scope, then review before creating.
4. Check the first retrieval against the source account. If access succeeds but no data appears, verify site permissions, API entitlements, identifiers and the availability of measurements.

## Check the result

Check that the first collection completed, then open the intended Insights account and verify the relevant measurements or metadata. Compare source IDs, timestamps and units with the original source. Check the next scheduled execution as well. An active schedule or a healthy job alone does not prove that every requested measurement was received.

For ordinary onboarding meters, creation requests an immediate first run and keeps recurring collection active. Source publication times, upload intervals and provider limits still apply; immediate collection cannot manufacture missing source data.

## If setup does not work

Provide Eniris with the connection name, account/site scope, time of the attempt and the exact error. Check source availability and access permissions before retrying. Share a source screenshot or sample without passwords or tokens.

## Access and costs

Costs are not established for this connector. Confirm provider access, export licences and any project charges with Eniris before activation.

[All connection setup guides](/en/Monitoring/Integrations/connections)


# Fusion Solar API Meta Data setup


import ClickableImage from '@site/src/components/ClickableImage';

# Fusion Solar API Meta Data setup

Synchronise FusionSolar installation and device metadata. Metadata alone does not provide power or energy time series.

<ClickableImage src="/img/eniris/monitoring/connection-guides/api-authorization.webp" alt="A privacy-safe API setup flow with authorization, limited installation scope, validation and a monitoring dashboard" maxWidth="1100px" />

*A reliable API connection combines the correct authorization method, an explicitly limited installation scope and a verified first retrieval.*

Connection type: **API and platform connection**.

## What to provide

Provide your company and contact person, the intended Insights account, the source identifiers and explicit permission for the requested scope. Include a recent source example for verification.

| Information / setting | What is needed | Supplied or configured by |
| --- | --- | --- |
| Account username (USERNAME) | Account name with access to the requested data. | Customer / installer |
| Account password (PASSWORD) | Share the source-account password through the secure channel agreed with Eniris. | Customer / installer |
| Installation scope (INSTALLATION_ID_ALLOW_LIST) | Exact installation IDs or numbers to include. Agree explicitly before including every installation. | Customer / installer |

## Set up the connection

1. Ask the provider or account owner to enable the data access required by this connector. Confirm the permitted sites/devices and requested API version.
2. Supply the exact credential types in the table through the agreed secure channel. A portal password, API token, application secret and OAuth grant are not interchangeable.
3. Choose this connector and the target Insights account in onboarding. Enter the required fields and the authorised installation scope, then review before creating.
4. Check the first retrieval against the source account. If access succeeds but no data appears, verify site permissions, API entitlements, identifiers and the availability of measurements.

## Check the result

Check that the first collection completed, then open the intended Insights account and verify the relevant measurements or metadata. Compare source IDs, timestamps and units with the original source. Check the next scheduled execution as well. An active schedule or a healthy job alone does not prove that every requested measurement was received.

For ordinary onboarding meters, creation requests an immediate first run and keeps recurring collection active. Source publication times, upload intervals and provider limits still apply; immediate collection cannot manufacture missing source data.

## If setup does not work

Provide Eniris with the connection name, account/site scope, time of the attempt and the exact error. Check source availability and access permissions before retrying. Share a source screenshot or sample without passwords or tokens.

## Access and costs

Costs are not established for this connector. Confirm provider access, export licences and any project charges with Eniris before activation.

[All connection setup guides](/en/Monitoring/Integrations/connections)


# Fusion Solar portal connection setup


import ClickableImage from '@site/src/components/ClickableImage';

# Fusion Solar portal connection setup

Read measurements available through the authorised Fusion Solar portal connection monitoring account. Only installations visible to that account can be collected.

<ClickableImage src="/img/eniris/monitoring/connection-guides/portal-access.webp" alt="A privacy-safe portal setup flow with sign-in, multi-factor authentication, installation selection and monitoring" maxWidth="1100px" />

*Confirm portal access, select only the agreed installations and complete any approval or multi-factor step before validating the data.*

Connection type: **Portal connection**.

## What to provide

Provide your company and contact person, the intended Insights account, the source identifiers and explicit permission for the requested scope. Include a recent source example for verification.

| Information / setting | What is needed | Supplied or configured by |
| --- | --- | --- |
| Account username (USERNAME) | Account name with access to the requested data. | Customer / installer |
| Account password (PASSWORD) | Share the source-account password through the secure channel agreed with Eniris. | Customer / installer |
| Portal region (REGION) | Region or portal instance in which the requested installations exist. | Customer / installer |
| Installation scope (INSTALLATION_ID_ALLOW_LIST) | Exact installation IDs or numbers to include. Agree explicitly before including every installation. | Customer / installer |
| Exclusions (INSTALLATION_ID_DENY_LIST) | IDs that must not be processed; Eniris checks the identifier type used by this connector. | Customer / installer |

## Set up the connection

1. The customer signs in to the correct provider portal and checks that the requested installations and recent measurements are visible.
2. Grant the agreed account access and supply the required account details securely. Identify any login approval or multi-factor step so Eniris can complete the authorised connection.
3. Select this connector in onboarding, choose the intended Insights account and enter the fields in the table. Restrict installation scope to the agreed list where supported.
4. Create the connection and inspect the first retrieval. A successful manual portal login does not itself prove that the collection service can read data.

## Check the result

Check that the first collection completed, then open the intended Insights account and verify the relevant measurements or metadata. Compare source IDs, timestamps and units with the original source. Check the next scheduled execution as well. An active schedule or a healthy job alone does not prove that every requested measurement was received.

For ordinary onboarding meters, creation requests an immediate first run and keeps recurring collection active. Source publication times, upload intervals and provider limits still apply; immediate collection cannot manufacture missing source data.

## If setup does not work

Provide Eniris with the connection name, account/site scope, time of the attempt and the exact error. Check source availability and access permissions before retrying. Share a source screenshot or sample without passwords or tokens.

## Access and costs

Onboarding classifies this portal connection as free. This label does not establish the terms of a separate provider subscription or equipment licence.

[All connection setup guides](/en/Monitoring/Integrations/connections)


# Fusion Solar Real Time Metrics setup


import ClickableImage from '@site/src/components/ClickableImage';

# Fusion Solar Real Time Metrics setup

Collect current FusionSolar metrics for the permitted installations. Availability and freshness depend on the source platform.

<ClickableImage src="/img/eniris/monitoring/connection-guides/api-authorization.webp" alt="A privacy-safe API setup flow with authorization, limited installation scope, validation and a monitoring dashboard" maxWidth="1100px" />

*A reliable API connection combines the correct authorization method, an explicitly limited installation scope and a verified first retrieval.*

Connection type: **API and platform connection**.

## What to provide

Provide your company and contact person, the intended Insights account, the source identifiers and explicit permission for the requested scope. Include a recent source example for verification.

| Information / setting | What is needed | Supplied or configured by |
| --- | --- | --- |
| Account username (USERNAME) | Account name with access to the requested data. | Customer / installer |
| Account password (PASSWORD) | Share the source-account password through the secure channel agreed with Eniris. | Customer / installer |
| Installation scope (INSTALLATION_ID_ALLOW_LIST) | Exact installation IDs or numbers to include. Agree explicitly before including every installation. | Customer / installer |

## Set up the connection

1. Ask the provider or account owner to enable the data access required by this connector. Confirm the permitted sites/devices and requested API version.
2. Supply the exact credential types in the table through the agreed secure channel. A portal password, API token, application secret and OAuth grant are not interchangeable.
3. Choose this connector and the target Insights account in onboarding. Enter the required fields and the authorised installation scope, then review before creating.
4. Check the first retrieval against the source account. If access succeeds but no data appears, verify site permissions, API entitlements, identifiers and the availability of measurements.

## Check the result

Check that the first collection completed, then open the intended Insights account and verify the relevant measurements or metadata. Compare source IDs, timestamps and units with the original source. Check the next scheduled execution as well. An active schedule or a healthy job alone does not prove that every requested measurement was received.

For ordinary onboarding meters, creation requests an immediate first run and keeps recurring collection active. Source publication times, upload intervals and provider limits still apply; immediate collection cannot manufacture missing source data.

## If setup does not work

Provide Eniris with the connection name, account/site scope, time of the attempt and the exact error. Check source availability and access permissions before retrying. Share a source screenshot or sample without passwords or tokens.

## Access and costs

Costs are not established for this connector. Confirm provider access, export licences and any project charges with Eniris before activation.

[All connection setup guides](/en/Monitoring/Integrations/connections)


# Giv Energy API setup


import ClickableImage from '@site/src/components/ClickableImage';

# Giv Energy API setup

Read Giv Energy data using the provider access configured for this connector. Confirm account permissions, installation scope and the requested measurements before activation.

<ClickableImage src="/img/eniris/monitoring/connection-guides/api-authorization.webp" alt="A privacy-safe API setup flow with authorization, limited installation scope, validation and a monitoring dashboard" maxWidth="1100px" />

*A reliable API connection combines the correct authorization method, an explicitly limited installation scope and a verified first retrieval.*

Connection type: **API and platform connection**.

## What to provide

Provide your company and contact person, the intended Insights account, the source identifiers and explicit permission for the requested scope. Include a recent source example for verification.

| Information / setting | What is needed | Supplied or configured by |
| --- | --- | --- |
| API key (API_KEY) | Obtain the key from the source account owner or provider; confirm its data permissions and share it securely. | Customer / installer |
| Installation scope (INSTALLATION_ID_ALLOW_LIST) | Exact installation IDs or numbers to include. Agree explicitly before including every installation. | Customer / installer |

## Set up the connection

1. Ask the provider or account owner to enable the data access required by this connector. Confirm the permitted sites/devices and requested API version.
2. Supply the exact credential types in the table through the agreed secure channel. A portal password, API token, application secret and OAuth grant are not interchangeable.
3. Choose this connector and the target Insights account in onboarding. Enter the required fields and the authorised installation scope, then review before creating.
4. Check the first retrieval against the source account. If access succeeds but no data appears, verify site permissions, API entitlements, identifiers and the availability of measurements.

## Check the result

Check that the first collection completed, then open the intended Insights account and verify the relevant measurements or metadata. Compare source IDs, timestamps and units with the original source. Check the next scheduled execution as well. An active schedule or a healthy job alone does not prove that every requested measurement was received.

For ordinary onboarding meters, creation requests an immediate first run and keeps recurring collection active. Source publication times, upload intervals and provider limits still apply; immediate collection cannot manufacture missing source data.

## If setup does not work

Provide Eniris with the connection name, account/site scope, time of the attempt and the exact error. Check source availability and access permissions before retrying. Share a source screenshot or sample without passwords or tokens.

## Access and costs

Costs are not established for this connector. Confirm provider access, export licences and any project charges with Eniris before activation.

[All connection setup guides](/en/Monitoring/Integrations/connections)


# Green Power Monitor API setup


import ClickableImage from '@site/src/components/ClickableImage';

# Green Power Monitor API setup

Read Green Power Monitor data using the provider access configured for this connector. Confirm account permissions, installation scope and the requested measurements before activation.

<ClickableImage src="/img/eniris/monitoring/connection-guides/api-authorization.webp" alt="A privacy-safe API setup flow with authorization, limited installation scope, validation and a monitoring dashboard" maxWidth="1100px" />

*A reliable API connection combines the correct authorization method, an explicitly limited installation scope and a verified first retrieval.*

Connection type: **API and platform connection**.

## What to provide

Provide your company and contact person, the intended Insights account, the source identifiers and explicit permission for the requested scope. Include a recent source example for verification.

| Information / setting | What is needed | Supplied or configured by |
| --- | --- | --- |
| Account username (USERNAME) | Account name with access to the requested data. | Customer / installer |
| Account password (PASSWORD) | Share the source-account password through the secure channel agreed with Eniris. | Customer / installer |
| Source endpoint (URL) | Exact endpoint for this customer or deployment; confirm it is reachable by the collection service. | Customer / installer |

## Set up the connection

1. Ask the provider or account owner to enable the data access required by this connector. Confirm the permitted sites/devices and requested API version.
2. Supply the exact credential types in the table through the agreed secure channel. A portal password, API token, application secret and OAuth grant are not interchangeable.
3. Choose this connector and the target Insights account in onboarding. Enter the required fields and the authorised installation scope, then review before creating.
4. Check the first retrieval against the source account. If access succeeds but no data appears, verify site permissions, API entitlements, identifiers and the availability of measurements.

## Check the result

Check that the first collection completed, then open the intended Insights account and verify the relevant measurements or metadata. Compare source IDs, timestamps and units with the original source. Check the next scheduled execution as well. An active schedule or a healthy job alone does not prove that every requested measurement was received.

For ordinary onboarding meters, creation requests an immediate first run and keeps recurring collection active. Source publication times, upload intervals and provider limits still apply; immediate collection cannot manufacture missing source data.

## If setup does not work

Provide Eniris with the connection name, account/site scope, time of the attempt and the exact error. Check source availability and access permissions before retrying. Share a source screenshot or sample without passwords or tokens.

## Access and costs

Costs are not established for this connector. Confirm provider access, export licences and any project charges with Eniris before activation.

[All connection setup guides](/en/Monitoring/Integrations/connections)


# Groupe E setup


import ClickableImage from '@site/src/components/ClickableImage';

# Groupe E setup

Collect the Groupe E Swiss grid-price feed.

<ClickableImage src="/img/eniris/monitoring/connection-guides/market-grid-data.webp" alt="A market area, date range, resolution and units feeding electricity price and grid charts" maxWidth="1100px" />

*Market and grid data must be scoped by area, product, time range, resolution, currency and units before the first comparison.*

Connection type: **Prices and grid data**.

## What to provide

Provide your company and contact person, the intended Insights account, the source identifiers and explicit permission for the requested scope. Include a recent source example for verification.

This connector exposes no standard customer input fields. Eniris must check the configured source, supported scope and any deployment-specific access before activation. An empty form does not mean every source or device is supported.

## Set up the connection

1. Agree market areas, price product or grid dataset, resolution, currency, units and publication date. Distinguish prices from physical meter readings.
2. Eniris checks the configured source and coverage. No customer password is requested by this connector’s current form; that does not guarantee unrestricted source access.
3. Enter the exposed scope and mapping settings, if any. Eniris verifies fixed source coverage where the form offers no selector.
4. Compare the first collected period with the original source, including timestamps, time zone, units and missing intervals.

## Check the result

Check that the first collection completed, then open the intended Insights account and verify the relevant measurements or metadata. Compare source IDs, timestamps and units with the original source. Check the next scheduled execution as well. An active schedule or a healthy job alone does not prove that every requested measurement was received.

For ordinary onboarding meters, creation requests an immediate first run and keeps recurring collection active. Source publication times, upload intervals and provider limits still apply; immediate collection cannot manufacture missing source data.

## If setup does not work

Provide Eniris with the connection name, account/site scope, time of the attempt and the exact error. Check source availability and access permissions before retrying. Share a source screenshot or sample without passwords or tokens.

## Access and costs

Costs are not established for this connector. Confirm provider access, export licences and any project charges with Eniris before activation.

[All connection setup guides](/en/Monitoring/Integrations/connections)


# Growatt (API) setup


import ClickableImage from '@site/src/components/ClickableImage';

# Growatt (API) setup

Read Growatt () data using the provider access configured for this connector. Confirm account permissions, installation scope and the requested measurements before activation.

<ClickableImage src="/img/eniris/monitoring/connection-guides/api-authorization.webp" alt="A privacy-safe API setup flow with authorization, limited installation scope, validation and a monitoring dashboard" maxWidth="1100px" />

*A reliable API connection combines the correct authorization method, an explicitly limited installation scope and a verified first retrieval.*

Connection type: **API and platform connection**.

## What to provide

Provide your company and contact person, the intended Insights account, the source identifiers and explicit permission for the requested scope. Include a recent source example for verification.

| Information / setting | What is needed | Supplied or configured by |
| --- | --- | --- |
| Account username (USERNAME) | Account name with access to the requested data. | Customer / installer |
| API key (API_KEY) | Obtain the key from the source account owner or provider; confirm its data permissions and share it securely. | Customer / installer |
| Installation scope (INSTALLATION_ID_ALLOW_LIST) | Exact installation IDs or numbers to include. Agree explicitly before including every installation. Optional for this connector. | Customer / installer |
| Time zone (TIMEZONE) | Time zone of the source timestamps, for example Europe/Brussels; identify any files already using UTC. | Customer / installer |

## Set up the connection

1. Ask the provider or account owner to enable the data access required by this connector. Confirm the permitted sites/devices and requested API version.
2. Supply the exact credential types in the table through the agreed secure channel. A portal password, API token, application secret and OAuth grant are not interchangeable.
3. Choose this connector and the target Insights account in onboarding. Enter the required fields and the authorised installation scope, then review before creating.
4. Check the first retrieval against the source account. If access succeeds but no data appears, verify site permissions, API entitlements, identifiers and the availability of measurements.

## Check the result

Check that the first collection completed, then open the intended Insights account and verify the relevant measurements or metadata. Compare source IDs, timestamps and units with the original source. Check the next scheduled execution as well. An active schedule or a healthy job alone does not prove that every requested measurement was received.

For ordinary onboarding meters, creation requests an immediate first run and keeps recurring collection active. Source publication times, upload intervals and provider limits still apply; immediate collection cannot manufacture missing source data.

## If setup does not work

Provide Eniris with the connection name, account/site scope, time of the attempt and the exact error. Check source availability and access permissions before retrying. Share a source screenshot or sample without passwords or tokens.

## Access and costs

Costs are not established for this connector. Confirm provider access, export licences and any project charges with Eniris before activation.

[All connection setup guides](/en/Monitoring/Integrations/connections)


# Helexia setup


import ClickableImage from '@site/src/components/ClickableImage';

# Helexia setup

Import Helexia project files using a device name and an agreed inverter configuration.

<ClickableImage src="/img/eniris/monitoring/connection-guides/file-import.webp" alt="A data logger creating a structured file, transferring it securely and mapping its fields to a dashboard" maxWidth="1100px" />

*File onboarding is complete only after the source export, secure delivery, field mapping and recurring arrival have all been checked.*

Connection type: **File import**.

## What to provide

Provide your company and contact person, the intended Insights account, the source identifiers and explicit permission for the requested scope. Include a recent source example for verification.

| Information / setting | What is needed | Supplied or configured by |
| --- | --- | --- |
| Device identity (DEVICE_NAME) | Stable source device identifier or name and its site mapping. | Customer / installer |
| File / folder location (SOURCE_FOLDER) | Agree the delivery folder and file layout. Eniris makes it accessible to the collection service; a path on the customer laptop is insufficient. | Eniris with installer |
| Inverter mapping (INVERTER_CONFS) | Provide inverter identities, file columns and units; Eniris prepares the configuration. | Eniris with installer |
| Time zone (TIMEZONE) | Time zone of the source timestamps, for example Europe/Brussels; identify any files already using UTC. | Customer / installer |

## Set up the connection

1. Identify the source logger or export system and supply an original sample file. Confirm model, firmware, format and time zone with Eniris.
2. Agree the delivery route. For an Eniris FTP destination, request dedicated server, protocol, port, username, password and folder settings from Eniris. Use the agreed protocol exactly.
3. The installer or source owner enables recurring delivery. Eniris configures the accessible source location and device/field mappings; creating a meter does not configure the remote source.
4. Send a test file and record its timestamp. Eniris verifies arrival before starting collection, then compares the processed measurements with the original file.

## Check the result

Check that the first collection completed, then open the intended Insights account and verify the relevant measurements or metadata. Compare source IDs, timestamps and units with the original source. Check the next scheduled execution as well. An active schedule or a healthy job alone does not prove that every requested measurement was received.

For ordinary onboarding meters, creation requests an immediate first run and keeps recurring collection active. Source publication times, upload intervals and provider limits still apply; immediate collection cannot manufacture missing source data.

## If setup does not work

If no file arrives, inspect the logger/export status, destination, authentication, network route and folder. If files arrive but no measurements appear, provide the filename, format, source identifiers and timestamp so Eniris can check parsing and mapping.

## Access and costs

Costs are not established for this connector. Confirm provider access, export licences and any project charges with Eniris before activation.

[All connection setup guides](/en/Monitoring/Integrations/connections)


# Hualogy FTP Export setup


import ClickableImage from '@site/src/components/ClickableImage';

# Hualogy FTP Export setup

Export authorised Insights measurements to a Hualogy FTP destination.

<ClickableImage src="/img/eniris/monitoring/connection-guides/outgoing-export.webp" alt="Authorized monitoring measurements being mapped, encrypted and delivered to a receiving system" maxWidth="1100px" />

*Agree the exact measurement scope and file layout, then verify both delivery and interpretation with the receiving platform.*

Connection type: **Outgoing data export**.

## What to provide

Provide your company and contact person, the intended Insights account, the source identifiers and explicit permission for the requested scope. Include a recent source example for verification.

| Information / setting | What is needed | Supplied or configured by |
| --- | --- | --- |
| File delivery source (BROWSER) | Agree the source location and transport; Eniris configures access without putting credentials in public URLs. | Eniris with installer |
| Time zone (TIMEZONE) | Time zone of the source timestamps, for example Europe/Brussels; identify any files already using UTC. | Customer / installer |

## Set up the connection

1. Agree with the receiving platform which Insights assets and measurements may be exported, the file layout and the delivery interval.
2. Obtain destination credentials from the receiving platform. Eniris separately configures authorised Insights access. These are two different accounts.
3. Eniris enters the destination and mapping, reviews the scope and starts the first export. No datalogger needs to push into Eniris for this route.
4. Ask the receiving platform to confirm both the file arrival and the interpreted measurements; compare timestamps, units and asset identifiers.

## Check the result

Confirm delivery and parsed data with the receiving platform. Compare source IDs, timestamps and units with the original source. Check the next scheduled execution as well. An active schedule or a healthy job alone does not prove that every requested measurement was received.

For ordinary onboarding meters, creation requests an immediate first run and keeps recurring collection active. Source publication times, upload intervals and provider limits still apply; immediate collection cannot manufacture missing source data.

## If setup does not work

Provide Eniris with the connection name, account/site scope, time of the attempt and the exact error. Check source availability and access permissions before retrying. Share a source screenshot or sample without passwords or tokens.

## Access and costs

Costs are not established for this connector. Confirm provider access, export licences and any project charges with Eniris before activation.

[All connection setup guides](/en/Monitoring/Integrations/connections)


# Huawei CSV setup


import ClickableImage from '@site/src/components/ClickableImage';

# Huawei CSV setup

Import the supported Huawei CSV file format. The source must deliver files in the format expected by this connector; renaming another file to CSV does not convert it.

<ClickableImage src="/img/eniris/monitoring/connection-guides/file-import.webp" alt="A data logger creating a structured file, transferring it securely and mapping its fields to a dashboard" maxWidth="1100px" />

*File onboarding is complete only after the source export, secure delivery, field mapping and recurring arrival have all been checked.*

Connection type: **File import**.

## What to provide

Provide your company and contact person, the intended Insights account, the source identifiers and explicit permission for the requested scope. Include a recent source example for verification.

| Information / setting | What is needed | Supplied or configured by |
| --- | --- | --- |
| File delivery source (BROWSER) | Agree the source location and transport; Eniris configures access without putting credentials in public URLs. | Eniris with installer |
| Time zone (TIMEZONE) | Time zone of the source timestamps, for example Europe/Brussels; identify any files already using UTC. | Customer / installer |

## Set up the connection

1. Identify the source logger or export system and supply an original sample file. Confirm model, firmware, format and time zone with Eniris.
2. Agree the delivery route. For an Eniris FTP destination, request dedicated server, protocol, port, username, password and folder settings from Eniris. Use the agreed protocol exactly.
3. The installer or source owner enables recurring delivery. Eniris configures the accessible source location and device/field mappings; creating a meter does not configure the remote source.
4. Send a test file and record its timestamp. Eniris verifies arrival before starting collection, then compares the processed measurements with the original file.

### Configure the datalogger

The installer configures export on the datalogger using FTP credentials supplied by Eniris. Follow the [Huawei SmartLogger FTP setup](https://docs.eniris.com/en/Monitoring/Integrations/datalogger-ftp/huawei) for preparation, model-specific options where documented, and the test upload. Eniris must confirm the exact model and export format for this connector.

## Check the result

Check that the first collection completed, then open the intended Insights account and verify the relevant measurements or metadata. Compare source IDs, timestamps and units with the original source. Check the next scheduled execution as well. An active schedule or a healthy job alone does not prove that every requested measurement was received.

For ordinary onboarding meters, creation requests an immediate first run and keeps recurring collection active. Source publication times, upload intervals and provider limits still apply; immediate collection cannot manufacture missing source data.

## If setup does not work

If no file arrives, inspect the logger/export status, destination, authentication, network route and folder. If files arrive but no measurements appear, provide the filename, format, source identifiers and timestamp so Eniris can check parsing and mapping.

## Access and costs

Costs are not established for this connector. Confirm provider access, export licences and any project charges with Eniris before activation.

[All connection setup guides](/en/Monitoring/Integrations/connections)


# Hupx Dam portal connection setup


import ClickableImage from '@site/src/components/ClickableImage';

# Hupx Dam portal connection setup

Collect Hupx Dam portal connection market or grid-reference data. Agree the market area, product, units, currency and publication period before using the values in reports.

<ClickableImage src="/img/eniris/monitoring/connection-guides/market-grid-data.webp" alt="A market area, date range, resolution and units feeding electricity price and grid charts" maxWidth="1100px" />

*Market and grid data must be scoped by area, product, time range, resolution, currency and units before the first comparison.*

Connection type: **Prices and grid data**.

## What to provide

Provide your company and contact person, the intended Insights account, the source identifiers and explicit permission for the requested scope. Include a recent source example for verification.

This connector exposes no standard customer input fields. Eniris must check the configured source, supported scope and any deployment-specific access before activation. An empty form does not mean every source or device is supported.

## Set up the connection

1. Agree market areas, price product or grid dataset, resolution, currency, units and publication date. Distinguish prices from physical meter readings.
2. Eniris checks the configured source and coverage. No customer password is requested by this connector’s current form; that does not guarantee unrestricted source access.
3. Enter the exposed scope and mapping settings, if any. Eniris verifies fixed source coverage where the form offers no selector.
4. Compare the first collected period with the original source, including timestamps, time zone, units and missing intervals.

## Check the result

Check that the first collection completed, then open the intended Insights account and verify the relevant measurements or metadata. Compare source IDs, timestamps and units with the original source. Check the next scheduled execution as well. An active schedule or a healthy job alone does not prove that every requested measurement was received.

For ordinary onboarding meters, creation requests an immediate first run and keeps recurring collection active. Source publication times, upload intervals and provider limits still apply; immediate collection cannot manufacture missing source data.

## If setup does not work

Provide Eniris with the connection name, account/site scope, time of the attempt and the exact error. Check source availability and access permissions before retrying. Share a source screenshot or sample without passwords or tokens.

## Access and costs

Onboarding classifies this portal connection as free. This label does not establish the terms of a separate provider subscription or equipment licence.

[All connection setup guides](/en/Monitoring/Integrations/connections)


# ILumen portal connection setup


import ClickableImage from '@site/src/components/ClickableImage';

# ILumen portal connection setup

Read measurements available through the authorised ILumen portal connection monitoring account. Only installations visible to that account can be collected.

<ClickableImage src="/img/eniris/monitoring/connection-guides/portal-access.webp" alt="A privacy-safe portal setup flow with sign-in, multi-factor authentication, installation selection and monitoring" maxWidth="1100px" />

*Confirm portal access, select only the agreed installations and complete any approval or multi-factor step before validating the data.*

Connection type: **Portal connection**.

## Before you start

This connector needs an API key in addition to the username and password. Supply all three through the agreed secure handover.

## What to provide

Provide your company and contact person, the intended Insights account, the source identifiers and explicit permission for the requested scope. Include a recent source example for verification.

| Information / setting | What is needed | Supplied or configured by |
| --- | --- | --- |
| Account username (username) | Account name with access to the requested data. | Customer / installer |
| Account password (password) | Share the source-account password through the secure channel agreed with Eniris. | Customer / installer |
| API key (apiKey) | Obtain the key from the source account owner or provider; confirm its data permissions and share it securely. | Customer / installer |

## Set up the connection

1. The customer signs in to the correct provider portal and checks that the requested installations and recent measurements are visible.
2. Grant the agreed account access and supply the required account details securely. Identify any login approval or multi-factor step so Eniris can complete the authorised connection.
3. Select this connector in onboarding, choose the intended Insights account and enter the fields in the table. Restrict installation scope to the agreed list where supported.
4. Create the connection and inspect the first retrieval. A successful manual portal login does not itself prove that the collection service can read data.

## Check the result

Check that the first collection completed, then open the intended Insights account and verify the relevant measurements or metadata. Compare source IDs, timestamps and units with the original source. Check the next scheduled execution as well. An active schedule or a healthy job alone does not prove that every requested measurement was received.

For ordinary onboarding meters, creation requests an immediate first run and keeps recurring collection active. Source publication times, upload intervals and provider limits still apply; immediate collection cannot manufacture missing source data.

## If setup does not work

Provide Eniris with the connection name, account/site scope, time of the attempt and the exact error. Check source availability and access permissions before retrying. Share a source screenshot or sample without passwords or tokens.

## Access and costs

Onboarding classifies this portal connection as free. This label does not establish the terms of a separate provider subscription or equipment licence.

[All connection setup guides](/en/Monitoring/Integrations/connections)


# Connection setup guides


import ClickableImage from '@site/src/components/ClickableImage';

# Connection setup guides

Select the exact connection used in onboarding. Each guide explains what to provide, who configures access, how to set up the connection and how to verify the result. There are 145 available connectors. API, portal and file variants have different requirements.

<ClickableImage src="/img/eniris/monitoring/integrations/integration-routes.webp" alt="Local, cloud and scheduled data routes leading from energy assets to a monitoring dashboard" maxWidth="1100px" />

*Choose the guide that matches the real data route: API, portal, file, local device, export, market or weather data.*

## API and platform connection

- [Abb API](https://docs.eniris.com/en/Monitoring/Integrations/connections/abb-api)
- [Cast4 All API](https://docs.eniris.com/en/Monitoring/Integrations/connections/cast4-all-api)
- [Dexter API](https://docs.eniris.com/en/Monitoring/Integrations/connections/dexter-api)
- [Ealyze API](https://docs.eniris.com/en/Monitoring/Integrations/connections/ealyze-api)
- [Efento API](https://docs.eniris.com/en/Monitoring/Integrations/connections/efento-api)
- [Elgris API](https://docs.eniris.com/en/Monitoring/Integrations/connections/elgris-api)
- [Emb2020 API](https://docs.eniris.com/en/Monitoring/Integrations/connections/emb2020-api)
- [Emi API](https://docs.eniris.com/en/Monitoring/Integrations/connections/emi-api)
- [Eniscope API](https://docs.eniris.com/en/Monitoring/Integrations/connections/eniscope-api)
- [Enphase API](https://docs.eniris.com/en/Monitoring/Integrations/connections/enphase-api)
- [Envitron API](https://docs.eniris.com/en/Monitoring/Integrations/connections/envitron-api)
- [Epias API](https://docs.eniris.com/en/Monitoring/Integrations/connections/epias-api)
- [Ewon](https://docs.eniris.com/en/Monitoring/Integrations/connections/ewon)
- [Fluvius API](https://docs.eniris.com/en/Monitoring/Integrations/connections/fluvius-api)
- [Fudura API](https://docs.eniris.com/en/Monitoring/Integrations/connections/fudura-api)
- [Fusion Solar Alarms](https://docs.eniris.com/en/Monitoring/Integrations/connections/fusion-solar-alarms)
- [Fusion Solar API Historical Metric](https://docs.eniris.com/en/Monitoring/Integrations/connections/fusion-solar-api-historical-metric)
- [Fusion Solar API Meta Data](https://docs.eniris.com/en/Monitoring/Integrations/connections/fusion-solar-api-meta-data)
- [Fusion Solar Real Time Metrics](https://docs.eniris.com/en/Monitoring/Integrations/connections/fusion-solar-real-time-metrics)
- [Giv Energy API](https://docs.eniris.com/en/Monitoring/Integrations/connections/giv-energy-api)
- [Green Power Monitor API](https://docs.eniris.com/en/Monitoring/Integrations/connections/green-power-monitor-api)
- [Growatt (API)](https://docs.eniris.com/en/Monitoring/Integrations/connections/growatt-api)
- [Innax API](https://docs.eniris.com/en/Monitoring/Integrations/connections/innax-api)
- [Meterbeheer API](https://docs.eniris.com/en/Monitoring/Integrations/connections/meterbeheer-api)
- [Nea API](https://docs.eniris.com/en/Monitoring/Integrations/connections/nea-api)
- [Nibe API](https://docs.eniris.com/en/Monitoring/Integrations/connections/nibe-api)
- [Nmbs Data](https://docs.eniris.com/en/Monitoring/Integrations/connections/nmbs-data)
- [Opinum API](https://docs.eniris.com/en/Monitoring/Integrations/connections/opinum-api)
- [Qantum Meta Data Sync](https://docs.eniris.com/en/Monitoring/Integrations/connections/qantum-meta-data-sync)
- [SMA (Sunny Portal API)](https://docs.eniris.com/en/Monitoring/Integrations/connections/sma-sunny-portal-api)
- [Smappee API](https://docs.eniris.com/en/Monitoring/Integrations/connections/smappee-api)
- [SolarEdge (official API)](https://docs.eniris.com/en/Monitoring/Integrations/connections/solaredge-official-api)
- [Solarman (API)](https://docs.eniris.com/en/Monitoring/Integrations/connections/solarman-api)
- [Solis (SolisCloud API)](https://docs.eniris.com/en/Monitoring/Integrations/connections/solis-soliscloud-api)
- [Sonnen Battery Data Recovery](https://docs.eniris.com/en/Monitoring/Integrations/connections/sonnen-battery-data-recovery)
- [Studer](https://docs.eniris.com/en/Monitoring/Integrations/connections/studer)
- [Vensys API](https://docs.eniris.com/en/Monitoring/Integrations/connections/vensys-api)
- [Windup API](https://docs.eniris.com/en/Monitoring/Integrations/connections/windup-api)

## File import

- [Cadis CSV](https://docs.eniris.com/en/Monitoring/Integrations/connections/cadis-csv)
- [Cloud Gate CSV](https://docs.eniris.com/en/Monitoring/Integrations/connections/cloud-gate-csv)
- [Cloud Gate FTP](https://docs.eniris.com/en/Monitoring/Integrations/connections/cloud-gate-ftp)
- [Cme3100](https://docs.eniris.com/en/Monitoring/Integrations/connections/cme3100)
- [CSV](https://docs.eniris.com/en/Monitoring/Integrations/connections/csv)
- [Elli Track CSV](https://docs.eniris.com/en/Monitoring/Integrations/connections/elli-track-csv)
- [Eniris Electricity Excel](https://docs.eniris.com/en/Monitoring/Integrations/connections/eniris-electricity-excel)
- [File](https://docs.eniris.com/en/Monitoring/Integrations/connections/file)
- [Fluvius NPSCsv Meter Deprecated](https://docs.eniris.com/en/Monitoring/Integrations/connections/fluvius-npscsv-meter-deprecated)
- [Fluvius Nps CSV](https://docs.eniris.com/en/Monitoring/Integrations/connections/fluvius-nps-csv)
- [Fronius JSON](https://docs.eniris.com/en/Monitoring/Integrations/connections/fronius-json)
- [Fronius Txt](https://docs.eniris.com/en/Monitoring/Integrations/connections/fronius-txt)
- [Helexia](https://docs.eniris.com/en/Monitoring/Integrations/connections/helexia)
- [Huawei CSV](https://docs.eniris.com/en/Monitoring/Integrations/connections/huawei-csv)
- [Moxa CSV](https://docs.eniris.com/en/Monitoring/Integrations/connections/moxa-csv)
- [Profi Nrg CSV](https://docs.eniris.com/en/Monitoring/Integrations/connections/profi-nrg-csv)
- [SMA CSV](https://docs.eniris.com/en/Monitoring/Integrations/connections/sma-csv)
- [SMA XML](https://docs.eniris.com/en/Monitoring/Integrations/connections/sma-xml)
- [Sofar](https://docs.eniris.com/en/Monitoring/Integrations/connections/sofar)
- [Solar Log CSV](https://docs.eniris.com/en/Monitoring/Integrations/connections/solar-log-csv)
- [Sun Rock CSV](https://docs.eniris.com/en/Monitoring/Integrations/connections/sun-rock-csv)
- [Sungrow XML](https://docs.eniris.com/en/Monitoring/Integrations/connections/sungrow-xml)
- [Two Wire CSV](https://docs.eniris.com/en/Monitoring/Integrations/connections/two-wire-csv)
- [Webdyn Sun](https://docs.eniris.com/en/Monitoring/Integrations/connections/webdyn-sun)
- [Webdynsun CSV](https://docs.eniris.com/en/Monitoring/Integrations/connections/webdynsun-csv)
- [Webdynsun Manual](https://docs.eniris.com/en/Monitoring/Integrations/connections/webdynsun-manual)

## Internal automation

- [Add Or Remove User To Roles](https://docs.eniris.com/en/Monitoring/Integrations/connections/add-or-remove-user-to-roles)
- [Rocket Chat](https://docs.eniris.com/en/Monitoring/Integrations/connections/rocket-chat)
- [Sales Handy2 Zoho API](https://docs.eniris.com/en/Monitoring/Integrations/connections/sales-handy2-zoho-api)
- [System Metrics](https://docs.eniris.com/en/Monitoring/Integrations/connections/system-metrics)
- [Toolbox Alarms](https://docs.eniris.com/en/Monitoring/Integrations/connections/toolbox-alarms)
- [Toolbox Insights Sync](https://docs.eniris.com/en/Monitoring/Integrations/connections/toolbox-insights-sync)
- [Toolbox Revenue](https://docs.eniris.com/en/Monitoring/Integrations/connections/toolbox-revenue)
- [Uptime Kuma](https://docs.eniris.com/en/Monitoring/Integrations/connections/uptime-kuma)
- [Zoho Add Country To Contacts](https://docs.eniris.com/en/Monitoring/Integrations/connections/zoho-add-country-to-contacts)
- [Zoho Detect And Update Silent Lead Contacts](https://docs.eniris.com/en/Monitoring/Integrations/connections/zoho-detect-and-update-silent-lead-contacts)
- [Zoho Follow Up Mail](https://docs.eniris.com/en/Monitoring/Integrations/connections/zoho-follow-up-mail)
- [Zoho Google Calendar](https://docs.eniris.com/en/Monitoring/Integrations/connections/zoho-google-calendar)
- [Zoho Merge Accounts](https://docs.eniris.com/en/Monitoring/Integrations/connections/zoho-merge-accounts)
- [Zoho Odoo API](https://docs.eniris.com/en/Monitoring/Integrations/connections/zoho-odoo-api)
- [Zoho Reopen Inactive Clients](https://docs.eniris.com/en/Monitoring/Integrations/connections/zoho-reopen-inactive-clients)
- [Zoho Sales Handy Checkbox](https://docs.eniris.com/en/Monitoring/Integrations/connections/zoho-sales-handy-checkbox)
- [Zoho Status Updater API](https://docs.eniris.com/en/Monitoring/Integrations/connections/zoho-status-updater-api)
- [controller](https://docs.eniris.com/en/Monitoring/Integrations/connections/controller)

## Local devices

- [Etrel Tcp Modpus](https://docs.eniris.com/en/Monitoring/Integrations/connections/etrel-tcp-modpus)
- [Siemens S7 1200](https://docs.eniris.com/en/Monitoring/Integrations/connections/siemens-s7-1200)
- [Youless](https://docs.eniris.com/en/Monitoring/Integrations/connections/youless)

## Outgoing data export

- [Hualogy FTP Export](https://docs.eniris.com/en/Monitoring/Integrations/connections/hualogy-ftp-export)
- [Solora FTP Export](https://docs.eniris.com/en/Monitoring/Integrations/connections/solora-ftp-export)
- [Synapti QFtp Push](https://docs.eniris.com/en/Monitoring/Integrations/connections/synapti-qftp-push)

## Portal connection

- [Ampere portal connection](https://docs.eniris.com/en/Monitoring/Integrations/connections/ampere-portal-connection)
- [Anexo portal connection](https://docs.eniris.com/en/Monitoring/Integrations/connections/anexo-portal-connection)
- [ESolar portal connection](https://docs.eniris.com/en/Monitoring/Integrations/connections/esolar-portal-connection)
- [EWTDirect Wind portal connection](https://docs.eniris.com/en/Monitoring/Integrations/connections/ewtdirect-wind-portal-connection)
- [Elekeeper portal connection](https://docs.eniris.com/en/Monitoring/Integrations/connections/elekeeper-portal-connection)
- [Enercon portal connection](https://docs.eniris.com/en/Monitoring/Integrations/connections/enercon-portal-connection)
- [Ennex Os portal connection](https://docs.eniris.com/en/Monitoring/Integrations/connections/ennex-os-portal-connection)
- [Enphase portal connection](https://docs.eniris.com/en/Monitoring/Integrations/connections/enphase-portal-connection)
- [Fimer portal connection](https://docs.eniris.com/en/Monitoring/Integrations/connections/fimer-portal-connection)
- [Flexpond portal connection](https://docs.eniris.com/en/Monitoring/Integrations/connections/flexpond-portal-connection)
- [Fronius portal connection](https://docs.eniris.com/en/Monitoring/Integrations/connections/fronius-portal-connection)
- [Fusion Solar portal connection](https://docs.eniris.com/en/Monitoring/Integrations/connections/fusion-solar-portal-connection)
- [ILumen portal connection](https://docs.eniris.com/en/Monitoring/Integrations/connections/ilumen-portal-connection)
- [Net Eco portal connection](https://docs.eniris.com/en/Monitoring/Integrations/connections/net-eco-portal-connection)
- [Panasonic portal connection](https://docs.eniris.com/en/Monitoring/Integrations/connections/panasonic-portal-connection)
- [Power Router portal connection](https://docs.eniris.com/en/Monitoring/Integrations/connections/power-router-portal-connection)
- [Scipher portal connection](https://docs.eniris.com/en/Monitoring/Integrations/connections/scipher-portal-connection)
- [Sems Plus portal connection](https://docs.eniris.com/en/Monitoring/Integrations/connections/sems-plus-portal-connection)
- [Sems portal connection](https://docs.eniris.com/en/Monitoring/Integrations/connections/sems-portal-connection)
- [Sigenergy portal connection](https://docs.eniris.com/en/Monitoring/Integrations/connections/sigenergy-portal-connection)
- [SolarEdge (portal connection)](https://docs.eniris.com/en/Monitoring/Integrations/connections/solaredge-portal-connection)
- [Solar Log portal connection](https://docs.eniris.com/en/Monitoring/Integrations/connections/solar-log-portal-connection)
- [Solar Man portal connection](https://docs.eniris.com/en/Monitoring/Integrations/connections/solar-man-portal-connection)
- [Sungrow ISolar Cloud portal connection](https://docs.eniris.com/en/Monitoring/Integrations/connections/sungrow-isolar-cloud-portal-connection)

## Prices and grid data

- [Ckw](https://docs.eniris.com/en/Monitoring/Integrations/connections/ckw)
- [Day Ahead Price Aggregator](https://docs.eniris.com/en/Monitoring/Integrations/connections/day-ahead-price-aggregator)
- [Day Ahead Price Rolling Average](https://docs.eniris.com/en/Monitoring/Integrations/connections/day-ahead-price-rolling-average)
- [Ekz](https://docs.eniris.com/en/Monitoring/Integrations/connections/ekz)
- [Elex Dam](https://docs.eniris.com/en/Monitoring/Integrations/connections/elex-dam)
- [Elex Prediction](https://docs.eniris.com/en/Monitoring/Integrations/connections/elex-prediction)
- [Enexgroup Xlsx](https://docs.eniris.com/en/Monitoring/Integrations/connections/enexgroup-xlsx)
- [Entsoe API](https://docs.eniris.com/en/Monitoring/Integrations/connections/entsoe-api)
- [Entsoe File](https://docs.eniris.com/en/Monitoring/Integrations/connections/entsoe-file)
- [Epex portal connection](https://docs.eniris.com/en/Monitoring/Integrations/connections/epex-portal-connection)
- [Frank Energie API](https://docs.eniris.com/en/Monitoring/Integrations/connections/frank-energie-api)
- [Groupe E](https://docs.eniris.com/en/Monitoring/Integrations/connections/groupe-e)
- [Hupx Dam portal connection](https://docs.eniris.com/en/Monitoring/Integrations/connections/hupx-dam-portal-connection)
- [Memo Dam portal connection](https://docs.eniris.com/en/Monitoring/Integrations/connections/memo-dam-portal-connection)
- [Memo Excel Dam portal connection](https://docs.eniris.com/en/Monitoring/Integrations/connections/memo-excel-dam-portal-connection)
- [Nord Pool portal connection](https://docs.eniris.com/en/Monitoring/Integrations/connections/nord-pool-portal-connection)
- [Okte API](https://docs.eniris.com/en/Monitoring/Integrations/connections/okte-api)
- [Oree Xlsx](https://docs.eniris.com/en/Monitoring/Integrations/connections/oree-xlsx)
- [Swiss Grid Price](https://docs.eniris.com/en/Monitoring/Integrations/connections/swiss-grid-price)
- [Swiss PVTarif API](https://docs.eniris.com/en/Monitoring/Integrations/connections/swiss-pvtarif-api)
- [Tennet portal connection](https://docs.eniris.com/en/Monitoring/Integrations/connections/tennet-portal-connection)
- [Vlaamsenutsregulator portal connection](https://docs.eniris.com/en/Monitoring/Integrations/connections/vlaamsenutsregulator-portal-connection)

## Weather data

- [Aemet API](https://docs.eniris.com/en/Monitoring/Integrations/connections/aemet-api)
- [Cds API](https://docs.eniris.com/en/Monitoring/Integrations/connections/cds-api)
- [Kmi API](https://docs.eniris.com/en/Monitoring/Integrations/connections/kmi-api)
- [Kmi portal connection](https://docs.eniris.com/en/Monitoring/Integrations/connections/kmi-portal-connection)
- [Knmi API](https://docs.eniris.com/en/Monitoring/Integrations/connections/knmi-api)
- [Knmi Data Platform API](https://docs.eniris.com/en/Monitoring/Integrations/connections/knmi-data-platform-api)
- [Met Office API](https://docs.eniris.com/en/Monitoring/Integrations/connections/met-office-api)
- [Meteo Swiss portal connection](https://docs.eniris.com/en/Monitoring/Integrations/connections/meteo-swiss-portal-connection)
- [Open Meteo API](https://docs.eniris.com/en/Monitoring/Integrations/connections/open-meteo-api)
- [Open Weather Map API](https://docs.eniris.com/en/Monitoring/Integrations/connections/open-weather-map-api)
- [Rmi Synoptic portal connection](https://docs.eniris.com/en/Monitoring/Integrations/connections/rmi-synoptic-portal-connection)

Choose the connection matching your platform and data format.


# Innax API setup


import ClickableImage from '@site/src/components/ClickableImage';

# Innax API setup

Read Innax data using the provider access configured for this connector. Confirm account permissions, installation scope and the requested measurements before activation.

<ClickableImage src="/img/eniris/monitoring/connection-guides/api-authorization.webp" alt="A privacy-safe API setup flow with authorization, limited installation scope, validation and a monitoring dashboard" maxWidth="1100px" />

*A reliable API connection combines the correct authorization method, an explicitly limited installation scope and a verified first retrieval.*

Connection type: **API and platform connection**.

## What to provide

Provide your company and contact person, the intended Insights account, the source identifiers and explicit permission for the requested scope. Include a recent source example for verification.

| Information / setting | What is needed | Supplied or configured by |
| --- | --- | --- |
| Application / key ID (CLIENT_ID) | Identifier belonging to the supplied secret and provider account. | Customer / installer |
| API/application secret (SECRET) | Secret paired with the corresponding client, application or API key ID; share securely. | Customer / installer |
| Refresh token (REFRESH_TOKEN) | Authorised refresh token for the agreed provider application; share securely. | Customer / installer |

## Set up the connection

1. Ask the provider or account owner to enable the data access required by this connector. Confirm the permitted sites/devices and requested API version.
2. Supply the exact credential types in the table through the agreed secure channel. A portal password, API token, application secret and OAuth grant are not interchangeable.
3. Choose this connector and the target Insights account in onboarding. Enter the required fields and the authorised installation scope, then review before creating.
4. Check the first retrieval against the source account. If access succeeds but no data appears, verify site permissions, API entitlements, identifiers and the availability of measurements.

## Check the result

Check that the first collection completed, then open the intended Insights account and verify the relevant measurements or metadata. Compare source IDs, timestamps and units with the original source. Check the next scheduled execution as well. An active schedule or a healthy job alone does not prove that every requested measurement was received.

For ordinary onboarding meters, creation requests an immediate first run and keeps recurring collection active. Source publication times, upload intervals and provider limits still apply; immediate collection cannot manufacture missing source data.

## If setup does not work

Provide Eniris with the connection name, account/site scope, time of the attempt and the exact error. Check source availability and access permissions before retrying. Share a source screenshot or sample without passwords or tokens.

## Access and costs

Costs are not established for this connector. Confirm provider access, export licences and any project charges with Eniris before activation.

[All connection setup guides](/en/Monitoring/Integrations/connections)


# Kmi API setup


import ClickableImage from '@site/src/components/ClickableImage';

# Kmi API setup

Collect Kmi weather data for the scope supported by the deployed connector. Agree the stations, variables and geographic coverage before activation.

<ClickableImage src="/img/eniris/monitoring/connection-guides/weather-data.webp" alt="A location, weather variables, time zone and forecast series feeding an energy monitoring dashboard" maxWidth="1100px" />

*Select the correct location, variables, units and time zone before comparing the collected series with the weather source.*

Connection type: **Weather data**.

## What to provide

Provide your company and contact person, the intended Insights account, the source identifiers and explicit permission for the requested scope. Include a recent source example for verification.

This connector exposes no standard customer input fields. Eniris must check the configured source, supported scope and any deployment-specific access before activation. An empty form does not mean every source or device is supported.

## Set up the connection

1. Agree stations or coordinates, required weather variables, units, forecast versus observations and source timestamps.
2. Eniris checks the configured source and coverage. No customer password is requested by this connector’s current form; that does not guarantee unrestricted source access.
3. Enter the exposed scope and mapping settings, if any. Eniris verifies fixed source coverage where the form offers no selector.
4. Compare the first collected period with the original source, including timestamps, time zone, units and missing intervals.

## Check the result

Check that the first collection completed, then open the intended Insights account and verify the relevant measurements or metadata. Compare source IDs, timestamps and units with the original source. Check the next scheduled execution as well. An active schedule or a healthy job alone does not prove that every requested measurement was received.

For ordinary onboarding meters, creation requests an immediate first run and keeps recurring collection active. Source publication times, upload intervals and provider limits still apply; immediate collection cannot manufacture missing source data.

## If setup does not work

Provide Eniris with the connection name, account/site scope, time of the attempt and the exact error. Check source availability and access permissions before retrying. Share a source screenshot or sample without passwords or tokens.

## Access and costs

Costs are not established for this connector. Confirm provider access, export licences and any project charges with Eniris before activation.

[All connection setup guides](/en/Monitoring/Integrations/connections)


# Kmi portal connection setup


import ClickableImage from '@site/src/components/ClickableImage';

# Kmi portal connection setup

Collect Kmi portal connection weather data for the scope supported by the deployed connector. Agree the stations, variables and geographic coverage before activation.

<ClickableImage src="/img/eniris/monitoring/connection-guides/weather-data.webp" alt="A location, weather variables, time zone and forecast series feeding an energy monitoring dashboard" maxWidth="1100px" />

*Select the correct location, variables, units and time zone before comparing the collected series with the weather source.*

Connection type: **Weather data**.

## What to provide

Provide your company and contact person, the intended Insights account, the source identifiers and explicit permission for the requested scope. Include a recent source example for verification.

This connector exposes no standard customer input fields. Eniris must check the configured source, supported scope and any deployment-specific access before activation. An empty form does not mean every source or device is supported.

## Set up the connection

1. Agree stations or coordinates, required weather variables, units, forecast versus observations and source timestamps.
2. Eniris checks the configured source and coverage. No customer password is requested by this connector’s current form; that does not guarantee unrestricted source access.
3. Enter the exposed scope and mapping settings, if any. Eniris verifies fixed source coverage where the form offers no selector.
4. Compare the first collected period with the original source, including timestamps, time zone, units and missing intervals.

## Check the result

Check that the first collection completed, then open the intended Insights account and verify the relevant measurements or metadata. Compare source IDs, timestamps and units with the original source. Check the next scheduled execution as well. An active schedule or a healthy job alone does not prove that every requested measurement was received.

For ordinary onboarding meters, creation requests an immediate first run and keeps recurring collection active. Source publication times, upload intervals and provider limits still apply; immediate collection cannot manufacture missing source data.

## If setup does not work

Provide Eniris with the connection name, account/site scope, time of the attempt and the exact error. Check source availability and access permissions before retrying. Share a source screenshot or sample without passwords or tokens.

## Access and costs

Onboarding classifies this portal connection as free. This label does not establish the terms of a separate provider subscription or equipment licence.

[All connection setup guides](/en/Monitoring/Integrations/connections)


# Knmi API setup


import ClickableImage from '@site/src/components/ClickableImage';

# Knmi API setup

Collect Knmi weather data for the scope supported by the deployed connector. Agree the stations, variables and geographic coverage before activation.

<ClickableImage src="/img/eniris/monitoring/connection-guides/weather-data.webp" alt="A location, weather variables, time zone and forecast series feeding an energy monitoring dashboard" maxWidth="1100px" />

*Select the correct location, variables, units and time zone before comparing the collected series with the weather source.*

Connection type: **Weather data**.

## What to provide

Provide your company and contact person, the intended Insights account, the source identifiers and explicit permission for the requested scope. Include a recent source example for verification.

This connector exposes no standard customer input fields. Eniris must check the configured source, supported scope and any deployment-specific access before activation. An empty form does not mean every source or device is supported.

## Set up the connection

1. Agree stations or coordinates, required weather variables, units, forecast versus observations and source timestamps.
2. Eniris checks the configured source and coverage. No customer password is requested by this connector’s current form; that does not guarantee unrestricted source access.
3. Enter the exposed scope and mapping settings, if any. Eniris verifies fixed source coverage where the form offers no selector.
4. Compare the first collected period with the original source, including timestamps, time zone, units and missing intervals.

## Check the result

Check that the first collection completed, then open the intended Insights account and verify the relevant measurements or metadata. Compare source IDs, timestamps and units with the original source. Check the next scheduled execution as well. An active schedule or a healthy job alone does not prove that every requested measurement was received.

For ordinary onboarding meters, creation requests an immediate first run and keeps recurring collection active. Source publication times, upload intervals and provider limits still apply; immediate collection cannot manufacture missing source data.

## If setup does not work

Provide Eniris with the connection name, account/site scope, time of the attempt and the exact error. Check source availability and access permissions before retrying. Share a source screenshot or sample without passwords or tokens.

## Access and costs

Costs are not established for this connector. Confirm provider access, export licences and any project charges with Eniris before activation.

[All connection setup guides](/en/Monitoring/Integrations/connections)


# Knmi Data Platform API setup


import ClickableImage from '@site/src/components/ClickableImage';

# Knmi Data Platform API setup

Collect Knmi Data Platform weather data for the scope supported by the deployed connector. Agree the stations, variables and geographic coverage before activation.

<ClickableImage src="/img/eniris/monitoring/connection-guides/weather-data.webp" alt="A location, weather variables, time zone and forecast series feeding an energy monitoring dashboard" maxWidth="1100px" />

*Select the correct location, variables, units and time zone before comparing the collected series with the weather source.*

Connection type: **Weather data**.

## What to provide

Provide your company and contact person, the intended Insights account, the source identifiers and explicit permission for the requested scope. Include a recent source example for verification.

| Information / setting | What is needed | Supplied or configured by |
| --- | --- | --- |
| API key (API_KEY) | Obtain the key from the source account owner or provider; confirm its data permissions and share it securely. | Customer / installer |

## Set up the connection

1. Agree stations or coordinates, required weather variables, units, forecast versus observations and source timestamps.
2. Obtain the required provider access shown in the table and confirm the permitted dataset. Supply secrets securely.
3. Enter the exposed scope and mapping settings, if any. Eniris verifies fixed source coverage where the form offers no selector.
4. Compare the first collected period with the original source, including timestamps, time zone, units and missing intervals.

## Check the result

Check that the first collection completed, then open the intended Insights account and verify the relevant measurements or metadata. Compare source IDs, timestamps and units with the original source. Check the next scheduled execution as well. An active schedule or a healthy job alone does not prove that every requested measurement was received.

For ordinary onboarding meters, creation requests an immediate first run and keeps recurring collection active. Source publication times, upload intervals and provider limits still apply; immediate collection cannot manufacture missing source data.

## If setup does not work

Provide Eniris with the connection name, account/site scope, time of the attempt and the exact error. Check source availability and access permissions before retrying. Share a source screenshot or sample without passwords or tokens.

## Access and costs

Costs are not established for this connector. Confirm provider access, export licences and any project charges with Eniris before activation.

[All connection setup guides](/en/Monitoring/Integrations/connections)


# Memo Dam portal connection setup


import ClickableImage from '@site/src/components/ClickableImage';

# Memo Dam portal connection setup

Collect Memo Dam portal connection market or grid-reference data. Agree the market area, product, units, currency and publication period before using the values in reports.

<ClickableImage src="/img/eniris/monitoring/connection-guides/market-grid-data.webp" alt="A market area, date range, resolution and units feeding electricity price and grid charts" maxWidth="1100px" />

*Market and grid data must be scoped by area, product, time range, resolution, currency and units before the first comparison.*

Connection type: **Prices and grid data**.

## What to provide

Provide your company and contact person, the intended Insights account, the source identifiers and explicit permission for the requested scope. Include a recent source example for verification.

This connector exposes no standard customer input fields. Eniris must check the configured source, supported scope and any deployment-specific access before activation. An empty form does not mean every source or device is supported.

## Set up the connection

1. Agree market areas, price product or grid dataset, resolution, currency, units and publication date. Distinguish prices from physical meter readings.
2. Eniris checks the configured source and coverage. No customer password is requested by this connector’s current form; that does not guarantee unrestricted source access.
3. Enter the exposed scope and mapping settings, if any. Eniris verifies fixed source coverage where the form offers no selector.
4. Compare the first collected period with the original source, including timestamps, time zone, units and missing intervals.

## Check the result

Check that the first collection completed, then open the intended Insights account and verify the relevant measurements or metadata. Compare source IDs, timestamps and units with the original source. Check the next scheduled execution as well. An active schedule or a healthy job alone does not prove that every requested measurement was received.

For ordinary onboarding meters, creation requests an immediate first run and keeps recurring collection active. Source publication times, upload intervals and provider limits still apply; immediate collection cannot manufacture missing source data.

## If setup does not work

Provide Eniris with the connection name, account/site scope, time of the attempt and the exact error. Check source availability and access permissions before retrying. Share a source screenshot or sample without passwords or tokens.

## Access and costs

Onboarding classifies this portal connection as free. This label does not establish the terms of a separate provider subscription or equipment licence.

[All connection setup guides](/en/Monitoring/Integrations/connections)


# Memo Excel Dam portal connection setup


import ClickableImage from '@site/src/components/ClickableImage';

# Memo Excel Dam portal connection setup

Collect Memo Excel Dam portal connection market or grid-reference data. Agree the market area, product, units, currency and publication period before using the values in reports.

<ClickableImage src="/img/eniris/monitoring/connection-guides/market-grid-data.webp" alt="A market area, date range, resolution and units feeding electricity price and grid charts" maxWidth="1100px" />

*Market and grid data must be scoped by area, product, time range, resolution, currency and units before the first comparison.*

Connection type: **Prices and grid data**.

## What to provide

Provide your company and contact person, the intended Insights account, the source identifiers and explicit permission for the requested scope. Include a recent source example for verification.

This connector exposes no standard customer input fields. Eniris must check the configured source, supported scope and any deployment-specific access before activation. An empty form does not mean every source or device is supported.

## Set up the connection

1. Agree market areas, price product or grid dataset, resolution, currency, units and publication date. Distinguish prices from physical meter readings.
2. Eniris checks the configured source and coverage. No customer password is requested by this connector’s current form; that does not guarantee unrestricted source access.
3. Enter the exposed scope and mapping settings, if any. Eniris verifies fixed source coverage where the form offers no selector.
4. Compare the first collected period with the original source, including timestamps, time zone, units and missing intervals.

## Check the result

Check that the first collection completed, then open the intended Insights account and verify the relevant measurements or metadata. Compare source IDs, timestamps and units with the original source. Check the next scheduled execution as well. An active schedule or a healthy job alone does not prove that every requested measurement was received.

For ordinary onboarding meters, creation requests an immediate first run and keeps recurring collection active. Source publication times, upload intervals and provider limits still apply; immediate collection cannot manufacture missing source data.

## If setup does not work

Provide Eniris with the connection name, account/site scope, time of the attempt and the exact error. Check source availability and access permissions before retrying. Share a source screenshot or sample without passwords or tokens.

## Access and costs

Onboarding classifies this portal connection as free. This label does not establish the terms of a separate provider subscription or equipment licence.

[All connection setup guides](/en/Monitoring/Integrations/connections)


# Met Office API setup


import ClickableImage from '@site/src/components/ClickableImage';

# Met Office API setup

Collect Met Office weather data for the scope supported by the deployed connector. Agree the stations, variables and geographic coverage before activation.

<ClickableImage src="/img/eniris/monitoring/connection-guides/weather-data.webp" alt="A location, weather variables, time zone and forecast series feeding an energy monitoring dashboard" maxWidth="1100px" />

*Select the correct location, variables, units and time zone before comparing the collected series with the weather source.*

Connection type: **Weather data**.

## Before you start

Supply the area in north/east/south/west order, the order ID and the requested latitude/longitude grid steps. Eniris manages the download file location.

## What to provide

Provide your company and contact person, the intended Insights account, the source identifiers and explicit permission for the requested scope. Include a recent source example for verification.

| Information / setting | What is needed | Supplied or configured by |
| --- | --- | --- |
| API key (API_KEY) | Obtain the key from the source account owner or provider; confirm its data permissions and share it securely. | Customer / installer |
| Data order ID (ORDER_ID) | Identifier of the authorised provider data order. | Customer / installer |
| Geographic area (COORDINATES) | Requested bounding box in the coordinate order specified in this guide. | Customer / installer |
| Grid spacing (LATITUDE_STEP) | Requested geographic grid step in degrees, agreed with Eniris. | Customer / installer |
| Grid spacing (LONGITUDE_STEP) | Requested geographic grid step in degrees, agreed with Eniris. | Customer / installer |
| Download location (FILEPATH) | Writable working location for downloaded data, configured on the collection service. | Eniris |

## Set up the connection

1. Agree stations or coordinates, required weather variables, units, forecast versus observations and source timestamps.
2. Obtain the required provider access shown in the table and confirm the permitted dataset. Supply secrets securely.
3. Enter the exposed scope and mapping settings, if any. Eniris verifies fixed source coverage where the form offers no selector.
4. Compare the first collected period with the original source, including timestamps, time zone, units and missing intervals.

## Check the result

Check that the first collection completed, then open the intended Insights account and verify the relevant measurements or metadata. Compare source IDs, timestamps and units with the original source. Check the next scheduled execution as well. An active schedule or a healthy job alone does not prove that every requested measurement was received.

For ordinary onboarding meters, creation requests an immediate first run and keeps recurring collection active. Source publication times, upload intervals and provider limits still apply; immediate collection cannot manufacture missing source data.

## If setup does not work

Provide Eniris with the connection name, account/site scope, time of the attempt and the exact error. Check source availability and access permissions before retrying. Share a source screenshot or sample without passwords or tokens.

## Access and costs

Costs are not established for this connector. Confirm provider access, export licences and any project charges with Eniris before activation.

[All connection setup guides](/en/Monitoring/Integrations/connections)


# Meteo Swiss portal connection setup


import ClickableImage from '@site/src/components/ClickableImage';

# Meteo Swiss portal connection setup

Collect Meteo Swiss portal connection weather data for the scope supported by the deployed connector. Agree the stations, variables and geographic coverage before activation.

<ClickableImage src="/img/eniris/monitoring/connection-guides/weather-data.webp" alt="A location, weather variables, time zone and forecast series feeding an energy monitoring dashboard" maxWidth="1100px" />

*Select the correct location, variables, units and time zone before comparing the collected series with the weather source.*

Connection type: **Weather data**.

## What to provide

Provide your company and contact person, the intended Insights account, the source identifiers and explicit permission for the requested scope. Include a recent source example for verification.

This connector exposes no standard customer input fields. Eniris must check the configured source, supported scope and any deployment-specific access before activation. An empty form does not mean every source or device is supported.

## Set up the connection

1. Agree stations or coordinates, required weather variables, units, forecast versus observations and source timestamps.
2. Eniris checks the configured source and coverage. No customer password is requested by this connector’s current form; that does not guarantee unrestricted source access.
3. Enter the exposed scope and mapping settings, if any. Eniris verifies fixed source coverage where the form offers no selector.
4. Compare the first collected period with the original source, including timestamps, time zone, units and missing intervals.

## Check the result

Check that the first collection completed, then open the intended Insights account and verify the relevant measurements or metadata. Compare source IDs, timestamps and units with the original source. Check the next scheduled execution as well. An active schedule or a healthy job alone does not prove that every requested measurement was received.

For ordinary onboarding meters, creation requests an immediate first run and keeps recurring collection active. Source publication times, upload intervals and provider limits still apply; immediate collection cannot manufacture missing source data.

## If setup does not work

Provide Eniris with the connection name, account/site scope, time of the attempt and the exact error. Check source availability and access permissions before retrying. Share a source screenshot or sample without passwords or tokens.

## Access and costs

Onboarding classifies this portal connection as free. This label does not establish the terms of a separate provider subscription or equipment licence.

[All connection setup guides](/en/Monitoring/Integrations/connections)


# Meterbeheer API setup


import ClickableImage from '@site/src/components/ClickableImage';

# Meterbeheer API setup

Read Meterbeheer data using the provider access configured for this connector. Confirm account permissions, installation scope and the requested measurements before activation.

<ClickableImage src="/img/eniris/monitoring/connection-guides/api-authorization.webp" alt="A privacy-safe API setup flow with authorization, limited installation scope, validation and a monitoring dashboard" maxWidth="1100px" />

*A reliable API connection combines the correct authorization method, an explicitly limited installation scope and a verified first retrieval.*

Connection type: **API and platform connection**.

## What to provide

Provide your company and contact person, the intended Insights account, the source identifiers and explicit permission for the requested scope. Include a recent source example for verification.

| Information / setting | What is needed | Supplied or configured by |
| --- | --- | --- |
| API key (API_KEY) | Obtain the key from the source account owner or provider; confirm its data permissions and share it securely. | Customer / installer |

## Set up the connection

1. Ask the provider or account owner to enable the data access required by this connector. Confirm the permitted sites/devices and requested API version.
2. Supply the exact credential types in the table through the agreed secure channel. A portal password, API token, application secret and OAuth grant are not interchangeable.
3. Choose this connector and the target Insights account in onboarding. Enter the required fields and the authorised installation scope, then review before creating.
4. Check the first retrieval against the source account. If access succeeds but no data appears, verify site permissions, API entitlements, identifiers and the availability of measurements.

## Check the result

Check that the first collection completed, then open the intended Insights account and verify the relevant measurements or metadata. Compare source IDs, timestamps and units with the original source. Check the next scheduled execution as well. An active schedule or a healthy job alone does not prove that every requested measurement was received.

For ordinary onboarding meters, creation requests an immediate first run and keeps recurring collection active. Source publication times, upload intervals and provider limits still apply; immediate collection cannot manufacture missing source data.

## If setup does not work

Provide Eniris with the connection name, account/site scope, time of the attempt and the exact error. Check source availability and access permissions before retrying. Share a source screenshot or sample without passwords or tokens.

## Access and costs

Costs are not established for this connector. Confirm provider access, export licences and any project charges with Eniris before activation.

[All connection setup guides](/en/Monitoring/Integrations/connections)


# Moxa CSV setup


import ClickableImage from '@site/src/components/ClickableImage';

# Moxa CSV setup

Import the supported Moxa CSV file format. The source must deliver files in the format expected by this connector; renaming another file to CSV does not convert it.

<ClickableImage src="/img/eniris/monitoring/connection-guides/file-import.webp" alt="A data logger creating a structured file, transferring it securely and mapping its fields to a dashboard" maxWidth="1100px" />

*File onboarding is complete only after the source export, secure delivery, field mapping and recurring arrival have all been checked.*

Connection type: **File import**.

## What to provide

Provide your company and contact person, the intended Insights account, the source identifiers and explicit permission for the requested scope. Include a recent source example for verification.

| Information / setting | What is needed | Supplied or configured by |
| --- | --- | --- |
| File / folder location (CSV_FOLDER) | Agree the delivery folder and file layout. Eniris makes it accessible to the collection service; a path on the customer laptop is insufficient. | Eniris with installer |

## Set up the connection

1. Identify the source logger or export system and supply an original sample file. Confirm model, firmware, format and time zone with Eniris.
2. Agree the delivery route. For an Eniris FTP destination, request dedicated server, protocol, port, username, password and folder settings from Eniris. Use the agreed protocol exactly.
3. The installer or source owner enables recurring delivery. Eniris configures the accessible source location and device/field mappings; creating a meter does not configure the remote source.
4. Send a test file and record its timestamp. Eniris verifies arrival before starting collection, then compares the processed measurements with the original file.

### Configure the datalogger

The installer configures export on the datalogger using FTP credentials supplied by Eniris. Follow the [Datalogger CSV and FTP setup](https://docs.eniris.com/en/Monitoring/Integrations/datalogger-ftp) for preparation, model-specific options where documented, and the test upload. Eniris must confirm the exact model and export format for this connector.

## Check the result

Check that the first collection completed, then open the intended Insights account and verify the relevant measurements or metadata. Compare source IDs, timestamps and units with the original source. Check the next scheduled execution as well. An active schedule or a healthy job alone does not prove that every requested measurement was received.

For ordinary onboarding meters, creation requests an immediate first run and keeps recurring collection active. Source publication times, upload intervals and provider limits still apply; immediate collection cannot manufacture missing source data.

## If setup does not work

If no file arrives, inspect the logger/export status, destination, authentication, network route and folder. If files arrive but no measurements appear, provide the filename, format, source identifiers and timestamp so Eniris can check parsing and mapping.

## Access and costs

Costs are not established for this connector. Confirm provider access, export licences and any project charges with Eniris before activation.

[All connection setup guides](/en/Monitoring/Integrations/connections)


# Nea API setup


import ClickableImage from '@site/src/components/ClickableImage';

# Nea API setup

Read supported compressed CSV data found beneath the configured NEA base URL and map it to solar installations and inverters.

<ClickableImage src="/img/eniris/monitoring/connection-guides/api-authorization.webp" alt="A privacy-safe API setup flow with authorization, limited installation scope, validation and a monitoring dashboard" maxWidth="1100px" />

*A reliable API connection combines the correct authorization method, an explicitly limited installation scope and a verified first retrieval.*

Connection type: **API and platform connection**.

## What to provide

Provide your company and contact person, the intended Insights account, the source identifiers and explicit permission for the requested scope. Include a recent source example for verification.

| Information / setting | What is needed | Supplied or configured by |
| --- | --- | --- |
| Source endpoint (BASE_URL) | Exact endpoint for this customer or deployment; confirm it is reachable by the collection service. | Customer / installer |

## Set up the connection

1. Ask the provider or account owner to enable the data access required by this connector. Confirm the permitted sites/devices and requested API version.
2. Supply the exact credential types in the table through the agreed secure channel. A portal password, API token, application secret and OAuth grant are not interchangeable.
3. Choose this connector and the target Insights account in onboarding. Enter the required fields and the authorised installation scope, then review before creating.
4. Check the first retrieval against the source account. If access succeeds but no data appears, verify site permissions, API entitlements, identifiers and the availability of measurements.

## Check the result

Check that the first collection completed, then open the intended Insights account and verify the relevant measurements or metadata. Compare source IDs, timestamps and units with the original source. Check the next scheduled execution as well. An active schedule or a healthy job alone does not prove that every requested measurement was received.

For ordinary onboarding meters, creation requests an immediate first run and keeps recurring collection active. Source publication times, upload intervals and provider limits still apply; immediate collection cannot manufacture missing source data.

## If setup does not work

Provide Eniris with the connection name, account/site scope, time of the attempt and the exact error. Check source availability and access permissions before retrying. Share a source screenshot or sample without passwords or tokens.

## Access and costs

Costs are not established for this connector. Confirm provider access, export licences and any project charges with Eniris before activation.

[All connection setup guides](/en/Monitoring/Integrations/connections)


# Net Eco portal connection setup


import ClickableImage from '@site/src/components/ClickableImage';

# Net Eco portal connection setup

Read installation data from a supported NetEco portal, using its base URL and authorised account.

<ClickableImage src="/img/eniris/monitoring/connection-guides/portal-access.webp" alt="A privacy-safe portal setup flow with sign-in, multi-factor authentication, installation selection and monitoring" maxWidth="1100px" />

*Confirm portal access, select only the agreed installations and complete any approval or multi-factor step before validating the data.*

Connection type: **Portal connection**.

## Before you start

Provide the correct portal URL and keep certificate validation enabled. If the certificate is invalid, ask the portal operator to fix it before commissioning.

## What to provide

Provide your company and contact person, the intended Insights account, the source identifiers and explicit permission for the requested scope. Include a recent source example for verification.

| Information / setting | What is needed | Supplied or configured by |
| --- | --- | --- |
| Source endpoint (BASE_URL) | Exact endpoint for this customer or deployment; confirm it is reachable by the collection service. | Customer / installer |
| Account username (USERNAME) | Account name with access to the requested data. | Customer / installer |
| Account password (PASSWORD) | Share the source-account password through the secure channel agreed with Eniris. | Customer / installer |
| Time zone (TIMEZONE) | Time zone of the source timestamps, for example Europe/Brussels; identify any files already using UTC. | Customer / installer |
| Installation scope (INSTALLATION_ID_ALLOW_LIST) | Exact installation IDs or numbers to include. Agree explicitly before including every installation. | Customer / installer |
| Exclusions (INSTALLATION_ID_DENY_LIST) | IDs that must not be processed; Eniris checks the identifier type used by this connector. | Customer / installer |
| Certificate validation (SSL) | Keep source certificate verification enabled. Resolve invalid certificates with the source operator. | Eniris with source owner |

## Set up the connection

1. The customer signs in to the correct provider portal and checks that the requested installations and recent measurements are visible.
2. Grant the agreed account access and supply the required account details securely. Identify any login approval or multi-factor step so Eniris can complete the authorised connection.
3. Select this connector in onboarding, choose the intended Insights account and enter the fields in the table. Restrict installation scope to the agreed list where supported.
4. Create the connection and inspect the first retrieval. A successful manual portal login does not itself prove that the collection service can read data.

## Check the result

Check that the first collection completed, then open the intended Insights account and verify the relevant measurements or metadata. Compare source IDs, timestamps and units with the original source. Check the next scheduled execution as well. An active schedule or a healthy job alone does not prove that every requested measurement was received.

For ordinary onboarding meters, creation requests an immediate first run and keeps recurring collection active. Source publication times, upload intervals and provider limits still apply; immediate collection cannot manufacture missing source data.

## If setup does not work

Provide Eniris with the connection name, account/site scope, time of the attempt and the exact error. Check source availability and access permissions before retrying. Share a source screenshot or sample without passwords or tokens.

## Access and costs

Onboarding classifies this portal connection as free. This label does not establish the terms of a separate provider subscription or equipment licence.

[All connection setup guides](/en/Monitoring/Integrations/connections)


# Nibe API setup


import ClickableImage from '@site/src/components/ClickableImage';

# Nibe API setup

Read Nibe data using the provider access configured for this connector. Confirm account permissions, installation scope and the requested measurements before activation.

<ClickableImage src="/img/eniris/monitoring/connection-guides/api-authorization.webp" alt="A privacy-safe API setup flow with authorization, limited installation scope, validation and a monitoring dashboard" maxWidth="1100px" />

*A reliable API connection combines the correct authorization method, an explicitly limited installation scope and a verified first retrieval.*

Connection type: **API and platform connection**.

## Before you start

The deployed connector expects a client ID, client secret and a derived basic authorisation value. Eniris checks the supported NIBE platform/API version and prepares the derived value; do not send a personal password instead.

## What to provide

Provide your company and contact person, the intended Insights account, the source identifiers and explicit permission for the requested scope. Include a recent source example for verification.

| Information / setting | What is needed | Supplied or configured by |
| --- | --- | --- |
| Application / key ID (CLIENT_ID) | Identifier belonging to the supplied secret and provider account. | Customer / installer |
| API/application secret (CLIENT_SECRET) | Secret paired with the corresponding client, application or API key ID; share securely. | Customer / installer |
| Derived authorisation value (BASIC_AUTHCODE) | Prepared from the approved application credentials. | Eniris |

## Set up the connection

1. Ask the provider or account owner to enable the data access required by this connector. Confirm the permitted sites/devices and requested API version.
2. Supply the exact credential types in the table through the agreed secure channel. A portal password, API token, application secret and OAuth grant are not interchangeable.
3. Choose this connector and the target Insights account in onboarding. Enter the required fields and the authorised installation scope, then review before creating.
4. Check the first retrieval against the source account. If access succeeds but no data appears, verify site permissions, API entitlements, identifiers and the availability of measurements.

## Check the result

Check that the first collection completed, then open the intended Insights account and verify the relevant measurements or metadata. Compare source IDs, timestamps and units with the original source. Check the next scheduled execution as well. An active schedule or a healthy job alone does not prove that every requested measurement was received.

For ordinary onboarding meters, creation requests an immediate first run and keeps recurring collection active. Source publication times, upload intervals and provider limits still apply; immediate collection cannot manufacture missing source data.

## If setup does not work

Provide Eniris with the connection name, account/site scope, time of the attempt and the exact error. Check source availability and access permissions before retrying. Share a source screenshot or sample without passwords or tokens.

## Access and costs

Costs are not established for this connector. Confirm provider access, export licences and any project charges with Eniris before activation.

[All connection setup guides](/en/Monitoring/Integrations/connections)


# Nmbs Data setup


import ClickableImage from '@site/src/components/ClickableImage';

# Nmbs Data setup

Collect the NMBS data implemented by this specialised connector. Agree the required dataset and output with Eniris before commissioning; this is not a physical energy meter.

<ClickableImage src="/img/eniris/monitoring/connection-guides/api-authorization.webp" alt="A privacy-safe API setup flow with authorization, limited installation scope, validation and a monitoring dashboard" maxWidth="1100px" />

*A reliable API connection combines the correct authorization method, an explicitly limited installation scope and a verified first retrieval.*

Connection type: **API and platform connection**.

## What to provide

Provide your company and contact person, the intended Insights account, the source identifiers and explicit permission for the requested scope. Include a recent source example for verification.

This connector exposes no standard customer input fields. Eniris must check the configured source, supported scope and any deployment-specific access before activation. An empty form does not mean every source or device is supported.

## Set up the connection

1. Contact Eniris with the intended source, required output and time range. This specialised connector requires an operator review before use.
2. Eniris checks the configured source, access and scope in the deployed implementation. The standard onboarding form cannot configure all of these details.
3. The operator agrees a limited first run and verifies its output against the original source before enabling further processing.

## Check the result

Check that the first collection completed, then open the intended Insights account and verify the relevant measurements or metadata. Compare source IDs, timestamps and units with the original source. Check the next scheduled execution as well. An active schedule or a healthy job alone does not prove that every requested measurement was received.

For ordinary onboarding meters, creation requests an immediate first run and keeps recurring collection active. Source publication times, upload intervals and provider limits still apply; immediate collection cannot manufacture missing source data.

## If setup does not work

Provide Eniris with the connection name, account/site scope, time of the attempt and the exact error. Check source availability and access permissions before retrying. Share a source screenshot or sample without passwords or tokens.

## Access and costs

Costs are not established for this connector. Confirm provider access, export licences and any project charges with Eniris before activation.

[All connection setup guides](/en/Monitoring/Integrations/connections)


# Nord Pool portal connection setup


import ClickableImage from '@site/src/components/ClickableImage';

# Nord Pool portal connection setup

Collect Nord Pool portal connection market or grid-reference data. Agree the market area, product, units, currency and publication period before using the values in reports.

<ClickableImage src="/img/eniris/monitoring/connection-guides/market-grid-data.webp" alt="A market area, date range, resolution and units feeding electricity price and grid charts" maxWidth="1100px" />

*Market and grid data must be scoped by area, product, time range, resolution, currency and units before the first comparison.*

Connection type: **Prices and grid data**.

## What to provide

Provide your company and contact person, the intended Insights account, the source identifiers and explicit permission for the requested scope. Include a recent source example for verification.

| Information / setting | What is needed | Supplied or configured by |
| --- | --- | --- |
| Country / market areas (AREA_CODE_LIST) | Countries or bidding-zone identifiers for the requested dataset. | Customer / installer |
| Area / operator mapping (CUSTOM_MAPPING) | Match source operator or market-area identifiers to the required output labels. | Eniris with customer |

## Set up the connection

1. Agree market areas, price product or grid dataset, resolution, currency, units and publication date. Distinguish prices from physical meter readings.
2. Eniris checks the configured source and coverage. No customer password is requested by this connector’s current form; that does not guarantee unrestricted source access.
3. Enter the exposed scope and mapping settings, if any. Eniris verifies fixed source coverage where the form offers no selector.
4. Compare the first collected period with the original source, including timestamps, time zone, units and missing intervals.

## Check the result

Check that the first collection completed, then open the intended Insights account and verify the relevant measurements or metadata. Compare source IDs, timestamps and units with the original source. Check the next scheduled execution as well. An active schedule or a healthy job alone does not prove that every requested measurement was received.

For ordinary onboarding meters, creation requests an immediate first run and keeps recurring collection active. Source publication times, upload intervals and provider limits still apply; immediate collection cannot manufacture missing source data.

## If setup does not work

Provide Eniris with the connection name, account/site scope, time of the attempt and the exact error. Check source availability and access permissions before retrying. Share a source screenshot or sample without passwords or tokens.

## Access and costs

Onboarding classifies this portal connection as free. This label does not establish the terms of a separate provider subscription or equipment licence.

[All connection setup guides](/en/Monitoring/Integrations/connections)


# Okte API setup


import ClickableImage from '@site/src/components/ClickableImage';

# Okte API setup

Collect Okte market or grid-reference data. Agree the market area, product, units, currency and publication period before using the values in reports.

<ClickableImage src="/img/eniris/monitoring/connection-guides/market-grid-data.webp" alt="A market area, date range, resolution and units feeding electricity price and grid charts" maxWidth="1100px" />

*Market and grid data must be scoped by area, product, time range, resolution, currency and units before the first comparison.*

Connection type: **Prices and grid data**.

## What to provide

Provide your company and contact person, the intended Insights account, the source identifiers and explicit permission for the requested scope. Include a recent source example for verification.

This connector exposes no standard customer input fields. Eniris must check the configured source, supported scope and any deployment-specific access before activation. An empty form does not mean every source or device is supported.

## Set up the connection

1. Agree market areas, price product or grid dataset, resolution, currency, units and publication date. Distinguish prices from physical meter readings.
2. Eniris checks the configured source and coverage. No customer password is requested by this connector’s current form; that does not guarantee unrestricted source access.
3. Enter the exposed scope and mapping settings, if any. Eniris verifies fixed source coverage where the form offers no selector.
4. Compare the first collected period with the original source, including timestamps, time zone, units and missing intervals.

## Check the result

Check that the first collection completed, then open the intended Insights account and verify the relevant measurements or metadata. Compare source IDs, timestamps and units with the original source. Check the next scheduled execution as well. An active schedule or a healthy job alone does not prove that every requested measurement was received.

For ordinary onboarding meters, creation requests an immediate first run and keeps recurring collection active. Source publication times, upload intervals and provider limits still apply; immediate collection cannot manufacture missing source data.

## If setup does not work

Provide Eniris with the connection name, account/site scope, time of the attempt and the exact error. Check source availability and access permissions before retrying. Share a source screenshot or sample without passwords or tokens.

## Access and costs

Costs are not established for this connector. Confirm provider access, export licences and any project charges with Eniris before activation.

[All connection setup guides](/en/Monitoring/Integrations/connections)


# Open Meteo API setup


import ClickableImage from '@site/src/components/ClickableImage';

# Open Meteo API setup

Collect Open Meteo weather data for the scope supported by the deployed connector. Agree the stations, variables and geographic coverage before activation.

<ClickableImage src="/img/eniris/monitoring/connection-guides/weather-data.webp" alt="A location, weather variables, time zone and forecast series feeding an energy monitoring dashboard" maxWidth="1100px" />

*Select the correct location, variables, units and time zone before comparing the collected series with the weather source.*

Connection type: **Weather data**.

## What to provide

Provide your company and contact person, the intended Insights account, the source identifiers and explicit permission for the requested scope. Include a recent source example for verification.

| Information / setting | What is needed | Supplied or configured by |
| --- | --- | --- |
| Weather-station metadata (METEOSTATION_METADATA_URL) | Accessible metadata file describing the stations and their coordinates. | Eniris with customer |

## Set up the connection

1. Agree stations or coordinates, required weather variables, units, forecast versus observations and source timestamps.
2. Eniris checks the configured source and coverage. No customer password is requested by this connector’s current form; that does not guarantee unrestricted source access.
3. Enter the exposed scope and mapping settings, if any. Eniris verifies fixed source coverage where the form offers no selector.
4. Compare the first collected period with the original source, including timestamps, time zone, units and missing intervals.

## Check the result

Check that the first collection completed, then open the intended Insights account and verify the relevant measurements or metadata. Compare source IDs, timestamps and units with the original source. Check the next scheduled execution as well. An active schedule or a healthy job alone does not prove that every requested measurement was received.

For ordinary onboarding meters, creation requests an immediate first run and keeps recurring collection active. Source publication times, upload intervals and provider limits still apply; immediate collection cannot manufacture missing source data.

## If setup does not work

Provide Eniris with the connection name, account/site scope, time of the attempt and the exact error. Check source availability and access permissions before retrying. Share a source screenshot or sample without passwords or tokens.

## Access and costs

Costs are not established for this connector. Confirm provider access, export licences and any project charges with Eniris before activation.

[All connection setup guides](/en/Monitoring/Integrations/connections)


# Open Weather Map API setup


import ClickableImage from '@site/src/components/ClickableImage';

# Open Weather Map API setup

Collect Open Weather Map weather data for the scope supported by the deployed connector. Agree the stations, variables and geographic coverage before activation.

<ClickableImage src="/img/eniris/monitoring/connection-guides/weather-data.webp" alt="A location, weather variables, time zone and forecast series feeding an energy monitoring dashboard" maxWidth="1100px" />

*Select the correct location, variables, units and time zone before comparing the collected series with the weather source.*

Connection type: **Weather data**.

## What to provide

Provide your company and contact person, the intended Insights account, the source identifiers and explicit permission for the requested scope. Include a recent source example for verification.

| Information / setting | What is needed | Supplied or configured by |
| --- | --- | --- |
| Access token (TOKEN) | Provider-issued token with access to the required data; share securely and record who maintains it. | Customer / installer |
| Locations (LOCATIONS) | Location names with latitude and longitude. | Customer / installer |

## Set up the connection

1. Agree stations or coordinates, required weather variables, units, forecast versus observations and source timestamps.
2. Obtain the required provider access shown in the table and confirm the permitted dataset. Supply secrets securely.
3. Enter the exposed scope and mapping settings, if any. Eniris verifies fixed source coverage where the form offers no selector.
4. Compare the first collected period with the original source, including timestamps, time zone, units and missing intervals.

## Check the result

Check that the first collection completed, then open the intended Insights account and verify the relevant measurements or metadata. Compare source IDs, timestamps and units with the original source. Check the next scheduled execution as well. An active schedule or a healthy job alone does not prove that every requested measurement was received.

For ordinary onboarding meters, creation requests an immediate first run and keeps recurring collection active. Source publication times, upload intervals and provider limits still apply; immediate collection cannot manufacture missing source data.

## If setup does not work

Provide Eniris with the connection name, account/site scope, time of the attempt and the exact error. Check source availability and access permissions before retrying. Share a source screenshot or sample without passwords or tokens.

## Access and costs

Costs are not established for this connector. Confirm provider access, export licences and any project charges with Eniris before activation.

[All connection setup guides](/en/Monitoring/Integrations/connections)


# Opinum API setup


import ClickableImage from '@site/src/components/ClickableImage';

# Opinum API setup

Read Opinum data using the provider access configured for this connector. Confirm account permissions, installation scope and the requested measurements before activation.

<ClickableImage src="/img/eniris/monitoring/connection-guides/api-authorization.webp" alt="A privacy-safe API setup flow with authorization, limited installation scope, validation and a monitoring dashboard" maxWidth="1100px" />

*A reliable API connection combines the correct authorization method, an explicitly limited installation scope and a verified first retrieval.*

Connection type: **API and platform connection**.

## What to provide

Provide your company and contact person, the intended Insights account, the source identifiers and explicit permission for the requested scope. Include a recent source example for verification.

| Information / setting | What is needed | Supplied or configured by |
| --- | --- | --- |
| Application / key ID (CLIENT_ID) | Identifier belonging to the supplied secret and provider account. | Customer / installer |
| API/application secret (SECRET) | Secret paired with the corresponding client, application or API key ID; share securely. | Customer / installer |
| Account username (USERNAME) | Account name with access to the requested data. | Customer / installer |
| Account password (PASSWORD) | Share the source-account password through the secure channel agreed with Eniris. | Customer / installer |

## Set up the connection

1. Ask the provider or account owner to enable the data access required by this connector. Confirm the permitted sites/devices and requested API version.
2. Supply the exact credential types in the table through the agreed secure channel. A portal password, API token, application secret and OAuth grant are not interchangeable.
3. Choose this connector and the target Insights account in onboarding. Enter the required fields and the authorised installation scope, then review before creating.
4. Check the first retrieval against the source account. If access succeeds but no data appears, verify site permissions, API entitlements, identifiers and the availability of measurements.

## Check the result

Check that the first collection completed, then open the intended Insights account and verify the relevant measurements or metadata. Compare source IDs, timestamps and units with the original source. Check the next scheduled execution as well. An active schedule or a healthy job alone does not prove that every requested measurement was received.

For ordinary onboarding meters, creation requests an immediate first run and keeps recurring collection active. Source publication times, upload intervals and provider limits still apply; immediate collection cannot manufacture missing source data.

## If setup does not work

Provide Eniris with the connection name, account/site scope, time of the attempt and the exact error. Check source availability and access permissions before retrying. Share a source screenshot or sample without passwords or tokens.

## Access and costs

Costs are not established for this connector. Confirm provider access, export licences and any project charges with Eniris before activation.

[All connection setup guides](/en/Monitoring/Integrations/connections)


# Oree Xlsx setup


import ClickableImage from '@site/src/components/ClickableImage';

# Oree Xlsx setup

Read OREE day-ahead prices from the spreadsheet source used by this connector.

<ClickableImage src="/img/eniris/monitoring/connection-guides/market-grid-data.webp" alt="A market area, date range, resolution and units feeding electricity price and grid charts" maxWidth="1100px" />

*Market and grid data must be scoped by area, product, time range, resolution, currency and units before the first comparison.*

Connection type: **Prices and grid data**.

## What to provide

Provide your company and contact person, the intended Insights account, the source identifiers and explicit permission for the requested scope. Include a recent source example for verification.

This connector exposes no standard customer input fields. Eniris must check the configured source, supported scope and any deployment-specific access before activation. An empty form does not mean every source or device is supported.

## Set up the connection

1. Agree market areas, price product or grid dataset, resolution, currency, units and publication date. Distinguish prices from physical meter readings.
2. Eniris checks the configured source and coverage. No customer password is requested by this connector’s current form; that does not guarantee unrestricted source access.
3. Enter the exposed scope and mapping settings, if any. Eniris verifies fixed source coverage where the form offers no selector.
4. Compare the first collected period with the original source, including timestamps, time zone, units and missing intervals.

## Check the result

Check that the first collection completed, then open the intended Insights account and verify the relevant measurements or metadata. Compare source IDs, timestamps and units with the original source. Check the next scheduled execution as well. An active schedule or a healthy job alone does not prove that every requested measurement was received.

For ordinary onboarding meters, creation requests an immediate first run and keeps recurring collection active. Source publication times, upload intervals and provider limits still apply; immediate collection cannot manufacture missing source data.

## If setup does not work

Provide Eniris with the connection name, account/site scope, time of the attempt and the exact error. Check source availability and access permissions before retrying. Share a source screenshot or sample without passwords or tokens.

## Access and costs

Costs are not established for this connector. Confirm provider access, export licences and any project charges with Eniris before activation.

[All connection setup guides](/en/Monitoring/Integrations/connections)


# Panasonic portal connection setup


import ClickableImage from '@site/src/components/ClickableImage';

# Panasonic portal connection setup

Read measurements available through the authorised Panasonic portal connection monitoring account. Only installations visible to that account can be collected.

<ClickableImage src="/img/eniris/monitoring/connection-guides/portal-access.webp" alt="A privacy-safe portal setup flow with sign-in, multi-factor authentication, installation selection and monitoring" maxWidth="1100px" />

*Confirm portal access, select only the agreed installations and complete any approval or multi-factor step before validating the data.*

Connection type: **Portal connection**.

## What to provide

Provide your company and contact person, the intended Insights account, the source identifiers and explicit permission for the requested scope. Include a recent source example for verification.

| Information / setting | What is needed | Supplied or configured by |
| --- | --- | --- |
| Account username (username) | Account name with access to the requested data. | Customer / installer |
| Account password (password) | Share the source-account password through the secure channel agreed with Eniris. | Customer / installer |

## Set up the connection

1. The customer signs in to the correct provider portal and checks that the requested installations and recent measurements are visible.
2. Grant the agreed account access and supply the required account details securely. Identify any login approval or multi-factor step so Eniris can complete the authorised connection.
3. Select this connector in onboarding, choose the intended Insights account and enter the fields in the table. Restrict installation scope to the agreed list where supported.
4. Create the connection and inspect the first retrieval. A successful manual portal login does not itself prove that the collection service can read data.

## Check the result

Check that the first collection completed, then open the intended Insights account and verify the relevant measurements or metadata. Compare source IDs, timestamps and units with the original source. Check the next scheduled execution as well. An active schedule or a healthy job alone does not prove that every requested measurement was received.

For ordinary onboarding meters, creation requests an immediate first run and keeps recurring collection active. Source publication times, upload intervals and provider limits still apply; immediate collection cannot manufacture missing source data.

## If setup does not work

Provide Eniris with the connection name, account/site scope, time of the attempt and the exact error. Check source availability and access permissions before retrying. Share a source screenshot or sample without passwords or tokens.

## Access and costs

Onboarding classifies this portal connection as free. This label does not establish the terms of a separate provider subscription or equipment licence.

[All connection setup guides](/en/Monitoring/Integrations/connections)


# Power Router portal connection setup


import ClickableImage from '@site/src/components/ClickableImage';

# Power Router portal connection setup

Read measurements available through the authorised Power Router portal connection monitoring account. Only installations visible to that account can be collected.

<ClickableImage src="/img/eniris/monitoring/connection-guides/portal-access.webp" alt="A privacy-safe portal setup flow with sign-in, multi-factor authentication, installation selection and monitoring" maxWidth="1100px" />

*Confirm portal access, select only the agreed installations and complete any approval or multi-factor step before validating the data.*

Connection type: **Portal connection**.

## What to provide

Provide your company and contact person, the intended Insights account, the source identifiers and explicit permission for the requested scope. Include a recent source example for verification.

| Information / setting | What is needed | Supplied or configured by |
| --- | --- | --- |
| Account username (USERNAME) | Account name with access to the requested data. | Customer / installer |
| Account password (PASSWORD) | Share the source-account password through the secure channel agreed with Eniris. | Customer / installer |

## Set up the connection

1. The customer signs in to the correct provider portal and checks that the requested installations and recent measurements are visible.
2. Grant the agreed account access and supply the required account details securely. Identify any login approval or multi-factor step so Eniris can complete the authorised connection.
3. Select this connector in onboarding, choose the intended Insights account and enter the fields in the table. Restrict installation scope to the agreed list where supported.
4. Create the connection and inspect the first retrieval. A successful manual portal login does not itself prove that the collection service can read data.

## Check the result

Check that the first collection completed, then open the intended Insights account and verify the relevant measurements or metadata. Compare source IDs, timestamps and units with the original source. Check the next scheduled execution as well. An active schedule or a healthy job alone does not prove that every requested measurement was received.

For ordinary onboarding meters, creation requests an immediate first run and keeps recurring collection active. Source publication times, upload intervals and provider limits still apply; immediate collection cannot manufacture missing source data.

## If setup does not work

Provide Eniris with the connection name, account/site scope, time of the attempt and the exact error. Check source availability and access permissions before retrying. Share a source screenshot or sample without passwords or tokens.

## Access and costs

Onboarding classifies this portal connection as free. This label does not establish the terms of a separate provider subscription or equipment licence.

[All connection setup guides](/en/Monitoring/Integrations/connections)


# Profi Nrg CSV setup


import ClickableImage from '@site/src/components/ClickableImage';

# Profi Nrg CSV setup

Import the supported Profi Nrg CSV file format. The source must deliver files in the format expected by this connector; renaming another file to CSV does not convert it.

<ClickableImage src="/img/eniris/monitoring/connection-guides/file-import.webp" alt="A data logger creating a structured file, transferring it securely and mapping its fields to a dashboard" maxWidth="1100px" />

*File onboarding is complete only after the source export, secure delivery, field mapping and recurring arrival have all been checked.*

Connection type: **File import**.

## What to provide

Provide your company and contact person, the intended Insights account, the source identifiers and explicit permission for the requested scope. Include a recent source example for verification.

| Information / setting | What is needed | Supplied or configured by |
| --- | --- | --- |
| File / folder location (CSV_FOLDER) | Agree the delivery folder and file layout. Eniris makes it accessible to the collection service; a path on the customer laptop is insufficient. | Eniris with installer |
| Time zone (TIMEZONE) | Time zone of the source timestamps, for example Europe/Brussels; identify any files already using UTC. | Customer / installer |

## Set up the connection

1. Identify the source logger or export system and supply an original sample file. Confirm model, firmware, format and time zone with Eniris.
2. Agree the delivery route. For an Eniris FTP destination, request dedicated server, protocol, port, username, password and folder settings from Eniris. Use the agreed protocol exactly.
3. The installer or source owner enables recurring delivery. Eniris configures the accessible source location and device/field mappings; creating a meter does not configure the remote source.
4. Send a test file and record its timestamp. Eniris verifies arrival before starting collection, then compares the processed measurements with the original file.

### Configure the datalogger

The installer configures export on the datalogger using FTP credentials supplied by Eniris. Follow the [Datalogger CSV and FTP setup](https://docs.eniris.com/en/Monitoring/Integrations/datalogger-ftp) for preparation, model-specific options where documented, and the test upload. Eniris must confirm the exact model and export format for this connector.

## Check the result

Check that the first collection completed, then open the intended Insights account and verify the relevant measurements or metadata. Compare source IDs, timestamps and units with the original source. Check the next scheduled execution as well. An active schedule or a healthy job alone does not prove that every requested measurement was received.

For ordinary onboarding meters, creation requests an immediate first run and keeps recurring collection active. Source publication times, upload intervals and provider limits still apply; immediate collection cannot manufacture missing source data.

## If setup does not work

If no file arrives, inspect the logger/export status, destination, authentication, network route and folder. If files arrive but no measurements appear, provide the filename, format, source identifiers and timestamp so Eniris can check parsing and mapping.

## Access and costs

Costs are not established for this connector. Confirm provider access, export licences and any project charges with Eniris before activation.

[All connection setup guides](/en/Monitoring/Integrations/connections)


# Qantum Meta Data Sync setup


import ClickableImage from '@site/src/components/ClickableImage';

# Qantum Meta Data Sync setup

Synchronise Qantum-related metadata using the configured Fudura API access. Verify metadata mappings rather than expecting a new power time series.

<ClickableImage src="/img/eniris/monitoring/connection-guides/api-authorization.webp" alt="A privacy-safe API setup flow with authorization, limited installation scope, validation and a monitoring dashboard" maxWidth="1100px" />

*A reliable API connection combines the correct authorization method, an explicitly limited installation scope and a verified first retrieval.*

Connection type: **API and platform connection**.

## What to provide

Provide your company and contact person, the intended Insights account, the source identifiers and explicit permission for the requested scope. Include a recent source example for verification.

| Information / setting | What is needed | Supplied or configured by |
| --- | --- | --- |
| API key (API_KEY) | Obtain the key from the source account owner or provider; confirm its data permissions and share it securely. | Customer / installer |

## Set up the connection

1. Ask the provider or account owner to enable the data access required by this connector. Confirm the permitted sites/devices and requested API version.
2. Supply the exact credential types in the table through the agreed secure channel. A portal password, API token, application secret and OAuth grant are not interchangeable.
3. Choose this connector and the target Insights account in onboarding. Enter the required fields and the authorised installation scope, then review before creating.
4. Check the first retrieval against the source account. If access succeeds but no data appears, verify site permissions, API entitlements, identifiers and the availability of measurements.

## Check the result

Check that the first collection completed, then open the intended Insights account and verify the relevant measurements or metadata. Compare source IDs, timestamps and units with the original source. Check the next scheduled execution as well. An active schedule or a healthy job alone does not prove that every requested measurement was received.

For ordinary onboarding meters, creation requests an immediate first run and keeps recurring collection active. Source publication times, upload intervals and provider limits still apply; immediate collection cannot manufacture missing source data.

## If setup does not work

Provide Eniris with the connection name, account/site scope, time of the attempt and the exact error. Check source availability and access permissions before retrying. Share a source screenshot or sample without passwords or tokens.

## Access and costs

Costs are not established for this connector. Confirm provider access, export licences and any project charges with Eniris before activation.

[All connection setup guides](/en/Monitoring/Integrations/connections)


# Rmi Synoptic portal connection setup


import ClickableImage from '@site/src/components/ClickableImage';

# Rmi Synoptic portal connection setup

Collect Rmi Synoptic portal connection weather data for the scope supported by the deployed connector. Agree the stations, variables and geographic coverage before activation.

<ClickableImage src="/img/eniris/monitoring/connection-guides/weather-data.webp" alt="A location, weather variables, time zone and forecast series feeding an energy monitoring dashboard" maxWidth="1100px" />

*Select the correct location, variables, units and time zone before comparing the collected series with the weather source.*

Connection type: **Weather data**.

## What to provide

Provide your company and contact person, the intended Insights account, the source identifiers and explicit permission for the requested scope. Include a recent source example for verification.

This connector exposes no standard customer input fields. Eniris must check the configured source, supported scope and any deployment-specific access before activation. An empty form does not mean every source or device is supported.

## Set up the connection

1. Agree stations or coordinates, required weather variables, units, forecast versus observations and source timestamps.
2. Eniris checks the configured source and coverage. No customer password is requested by this connector’s current form; that does not guarantee unrestricted source access.
3. Enter the exposed scope and mapping settings, if any. Eniris verifies fixed source coverage where the form offers no selector.
4. Compare the first collected period with the original source, including timestamps, time zone, units and missing intervals.

## Check the result

Check that the first collection completed, then open the intended Insights account and verify the relevant measurements or metadata. Compare source IDs, timestamps and units with the original source. Check the next scheduled execution as well. An active schedule or a healthy job alone does not prove that every requested measurement was received.

For ordinary onboarding meters, creation requests an immediate first run and keeps recurring collection active. Source publication times, upload intervals and provider limits still apply; immediate collection cannot manufacture missing source data.

## If setup does not work

Provide Eniris with the connection name, account/site scope, time of the attempt and the exact error. Check source availability and access permissions before retrying. Share a source screenshot or sample without passwords or tokens.

## Access and costs

Onboarding classifies this portal connection as free. This label does not establish the terms of a separate provider subscription or equipment licence.

[All connection setup guides](/en/Monitoring/Integrations/connections)


# Rocket Chat setup


import ClickableImage from '@site/src/components/ClickableImage';

# Rocket Chat setup

Send a configured message to Rocket.Chat. Running this automation can send a real message; it does not import meter data.

<ClickableImage src="/img/eniris/monitoring/connection-guides/workflow-automation.webp" alt="A scheduled workflow with access control, transformation, validation, execution and an audit trail" maxWidth="1100px" />

*An automation should have a defined trigger, restricted access, validation, observable execution and a usable audit trail.*

Connection type: **Internal automation**.

## What to provide

Name the responsible Eniris operator, the approved scope and the expected outcome. Configuration and service credentials stay with the internal operator.

## Set up the connection

1. Ask the Eniris owner of this automation to agree its purpose, affected records/accounts and expected changes. This entry is not a customer meter connection.
2. The Eniris operator configures the required service access and scopes. Do not request internal administrator credentials from the customer.
3. Review a bounded test scope and its expected outcome before activation. For messaging, permission, merging or CRM workflows, the first run may change records or send messages.
4. Verify the intended action in the destination system and check for unintended changes before allowing the recurring schedule.

## Check the result

Verify the expected records or actions in the target system and the execution status. A meter dashboard may not apply. Review the effects of the first run before continuing a recurring automation.

## If setup does not work

Contact the responsible Eniris operator with the job reference, expected action and observed result. Avoid repeating a write or send action without checking whether it already happened.

[All connection setup guides](/en/Monitoring/Integrations/connections)


# Sales Handy2 Zoho API setup


import ClickableImage from '@site/src/components/ClickableImage';

# Sales Handy2 Zoho API setup

Synchronise configured SalesHandy information into Zoho.

<ClickableImage src="/img/eniris/monitoring/connection-guides/workflow-automation.webp" alt="A scheduled workflow with access control, transformation, validation, execution and an audit trail" maxWidth="1100px" />

*An automation should have a defined trigger, restricted access, validation, observable execution and a usable audit trail.*

Connection type: **Internal automation**.

## What to provide

Name the responsible Eniris operator, the approved scope and the expected outcome. Configuration and service credentials stay with the internal operator.

## Set up the connection

1. Ask the Eniris owner of this automation to agree its purpose, affected records/accounts and expected changes. This entry is not a customer meter connection.
2. The Eniris operator configures the required service access and scopes. Do not request internal administrator credentials from the customer.
3. Review a bounded test scope and its expected outcome before activation. For messaging, permission, merging or CRM workflows, the first run may change records or send messages.
4. Verify the intended action in the destination system and check for unintended changes before allowing the recurring schedule.

## Check the result

Verify the expected records or actions in the target system and the execution status. A meter dashboard may not apply. Review the effects of the first run before continuing a recurring automation.

## If setup does not work

Contact the responsible Eniris operator with the job reference, expected action and observed result. Avoid repeating a write or send action without checking whether it already happened.

[All connection setup guides](/en/Monitoring/Integrations/connections)


# Scipher portal connection setup


import ClickableImage from '@site/src/components/ClickableImage';

# Scipher portal connection setup

Read measurements available through the authorised Scipher portal connection monitoring account. Only installations visible to that account can be collected.

<ClickableImage src="/img/eniris/monitoring/connection-guides/portal-access.webp" alt="A privacy-safe portal setup flow with sign-in, multi-factor authentication, installation selection and monitoring" maxWidth="1100px" />

*Confirm portal access, select only the agreed installations and complete any approval or multi-factor step before validating the data.*

Connection type: **Portal connection**.

## What to provide

Provide your company and contact person, the intended Insights account, the source identifiers and explicit permission for the requested scope. Include a recent source example for verification.

| Information / setting | What is needed | Supplied or configured by |
| --- | --- | --- |
| Account username (username) | Account name with access to the requested data. | Customer / installer |
| Account password (password) | Share the source-account password through the secure channel agreed with Eniris. | Customer / installer |

## Set up the connection

1. The customer signs in to the correct provider portal and checks that the requested installations and recent measurements are visible.
2. Grant the agreed account access and supply the required account details securely. Identify any login approval or multi-factor step so Eniris can complete the authorised connection.
3. Select this connector in onboarding, choose the intended Insights account and enter the fields in the table. Restrict installation scope to the agreed list where supported.
4. Create the connection and inspect the first retrieval. A successful manual portal login does not itself prove that the collection service can read data.

## Check the result

Check that the first collection completed, then open the intended Insights account and verify the relevant measurements or metadata. Compare source IDs, timestamps and units with the original source. Check the next scheduled execution as well. An active schedule or a healthy job alone does not prove that every requested measurement was received.

For ordinary onboarding meters, creation requests an immediate first run and keeps recurring collection active. Source publication times, upload intervals and provider limits still apply; immediate collection cannot manufacture missing source data.

## If setup does not work

Provide Eniris with the connection name, account/site scope, time of the attempt and the exact error. Check source availability and access permissions before retrying. Share a source screenshot or sample without passwords or tokens.

## Access and costs

Onboarding classifies this portal connection as free. This label does not establish the terms of a separate provider subscription or equipment licence.

[All connection setup guides](/en/Monitoring/Integrations/connections)


# Sems Plus portal connection setup


import ClickableImage from '@site/src/components/ClickableImage';

# Sems Plus portal connection setup

Read measurements available through the authorised Sems Plus portal connection monitoring account. Only installations visible to that account can be collected.

<ClickableImage src="/img/eniris/monitoring/connection-guides/portal-access.webp" alt="A privacy-safe portal setup flow with sign-in, multi-factor authentication, installation selection and monitoring" maxWidth="1100px" />

*Confirm portal access, select only the agreed installations and complete any approval or multi-factor step before validating the data.*

Connection type: **Portal connection**.

## What to provide

Provide your company and contact person, the intended Insights account, the source identifiers and explicit permission for the requested scope. Include a recent source example for verification.

| Information / setting | What is needed | Supplied or configured by |
| --- | --- | --- |
| Account username (USERNAME) | Account name with access to the requested data. | Customer / installer |
| Account password (PASSWORD) | Share the source-account password through the secure channel agreed with Eniris. | Customer / installer |
| Time zone (TIMEZONE) | Time zone of the source timestamps, for example Europe/Brussels; identify any files already using UTC. | Customer / installer |
| Installation scope (INSTALLATION_ID_ALLOW_LIST) | Exact installation IDs or numbers to include. Agree explicitly before including every installation. | Customer / installer |

## Set up the connection

1. The customer signs in to the correct provider portal and checks that the requested installations and recent measurements are visible.
2. Grant the agreed account access and supply the required account details securely. Identify any login approval or multi-factor step so Eniris can complete the authorised connection.
3. Select this connector in onboarding, choose the intended Insights account and enter the fields in the table. Restrict installation scope to the agreed list where supported.
4. Create the connection and inspect the first retrieval. A successful manual portal login does not itself prove that the collection service can read data.

## Check the result

Check that the first collection completed, then open the intended Insights account and verify the relevant measurements or metadata. Compare source IDs, timestamps and units with the original source. Check the next scheduled execution as well. An active schedule or a healthy job alone does not prove that every requested measurement was received.

For ordinary onboarding meters, creation requests an immediate first run and keeps recurring collection active. Source publication times, upload intervals and provider limits still apply; immediate collection cannot manufacture missing source data.

## If setup does not work

Provide Eniris with the connection name, account/site scope, time of the attempt and the exact error. Check source availability and access permissions before retrying. Share a source screenshot or sample without passwords or tokens.

## Access and costs

Onboarding classifies this portal connection as free. This label does not establish the terms of a separate provider subscription or equipment licence.

[All connection setup guides](/en/Monitoring/Integrations/connections)


# Sems portal connection setup


import ClickableImage from '@site/src/components/ClickableImage';

# Sems portal connection setup

Read measurements available through the authorised Sems portal connection monitoring account. Only installations visible to that account can be collected.

<ClickableImage src="/img/eniris/monitoring/connection-guides/portal-access.webp" alt="A privacy-safe portal setup flow with sign-in, multi-factor authentication, installation selection and monitoring" maxWidth="1100px" />

*Confirm portal access, select only the agreed installations and complete any approval or multi-factor step before validating the data.*

Connection type: **Portal connection**.

## What to provide

Provide your company and contact person, the intended Insights account, the source identifiers and explicit permission for the requested scope. Include a recent source example for verification.

| Information / setting | What is needed | Supplied or configured by |
| --- | --- | --- |
| Account username (USERNAME) | Account name with access to the requested data. | Customer / installer |
| Account password (PASSWORD) | Share the source-account password through the secure channel agreed with Eniris. | Customer / installer |
| Time zone (TIMEZONE) | Time zone of the source timestamps, for example Europe/Brussels; identify any files already using UTC. | Customer / installer |
| Installation scope (INSTALLATION_ID_ALLOW_LIST) | Exact installation IDs or numbers to include. Agree explicitly before including every installation. | Customer / installer |

## Set up the connection

1. The customer signs in to the correct provider portal and checks that the requested installations and recent measurements are visible.
2. Grant the agreed account access and supply the required account details securely. Identify any login approval or multi-factor step so Eniris can complete the authorised connection.
3. Select this connector in onboarding, choose the intended Insights account and enter the fields in the table. Restrict installation scope to the agreed list where supported.
4. Create the connection and inspect the first retrieval. A successful manual portal login does not itself prove that the collection service can read data.

## Check the result

Check that the first collection completed, then open the intended Insights account and verify the relevant measurements or metadata. Compare source IDs, timestamps and units with the original source. Check the next scheduled execution as well. An active schedule or a healthy job alone does not prove that every requested measurement was received.

For ordinary onboarding meters, creation requests an immediate first run and keeps recurring collection active. Source publication times, upload intervals and provider limits still apply; immediate collection cannot manufacture missing source data.

## If setup does not work

Provide Eniris with the connection name, account/site scope, time of the attempt and the exact error. Check source availability and access permissions before retrying. Share a source screenshot or sample without passwords or tokens.

## Access and costs

Onboarding classifies this portal connection as free. This label does not establish the terms of a separate provider subscription or equipment licence.

[All connection setup guides](/en/Monitoring/Integrations/connections)


# Siemens S7 1200 setup


import ClickableImage from '@site/src/components/ClickableImage';

# Siemens S7 1200 setup

Read Siemens S7-1200 measurements from a configured HTTP data endpoint. This connector expects a URL, not an arbitrary PLC register list.

<ClickableImage src="/img/eniris/monitoring/connection-guides/local-device.webp" alt="A meter and controller on a private network connected securely through a firewall to a monitoring dashboard" maxWidth="1100px" />

*Keep the device on the private site network and verify the supported endpoint, gateway route and secure outbound connection.*

Connection type: **Local devices**.

## What to provide

Provide your company and contact person, the intended Insights account, the source identifiers and explicit permission for the requested scope. Include a recent source example for verification.

| Information / setting | What is needed | Supplied or configured by |
| --- | --- | --- |
| Source endpoint (API) | Exact endpoint for this customer or deployment; confirm it is reachable by the collection service. | Customer / installer |
| Time zone (TIMEZONE) | Time zone of the source timestamps, for example Europe/Brussels; identify any files already using UTC. | Customer / installer |

## Set up the connection

1. Give Eniris the device model, firmware, identity, network location and the measurements to collect.
2. Have the site installer enable the supported data interface. Eniris verifies the required network route from the collection service; reaching the device on a customer laptop is not sufficient.
3. Enter the endpoint or device identity shown below and agree the time zone and signal mapping. Do not expose the device publicly to work around routing.
4. Start the first collection and compare a recent value and timestamp against the device itself.

## Check the result

Check that the first collection completed, then open the intended Insights account and verify the relevant measurements or metadata. Compare source IDs, timestamps and units with the original source. Check the next scheduled execution as well. An active schedule or a healthy job alone does not prove that every requested measurement was received.

For ordinary onboarding meters, creation requests an immediate first run and keeps recurring collection active. Source publication times, upload intervals and provider limits still apply; immediate collection cannot manufacture missing source data.

## If setup does not work

Provide Eniris with the connection name, account/site scope, time of the attempt and the exact error. Check source availability and access permissions before retrying. Share a source screenshot or sample without passwords or tokens.

## Access and costs

Costs are not established for this connector. Confirm provider access, export licences and any project charges with Eniris before activation.

[All connection setup guides](/en/Monitoring/Integrations/connections)


# Sigenergy portal connection setup


import ClickableImage from '@site/src/components/ClickableImage';

# Sigenergy portal connection setup

Read measurements available through the authorised Sigenergy portal connection monitoring account. Only installations visible to that account can be collected.

<ClickableImage src="/img/eniris/monitoring/connection-guides/portal-access.webp" alt="A privacy-safe portal setup flow with sign-in, multi-factor authentication, installation selection and monitoring" maxWidth="1100px" />

*Confirm portal access, select only the agreed installations and complete any approval or multi-factor step before validating the data.*

Connection type: **Portal connection**.

## What to provide

Provide your company and contact person, the intended Insights account, the source identifiers and explicit permission for the requested scope. Include a recent source example for verification.

| Information / setting | What is needed | Supplied or configured by |
| --- | --- | --- |
| Account username (username) | Account name with access to the requested data. | Customer / installer |
| Account password (password) | Share the source-account password through the secure channel agreed with Eniris. | Customer / installer |

## Set up the connection

1. The customer signs in to the correct provider portal and checks that the requested installations and recent measurements are visible.
2. Grant the agreed account access and supply the required account details securely. Identify any login approval or multi-factor step so Eniris can complete the authorised connection.
3. Select this connector in onboarding, choose the intended Insights account and enter the fields in the table. Restrict installation scope to the agreed list where supported.
4. Create the connection and inspect the first retrieval. A successful manual portal login does not itself prove that the collection service can read data.

## Check the result

Check that the first collection completed, then open the intended Insights account and verify the relevant measurements or metadata. Compare source IDs, timestamps and units with the original source. Check the next scheduled execution as well. An active schedule or a healthy job alone does not prove that every requested measurement was received.

For ordinary onboarding meters, creation requests an immediate first run and keeps recurring collection active. Source publication times, upload intervals and provider limits still apply; immediate collection cannot manufacture missing source data.

## If setup does not work

Provide Eniris with the connection name, account/site scope, time of the attempt and the exact error. Check source availability and access permissions before retrying. Share a source screenshot or sample without passwords or tokens.

## Access and costs

Onboarding classifies this portal connection as free. This label does not establish the terms of a separate provider subscription or equipment licence.

[All connection setup guides](/en/Monitoring/Integrations/connections)


# SMA CSV setup


import ClickableImage from '@site/src/components/ClickableImage';

# SMA CSV setup

Import the supported SMA CSV file format. The source must deliver files in the format expected by this connector; renaming another file to CSV does not convert it.

<ClickableImage src="/img/eniris/monitoring/connection-guides/file-import.webp" alt="A data logger creating a structured file, transferring it securely and mapping its fields to a dashboard" maxWidth="1100px" />

*File onboarding is complete only after the source export, secure delivery, field mapping and recurring arrival have all been checked.*

Connection type: **File import**.

## Before you start

Provide the installed peak power used for spike filtering and confirm its interpretation against your export. CSV support depends on the exact SMA logger model.

## What to provide

Provide your company and contact person, the intended Insights account, the source identifiers and explicit permission for the requested scope. Include a recent source example for verification.

| Information / setting | What is needed | Supplied or configured by |
| --- | --- | --- |
| File delivery source (BROWSER) | Agree the source location and transport; Eniris configures access without putting credentials in public URLs. | Eniris with installer |
| Peak power for validation (LARGEST_KWP) | Installed peak power in kWp; confirm the rating used for this connector’s spike filter. | Customer / installer |
| Time zone (TIMEZONE) | Time zone of the source timestamps, for example Europe/Brussels; identify any files already using UTC. | Customer / installer |

## Set up the connection

1. Identify the source logger or export system and supply an original sample file. Confirm model, firmware, format and time zone with Eniris.
2. Agree the delivery route. For an Eniris FTP destination, request dedicated server, protocol, port, username, password and folder settings from Eniris. Use the agreed protocol exactly.
3. The installer or source owner enables recurring delivery. Eniris configures the accessible source location and device/field mappings; creating a meter does not configure the remote source.
4. Send a test file and record its timestamp. Eniris verifies arrival before starting collection, then compares the processed measurements with the original file.

### Configure the datalogger

The installer configures export on the datalogger using FTP credentials supplied by Eniris. Follow the [SMA datalogger FTP setup](https://docs.eniris.com/en/Monitoring/Integrations/datalogger-ftp/sma) for preparation, model-specific options where documented, and the test upload. Eniris must confirm the exact model and export format for this connector.

## Check the result

Check that the first collection completed, then open the intended Insights account and verify the relevant measurements or metadata. Compare source IDs, timestamps and units with the original source. Check the next scheduled execution as well. An active schedule or a healthy job alone does not prove that every requested measurement was received.

For ordinary onboarding meters, creation requests an immediate first run and keeps recurring collection active. Source publication times, upload intervals and provider limits still apply; immediate collection cannot manufacture missing source data.

## If setup does not work

If no file arrives, inspect the logger/export status, destination, authentication, network route and folder. If files arrive but no measurements appear, provide the filename, format, source identifiers and timestamp so Eniris can check parsing and mapping.

## Access and costs

Costs are not established for this connector. Confirm provider access, export licences and any project charges with Eniris before activation.

[All connection setup guides](/en/Monitoring/Integrations/connections)


# SMA (Sunny Portal API) setup


import ClickableImage from '@site/src/components/ClickableImage';

# SMA (Sunny Portal API) setup

Collect SMA installation and device telemetry using the existing Sunny Portal connector. Its ongoing collection is paced by the dedicated SMA scheduler.

<ClickableImage src="/img/eniris/monitoring/connection-guides/api-authorization.webp" alt="A privacy-safe API setup flow with authorization, limited installation scope, validation and a monitoring dashboard" maxWidth="1100px" />

*A reliable API connection combines the correct authorization method, an explicitly limited installation scope and a verified first retrieval.*

Connection type: **API and platform connection**.

## Before you start

The fields here describe the deployed account-based connector. SMA also offers OAuth-based developer APIs; those credentials are not interchangeable. [SMA API access control](https://developer.sma.de/api-access-control). Keep the managed SMA schedule selected during onboarding.

## What to provide

Provide your company and contact person, the intended Insights account, the source identifiers and explicit permission for the requested scope. Include a recent source example for verification.

| Information / setting | What is needed | Supplied or configured by |
| --- | --- | --- |
| Account username (USERNAME) | Account name with access to the requested data. | Customer / installer |
| Account password (PASSWORD) | Share the source-account password through the secure channel agreed with Eniris. | Customer / installer |
| Installation scope (INSTALLATION_ID_ALLOW_LIST) | Exact installation IDs or numbers to include. Agree explicitly before including every installation. Optional for this connector. | Customer / installer |

## Set up the connection

1. Ask the provider or account owner to enable the data access required by this connector. Confirm the permitted sites/devices and requested API version.
2. Supply the exact credential types in the table through the agreed secure channel. A portal password, API token, application secret and OAuth grant are not interchangeable.
3. Choose this connector and the target Insights account in onboarding. Enter the required fields and the authorised installation scope, then review before creating.
4. Check the first retrieval against the source account. If access succeeds but no data appears, verify site permissions, API entitlements, identifiers and the availability of measurements.

## Check the result

Check that the first collection completed, then open the intended Insights account and verify the relevant measurements or metadata. Compare source IDs, timestamps and units with the original source. Check the next scheduled execution as well. An active schedule or a healthy job alone does not prove that every requested measurement was received.

For ordinary onboarding meters, creation requests an immediate first run and keeps recurring collection active. Source publication times, upload intervals and provider limits still apply; immediate collection cannot manufacture missing source data.

## If setup does not work

Provide Eniris with the connection name, account/site scope, time of the attempt and the exact error. Check source availability and access permissions before retrying. Share a source screenshot or sample without passwords or tokens.

## Access and costs

Onboarding classifies this API route as paid. Confirm the applicable provider access and commercial agreement before activation.

[All connection setup guides](/en/Monitoring/Integrations/connections)


# SMA XML setup


import ClickableImage from '@site/src/components/ClickableImage';

# SMA XML setup

Import Sunny WebBox XML data from an agreed delivery location. This is a separate format from the SMA CSV connector.

<ClickableImage src="/img/eniris/monitoring/connection-guides/file-import.webp" alt="A data logger creating a structured file, transferring it securely and mapping its fields to a dashboard" maxWidth="1100px" />

*File onboarding is complete only after the source export, secure delivery, field mapping and recurring arrival have all been checked.*

Connection type: **File import**.

## Before you start

Provide the largest inverter rating in kWp for spike filtering. Ask Eniris to confirm the logger model and XML export before enabling delivery; the CSV setup procedure is not an XML recipe.

## What to provide

Provide your company and contact person, the intended Insights account, the source identifiers and explicit permission for the requested scope. Include a recent source example for verification.

| Information / setting | What is needed | Supplied or configured by |
| --- | --- | --- |
| File delivery source (BROWSER) | Agree the source location and transport; Eniris configures access without putting credentials in public URLs. | Eniris with installer |
| Peak power for validation (LARGEST_KWP) | Installed peak power in kWp; confirm the rating used for this connector’s spike filter. | Customer / installer |
| Time zone (TIMEZONE) | Time zone of the source timestamps, for example Europe/Brussels; identify any files already using UTC. | Customer / installer |

## Set up the connection

1. Identify the source logger or export system and supply an original sample file. Confirm model, firmware, format and time zone with Eniris.
2. Agree the delivery route. For an Eniris FTP destination, request dedicated server, protocol, port, username, password and folder settings from Eniris. Use the agreed protocol exactly.
3. The installer or source owner enables recurring delivery. Eniris configures the accessible source location and device/field mappings; creating a meter does not configure the remote source.
4. Send a test file and record its timestamp. Eniris verifies arrival before starting collection, then compares the processed measurements with the original file.

Use the XML-capable FTP push procedure for your exact WebBox model. The [SMA logger guide](/en/Monitoring/Integrations/datalogger-ftp/sma) explains the model distinction; ask Eniris to confirm XML settings before upload.

## Check the result

Check that the first collection completed, then open the intended Insights account and verify the relevant measurements or metadata. Compare source IDs, timestamps and units with the original source. Check the next scheduled execution as well. An active schedule or a healthy job alone does not prove that every requested measurement was received.

For ordinary onboarding meters, creation requests an immediate first run and keeps recurring collection active. Source publication times, upload intervals and provider limits still apply; immediate collection cannot manufacture missing source data.

## If setup does not work

If no file arrives, inspect the logger/export status, destination, authentication, network route and folder. If files arrive but no measurements appear, provide the filename, format, source identifiers and timestamp so Eniris can check parsing and mapping.

## Access and costs

Costs are not established for this connector. Confirm provider access, export licences and any project charges with Eniris before activation.

[All connection setup guides](/en/Monitoring/Integrations/connections)


# Smappee API setup


import ClickableImage from '@site/src/components/ClickableImage';

# Smappee API setup

Read Smappee data using the provider access configured for this connector. Confirm account permissions, installation scope and the requested measurements before activation.

<ClickableImage src="/img/eniris/monitoring/connection-guides/api-authorization.webp" alt="A privacy-safe API setup flow with authorization, limited installation scope, validation and a monitoring dashboard" maxWidth="1100px" />

*A reliable API connection combines the correct authorization method, an explicitly limited installation scope and a verified first retrieval.*

Connection type: **API and platform connection**.

## What to provide

Provide your company and contact person, the intended Insights account, the source identifiers and explicit permission for the requested scope. Include a recent source example for verification.

| Information / setting | What is needed | Supplied or configured by |
| --- | --- | --- |
| Application / key ID (CLIENT_ID) | Identifier belonging to the supplied secret and provider account. | Customer / installer |
| API/application secret (CLIENT_SECRET) | Secret paired with the corresponding client, application or API key ID; share securely. | Customer / installer |
| Account username (USERNAME) | Account name with access to the requested data. | Customer / installer |
| Account password (PASSWORD) | Share the source-account password through the secure channel agreed with Eniris. | Customer / installer |
| Installation scope (INSTALLATION_ID_ALLOW_LIST) | Exact installation IDs or numbers to include. Agree explicitly before including every installation. | Customer / installer |

## Set up the connection

1. Ask the provider or account owner to enable the data access required by this connector. Confirm the permitted sites/devices and requested API version.
2. Supply the exact credential types in the table through the agreed secure channel. A portal password, API token, application secret and OAuth grant are not interchangeable.
3. Choose this connector and the target Insights account in onboarding. Enter the required fields and the authorised installation scope, then review before creating.
4. Check the first retrieval against the source account. If access succeeds but no data appears, verify site permissions, API entitlements, identifiers and the availability of measurements.

## Check the result

Check that the first collection completed, then open the intended Insights account and verify the relevant measurements or metadata. Compare source IDs, timestamps and units with the original source. Check the next scheduled execution as well. An active schedule or a healthy job alone does not prove that every requested measurement was received.

For ordinary onboarding meters, creation requests an immediate first run and keeps recurring collection active. Source publication times, upload intervals and provider limits still apply; immediate collection cannot manufacture missing source data.

## If setup does not work

Provide Eniris with the connection name, account/site scope, time of the attempt and the exact error. Check source availability and access permissions before retrying. Share a source screenshot or sample without passwords or tokens.

## Access and costs

Costs are not established for this connector. Confirm provider access, export licences and any project charges with Eniris before activation.

[All connection setup guides](/en/Monitoring/Integrations/connections)


# Sofar setup


import ClickableImage from '@site/src/components/ClickableImage';

# Sofar setup

Import the supported Sofar file layout from an agreed delivery source.

<ClickableImage src="/img/eniris/monitoring/connection-guides/file-import.webp" alt="A data logger creating a structured file, transferring it securely and mapping its fields to a dashboard" maxWidth="1100px" />

*File onboarding is complete only after the source export, secure delivery, field mapping and recurring arrival have all been checked.*

Connection type: **File import**.

## What to provide

Provide your company and contact person, the intended Insights account, the source identifiers and explicit permission for the requested scope. Include a recent source example for verification.

| Information / setting | What is needed | Supplied or configured by |
| --- | --- | --- |
| File delivery source (BROWSER) | Agree the source location and transport; Eniris configures access without putting credentials in public URLs. | Eniris with installer |
| Time zone (TIMEZONE) | Time zone of the source timestamps, for example Europe/Brussels; identify any files already using UTC. | Customer / installer |

## Set up the connection

1. Identify the source logger or export system and supply an original sample file. Confirm model, firmware, format and time zone with Eniris.
2. Agree the delivery route. For an Eniris FTP destination, request dedicated server, protocol, port, username, password and folder settings from Eniris. Use the agreed protocol exactly.
3. The installer or source owner enables recurring delivery. Eniris configures the accessible source location and device/field mappings; creating a meter does not configure the remote source.
4. Send a test file and record its timestamp. Eniris verifies arrival before starting collection, then compares the processed measurements with the original file.

## Check the result

Check that the first collection completed, then open the intended Insights account and verify the relevant measurements or metadata. Compare source IDs, timestamps and units with the original source. Check the next scheduled execution as well. An active schedule or a healthy job alone does not prove that every requested measurement was received.

For ordinary onboarding meters, creation requests an immediate first run and keeps recurring collection active. Source publication times, upload intervals and provider limits still apply; immediate collection cannot manufacture missing source data.

## If setup does not work

If no file arrives, inspect the logger/export status, destination, authentication, network route and folder. If files arrive but no measurements appear, provide the filename, format, source identifiers and timestamp so Eniris can check parsing and mapping.

## Access and costs

Costs are not established for this connector. Confirm provider access, export licences and any project charges with Eniris before activation.

[All connection setup guides](/en/Monitoring/Integrations/connections)


# Solar Log CSV setup


import ClickableImage from '@site/src/components/ClickableImage';

# Solar Log CSV setup

Import the supported Solar Log CSV file format. The source must deliver files in the format expected by this connector; renaming another file to CSV does not convert it.

<ClickableImage src="/img/eniris/monitoring/connection-guides/file-import.webp" alt="A data logger creating a structured file, transferring it securely and mapping its fields to a dashboard" maxWidth="1100px" />

*File onboarding is complete only after the source export, secure delivery, field mapping and recurring arrival have all been checked.*

Connection type: **File import**.

## What to provide

Provide your company and contact person, the intended Insights account, the source identifiers and explicit permission for the requested scope. Include a recent source example for verification.

| Information / setting | What is needed | Supplied or configured by |
| --- | --- | --- |
| File delivery source (BROWSER) | Agree the source location and transport; Eniris configures access without putting credentials in public URLs. | Eniris with installer |
| Time zone (TIMEZONE) | Time zone of the source timestamps, for example Europe/Brussels; identify any files already using UTC. | Customer / installer |
| Installation scope (INSTALLATION_ID_ALLOW_LIST) | Exact installation IDs or numbers to include. Agree explicitly before including every installation. | Customer / installer |
| Exclusions (INSTALLATION_ID_DENY_LIST) | IDs that must not be processed; Eniris checks the identifier type used by this connector. | Customer / installer |

## Set up the connection

1. Identify the source logger or export system and supply an original sample file. Confirm model, firmware, format and time zone with Eniris.
2. Agree the delivery route. For an Eniris FTP destination, request dedicated server, protocol, port, username, password and folder settings from Eniris. Use the agreed protocol exactly.
3. The installer or source owner enables recurring delivery. Eniris configures the accessible source location and device/field mappings; creating a meter does not configure the remote source.
4. Send a test file and record its timestamp. Eniris verifies arrival before starting collection, then compares the processed measurements with the original file.

### Configure the datalogger

The installer configures export on the datalogger using FTP credentials supplied by Eniris. Follow the [Solar-Log FTP setup](https://docs.eniris.com/en/Monitoring/Integrations/datalogger-ftp/solar-log) for preparation, model-specific options where documented, and the test upload. Eniris must confirm the exact model and export format for this connector.

## Check the result

Check that the first collection completed, then open the intended Insights account and verify the relevant measurements or metadata. Compare source IDs, timestamps and units with the original source. Check the next scheduled execution as well. An active schedule or a healthy job alone does not prove that every requested measurement was received.

For ordinary onboarding meters, creation requests an immediate first run and keeps recurring collection active. Source publication times, upload intervals and provider limits still apply; immediate collection cannot manufacture missing source data.

## If setup does not work

If no file arrives, inspect the logger/export status, destination, authentication, network route and folder. If files arrive but no measurements appear, provide the filename, format, source identifiers and timestamp so Eniris can check parsing and mapping.

## Access and costs

Costs are not established for this connector. Confirm provider access, export licences and any project charges with Eniris before activation.

[All connection setup guides](/en/Monitoring/Integrations/connections)


# Solar Log portal connection setup


import ClickableImage from '@site/src/components/ClickableImage';

# Solar Log portal connection setup

Read measurements available through the authorised Solar Log portal connection monitoring account. Only installations visible to that account can be collected.

<ClickableImage src="/img/eniris/monitoring/connection-guides/portal-access.webp" alt="A privacy-safe portal setup flow with sign-in, multi-factor authentication, installation selection and monitoring" maxWidth="1100px" />

*Confirm portal access, select only the agreed installations and complete any approval or multi-factor step before validating the data.*

Connection type: **Portal connection**.

## What to provide

Provide your company and contact person, the intended Insights account, the source identifiers and explicit permission for the requested scope. Include a recent source example for verification.

| Information / setting | What is needed | Supplied or configured by |
| --- | --- | --- |
| Source endpoint (BASE_URL) | Exact endpoint for this customer or deployment; confirm it is reachable by the collection service. | Customer / installer |
| Account username (USERNAME) | Account name with access to the requested data. | Customer / installer |
| Account password (PASSWORD) | Share the source-account password through the secure channel agreed with Eniris. | Customer / installer |
| Installation scope (INSTALLATION_ID_ALLOW_LIST) | Exact installation IDs or numbers to include. Agree explicitly before including every installation. | Customer / installer |

## Set up the connection

1. The customer signs in to the correct provider portal and checks that the requested installations and recent measurements are visible.
2. Grant the agreed account access and supply the required account details securely. Identify any login approval or multi-factor step so Eniris can complete the authorised connection.
3. Select this connector in onboarding, choose the intended Insights account and enter the fields in the table. Restrict installation scope to the agreed list where supported.
4. Create the connection and inspect the first retrieval. A successful manual portal login does not itself prove that the collection service can read data.

## Check the result

Check that the first collection completed, then open the intended Insights account and verify the relevant measurements or metadata. Compare source IDs, timestamps and units with the original source. Check the next scheduled execution as well. An active schedule or a healthy job alone does not prove that every requested measurement was received.

For ordinary onboarding meters, creation requests an immediate first run and keeps recurring collection active. Source publication times, upload intervals and provider limits still apply; immediate collection cannot manufacture missing source data.

## If setup does not work

Provide Eniris with the connection name, account/site scope, time of the attempt and the exact error. Check source availability and access permissions before retrying. Share a source screenshot or sample without passwords or tokens.

## Access and costs

Onboarding classifies this portal connection as free. This label does not establish the terms of a separate provider subscription or equipment licence.

[All connection setup guides](/en/Monitoring/Integrations/connections)


# Solar Man portal connection setup


import ClickableImage from '@site/src/components/ClickableImage';

# Solar Man portal connection setup

Read measurements available through the authorised Solar Man portal connection monitoring account. Only installations visible to that account can be collected.

<ClickableImage src="/img/eniris/monitoring/connection-guides/portal-access.webp" alt="A privacy-safe portal setup flow with sign-in, multi-factor authentication, installation selection and monitoring" maxWidth="1100px" />

*Confirm portal access, select only the agreed installations and complete any approval or multi-factor step before validating the data.*

Connection type: **Portal connection**.

## What to provide

Provide your company and contact person, the intended Insights account, the source identifiers and explicit permission for the requested scope. Include a recent source example for verification.

| Information / setting | What is needed | Supplied or configured by |
| --- | --- | --- |
| Account email (EMAIL) | Email address of the authorised source account. | Customer / installer |
| Account password (PASSWORD) | Share the source-account password through the secure channel agreed with Eniris. | Customer / installer |

## Set up the connection

1. The customer signs in to the correct provider portal and checks that the requested installations and recent measurements are visible.
2. Grant the agreed account access and supply the required account details securely. Identify any login approval or multi-factor step so Eniris can complete the authorised connection.
3. Select this connector in onboarding, choose the intended Insights account and enter the fields in the table. Restrict installation scope to the agreed list where supported.
4. Create the connection and inspect the first retrieval. A successful manual portal login does not itself prove that the collection service can read data.

## Check the result

Check that the first collection completed, then open the intended Insights account and verify the relevant measurements or metadata. Compare source IDs, timestamps and units with the original source. Check the next scheduled execution as well. An active schedule or a healthy job alone does not prove that every requested measurement was received.

For ordinary onboarding meters, creation requests an immediate first run and keeps recurring collection active. Source publication times, upload intervals and provider limits still apply; immediate collection cannot manufacture missing source data.

## If setup does not work

Provide Eniris with the connection name, account/site scope, time of the attempt and the exact error. Check source availability and access permissions before retrying. Share a source screenshot or sample without passwords or tokens.

## Access and costs

Onboarding classifies this portal connection as free. This label does not establish the terms of a separate provider subscription or equipment licence.

[All connection setup guides](/en/Monitoring/Integrations/connections)


# SolarEdge Monitoring API (V2) setup


import ClickableImage from '@site/src/components/ClickableImage';

# SolarEdge Monitoring API (V2) setup

Connect your SolarEdge installation to Eniris through the V2 Monitoring API. You create a Monitoring API application on the SolarEdge developer portal and send its API key to Eniris through our support portal. The whole process takes about 10 minutes.

<ClickableImage src="/img/eniris/monitoring/connection-guides/api-authorization.webp" alt="A privacy-safe API setup flow with authorization, limited installation scope, validation and a monitoring dashboard" maxWidth="1100px" />

*A reliable API connection combines the correct authorization method, an explicitly limited installation scope and a verified first retrieval.*

Connection type: **API and platform connection**.

## Before you start

Make sure you have:

- Login details for the SolarEdge developer portal
- Access to the fleet (sites) you want to connect, or the contact details of the fleet owner
- An account on the Eniris support portal

## Step 1: Log in to the SolarEdge developer portal

Go to [developer.solaredge.com](https://developer.solaredge.com) and log in with your SolarEdge account. After logging in, you land on the dashboard.

{/* TODO: add a ClickableImage of the SolarEdge developer portal dashboard */}

## Step 2: Create a new application

Go to **Applications** and click **Create application** in the top right corner. Fill in the form:

| Field | What to enter |
| ---------------- | ------------------------------------------------------ |
| Application name | Any name you like, for example `EnirisAPIConnection` |
| Description | API key for Eniris |
| API service | **Monitoring API** |

Then click **Next**.

## Step 3: Choose the fleet and access duration

Pick **My fleet** whenever it is available; it is the quickest option because no one else needs to approve it.

| Option | When to use it | What you need to do |
| ------------------ | ------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------- |
| **My fleet** | The sites are in your own SolarEdge account | Nothing extra |
| **External fleet** | The sites belong to another SolarEdge account, for example an installer or site owner | Send the email or share link that SolarEdge generates to the fleet owner, who must approve access |

For **Access duration**, choose the longest period available. A shorter period means the connection to Eniris stops when access expires and the setup has to be repeated.

## Step 4: Retrieve the API credentials

Once the application is created, open it and go to **Credentials**. Copy the API key; you send it to Eniris in the next step.

If you chose an external fleet, wait until the fleet owner has approved access before sending the key.

> **Important:** treat the API key like a password. Never paste it directly into an email, ticket or chat message.

## Step 5: Send the API key to Eniris

Share the key through a one-time secret link and submit that link in a support ticket, so the key is never stored in plain text.

1. Go to [onetimesecret.com](https://onetimesecret.com), paste the API key and create a secret link.
2. Go to the Eniris support portal and create a new ticket.
3. Choose **APP** or **SmartgridX** as the category.
4. Copy the ticket template below into the ticket and fill in your choices.
5. Paste the one-time secret link in the template and submit the ticket.

The link can be opened only once, so the key cannot be read by anyone after Eniris has retrieved it.

### Ticket template

Copy this into the ticket. Leave the allow and deny lists empty unless you want to limit which installations are collected.

```text
Subject: Upgrading SolarEdge to V2

Hello Eniris team,

We would like to upgrade our SolarEdge connection to the V2 API.

API key (one-time secret link): <paste link here>
Installation allow list:
Installation deny list:
Run interval (hours): 1
Data resolution: QUARTER_HOUR

Kind regards,
```

### Parameters

| Parameter | What it does | What to fill in | Default |
| ----------------------- | ------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------- | ---------------- |
| API key | Gives Eniris access to your SolarEdge data | The one-time secret link from Step 5 | Required |
| Installation allow list | Collects only the installations you list | Leave empty for all installations, or list the installation IDs, for example 1148616, 1148617 | Empty |
| Installation deny list | Skips the installations you list | Leave empty to skip none, or list the installation IDs you want skipped | Empty |
| Run interval (hours) | How often data is collected. Each run picks up everything since the previous one, including anything missed | A whole number of hours | 1 |
| Data resolution | How detailed the collected data is | `QUARTER_HOUR` for a value every 15 minutes, or `HOUR` for one every hour | `QUARTER_HOUR` |

**Finding an installation ID:** open the installation in the SolarEdge monitoring portal and look at the address bar. The number after `siteId=` is the installation ID.

```text
https://monitoring.solaredge.com/one#/commercial/analysis?siteId=xxxxx
```

## Step 6: Activate new installations in Eniris

Installations already on the Eniris platform keep their current status. New installations are added as **inactive**, and no data is collected for them until you activate them.

A new installation on your SolarEdge account appears in Eniris within 24 hours, because the site list is refreshed once a day.

To start collecting data, go to **Settings → Installations without follow up** in the Eniris portal and click **Activate** for each installation you want to follow up.

Activation works the other way round too. To stop collecting data for an installation you no longer need, open that installation, go to **Settings** and unmark **Show installation**.

## Credits and tiers

Each data collection costs API credits, and your SolarEdge plan sets how many credits you have per month. Check the expected usage below against your tier before you choose a run interval.

Find the row that matches your equipment and the number of installations. The figures are an estimate of the total credits used per month.

| Installation type | Installations | Every 1 h | Every 2 h | Every 4 h | Every 6 h | Every 12 h | Every 24 h (hourly data) |
| -------------------------- | ------------: | --------: | --------: | --------: | --------: | ---------: | -----------------------: |
| Inverter only | 1 | 1,750 | 900 | 470 | 330 | 180 | 110 |
| Inverter only | 10 | 9,460 | 4,760 | 2,410 | 1,620 | 840 | 440 |
| Inverter only | 50 | 43,800 | 22,000 | 11,100 | 7,370 | 3,740 | 1,920 |
| Inverter only | 100 | 86,600 | 43,400 | 21,800 | 14,600 | 7,360 | 3,760 |
| Inverter only | 1,000 | 860,000 | 431,000 | 216,000 | 145,000 | 72,800 | 37,100 |
| Inverter + meter | 1 | 2,610 | 1,330 | 680 | 470 | 260 | 150 |
| Inverter + meter | 10 | 18,100 | 9,040 | 4,540 | 3,050 | 1,550 | 800 |
| Inverter + meter | 50 | 86,600 | 43,400 | 21,700 | 14,500 | 7,300 | 3,700 |
| Inverter + meter | 100 | 173,000 | 86,200 | 43,200 | 28,900 | 14,500 | 7,330 |
| Inverter + meter | 1,000 | 1,720,000 | 859,000 | 430,000 | 287,000 | 145,000 | 72,700 |
| Inverter + meter + battery | 1 | 4,320 | 2,180 | 1,110 | 750 | 400 | 220 |
| Inverter + meter + battery | 10 | 35,200 | 17,600 | 8,820 | 5,900 | 2,980 | 1,510 |
| Inverter + meter + battery | 50 | 173,000 | 86,100 | 43,100 | 28,800 | 14,500 | 7,270 |
| Inverter + meter + battery | 100 | 344,000 | 172,000 | 86,000 | 57,400 | 28,800 | 14,500 |
| Inverter + meter + battery | 1,000 | 3,430,000 | 1,720,000 | 858,000 | 573,000 | 287,000 | 144,000 |

The **Every 24 h** column assumes hourly data (`HOUR`); the other columns assume quarter-hourly data (`QUARTER_HOUR`).

### SolarEdge tiers

| Tier | Monthly price | Credits / month | CPM | Max apps |
| ----------------- | ------------: | --------------: | ------: | -------: |
| Free | $0 | 2,000 | 10 | 1 |
| Business Starter | $100 | 20,000 | 25 | 1 |
| Business Growth | $400 | 100,000 | 50 | 3 |
| Business Pro | $1,000 | 400,000 | 100 | 5 |
| Enterprise | Custom | Custom | Custom | Custom |

Tiers as of 1 October 2026. SolarEdge can change its prices and allowances at any time.

You buy or change your tier in the SolarEdge developer portal under **Settings → Plans**. See [Tiers and rate limits](https://api-docs.solaredge.com/docs/developer-platform/pwh8p4k2wtajh-tiers-and-rate-limits) in the SolarEdge developer documentation for the current figures.

## Need help?

If you have any questions about the steps above, contact Eniris support for further assistance.

[All connection setup guides](/en/Monitoring/Integrations/connections)


# SolarEdge (portal connection) setup


import ClickableImage from '@site/src/components/ClickableImage';

# SolarEdge (portal connection) setup

Read measurements available through the authorised SolarEdge (portal connection) monitoring account. Only installations visible to that account can be collected.

<ClickableImage src="/img/eniris/monitoring/connection-guides/portal-access.webp" alt="A privacy-safe portal setup flow with sign-in, multi-factor authentication, installation selection and monitoring" maxWidth="1100px" />

*Confirm portal access, select only the agreed installations and complete any approval or multi-factor step before validating the data.*

Connection type: **Portal connection**.

## What to provide

Provide your company and contact person, the intended Insights account, the source identifiers and explicit permission for the requested scope. Include a recent source example for verification.

| Information / setting | What is needed | Supplied or configured by |
| --- | --- | --- |
| Account username (USERNAME) | Account name with access to the requested data. | Customer / installer |
| Account password (PASSWORD) | Share the source-account password through the secure channel agreed with Eniris. | Customer / installer |
| Installation scope (INSTALLATION_ID_ALLOW_LIST) | Exact installation IDs or numbers to include. Agree explicitly before including every installation. Optional for this connector. | Customer / installer |

## Set up the connection

1. The customer signs in to the correct provider portal and checks that the requested installations and recent measurements are visible.
2. Grant the agreed account access and supply the required account details securely. Identify any login approval or multi-factor step so Eniris can complete the authorised connection.
3. Select this connector in onboarding, choose the intended Insights account and enter the fields in the table. Restrict installation scope to the agreed list where supported.
4. Create the connection and inspect the first retrieval. A successful manual portal login does not itself prove that the collection service can read data.

## Check the result

Check that the first collection completed, then open the intended Insights account and verify the relevant measurements or metadata. Compare source IDs, timestamps and units with the original source. Check the next scheduled execution as well. An active schedule or a healthy job alone does not prove that every requested measurement was received.

For ordinary onboarding meters, creation requests an immediate first run and keeps recurring collection active. Source publication times, upload intervals and provider limits still apply; immediate collection cannot manufacture missing source data.

## If setup does not work

Provide Eniris with the connection name, account/site scope, time of the attempt and the exact error. Check source availability and access permissions before retrying. Share a source screenshot or sample without passwords or tokens.

## Access and costs

Onboarding classifies this portal connection as free. This label does not establish the terms of a separate provider subscription or equipment licence.

[All connection setup guides](/en/Monitoring/Integrations/connections)


# Solarman (API) setup


import ClickableImage from '@site/src/components/ClickableImage';

# Solarman (API) setup

Eniris can read your plant and device data through the official SOLARMAN Open API. You ask Solarman for API access once. After that you send four values to Eniris through our support portal.

<ClickableImage src="/img/eniris/monitoring/connection-guides/api-authorization.webp" alt="A privacy-safe API setup flow with authorization, limited installation scope, validation and a monitoring dashboard" maxWidth="1100px" />

*A reliable API connection combines the correct authorization method, an explicitly limited installation scope and a verified first retrieval.*

Connection type: **API and platform connection**.

## Before you start

Make sure you have:

- A SOLARMAN Smart or SOLARMAN Business account where your plants and data loggers are visible and show current data. The connection can only read what this account can read.
- An account on the international data centre (`globalapi.solarmanpv.com`). Accounts on the Chinese data centre cannot be read by this connector.
- An account on the Eniris support portal.

## Step 1: Ask Solarman to activate the API

API access is not enabled by default. Send your request to your Solarman business contact or to the service address **service@solarmanpv.com**. Solarman wants to know who you are, what kind of customer you are and what you will use the API for. Their [Open API docs](https://doc.solarmanpv.com/en/Documentation%20and%20Quick%20Guide) describes the procedure. You can also open a ticket at the [SOLARMAN Help Centre](https://helpcenter.solarmanpv.com/portal/en/signin).

Use the template below. Replace the values between angle brackets and delete what does not apply.

```text
Subject: OpenAPI activation request for <your Solarman account email>

Dear Solarman support,

I would like to activate the OpenAPI for my SOLARMAN account.

Solarman account (email): <your Solarman login>
Platform: SOLARMAN Smart / SOLARMAN Business
Data centre: International
Customer type: individual / equipment manufacturer / installation and
maintenance provider / distributor / investor
Number of plants: <number>

Reason: my PV installation is monitored by Eniris (https://eniris.com).
Eniris reads my plant and device data through the SOLARMAN OpenAPI for
monitoring and reporting.

Please send the APP ID and APP SECRET to this email address.

Kind regards,
<name>, <company>
```

## Step 2: Complete Solarman's review

Solarman registers you as a developer and creates the application. The application then goes through a review. Solarman may ask you to confirm the API Developer Agreement by email to **customerservice@solarmanpv.com** before the activation continues.

## Step 3: Receive your credentials

When the review is done, Solarman activates the API and sends the **APP ID** and **APP SECRET** to your email address.

You do not have to create an access token or a refresh token yourself. Eniris takes care of that with the values below.

| Information / setting | What is needed |
| --- | --- |
| Application ID (`APP_ID`) | Issued by Solarman after API activation. |
| Application secret (`APP_SECRET`) | Secret that belongs to that APP ID. |
| Account email (`EMAIL`) | The Solarman account that sees the plants. |
| Account password (`PASSWORD`) | Password of that account. |
| Plant scope | The plants Eniris may read. |

Use a separate Solarman account for Eniris where you can and share the relevant plants with it. That is safer than handing over a personal or administrator login.

> **Important:** treat the APP SECRET and the account password like passwords. Never paste them into an email, a ticket or a chat message.

## Step 4: Send the credentials to Eniris

Share the secret and the password through a one-time secret link and put that link in a support ticket. Nothing is then stored in plain text.

1. Go to [onetimesecret.com](https://onetimesecret.com), paste the APP SECRET and the account password and create a secret link.
2. Go to the Eniris support portal and create a new ticket.
3. Choose APP or SmartgridX as the category.
4. Copy the ticket template below into the ticket and fill in your choices.
5. Paste the one-time secret link in the template and submit the ticket.

The link can be opened only once. After Eniris has read it, nobody else can.

### Ticket template

Copy this into the ticket. Leave the plant list empty if you want all plants.

```text
Subject: New Solarman (API) connection

Hello Eniris team,

We would like to connect our Solarman installation through the official
Solarman Open API.

APP ID: <your APP ID>
Solarman account (email): <your Solarman login>
APP SECRET and password (one-time secret link): <paste link here>
Plants to collect:

Kind regards,
```

:::caution Changing your Solarman password stops the data collection
Solarman blocks the API access as soon as the account password is reset or changed. The same happens when the role of the account changes. The connection then stops collecting and no data is stored for that period. Open a ticket before you change the password and send the new credentials through a new one-time secret link. We can then update the connection the same day.
:::

## Step 5: Check the result

What we collect depends on your equipment.

| Level | What is collected |
| --- | --- |
| Plant | Name, installed capacity, time zone, coordinates, address, commissioning date, generation power and production |
| Inverter | Total AC power, total yield, phase voltages, line voltages and phase currents |
| Hybrid inverter | Total AC power, imported and exported energy |
| Battery | State of charge, state of health, charged and discharged energy, power, current and voltage |
| Optimiser | Voltage, current, power and yield per optimiser |
| Grid meter | Total and per-phase power, reactive power, line voltages, imported and exported energy |
| Consumption meter | Imported energy and power |
| Alarms | Device alerts, linked to the device they belong to |


## Access and costs

Solarman decides the conditions for API access and can charge for it. That depends on your platform, the number of plants and how many calls are needed. Ask Solarman what applies to your account when you request activation. Their [API access conditions](https://helpcenter.solarmanpv.com/portal/en/kb/articles/i-want-to-open-api-how-can-i-open-api) page has the current overview.

## Need help?

Any questions about the steps above? Contact Eniris support and we will help you further.

[All connection setup guides](/en/Monitoring/Integrations/connections)


# Solis (SolisCloud API) setup


import ClickableImage from '@site/src/components/ClickableImage';

# Solis (SolisCloud API) setup

Read Solis (SolisCloud ) data using the provider access configured for this connector. Confirm account permissions, installation scope and the requested measurements before activation.

<ClickableImage src="/img/eniris/monitoring/connection-guides/api-authorization.webp" alt="A privacy-safe API setup flow with authorization, limited installation scope, validation and a monitoring dashboard" maxWidth="1100px" />

*A reliable API connection combines the correct authorization method, an explicitly limited installation scope and a verified first retrieval.*

Connection type: **API and platform connection**.

## Before you start

Request API activation from Solis. After activation, the current SolisCloud guide directs owners/installers to Service → API Management to retrieve KeyID and KeySecret. Supply those as API key ID and secret; do not substitute OAuth client credentials. [SolisCloud activation guide](https://developer.soliscloud.com/guide/quick-start).

## What to provide

Provide your company and contact person, the intended Insights account, the source identifiers and explicit permission for the requested scope. Include a recent source example for verification.

| Information / setting | What is needed | Supplied or configured by |
| --- | --- | --- |
| Application / key ID (API_KEY_ID) | Identifier belonging to the supplied secret and provider account. | Customer / installer |
| API/application secret (API_KEY_SECRET) | Secret paired with the corresponding client, application or API key ID; share securely. | Customer / installer |

## Set up the connection

1. Ask the provider or account owner to enable the data access required by this connector. Confirm the permitted sites/devices and requested API version.
2. Supply the exact credential types in the table through the agreed secure channel. A portal password, API token, application secret and OAuth grant are not interchangeable.
3. Choose this connector and the target Insights account in onboarding. Enter the required fields and the authorised installation scope, then review before creating.
4. Check the first retrieval against the source account. If access succeeds but no data appears, verify site permissions, API entitlements, identifiers and the availability of measurements.

## Check the result

Check that the first collection completed, then open the intended Insights account and verify the relevant measurements or metadata. Compare source IDs, timestamps and units with the original source. Check the next scheduled execution as well. An active schedule or a healthy job alone does not prove that every requested measurement was received.

For ordinary onboarding meters, creation requests an immediate first run and keeps recurring collection active. Source publication times, upload intervals and provider limits still apply; immediate collection cannot manufacture missing source data.

## If setup does not work

Provide Eniris with the connection name, account/site scope, time of the attempt and the exact error. Check source availability and access permissions before retrying. Share a source screenshot or sample without passwords or tokens.

## Access and costs

Costs are not established for this connector. Confirm provider access, export licences and any project charges with Eniris before activation.

[All connection setup guides](/en/Monitoring/Integrations/connections)


# Solora FTP Export setup


import ClickableImage from '@site/src/components/ClickableImage';

# Solora FTP Export setup

Export authorised Insights measurements to the configured Solora FTP destination.

<ClickableImage src="/img/eniris/monitoring/connection-guides/outgoing-export.webp" alt="Authorized monitoring measurements being mapped, encrypted and delivered to a receiving system" maxWidth="1100px" />

*Agree the exact measurement scope and file layout, then verify both delivery and interpretation with the receiving platform.*

Connection type: **Outgoing data export**.

## What to provide

Provide your company and contact person, the intended Insights account, the source identifiers and explicit permission for the requested scope. Include a recent source example for verification.

| Information / setting | What is needed | Supplied or configured by |
| --- | --- | --- |
| Destination FTP server (FTP_HOST) | Destination hostname and agreed transport, port and folder for the outgoing export. | Receiving platform |
| Destination FTP access (FTP_USERNAME) | Dedicated destination credentials, supplied securely by the receiving platform. | Receiving platform |
| Destination FTP access (FTP_PASSWORD) | Dedicated destination credentials, supplied securely by the receiving platform. | Receiving platform |

## Set up the connection

1. Agree with the receiving platform which Insights assets and measurements may be exported, the file layout and the delivery interval.
2. Obtain destination credentials from the receiving platform. Eniris separately configures authorised Insights access. These are two different accounts.
3. Eniris enters the destination and mapping, reviews the scope and starts the first export. No datalogger needs to push into Eniris for this route.
4. Ask the receiving platform to confirm both the file arrival and the interpreted measurements; compare timestamps, units and asset identifiers.

## Check the result

Confirm delivery and parsed data with the receiving platform. Compare source IDs, timestamps and units with the original source. Check the next scheduled execution as well. An active schedule or a healthy job alone does not prove that every requested measurement was received.

For ordinary onboarding meters, creation requests an immediate first run and keeps recurring collection active. Source publication times, upload intervals and provider limits still apply; immediate collection cannot manufacture missing source data.

## If setup does not work

Provide Eniris with the connection name, account/site scope, time of the attempt and the exact error. Check source availability and access permissions before retrying. Share a source screenshot or sample without passwords or tokens.

## Access and costs

Costs are not established for this connector. Confirm provider access, export licences and any project charges with Eniris before activation.

[All connection setup guides](/en/Monitoring/Integrations/connections)


# Sonnen Battery Data Recovery setup


import ClickableImage from '@site/src/components/ClickableImage';

# Sonnen Battery Data Recovery setup

Recover historical Sonnen battery data for a project-specific deployment. The connector exposes no standard credential form; Eniris must confirm its configured plants, access and requested period before running it.

<ClickableImage src="/img/eniris/monitoring/connection-guides/api-authorization.webp" alt="A privacy-safe API setup flow with authorization, limited installation scope, validation and a monitoring dashboard" maxWidth="1100px" />

*A reliable API connection combines the correct authorization method, an explicitly limited installation scope and a verified first retrieval.*

Connection type: **API and platform connection**.

## What to provide

Provide your company and contact person, the intended Insights account, the source identifiers and explicit permission for the requested scope. Include a recent source example for verification.

This connector exposes no standard customer input fields. Eniris must check the configured source, supported scope and any deployment-specific access before activation. An empty form does not mean every source or device is supported.

## Set up the connection

1. Contact Eniris with the intended source, required output and time range. This specialised connector requires an operator review before use.
2. Eniris checks the configured source, access and scope in the deployed implementation. The standard onboarding form cannot configure all of these details.
3. The operator agrees a limited first run and verifies its output against the original source before enabling further processing.

## Check the result

Check that the first collection completed, then open the intended Insights account and verify the relevant measurements or metadata. Compare source IDs, timestamps and units with the original source. Check the next scheduled execution as well. An active schedule or a healthy job alone does not prove that every requested measurement was received.

For ordinary onboarding meters, creation requests an immediate first run and keeps recurring collection active. Source publication times, upload intervals and provider limits still apply; immediate collection cannot manufacture missing source data.

## If setup does not work

Provide Eniris with the connection name, account/site scope, time of the attempt and the exact error. Check source availability and access permissions before retrying. Share a source screenshot or sample without passwords or tokens.

## Access and costs

Costs are not established for this connector. Confirm provider access, export licences and any project charges with Eniris before activation.

[All connection setup guides](/en/Monitoring/Integrations/connections)


# Studer setup


import ClickableImage from '@site/src/components/ClickableImage';

# Studer setup

Read selected Studer measurements for a specific installation number using account access.

<ClickableImage src="/img/eniris/monitoring/connection-guides/api-authorization.webp" alt="A privacy-safe API setup flow with authorization, limited installation scope, validation and a monitoring dashboard" maxWidth="1100px" />

*A reliable API connection combines the correct authorization method, an explicitly limited installation scope and a verified first retrieval.*

Connection type: **API and platform connection**.

## What to provide

Provide your company and contact person, the intended Insights account, the source identifiers and explicit permission for the requested scope. Include a recent source example for verification.

| Information / setting | What is needed | Supplied or configured by |
| --- | --- | --- |
| Account email (EMAIL) | Email address of the authorised source account. | Customer / installer |
| Account password (PWD) | Share the source-account password through the secure channel agreed with Eniris. | Customer / installer |
| Installation scope (INSTALLATION_NUMBER) | Exact installation IDs or numbers to include. Agree explicitly before including every installation. | Customer / installer |
| Required measurements (MEASUREMENTS) | Signals and units to collect; Eniris configures the corresponding measurement mapping. | Eniris with customer |

## Set up the connection

1. Ask the provider or account owner to enable the data access required by this connector. Confirm the permitted sites/devices and requested API version.
2. Supply the exact credential types in the table through the agreed secure channel. A portal password, API token, application secret and OAuth grant are not interchangeable.
3. Choose this connector and the target Insights account in onboarding. Enter the required fields and the authorised installation scope, then review before creating.
4. Check the first retrieval against the source account. If access succeeds but no data appears, verify site permissions, API entitlements, identifiers and the availability of measurements.

## Check the result

Check that the first collection completed, then open the intended Insights account and verify the relevant measurements or metadata. Compare source IDs, timestamps and units with the original source. Check the next scheduled execution as well. An active schedule or a healthy job alone does not prove that every requested measurement was received.

For ordinary onboarding meters, creation requests an immediate first run and keeps recurring collection active. Source publication times, upload intervals and provider limits still apply; immediate collection cannot manufacture missing source data.

## If setup does not work

Provide Eniris with the connection name, account/site scope, time of the attempt and the exact error. Check source availability and access permissions before retrying. Share a source screenshot or sample without passwords or tokens.

## Access and costs

Costs are not established for this connector. Confirm provider access, export licences and any project charges with Eniris before activation.

[All connection setup guides](/en/Monitoring/Integrations/connections)


# Sun Rock CSV setup


import ClickableImage from '@site/src/components/ClickableImage';

# Sun Rock CSV setup

Import Sunrock CSV files from the selected folder and installation scope.

<ClickableImage src="/img/eniris/monitoring/connection-guides/file-import.webp" alt="A data logger creating a structured file, transferring it securely and mapping its fields to a dashboard" maxWidth="1100px" />

*File onboarding is complete only after the source export, secure delivery, field mapping and recurring arrival have all been checked.*

Connection type: **File import**.

## What to provide

Provide your company and contact person, the intended Insights account, the source identifiers and explicit permission for the requested scope. Include a recent source example for verification.

| Information / setting | What is needed | Supplied or configured by |
| --- | --- | --- |
| File delivery source (BROWSER) | Agree the source location and transport; Eniris configures access without putting credentials in public URLs. | Eniris with installer |
| File / folder location (FOLDER) | Agree the delivery folder and file layout. Eniris makes it accessible to the collection service; a path on the customer laptop is insufficient. | Eniris with installer |
| Time zone (TIMEZONE) | Time zone of the source timestamps, for example Europe/Brussels; identify any files already using UTC. | Customer / installer |
| Installation scope (INSTALLATION_ID_ALLOW_LIST) | Exact installation IDs or numbers to include. Agree explicitly before including every installation. | Customer / installer |

## Set up the connection

1. Identify the source logger or export system and supply an original sample file. Confirm model, firmware, format and time zone with Eniris.
2. Agree the delivery route. For an Eniris FTP destination, request dedicated server, protocol, port, username, password and folder settings from Eniris. Use the agreed protocol exactly.
3. The installer or source owner enables recurring delivery. Eniris configures the accessible source location and device/field mappings; creating a meter does not configure the remote source.
4. Send a test file and record its timestamp. Eniris verifies arrival before starting collection, then compares the processed measurements with the original file.

### Configure the datalogger

The installer configures export on the datalogger using FTP credentials supplied by Eniris. Follow the [Datalogger CSV and FTP setup](https://docs.eniris.com/en/Monitoring/Integrations/datalogger-ftp) for preparation, model-specific options where documented, and the test upload. Eniris must confirm the exact model and export format for this connector.

## Check the result

Check that the first collection completed, then open the intended Insights account and verify the relevant measurements or metadata. Compare source IDs, timestamps and units with the original source. Check the next scheduled execution as well. An active schedule or a healthy job alone does not prove that every requested measurement was received.

For ordinary onboarding meters, creation requests an immediate first run and keeps recurring collection active. Source publication times, upload intervals and provider limits still apply; immediate collection cannot manufacture missing source data.

## If setup does not work

If no file arrives, inspect the logger/export status, destination, authentication, network route and folder. If files arrive but no measurements appear, provide the filename, format, source identifiers and timestamp so Eniris can check parsing and mapping.

## Access and costs

Costs are not established for this connector. Confirm provider access, export licences and any project charges with Eniris before activation.

[All connection setup guides](/en/Monitoring/Integrations/connections)


# Sungrow ISolar Cloud portal connection setup


import ClickableImage from '@site/src/components/ClickableImage';

# Sungrow ISolar Cloud portal connection setup

Read measurements available through the authorised Sungrow ISolar Cloud portal connection monitoring account. Only installations visible to that account can be collected.

<ClickableImage src="/img/eniris/monitoring/connection-guides/portal-access.webp" alt="A privacy-safe portal setup flow with sign-in, multi-factor authentication, installation selection and monitoring" maxWidth="1100px" />

*Confirm portal access, select only the agreed installations and complete any approval or multi-factor step before validating the data.*

Connection type: **Portal connection**.

## What to provide

Provide your company and contact person, the intended Insights account, the source identifiers and explicit permission for the requested scope. Include a recent source example for verification.

| Information / setting | What is needed | Supplied or configured by |
| --- | --- | --- |
| Account username (USERNAME) | Account name with access to the requested data. | Customer / installer |
| Account password (PASSWORD) | Share the source-account password through the secure channel agreed with Eniris. | Customer / installer |
| Installation scope (INSTALLATION_ID_ALLOW_LIST) | Exact installation IDs or numbers to include. Agree explicitly before including every installation. | Customer / installer |
| Time zone (TIMEZONE) | Time zone of the source timestamps, for example Europe/Brussels; identify any files already using UTC. | Customer / installer |

## Set up the connection

1. The customer signs in to the correct provider portal and checks that the requested installations and recent measurements are visible.
2. Grant the agreed account access and supply the required account details securely. Identify any login approval or multi-factor step so Eniris can complete the authorised connection.
3. Select this connector in onboarding, choose the intended Insights account and enter the fields in the table. Restrict installation scope to the agreed list where supported.
4. Create the connection and inspect the first retrieval. A successful manual portal login does not itself prove that the collection service can read data.

## Check the result

Check that the first collection completed, then open the intended Insights account and verify the relevant measurements or metadata. Compare source IDs, timestamps and units with the original source. Check the next scheduled execution as well. An active schedule or a healthy job alone does not prove that every requested measurement was received.

For ordinary onboarding meters, creation requests an immediate first run and keeps recurring collection active. Source publication times, upload intervals and provider limits still apply; immediate collection cannot manufacture missing source data.

## If setup does not work

Provide Eniris with the connection name, account/site scope, time of the attempt and the exact error. Check source availability and access permissions before retrying. Share a source screenshot or sample without passwords or tokens.

## Access and costs

Onboarding classifies this portal connection as free. This label does not establish the terms of a separate provider subscription or equipment licence.

[All connection setup guides](/en/Monitoring/Integrations/connections)


# Sungrow XML setup


import ClickableImage from '@site/src/components/ClickableImage';

# Sungrow XML setup

Import the supported Sungrow XML export format from an agreed delivery source.

<ClickableImage src="/img/eniris/monitoring/connection-guides/file-import.webp" alt="A data logger creating a structured file, transferring it securely and mapping its fields to a dashboard" maxWidth="1100px" />

*File onboarding is complete only after the source export, secure delivery, field mapping and recurring arrival have all been checked.*

Connection type: **File import**.

## What to provide

Provide your company and contact person, the intended Insights account, the source identifiers and explicit permission for the requested scope. Include a recent source example for verification.

| Information / setting | What is needed | Supplied or configured by |
| --- | --- | --- |
| File delivery source (BROWSER) | Agree the source location and transport; Eniris configures access without putting credentials in public URLs. | Eniris with installer |
| Time zone (TIMEZONE) | Time zone of the source timestamps, for example Europe/Brussels; identify any files already using UTC. | Customer / installer |

## Set up the connection

1. Identify the source logger or export system and supply an original sample file. Confirm model, firmware, format and time zone with Eniris.
2. Agree the delivery route. For an Eniris FTP destination, request dedicated server, protocol, port, username, password and folder settings from Eniris. Use the agreed protocol exactly.
3. The installer or source owner enables recurring delivery. Eniris configures the accessible source location and device/field mappings; creating a meter does not configure the remote source.
4. Send a test file and record its timestamp. Eniris verifies arrival before starting collection, then compares the processed measurements with the original file.

## Check the result

Check that the first collection completed, then open the intended Insights account and verify the relevant measurements or metadata. Compare source IDs, timestamps and units with the original source. Check the next scheduled execution as well. An active schedule or a healthy job alone does not prove that every requested measurement was received.

For ordinary onboarding meters, creation requests an immediate first run and keeps recurring collection active. Source publication times, upload intervals and provider limits still apply; immediate collection cannot manufacture missing source data.

## If setup does not work

If no file arrives, inspect the logger/export status, destination, authentication, network route and folder. If files arrive but no measurements appear, provide the filename, format, source identifiers and timestamp so Eniris can check parsing and mapping.

## Access and costs

Costs are not established for this connector. Confirm provider access, export licences and any project charges with Eniris before activation.

[All connection setup guides](/en/Monitoring/Integrations/connections)


# Swiss Grid Price setup


import ClickableImage from '@site/src/components/ClickableImage';

# Swiss Grid Price setup

Provide the shared Swiss grid-price collection implementation. Use a provider-specific CKW, EKZ or Groupe E connector for a new feed unless Eniris has configured a dedicated provider.

<ClickableImage src="/img/eniris/monitoring/connection-guides/market-grid-data.webp" alt="A market area, date range, resolution and units feeding electricity price and grid charts" maxWidth="1100px" />

*Market and grid data must be scoped by area, product, time range, resolution, currency and units before the first comparison.*

Connection type: **Prices and grid data**.

## What to provide

Provide your company and contact person, the intended Insights account, the source identifiers and explicit permission for the requested scope. Include a recent source example for verification.

This connector exposes no standard customer input fields. Eniris must check the configured source, supported scope and any deployment-specific access before activation. An empty form does not mean every source or device is supported.

## Set up the connection

1. Contact Eniris with the intended source, required output and time range. This specialised connector requires an operator review before use.
2. Eniris checks the configured source, access and scope in the deployed implementation. The standard onboarding form cannot configure all of these details.
3. The operator agrees a limited first run and verifies its output against the original source before enabling further processing.

## Check the result

Check that the first collection completed, then open the intended Insights account and verify the relevant measurements or metadata. Compare source IDs, timestamps and units with the original source. Check the next scheduled execution as well. An active schedule or a healthy job alone does not prove that every requested measurement was received.

For ordinary onboarding meters, creation requests an immediate first run and keeps recurring collection active. Source publication times, upload intervals and provider limits still apply; immediate collection cannot manufacture missing source data.

## If setup does not work

Provide Eniris with the connection name, account/site scope, time of the attempt and the exact error. Check source availability and access permissions before retrying. Share a source screenshot or sample without passwords or tokens.

## Access and costs

Costs are not established for this connector. Confirm provider access, export licences and any project charges with Eniris before activation.

[All connection setup guides](/en/Monitoring/Integrations/connections)


# Swiss PVTarif API setup


import ClickableImage from '@site/src/components/ClickableImage';

# Swiss PVTarif API setup

Collect Swiss PVTarif market or grid-reference data. Agree the market area, product, units, currency and publication period before using the values in reports.

<ClickableImage src="/img/eniris/monitoring/connection-guides/market-grid-data.webp" alt="A market area, date range, resolution and units feeding electricity price and grid charts" maxWidth="1100px" />

*Market and grid data must be scoped by area, product, time range, resolution, currency and units before the first comparison.*

Connection type: **Prices and grid data**.

## What to provide

Provide your company and contact person, the intended Insights account, the source identifiers and explicit permission for the requested scope. Include a recent source example for verification.

| Information / setting | What is needed | Supplied or configured by |
| --- | --- | --- |
| API key (API_KEY) | Obtain the key from the source account owner or provider; confirm its data permissions and share it securely. | Customer / installer |
| Area / operator mapping (OPERATOR_MAP) | Match source operator or market-area identifiers to the required output labels. | Eniris with customer |

## Set up the connection

1. Agree market areas, price product or grid dataset, resolution, currency, units and publication date. Distinguish prices from physical meter readings.
2. Obtain the required provider access shown in the table and confirm the permitted dataset. Supply secrets securely.
3. Enter the exposed scope and mapping settings, if any. Eniris verifies fixed source coverage where the form offers no selector.
4. Compare the first collected period with the original source, including timestamps, time zone, units and missing intervals.

## Check the result

Check that the first collection completed, then open the intended Insights account and verify the relevant measurements or metadata. Compare source IDs, timestamps and units with the original source. Check the next scheduled execution as well. An active schedule or a healthy job alone does not prove that every requested measurement was received.

For ordinary onboarding meters, creation requests an immediate first run and keeps recurring collection active. Source publication times, upload intervals and provider limits still apply; immediate collection cannot manufacture missing source data.

## If setup does not work

Provide Eniris with the connection name, account/site scope, time of the attempt and the exact error. Check source availability and access permissions before retrying. Share a source screenshot or sample without passwords or tokens.

## Access and costs

Costs are not established for this connector. Confirm provider access, export licences and any project charges with Eniris before activation.

[All connection setup guides](/en/Monitoring/Integrations/connections)


# Synapti QFtp Push setup


import ClickableImage from '@site/src/components/ClickableImage';

# Synapti QFtp Push setup

Push authorised Insights measurements to SynaptiQ files, with configured asset selection, tags and sampling.

<ClickableImage src="/img/eniris/monitoring/connection-guides/outgoing-export.webp" alt="Authorized monitoring measurements being mapped, encrypted and delivered to a receiving system" maxWidth="1100px" />

*Agree the exact measurement scope and file layout, then verify both delivery and interpretation with the receiving platform.*

Connection type: **Outgoing data export**.

## What to provide

Provide your company and contact person, the intended Insights account, the source identifiers and explicit permission for the requested scope. Include a recent source example for verification.

| Information / setting | What is needed | Supplied or configured by |
| --- | --- | --- |
| File delivery source (BROWSER) | Agree the source location and transport; Eniris configures access without putting credentials in public URLs. | Eniris with installer |
| Assets to export (ROOT_NODE_IDS) | Explicit Insights asset scope approved for delivery to the destination. | Customer / installer |
| Export mapping (USE_CUSTOM_ADDRESS) | Agree destination signal names, tags and asset-address rules. | Eniris with receiving platform |
| Export timing (INTERPOLATION_INTERVAL_S) | Sampling and interpolation intervals in seconds, agreed for the receiving platform. | Eniris with receiving platform |
| Export timing (SAMPLE_INTERVAL_S) | Sampling and interpolation intervals in seconds, agreed for the receiving platform. | Eniris with receiving platform |
| Export mapping (TAG_CONFIGURATIONS) | Agree destination signal names, tags and asset-address rules. | Eniris with receiving platform |
| Export mapping (CUSTOM_NAME_CONDITIONS) | Agree destination signal names, tags and asset-address rules. | Eniris with receiving platform |

## Set up the connection

1. Agree with the receiving platform which Insights assets and measurements may be exported, the file layout and the delivery interval.
2. Obtain destination credentials from the receiving platform. Eniris separately configures authorised Insights access. These are two different accounts.
3. Eniris enters the destination and mapping, reviews the scope and starts the first export. No datalogger needs to push into Eniris for this route.
4. Ask the receiving platform to confirm both the file arrival and the interpreted measurements; compare timestamps, units and asset identifiers.

## Check the result

Confirm delivery and parsed data with the receiving platform. Compare source IDs, timestamps and units with the original source. Check the next scheduled execution as well. An active schedule or a healthy job alone does not prove that every requested measurement was received.

For ordinary onboarding meters, creation requests an immediate first run and keeps recurring collection active. Source publication times, upload intervals and provider limits still apply; immediate collection cannot manufacture missing source data.

## If setup does not work

Provide Eniris with the connection name, account/site scope, time of the attempt and the exact error. Check source availability and access permissions before retrying. Share a source screenshot or sample without passwords or tokens.

## Access and costs

Costs are not established for this connector. Confirm provider access, export licences and any project charges with Eniris before activation.

[All connection setup guides](/en/Monitoring/Integrations/connections)


# System Metrics setup


import ClickableImage from '@site/src/components/ClickableImage';

# System Metrics setup

Process internal system-metric files using the configured device and metadata mapping.

<ClickableImage src="/img/eniris/monitoring/connection-guides/workflow-automation.webp" alt="A scheduled workflow with access control, transformation, validation, execution and an audit trail" maxWidth="1100px" />

*An automation should have a defined trigger, restricted access, validation, observable execution and a usable audit trail.*

Connection type: **Internal automation**.

## What to provide

Name the responsible Eniris operator, the approved scope and the expected outcome. Configuration and service credentials stay with the internal operator.

## Set up the connection

1. Ask the Eniris owner of this automation to agree its purpose, affected records/accounts and expected changes. This entry is not a customer meter connection.
2. The Eniris operator configures the required service access and scopes. Do not request internal administrator credentials from the customer.
3. Review a bounded test scope and its expected outcome before activation. For messaging, permission, merging or CRM workflows, the first run may change records or send messages.
4. Verify the intended action in the destination system and check for unintended changes before allowing the recurring schedule.

## Check the result

Verify the expected records or actions in the target system and the execution status. A meter dashboard may not apply. Review the effects of the first run before continuing a recurring automation.

## If setup does not work

Contact the responsible Eniris operator with the job reference, expected action and observed result. Avoid repeating a write or send action without checking whether it already happened.

[All connection setup guides](/en/Monitoring/Integrations/connections)


# Tennet portal connection setup


import ClickableImage from '@site/src/components/ClickableImage';

# Tennet portal connection setup

Collect Tennet portal connection market or grid-reference data. Agree the market area, product, units, currency and publication period before using the values in reports.

<ClickableImage src="/img/eniris/monitoring/connection-guides/market-grid-data.webp" alt="A market area, date range, resolution and units feeding electricity price and grid charts" maxWidth="1100px" />

*Market and grid data must be scoped by area, product, time range, resolution, currency and units before the first comparison.*

Connection type: **Prices and grid data**.

## What to provide

Provide your company and contact person, the intended Insights account, the source identifiers and explicit permission for the requested scope. Include a recent source example for verification.

This connector exposes no standard customer input fields. Eniris must check the configured source, supported scope and any deployment-specific access before activation. An empty form does not mean every source or device is supported.

## Set up the connection

1. Agree market areas, price product or grid dataset, resolution, currency, units and publication date. Distinguish prices from physical meter readings.
2. Eniris checks the configured source and coverage. No customer password is requested by this connector’s current form; that does not guarantee unrestricted source access.
3. Enter the exposed scope and mapping settings, if any. Eniris verifies fixed source coverage where the form offers no selector.
4. Compare the first collected period with the original source, including timestamps, time zone, units and missing intervals.

## Check the result

Check that the first collection completed, then open the intended Insights account and verify the relevant measurements or metadata. Compare source IDs, timestamps and units with the original source. Check the next scheduled execution as well. An active schedule or a healthy job alone does not prove that every requested measurement was received.

For ordinary onboarding meters, creation requests an immediate first run and keeps recurring collection active. Source publication times, upload intervals and provider limits still apply; immediate collection cannot manufacture missing source data.

## If setup does not work

Provide Eniris with the connection name, account/site scope, time of the attempt and the exact error. Check source availability and access permissions before retrying. Share a source screenshot or sample without passwords or tokens.

## Access and costs

Onboarding classifies this portal connection as free. This label does not establish the terms of a separate provider subscription or equipment licence.

[All connection setup guides](/en/Monitoring/Integrations/connections)


# Toolbox Alarms setup


import ClickableImage from '@site/src/components/ClickableImage';

# Toolbox Alarms setup

Process internal Toolbox alarm information.

<ClickableImage src="/img/eniris/monitoring/connection-guides/workflow-automation.webp" alt="A scheduled workflow with access control, transformation, validation, execution and an audit trail" maxWidth="1100px" />

*An automation should have a defined trigger, restricted access, validation, observable execution and a usable audit trail.*

Connection type: **Internal automation**.

## What to provide

Name the responsible Eniris operator, the approved scope and the expected outcome. Configuration and service credentials stay with the internal operator.

## Set up the connection

1. Ask the Eniris owner of this automation to agree its purpose, affected records/accounts and expected changes. This entry is not a customer meter connection.
2. The Eniris operator configures the required service access and scopes. Do not request internal administrator credentials from the customer.
3. Review a bounded test scope and its expected outcome before activation. For messaging, permission, merging or CRM workflows, the first run may change records or send messages.
4. Verify the intended action in the destination system and check for unintended changes before allowing the recurring schedule.

## Check the result

Verify the expected records or actions in the target system and the execution status. A meter dashboard may not apply. Review the effects of the first run before continuing a recurring automation.

## If setup does not work

Contact the responsible Eniris operator with the job reference, expected action and observed result. Avoid repeating a write or send action without checking whether it already happened.

[All connection setup guides](/en/Monitoring/Integrations/connections)


# Toolbox Insights Sync setup


import ClickableImage from '@site/src/components/ClickableImage';

# Toolbox Insights Sync setup

Synchronise internal Toolbox and Insights information.

<ClickableImage src="/img/eniris/monitoring/connection-guides/workflow-automation.webp" alt="A scheduled workflow with access control, transformation, validation, execution and an audit trail" maxWidth="1100px" />

*An automation should have a defined trigger, restricted access, validation, observable execution and a usable audit trail.*

Connection type: **Internal automation**.

## What to provide

Name the responsible Eniris operator, the approved scope and the expected outcome. Configuration and service credentials stay with the internal operator.

## Set up the connection

1. Ask the Eniris owner of this automation to agree its purpose, affected records/accounts and expected changes. This entry is not a customer meter connection.
2. The Eniris operator configures the required service access and scopes. Do not request internal administrator credentials from the customer.
3. Review a bounded test scope and its expected outcome before activation. For messaging, permission, merging or CRM workflows, the first run may change records or send messages.
4. Verify the intended action in the destination system and check for unintended changes before allowing the recurring schedule.

## Check the result

Verify the expected records or actions in the target system and the execution status. A meter dashboard may not apply. Review the effects of the first run before continuing a recurring automation.

## If setup does not work

Contact the responsible Eniris operator with the job reference, expected action and observed result. Avoid repeating a write or send action without checking whether it already happened.

[All connection setup guides](/en/Monitoring/Integrations/connections)


# Toolbox Revenue setup


import ClickableImage from '@site/src/components/ClickableImage';

# Toolbox Revenue setup

Process internal Toolbox revenue information.

<ClickableImage src="/img/eniris/monitoring/connection-guides/workflow-automation.webp" alt="A scheduled workflow with access control, transformation, validation, execution and an audit trail" maxWidth="1100px" />

*An automation should have a defined trigger, restricted access, validation, observable execution and a usable audit trail.*

Connection type: **Internal automation**.

## What to provide

Name the responsible Eniris operator, the approved scope and the expected outcome. Configuration and service credentials stay with the internal operator.

## Set up the connection

1. Ask the Eniris owner of this automation to agree its purpose, affected records/accounts and expected changes. This entry is not a customer meter connection.
2. The Eniris operator configures the required service access and scopes. Do not request internal administrator credentials from the customer.
3. Review a bounded test scope and its expected outcome before activation. For messaging, permission, merging or CRM workflows, the first run may change records or send messages.
4. Verify the intended action in the destination system and check for unintended changes before allowing the recurring schedule.

## Check the result

Verify the expected records or actions in the target system and the execution status. A meter dashboard may not apply. Review the effects of the first run before continuing a recurring automation.

## If setup does not work

Contact the responsible Eniris operator with the job reference, expected action and observed result. Avoid repeating a write or send action without checking whether it already happened.

[All connection setup guides](/en/Monitoring/Integrations/connections)


# Two Wire CSV setup


import ClickableImage from '@site/src/components/ClickableImage';

# Two Wire CSV setup

Import the supported Two Wire CSV file format. The source must deliver files in the format expected by this connector; renaming another file to CSV does not convert it.

<ClickableImage src="/img/eniris/monitoring/connection-guides/file-import.webp" alt="A data logger creating a structured file, transferring it securely and mapping its fields to a dashboard" maxWidth="1100px" />

*File onboarding is complete only after the source export, secure delivery, field mapping and recurring arrival have all been checked.*

Connection type: **File import**.

## What to provide

Provide your company and contact person, the intended Insights account, the source identifiers and explicit permission for the requested scope. Include a recent source example for verification.

| Information / setting | What is needed | Supplied or configured by |
| --- | --- | --- |
| File / folder location (CSV_FOLDER) | Agree the delivery folder and file layout. Eniris makes it accessible to the collection service; a path on the customer laptop is insufficient. | Eniris with installer |
| Time zone (TIMEZONE) | Time zone of the source timestamps, for example Europe/Brussels; identify any files already using UTC. | Customer / installer |

## Set up the connection

1. Identify the source logger or export system and supply an original sample file. Confirm model, firmware, format and time zone with Eniris.
2. Agree the delivery route. For an Eniris FTP destination, request dedicated server, protocol, port, username, password and folder settings from Eniris. Use the agreed protocol exactly.
3. The installer or source owner enables recurring delivery. Eniris configures the accessible source location and device/field mappings; creating a meter does not configure the remote source.
4. Send a test file and record its timestamp. Eniris verifies arrival before starting collection, then compares the processed measurements with the original file.

### Configure the datalogger

The installer configures export on the datalogger using FTP credentials supplied by Eniris. Follow the [Datalogger CSV and FTP setup](https://docs.eniris.com/en/Monitoring/Integrations/datalogger-ftp) for preparation, model-specific options where documented, and the test upload. Eniris must confirm the exact model and export format for this connector.

## Check the result

Check that the first collection completed, then open the intended Insights account and verify the relevant measurements or metadata. Compare source IDs, timestamps and units with the original source. Check the next scheduled execution as well. An active schedule or a healthy job alone does not prove that every requested measurement was received.

For ordinary onboarding meters, creation requests an immediate first run and keeps recurring collection active. Source publication times, upload intervals and provider limits still apply; immediate collection cannot manufacture missing source data.

## If setup does not work

If no file arrives, inspect the logger/export status, destination, authentication, network route and folder. If files arrive but no measurements appear, provide the filename, format, source identifiers and timestamp so Eniris can check parsing and mapping.

## Access and costs

Costs are not established for this connector. Confirm provider access, export licences and any project charges with Eniris before activation.

[All connection setup guides](/en/Monitoring/Integrations/connections)


# Uptime Kuma setup


import ClickableImage from '@site/src/components/ClickableImage';

# Uptime Kuma setup

Evaluate configured country-scoped monitoring information for the internal uptime workflow.

<ClickableImage src="/img/eniris/monitoring/connection-guides/workflow-automation.webp" alt="A scheduled workflow with access control, transformation, validation, execution and an audit trail" maxWidth="1100px" />

*An automation should have a defined trigger, restricted access, validation, observable execution and a usable audit trail.*

Connection type: **Internal automation**.

## What to provide

Name the responsible Eniris operator, the approved scope and the expected outcome. Configuration and service credentials stay with the internal operator.

## Set up the connection

1. Ask the Eniris owner of this automation to agree its purpose, affected records/accounts and expected changes. This entry is not a customer meter connection.
2. The Eniris operator configures the required service access and scopes. Do not request internal administrator credentials from the customer.
3. Review a bounded test scope and its expected outcome before activation. For messaging, permission, merging or CRM workflows, the first run may change records or send messages.
4. Verify the intended action in the destination system and check for unintended changes before allowing the recurring schedule.

## Check the result

Verify the expected records or actions in the target system and the execution status. A meter dashboard may not apply. Review the effects of the first run before continuing a recurring automation.

## If setup does not work

Contact the responsible Eniris operator with the job reference, expected action and observed result. Avoid repeating a write or send action without checking whether it already happened.

[All connection setup guides](/en/Monitoring/Integrations/connections)


# Vensys API setup


import ClickableImage from '@site/src/components/ClickableImage';

# Vensys API setup

Read Vensys data using the provider access configured for this connector. Confirm account permissions, installation scope and the requested measurements before activation.

<ClickableImage src="/img/eniris/monitoring/connection-guides/api-authorization.webp" alt="A privacy-safe API setup flow with authorization, limited installation scope, validation and a monitoring dashboard" maxWidth="1100px" />

*A reliable API connection combines the correct authorization method, an explicitly limited installation scope and a verified first retrieval.*

Connection type: **API and platform connection**.

## Before you start

The connector identifies turbines using numeric TIDs. Ask the account owner for the API key and the corresponding turbine list from their Vensys API access page.

## What to provide

Provide your company and contact person, the intended Insights account, the source identifiers and explicit permission for the requested scope. Include a recent source example for verification.

| Information / setting | What is needed | Supplied or configured by |
| --- | --- | --- |
| API key (APIKEY) | Obtain the key from the source account owner or provider; confirm its data permissions and share it securely. | Customer / installer |
| Turbine scope (TID_LIST) | Turbine identifiers and the explicit list to include or exclude. | Customer / installer |

## Set up the connection

1. Ask the provider or account owner to enable the data access required by this connector. Confirm the permitted sites/devices and requested API version.
2. Supply the exact credential types in the table through the agreed secure channel. A portal password, API token, application secret and OAuth grant are not interchangeable.
3. Choose this connector and the target Insights account in onboarding. Enter the required fields and the authorised installation scope, then review before creating.
4. Check the first retrieval against the source account. If access succeeds but no data appears, verify site permissions, API entitlements, identifiers and the availability of measurements.

## Check the result

Check that the first collection completed, then open the intended Insights account and verify the relevant measurements or metadata. Compare source IDs, timestamps and units with the original source. Check the next scheduled execution as well. An active schedule or a healthy job alone does not prove that every requested measurement was received.

For ordinary onboarding meters, creation requests an immediate first run and keeps recurring collection active. Source publication times, upload intervals and provider limits still apply; immediate collection cannot manufacture missing source data.

## If setup does not work

Provide Eniris with the connection name, account/site scope, time of the attempt and the exact error. Check source availability and access permissions before retrying. Share a source screenshot or sample without passwords or tokens.

## Access and costs

Costs are not established for this connector. Confirm provider access, export licences and any project charges with Eniris before activation.

[All connection setup guides](/en/Monitoring/Integrations/connections)


# Vlaamsenutsregulator portal connection setup


import ClickableImage from '@site/src/components/ClickableImage';

# Vlaamsenutsregulator portal connection setup

Collect Vlaamsenutsregulator portal connection market or grid-reference data. Agree the market area, product, units, currency and publication period before using the values in reports.

<ClickableImage src="/img/eniris/monitoring/connection-guides/market-grid-data.webp" alt="A market area, date range, resolution and units feeding electricity price and grid charts" maxWidth="1100px" />

*Market and grid data must be scoped by area, product, time range, resolution, currency and units before the first comparison.*

Connection type: **Prices and grid data**.

## What to provide

Provide your company and contact person, the intended Insights account, the source identifiers and explicit permission for the requested scope. Include a recent source example for verification.

This connector exposes no standard customer input fields. Eniris must check the configured source, supported scope and any deployment-specific access before activation. An empty form does not mean every source or device is supported.

## Set up the connection

1. Agree market areas, price product or grid dataset, resolution, currency, units and publication date. Distinguish prices from physical meter readings.
2. Eniris checks the configured source and coverage. No customer password is requested by this connector’s current form; that does not guarantee unrestricted source access.
3. Enter the exposed scope and mapping settings, if any. Eniris verifies fixed source coverage where the form offers no selector.
4. Compare the first collected period with the original source, including timestamps, time zone, units and missing intervals.

## Check the result

Check that the first collection completed, then open the intended Insights account and verify the relevant measurements or metadata. Compare source IDs, timestamps and units with the original source. Check the next scheduled execution as well. An active schedule or a healthy job alone does not prove that every requested measurement was received.

For ordinary onboarding meters, creation requests an immediate first run and keeps recurring collection active. Source publication times, upload intervals and provider limits still apply; immediate collection cannot manufacture missing source data.

## If setup does not work

Provide Eniris with the connection name, account/site scope, time of the attempt and the exact error. Check source availability and access permissions before retrying. Share a source screenshot or sample without passwords or tokens.

## Access and costs

Onboarding classifies this portal connection as free. This label does not establish the terms of a separate provider subscription or equipment licence.

[All connection setup guides](/en/Monitoring/Integrations/connections)


# Webdyn Sun setup


import ClickableImage from '@site/src/components/ClickableImage';

# Webdyn Sun setup

Import WebdynSun data and device-definition files from a folder accessible to the collection service.

<ClickableImage src="/img/eniris/monitoring/connection-guides/file-import.webp" alt="A data logger creating a structured file, transferring it securely and mapping its fields to a dashboard" maxWidth="1100px" />

*File onboarding is complete only after the source export, secure delivery, field mapping and recurring arrival have all been checked.*

Connection type: **File import**.

## What to provide

Provide your company and contact person, the intended Insights account, the source identifiers and explicit permission for the requested scope. Include a recent source example for verification.

| Information / setting | What is needed | Supplied or configured by |
| --- | --- | --- |
| File / folder location (FTP_FOLDER) | Agree the delivery folder and file layout. Eniris makes it accessible to the collection service; a path on the customer laptop is insufficient. | Eniris with installer |

## Set up the connection

1. Identify the source logger or export system and supply an original sample file. Confirm model, firmware, format and time zone with Eniris.
2. Agree the delivery route. For an Eniris FTP destination, request dedicated server, protocol, port, username, password and folder settings from Eniris. Use the agreed protocol exactly.
3. The installer or source owner enables recurring delivery. Eniris configures the accessible source location and device/field mappings; creating a meter does not configure the remote source.
4. Send a test file and record its timestamp. Eniris verifies arrival before starting collection, then compares the processed measurements with the original file.

For gateway configuration, see [WebdynSun FTP setup](/en/Monitoring/Integrations/datalogger-ftp/webdynsun). Eniris must also confirm the file/definition layout for this particular parser.

## Check the result

Check that the first collection completed, then open the intended Insights account and verify the relevant measurements or metadata. Compare source IDs, timestamps and units with the original source. Check the next scheduled execution as well. An active schedule or a healthy job alone does not prove that every requested measurement was received.

For ordinary onboarding meters, creation requests an immediate first run and keeps recurring collection active. Source publication times, upload intervals and provider limits still apply; immediate collection cannot manufacture missing source data.

## If setup does not work

If no file arrives, inspect the logger/export status, destination, authentication, network route and folder. If files arrive but no measurements appear, provide the filename, format, source identifiers and timestamp so Eniris can check parsing and mapping.

## Access and costs

Costs are not established for this connector. Confirm provider access, export licences and any project charges with Eniris before activation.

[All connection setup guides](/en/Monitoring/Integrations/connections)


# Webdynsun CSV setup


import ClickableImage from '@site/src/components/ClickableImage';

# Webdynsun CSV setup

Import the supported Webdynsun CSV file format. The source must deliver files in the format expected by this connector; renaming another file to CSV does not convert it.

<ClickableImage src="/img/eniris/monitoring/connection-guides/file-import.webp" alt="A data logger creating a structured file, transferring it securely and mapping its fields to a dashboard" maxWidth="1100px" />

*File onboarding is complete only after the source export, secure delivery, field mapping and recurring arrival have all been checked.*

Connection type: **File import**.

## What to provide

Provide your company and contact person, the intended Insights account, the source identifiers and explicit permission for the requested scope. Include a recent source example for verification.

| Information / setting | What is needed | Supplied or configured by |
| --- | --- | --- |
| File delivery source (BROWSER) | Agree the source location and transport; Eniris configures access without putting credentials in public URLs. | Eniris with installer |
| Time zone (TIMEZONE) | Time zone of the source timestamps, for example Europe/Brussels; identify any files already using UTC. | Customer / installer |

## Set up the connection

1. Identify the source logger or export system and supply an original sample file. Confirm model, firmware, format and time zone with Eniris.
2. Agree the delivery route. For an Eniris FTP destination, request dedicated server, protocol, port, username, password and folder settings from Eniris. Use the agreed protocol exactly.
3. The installer or source owner enables recurring delivery. Eniris configures the accessible source location and device/field mappings; creating a meter does not configure the remote source.
4. Send a test file and record its timestamp. Eniris verifies arrival before starting collection, then compares the processed measurements with the original file.

### Configure the datalogger

The installer configures export on the datalogger using FTP credentials supplied by Eniris. Follow the [WebdynSun FTP setup](https://docs.eniris.com/en/Monitoring/Integrations/datalogger-ftp/webdynsun) for preparation, model-specific options where documented, and the test upload. Eniris must confirm the exact model and export format for this connector.

## Check the result

Check that the first collection completed, then open the intended Insights account and verify the relevant measurements or metadata. Compare source IDs, timestamps and units with the original source. Check the next scheduled execution as well. An active schedule or a healthy job alone does not prove that every requested measurement was received.

For ordinary onboarding meters, creation requests an immediate first run and keeps recurring collection active. Source publication times, upload intervals and provider limits still apply; immediate collection cannot manufacture missing source data.

## If setup does not work

If no file arrives, inspect the logger/export status, destination, authentication, network route and folder. If files arrive but no measurements appear, provide the filename, format, source identifiers and timestamp so Eniris can check parsing and mapping.

## Access and costs

Costs are not established for this connector. Confirm provider access, export licences and any project charges with Eniris before activation.

[All connection setup guides](/en/Monitoring/Integrations/connections)


# Webdynsun Manual setup


import ClickableImage from '@site/src/components/ClickableImage';

# Webdynsun Manual setup

Import the specialised WebdynSun compressed-file layout using the configured file source and optional request headers.

<ClickableImage src="/img/eniris/monitoring/connection-guides/file-import.webp" alt="A data logger creating a structured file, transferring it securely and mapping its fields to a dashboard" maxWidth="1100px" />

*File onboarding is complete only after the source export, secure delivery, field mapping and recurring arrival have all been checked.*

Connection type: **File import**.

## Before you start

The current parser uses Europe/Brussels for file times. Tell Eniris if the source uses a different time zone before collecting data.

## What to provide

Provide your company and contact person, the intended Insights account, the source identifiers and explicit permission for the requested scope. Include a recent source example for verification.

| Information / setting | What is needed | Supplied or configured by |
| --- | --- | --- |
| File delivery source (BROWSER) | Agree the source location and transport; Eniris configures access without putting credentials in public URLs. | Eniris with installer |
| File-source request headers (HEADERS) | Any access headers required by the delivery source. Share authentication values securely. | Eniris with source owner |

## Set up the connection

1. Identify the source logger or export system and supply an original sample file. Confirm model, firmware, format and time zone with Eniris.
2. Agree the delivery route. For an Eniris FTP destination, request dedicated server, protocol, port, username, password and folder settings from Eniris. Use the agreed protocol exactly.
3. The installer or source owner enables recurring delivery. Eniris configures the accessible source location and device/field mappings; creating a meter does not configure the remote source.
4. Send a test file and record its timestamp. Eniris verifies arrival before starting collection, then compares the processed measurements with the original file.

For gateway configuration, see [WebdynSun FTP setup](/en/Monitoring/Integrations/datalogger-ftp/webdynsun). Eniris must also confirm the file/definition layout for this particular parser.

## Check the result

Check that the first collection completed, then open the intended Insights account and verify the relevant measurements or metadata. Compare source IDs, timestamps and units with the original source. Check the next scheduled execution as well. An active schedule or a healthy job alone does not prove that every requested measurement was received.

For ordinary onboarding meters, creation requests an immediate first run and keeps recurring collection active. Source publication times, upload intervals and provider limits still apply; immediate collection cannot manufacture missing source data.

## If setup does not work

If no file arrives, inspect the logger/export status, destination, authentication, network route and folder. If files arrive but no measurements appear, provide the filename, format, source identifiers and timestamp so Eniris can check parsing and mapping.

## Access and costs

Costs are not established for this connector. Confirm provider access, export licences and any project charges with Eniris before activation.

[All connection setup guides](/en/Monitoring/Integrations/connections)


# Windup API setup


import ClickableImage from '@site/src/components/ClickableImage';

# Windup API setup

Read Windup data using the provider access configured for this connector. Confirm account permissions, installation scope and the requested measurements before activation.

<ClickableImage src="/img/eniris/monitoring/connection-guides/api-authorization.webp" alt="A privacy-safe API setup flow with authorization, limited installation scope, validation and a monitoring dashboard" maxWidth="1100px" />

*A reliable API connection combines the correct authorization method, an explicitly limited installation scope and a verified first retrieval.*

Connection type: **API and platform connection**.

## Before you start

Confirm turbine scope explicitly. The parameter name TIDALLOWLIST and its historical description disagree about inclusion/exclusion; Eniris must verify the actual selection against a small known turbine list before enabling the full scope.

## What to provide

Provide your company and contact person, the intended Insights account, the source identifiers and explicit permission for the requested scope. Include a recent source example for verification.

| Information / setting | What is needed | Supplied or configured by |
| --- | --- | --- |
| Account username (USERNAME) | Account name with access to the requested data. | Customer / installer |
| Account password (PASSWORD) | Share the source-account password through the secure channel agreed with Eniris. | Customer / installer |
| Turbine scope (TIDALLOWLIST) | Turbine identifiers and the explicit list to include or exclude. | Customer / installer |

## Set up the connection

1. Ask the provider or account owner to enable the data access required by this connector. Confirm the permitted sites/devices and requested API version.
2. Supply the exact credential types in the table through the agreed secure channel. A portal password, API token, application secret and OAuth grant are not interchangeable.
3. Choose this connector and the target Insights account in onboarding. Enter the required fields and the authorised installation scope, then review before creating.
4. Check the first retrieval against the source account. If access succeeds but no data appears, verify site permissions, API entitlements, identifiers and the availability of measurements.

## Check the result

Check that the first collection completed, then open the intended Insights account and verify the relevant measurements or metadata. Compare source IDs, timestamps and units with the original source. Check the next scheduled execution as well. An active schedule or a healthy job alone does not prove that every requested measurement was received.

For ordinary onboarding meters, creation requests an immediate first run and keeps recurring collection active. Source publication times, upload intervals and provider limits still apply; immediate collection cannot manufacture missing source data.

## If setup does not work

Provide Eniris with the connection name, account/site scope, time of the attempt and the exact error. Check source availability and access permissions before retrying. Share a source screenshot or sample without passwords or tokens.

## Access and costs

Costs are not established for this connector. Confirm provider access, export licences and any project charges with Eniris before activation.

[All connection setup guides](/en/Monitoring/Integrations/connections)


# Youless setup


import ClickableImage from '@site/src/components/ClickableImage';

# Youless setup

Read local Youless measurements using its MAC address to resolve the device on the network.

<ClickableImage src="/img/eniris/monitoring/connection-guides/local-device.webp" alt="A meter and controller on a private network connected securely through a firewall to a monitoring dashboard" maxWidth="1100px" />

*Keep the device on the private site network and verify the supported endpoint, gateway route and secure outbound connection.*

Connection type: **Local devices**.

## What to provide

Provide your company and contact person, the intended Insights account, the source identifiers and explicit permission for the requested scope. Include a recent source example for verification.

| Information / setting | What is needed | Supplied or configured by |
| --- | --- | --- |
| Device MAC address (MAC_ADDRESS) | MAC address of the device; Eniris checks network discovery and reachability. | Customer / installer |

## Set up the connection

1. Give Eniris the device model, firmware, identity, network location and the measurements to collect.
2. Have the site installer enable the supported data interface. Eniris verifies the required network route from the collection service; reaching the device on a customer laptop is not sufficient.
3. Enter the endpoint or device identity shown below and agree the time zone and signal mapping. Do not expose the device publicly to work around routing.
4. Start the first collection and compare a recent value and timestamp against the device itself.

## Check the result

Check that the first collection completed, then open the intended Insights account and verify the relevant measurements or metadata. Compare source IDs, timestamps and units with the original source. Check the next scheduled execution as well. An active schedule or a healthy job alone does not prove that every requested measurement was received.

For ordinary onboarding meters, creation requests an immediate first run and keeps recurring collection active. Source publication times, upload intervals and provider limits still apply; immediate collection cannot manufacture missing source data.

## If setup does not work

Provide Eniris with the connection name, account/site scope, time of the attempt and the exact error. Check source availability and access permissions before retrying. Share a source screenshot or sample without passwords or tokens.

## Access and costs

Costs are not established for this connector. Confirm provider access, export licences and any project charges with Eniris before activation.

[All connection setup guides](/en/Monitoring/Integrations/connections)


# Zoho Add Country To Contacts setup


import ClickableImage from '@site/src/components/ClickableImage';

# Zoho Add Country To Contacts setup

Update country information on Zoho contacts.

<ClickableImage src="/img/eniris/monitoring/connection-guides/workflow-automation.webp" alt="A scheduled workflow with access control, transformation, validation, execution and an audit trail" maxWidth="1100px" />

*An automation should have a defined trigger, restricted access, validation, observable execution and a usable audit trail.*

Connection type: **Internal automation**.

## What to provide

Name the responsible Eniris operator, the approved scope and the expected outcome. Configuration and service credentials stay with the internal operator.

## Set up the connection

1. Ask the Eniris owner of this automation to agree its purpose, affected records/accounts and expected changes. This entry is not a customer meter connection.
2. The Eniris operator configures the required service access and scopes. Do not request internal administrator credentials from the customer.
3. Review a bounded test scope and its expected outcome before activation. For messaging, permission, merging or CRM workflows, the first run may change records or send messages.
4. Verify the intended action in the destination system and check for unintended changes before allowing the recurring schedule.

## Check the result

Verify the expected records or actions in the target system and the execution status. A meter dashboard may not apply. Review the effects of the first run before continuing a recurring automation.

## If setup does not work

Contact the responsible Eniris operator with the job reference, expected action and observed result. Avoid repeating a write or send action without checking whether it already happened.

[All connection setup guides](/en/Monitoring/Integrations/connections)


# Zoho Detect And Update Silent Lead Contacts setup


import ClickableImage from '@site/src/components/ClickableImage';

# Zoho Detect And Update Silent Lead Contacts setup

Identify and update Zoho lead contacts in the configured inactivity workflow.

<ClickableImage src="/img/eniris/monitoring/connection-guides/workflow-automation.webp" alt="A scheduled workflow with access control, transformation, validation, execution and an audit trail" maxWidth="1100px" />

*An automation should have a defined trigger, restricted access, validation, observable execution and a usable audit trail.*

Connection type: **Internal automation**.

## What to provide

Name the responsible Eniris operator, the approved scope and the expected outcome. Configuration and service credentials stay with the internal operator.

## Set up the connection

1. Ask the Eniris owner of this automation to agree its purpose, affected records/accounts and expected changes. This entry is not a customer meter connection.
2. The Eniris operator configures the required service access and scopes. Do not request internal administrator credentials from the customer.
3. Review a bounded test scope and its expected outcome before activation. For messaging, permission, merging or CRM workflows, the first run may change records or send messages.
4. Verify the intended action in the destination system and check for unintended changes before allowing the recurring schedule.

## Check the result

Verify the expected records or actions in the target system and the execution status. A meter dashboard may not apply. Review the effects of the first run before continuing a recurring automation.

## If setup does not work

Contact the responsible Eniris operator with the job reference, expected action and observed result. Avoid repeating a write or send action without checking whether it already happened.

[All connection setup guides](/en/Monitoring/Integrations/connections)


# Zoho Follow Up Mail setup


import ClickableImage from '@site/src/components/ClickableImage';

# Zoho Follow Up Mail setup

Run the configured Zoho follow-up email workflow. Execution may send messages.

<ClickableImage src="/img/eniris/monitoring/connection-guides/workflow-automation.webp" alt="A scheduled workflow with access control, transformation, validation, execution and an audit trail" maxWidth="1100px" />

*An automation should have a defined trigger, restricted access, validation, observable execution and a usable audit trail.*

Connection type: **Internal automation**.

## What to provide

Name the responsible Eniris operator, the approved scope and the expected outcome. Configuration and service credentials stay with the internal operator.

## Set up the connection

1. Ask the Eniris owner of this automation to agree its purpose, affected records/accounts and expected changes. This entry is not a customer meter connection.
2. The Eniris operator configures the required service access and scopes. Do not request internal administrator credentials from the customer.
3. Review a bounded test scope and its expected outcome before activation. For messaging, permission, merging or CRM workflows, the first run may change records or send messages.
4. Verify the intended action in the destination system and check for unintended changes before allowing the recurring schedule.

## Check the result

Verify the expected records or actions in the target system and the execution status. A meter dashboard may not apply. Review the effects of the first run before continuing a recurring automation.

## If setup does not work

Contact the responsible Eniris operator with the job reference, expected action and observed result. Avoid repeating a write or send action without checking whether it already happened.

[All connection setup guides](/en/Monitoring/Integrations/connections)


# Zoho Google Calendar setup


import ClickableImage from '@site/src/components/ClickableImage';

# Zoho Google Calendar setup

Run the configured Zoho and Google Calendar synchronisation.

<ClickableImage src="/img/eniris/monitoring/connection-guides/workflow-automation.webp" alt="A scheduled workflow with access control, transformation, validation, execution and an audit trail" maxWidth="1100px" />

*An automation should have a defined trigger, restricted access, validation, observable execution and a usable audit trail.*

Connection type: **Internal automation**.

## What to provide

Name the responsible Eniris operator, the approved scope and the expected outcome. Configuration and service credentials stay with the internal operator.

## Set up the connection

1. Ask the Eniris owner of this automation to agree its purpose, affected records/accounts and expected changes. This entry is not a customer meter connection.
2. The Eniris operator configures the required service access and scopes. Do not request internal administrator credentials from the customer.
3. Review a bounded test scope and its expected outcome before activation. For messaging, permission, merging or CRM workflows, the first run may change records or send messages.
4. Verify the intended action in the destination system and check for unintended changes before allowing the recurring schedule.

## Check the result

Verify the expected records or actions in the target system and the execution status. A meter dashboard may not apply. Review the effects of the first run before continuing a recurring automation.

## If setup does not work

Contact the responsible Eniris operator with the job reference, expected action and observed result. Avoid repeating a write or send action without checking whether it already happened.

[All connection setup guides](/en/Monitoring/Integrations/connections)


# Zoho Merge Accounts setup


import ClickableImage from '@site/src/components/ClickableImage';

# Zoho Merge Accounts setup

Merge accounts according to the configured Zoho workflow. Merging can alter existing customer records.

<ClickableImage src="/img/eniris/monitoring/connection-guides/workflow-automation.webp" alt="A scheduled workflow with access control, transformation, validation, execution and an audit trail" maxWidth="1100px" />

*An automation should have a defined trigger, restricted access, validation, observable execution and a usable audit trail.*

Connection type: **Internal automation**.

## What to provide

Name the responsible Eniris operator, the approved scope and the expected outcome. Configuration and service credentials stay with the internal operator.

## Set up the connection

1. Ask the Eniris owner of this automation to agree its purpose, affected records/accounts and expected changes. This entry is not a customer meter connection.
2. The Eniris operator configures the required service access and scopes. Do not request internal administrator credentials from the customer.
3. Review a bounded test scope and its expected outcome before activation. For messaging, permission, merging or CRM workflows, the first run may change records or send messages.
4. Verify the intended action in the destination system and check for unintended changes before allowing the recurring schedule.

## Check the result

Verify the expected records or actions in the target system and the execution status. A meter dashboard may not apply. Review the effects of the first run before continuing a recurring automation.

## If setup does not work

Contact the responsible Eniris operator with the job reference, expected action and observed result. Avoid repeating a write or send action without checking whether it already happened.

[All connection setup guides](/en/Monitoring/Integrations/connections)


# Zoho Odoo API setup


import ClickableImage from '@site/src/components/ClickableImage';

# Zoho Odoo API setup

Synchronise configured Zoho and Odoo information.

<ClickableImage src="/img/eniris/monitoring/connection-guides/workflow-automation.webp" alt="A scheduled workflow with access control, transformation, validation, execution and an audit trail" maxWidth="1100px" />

*An automation should have a defined trigger, restricted access, validation, observable execution and a usable audit trail.*

Connection type: **Internal automation**.

## What to provide

Name the responsible Eniris operator, the approved scope and the expected outcome. Configuration and service credentials stay with the internal operator.

## Set up the connection

1. Ask the Eniris owner of this automation to agree its purpose, affected records/accounts and expected changes. This entry is not a customer meter connection.
2. The Eniris operator configures the required service access and scopes. Do not request internal administrator credentials from the customer.
3. Review a bounded test scope and its expected outcome before activation. For messaging, permission, merging or CRM workflows, the first run may change records or send messages.
4. Verify the intended action in the destination system and check for unintended changes before allowing the recurring schedule.

## Check the result

Verify the expected records or actions in the target system and the execution status. A meter dashboard may not apply. Review the effects of the first run before continuing a recurring automation.

## If setup does not work

Contact the responsible Eniris operator with the job reference, expected action and observed result. Avoid repeating a write or send action without checking whether it already happened.

[All connection setup guides](/en/Monitoring/Integrations/connections)


# Zoho Reopen Inactive Clients setup


import ClickableImage from '@site/src/components/ClickableImage';

# Zoho Reopen Inactive Clients setup

Reopen clients according to the configured inactivity workflow.

<ClickableImage src="/img/eniris/monitoring/connection-guides/workflow-automation.webp" alt="A scheduled workflow with access control, transformation, validation, execution and an audit trail" maxWidth="1100px" />

*An automation should have a defined trigger, restricted access, validation, observable execution and a usable audit trail.*

Connection type: **Internal automation**.

## What to provide

Name the responsible Eniris operator, the approved scope and the expected outcome. Configuration and service credentials stay with the internal operator.

## Set up the connection

1. Ask the Eniris owner of this automation to agree its purpose, affected records/accounts and expected changes. This entry is not a customer meter connection.
2. The Eniris operator configures the required service access and scopes. Do not request internal administrator credentials from the customer.
3. Review a bounded test scope and its expected outcome before activation. For messaging, permission, merging or CRM workflows, the first run may change records or send messages.
4. Verify the intended action in the destination system and check for unintended changes before allowing the recurring schedule.

## Check the result

Verify the expected records or actions in the target system and the execution status. A meter dashboard may not apply. Review the effects of the first run before continuing a recurring automation.

## If setup does not work

Contact the responsible Eniris operator with the job reference, expected action and observed result. Avoid repeating a write or send action without checking whether it already happened.

[All connection setup guides](/en/Monitoring/Integrations/connections)


# Zoho Sales Handy Checkbox setup


import ClickableImage from '@site/src/components/ClickableImage';

# Zoho Sales Handy Checkbox setup

Update the configured SalesHandy-related status in Zoho.

<ClickableImage src="/img/eniris/monitoring/connection-guides/workflow-automation.webp" alt="A scheduled workflow with access control, transformation, validation, execution and an audit trail" maxWidth="1100px" />

*An automation should have a defined trigger, restricted access, validation, observable execution and a usable audit trail.*

Connection type: **Internal automation**.

## What to provide

Name the responsible Eniris operator, the approved scope and the expected outcome. Configuration and service credentials stay with the internal operator.

## Set up the connection

1. Ask the Eniris owner of this automation to agree its purpose, affected records/accounts and expected changes. This entry is not a customer meter connection.
2. The Eniris operator configures the required service access and scopes. Do not request internal administrator credentials from the customer.
3. Review a bounded test scope and its expected outcome before activation. For messaging, permission, merging or CRM workflows, the first run may change records or send messages.
4. Verify the intended action in the destination system and check for unintended changes before allowing the recurring schedule.

## Check the result

Verify the expected records or actions in the target system and the execution status. A meter dashboard may not apply. Review the effects of the first run before continuing a recurring automation.

## If setup does not work

Contact the responsible Eniris operator with the job reference, expected action and observed result. Avoid repeating a write or send action without checking whether it already happened.

[All connection setup guides](/en/Monitoring/Integrations/connections)


# Zoho Status Updater API setup


import ClickableImage from '@site/src/components/ClickableImage';

# Zoho Status Updater API setup

Update statuses in the configured Zoho workflow.

<ClickableImage src="/img/eniris/monitoring/connection-guides/workflow-automation.webp" alt="A scheduled workflow with access control, transformation, validation, execution and an audit trail" maxWidth="1100px" />

*An automation should have a defined trigger, restricted access, validation, observable execution and a usable audit trail.*

Connection type: **Internal automation**.

## What to provide

Name the responsible Eniris operator, the approved scope and the expected outcome. Configuration and service credentials stay with the internal operator.

## Set up the connection

1. Ask the Eniris owner of this automation to agree its purpose, affected records/accounts and expected changes. This entry is not a customer meter connection.
2. The Eniris operator configures the required service access and scopes. Do not request internal administrator credentials from the customer.
3. Review a bounded test scope and its expected outcome before activation. For messaging, permission, merging or CRM workflows, the first run may change records or send messages.
4. Verify the intended action in the destination system and check for unintended changes before allowing the recurring schedule.

## Check the result

Verify the expected records or actions in the target system and the execution status. A meter dashboard may not apply. Review the effects of the first run before continuing a recurring automation.

## If setup does not work

Contact the responsible Eniris operator with the job reference, expected action and observed result. Avoid repeating a write or send action without checking whether it already happened.

[All connection setup guides](/en/Monitoring/Integrations/connections)


# Huawei SmartLogger CSV export over FTP


# Huawei SmartLogger CSV export over FTP

Before changing the logger, request dedicated FTP credentials from Eniris. Provide the site name, logger model, firmware and serial number, time zone, devices to include and installer contact. Eniris supplies the destination address, protocol, port, username, password and remote folder. Use the issued settings exactly; do not substitute your manufacturer portal login.

Follow the [preparation and acceptance checklist](/en/Monitoring/Integrations/datalogger-ftp). Confirm the export format with Eniris using an original sample file before commissioning. A working FTP connection alone does not prove that measurements can be imported.

## Configure the SmartLogger

1. Open the SmartLogger's local IP address and sign in using an authorised account.
2. Open **Settings → FTP**.
3. Enter the Eniris-issued FTP server, username, password and remote directory.
4. Enable **Data export**. For the Eniris Format 4 ingestion workflow, use the settings below after Eniris confirms that they match your model and firmware.
5. Save with **Submit**, then run **Start report test**. Check the latest report status and record the transmission time.

The menu and report test are described in [Huawei's SmartLogger3000 manual, section 8.2](https://fcc.report/FCC-ID/QISSMARTLOGGER310/4660613.pdf). The ingestion profile below follows the [Eniris Huawei configuration guide](/en/Monitoring/Integrations/Battery%20or%20PV%20inverters/Huawei%20integration/HuaweiLocalIntervention).

| Export setting | Eniris Format 4 ingestion profile |
| --- | --- |
| File format | Format 4 |
| File name | minYYMMDD.csv |
| Time format | YY-MM-DD |
| Export mode | Cyclic |
| Export interval | 5 minutes or longer, as agreed with Eniris |
| File mode | Accumulated |
| Remote directory | Use the issued folder; the existing Eniris profile uses /files |

Do not assume every SmartLogger firmware exposes identical formats or security options. If a setting is absent, send the model, firmware and available export options to Eniris before changing the profile.

## Verify the result

Record the upload time and result. Ask Eniris to confirm a new file in the assigned folder and measurements in the correct Insights account. Compare device IDs, timestamps, units and values with the logger. Check another scheduled upload to confirm that recurring delivery works. The initial SmartgridX retrieval can only process files that have already arrived.

If no file arrives, check the issued destination, credentials, folder and network access. If a file arrives without measurements, send Eniris the filename, logger model, export settings and affected time range. Keep passwords out of screenshots.


# Datalogger CSV and FTP setup


# Datalogger CSV and FTP setup

CSV monitoring requires the customer or installer to configure automatic export on the datalogger. Creating a connection in SmartgridX does not configure the logger or start its uploads.

## Choose your datalogger

- [SMA Sunny WebBox](/en/Monitoring/Integrations/datalogger-ftp/sma)
- [Huawei SmartLogger](/en/Monitoring/Integrations/datalogger-ftp/huawei)
- [Solar-Log](/en/Monitoring/Integrations/datalogger-ftp/solar-log)
- [WebdynSun](/en/Monitoring/Integrations/datalogger-ftp/webdynsun)

For another logger, send Eniris its exact model, firmware, export manual and a sample file. Eniris must confirm its format and delivery method before activation. CSV is a file format, not a guarantee that every CSV-producing device is compatible. Files supplied by a grid operator, manual historical imports and exports from SmartgridX to another platform follow separate workflows.

## 1. Collect the site information

Provide the company and contact person, site name and address, logger model and serial number, firmware, time zone, installation and device identifiers, requested measurements and upload frequency. State which devices may be included and which must be excluded. For SMA, provide the rated peak power of the largest PV installation in kWp so Eniris can configure spike filtering.

Nominate an installer who has permission to change the datalogger settings and can reach its local interface. Send an unmodified sample export with a description of units and timestamps. State which SmartgridX / Insights account should receive the data.

## 2. Request FTP credentials from Eniris

Eniris must provision the destination before the installer configures recurring uploads. Request the following for this connection:

| Setting | Supplied or confirmed by Eniris |
| --- | --- |
| Destination | Server hostname and port |
| Transport | FTP, FTPS or SFTP, including supported security settings |
| Authentication | Dedicated username and password |
| Remote directory | Exact destination folder; leave blank only if instructed |
| Export | Supported file format/version, filename convention and upload interval |
| Network | Outbound access requirements, including data connections where applicable |

These credentials are separate from the manufacturer's monitoring portal account. Transfer them using the secure channel agreed with Eniris. FTP, FTPS and SFTP are different protocols; the logger and destination must support the same one. Do not change encryption settings by trial and error.

## 3. Configure the logger

Open its local interface, confirm that current measurements are present and that the clock is correct. Use the model-specific guide above to enable recurring export with the issued settings. Preserve existing settings and check with the site owner before replacing a destination used by another service. If the model has no supported export option, ask Eniris to confirm another data route.

Run the logger's connection or report test where available, then wait for an actual measurement file. Keep recurring export enabled. File delivery is limited by the logger's recording and upload intervals; a SmartgridX worker cannot retrieve data that has not been uploaded.

## Verify the result

Record the upload time and result. Ask Eniris to confirm a new file in the assigned folder and measurements in the correct Insights account. Compare device IDs, timestamps, units and values with the logger. Check another scheduled upload to confirm that recurring delivery works. The initial SmartgridX retrieval can only process files that have already arrived.

If no file arrives, check the issued destination, credentials, folder and network access. If a file arrives without measurements, send Eniris the filename, logger model, export settings and affected time range. Keep passwords out of screenshots.

Related: [Requesting FTP credentials](/en/Monitoring/Web%20portal/features/ftp-tool/credentials).


# SMA datalogger CSV export over FTP


# SMA datalogger CSV export over FTP

Before changing the logger, request dedicated FTP credentials from Eniris. Provide the site name, logger model, firmware and serial number, time zone, devices to include and installer contact. Eniris supplies the destination address, protocol, port, username, password and remote folder. Use the issued settings exactly; do not substitute your manufacturer portal login.

Follow the [preparation and acceptance checklist](/en/Monitoring/Integrations/datalogger-ftp). Confirm the export format with Eniris using an original sample file before commissioning. A working FTP connection alone does not prove that measurements can be imported.

## Check the exact SMA model

The steps below apply to **Sunny WebBox with Bluetooth**. Its FTP push settings offer CSV export. The separate legacy **Sunny WebBox** manual describes FTP push as XML-only; do not apply the CSV instructions to that model. Send its model and a sample export to Eniris to select a suitable connector. Other SMA loggers, including Data Manager models, need their own model and firmware compatibility check. See the [Bluetooth manual, sections 8.5.2–8.5.3](https://files.sma.de/downloads/SWebBox20-BA-en-13.pdf) and [legacy WebBox manual, section 9.4](https://files.sma.de/downloads/SWebBox-BA-en-36.pdf).

## Configure Sunny WebBox with Bluetooth

1. Open the logger's local IP address and sign in with an authorised installer account.
2. Select the WebBox in the plant tree. Open **Settings → Further Applications → FTP Push**, then **Edit**.
3. Fill **Server**, **Port**, **Login**, **Password** and **Server path** with the Eniris-issued values.
4. Enable **Data export in CSV format**. Enable XML only if Eniris also requested it.
5. Save. Run **Connection test → Execute**; inspect **Result of the last connection test** for **OK**.

These controls are documented in the [SMA Bluetooth WebBox manual](https://files.sma.de/downloads/SWebBox20-BA-en-13.pdf). Menu wording can differ with firmware.

## Information Eniris needs

Send the logger model, firmware and serial number; installation and inverter identifiers; site time zone; an original CSV export; and the rated peak power of the largest installation in kWp. Eniris uses that capacity to configure spike filtering. Eniris manages the ingestion folder and internal account mapping; the customer does not need to provide a technical root-account setting.

## Verify the result

Record the upload time and result. Ask Eniris to confirm a new file in the assigned folder and measurements in the correct Insights account. Compare device IDs, timestamps, units and values with the logger. Check another scheduled upload to confirm that recurring delivery works. The initial SmartgridX retrieval can only process files that have already arrived.

If no file arrives, check the issued destination, credentials, folder and network access. If a file arrives without measurements, send Eniris the filename, logger model, export settings and affected time range. Keep passwords out of screenshots.


# Solar-Log CSV export over FTP


# Solar-Log CSV export over FTP

Before changing the logger, request dedicated FTP credentials from Eniris. Provide the site name, logger model, firmware and serial number, time zone, devices to include and installer contact. Eniris supplies the destination address, protocol, port, username, password and remote folder. Use the issued settings exactly; do not substitute your manufacturer portal login.

Follow the [preparation and acceptance checklist](/en/Monitoring/Integrations/datalogger-ftp). Confirm the export format with Eniris using an original sample file before commissioning. A working FTP connection alone does not prove that measurements can be imported.

## Check the export licence

Solar-Log Base firmware 6.x documents automatic export as a licensed feature with a trial period. Confirm the licence before relying on continued uploads; CSV export is not automatically free. See the [Solar-Log Base 6.x manual, Export](https://www.solar-log.com/fileadmin/user_upload/documents/Handbuecher_und_Inlet/en_GB/SolarLog_Base_Manual_6.x_EN.pdf).

## Configure export

1. Sign in to the logger's local interface with permission to change configuration.
2. Open **Configuration → Internet → Export** and enable export.
3. Enter the destination server, username, password and directory supplied by Eniris.
4. Set the agreed upload interval and choose **CSV** as the data format.
5. Select the CSV version confirmed by Eniris from a sample file. The manual describes versions 0.1 and 1.0; do not assume they are interchangeable.
6. Match the FTP/FTPS security settings to the issued destination. Save and inspect the next transfer result.

These steps refer to the [Base 6.x manual](https://www.solar-log.com/fileadmin/user_upload/documents/Handbuecher_und_Inlet/en_GB/SolarLog_Base_Manual_6.x_EN.pdf). For other models or firmware, provide the relevant export screen and sample file to Eniris before commissioning.

## Verify the result

Record the upload time and result. Ask Eniris to confirm a new file in the assigned folder and measurements in the correct Insights account. Compare device IDs, timestamps, units and values with the logger. Check another scheduled upload to confirm that recurring delivery works. The initial SmartgridX retrieval can only process files that have already arrived.

If no file arrives, check the issued destination, credentials, folder and network access. If a file arrives without measurements, send Eniris the filename, logger model, export settings and affected time range. Keep passwords out of screenshots.

For further diagnosis, use [Solar-Log FTP troubleshooting](/en/Monitoring/Web%20portal/features/ftp-tool/solar-log).


# WebdynSun CSV export over FTP


# WebdynSun CSV export over FTP

Before changing the logger, request dedicated FTP credentials from Eniris. Provide the site name, logger model, firmware and serial number, time zone, devices to include and installer contact. Eniris supplies the destination address, protocol, port, username, password and remote folder. Use the issued settings exactly; do not substitute your manufacturer portal login.

Follow the [preparation and acceptance checklist](/en/Monitoring/Integrations/datalogger-ftp). Confirm the export format with Eniris using an original sample file before commissioning. A working FTP connection alone does not prove that measurements can be imported.

## Configure the original WebdynSun

1. Open the gateway's local IP address and sign in with an authorised account.
2. Open **Configuration**. Check the Ethernet or modem connection settings with the site's network administrator.
3. Enter the FTP destination and account details provided by Eniris.
4. Save the settings and arrange the gateway restart required by Webdyn's procedure with the site operator.
5. Open **Installation → Connection** and start a connection.

Webdyn documents this sequence in its [WebdynSun configuration FAQ](https://www.webdyn.com/product/webdynsun/). It also explains that delivered data files contain CSV compressed as GZ. Preserve the original files when sending a sample to Eniris. Do not assume WebdynSunPM or another gateway has identical menus.

## Confirm the collection profile

Provide the gateway ID, firmware, connected device list, time zone and an original export. Eniris must confirm the measurements, upload schedule, directory layout and required definition files. Changing the remote server may affect the existing configuration workflow, so agree the destination change with the operator first. The [WebdynSun user manual](https://www.webdyn.com/wp-content/uploads/2022/02/WebdynSun-user-manual-1.pdf) describes its remote configuration files and data formats.

## Verify the result

Record the upload time and result. Ask Eniris to confirm a new file in the assigned folder and measurements in the correct Insights account. Compare device IDs, timestamps, units and values with the logger. Check another scheduled upload to confirm that recurring delivery works. The initial SmartgridX retrieval can only process files that have already arrived.

If no file arrives, check the issued destination, credentials, folder and network access. If a file arrives without measurements, send Eniris the filename, logger model, export settings and affected time range. Keep passwords out of screenshots.


# Monitoring Fluvius Energy Meter


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import RS485AddressNote from '@site/src/components/RS485AddressNote';
import ClickableImage from '@site/src/components/ClickableImage';

# Fluvius Energy Meter

## Introduction

Fluvius is the electricity and natural gas distribution system operator in Flanders, Belgium. Through their digital metering system, customers can share their energy consumption data with third-party service providers like Eniris.

## Data Sharing Flow

<ClickableImage src="/img/eniris/monitoring/integrations/digital-meter-consent.webp" alt="A digital energy meter sharing authorized historical readings through a secure data service with a monitoring dashboard" maxWidth="1100px" />

*The customer authorizes the data-sharing mandate before historical and new meter readings can become available in SmartgridX.*

<ClickableImage src="/img/generic/energiedienstverlener-met-api.webp" alt="Fluvius data sharing configuration interface" maxWidth="450px" />

## Configuration Steps

1. Create a support ticket on [eniris.io](https://eniris.io)
   - **Important**: Include "Fluvius API New Integration" in your ticket

2. Our support team will provide you with an endpoint URL
   - The endpoint URL will end with a `flow=` parameter
   - Specify one of these options:
     - `flow=B2B` for Business to Business connections
     - `flow=B2C` for Business to Consumer connections

3. Access the endpoint URL
   - You will receive a "ShortUrl" in the response
   - This ShortUrl is required for the next step

4. Complete the authorization process
   - Use the ShortUrl from step 3
   - Follow the official Fluvius video guide: [Fluvius Data Sharing Guide](https://www.fluvius.be/nl/veelgestelde-vragen/mijn-fluvius/verbruik-delen-met-energiedienstverlener#delen)

## Data Availability

After completing the configuration:
- Data will automatically appear in your Insights 3 dashboard
- Historical data for the past 3 years will be imported during the first synchronization
- Subsequent data updates will occur automatically

# Meters, sensors, gateways & building systems


import ClickableImage from '@site/src/components/ClickableImage';

# Meters, sensors, gateways & building systems

Use this list for metering and operational data supplied by a meter platform, gateway, PLC, building-management system, API, or structured export.

<ClickableImage src="/img/eniris/monitoring/integrations/integration-routes.webp" alt="An energy meter and inverter connected to SmartgridX through local, cloud and scheduled data routes" maxWidth="1100px" />

*The meter can reach SmartgridX through a controller, a supported platform or another documented data route.*

<Callout type="info" title="Compatibility is verified per project">
  A listed integration means that a supported data route exists. It does not guarantee every model, firmware version, measurement, alarm, history interval, region, or control function. Eniris confirms the precise scope before commissioning.
</Callout>

| Integration | Typical monitoring scope | What Eniris needs |
| --- | --- | --- |
| [IMT Si-RS485TC-T-MB](/Controller/Devices/Energy-meter/IMT) | Solar irradiance in W/m², collected locally through a controller over RS485 / Modbus RTU | To connect this sensor, provide the sensor model, controller and site, RS485 connection, Modbus address and serial communication settings. |
| **Fluvius API** | Electricity and gas metering for authorized Flemish connection points | Customer authorization, B2B or B2C flow, reference number, EAN/GSRN context, and the connection points to include. |
| **Fluvius NPS files** | Recurring Fluvius meter files | Contract allow-list, supported file delivery route, time zone, and confirmation of EAN/GSRN and serial-number mapping. |
| **Fudura** | Utility-meter data available through the Fudura API | API key, EAN or meter scope, customer authorization, and time zone. |
| **Innax** | Metering and building-energy data | Client ID, client secret, refresh token or approved account connection, and the source IDs to include. |
| **Opinum** | Metering and energy-management data | Client ID and secret, dedicated account credentials, source IDs, and requested measurements. |
| **Smappee API** | Electricity, appliance, and site measurements where available | Client ID, client secret, dedicated account, installation allow-list, and service-location identifiers. |
| **Smappee MQTT** | Measurements published by a supported Smappee setup | Topic structure, payload sample, device identifiers, units, and publishing interval. MQTT credentials must be requested through the Eniris webshop. |
| **Eniscope** | Building and circuit-level energy measurements | Dedicated account, installation allow-list, and device or channel mapping. |
| **Youless** | Local electricity and gas readings from supported Youless devices | Exact model, local IP address, device access, meter mode, and site-network reachability. |
| **Elgris / EmonCMS-compatible feed** | Power-meter and energy-feed data | API key, feed identifiers, device/site mapping, units, and time zone. |
| **E-alyzer** | Meter data associated with EAN connection points | EAN identifiers, customer authorization, requested period, and site mapping. |
| **Envitron** | Metering platform data | Dedicated platform account, meter ID, approved API access, and site/time-zone mapping. |
| **Efento** | Environmental and temperature-sensor data | API key, sensor identifiers, installation mapping, units, and required interval. |
| **Meterbeheer** | Metering data from the Meterbeheer platform | API key, meter identifiers, installation mapping, and requested measurements. |
| **EMB 2020** | Supported meter and building-energy data | Platform user or approved access, meter list, site mapping, and time zone. |
| **Cast4All** | Meter and telemetry data exposed by a Cast4All deployment | API base URL, client credentials, and an installation allow-list. |
| **CADIS** | Structured meter CSV data | Representative CADIS file, source folder/delivery route, time zone, device names, OBIS mapping, units, and interval. |
| **CME 3100** | Supported recurring meter files | Representative file, delivery folders, time zone, meter serial numbers, and parameter/unit mapping. |
| **CloudGate** | Gateway CSV or FTP data | Gateway identity, supported file delivery route, time column and format, time zone, device-ID column, fields, tags, and sample file. |
| **Moxa** | CSV data from supported Moxa gateways | Representative file, delivery route, device/column mapping, units, timestamp definition, and error-file handling. |
| **2-Wire** | Supported recurring meter CSV files | Representative file, delivery folders, time zone, device identifiers, units, and agreed schedule. |
| **ProfiNrg** | Supported meter CSV delivery | Representative file, delivery folders, time zone, device mapping, units, and schedule. |
| **WAGO** | Data exposed by a supported WAGO installation | Installation ID, endpoint or daily data URL, time zone, tag/register mapping, and network reachability. |
| **Siemens S7-1200** | PLC tags and mapped energy signals | PLC name, reachable endpoint, tag mapping, time zone, network route, and an agreed sampling interval. |
| **Siemens MQTT** | PLC or gateway measurements published through MQTT | Broker route, topics, payload sample, device/tag mapping, units, timestamps, TLS setup, and publish interval. MQTT credentials must be requested through the Eniris webshop. |
| **Ewon Talk2M** | Data from supported Ewon gateways | Talk2M device ID and token, installation IDs, gateway access, and tag mapping. |
| **Helexia** | Supported project files containing inverter or meter data | Device name, source/delivery folders, inverter configuration, time zone, file sample, and units. |
| **Qantum** | Project metadata and supported platform data | Dedicated Qantum account, authorized Eniris integration access, installation mapping, and requested data scope. |
| **Scipher** | Supported platform data | Dedicated account, site/device identifiers, time zone, and requested measurements. |
| **NEA** | Data from a supported NEA endpoint | API base URL, site/source identifiers, expected fields, units, and time zone. |
| **ElliTrack** | Supported recurring tracker or asset files | Delivery route, time zone, asset identifiers, serial-number mapping, and representative files. |
| **Generic CSV, Excel, JSON, XML, or TXT** | Historical or recurring structured imports | Sample files, delivery method, timestamp column and format, time zone, decimal separator, device ID, tags, fields, units, retention rule, and update schedule. |

## Before requesting activation

Provide the exact manufacturer and model, firmware version, source account or installation identifiers, required measurements and alarms, expected interval, time zone, and a recent source screenshot or export. Never place passwords, API secrets, private keys, or refresh tokens in a support ticket.


# Supported devices and data sources


import { FolderOverview } from '@/components/FolderOverview';
import ClickableImage from '@site/src/components/ClickableImage';

<span id="integrations-overview" />

# Supported devices and data sources

SmartgridX Monitoring can combine measurements from manufacturer platforms, meters, data loggers, building systems, weather services, market feeds, and structured files. The data is mapped to the SmartgridX device hierarchy so that it can be used in dashboards, device pages, alarms, reports, and public displays.

<ClickableImage src="/img/eniris/monitoring/integrations/integration-routes.webp" alt="An energy device sending measurements to SmartgridX through a local controller, a secure manufacturer cloud or a scheduled file transfer" maxWidth="1100px" />

*SmartgridX can combine local, cloud and scheduled data routes in one monitoring environment.*

<Callout type="info" title="This catalogue describes data collection">
  A listed integration means that a supported data route exists for monitoring data. It does not automatically mean that every model, firmware version, measurement, alarm, historical interval, or control function is available. Eniris verifies the exact scope before commissioning.
</Callout>

## What we always need

Provide the following information for every new integration request:

| Item | What to provide | Why it matters |
| --- | --- | --- |
| **Installation** | Customer, site name, address or country, time zone, and requested go-live date | Prevents data from being assigned to the wrong site or time zone. |
| **Equipment** | Manufacturer, exact model, firmware, serial numbers, and number of devices | Determines whether the available data route matches the installed equipment. |
| **Source** | Platform name, portal region or URL, and whether data is available through an API, shared account, file export, MQTT, or a local gateway | Selects the correct connector and onboarding procedure. |
| **Scope** | Plant, site, system, device, meter, EAN, or other source identifiers | Defines exactly which assets may be imported. |
| **Expected data** | Required measurements, alarms, historical depth, and preferred interval | Confirms whether the external source exposes enough detail for the intended dashboard or report. |
| **Validation** | A recent screenshot or export containing the source values and timestamps | Makes it possible to compare SmartgridX with the source after commissioning. |

> [!IMPORTANT]
> Do not place passwords, API secrets, private keys, or refresh tokens in the text of a support ticket. State which credential type is available. Eniris Support will provide the appropriate secure handover method. Where the provider supports user sharing, create a dedicated read-only integration user instead of sharing a personal administrator account.

## Select the data route

| Route | Best suited for | Additional requirements |
| --- | --- | --- |
| **Manufacturer API** | Cloud-connected assets already visible in a supported manufacturer platform | API entitlement or plan, key and secret or OAuth credentials, account permissions, source IDs, and provider region. |
| **Shared manufacturer account** | Platforms where installations can be shared with a dedicated integration user | Dedicated read-only user, access to the requested sites, site identifiers, and confirmation from the owner. |
| **FTP or file push** | Supported data loggers and recurring CSV, XML, JSON, TXT, or Excel exports | Supported logger and format, export interval, time zone, filename convention, destination configuration, and outbound network access. |
| **MQTT** | Gateways and platforms that publish measurements to a broker | Topic structure, payload example, units, timestamps, publishing interval, TLS requirements, and device identifiers. MQTT credentials must be requested through the Eniris webshop. |
| **Local gateway or controller** | Fast operational measurements from Modbus, PLCs, local HTTP interfaces, or other site protocols | Reachable endpoint, protocol settings, register or tag mapping, network route, firewall rules, and an on-site commissioning test. |
| **Existing file or database export** | Historical imports and project-specific data deliveries | Representative sample files, column definitions, units, time zone, decimal format, unique device identifier, and delivery schedule. |

## Browse the compatibility catalogue

Choose the category that matches the device, platform, or contextual data source. Every category contains the supported integrations and the information Eniris needs before activation.

<FolderOverview folder="Monitoring/Integrations" />

## Commissioning and acceptance

An integration is accepted only after the following checks succeed:

1. The expected installations and devices appear in the correct SmartgridX hierarchy.
2. Current power, cumulative energy, state, and other key values match the source within the expected update delay.
3. Units, scaling, import/export sign convention, and time zone are correct.
4. Historical data contains no unexplained gaps, duplicates, or shifted timestamps.
5. Alarms and statuses are tested when the external source exposes them.
6. The customer confirms which account owner will maintain access, subscriptions, and provider permissions.

<Callout type="warning" title="Monitoring is not control">
  A cloud or file integration that is suitable for dashboards and reports may be too slow, read-only, or insufficiently available for local control, peak shaving, or VPP operation. Those applications require a separate technical assessment.
</Callout>

If a source is not listed, submit the manufacturer, model, firmware, protocol or API documentation, sample payloads or files, required measurements, and expected project volume through the [Eniris integration request](https://www.eniris.com/integration_request).



# Weather, market & grid data


# Weather, market & grid data

These sources enrich dashboards, analysis, forecasting, tariffs and reports. They provide context and do not represent a physical meter at the installation.

<Callout type="info" title="Compatibility is verified per project">
  A listed integration means that a supported data route exists. It does not guarantee every model, firmware version, measurement, alarm, history interval, region, or control function. Eniris confirms the precise scope before commissioning.
</Callout>

These integrations provide context for analysis, forecasting, tariffs, or reporting. They do not represent a physical meter at the installation.

| Integration | Typical data | What Eniris needs |
| --- | --- | --- |
| **AEMET** | Spanish weather observations or forecasts | API key, coordinates or station scope, variables, interval, and time zone. |
| **Copernicus Climate Data Store** | Gridded weather and radiation data | CDS API key, coordinates, variables, requested period, output format, and time zone. |
| **DWD** | German weather and solar-radiation observations | Coordinates or station scope, requested variables, interval, and time zone. |
| **KMI / RMI** | Belgian weather and synoptic data | Coordinates or station scope, requested variables, interval, and time zone. |
| **KNMI / KNMI Data Platform** | Dutch weather and station data | API key where required, station or coordinate scope, variables, interval, and time zone. |
| **MeteoSwiss** | Swiss weather observations | Station or coordinate scope, variables, interval, and time zone. |
| **UK Met Office** | Weather model or observation data | API key, order ID where applicable, coordinates, grid step, variables, period, and time zone. |
| **Open-Meteo** | Forecast or weather-station context | Installation coordinates or weather-station metadata, variables, interval, and time zone. |
| **OpenWeatherMap** | Weather observations and forecasts | API token, locations or coordinates, variables, interval, and time zone. |
| **ENTSO-E** | European electricity-market and system data | ENTSO-E token, country/bidding-zone scope, data item, resolution, currency, and time zone. |
| **Elex** | Day-ahead prices and forecasts | API key, required regions, resolution, currency, and time zone. |
| **EPEX SPOT** | Day-ahead market results | Market area, product or resolution, currency, requested period, and time zone. |
| **HUPX** | Hungarian day-ahead and quarter-hour price data | Market area, product/resolution, currency, requested period, and time zone. |
| **Nord Pool** | Day-ahead price indices | Area-code list, custom area mapping where required, currency, resolution, and time zone. |
| **Frank Energie** | Supported dynamic electricity prices | Country/product scope, resolution, currency, and time zone. |
| **Elia** | Belgian grid and market context | Dataset, geographic or market scope, resolution, period, units, and time zone. |
| **TenneT** | Dutch grid and market context | Dataset, market scope, resolution, period, units, and time zone. |
| **MEMO market data** | Supported market-price exports | Market area, product, resolution, currency, requested period, and time zone. |
| **CKW** | Swiss grid-price schedules | Applicable grid operator, tariff/product, customer category, validity period, and site mapping. |
| **EKZ** | Swiss grid-price schedules | Applicable grid operator, tariff/product, customer category, validity period, and site mapping. |
| **Groupe E** | Swiss grid-price schedules | Applicable grid operator, tariff/product, customer category, validity period, and site mapping. |
| **Swiss PV tariff data** | Swiss feed-in and PV tariff context | API key where required, grid operator mapping, installation region, validity period, and currency. |
| **Vlaamse Nutsregulator reference data** | Flemish energy-market reference data | Required dataset, region/scope, validity period, and intended use. |

## Before requesting activation

Provide the exact manufacturer and model, firmware version, source account or installation identifiers, required measurements and alarms, expected interval, time zone, and a recent source screenshot or export. Never place passwords, API secrets, private keys, or refresh tokens in a support ticket.


# Wind, fleet & specialist platforms


# Wind, fleet & specialist platforms

Use this list for wind assets, cross-site fleets and specialist platforms that supply monitoring data through an account, API, gateway, or file route.

<Callout type="info" title="Compatibility is verified per project">
  A listed integration means that a supported data route exists. It does not guarantee every model, firmware version, measurement, alarm, history interval, region, or control function. Eniris confirms the precise scope before commissioning.
</Callout>

| Integration | Typical monitoring scope | What Eniris needs |
| --- | --- | --- |
| **Enercon** | Wind farms, turbines, production, status, and events where available | Dedicated platform access, farm/turbine identifiers, turbine serial numbers, and source time zone. |
| **EWT DirectWind** | Wind-farm and turbine data | Dedicated platform access, farm and turbine identifiers, serial numbers, and requested measurements. |
| **Vensys** | Wind farms, turbines, telemetry, and alarms where available | Vensys API key and the turbine TID list to include. |
| **Windup** | Wind farms and turbine telemetry | Dedicated API account and an allow-list of turbine IDs. |
| **SynaptiQ API** | Wind or renewable portfolio telemetry | Dedicated account, plant/turbine scope, time zone, and requested signals. |
| **SynaptiQ file push** | Recurring telemetry files | Delivery credentials, root asset IDs, address and tag configuration, sampling/interpolation interval, time zone, and sample files. |
| **GreenPowerMonitor** | Renewable plants, elements, inverters, and measurements where available | Dedicated API account, platform URL, plant scope, and element/device identifiers. |
| **Dexter** | Forecasts and actual energy measurements | Dedicated API account, environment, requested forecast queries, actuals source, asset identifiers, units, and time zone. |
| **Hualogy export** | Portfolio telemetry delivered through a supported export | Export access, plant list, device mapping, time zone, sample files, and delivery interval. |
| **EMI** | Supported installation telemetry | API key, time zone, installation allow-list, and source identifiers. |
| **EPIAS** | Supported energy-platform data | API username/password or approved service account, installation scope, and requested measurements. |
| **OKTE** | Supported market or energy data | Required area or asset scope, time range, units, and commissioning contact. |
| **OREE** | Supported structured energy data | Representative export, site/source mapping, timestamp and unit definitions, and delivery schedule. |
| **WebdynSun manual/file routes** | PV logger and fleet data | Logger identity, export route, representative files, site/inverter mapping, time zone, and schedule. |

## Before requesting activation

Provide the exact manufacturer and model, firmware version, source account or installation identifiers, required measurements and alarms, expected interval, time zone, and a recent source screenshot or export. Never place passwords, API secrets, private keys, or refresh tokens in a support ticket.


# Account settings


# Account settings

The current **User profile** page shows the email address associated with the authenticated user and provides the password-change workflow.

## Change your password

1. Open the user menu and choose **User profile** or **Account settings**.
2. Confirm the email address shown on the page.
3. Enter your current password.
4. Enter the new password and submit the form.
5. Wait for the success state before leaving the page.

The profile component sends the current and new password to the authenticated password-update endpoint and displays validation, authorisation, or unexpected-error feedback returned by the service.

<Callout type="info" title="Email changes are not part of this page">
  The current profile implementation exposes the email address as account information but does not provide an active email-change form. Ask an authorised administrator or Support when an identity must be migrated.
</Callout>

## Security recommendations

- use a unique password;
- do not reuse controller, FTP, or email credentials;
- remove old role memberships when responsibilities change;
- use password reset instead of asking another person to share credentials;
- report unexpected company or installation access immediately.


# Contacts and recipients


import ClickableImage from '@/components/ClickableImage';

# Contacts and recipients

Contacts provide operational context and reusable recipient data. Depending on page settings, a device can expose both **Notes and maintenance** and **Contacts** from its Features menu.

## Contact information

A contact can contain fields such as name, email address, phone number, language, and contact type. Available fields and types depend on the organisation configuration.

## Add a reusable contact

1. Open the organisation contact settings.
2. Create the contact with a recognisable name and valid communication details.
3. Select the appropriate contact type and language.
4. Save the record.
5. Open the relevant installation or device and attach the saved contact.

<ClickableImage src="/img/eniris/monitoring/screenshots/contact-add-form.webp" alt="SmartgridX form for adding a reusable contact with language and contact type" maxWidth="1140px" />

*Name, telephone number, email, language, and type are stored as contact data; portal access is still managed separately.*

## How contacts are used

- installation responsibility and maintenance context;
- simple recipient selection in report instances;
- alarm notification recipient lists, where supported by the configured workflow;
- customer-facing communication lists.

For the current alarm notification setup, see [Advanced alarms notifications](../management/alarms/advanced-alarms#notifications).

<Callout type="warning" title="A contact is not a portal user">
  Contact records support communication. Portal access is granted separately through role membership in User management.
</Callout>

Review contacts when an installation changes owner, maintenance provider, or operational responsibility. Remove obsolete addresses from both the contact record and any fixed recipient lists.


# General dashboard settings


import ClickableImage from '@/components/ClickableImage';

# General dashboard settings

General settings shape the portal that the Insights application builds from the device forest. They affect navigation, device pages, portfolio presentation, and policy flows.

## Page visibility

Visibility is evaluated for the current role and, on device pages, for the device type and authority. Settings can control whether users see:

- portfolio and management pages;
- reports and alarm pages;
- device overviews;
- descendant-device groups;
- Insights alarms and manufacturer logs;
- targets, contacts, documents, streams, and settings;
- individual widget, line-chart, and bar-chart groups.

<Callout type="info" title="Visibility is additive to access control">
  A visible page still requires the underlying route and role relationship. Conversely, a user with a broad role may not see a section that page settings deliberately hide for that authority.
</Callout>

<ClickableImage src="/img/eniris/monitoring/screenshots/dashboard-page-permissions.webp" alt="SmartgridX dashboard settings with page visibility per portal role" maxWidth="1140px" />

*Compare owner, administrator, installer, and visitor visibility before publishing the configuration.*

## Site tags

Tags classify active sites into navigation groups. The current SmartgridX layout:

1. searches active site nodes;
2. determines which configured tags are present;
3. shows only those tag groups;
4. opens the site route with the selected tag as a query parameter.

Use stable tag values and translate only their labels. Changing a value can affect saved routes and portfolio grouping.

<ClickableImage src="/img/eniris/monitoring/screenshots/installations-without-follow-up.webp" alt="An anonymized SmartgridX overview of installations that are not currently followed up" maxWidth="1140px" />

*The follow-up overview separates installations that need activation or review from the active monitored portfolio.*

## Device overview configuration

Each device type can receive defaults for:

- summary widgets;
- line-chart groups;
- bar-chart groups;
- height and responsive presentation;
- feature visibility.

The application still checks whether valid telemetry exists before rendering a configured chart.

<ClickableImage src="/img/eniris/monitoring/screenshots/data-stream-configuration.webp" alt="An anonymized SmartgridX data-stream configuration with calculation and scaling controls" maxWidth="1140px" />

*Stream mapping and page configuration jointly determine whether a meaningful chart can be rendered.*

## Policies and agreements

Required policies are checked after sign-in. The current router can temporarily make the policy viewer the user's home route when a required policy has not been accepted. A recent skip can postpone the prompt for a limited period when the policy configuration allows it.

When adding an agreement, verify:

- stable policy identifier;
- required-by date;
- supported languages;
- title and content;
- links and formatting;
- behaviour for a new user and an existing user.

## Presentation defaults

Organisation settings can also define:

- contact, alarm, document, and site categories;
- monthly production or performance reference distributions;
- number formatting and decimals;
- table columns and tile elements;
- organisation-specific translations;
- orientation or diagram settings used by configured views.

<ClickableImage src="/img/eniris/monitoring/screenshots/translation-settings.webp" alt="SmartgridX translation settings with supported languages and translation keys" maxWidth="1140px" />

*Translate labels while keeping stable internal identifiers unchanged.*

## Safe change sequence

1. Change one setting group at a time.
2. Test as owner and visitor.
3. Check desktop and mobile navigation.
4. Open at least one site and one child device.
5. Verify alarms and reports are still reachable.
6. Record the change when it affects customer-facing presentation.


# Dashboard settings


import { FolderOverview } from '@/components/FolderOverview';
import ClickableImage from '@/components/ClickableImage';

# Dashboard settings

Dashboard settings determine how the same connected assets are presented to different audiences. In the current application, page settings are resolved using both the device type and the user's authority on that device. Owners, administrators, installers, and visitors can therefore receive different menus and visual elements.

<ClickableImage src="/img/eniris/monitoring/screenshots/dashboard-page-permissions.webp" alt="SmartgridX dashboard settings with page visibility per portal role" maxWidth="1140px" />

*Page selection lets a super administrator control which routes each portal role can see.*

## What settings influence

| Setting area | Effect in the current portal |
| --- | --- |
| **Site tags and labels** | Determine which active installation groups appear in the main navigation. |
| **Page visibility** | Controls whether portfolio tables, reports, alarm pages, device overviews, or individual device sections are shown. |
| **Device overview elements** | Selects applicable widget trays, line-chart groups, and bar-chart groups per device type. |
| **Role-specific visibility** | Separates owner or administrator tools from visitor-facing information. |
| **Translations** | Localises configured labels and organisation-specific terminology. |
| **Contacts** | Supplies reusable recipients and installation contacts for reports and alert messages. |

<Callout type="warning" title="Configuration can hide documented features">
  If an article describes a page that is absent from your portal, first verify your role, the active view, the device's page settings, and the relevant licence or feature flag.
</Callout>

## Settings guides

<FolderOverview folder="Monitoring/Web portal/dashboard-settings" />


# Translation settings


import ClickableImage from '@/components/ClickableImage';

# Translation settings

The current portal combines built-in application translations with translations stored in the organisation settings. This is especially important for configured site tags, types, dashboard labels, and white-label terminology.

## Recommended workflow

1. Enable only the languages the organisation will maintain.
2. Keep the underlying key or tag value stable.
3. Add a clear label in every enabled language.
4. Test navigation, tables, device menus, reports, and public displays.
5. Check mobile layouts for longer translations.

<ClickableImage src="/img/eniris/monitoring/screenshots/translation-settings.webp" alt="SmartgridX translation settings with supported languages and translation keys" maxWidth="1140px" />

*Enable the maintained languages first, then add labels for stable configured keys.*

## What to translate

- site-tag labels shown in the main navigation;
- organisation-specific contact, document, or alarm type labels;
- configured dashboard headings and KPI labels;
- public-display text blocks where the template expects translated content;
- white-label product terminology.

<Callout type="warning" title="Do not translate identifiers">
  Route paths, telemetry keys, node types, and stable configuration identifiers are technical values. Translate their displayed label, not the identifier used by the application.
</Callout>


# FTP credentials


For a new connection, follow the [datalogger setup guide](/en/Monitoring/Integrations/datalogger-ftp). The customer or installer configures export on the logger using FTP credentials supplied by Eniris. Use the issued destination and folder settings for this connection.


import ClickableImage from '@/components/ClickableImage';

# FTP credentials

FTP credentials are provisioned for a specific data-ingestion workflow. Request them through the approved Eniris support channel and include:

- customer and installation name;
- source manufacturer and exact model;
- logger or portal identifier;
- expected file format and upload interval;
- the person responsible for configuring the source.

<ClickableImage src="/img/eniris/monitoring/screenshots/ftp-control-tool.webp" alt="SmartgridX FTP control tool with source identity, generated-password, and protocol controls" maxWidth="1140px" />

*The source identity belongs in the tool; the password itself should never be copied into documentation or screenshots.*

<Callout type="warning" title="Do not reuse or publish credentials">
  Store credentials in the organisation's approved password manager. Do not place them in documentation, tickets visible to unrelated users, screenshots, or public-display templates.
</Callout>

After configuration, verify both file arrival in the FTP tool and resulting telemetry in the correct installation. A successful login alone does not prove the mapping is correct.


# Validate historical-data accuracy


# Validate historical-data accuracy

Manufacturer, controller, and grid-operator totals can differ even when every system is functioning correctly. First determine whether the sources measure the same physical point and period.

## Common causes of differences

| Cause | Example |
| --- | --- |
| **Measurement location** | Inverter production is measured before cable and transformer losses; the grid meter is measured at the connection point. |
| **Different boundaries** | One source uses local midnight while another aggregates in UTC. |
| **Sampling and interpolation** | A portal estimates short gaps while the raw source leaves them empty. |
| **Counter resets or rollover** | Energy difference calculations cross a device reset. |
| **Late or missing files** | A daily upload arrives after a report was generated. |
| **Unit or scaling error** | Watts interpreted as kilowatts or a meter multiplier omitted. |
| **Asset mapping** | A file is attached to the wrong inverter or installation. |

## Validation method

1. Select one complete day without known outages.
2. Align both sources to the same timezone and boundaries.
3. Compare cumulative start and end values where available.
4. Compare energy totals, not only instantaneous power samples.
5. Repeat for a longer period.
6. Document the expected measurement-location difference.

<Callout type="warning" title="Do not assume a fixed acceptable percentage">
  The expected difference depends on measurement class, topology, cable losses, transformers, aggregation, and source processing. Investigate the physical and data boundaries before applying a generic tolerance.
</Callout>


# Add historical data


# Add historical data

Use the approved historical-import template for the active environment. The import must identify the target asset and timestamp for every row.

## Required identity fields

| Field | Requirement |
| --- | --- |
| **ID** | The exact installation or device ID that owns the measurement. |
| **time** | An unambiguous timestamp, preferably ISO 8601 with an offset or `Z`. |
| **timezone** | Required when the timestamp itself has no offset; use an IANA name such as `Europe/Brussels`. |

## Typical measurement fields

Supported import workflows can include fields such as:

- `actualPower_W`;
- `energyDelta_Wh`;
- phase or line voltages in volts;
- phase currents in amperes;
- temperature in degrees Celsius.

Use plain decimal notation without thousands separators. Do not convert watts to kilowatts or watt-hours to kilowatt-hours without also changing the field definition.

## Example

| ID | time | timezone | actualPower_W | energyDelta_Wh | temperature_C |
| --- | --- | --- | ---: | ---: | ---: |
| 123 | 2026-02-01T08:00:00Z | UTC | 15000.001 | 500.2 | 25.0 |
| 123 | 2026-02-01T08:15:00Z | UTC | 14800.750 | 490.0 | 24.8 |

When the same ID and timestamp occur more than once, duplicate handling depends on the importer. Remove unintended duplicates before upload and document intentional corrections.

## Import sequence

1. Export or create a small sample.
2. Verify headers, IDs, timestamps, timezone, and units.
3. Compare the interval with existing telemetry.
4. Import the sample.
5. Verify the resulting device chart and energy total.
6. Import the remaining approved range.
7. Record the source file and validation result.

[Download the example workbook](/img/generic/historic-data-example.xlsx)

<Callout type="warning" title="Back up the source file">
  Keep the original export unchanged. Perform cleaning or unit conversion in a separate working copy so every imported value remains traceable.
</Callout>


# Historical data


import { FolderOverview } from '@/components/FolderOverview';
import ClickableImage from '@/components/ClickableImage';

# Historical data

Historical imports are used to close a known data gap or migrate a trustworthy source into SmartgridX Monitoring. They should preserve the meaning of the original series rather than merely filling a chart.

## Safe import sequence

1. Identify the exact installation, device, signal, unit, and source timezone.
2. Export a small sample and verify delimiter, decimal separator, timestamp format, and counter behaviour.
3. Compare the requested interval with data that already exists.
4. Import a limited range first.
5. Validate the first point, last point, expected interval, and totals in the portal.
6. Only then import the full approved period.

<ClickableImage src="/img/eniris/monitoring/screenshots/ftp-control-tool.webp" alt="SmartgridX FTP control tool used before a supported historical-data workflow" maxWidth="1140px" />

<ClickableImage src="/img/eniris/monitoring/screenshots/power-meter-detail.webp" alt="An anonymized SmartgridX meter page used to validate imported intervals and totals" maxWidth="1140px" />

*Validate the imported range in the destination device context, not only in the source-transfer tool.*

<Callout type="warning" title="Do not interpolate operational history silently">
  Generated or estimated values must remain distinguishable from measured data. If a gap cannot be recovered from an authoritative source, document the gap instead of creating measurements that appear genuine.
</Callout>

## Historical-data guides

<FolderOverview folder="Monitoring/Web portal/features/ftp-tool/historical-data" />


# FTP and data import


import { FolderOverview } from '@/components/FolderOverview';
import ClickableImage from '@/components/ClickableImage';

# FTP and data import

The FTP tool supports data-ingestion workflows for environments that still receive files from devices or manufacturer platforms. In the current navigation it appears only for the company owner when `allowFtpTool` is enabled.

<ClickableImage src="/img/eniris/monitoring/screenshots/ftp-control-tool.webp" alt="SmartgridX FTP control tool for checking source credentials and protocol detection" maxWidth="1140px" />

*Use the control tool to verify the source identity and connection protocol before analysing imported data.*

## What to verify before importing

| Check | Why it matters |
| --- | --- |
| **Source identity** | Prevents data from being attached to the wrong installation or device. |
| **Timezone and timestamps** | Avoids shifted or duplicated measurements around midnight and daylight-saving changes. |
| **Units and counters** | Distinguishes instantaneous values from cumulative meter readings. |
| **Sampling interval** | Determines whether gaps are real or expected for the source. |
| **Existing data** | Prevents accidental duplicates or conflicting series. |

<Callout type="warning" title="FTP availability does not prove data quality">
  A successful file transfer only confirms delivery. Always verify the resulting timestamps, units, continuity, and installation mapping in Monitoring.
</Callout>

## FTP and import guides

<FolderOverview folder="Monitoring/Web portal/features/ftp-tool" />


# How the FTP tool is used


import ClickableImage from '@/components/ClickableImage';

# How the FTP tool is used

The FTP tool helps owners inspect file-based data delivery from supported loggers or manufacturer systems. It appears only when the organisation enables the FTP feature.

## Two separate checks

1. **Delivery check:** did the expected source upload a file at the expected time?
2. **Processing check:** was the file parsed, mapped to the correct asset, and converted into valid telemetry?

Use the FTP tool for the first check and the installation or device charts for the second.

<ClickableImage src="/img/eniris/monitoring/screenshots/ftp-control-tool.webp" alt="SmartgridX FTP control tool for checking source credentials and protocol detection" maxWidth="1140px" />

<ClickableImage src="/img/eniris/monitoring/screenshots/installation-overview.webp" alt="An anonymized SmartgridX installation overview used to verify processed telemetry" maxWidth="1140px" />

*A successful source check and a valid installation chart prove two different parts of the ingestion chain.*

## Record during troubleshooting

- source username or identifier, without its password;
- last successful upload time;
- expected upload frequency;
- filename and file timestamp;
- affected installation and device;
- first missing or incorrect measurement time;
- timezone used by the source.

<Callout type="info" title="Delayed uploads affect alarms and reports">
  No-data alarms, report delays, and historical completeness must reflect the actual source schedule. A daily file source should not be supervised like a continuously connected controller.
</Callout>


# Solar-Log FTP troubleshooting


For a new connection, follow the [datalogger setup guide](/en/Monitoring/Integrations/datalogger-ftp/solar-log). The customer or installer configures export on the logger using FTP credentials supplied by Eniris. Use the issued destination and folder settings for this connection.


# Solar-Log FTP troubleshooting

Use the following sequence to distinguish a Solar-Log configuration problem from a SmartgridX processing problem.

## 1. Confirm the source is online

Check whether recent data is visible in the local Solar-Log interface or manufacturer portal. If not, resolve power, internet, clock, or logger issues first.

## 2. Verify the destination

Compare the configured server address, protocol, port, username, remote path, and security mode with the issued credentials. A wrong destination can prevent any connection attempt; a wrong username can make the upload difficult to identify in source-specific logs.

## 3. Check network policy

Verify DNS resolution, outbound firewall rules, and any required passive-mode or TLS settings. Record the exact connection error shown by the logger.

## 4. Check file arrival

Use the FTP tool to identify the last file received for the source. Compare its timestamp and size with the expected upload interval.

## 5. Check processed telemetry

Open the mapped installation and compare the file time with the first or last resulting measurement. If the file arrived but no telemetry appears, provide the filename, source identifier, installation, and affected period to Support.

<Callout type="warning" title="Avoid repeated blind changes">
  Change one connection setting at a time and keep the exact error. Replacing several parameters simultaneously removes useful diagnostic evidence and can trigger claim or authentication rate limits.
</Callout>


# Operational features


import { FolderOverview } from '@/components/FolderOverview';
import ClickableImage from '@/components/ClickableImage';

# Operational features

SmartgridX Monitoring turns measured data into repeatable operational outputs. The current Insights application exposes these tools only when the organisation, view settings, and user rights allow them.

<Cards>
  <Card title="Virtual meters" description="Add, subtract, or scale measured signals in an analysis and export the calculated series with the chart data." href="./virtual-meters" />
  <Card title="Reports" description="Create report instances from configured templates, choose periods and recipients, control contained entities, and manage who may view or edit the report." href="./reports" />
  <Card title="Public displays" description="Build reusable slide templates, configure site-specific content, and link a display controller to the resulting presentation." href="./infographics" />
  <Card title="FTP and historical data" description="Import or recover data for supported workflows, while preserving timestamps, units, and source consistency." href="./ftp-tool" />
</Cards>

<ClickableImage src="/img/eniris/monitoring/screenshots/report-configurations.webp" alt="SmartgridX report-configuration page" maxWidth="1140px" />

*Reports turn a configured route, period, scope, and recipient list into a repeatable output.*

<ClickableImage src="/img/eniris/monitoring/screenshots/public-display-overview.webp" alt="SmartgridX public-display overview for controllers, templates, and documentation" maxWidth="1140px" />

*Public displays separate reusable templates, site configurations, and physical controllers.*

<ClickableImage src="/img/eniris/monitoring/screenshots/ftp-control-tool.webp" alt="SmartgridX FTP control tool for checking source credentials and protocol detection" maxWidth="1140px" />

*The FTP tool validates the source connection before an import or troubleshooting workflow continues.*

## Feature availability

| Feature | Code-backed availability rule |
| --- | --- |
| **Virtual meters** | The **Analyses** page must be available for the selected account; formulas use only measurement points the user can access. |
| **Reports** | The company must allow reports and the report page must be visible for the current role. |
| **FTP tool** | The company must own the view and the FTP-tool feature must be enabled. |
| **Public displays** | The company must own the view. Site-level public-display links additionally require administrator authority on a supported site. |

<Callout type="info" title="Configured routes define the actual output">
  Report and alarm templates point to dashboard routes configured for the active view. The portal only offers report routes ending in `-report` and alarm routes ending in `-alarm`, which prevents a template from being attached to an unrelated page.
</Callout>

## Feature guides

<FolderOverview folder="Monitoring/Web portal/features" />


# Site-specific display configuration


# Site-specific display configuration

An instance configuration resolves a reusable template for one installation. It is where site-specific images, measurements, and controller assignment come together.

## Open the site configuration

Open the installation and choose **Public displays** from its Features menu. The link is shown to administrators on supported site types.

![Navigation to a site's public-display configuration.](/img/generic/infographic-configuration-navigation.png)

The overview lists the configurations already associated with the site.

![The site configuration overview.](/img/generic/infographic-configuration-table.png)

## Create an instance

1. Choose **Add**.
2. Select a saved template.
3. Review the slides and configurable blocks.
4. Supply the site-specific values or assets.
5. Save the instance.

![Selecting a template for a new display instance.](/img/generic/infographic-configuration-add.png)

## Override supported blocks

Template defaults remain available when no override is required. The instance editor can replace supported content—particularly image configuration—without modifying the source template for other sites.

![Configuring site-specific display content.](/img/generic/infographic-configuration-configuration.png)

## Preview

Open **View** to render the resolved instance. Test at the target screen size and inspect every slide.

![Preview of a configured public display.](/img/generic/infographic-configuration-view.png)

Verify:

- correct installation and measurements;
- expected time ranges;
- image crop and resolution;
- readable typography;
- no missing or empty blocks;
- acceptable loading behaviour.

## Link a controller

After preview approval, link the instance to the intended claimed controller.

![Linking a display instance to a controller.](/img/generic/infographic-configuration-claim.png)

<Callout type="warning" title="Confirm the physical destination">
  Controller names are administrative labels. Verify the serial number or physical installation record before replacing an existing screen assignment.
</Callout>

## Change management

For a production display, preview changes before saving, record substantial template changes, and keep a rollback option. Updating a shared template can affect several site instances; updating an instance should affect only that site's resolved presentation.


# Public-display controllers


import ClickableImage from '@/components/ClickableImage';
import YouTubeEmbed from '@/components/YouTubeEmbed';

# Public-display controllers

A display controller is the endpoint that opens a public-display instance on a connected screen. Controller management is separate from template design and site-instance configuration.

<YouTubeEmbed
 videoId="zErgPJpKK7Y"
 videoIdNl="UFSzrPZ5dEA"
 videoIdFr="J6XqJUcRJKw"
 videoIdDe="TmuiJzOCCho"
 featured
/>

## Open controller management

From the owner-only **Public displays** area, open the controller overview.

<ClickableImage src="/img/eniris/monitoring/screenshots/public-display-controllers.webp" alt="SmartgridX public-display controller manager" maxWidth="1140px" />

*The controller manager is where you claim endpoints and review the controllers available to the organisation.*

![The controller section in the public-display overview.](/img/generic/infographic-controller-overview.png)

The table lists the controllers available to the organisation and provides the supported management actions.

![The public-display controller table.](/img/generic/infographic-controller-table.png)

## Claim a controller

1. Choose **Claim controller**.
2. Enter the serial number printed on the controller label.
3. Enter the verification code.
4. Submit the claim.
5. Confirm that the controller appears in the organisation table.

![The controller claim form.](/img/generic/infographic-claim-controller-form.png)

The claim component validates the supplied identity before the controller becomes available for linking.

## Name and link the controller

Use a name that identifies the physical destination, for example the site and screen location. The controller is linked from a saved site-instance configuration rather than directly from the template.

![A successfully claimed controller.](/img/generic/infographic-claimed-controller.png)

## Unclaim safely

Before unclaiming:

1. identify the linked instance and physical screen;
2. arrange a replacement when the display must remain online;
3. unlink or document the current assignment;
4. unclaim the controller;
5. confirm the screen no longer exposes stale content.

<Callout type="warning" title="Do not confuse controller types">
  A public-display controller is managed in the Infographic feature. A SmartgridOne energy controller is claimed from the global Add page and creates an energy-device hierarchy.
</Callout>


# Public displays quick start


# Public displays quick start

The public-display system uses three related objects:

1. a **template** defines reusable slides and block positions;
2. an **instance configuration** applies that template to one site;
3. a **controller** displays the resulting instance on a screen.

You can create and preview templates without hardware. Claim and link a controller only when the visual result is ready for deployment.

## Step 1: Create the template

Open **Public displays** and choose the template area.

![The public-display template overview.](/img/generic/infographic-template-overview.png)

1. Add a template and give it a descriptive title.
2. Configure the canvas margin.
3. Add one or more slides.
4. Add blocks to each slide.
5. Position and size the blocks.
6. Configure the block type and its defaults.
7. Save and preview.

The current code supports image, chart, and solar-overview block types. Chart blocks select a series type and range; image blocks support an uploaded image and preview.

![A template with positioned public-display blocks.](/img/generic/infographic-template-block.png)

## Step 2: Configure the site instance

Open the target installation and choose **Public displays** from the device Features menu. This site-level entry requires administrator authority on a supported site type.

![The site-level public-display configuration list.](/img/generic/infographic-configuration-table.png)

1. Add an instance configuration.
2. Select the template.
3. Override the supported block values for this site.
4. Save the configuration.
5. Open **View** to preview the resolved presentation.

## Step 3: Claim and link a controller

The global controller area is available to owners.

![The form used to claim a public-display controller.](/img/generic/infographic-claim-controller-form.png)

1. Enter the display controller serial number.
2. Enter its verification code.
3. Claim the controller.
4. Return to the site instance and link it to the intended controller.
5. Verify the result on the physical screen.

<Callout type="warning" title="Keep controller credentials private">
  Treat the serial number and verification code as provisioning credentials. Store them in the approved credential system and do not place them in a public document or display template.
</Callout>

## Final checks

- all blocks fit at the target aspect ratio;
- text remains readable at viewing distance;
- charts use the intended site and time range;
- uploaded images are appropriate for light and dark surroundings;
- no private operational data is exposed on a public screen;
- the linked controller is physically installed at the intended site.


# Public displays


import { FolderOverview } from '@/components/FolderOverview';
import ClickableImage from '@/components/ClickableImage';

# Public displays

The Insights code calls this feature **Infographic**, while the portal menu presents it as **Public displays**. It is built in three layers.

<ClickableImage src="/img/eniris/monitoring/screenshots/public-display-overview.webp" alt="SmartgridX public-display overview for controllers, templates, and documentation" maxWidth="1140px" />

*Start from controllers when managing a screen endpoint, or from templates when designing reusable content.*

| Layer | Purpose |
| --- | --- |
| **Template** | Defines slides, canvas margins, block positions, and reusable chart or image blocks. |
| **Instance configuration** | Connects a template to a specific site and supplies site-specific content or images. |
| **Controller** | Links the resulting presentation to a physical or browser-based display endpoint. |

Template editors can add and delete slides, set the title and canvas margin, position blocks by width and height, upload images, and configure chart series and time ranges. Instance editors can then override supported content without changing the reusable template.

<Callout type="info" title="Owner and site-admin access differ">
  The global public-display area is owner-only. A site-level infographic link is shown to administrators on supported site types so they can work with that site's configuration.
</Callout>

## Recommended workflow

1. Create or select a reusable template.
2. Add slides and define the layout blocks.
3. Configure chart sources, ranges, text, and images.
4. Create the site-specific instance.
5. Link or claim the display controller.
6. Preview the final result at the target screen size.

## Public-display guides

<FolderOverview folder="Monitoring/Web portal/features/infographics" />


# Public-display templates


# Public-display templates

A template is the reusable visual structure of a public display. It defines the slides, block geometry, and default content without binding the design to one installation.

## Template overview

The overview lists saved templates and supports adding, editing, and deleting them.

![The public-display template table.](/img/generic/infographic-template-table.png)

## Template-level settings

Give the template a clear title and configure the canvas margin. The editor uses a default canvas margin when a new template is created, which can then be changed for the target display.

![Template title and margin settings.](/img/generic/infographic-template-titlemargin.png)

## Slides

- add a slide for each distinct screen state or topic;
- delete obsolete slides deliberately;
- keep a consistent information hierarchy across slides;
- preview the complete rotation before deployment.

## Blocks and geometry

Each block has a position, width, and height. Select a block to edit its exact geometry or adjust it visually in the slide editor.

![A slide with multiple configurable blocks.](/img/generic/infographic-template-block.png)

The current code enforces minimum block dimensions and reports when no block is selected. Avoid edge-to-edge content unless the target screen's overscan and browser viewport have been tested.

## Supported block types

| Type | Use | Template configuration |
| --- | --- | --- |
| **Image** | Logo, photo, diagram, or decorative visual. | Upload, preview, replace, or remove the image. |
| **Chart** | Historical energy or operational trend. | Select the series type and supported range. |
| **Solar overview** | Site-oriented renewable-energy summary. | Uses the site context supplied by the instance. |

![The block-configuration panel.](/img/generic/infographic-template-blockconfig.png)

## Design recommendations

- design for the actual aspect ratio;
- use few large KPIs instead of many small values;
- give charts a clear visual purpose;
- reserve images for context or branding;
- keep margins consistent;
- avoid exposing technical identifiers on a public screen;
- verify colour contrast from the expected viewing distance.

## Save and validate

Save the template, return to the overview, and open it again before creating site instances. This confirms that slide order, geometry, uploaded assets, and chart configuration were persisted.

![A completed public-display template.](/img/generic/infographic-template-done.png)

<Callout type="warning" title="Deleting a template can affect instances">
  Check which site configurations depend on the template before deleting it. Prefer creating a new version when a production display needs a substantial redesign.
</Callout>


# Reports


import ClickableImage from '@/components/ClickableImage';

# Reports

The current reporting page manages **report instances**. A report instance combines a reusable template with a period, device scope, formatting, mail configuration, and access rules.

Reports are shown only when reporting is enabled for the organisation and the page is visible for the current role.

<ClickableImage src="/img/eniris/monitoring/screenshots/report-configurations.webp" alt="SmartgridX report-configuration page with an empty configuration list" maxWidth="1140px" />

*An empty list means that no report configuration is available in the current view; it is not a report-generation error by itself.*

## Template and instance model

| Object | Defines |
| --- | --- |
| **Report template** | Name, compatible dashboard route, allowed periods, and group-configuration rules. |
| **Report instance** | The selected template plus timezone, period, offset, delay, active dates, recipients, formatting, contained entities, and viewers. |

The template editor only offers configured dashboard routes whose path ends in `-report`. A template must have a name, route, at least one period, and valid group configuration before it can be saved.

## How report periods work

The report engine resolves the following values for each selected device group:

- **timezone** used for period boundaries;
- **period** such as day, week, month, or year;
- **offset** applied to the reporting window;
- **delay** between the end of a period and generation;
- **start and end dates** during which the report is active;
- **recipients** for distribution.

From these settings, the portal calculates the available content windows and their generation dates. You can choose one of those windows or use a supported custom range.

<Callout type="idea" title="Why a delay is useful">
  A monthly report does not always need to run at midnight on the first day of the next month. A delay gives slower data sources time to deliver their final measurements before the PDF is generated.
</Callout>

## Create a report instance

1. Open **Reports**.
2. Choose **Add** when your role has editing rights.
3. Select a compatible report template.
4. Choose the creator role and applicable device group.
5. Configure timezone, period, offset, delay, and active dates.
6. Configure backgrounds and page margins only when the template exposes them.
7. Add recipients and review the message language, subject, and body.
8. Save the instance.
9. Add contained devices or roles and configure viewer rights.
10. Preview or download a representative period before relying on automation.

## Scope and access

### Contained entities

Contained entities decide which devices or role-linked assets supply data to the report. This is separate from who may open the report configuration.

### Viewer management

Roles can be granted:

- viewing access;
- editing rights;
- permission to manage other viewers.

Keep editing and viewer-management rights limited to operational owners of the report.

## Mail configuration

Recipient resolution can use a supported simple strategy or a configured custom function. For the simple workflow, add the intended addresses, choose the language, and review the subject and body.

<Callout type="warning" title="Preview with real scope">
  A visually correct preview with the wrong device group, timezone, or period is still an incorrect report. Validate one known energy total and one known alarm or KPI before activating customer distribution.
</Callout>

## Troubleshooting

| Symptom | Check first |
| --- | --- |
| Template list is empty | The active view has no compatible `-report` route or no template is configured. |
| A period is unavailable | It is not included in the selected template's allowed periods. |
| No device group can be selected | The template's group configuration does not resolve against the contained entities. |
| Dates look shifted | Check the report timezone, offset, delay, and site timezone. |
| No email is sent | Check recipient resolution, active dates, generation date, and mail content. |
| User cannot edit | Check the role's report viewer entry and editing right. |


# Virtual meters


# Virtual meters

A **virtual meter** in SmartgridX is a calculated time series. It combines existing measurement points with addition, subtraction, and optional multiplication factors.

> [!IMPORTANT]
> A SmartgridX virtual meter is an **analysis tool**. It does not create a physical meter, change the controller topology, or become a control reference for the SmartgridOne controller.

## What you can calculate

| Question | Example formula |
| --- | --- |
| What is the combined power of two transformer feeders? | `Transformer total = Meter A + Meter B` |
| How much load is not covered by the known submeters? | `Unmetered load = Main meter - Submeter 1 - Submeter 2` |
| What is the total of several comparable assets? | `Asset total = Source 1 + Source 2 + Source 3` |
| Does a source require a conversion factor? | `Converted value = 0.001 x Source` |

Only combine signals with compatible units and sign conventions. SmartgridX warns when a formula contains mixed units, but it cannot decide whether the result is electrically meaningful.

## Create a virtual meter

1. Open **Analyses** in SmartgridX.
2. Select **Compare data** and choose the required period.
3. Add the real measurement points you want to inspect to the chart.
4. Under **Virtual meters**, select **Virtual meter**.
5. Give the calculated series a descriptive name, such as `Combined transformer power`.
6. For every source:
   - choose **+** to add it or **-** to subtract it;
   - enter a multiplication factor when required;
   - select the measurement point.
7. Check the resulting formula shown above the source list.
8. Select **Save as...** to retain the analysis for the current account.

The virtual series is drawn as a separate, highlighted line. Select **Export CSV** to export the plotted real and virtual series together.

## Example: two transformer meters

Suppose one site receives power through two transformers and each feeder has its own meter:

```text
Meter transformer A  ──┐
                       ├──  Combined transformer power = A + B
Meter transformer B  ──┘
```

Use the same power field and unit for both sources. Before using the result, verify the direction of each meter with a known import or export event. A reversed meter can make a correct formula produce an incorrect total.

## Example: calculate the unmetered remainder

If a main meter covers an entire switchboard while two branches have their own submeters, the remaining load can be estimated as:

```text
Unmetered remainder = Main meter - Branch meter A - Branch meter B
```

This result is intended for investigation and reporting. For continuous controller-side calculation, continue with the [setup guide](/Controller/Configuration%20from%20A%20to%20Z/11-Extra-Information/virtual-energy-meters/).

## How time series are combined

Sources do not always report at exactly the same timestamp. SmartgridX aligns the available samples and carries the latest known value forward between samples. The virtual line starts only after every source has delivered at least one value in the selected period.

This has practical consequences:

- a stale or missing source can leave the virtual meter empty or incomplete;
- very different reporting intervals can make short transients look less precise;
- formulas should normally use signals with the same retention period and unit;
- a saved analysis stores the formula, but it does not turn the result into a reusable device elsewhere in the portal.

## Analysis or controller configuration?

| You need to... | Use... |
| --- | --- |
| compare, add, or subtract arbitrary telemetry | **SmartgridX virtual meter** |
| export a calculated series with the chart data | **SmartgridX virtual meter** |
| calculate the unmeasured remainder below one real meter continuously | **SmartgridOne virtual energy submeter** |
| aggregate several physical meters for a shared control boundary | **advanced groups** in the controller |
| enforce separate limits for independent grid connections | separate electrical control boundaries; do not replace them with one analysis formula |

See [Virtual energy meters and meter aggregation](/Controller/Configuration%20from%20A%20to%20Z/11-Extra-Information/virtual-energy-meters/) for the controller-side options and their safety boundaries.

## Troubleshooting

| Observed problem | First check |
| --- | --- |
| The virtual line is empty | Every source must have data in the selected period. |
| The result has the wrong sign | Check the import/export convention and switch the affected source between addition and subtraction. |
| The result is unexpectedly large | Check the multiplication factors and units. |
| The formula disappears later | Save the analysis after editing the virtual meter. |
| The chart is correct but the controller does not react | This virtual meter is analysis-only; configure the controller topology separately. |


# Portal capabilities


import ClickableImage from '@/components/ClickableImage';

# Portal capabilities

SmartgridX Monitoring is not one fixed dashboard. The Insights application combines a device forest, configurable dashboard routes, page settings, feature flags, and role-based access into the portal shown to each user.

## Portfolio navigation

- Active installations are grouped by configured site tags.
- Empty site groups are omitted automatically.
- Search covers active solar installations and SmartgridOne controller sites.
- A controller serial number is included in search results when it is not already part of the site name.
- Company and view selection determine which portfolio and configuration are loaded.

<ClickableImage src="/img/eniris/monitoring/screenshots/portfolio-overview.webp" alt="An anonymized SmartgridX portfolio overview with alarm summaries and site comparison data" maxWidth="1140px" />

*The portfolio combines discovery, status, and comparison before you open an individual installation.*

## Device investigation

Every device can receive a different menu. Depending on its type, data, settings, and your authority, the portal can show:

- overview widgets;
- live and historical line charts;
- energy, performance-ratio, uptime, and irradiation bar charts;
- descendant-device groups and hierarchy management;
- Insights alarms and manufacturer alarm logs;
- remote controller access;
- targets, notes, contacts, documents, public displays, and data streams;
- device settings and page settings.

The current chart components cover active and reactive power, current, voltage, state of charge, temperature, irradiation, prices, pressure, flow, grid limits, insulation resistance, phase angle, angle differential, and configured overshoot signals. A chart is only rendered when a valid series exists for the selected device.

<ClickableImage src="/img/eniris/monitoring/screenshots/power-meter-detail.webp" alt="An anonymized SmartgridX power-meter detail page with time-range and chart controls" maxWidth="1140px" />

*Device pages keep the hierarchy, time controls, and relevant signal groups in one investigation context.*

## Operational management

| Capability | What the application supports |
| --- | --- |
| **Asset onboarding** | Claim a controller using a serial number and verification code, or create a supported virtual asset. |
| **User management** | Search roles and email addresses, assign members to roles, remove access with confirmation, and paginate large organisations. |
| **Advanced alarms** | Configure alarm templates, evaluation periods, instances, scope, delays, recipients, messages, and viewer rights. |
| **Reports** | Build report instances from templates, resolve device groups and periods, preview or download PDFs, and control recipients and viewers. |
| **Public displays** | Create slide templates, add chart and image blocks, configure site instances, and link display controllers. |
| **Historical data** | Import supported source data and validate its mapping, timestamps, units, and continuity. |

<ClickableImage src="/img/eniris/monitoring/screenshots/user-management.webp" alt="An anonymized SmartgridX user-management table with roles and member chips" maxWidth="1140px" />

<ClickableImage src="/img/eniris/monitoring/screenshots/alarm-management.webp" alt="An anonymized SmartgridX alarm overview grouped by installation" maxWidth="1140px" />

*Management covers both who may act and how the portfolio is supervised.*

## Access is part of the functionality

The code does not merely hide buttons cosmetically. Routes and menu entries are conditionally created from ownership, device authority, page visibility, organisation settings, and white-label flags.

<Callout type="info" title="Examples">
  Owners can see the global asset-add and public-display areas. User management is available to owners and qualifying site administrators. Reports and FTP require explicit feature settings. Advanced alarms is only routed when enabled for the active white-label environment.
</Callout>

<ClickableImage src="/img/eniris/monitoring/screenshots/dashboard-page-permissions.webp" alt="SmartgridX dashboard settings showing page visibility for different portal roles" maxWidth="1140px" />

*Role relationships and page settings work together to determine the final navigation.*

## A practical operating loop

1. Use the portfolio overview to identify an exception.
2. Open the site and read the highest-level energy or status view.
3. Follow the hierarchy to the device that explains the behaviour.
4. Compare the relevant signals over the same time range.
5. Check alarms, manufacturer logs, notes, and maintenance context.
6. Assign follow-up through users, contacts, alarm notifications, or reports.
7. Confirm that the site returns to its expected state.

<ClickableImage src="/img/eniris/monitoring/screenshots/installation-overview.webp" alt="An anonymized SmartgridX installation overview used in the operating loop" maxWidth="1140px" />


# Portfolio and homepage


import { FolderOverview } from '@/components/FolderOverview';
import ClickableImage from '@/components/ClickableImage';

# Portfolio and homepage

The first useful level of SmartgridX Monitoring is the portfolio view. Its purpose is not to show every signal at once, but to help you decide which installation deserves attention.

<ClickableImage src="/img/eniris/monitoring/screenshots/portfolio-overview.webp" alt="An anonymized SmartgridX portfolio overview with alarm summaries and a site comparison table" maxWidth="1140px" />

*The portfolio combines fleet-level alarm signals with comparable site KPIs. The example data and names are anonymized.*

## Installation groups

The current portal creates installation-menu items from active site tags. A tag is only shown when at least one active site uses it. Selecting a group opens the corresponding site view with that tag as a filter.

This means the labels in your portal may be organisation-specific. A portfolio can, for example, separate solar installations, wind farms, controller sites, or customer-defined categories without changing the underlying application.

## Search for a site

Use the installation search in the navigation to jump directly to an active solar installation or SmartgridOne controller site. For controllers, the serial number is appended when the installation name does not already contain it.

## Choose the right layout

| Layout | Best for | Typical question |
| --- | --- | --- |
| **Table** | Comparing the same KPIs across many sites and sorting operational exceptions. | Which site has the lowest yield, uptime, or latest data timestamp? |
| **Tiles** | Scanning a smaller portfolio visually and presenting selected KPIs prominently. | Which installations need a quick follow-up? |

The exact columns, tiles, and actions come from the configured dashboard route and page settings. Owners can expose different elements to visitors than to administrators.

<Callout type="idea" title="Start broad, then drill down">
  Use the portfolio view to identify an exception. Open that installation, compare its energy flow and KPIs, then move to the device or signal that explains the difference.
</Callout>

## Homepage guides

<FolderOverview folder="Monitoring/Web portal/homepage" />


# Configure the table layout


import ClickableImage from '@/components/ClickableImage';

# Configure the table layout

The table layout is best for comparing the same KPI across many installations. Its exact columns are defined by the configured dashboard route and page settings rather than one universal SmartgridX schema.

<ClickableImage src="/img/eniris/monitoring/screenshots/installation-search.webp" alt="An anonymized SmartgridX installation search opened above the portfolio table" maxWidth="1140px" />

*Use the global installation search to jump directly to an asset; use the table search when you only want to filter the current portfolio.*

<ClickableImage src="/img/eniris/monitoring/screenshots/portfolio-element-selection.webp" alt="SmartgridX portfolio element selection for owners and visitors" maxWidth="1140px" />

*Page settings can expose different portfolio elements and alarm tiles to owners and visitors.*

## Temporary column selection

Use the table's column selector to show or hide columns for the current working session. This is useful during an investigation when you want to focus on a small set of signals without changing the default for other users.

## Table behaviour by audience

<ClickableImage src="/img/eniris/monitoring/screenshots/portfolio-table-behaviour.webp" alt="SmartgridX portfolio settings for alarm tiles, sorting, and page size" maxWidth="1140px" />

*The owner and visitor views can have different alarm tiles, sort fields, sort order, page size, and initial filters.*

## Persistent visibility

When your role exposes page settings:

1. Open the page-settings action for the portfolio view.
2. Find the column or element-selection section.
3. Choose the applicable audience or authority.
4. Enable only columns that have a clear operational purpose.
5. Save and reload the portfolio as that audience.

<ClickableImage src="/img/eniris/monitoring/screenshots/portfolio-column-selection.webp" alt="SmartgridX persistent column selection for owner and visitor audiences" maxWidth="1140px" />

*Persistent column settings are configured separately for owners and visitors.*

## Recommended column groups

| Purpose | Useful columns |
| --- | --- |
| **Data freshness** | Last measurement, communication state, or uptime. |
| **Production** | Active power, energy, specific yield, and performance ratio. |
| **Storage** | State of charge, charge/discharge power, and availability. |
| **Grid** | Import/export power, energy, and configured limits. |
| **Follow-up** | Active alarm count, status, owner, or contact where configured. |

<Callout type="warning" title="Hidden does not mean disabled">
  Removing a column from a table changes presentation only. It does not stop telemetry, alarms, reports, or device operation.
</Callout>


# Configure the tile layout


import ClickableImage from '@/components/ClickableImage';

# Configure the tile layout

Tiles provide a fast visual scan of selected installation information. The current portal reads the available elements from the configured dashboard page and can apply different visibility settings for owners and visitors.

<ClickableImage src="/img/eniris/monitoring/screenshots/portfolio-element-selection.webp" alt="Portfolio tile and element visibility settings for owner and visitor roles" maxWidth="1140px" />

*Enable only the tiles that help each audience decide what to inspect next.*

## Configure visible tiles

1. Open the portfolio view for the relevant installation group.
2. Open its page settings when your role permits it.
3. Select the element or tile visibility section.
4. Choose the audience whose view you are changing.
5. Keep the most decision-relevant tiles visible and save.
6. Verify the result using the intended role or preview mode.

## Design a useful tile set

- include one freshness or availability indicator;
- show the dominant energy flow or production KPI;
- add state of charge for storage portfolios;
- expose alarm state when the viewer is expected to act;
- avoid repeating the same value in several visual forms;
- keep customer views simpler than operational views.

<Callout type="idea" title="Use tiles for triage, charts for diagnosis">
  A tile should help the reader decide where to click next. Detailed time-series interpretation belongs on the installation or device page.
</Callout>


# Portfolio video guide


# Portfolio video guide

This walkthrough demonstrates the portfolio and homepage workflow.

<iframe
  title="SmartgridX portfolio walkthrough"
  width="100%"
  height="420"
  src="https://www.youtube.com/embed/2wh5yph9Igs"
  allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture"
  allowFullScreen
></iframe>

The current portal builds site groups from active tags and filters menu items by role and configuration. If the recording differs from your interface, use the current [Portfolio and homepage](./) guide.


# Web portal


import { FolderOverview } from '@/components/FolderOverview';
import ClickableImage from '@/components/ClickableImage';
import { MonitoringScopeMap } from '@/components/MonitoringScope';

# SmartgridX Monitoring web portal

The web portal is built around an energy-asset hierarchy. You start with a portfolio or site-type overview, open an installation, move through its descendant devices, and inspect the charts or operational tools that are relevant to that device.

The portal is intentionally configuration-driven. The Insights application builds its navigation from the active company, selected view, available site tags, connected device types, page settings, feature licences, and your role. Two users can therefore have a different menu without either view being incorrect.

## What SmartgridX monitors

SmartgridX connects a portfolio overview to the technical structure inside every site. Depending on the integration, you can move from a complete installation to individual inverters, batteries, meters, chargers, MPPT trackers, PV strings, battery racks, cells, phases, connectors, and finally their measurements or alarms.

<MonitoringScopeMap
  ariaLabel="SmartgridX monitoring levels"
  eyebrow="Monitoring depth"
  title="From an entire portfolio to one PV string"
  description="SmartgridX keeps every measurement in its operational context. Start broad, find the site that deviates, and drill down until the responsible device, component, or signal becomes visible."
  badge="Hierarchy-aware"
  levels={[
    { label: "Level 01", title: "Portfolio", summary: "Compare sites, rank exceptions, and see where attention is needed.", examples: ["Fleet KPIs", "Site comparison", "Alarm state"] },
    { label: "Level 02", title: "Installation", summary: "Understand the complete energy balance at one physical site.", examples: ["Grid exchange", "Generation & load", "Site availability"] },
    { label: "Level 03", title: "Asset", summary: "Investigate the individual device responsible for the site behaviour.", examples: ["Inverter", "Battery or BMS", "Meter or charger"] },
    { label: "Level 04", title: "Subcomponent", summary: "Drill into the internal structure when the connected system exposes it.", examples: ["MPPT & PV string", "Rack, module or cell", "Phase or connector"] },
    { label: "Level 05", title: "Signal & event", summary: "Follow the measurement, state, or alarm that explains what changed.", examples: ["Power & energy", "Voltage & current", "Status & alarms"] },
  ]}
  drillDownEyebrow="Example drill-down"
  drillDownTitle="Follow one production anomaly to its source"
  drillDown={[
    { label: "Portfolio", value: "Solar fleet" },
    { label: "Installation", value: "Warehouse site" },
    { label: "Asset", value: "Inverter 02" },
    { label: "Component", value: "MPPT 1" },
    { label: "Component", value: "String 1" },
    { label: "Signal", value: "DC current" },
  ]}
  noteTitle="The available depth is integration-specific."
  noteText="SmartgridX can show MPPTs, strings, battery racks, cells, phases, and connectors only when the device, gateway, or API exposes those objects and signals."
/>

For the complete asset overview, signal families, and integration limitations, read [What we monitor](./what-we-monitor).

## How the current portal is organised

| Area | What it is for | When it appears |
| --- | --- | --- |
| **Installation groups** | Open active sites grouped by configured site tags, such as solar, wind, storage, or controller sites. | Only tags that contain active sites are shown. |
| **Search** | Jump directly to an active solar installation or SmartgridOne controller site. Controller serial numbers are included when useful. | Available in the SmartgridX navigation. |
| **Installation detail** | Inspect widgets, line charts, bar charts, descendants, alarms, targets, contacts, documents, data streams, and settings. | The menu is assembled per device type and role. |
| **Management** | Add assets, assign users, configure alarms, and manage installation visibility. | Primarily for owners, administrators, and installers with the required rights. |
| **Features** | Work with reports, data import tools, and public displays. | Depends on portal settings and enabled licences. |
| **Profile** | Review the signed-in email address and change the account password. | Available to every authenticated user. |

<Callout type="info" title="A missing menu item is usually intentional">
  Reports require reporting to be enabled. The FTP tool requires its feature flag. Public-display management is owner-only. User management is shown to owners and administrators of supported site types. Device sections are also filtered by page settings and role.
</Callout>

<ClickableImage src="/img/eniris/monitoring/screenshots/portfolio-overview.webp" alt="An anonymized SmartgridX portfolio overview with alarm summaries and a site comparison table" maxWidth="1140px" />

*The portfolio is the starting point for locating a site and deciding which installation needs attention.*

<ClickableImage src="/img/eniris/monitoring/screenshots/installation-overview.webp" alt="An anonymized SmartgridX installation overview with hierarchy, summary, and charts" maxWidth="1140px" />

*Opening an installation changes the context from portfolio comparison to device-level investigation.*

## Recommended learning path

<Cards>
  <Card title="1. Understand the monitoring scope" description="See which assets, components, signals, and hierarchy levels SmartgridX can expose." href="./what-we-monitor" />
  <Card title="2. Navigate the portfolio" description="Learn how site groups, search, table views, and tile views help you find the right installation." href="./homepage" />
  <Card title="3. Investigate an installation" description="Follow the device hierarchy and learn which widgets, charts, alarms, and tools can appear." href="./installations" />
  <Card title="4. Configure operations" description="Add assets, assign access, supervise alarms, and manage the portfolio safely." href="./management" />
  <Card title="5. Use portal features" description="Create virtual meters and reports, import historical data, and build public displays." href="./features" />
</Cards>

<ClickableImage src="/img/eniris/monitoring/screenshots/public-display-overview.webp" alt="SmartgridX public-display overview illustrating one of the owner-only operational feature areas" maxWidth="1140px" />

## Current portal versus legacy portal

The articles in this section describe the current SmartgridX interface found in the Insights codebase. The separate **Legacy web portal** folder remains available for organisations that still use the previous interface; buttons, menu names, and workflows in those articles should not be assumed to match the current portal.

## All web-portal documentation

<FolderOverview folder="Monitoring/Web portal" />


# Add an installation or asset


import ClickableImage from '@/components/ClickableImage';

# Add an installation or asset

The global **Add** page is available to company owners and contains two code-backed workflows.

<ClickableImage src="/img/eniris/monitoring/screenshots/claim-controller-and-add-asset.webp" alt="SmartgridX forms for claiming a controller and creating a virtual asset" maxWidth="1140px" />

*Claim an existing controller with its verification details, or create a virtual parent for organisational purposes.*

## Claim a SmartgridOne controller

Use this workflow when the controller already exists and should be linked to the current company.

1. Open **Add** in the SmartgridX navigation.
2. Enter the controller serial number.
3. Enter the verification code supplied for that controller.
4. Submit the claim.
5. Confirm that the controller site and its hierarchy appear in the expected installation group.

The application normalises the serial number to uppercase and validates missing serial numbers, missing verification codes, unknown controllers, invalid codes, and recent failed attempts.

<Callout type="warning" title="Use the code for the intended controller">
  Claiming creates a management relationship with the controller hierarchy. Verify the serial number, company, and view before submitting; do not test with a production controller owned by another organisation.
</Callout>

## Create a virtual asset

Use this workflow for a supported manually managed node type.

1. Open **Add**.
2. Enter a clear asset name.
3. Select one of the node types marked as creatable by the application.
4. Submit the form.
5. Configure its hierarchy, monitoring relations, streams, and visibility as required.

The new asset receives a generated identifier beginning with `custom-` and initially has no descendants or telemetry series.

## After adding

- assign the correct site tag;
- confirm timezone and location;
- verify whether it should be active and included in monitored tables;
- assign users and contacts;
- check whether charts receive valid streams;
- configure alarms, targets, reports, and public displays only after the hierarchy is correct.


# Documents


import ClickableImage from '@/components/ClickableImage';

# Documents

The **Documents** entry appears in a device's Features menu when document visibility is enabled for that device type and authority.

## Good uses

- single-line diagrams and wiring plans;
- commissioning and acceptance records;
- datasheets and certificates;
- maintenance instructions;
- approved site photographs;
- grid or regulatory documents intended for the portal audience.

## Upload and organisation

1. Open the exact installation or device that owns the document.
2. Choose **Documents** from its Features menu.
3. Select the configured document type.
4. Upload a supported file extension.
5. Use a clear filename with revision or date where applicable.
6. Confirm the document opens for the intended role.

<ClickableImage src="/img/eniris/monitoring/screenshots/document-upload.webp" alt="An anonymized SmartgridX document upload form for an installation" maxWidth="1140px" />

*Choose the configured document type before selecting the file. The available types come from dashboard settings.*

Document types and allowed file extensions are configured in dashboard settings.

<Callout type="warning" title="Respect document access">
  A document inherits the context and visibility of its portal location. Do not upload credentials, private contracts, or personal data unless the configured audience and retention policy explicitly allow it.
</Callout>


# Installation features


import { FolderOverview } from '@/components/FolderOverview';
import ClickableImage from '@/components/ClickableImage';

# Installation features

The **Features** menu on a device is assembled dynamically. It only appears when at least one applicable feature is visible for that device type and role.

<ClickableImage src="/img/eniris/monitoring/screenshots/installation-features-menu.webp" alt="An anonymized SmartgridX installation with the Features menu open" maxWidth="1140px" />

*The available entries follow the selected asset, its capabilities, the page settings, and your role.*

## Features that can appear

| Feature | Purpose | Main visibility condition |
| --- | --- | --- |
| **Remote** | Open the SmartgridOne remote session in a new browser tab. | Controller site with a serial number; administrator or installer. |
| **Targets** | Store production or performance expectations used in comparisons and reports. | Enabled in the page settings for that device and role. |
| **Notes and maintenance** | Record operational observations and maintenance context. | Contact features enabled for that device and role. |
| **Contacts** | Associate people and recipient information with the device. | Contact features enabled for that device and role. |
| **Documents** | Keep device-related documents available from the installation hierarchy. | Document features enabled for that device and role. |
| **Public displays** | Configure a site-specific infographic instance. | Administrator on a supported site type. |
| **Data streams** | Inspect the telemetry streams associated with the device. | Stream visibility enabled for that device and role. |

<Callout type="info" title="The feature list is device-specific">
  An inverter, meter, battery, controller site, and portfolio node do not necessarily expose the same tools. This is expected and follows both device capabilities and dashboard configuration.
</Callout>

## Operational context and stream mapping

<ClickableImage src="/img/eniris/monitoring/screenshots/notes-maintenance-overview.webp" alt="The notes and maintenance overview for an anonymized installation" maxWidth="1140px" />

*Notes and maintenance activities keep time-bound operational context next to the asset it describes.*

<ClickableImage src="/img/eniris/monitoring/screenshots/data-stream-configuration.webp" alt="An anonymized data-stream configuration showing calculation modes and scaling" maxWidth="1140px" />

*Data streams explain where a measurement comes from and whether it is embedded, summed, averaged, offset, or scaled.*

## Installation feature guides

<FolderOverview folder="Monitoring/Web portal/installations/features" />


# Production, PR, and uptime targets


import ClickableImage from '@/components/ClickableImage';
import CustomerOnly from '@/components/CustomerOnly';

# Production, PR, and uptime targets

The current page settings distinguish two target groups:

- **expectations** for planned or benchmark performance;
- **warranties** for contracted or guaranteed performance.

Each group can expose production, performance ratio, and uptime independently.

## Production expectation

Use an energy target when an approved forecast or budget exists for the same installation boundary and period. Monthly targets are usually more useful than one annual number because they preserve the seasonal profile.

## Performance-ratio expectation

PR compares production with installed capacity and irradiation. Before using a PR target, verify:

- installed DC capacity;
- irradiation source and plane;
- timezone and daily boundaries;
- curtailment or availability treatment;
- whether the target is an expectation or a warranty.



## Uptime expectation

Define uptime against the operating window in which the asset is expected to be available. Excluding night-time or planned maintenance may be appropriate, but the rule must be documented and consistent with reporting.

## Recommended workflow

<ClickableImage src="/img/eniris/monitoring/screenshots/target-configuration.webp" alt="An anonymized SmartgridX target configuration for a monitored installation" maxWidth="1140px" />

*Use the same target screen to review the selected node, target type, period, and configured value before saving.*

1. Identify the approved source for the target.
2. Confirm unit, period, installation boundary, and version.
3. Enter the expectation or warranty values.
4. Compare them with one known period.
5. Verify the corresponding bar chart or report output.
6. Record changes after repowering, extension, or contract revision.

<Callout type="warning" title="Do not mix expectation and warranty">
  A business forecast and a contractual guarantee can use different assumptions. Store them in the appropriate group and explain the difference to report recipients.
</Callout>


# Targets


import { FolderOverview } from '@/components/FolderOverview';
import ClickableImage from '@/components/ClickableImage';

# Targets

Targets add context to measured production. A chart can tell you what happened; a target tells you whether that result was expected for the installation and period.

The target page is shown only when it is enabled for the current device type and user role. The available target fields can depend on the asset configuration.

## Typical target workflow

1. Confirm the installation capacity, location, and panel configuration where applicable.
2. Choose whether the target is entered as energy, specific yield, or another supported performance reference.
3. Enter or review the values for the relevant periods.
4. Compare measured performance with the target in dashboards or reports.
5. Revisit the target after a material system change, such as an extension or repowering.

<ClickableImage src="/img/eniris/monitoring/screenshots/target-configuration.webp" alt="An anonymized SmartgridX performance-ratio target configuration" maxWidth="1140px" />

*Add a period and its reference value; the overview then keeps each target period explicit and reviewable.*

<Callout type="warning" title="A target is not a measurement">
  Targets are planning and comparison values. Do not use them to fill missing telemetry or to hide a data-quality problem.
</Callout>

## Target guides

<FolderOverview folder="Monitoring/Web portal/installations/features/targets" />


# Installations and devices


import { FolderOverview } from '@/components/FolderOverview';
import ClickableImage from '@/components/ClickableImage';

# Installations and devices

An installation page is the bridge between a portfolio exception and its technical explanation. The current portal constructs the page from the selected device, its ancestry and descendants, valid telemetry series, page settings, and your authority on that device.

<ClickableImage src="/img/eniris/monitoring/screenshots/installation-overview.webp" alt="An anonymized installation overview with a device hierarchy, production summary, and active-power chart" maxWidth="1140px" />

*Use the hierarchy to select context, the summary to assess the day, and the chart to locate when behaviour changed. Names and values in the example are anonymized.*

## The device hierarchy

The URL and device menu preserve the complete ancestry of the selected device. This lets the portal understand whether you are looking at a site, inverter, meter, battery, charger, sensor, or another descendant—and which parent context belongs to it.

The **Descendant devices** menu groups available children by node type. It also provides a hierarchy-management link when the current device can contain child devices. Inactive children can be hidden from normal navigation while remaining part of the stored structure.

This hierarchy can continue below a device. A PV inverter may expose MPPT trackers and strings; a battery may expose a BMS, racks, modules, or cells; a meter may expose phases or circuits; and an EV charger may expose connectors. Which children appear depends on the connected integration. See [What SmartgridX monitors](../what-we-monitor) for the complete visual hierarchy and asset overview.

<ClickableImage src="/img/eniris/monitoring/screenshots/descendant-devices-menu.webp" alt="An anonymized installation hierarchy with the Descendant devices menu open" maxWidth="1140px" />

*The hierarchy keeps parent context visible while the menu narrows the next step to links or a specific descendant type.*

## What appears on the overview

The overview renders only groups that have valid content:

| Group | Examples in the current code |
| --- | --- |
| **Widgets** | Solar summary, savings information, and configured image tiles. |
| **Line charts** | Active power, reactive power, current, voltage, state of charge, temperature, irradiation, price, pressure, flow, grid limit, insulation resistance, angle, angle differential, and length overshoot. |
| **Bar charts** | Active energy, performance ratio, uptime, and radiant exposure. |

Chart height adapts to the viewport. All charts in a group share the selected range and pointer context where applicable, which makes signals easier to compare over the same moment and interval.

<Callout type="info" title="No chart can be a valid result">
  A chart group is omitted when the device has no valid matching telemetry series or when page settings hide it. First verify the device type, selected period, stream mapping, and role before treating a missing chart as a software fault.
</Callout>

## Device-menu sections

### Overview

Shows the configured widgets and chart groups for the selected device.

### Descendant devices

Opens a filtered list for a specific child type or the hierarchy-management view.

### Alarms

Can show both Insights alarms and manufacturer alarm logs. Controller alerting is a separate Eniris-only action for supported controller sites.

<ClickableImage src="/img/eniris/monitoring/screenshots/alarm-management.webp" alt="An anonymized SmartgridX alarm overview grouped by installation" maxWidth="1140px" />

*Use the Insights alarm overview for configured monitoring rules and their current state.*

<ClickableImage src="/img/eniris/monitoring/screenshots/manufacturer-alarm-log.webp" alt="The SmartgridX manufacturer alarm log with grouping, filtering, and time controls" maxWidth="1140px" />

*The manufacturer log is a separate technical source and can reveal device-originated events that are not Insights alarm instances.*

### Features

Can include:

- remote controller access for administrators and installers;
- targets;
- notes and maintenance;
- contacts;
- documents;
- site-level public displays;
- data streams.

<ClickableImage src="/img/eniris/monitoring/screenshots/installation-features-menu.webp" alt="An anonymized SmartgridX installation with the complete Features menu open" maxWidth="1140px" />

*The menu is assembled for the selected device and authority, so another site or role can show fewer entries.*

### Settings

Contains device-specific configuration when enabled for the current authority. Owners can also receive a direct page-settings link for the configured device route.

<ClickableImage src="/img/eniris/monitoring/screenshots/installation-management-controls.webp" alt="An anonymized SmartgridX installation settings page with visibility and management controls" maxWidth="1140px" />

*Settings combine ordinary configuration with higher-impact management actions; verify the selected installation before saving.*

## Investigation workflow

1. Confirm the installation and the time of the reported behaviour.
2. Read the site-level power flow or summary values.
3. Use line charts to identify which signal changed first.
4. Open the relevant child-device group and compare siblings.
5. Check Insights alarms and the manufacturer log separately.
6. Review notes, maintenance, documents, targets, or data streams for context.
7. Escalate with the site, device, signal, time range, and observed values.

## Installation actions exposed by the portal

<Cards>
  <Card title="Add an asset" description="Claim a controller or create a supported virtual asset." href="./add" />
  <Card title="Remove or hide an asset" description="Choose between visibility changes, unclaiming a controller, and deleting a custom asset." href="./remove" />
  <Card title="Installation features" description="Learn about targets, documents, contacts, notes, displays, and streams." href="./features" />
</Cards>

## All installation guides

<FolderOverview folder="Monitoring/Web portal/installations" />


# Remove, hide, or unclaim an asset


import ClickableImage from '@/components/ClickableImage';

# Remove, hide, or unclaim an asset

The current device-management code distinguishes visibility changes from structural removal.

## Choose the correct action

| Intent | Action |
| --- | --- |
| Keep history but hide the asset from normal navigation | Disable **Show installation/asset**. |
| Keep the asset active but exclude it from the monitored overview | Disable **Show in monitored table**. |
| Detach a SmartgridOne controller from the company | Use **Unclaim** on the controller site. |
| Delete a manually created virtual asset | Use **Delete** on an asset whose identifier begins with `custom-`. |

<ClickableImage src="/img/eniris/monitoring/screenshots/installation-management-controls.webp" alt="An anonymized SmartgridX installation settings page with visibility and delete controls" maxWidth="1140px" />

*Visibility and monitoring controls are reversible presentation choices; Delete is a structural action and must be treated separately.*

## What unclaiming does

For a controller site, the application identifies the controller role, gathers monitor relations for the complete hierarchy, removes the current company's applicable monitor relations, and removes the company-to-controller management relation. The controller itself is not treated like a `custom-` virtual asset.

## What deleting a custom asset does

For a manually created asset, the application removes monitor relations for which the current role has management rights. This can immediately remove the asset from the current portfolio.

<Callout type="warning" title="Confirm dependencies first">
  Before a structural removal, check users, reports, alarm scopes, public displays, contacts, documents, targets, API references, and historical-data expectations. Prefer a visibility change when the business intent is only to stop day-to-day monitoring.
</Callout>

## Verification after the change

1. Reload the portfolio and search for the asset.
2. Confirm that unrelated companies or views are unaffected.
3. Check alarm and report scopes for stale references.
4. Record the reason, operator, and effective date in the operational ticket or maintenance record.


# Account Settings


import { BrandName, ControllerName, CustomerName, InsightsName, InsightsUrl } from '@site/src/components/customFields';
import ClickableImage from '@site/src/components/ClickableImage';

On this page you are able to change your password and username by filling in the fields. 


<ClickableImage src="/img/eniris/AccountSettings.png" alt="Account Settings" maxWidth="800px" />

# Adding a New Alarm


import { BrandName, ControllerName } from '@site/src/components/customFields';
import ClickableImage from '@site/src/components/ClickableImage';

# Adding a new alarm
To add an alarm you need to enter 3 fields.

- Type: This is to say what type of alarms you want to get an email for. (This depends on what you configured in the datapoints themself)

- Creator role: For this you look for the building you want an alarm for. This is only per building so you'll need to set up multiple alarms like this if you have more buildings. Here you pick one of the roles, this does not matter what.

- Description: Name of your alarm. I recommend using type of alarm - name of building. This keeps it easy to manage.

When these are filled in you can click on 'Frequency' and go to the next step.


<ClickableImage src="/img/eniris/AddAlarm.png" alt="Add alarm" maxWidth="800px" />

## Frequency

This is standard set to the highest frequency. You don't want to edit this. Now you have to click on 'Actions' and go to the next step.

Deprecated:

- Advanced settings

<ClickableImage src="/img/eniris/AddAlarmFrequency.png" alt="Add alarm frequency" maxWidth="800px" />


## Actions

Once here you need to click on the top most 'Add'. This will add a mail action. 

You can then press this to open the menu as shown in the screenshot.

Configuration:

You can make 2 alarms if this is needed. 1 for when the alarm is triggered and 1 for when it' back to normal. This can be configured with the 'Alarm status' and adding 2 actions (1 for each).

On the receivers, you can select 'Fixed'. This will show a box where you can add the emails of the people you want to receive the email.

You can select a language to set up mails for specific languages.

The subject will just be the subject of the email. You can see there is a parameter defined here date this will show the date of the alarm. Later in this tutorial you will see more parameters.

Content is used for the email itself. This uses #points to iterate over each point that's triggered if multiple points have triggered.

When you're done setting this up (you can also do this later), you can click on the bottom side 'Add' and continue to the next step.

<ClickableImage src="/img/eniris/AddAlarmActions.png" alt="Add alarm actions" maxWidth="800px" />


## Supervised objects

When you're done with the last steps you will need to go back to the settings icon and find 'Supervised objects'. Then select the site again that you want to overview. If this is done you can go to the next step.

<ClickableImage src="/img/eniris/Supervised.png" alt="Add alarm supervised objects" maxWidth="800px" />

## Viewer management


Don't do this but this is information to remove an alarm.

When clicking in the menu to 'Viewer management', you will find the delete button if you want to remove an alarm. Removing all accounts will permanently delete the alarm.


<ClickableImage src="/img/eniris/ViewerManagement.png" alt="Add alarm viewer management" maxWidth="800px" />


## Testing the alarm

Now all steps are correctly executed and you need to go back to the overview page of the alarms. There you need to find your alarm and click on it. If you see the 'View' button, press it.

<ClickableImage src="/img/eniris/TestingAlarm.png" alt="Add alarm view" maxWidth="800px" />

## Final result

If you now see a page like this with a table your alarm will work. You can also see what datapoints are currently being watched for this building here. 

If you have further questions or something does not work and you checked every step, please contact support.
https://eniris.io/support-ticket/
<ClickableImage src="/img/eniris/FinalResult.png" alt="Add alarm final result" maxWidth="800px" />

# Alarm Configuration


import { BrandName, ControllerName } from '@site/src/components/customFields';
import ClickableImage from '@site/src/components/ClickableImage';


This is the first step in configuring alarms. Here we will specify what type of alarm and when it is triggered. Also here we can check why it triggered.

This also has a direct link to the Alarms page in the sidebar. This is because these two features are linked to each other.

Deprecated: 

- Settings (classic/ contact list): I don't recommend using this. There is a better way to add emails. You can see this on the Alarms manual for the side bar. This will also be linked on this page. 


<ClickableImage src="/img/eniris/AlarmConfiguration.png" alt="Alarm configuration" maxWidth="800px" />

## Data 
In this part you can say how the data is read, if you want real-time or averages and what interval. For example I want to see if the data has been under a certain threshold for the last 7 days. Then you can select 'Last 7 days' and configure how much the data can be for that period in the next part.

<ClickableImage src="/img/eniris/AlarmConfigurationData.png" alt="Alarm configuration data" maxWidth="800px" />


## Alarm type + threshold

Here we can set the actual parameters of the alarm. In this case I set up an alarm for when the datapoint is:

- Offline

- Doesn't get data for 300 minutes (5 hours)

<ClickableImage src="/img/eniris/AlarmConfigurationAlarmType.png" alt="Alarm configuration alarm type" maxWidth="800px" />


## Window

On this step we can specify when in the day this is going to be active. This is useful for when you have for example: 

Solar panels if you want know that they're not producing. But every evening when the sun sets they're going to stop. So you might want to add a window to watch only from 10am - 4pm.

Severity is an informative field. 

When adding a time window, it's possible that an alarm keeps getting triggered. You might want to get a reminder every day or maybe you just want 1 alarm.

For this you can use the 'During the guard period'. Selecting 'Keep state' will not send new alarms. Meaning when an alarm is triggered it won't trigger again. If you select 'Reset state', every time the alarm reaches the start of the window it will send a new email.

<ClickableImage src="/img/eniris/Window.png" alt="Alarm configuration window" maxWidth="800px" />

## Guarded datapoints

This table is used to see if the alarm is triggered or not. Since my last value is less then 5 hours ago sent, I will not get an alarm.

<ClickableImage src="/img/eniris/Guardeddatapoints.png" alt="Alarm configuration guarded datapoints" maxWidth="800px" />

## Alarms

[Adding Alarms](/Monitoring/Web%20portal/Legacy%20web%20portal/Alarms%20Legacy%20Web%20Portal/AddingANewAlarm/)


# Alarms Legacy Web Portal


import { FolderOverview } from '@/components/FolderOverview';

# Alarms Legacy Web Portal

<FolderOverview folder="Monitoring/Web portal/Legacy web portal/Alarms Legacy Web Portal" />


# Add Buildings or Remove

import { BrandName, ControllerName } from '@site/src/components/customFields';
import ClickableImage from '@site/src/components/ClickableImage';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';


This page contains most things to manage buildings and/ or Smart Grid Controllers. 

<ClickableImage src="/img/eniris/AddBuilding.png" alt="Image 1" maxWidth="450px" />

## New site
 This is used to manually add a new building to your BMS. Only name is required. Once 'Add' is pressed the page will reload and your building will be added.

If you have a <ControllerName />, you don't have to do this.
<ClickableImage src="/img/eniris/NewSite.png" alt="Image 1" maxWidth="450px" />
## Claim <ControllerName/>
In order to generate a building for your <ControllerName />, you will need to claim it first. You can do this by entering the serial number and verification code which you can find on the controller. After submitting it will show in the 'Generate building for <ControllerName/>'.
<ClickableImage src="/img/eniris/Claim.png" alt="Image 1" maxWidth="450px" />
## Generate <ControllerName/>
All the claimed controllers that have not yet generated a building, can generate one here. Just select the controller in the dropdown and select 'Standard residential dashboard'
<ClickableImage src="/img/eniris/Generate.png" alt="Image 1" maxWidth="450px" />
## Synchronize building for <ControllerName/>
In this field you will be able to add measurements. This means if you added devices to your controller that the new measurements of these devices will show up in the dashboard. These will not be added to the widgets so you will have to add those manually. This is in case you made your own dashboard for a controller and don't want to reset your configuration. This will also not change names if you changed those of existing measurements. 
<ClickableImage src="/img/eniris/Synchronize.png" alt="Image 1" maxWidth="450px" />
## Reset building for <ControllerName/>
This does the same as generating a building. Only this works for controllers that already have been generated.
<ClickableImage src="/img/eniris/ResetBuilding.png" alt="Image 1" maxWidth="450px" />
## Inactive installations
This is the list of inactive buildings. These will not be shown on the portal. To show them press the button 'Enable monitoring' and it will be in the list of active installations.
<ClickableImage src="/img/eniris/InactiveInstallation.png" alt="Image 1" maxWidth="450px" />
## Active installations
These are the currently active installations. Here you can disable them or not show them for superadmins. This is if you have a lot of buildings to hide them for you but not for your client.
<ClickableImage src="/img/eniris/ActiveInstallations.png" alt="Image 1" maxWidth="450px" />

# Credentials and Licenses


import { BrandName, ControllerName } from '@site/src/components/customFields';
import ClickableImage from '@site/src/components/ClickableImage';

This is a legacy administration page. New Eniris MQTT credentials must be requested through the [Eniris webshop](https://webshop.eniris.com/); do not request access to this legacy feature through a support ticket.

Deprecated:

- Licenses

## Managing MQTT Credentials

Depending on your legacy account permissions, this page may still show or manage existing credentials. It is not the provisioning route for new MQTT credentials. Submit every new request through the [Eniris webshop](https://webshop.eniris.com/).
<ClickableImage src="/img/eniris/Credentials.png" alt="Credentials" maxWidth="800px" />
<ClickableImage src="/img/eniris/NewCredentials.png" alt="New Credentials" maxWidth="800px" />


# fileManagement (feature)


import { BrandName, ControllerName, CustomerName, InsightsName, InsightsUrl } from '@site/src/components/customFields';
import ClickableImage from '@site/src/components/ClickableImage';

## Filemanagement (FEATURE)

This page is to store certain documents or images. Once you press the Upload file button, you will get a popup where you can select files. This can be used to upload SVGs, images or other files you might want to use in widgets that support this. 

<ClickableImage src="/img/eniris/fileManagement.png" alt="Filemanagement" maxWidth="800px" />

## Using Images in the file management

When you upload an image, you will see it appear in the table under the button. Here you have some fields:

Name: name of the original image

FileUrl: This is what you need to copy so you can use it in a widget (SVGs and images).

Copy: This is to simply copy the FileUrl without having to select it.

Delete: This deletes the file out of this list.
<ClickableImage src="/img/eniris/ImagesInFileManagement.png" alt="Filemanagement table" maxWidth="800px" />

# Global Settings


import { FolderOverview } from '@/components/FolderOverview';

# Global Settings

<FolderOverview folder="Monitoring/Web portal/Legacy web portal/Global Settings" />


# Legacy Web Portal


import { FolderOverview } from '@/components/FolderOverview';

# Legacy Web Portal

<FolderOverview folder="Monitoring/Web portal/Legacy web portal" />


# Manual


import { BrandName, ControllerName } from '@site/src/components/customFields';
import ClickableImage from '@site/src/components/ClickableImage';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';

This is the button you press to open this manual.

<ClickableImage src="/img/eniris/Manual.png" alt="Manual" maxWidth="800px" />

# My Buildings


import { FolderOverview } from '@/components/FolderOverview';

# My Buildings

<FolderOverview folder="Monitoring/Web portal/Legacy web portal/My Buildings" />


# Bar Chart


import { BrandName, ControllerName, CustomerName, InsightsName, InsightsUrl } from '@site/src/components/customFields';
import ClickableImage from '@site/src/components/ClickableImage';

## Bar chart
This widget is used to show bar charts.
<ClickableImage src="/img/eniris/BarChart.png" alt="Bar chart" maxWidth="800px" />


## Settings

Chart active: Activates the widget in the dashboard.

Expand legend: This increases the space underneath the widget allowing more datapoint to be visible without a scroll bar.

Position legend under chart: This positions the legend under the graph is case this is wanted.

Stacked view: This will stack the bars on top of each other instead of being next to each other.

Show throbber. You can turn this on if you want to see the loading icon when new data is sent to the portal.

Title: This is the title of the widget.

Widget position: This is the position of the widget in the list on the dashboard.

Widget size: This is if you want to see multiple widgets next to each other.

To know what to select you need to see the dashboard as 12 divisions. Here is a list to see how much divisions a size takes:

- XXL: Full size/ standard; 12/12

- XL: 10/12

- L: 8/12

- M: Half; 6/12

- S: 4/12

- XS: 2/12

Period: Select what the standard period is when the dashboard is loaded. Ex. Month so when you open the dashboard you don't need to edit it so it shows data for a month.

<ClickableImage src="/img/eniris/barChartSettings.png" alt="Bar chart settings" maxWidth="800px" />

# Bar Line Chart


import { BrandName, ControllerName, CustomerName, InsightsName, InsightsUrl } from '@site/src/components/customFields';
import ClickableImage from '@site/src/components/ClickableImage';

## Bar Line Chart

<ClickableImage src="/img/eniris/BarLineChart.png" alt="Bar Line Chart" maxWidth="800px" />

## Settings

Chart active: Activates the widget in the dashboard.

Expand legend: This increases the space underneath the widget allowing more datapoint to be visible without a scroll bar.

Show throbber. You can turn this on if you want to see the loading icon when new data is sent to the portal.

Title: This is the title of the widget.

Widget position: This is the position of the widget in the list on the dashboard.

Widget size: This is if you want to see multiple widgets next to each other.

To know what to select you need to see the dashboard as 12 divisions. Here is a list to see how much divisions a size takes:

- XXL: Full size/ standard; 12/12

- XL: 10/12

- L: 8/12

- M: Half; 6/12

- S: 4/12

- XS: 2/12

Period: Select what the standard period is when the dashboard is loaded. Ex. Month so when you open the dashboard you don't need to edit it so it shows data for a month.

<ClickableImage src="/img/eniris/BarLineChartSettings.png" alt="Bar Line Chart settings" maxWidth="800px" />


# Classic SVG Widget


import { BrandName, ControllerName, CustomerName, InsightsName, InsightsUrl } from '@site/src/components/customFields';
import ClickableImage from '@site/src/components/ClickableImage';


# Classic SVG Widget
This widget is used to show SVG images.
<ClickableImage src="/img/eniris/ClassicSVG.png" alt="Classic SVG Widget" maxWidth="800px" />
## Settings

Widget active: Shows the widget on the dashboard.

Title active: If you are happy with your result you can also choose to hide the title this will make it so the border and title on top disappear. Be wary that you will not be able to enter the settings page (This can be deleted or changed in the JSON).

Widget title: Title for the widget.

Widget size: This is if you want to see multiple widgets next to each other.

To know what to select you need to see the dashboard as 12 divisions. Here is a list to see how much divisions a size takes:

- XXL: Full size/ standard; 12/12

- XL: 10/12

- L: 8/12

- M: Half; 6/12

- S: 4/12

- XS: 2/12

Widget position: This is the position of the widget in the list on the dashboard.

SVG URL: You can place an URL of a SVG here. If you don't know how to put images online you can use our feature for this. (Button below)

<ClickableImage src="/img/eniris/svgWidgetSettings.png" alt="Classic SVG Widget settings" maxWidth="800px" />

# Heat Map

import { BrandName, ControllerName, CustomerName, InsightsName, InsightsUrl } from '@site/src/components/customFields';
import ClickableImage from '@site/src/components/ClickableImage';

# Heat Map
This widget is used to show heatmaps.
<ClickableImage src="/img/eniris/Heatmap.png" alt="Heatmap" maxWidth="800px" />

## Settings

Chart active: Activates the widget in the dashboard.

Expand legend: This increases the space underneath the widget allowing more datapoint to be visible without a scroll bar.

Reverse heatmap: Switches the x- and y-axis.

Title: This is the title of the widget.

Widget position: This is the position of the widget in the list on the dashboard.

Widget size: This is if you want to see multiple widgets next to each other.

To know what to select you need to see the dashboard as 12 divisions. Here is a list to see how much divisions a size takes:

- XXL: Full size/ standard; 12/12

- XL: 10/12

- L: 8/12

- M: Half; 6/12

- S: 4/12

- XS: 2/12

Period: Select what the standard period is when the dashboard is loaded. Ex. Month so when you open the dashboard you don't need to edit it so it shows data for a month.

<ClickableImage src="/img/eniris/HeatmapSettings.png" alt="Heatmap settings" maxWidth="800px" />

# HMIIframe


import { BrandName, ControllerName, CustomerName, InsightsName, InsightsUrl } from '@site/src/components/customFields';
import ClickableImage from '@site/src/components/ClickableImage';

# HMIIframe
This widget can be used to embed URLs or HMIs
<ClickableImage src="/img/eniris/HMIIframe.png" alt="HMI Iframe" maxWidth="800px" />

## Settings
Widget title: Title for the widget.

Widget position: This is the position of the widget in the list on the dashboard.

Widget active: Shows the widget on the dashboard.

Code: For this part you can use this example but with your own URL. Afterwards you can play with the styling to make it to your liking.

```json
[
    {
        "cardHeader": "Title",
        "cardClass": "col-12",
        "iframeClass": "w-100",
        "iframeStyle": "height: 800px",
        "iframeUrl": "[https://www.google.com](https://www.google.com)"
    }
]
```
<ClickableImage src="/img/eniris/HMIIframeSettings.png" alt="HMI Iframe settings" maxWidth="800px" />

# Image Widget


import { BrandName, ControllerName, CustomerName, InsightsName, InsightsUrl } from '@site/src/components/customFields';
import ClickableImage from '@site/src/components/ClickableImage';

# Image Widget
This widget is used to show a image.
<ClickableImage src="/img/eniris/ImageWidget.png" alt="Image Widget" maxWidth="800px" />
## Settings
Widget active: Shows the widget on the dashboard.

Title active: If you are happy with your result you can also choose to hide the title this will make it so the border and title on top disappear. Be wary that you will not be able to enter the settings page (This can be deleted or changed in the JSON).

Widget title: Title for the widget.

Widget size: This is if you want to see multiple widgets next to each other.

To know what to select you need to see the dashboard as 12 divisions. Here is a list to see how much divisions a size takes:

- XXL: Full size/ standard; 12/12

- XL: 10/12

- L: 8/12

- M: Half; 6/12

- S: 4/12

- XS: 2/12

Widget position: This is the position of the widget in the list on the dashboard.


<ClickableImage src="/img/eniris/ImageWidgetSettings.png" alt="Image Widget settings" maxWidth="800px" />


[File Management](/Monitoring/Web%20portal/Legacy%20web%20portal/Global%20Settings/FileManagement%20Feature) feature for this.

# Widgets


import { FolderOverview } from '@/components/FolderOverview';

# Widgets

<FolderOverview folder="Monitoring/Web portal/Legacy web portal/My Buildings/widgets" />


# Line Chart


import { BrandName, ControllerName, CustomerName, InsightsName, InsightsUrl } from '@site/src/components/customFields';
import ClickableImage from '@site/src/components/ClickableImage';

# Line Chart
This widget is used to show a standard line chart.
<ClickableImage src="/img/eniris/LineChart.png" alt="Line chart" maxWidth="800px" />


## Settings

Chart active: Activates the widget in the dashboard.

Zoom active: Adds a bar underneath the graph where you can select an area to zoom in on. You can then drag this.

Expand legend: This increases the space underneath the widget allowing more datapoint to be visible without a scroll bar.

Calculator: Adds a new field to the line chart. Here you can find the min, max and average of each datapoint. This is configurable on the bottom of the page so I will not explain it separately. This is to configure what period is being looked at when calculating this. This also comes with a button next to the download button to show this for the currently selected period and the added rescaling that was done to show it in the graph. The calculator on the bottom will take the raw data of the measurement.

Position legend under chart: This positions the legend under the graph is case this is wanted.

Show min-max: This shows the min and max for each measurement.

Show throbber. You can turn this on if you want to see the loading icon when new data is sent to the portal.

Title: This is the title of the widget.

Widget position: This is the position of the widget in the list on the dashboard.

Widget size: This is if you want to see multiple widgets next to each other.

To know what to select you need to see the dashboard as 12 divisions. Here is a list to see how much divisions a size takes:

XXL: Full size/ standard; 12/12

XL: 10/12

L: 8/12

M: Half; 6/12

S: 4/12

XS: 2/12

Set start date: This sets the start date so when you load this chart it will always start on that date.

Relative start date: This makes it so you can see for example: last weeks data. Without you having to always press the button to go back.

Units on y-axis: This will edit the value of the unit when the conditions described in the fields are met.

All measuring points are counter readings: If you select this you will see a new button to calculate the values based of the counter reading.

Take derivative: This works if the option above is turned on. This then calculates the values already without you having to press the button.

Number of decimals: Here you can choose how much decimals are shown.

Period: Select what the standard period is when the dashboard is loaded. Ex. Month so when you open the dashboard you don't need to edit it so it shows data for a month.

Reference line: This will take a value and create a line on the chart. This can also be used to set the max of the y-axis (chart will scale to where the reference point is. If the values are greater then the reference line this won't happen).

Calculator: Here you can configure the date of the calculator on the bottom if this option is turned on.


<ClickableImage src="/img/eniris/LineChartSettings.png" alt="Line chart settings" maxWidth="800px" />

# Pie Chart


import { BrandName, ControllerName, CustomerName, InsightsName, InsightsUrl } from '@site/src/components/customFields';
import ClickableImage from '@site/src/components/ClickableImage';

# Pie Chart
This widget is used to show a standard pie chart.

## Settings
Chart active: Activate the widget for the dashboard.

Simplified pie chart: A secondary version of the pie chart. 

Remove legend: Removes the legend.

Editable hours (Feature): Select the date and also hours. Used to see very specific data on a pie chart.

Doughtnut: Works with the simplified version to make it a donut chart. (Empty inside)

Expand legend: This increases the space underneath the widget allowing more datapoint to be visible without a scroll bar.

Period: Select what the standard period is when the dashboard is loaded. Ex. Month so when you open the dashboard you don't need to edit it so it shows data for a month.

<ClickableImage src="/img/eniris/PieChartSettings.png" alt="Pie Chart Settings" maxWidth="800px" />

# Table of meter reading deltas


import { BrandName, ControllerName, CustomerName, InsightsName, InsightsUrl } from '@site/src/components/customFields';
import ClickableImage from '@site/src/components/ClickableImage';


## Table with deltas of meter readings on a monthly basis for the past period
This widget is used to show a table with data for each month for the past year.
<ClickableImage src="/img/eniris/TableWithDeltas.png" alt="Table with deltas of meter readings on a monthly basis for the past period" maxWidth="800px" />
### Settings (Tables)
Enable widget: Activates the widget in your dashboard.

Header presets: This selects the headers of your table. This is always set to the correct value unless you need other units.

Hidden columns: Here you can select all the fields you don't want to see in your table.

Sorting order: Here you can select what table will be used to sort them.

Widget size: This is if you want to see multiple widgets next to each other.

To know what to select you need to see the dashboard as 12 divisions. Here is a list to see how much divisions a size takes:

    - XXL: Full size/ standard; 12/12

    - XL: 10/12   

    - L: 8/12

    - M: Half; 6/12

    - S: 4/12

    - XS: 2/12

Title table: This is the title of the table

Widget position: This is to put widgets in certain positions on your dashboard. (If you add a new widget and you want it higher maybe)

<ClickableImage src="/img/eniris/TableSettings.png" alt="Widget position" maxWidth="800px" />

# Creating Reports


import { BrandName, ControllerName } from '@site/src/components/customFields';
import RS485ConnectionTable from '@site/src/components/RS485ConnectionTable';
import ClickableImage from '@site/src/components/ClickableImage';


# Creating reports
For the first step you want to press 'Add' to create a new report


<ClickableImage src="/img/eniris/AddReport.png" alt="Add Report" maxWidth="800px" />

Select what type of report you want to make. In this example I 'am making a month report.

Then you enter a name.

After that select the Admins or any role for what building you want to create this report.

<ClickableImage src="/img/eniris/SelectReport.png" alt="Select Report" maxWidth="800px" />

## Details in setup for reports

When you get to this page usually you will only need the 3 initial fields. You will normally never need the other fields. If you do we will help you accordingly but this is not important for normal reports.

Once your done here, you can click on the top menu to navigate to 'Mail configuration'.

<ClickableImage src="/img/eniris/DetailsInSetup.png" alt="Details in setup" maxWidth="800px" />

## Mail config for reports

On this page you can add emails. This will send the reports automatically depending on what type of report you created.

Ex. Monthly reports are sent monthly.

Optionally you can add a subject and content if you want this. If this is empty you will get a no subject email with the report in pdf as attachment.

When this is done you can click save to add the report.

<ClickableImage src="/img/eniris/MailConfig.png" alt="Mail config" maxWidth="800px" />

## Contained entities
Once you clicked to add the report you will see it appear in the list. If you click on the report and then go to the cogwheel you will see a menu-item called 'contained entities'. If you press this just add the role again of the building you want to create a report for. 

If this is done you can go back to the report list.

<ClickableImage src="/img/eniris/ContainedEntities.png" alt="Contained entities" maxWidth="800px" />
<ClickableImage src="/img/eniris/ContainedEntities2.png" alt="Contained entities" maxWidth="800px" />

## Opening reports

When all the previous steps are done you can open and view a report using the eye icon. Here you can edit it. Or you can download the report which will download a pdf after some time.
<ClickableImage src="/img/eniris/OpeningReport.png" alt="Open report" maxWidth="800px" />



# Editing Reports


import { BrandName, ControllerName } from "@site/src/components/customFields";
import ClickableImage from "@site/src/components/ClickableImage";

In order to edit a report you have to make sure the 'Edit report' box is checked. This will give you a list of widgets that you can choose to put on the report.

When pressing on a title, the settings page of the corresponding widget will open. Activating a widget will place it on the report.

And that's it. This is very similar to creating dashboards. For more information about widgets, use the button below.

<ClickableImage
  src="/img/eniris/EditReport.png"
  alt="Edit report"
  maxWidth="800px"
/>

## Widget

([Widgets](/Monitoring/Web%20portal/Legacy%20web%20portal/My%20Buildings/widgets))


# Reports Legacy Web Portal


import { FolderOverview } from '@/components/FolderOverview';

# Reports Legacy Web Portal

<FolderOverview folder="Monitoring/Web portal/Legacy web portal/Reports Legacy web portal" />


# Side menu


This menu is used to navigate to certain features in the BMS.

- Deprecated features:

- Analyse

- Support

- Rights

- Cost Simulation

- Pageviews

- BMS (Dropdown)

- Reports

- Alarms

- Users

- Global Settings

- Manual

- Account Settings

- Logout

# Users


import { BrandName, ControllerName } from '@site/src/components/customFields';
import ClickableImage from '@site/src/components/ClickableImage';


This page is used to manage your users. 

This example is very simple since we only have 1 building. 

Here are the possible options:

Superadmin: This is the role that usually has the name of your company without anything next to it. As you can see in the screenshot here it's 'matthijstest'.

Superadmins can edit everything and see every building. 

Admins: These have a little bit less rights then superadmins in global settings. They can only see the building they're assigned for. You can assign someone to multiple buildings.

Installers: These are like admins only they can not generate reports or do alarm management. 

Users: These can only see their dashboard. They can not edit anything.


<ClickableImage src="/img/eniris/Users.png" alt="Users" maxWidth="800px" />

# Sign in and recover access


# Sign in and recover access

SmartgridX uses an email address and password for the standard sign-in flow. After authentication, the application loads your company, active view, user preferences, dashboard configuration, and accepted policies before constructing the available routes.

## Sign in

1. Open the SmartgridX login page supplied by your organisation.
2. Enter the email address linked to your role membership.
3. Enter your password.
4. Complete any policy acceptance presented after sign-in.
5. Confirm that the expected company and view are selected.

## If you do not have access

Ask an administrator of the relevant company or installation to add your email address to the correct role. Eniris Support should not choose a role on behalf of an organisation without the required authorisation.

## Password recovery

Use the **Password reset** flow from the login page. The current application has separate routes for starting a reset and applying the reset token. Always use the most recent reset email and check that the request was made for the same email address used in SmartgridX.

<Callout type="warning" title="Do not share credentials">
  Each person should use an individual account. Access is assigned through role membership, so shared passwords are unnecessary and make operational changes harder to audit.
</Callout>

## Unexpected portal after sign-in

If authentication succeeds but the wrong content appears, check:

- selected company and view;
- role membership;
- whether a required policy is still awaiting acceptance;
- organisation-specific domain or white-label environment;
- whether the expected asset is active and linked to that role.


# Adding installations


import ClickableImage from '@/components/ClickableImage';

# Adding installations

The current owner-only **Add** page supports two workflows: claiming an existing SmartgridOne controller and creating a supported virtual asset.

Read the current code-aligned guide here:

<Card title="Add an installation or asset" description="Claim a controller with its serial number and verification code, or create a virtual asset with a name and supported type." href="../../installations/add" />

Do not create a virtual asset as a substitute for claiming a controller. The two workflows create different ownership and hierarchy relationships.

<ClickableImage src="/img/eniris/monitoring/screenshots/claim-controller-and-add-asset.webp" alt="SmartgridX controller-claim and virtual-asset creation forms" maxWidth="1140px" />


# Assets and installations


import { FolderOverview } from '@/components/FolderOverview';
import ClickableImage from '@/components/ClickableImage';

# Assets and installations

The current **Add** page contains two separate workflows. Choosing the correct one matters because their ownership and removal behaviour differ.

| Workflow | Use it for | Required information |
| --- | --- | --- |
| **Claim controller** | Link an already installed SmartgridOne controller and its device hierarchy to the company. | Controller serial number and verification code. |
| **Create virtual asset** | Create a manually managed portfolio object for a supported, creatable node type. | Asset name and asset type. |

Only owners see the global **Add** menu item. The application validates empty names, missing asset types, serial numbers, verification codes, unknown controllers, invalid codes, and claim-rate limits before changing the portfolio.

<Callout type="info" title="Claiming is different from creating">
  A claimed controller retains its controller-managed hierarchy. A virtual asset receives a generated `custom-…` identifier and starts without children or telemetry streams until these are configured separately.
</Callout>

<ClickableImage src="/img/eniris/monitoring/screenshots/claim-controller-and-add-asset.webp" alt="SmartgridX forms for claiming a controller and creating a virtual asset" maxWidth="1140px" />

*The two forms are deliberately separate because they create different ownership and hierarchy relationships.*

## Management actions

<FolderOverview folder="Monitoring/Web portal/management/add" />


# Combine installations structurally


import ClickableImage from '@/components/ClickableImage';

# Combine installations structurally

The current Insights code does not expose a general one-click **merge installations** feature. Combining assets means changing their hierarchy or configured dashboard representation and should be treated as a structural migration.

## Safe approach

1. Define the intended parent installation and its physical boundary.
2. Inventory the existing sites, devices, streams, users, alarms, reports, contacts, documents, and targets.
3. Decide whether child histories remain separate or require an approved aggregation view.
4. Create or select the parent asset.
5. Link descendants using the supported hierarchy-management workflow.
6. Validate energy totals and avoid double counting.
7. Recheck roles, alarms, reports, and portfolio tags.

<ClickableImage src="/img/eniris/monitoring/screenshots/customer-installation-hierarchy.webp" alt="An anonymized SmartgridX customer, installation, and device hierarchy" maxWidth="1140px" />

*Use the resulting hierarchy to verify the intended parent-child structure while keeping original data sources traceable.*

<Callout type="warning" title="Hierarchy is not historical data merging">
  Placing two assets under one parent does not make their counters one physical meter. Keep original sources traceable and document any aggregation formula.
</Callout>


# Other asset actions


import { FolderOverview } from '@/components/FolderOverview';

# Other asset actions

Combining, replacing, hiding, deleting, and unclaiming assets solve different problems. Do not use them interchangeably.

| Action | What it changes | Typical use |
| --- | --- | --- |
| **Hide / deactivate** | Keeps the asset and its history but removes it from normal active views. | Temporarily or permanently stop operational follow-up without deleting data. |
| **Hide from monitored table** | Keeps the asset active but removes it from the main monitored overview. | Exclude an auxiliary or non-operational asset from portfolio supervision. |
| **Unclaim controller** | Detaches company management relations from a controller hierarchy. | Transfer or remove a controller from the current company. |
| **Delete custom asset** | Removes monitor relations for a manually created `custom-…` asset. | Remove a virtual object that should no longer exist. |
| **Combine / replace** | Changes how existing records or histories are represented. | Correct a structural migration with support guidance. |

<Callout type="warning" title="Use support for structural migrations">
  Combining or replacing installations can affect hierarchy, historical interpretation, alarms, reports, and access. Record the intended source, destination, and effective date before applying the change.
</Callout>

## Action guides

<FolderOverview folder="Monitoring/Web portal/management/add/other-actions" />


# Replace a device


import ClickableImage from '@/components/ClickableImage';

# Replace a device

A device replacement should preserve the old device's history and start the new device at the correct effective date.

## Replacement workflow

1. Record the old and new manufacturer, model, serial number, and meter relationship.
2. Choose the exact replacement timestamp and site timezone.
3. Keep the old device in the hierarchy for historical periods.
4. Add the new device beneath the same physical parent.
5. Set deactivation or activity information for the old device where supported.
6. Set activation or installation information for the new device.
7. Map new telemetry streams and validate units and signs.
8. Check alarms, reports, targets, and public displays across the transition.

<ClickableImage src="/img/eniris/monitoring/screenshots/customer-installation-hierarchy.webp" alt="An anonymized SmartgridX hierarchy used to verify parent and child relationships" maxWidth="1140px" />

<ClickableImage src="/img/eniris/monitoring/screenshots/data-stream-configuration.webp" alt="An anonymized SmartgridX data-stream configuration used after replacing a device" maxWidth="1140px" />

*Confirm both the new hierarchy position and the new stream mapping before retiring the previous device.*

<Callout type="warning" title="Do not join incompatible counters silently">
  A new inverter or meter can start from zero or use a different scaling factor. Reports must either handle the transition explicitly or aggregate validated energy deltas rather than subtracting unrelated counters.
</Callout>


# Removing installations


import ClickableImage from '@/components/ClickableImage';

# Removing installations

The current portal distinguishes hiding an asset, excluding it from monitored tables, unclaiming a controller, and deleting a manually created asset.

<Card title="Choose the correct removal action" description="Review the code-backed differences and the required dependency checks before changing the portfolio." href="../../installations/remove" />

Prefer the least destructive action that matches the business intent. A visibility change preserves the hierarchy and history; unclaiming or deleting changes portfolio relationships.

<ClickableImage src="/img/eniris/monitoring/screenshots/installation-management-controls.webp" alt="An anonymized SmartgridX installation settings page with visibility and delete controls" maxWidth="1140px" />


# Access and loading


# Open Advanced alarms

Advanced alarms is embedded in SmartgridX Monitoring. Its menu item and route appear only when the feature is enabled for the active environment.

## How it opens

1. Select **Advanced alarms** from the SmartgridX navigation.
2. The portal requests a single sign-on session.
3. While the session is prepared, the page shows a loading state.
4. The Advanced alarms workspace opens inside the portal.

The workspace can use clipboard read and write for supported workflows.

## If Advanced alarms does not load

- confirm the feature is enabled for the active white-label environment;
- verify that the user is authenticated in the correct company and view;
- retry after reloading the SmartgridX session;
- check browser or network rules that block embedded content;
- report the time, user, company, and visible single sign-on error to Support.

<Callout type="info" title="Availability depends on your environment">
  Advanced alarms can expose different rules, views, and notification workflows per organisation. Follow the operational process configured for your company.
</Callout>


# Rules and analysis


# Advanced alarms rules and analysis

Advanced alarms turn SmartgridX telemetry into an operational workflow. Instead of only reporting a manufacturer fault, the alerting engine evaluates whether an installation is still communicating, following control instructions, respecting grid limits, producing as expected, and delivering the intended result.

<Callout type="info" title="Availability">
  Advanced alarms are shown only for organisations for which the alerting application is enabled. The available rule types also depend on the signals and assets detected at the selected installation.
</Callout>

## From signal to action

| Step | What SmartgridX does | What you see |
| --- | --- | --- |
| **1. Discover** | Finds the applicable site, asset, planning, price, and external-control signals. | Only eligible installations can be selected for an automatic rule. |
| **2. Evaluate** | Runs each enabled rule over its own lookback window and data-quality requirements. | A status of **OK**, **Firing**, **No data**, **Pending**, **Waiting**, or **Error**. |
| **3. Explain** | Keeps the values, timestamps, limits, and comparison series behind the result. | A compact trend on the rule card and a detailed analysis view. |
| **4. Notify** | Detects newly opened and resolved conditions and deduplicates repeated events. | Bundled email and, when configured, SMS notifications. |

This separation is important: a missing signal is not treated as proof that an operating limit was violated, and a temporary scheduler wait is not shown as a customer alarm.

## Rule catalogue

### Grid safety

Compares the site's quarter-hour average grid power with the maximum import and export limits configured on the controller. Positive grid power represents import; negative grid power represents export.

The rule fires when either:

- grid import exceeds the configured maximum consumption; or
- grid export exceeds the configured maximum injection.

The analysis chart shows the measured grid power together with both limits, so the direction and size of a breach are visible immediately. The rule is offered only for sites where these limits are configured.

### PV status

Compares solar inverters at the same site. It fires when one or more inverters produce almost nothing while their peers clearly produce. This makes it useful for finding an offline inverter or string without relying on a weather forecast.

- If all inverters are inactive, for example at night or during very low irradiance, the rule does not infer a failure.
- A site with only one inverter cannot use peer comparison to reach the same conclusion.
- A missing inverter signal remains distinguishable from a confirmed production anomaly.

### Performance index (PI)

Compares total measured PV energy with total expected PV energy over complete local calendar days. The default is a minimum PI of **90%** over **3 days**, with one full day of weather-data delay. An alarm opens only when the period PI is below the configured minimum. Known curtailment hours are excluded; incomplete required data gives **No data**, not an underperformance alarm.

Add PI monitoring explicitly through **Add alarm → Performance index (PI)** for one site or **All eligible sites**. Existing PI rules are skipped. Automatic dashboard setup never creates PI rules, and future sites are not enrolled automatically. PI and performance ratio (PR) measure different comparisons.

See [Performance index (PI) monitoring](/Monitoring/Web%20portal/management/alarms/performance-index) for the formula, settings, data requirements, analysis and email setup.

### External signal

Supervises external control signals on the site and all descendant devices.

1. **Signal liveness:** fires when no new external-signal sample has arrived for more than **1 hour**. The evaluator looks back **24 hours** to report the most recent activity.
2. **Setpoint tracking:** when the signal contains a power setpoint, SmartgridX compares it with the asset's actual power over the last **2 hours**. A point deviates when the difference is greater than the larger of **3 kW** or **10% of the setpoint**. The rule fires when more than **30%** of the aligned points deviate and the latest point still deviates.

Setpoints and measured power are aligned by carrying the most recent observation forward to the setpoint timestamp. This avoids comparing values from unrelated moments.

### Battery status

Detects a state-of-charge signal that appears to be stuck. By default, the highest and lowest SoC values over **48 hours** must differ by at least **1 percentage point**.

To prevent false alarms on a newly connected battery, the evaluator requires at least two measurements and data covering at least half of the 48-hour window. Otherwise the result is **No data**, not **Firing**. On a site with multiple batteries, one stuck battery is sufficient to open the alarm, and the analysis view identifies the affected device.

### Savings

Checks whether estimated EMS savings continue to grow over a minimum period of **7 days**. The rule is offered only when SmartgridX has savings data and at least one asset is configured for cost optimisation.

The analysis can separate the contribution of batteries, PV, EV charging, and HVAC or switched loads, and it surfaces invalid or incomplete source data. Savings alarms are intended for operational analysis in the application and are not included in customer alarm-email bundles.

### Custom threshold

Creates a rule from a telemetry signal available at the selected site or one of its devices. Choose:

- the measurement;
- **above** or **below**;
- the numeric threshold; and
- how long the condition must persist.

Available measurements are discovered from the installation and can include grid power, production, battery power, EV charging power, base load, state of charge, planning values, setpoints, limits, and prices. Always confirm the displayed unit before saving the rule.

## Understand the status

| Status | Meaning | Recommended action |
| --- | --- | --- |
| **OK** | The latest evaluation satisfies the rule. | No action required. |
| **Firing** | The rule condition is currently violated. | Open **Analysis**, confirm the evidence, and investigate the asset or control path. |
| **No data** | There is not enough valid telemetry to evaluate the condition. | Check connectivity, signal mapping, and the time of the last measurement. |
| **Pending** | The evaluation is queued or has not completed yet. | Wait for the next completed evaluation. |
| **Waiting** | A temporary, non-actionable hold is active, for example during connection recovery. | Do not interpret this as an installation fault. |
| **Error** | The evaluator could not complete the rule. | Retry, then report the rule, site, time, and visible error if it persists. |

For firing alarms, SmartgridX also distinguishes a **recent outage** from a signal with **no recent healthy activity**. The last known healthy timestamp helps separate a fresh failure from an installation that was never fully commissioned.

## Use the analysis view

Open **Analysis** from a rule card before acting on an alarm. Depending on the rule, the view can show:

- the measured series and its threshold or import/export limits;
- actual power next to the requested setpoint;
- one chart per affected inverter or battery;
- strategy overlays and categorical control-state bands;
- shaded breach intervals;
- followed, constrained, and violated setpoint samples; and
- the last healthy activity and duration of the current violation.

The small chart on a rule card is intentionally a summary. Use the full analysis view to verify timing, units, and the relationship between signals.

## Create and manage rules

1. Open **Advanced alarms** for the correct SmartgridX organisation.
2. Select **Add alarm** and choose a rule type.
3. Select an installation. For automatic rules, the selector shows only sites with the required assets, signals, or controller settings.
4. Review the fixed rule definition or configure the threshold fields.
5. Add an optional recognisable name and save the rule.
6. Open **Analysis** after the first evaluation to verify that the expected signals were selected.
7. Add notification recipients only after the rule has been validated.

Rules can be enabled or disabled without deleting their configuration. Operators can also edit or remove a rule, filter the overview by type and status, group results by installation, and manually request a recheck.

### Configure a portfolio efficiently

Bulk configuration can create applicable automatic rules across multiple sites. SmartgridX first checks each site's eligibility, so a battery rule is not created for a site without a detected battery, and a grid-safety rule is not created without grid limits.

[PI monitoring](/Monitoring/Web%20portal/management/alarms/performance-index) is excluded from automatic setup. Use its **All eligible sites** option to add it explicitly to the current suitable installations; existing PI rules keep their settings.

Use individual configuration for custom thresholds and 7C compliance: both require an explicit operational choice rather than generic portfolio-wide defaults. Account or subscription limits can restrict how many rules are active.

## Notifications

Email notifications are bundled per recipient and organisation. A recipient can choose a minimum interval of **1 hour**, **3 hours**, **6 hours**, or **24 hours**. A bundle can contain both newly opened alarms and resolved alarms.

To avoid notification floods:

- email is never sent more frequently than once per hour to the same recipient;
- repeated evaluations of the same open condition are deduplicated;
- a short warm-up period after an alerting-service restart allows all rules to be evaluated before notifications resume; and
- configured SMS uses the same cadence and reports new alarms only.

<Callout type="warning" title="Validate before notifying">
  An alarm can be technically valid but operationally noisy when a limit, signal mapping, or expected active period is wrong. Validate the analysis for a representative site before enabling a large recipient list or rolling a rule out across a portfolio.
</Callout>

## Troubleshooting checklist

| Symptom | Check first |
| --- | --- |
| A site is missing from the selector | Confirm that the required asset, signal, savings source, or controller grid limits exist. |
| The result is **No data** | Check the last sample, required window coverage, device hierarchy, and selected telemetry unit. |
| An external-signal alarm fires | Verify both signal freshness and whether actual asset power is following the setpoint. |
| A PV alarm does not fire | Confirm that at least one peer inverter is producing; a fully inactive site cannot be peer-compared. |
| Grid safety appears inverted | Remember that positive grid power is import and negative grid power is export. |
| A battery alarm appears too early | Confirm that the data covers at least half of the 48-hour evaluation window. |
| No email was received | Confirm the recipient is enabled, the cadence has elapsed, the condition is new or resolved, and the service is past warm-up. |




# Default alarm strategy


import ClickableImage from '@/components/ClickableImage';

# Default alarm strategy

Default alarms are intended to catch meaningful problems without overwhelming operators. Exact defaults are configuration data and can evolve independently of the Insights user-interface code, so always review the values shown in your active portal.

## Common default categories

| Category | Typical signals or calculations | Important context |
| --- | --- | --- |
| **No production data** | Active production power | Solar operating window and source delivery interval. |
| **No storage data** | Storage power or state of charge | Whether the battery is expected to communicate continuously. |
| **No charger data** | Charger or socket power | Chargers can remain unused while still communicating normally. |
| **No grid data** | Grid power or meter measurements | Meter polling interval and gateway health. |
| **Zero energy change** | Cumulative import, export, production, charge, or discharge counters | A stable counter is different from a missing signal. |
| **Low performance ratio** | Production relative to irradiation and installed capacity | Irradiation quality, weather delay, curtailment, and maintenance. |
| **Low uptime** | Valid operating time relative to expected time | Site schedule and measurement completeness. |

<ClickableImage src="/img/eniris/monitoring/screenshots/alarm-library.webp" alt="SmartgridX alarm library with common no-data, low-delta, performance-ratio, and uptime alarms" maxWidth="1140px" />

*The alarm library makes the distinction between no-data, low-delta, performance-ratio, and uptime checks visible before you edit a rule.*

## PI monitoring is added manually

[Performance index (PI) monitoring](/Monitoring/Web%20portal/management/alarms/performance-index) is not included in automatic dashboard setup. Add it through **Add alarm → Performance index (PI)** for one installation or **All eligible sites**. This applies to currently eligible sites only; new installations are not enrolled automatically and existing PI rules are skipped.

The initial settings are **90% minimum PI** over **3 complete days**. These are the starting values in the manual editor, not a rule that is activated by default. Configure notification recipients separately.

## Tune by source and site type

- continuously connected controllers can use shorter no-data delays than daily FTP uploads;
- solar rules should avoid night-time false positives;
- EV charging requires a distinction between communication and actual charging activity;
- PR and uptime need reliable reference data and enough complete days;
- a newly commissioned site may require a stabilisation period.

<Callout type="warning" title="Do not copy thresholds blindly">
  Validate each threshold against a known healthy period and a known incident. An alarm that is always active or never active is not operational supervision.
</Callout>

## Review after commissioning

Review the alarm set after the first week and first full reporting period. Track nuisance alarms, missed events, delivery delays, and site-specific operating windows, then adjust the most specific matching rule rather than weakening the global fallback.


# Alarm rules


import ClickableImage from '@/components/ClickableImage';

# Alarm rules

An alarm represents an undesirable measured state. It can be shown in portfolio tables, device pages, alarm dashboards, and reports. Alarm watchdogs have been replaced by Advanced alarms. See [Advanced alarms: rules and analysis](./advanced-alarms) for the current rule setup and notification workflow.

## Common alarm logic

Configured environments can evaluate conditions such as:

- no recent data for an expected signal;
- insufficient change in a cumulative energy counter;
- low performance ratio;
- low uptime;
- manufacturer-reported fault states;
- organisation-specific dashboard alarm logic.

## Rule inputs

| Input | Purpose |
| --- | --- |
| **Signals** | Defines which telemetry series supplies the condition. |
| **Node types** | Limits the logic to applicable device categories. |
| **Tags or source characteristics** | Applies different behaviour to subgroups or data-delivery methods. |
| **Lookback period** | Defines the historical window used for evaluation. |
| **Active time window** | Avoids evaluating an expected inactive period, such as solar production at night. |
| **Threshold** | Defines the boundary between expected and undesirable behaviour. |

<ClickableImage src="/img/eniris/monitoring/screenshots/alarm-rule-editor.webp" alt="SmartgridX alarm-rule editor with supervised signals, node types, text labels, and evaluation period" maxWidth="1140px" />

*A rule combines supervised signals and node types with a lookback period and optional filters.*

## Order-specific rules

When several rules can match the same asset, place the most specific rule before the general fallback. For example, a daily FTP source can require a longer no-data period than a continuously connected controller.

<Callout type="warning" title="Separate missing data from zero production">
  No data means the signal did not arrive. Zero production means data arrived and its value or counter change was insufficient. They require different diagnosis and should not share the same alarm meaning.
</Callout>

## Validate a new alarm

1. Test one known device and time range.
2. Confirm the selected series and unit.
3. Verify timezone and active window.
4. Trigger or reproduce the condition.
5. Confirm the alarm clears when the condition is resolved.
6. Only then attach notification actions or broad portfolio scope.


# Advanced alarms


import { FolderOverview } from '@/components/FolderOverview';
import ClickableImage from '@/components/ClickableImage';

# Advanced alarms

Advanced alarms has replaced alarm watchdogs. It evaluates installation telemetry, shows the evidence behind each result, and notifies recipients when conditions open or resolve.

Follow [Advanced alarms: rules and analysis](./advanced-alarms) for the current setup instructions.

<ClickableImage src="/img/eniris/monitoring/screenshots/alarm-management.webp" alt="An anonymized SmartgridX alarm overview grouped by installation" maxWidth="1140px" />

*Group alarms by installation or device type, then compare communication, production, storage, grid, PR, and uptime signals. Example entities and values are anonymized.*

<ClickableImage src="/img/eniris/monitoring/screenshots/manufacturer-alarm-log.webp" alt="The SmartgridX manufacturer alarm log with grouping, filtering, and time controls" maxWidth="1140px" />

*Manufacturer alarms have their own log and filters. Check it separately from Insights alarm logic when a device reports an internal fault.*

## Choose the right workflow

| Need | Start with |
| --- | --- |
| Create alarm rules and configure notifications | [Rules and analysis](./advanced-alarms) |
| Monitor EMS behaviour using grid, PV, battery, planning, price, or external-control telemetry | [Advanced alarms rules](./advanced-alarms#rule-catalogue) |
| Monitor measured PV production against expected production | [Performance index (PI) monitoring](/Monitoring/Web%20portal/management/alarms/performance-index) |
| Open Advanced alarms in SmartgridX | [Access and loading](./access) |
| Review faults reported by the device manufacturer | The manufacturer alarm log in the installation or device view |

## Advanced alarms guides

<FolderOverview folder="Monitoring/Web portal/management/alarms" />



# Performance index (PI) monitoring


# Performance index (PI) monitoring

Performance index (PI) monitoring detects PV installations that produce less energy than expected. Add it through **Add alarm → Performance index (PI)** in **Advanced alarms**, for one installation or all eligible installations in the selected organisation.

**PI monitoring is an explicit choice.** Automatic dashboard setup never adds this alarm, and new installations are not enrolled automatically.

## Add PI monitoring

1. Open **Advanced alarms** for the organisation you want to monitor.
2. Select **Add alarm**, then **Performance index (PI)**.
3. Choose **One site** or **All eligible sites**. For one site, select the installation.
4. Set **Minimum PI (%)** and **Measurement window (full days)**.
5. Review the number of eligible sites and new alarms. Expand the unavailable-sites list to see why an installation cannot be included.
6. Select **Add PI monitoring** and wait for saving to finish.
7. Open **Analysis** after the first evaluation to check the result and the evaluated period.

| Setting | Default | Effect |
| --- | --- | --- |
| Minimum PI (%) | 90% | An alarm opens when the PI for the entire measurement window is below this value. The editor accepts 0.1% to 100%. |
| Measurement window (full days) | 3 days | The number of complete local calendar days to evaluate. Choose 1 to 14 days. |
| Scope | One site | Select one installation or all currently eligible installations in the selected organisation. |

**All eligible sites** adds an individual rule to each suitable current installation. Existing PI rules are skipped, so adding the same portfolio again does not create duplicate PI rules or change their settings. Repeat this action when you want to include newly added installations. Account limits on monitored sites still apply.

Use **Edit alarm** to change an existing rule's minimum PI or measurement window. A rule can also be disabled without deleting its settings.

## What PI measures

**PI (%) = total measured PV energy ÷ total expected PV energy × 100**

The calculation sums energy over the measurement window before dividing. It is not an average of the hourly percentages: hours with more expected production have more weight.

Expected production follows the installation's production configuration and applicable targets in Insights. Depending on the configuration, this uses installed PV capacity, panel orientation, location and irradiation data, together with the correction factor and dated PR targets. A supported production plan configured for the installation can also provide the expectation. Review these settings under **Features → Targets** and in the installation's production settings.

For the irradiation-based expectation, the configured correction factor is used when no dated PR target applies. The fallback factor is **0.8** when no specific correction factor is configured. A target change during the measurement window is applied to its corresponding period.

### PI and PR are different

Performance ratio (PR) compares measured production with theoretical ideal production. PI compares measured production with the configured expected production, which already accounts for the expected performance.

For example, with no curtailment:

| Quantity | Example |
| --- | --- |
| Theoretical ideal production | 1,000 kWh |
| Expected performance factor | 80% |
| Expected production | 800 kWh |
| Measured production | 720 kWh |
| PR | 72%: 720 ÷ 1,000 × 100 |
| PI | 90%: 720 ÷ 800 × 100 |

With a minimum PI of 90%, this example meets the limit. The alarm opens only below the limit. A PI above 100% means measured production exceeded the configured expectation. PI monitoring can be used independently of a separate PR alarm.

## Which days are evaluated?

The rule uses complete calendar days in the installation's time zone and leaves **one full day for meteorological data to become available**. It does not compare an incomplete current day with a full-day expectation.

For example, an evaluation on 25 June with a three-day window covers **21, 22 and 23 June**. It excludes 24 June for the weather-data delay and excludes the current day, 25 June. A longer window smooths daily fluctuations; a shorter window reacts to a smaller period of production.

## Curtailment and missing data

When configured curtailment telemetry indicates production limiting, the affected hours are excluded from **both measured and expected energy**. Curtailment that is not recorded in the available telemetry cannot be excluded automatically.

The rule needs valid production and reference data for the relevant hours. Missing, incomplete or invalid production, irradiation or configured curtailment data gives **No data / PI unavailable**. Missing data is not replaced by zero production, does not create a PI underperformance alarm and does not confirm recovery from an existing alarm.

The result is also unavailable when there is no expected production or when the entire evaluated production period is excluded because of curtailment. Eligibility at setup confirms that a calculation can be configured; it does not guarantee that all historical measurements have arrived.

## Read the result and analysis

- **OK:** the PI for the measurement window meets or exceeds the configured minimum.
- **Firing:** the PI for the measurement window is below the minimum. Open **Analysis** to investigate production and the configured expectation.
- **No data:** the calculation cannot be completed reliably. Read the reason before changing thresholds.
- **Pending / loading:** the evaluation has not finished yet. Wait for a completed result.

The analysis graph shows **hourly PI values**. The displayed overall result and alarm decision use the **energy totals for the entire window**. A single hourly dip below the line does not by itself trigger the period alarm, and averaging the plotted percentages will not necessarily reproduce the overall PI.

## Enable email notifications

Creating PI rules enables monitoring in the dashboard. It does not create or activate email recipients.

1. Open **Alarm recipients**.
2. Add or edit the recipient's email address.
3. Select the installations to include, or all installations, and the notification language.
4. Choose a minimum email interval of **1, 3, 6 or 24 hours**.
5. Enable **Active** when you want delivery to begin, and save.

Emails bundle newly opened alarms and confirmed recoveries. Repeated evaluations of the same open condition do not produce a new notification each time. You can leave a recipient inactive while checking the dashboard results. See [Notifications](/Monitoring/Web%20portal/management/alarms/advanced-alarms#notifications) for the shared delivery behaviour.

## Troubleshooting

| What you see | What to check |
| --- | --- |
| An installation is unavailable during setup | Check its production measurements, PV configuration and applicable targets. The editor lists a reason for each unavailable site. |
| PI remains unavailable after saving | Check production, irradiation and any configured curtailment series for the evaluated dates. Wait for delayed source data to arrive; the weather-data lag is already included in the window. |
| A production plan on child devices is not supported | Review the production plan at installation level. The rule reports an unavailable result rather than ignoring unsupported child-device targets. |
| The selected window requires too much detailed data | Select fewer days, as requested by the message. |
| PI is unexpectedly high or low | Check installed capacity, panel orientation, location, correction factor, dated targets and the production-data mapping. Compare PI with expected production rather than with the PR percentage. |
| A low hourly value does not open an alarm | Compare the overall PI with the minimum; the rule evaluates the full-window energy totals. |
| A new installation has no PI rule | Add it manually, or run **All eligible sites** again. Automatic setup never adds PI rules. |
| No email arrives | Check the recipient's **Active** setting, site scope, delivery interval and whether a new alarm or confirmed recovery occurred. |


# Watchdogs replaced by Advanced alarms


# Watchdogs replaced by Advanced alarms

Alarm watchdogs have been replaced by **Advanced alarms**.

See [Advanced alarms: rules and analysis](./advanced-alarms) for the current instructions on creating alarm rules, reviewing results, and configuring notifications.

For help opening the feature, see [Access and loading](./access).


# Customer records


import ClickableImage from '@/components/ClickableImage';

# Customer records

The current SmartgridX navigation adds a **Customers** entry when the device forest contains at least one `customerFile` node. Customer records are therefore portfolio assets, not merely address-book entries.

<ClickableImage src="/img/eniris/monitoring/screenshots/customer-management.webp" alt="An anonymized SmartgridX customer-record table" maxWidth="1140px" />

*The customer table shows organisational records and how many installations belong to each record. All example entries are anonymized.*

## Create a customer record

1. Open the owner-only **Add** page.
2. Choose a creatable customer-file or customer-record type when available.
3. Enter a clear customer name.
4. Create the virtual asset.
5. Link or organise the relevant installations beneath the intended customer structure.
6. Add contacts and role memberships separately.

<ClickableImage src="/img/eniris/monitoring/screenshots/customer-installation-hierarchy.webp" alt="An anonymized customer record with its installation and device hierarchy" maxWidth="1140px" />

*Opening a customer record exposes the installations and devices organised beneath that customer context.*

## What customer records are useful for

- grouping installations by customer responsibility;
- attaching customer-level contacts or documents;
- building configured customer-file dashboard routes;
- assigning scoped roles;
- giving reports and alarms a stable organisational context.

<Callout type="info" title="Customer, contact, and user are different objects">
  A customer record organises assets. A contact stores communication details. A user receives portal access through a role. Creating one does not automatically create the other two.
</Callout>


# Incident surveillance


# Incident surveillance

Some SmartgridX environments include a configured incident-surveillance dashboard that aggregates conditions across several sites. This is not a universal static route in the current Insights application; it appears when the active view supplies the matching dashboard route and configuration.

## Typical configuration

An incident rule can combine:

- all sites or a selected subset;
- controller availability, device error messages, or external-signal issues;
- a relative threshold based on the percentage of affected sites;
- an absolute threshold based on the number of affected sites;
- one or more email recipients.

## Incident surveillance and Advanced alarms

Alarm watchdogs have been replaced by [Advanced alarms](./alarms/advanced-alarms). Use that guide for alarm rules, analysis, and notifications. Incident surveillance aggregates conditions across sites.

| Use | Best fit |
| --- | --- |
| Notify when an alarm opens or resolves | [Advanced alarms notifications](./alarms/advanced-alarms#notifications). |
| Aggregate the number or percentage of affected sites into one portfolio condition | Configured incident surveillance. |
| Open the Advanced alarms workspace | [Access and loading](./alarms/access). |

<Callout type="warning" title="Verify the configured route">
  Because incident surveillance is dashboard-configured, field names and available triggers can differ by organisation. Use the labels in the active portal and test the threshold with a controlled condition before relying on it for escalation.
</Callout>


# Management


import { FolderOverview } from '@/components/FolderOverview';
import ClickableImage from '@/components/ClickableImage';

# Management

Management pages change the structure or behaviour of the monitoring environment. They are therefore filtered more strictly than read-only portfolio and device pages.

## Management areas

<Cards>
  <Card title="Assets and installations" description="Claim a controller, create a virtual asset, control visibility, or detach an asset safely." href="./add" />
  <Card title="Users and roles" description="Assign email addresses to the roles that determine which sites and actions a person can access." href="./user-management" />
  <Card title="Advanced alarms" description="Configure alarm logic, schedules, supervised entities, notification channels, and viewing rights." href="./alarms" />
  <Card title="Customers and incidents" description="Maintain customer-facing context and the operational follow-up information used by the portal." href="./customers" />
</Cards>

<ClickableImage src="/img/eniris/monitoring/screenshots/customer-management.webp" alt="An anonymized SmartgridX customer-record table" maxWidth="1140px" />

*Customer records keep commercial and operational context connected to the installations they cover.*

<ClickableImage src="/img/eniris/monitoring/screenshots/power-meter-management.webp" alt="An anonymized SmartgridX power-meter table with power, energy, and status columns" maxWidth="1140px" />

*Fleet tables make it possible to compare current power, accumulated energy, and device state across the portfolio.*

<ClickableImage src="/img/eniris/monitoring/screenshots/user-management.webp" alt="An anonymized SmartgridX user-management table with roles and member chips" maxWidth="1140px" />

<ClickableImage src="/img/eniris/monitoring/screenshots/alarm-management.webp" alt="An anonymized SmartgridX alarm overview grouped by installation" maxWidth="1140px" />

*Access management and supervision are separate responsibilities, even when the same administrator maintains both.*

## Why some management items are hidden

The current SmartgridX navigation applies concrete checks:

- **Add asset** is owner-only.
- **User management** appears for owners or administrators of supported site types.
- **Advanced alarms** must be enabled for the current role.
- **Reports and FTP** have their own feature and page-visibility checks.
- Destructive device actions are limited by device type and how the asset was created.

<Callout type="warning" title="Treat management actions as production changes">
  Removing a monitor relation, unclaiming a controller, changing a role, or deleting a configuration can immediately affect visibility and operations. Verify the selected company, view, site, and role before saving.
</Callout>

## Management guides

<FolderOverview folder="Monitoring/Web portal/management" />


# Power meters


import ClickableImage from '@/components/ClickableImage';

# Power meters

The **Power meters** page gives owners a portfolio-wide view of meter devices. It is most useful for checking whether grid, production, storage, and submeter data are arriving before you investigate an individual installation.

<ClickableImage src="/img/eniris/monitoring/screenshots/power-meter-management.webp" alt="An anonymized SmartgridX power-meter table with power, energy, and status columns" maxWidth="1140px" />

*Names, serial numbers, and values in this example are anonymized.*

## Read the table

| Column group | What to check |
| --- | --- |
| **Identity** | Confirm the meter name and serial number match the intended physical or virtual source. |
| **Active power** | Check the sign convention before interpreting import, export, charge, or discharge. |
| **Imported energy** | Compare daily and yearly totals with the expected consumption boundary. |
| **Exported energy** | Verify that generation or battery export is recorded on the intended meter. |
| **Status** | Treat stale or unavailable data as a communication or mapping issue before analysing energy totals. |

## Investigation workflow

1. Search for the meter by a stable name or serial number.
2. Confirm that the latest active-power value is plausible for the site state.
3. Compare yesterday's import and export with a known source when available.
4. Open the meter and inspect the relevant time range.
5. Check its parent installation and communication path when data is missing.
6. Record the meter, interval, unit, sign convention, and observed value when escalating.

<ClickableImage src="/img/eniris/monitoring/screenshots/power-meter-detail.webp" alt="An anonymized SmartgridX power-meter detail page with time-range and chart controls" maxWidth="1140px" />

*Open the meter to choose the exact interval, inspect its signal, and relate it back to the parent installation.*

<Callout type="warning" title="A negative value needs context">
  The meaning of a negative power value depends on the configured measurement direction. Verify the site's convention before reporting import, export, charging, or discharging.
</Callout>

## Combine meter signals

To add or subtract several meter signals without changing the installation topology, create a [virtual meter in Analyses](/Monitoring/Web%20portal/features/virtual-meters/). For a controller-side residual meter or an aggregate used for control, see [Virtual energy meters and meter aggregation](/Controller/Configuration%20from%20A%20to%20Z/11-Extra-Information/virtual-energy-meters/).


# Add or remove users


import ClickableImage from '@/components/ClickableImage';

# Add or remove users

The user-management page groups email addresses by role. Adding a person means creating or updating a membership for the selected role; it does not copy one universal permission set to the user.

## Add a user

1. Open **User management**.
2. Search for the intended role by role name or existing member email.
3. Confirm that the role belongs to the correct company, view, or installation scope.
4. Add the person's email address to that role.
5. Ask the person to use the invitation or password-reset flow associated with that email address.
6. Verify the result using the intended company and view.

Multiple email addresses can be parsed and added by the chip-list input, but review them before committing a bulk change.

<ClickableImage src="/img/eniris/monitoring/screenshots/user-role-membership.webp" alt="An anonymized SmartgridX role-membership example with owner, installer, and visitor roles" maxWidth="1140px" />

*Membership is granted on a role: always confirm the company, asset scope, and authority before adding the email address.*

## Remove a user

1. Locate the role containing the email address.
2. Remove the membership chip.
3. Confirm the removal dialog.
4. Use the short undo opportunity if the wrong member was selected.
5. Verify whether the person has access through another role.

<Callout type="warning" title="Removing one membership may not remove all access">
  A user can belong to multiple roles. Search the full user-management view before concluding that an email address no longer has access to the company or asset.
</Callout>

## Verification checklist

- correct company and view;
- correct installation scope;
- correct authority on the device;
- expected menu items only;
- no access to unrelated customer sites;
- report, alarm, and public-display rights appropriate for the role.


# User management


import { FolderOverview } from '@/components/FolderOverview';
import ClickableImage from '@/components/ClickableImage';

# User management

The current portal manages access by assigning email addresses to roles. The user table groups members by role, supports searching by role name or email address, and paginates large organisations.

<ClickableImage src="/img/eniris/monitoring/screenshots/user-management.webp" alt="An anonymized SmartgridX user-management table with roles and member chips" maxWidth="1140px" />

*Search by role or member, add people to the correct scope, and remove only the membership you intend to revoke. All addresses and role names shown here are examples.*

## How access is built

| Concept | Meaning |
| --- | --- |
| **Role** | A reusable access scope connected to a company, view, installation, or other managed entity. |
| **Member** | An email address assigned to that role. |
| **Device authority** | The resulting relationship on a device, such as visitor, installer, or administrator. |
| **Page settings** | The final filter that determines which sections that authority may see. |

Adding an email address updates the membership of the selected role. Removing a member requires confirmation and the interface offers a short undo window. Removing your own access can immediately change or end the current session.

<Callout type="info" title="Role names are organisation-specific">
  The application reads roles from the metadata service; it does not rely on one universal list of hard-coded role names. Use the role's actual scope and rights—not only its label—to decide where a person belongs.
</Callout>

## User-management guides

<FolderOverview folder="Monitoring/Web portal/management/user-management" />


# Roles and effective access


import ClickableImage from '@/components/ClickableImage';

# Roles and effective access

SmartgridX roles are metadata objects associated with a company and view. Their names can follow organisation-specific conventions, so the effective rights and scope matter more than the label alone.

## Access layers

| Layer | Question it answers |
| --- | --- |
| **Company and view** | Which SmartgridX environment is the person entering? |
| **Role membership** | Which managed scope is the person's email assigned to? |
| **Device authority** | Is the person a visitor, installer, or administrator for this device? |
| **Page settings** | Which sections are visible for that authority and device type? |
| **Feature settings** | Are reports, FTP, alarms, or other optional tools enabled? |

## Common role patterns

<ClickableImage src="/img/eniris/monitoring/screenshots/user-role-membership.webp" alt="An anonymized SmartgridX role-membership example with owner, installer, and visitor roles" maxWidth="1140px" />

*The membership list is the practical place to verify which email addresses currently inherit each role.*

- An organisation-wide owner or super-administrator role can manage the full view.
- Site-administrator roles can manage assigned installations without receiving company-wide ownership.
- Installer roles can receive technical access, including controller remote access where allowed, without every owner-only feature.
- Visitor or end-user roles usually receive read-only, audience-specific dashboards.

These are patterns, not hard-coded guarantees. Always inspect the role's actual relations and validate the resulting portal.

<Callout type="info" title="Why a menu differs between two users">
  The navigation is recalculated from ownership, device authority, active site types, page settings, feature flags, and available data. Different menus are expected when any of those inputs differ.
</Callout>


# Monitoring onboarding


import ClickableImage from '@/components/ClickableImage';

# Monitoring onboarding

A useful SmartgridX environment depends on more than a successful login. Complete onboarding in layers so that hierarchy, telemetry, access, and automation all refer to the same assets.

## 1. Confirm the company and view

- sign in with the invited email address;
- select the correct company and SmartgridX Monitoring view;
- accept any required policies;
- confirm the intended white-label domain and language.

The application builds its routes only after authentication, company data, view configuration, the device forest, white-label settings, and user preferences are available.

## 2. Add the asset source

Choose the workflow that matches the source:

- **claim a SmartgridOne controller** with its serial number and verification code;
- **create a virtual asset** for a supported manually managed node type;
- **configure a manufacturer integration** using the relevant integration guide;
- **prepare an FTP or historical import** for an approved file-based source.

<ClickableImage src="/img/eniris/monitoring/screenshots/claim-controller-and-add-asset.webp" alt="SmartgridX forms for claiming a controller and creating a virtual asset" maxWidth="1140px" />

*Choose the controller-claim or virtual-asset workflow according to the actual data source.*

## 3. Validate hierarchy and telemetry

Before styling dashboards or enabling reports:

1. confirm the site is under the correct company and site tag;
2. inspect the descendant hierarchy;
3. verify timezone and location;
4. check that expected streams produce valid charts;
5. compare one known meter or manufacturer value with Monitoring;
6. document any known historical gap.

<ClickableImage src="/img/eniris/monitoring/screenshots/installation-overview.webp" alt="An anonymized installation overview used to validate hierarchy, summary values, and telemetry" maxWidth="1140px" />

*Validate the hierarchy and one representative chart before continuing with presentation or automation.*

## 4. Configure the portal presentation

- choose site tags and translated labels;
- configure table columns and tiles;
- select device widgets and chart groups;
- define owner, administrator, installer, and visitor visibility;
- add organisation-specific translations and contacts.

<ClickableImage src="/img/eniris/monitoring/screenshots/dashboard-page-permissions.webp" alt="SmartgridX dashboard settings with page visibility per portal role" maxWidth="1140px" />

*Page visibility should be checked per role, not only from the administrator account.*

<ClickableImage src="/img/eniris/monitoring/screenshots/portfolio-element-selection.webp" alt="SmartgridX portfolio element selection for owner and visitor audiences" maxWidth="1140px" />

*Configure the portfolio fields that help each audience make a decision; hide fields that add noise.*

## 5. Assign user access

Add each person's email address to the narrowest role that satisfies their responsibility. Verify the result as that role; do not rely on the role name alone.

<ClickableImage src="/img/eniris/monitoring/screenshots/user-role-membership.webp" alt="An anonymized SmartgridX role-membership example with owner, installer, and visitor roles" maxWidth="1140px" />

*Membership chips make the effective role assignment visible before handover.*

## 6. Activate operations

After data and access are correct:

- create rules for the relevant installations using [Advanced alarms](./management/alarms/advanced-alarms);
- validate rule results in **Analysis** and verify notification recipients and frequency;
- create and preview reports with real device groups;
- add targets, documents, notes, and maintenance context;
- create public displays where required.

Alarm watchdogs have been replaced by Advanced alarms. Follow the [notification guide](./management/alarms/advanced-alarms#notifications) after validating the underlying telemetry and rule results.

<Callout type="warning" title="Do not automate unverified data">
  Alarm notifications and recurring reports amplify configuration errors. Validate the installation hierarchy, signal units, timezone, and one representative reporting period before enabling customer communication.
</Callout>

## 7. Handover checklist

- responsible owner and support contact identified;
- installation names and tags approved;
- users tested with least-privilege access;
- alarm recipient and clear notification tested;
- report preview approved;
- white-label email and login flows tested;
- data gaps and exceptions documented.


# Video tutorials


# Video tutorials

The SmartgridX video playlist contains visual walkthroughs for common portal tasks.

[Open the SmartgridX tutorial playlist on YouTube](https://www.youtube.com/playlist?list=PLHVO4E4u7MmljYgCPk7jsqzmk5hDfaZ5G)

<iframe
  title="SmartgridX tutorial playlist"
  width="100%"
  height="420"
  src="https://www.youtube.com/embed/videoseries?list=PLHVO4E4u7MmljYgCPk7jsqzmk5hDfaZ5G"
  allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture"
  allowFullScreen
></iframe>

<Callout type="info" title="Use the written guide for current behaviour">
  The application changes more frequently than recorded videos. When a button or menu differs, follow the current article and the role or feature-availability notes in these docs.
</Callout>


# What we monitor


import { MonitoringCoverageGrid, MonitoringScopeMap } from '@/components/MonitoringScope';
import ClickableImage from '@/components/ClickableImage';

# What SmartgridX monitors

SmartgridX Monitoring connects the commercial overview of an energy portfolio with the technical detail inside each installation. The platform can compare complete sites, follow individual energy assets, and—when the integration provides the data—continue down to components such as MPPT trackers, PV strings, battery racks, cells, phases, or charging connectors.

## Monitoring levels

<MonitoringScopeMap
  ariaLabel="SmartgridX monitoring levels"
  eyebrow="Monitoring depth"
  title="From an entire portfolio to one PV string"
  description="SmartgridX keeps every measurement in its operational context. Start broad, find the site that deviates, and drill down until the responsible device, component, or signal becomes visible."
  badge="Hierarchy-aware"
  levels={[
    { label: "Level 01", title: "Portfolio", summary: "Compare sites, rank exceptions, and see where attention is needed.", examples: ["Fleet KPIs", "Site comparison", "Alarm state"] },
    { label: "Level 02", title: "Installation", summary: "Understand the complete energy balance at one physical site.", examples: ["Grid exchange", "Generation & load", "Site availability"] },
    { label: "Level 03", title: "Asset", summary: "Investigate the individual device responsible for the site behaviour.", examples: ["Inverter", "Battery or BMS", "Meter or charger"] },
    { label: "Level 04", title: "Subcomponent", summary: "Drill into the internal structure when the connected system exposes it.", examples: ["MPPT & PV string", "Rack, module or cell", "Phase or connector"] },
    { label: "Level 05", title: "Signal & event", summary: "Follow the measurement, state, or alarm that explains what changed.", examples: ["Power & energy", "Voltage & current", "Status & alarms"] },
  ]}
  drillDownEyebrow="Example drill-down"
  drillDownTitle="Follow one production anomaly to its source"
  drillDown={[
    { label: "Portfolio", value: "Solar fleet" },
    { label: "Installation", value: "Warehouse site" },
    { label: "Asset", value: "Inverter 02" },
    { label: "Component", value: "MPPT 1" },
    { label: "Component", value: "String 1" },
    { label: "Signal", value: "DC current" },
  ]}
  noteTitle="The available depth is integration-specific."
  noteText="SmartgridX can show MPPTs, strings, battery racks, cells, phases, and connectors only when the device, gateway, or API exposes those objects and signals."
/>

The hierarchy prevents a measurement from becoming an isolated number. A drop in portfolio yield can be traced to one site, one inverter, one MPPT, one string, and finally the DC current or alarm that explains the deviation.

## Energy assets and systems

<MonitoringCoverageGrid
  ariaLabel="Monitored asset categories"
  areas={[
    { title: "Solar generation", summary: "From total PV production down to the available DC-side detail.", items: ["PV inverters", "MPPT trackers", "PV strings", "Irradiance & yield"] },
    { title: "Battery storage", summary: "Follow conversion, stored energy, limits, health, and availability.", items: ["Battery inverter / PCS", "BMS", "Racks, modules & cells", "SoC & temperature"] },
    { title: "Grid & consumption", summary: "Explain where energy enters, leaves, and is consumed within a site.", items: ["Grid meter", "Submeters", "Phases & circuits", "Power quality"] },
    { title: "Flexible assets", summary: "Supervise controllable loads and distributed energy equipment.", items: ["EV chargers & connectors", "Heat pumps", "Generators", "Controllable loads"] },
    { title: "Wind & other generation", summary: "Combine diverse generation technologies in the same portfolio view.", items: ["Wind turbines", "Generators", "Production meters", "Availability & alarms"] },
    { title: "Environment & I/O", summary: "Add the context required to interpret asset performance correctly.", items: ["Weather sensors", "Temperature", "Digital & analogue I/O", "Custom telemetry"] },
  ]}
/>

## What is measured

The exact signal set differs by manufacturer and integration, but SmartgridX commonly works with five signal families:

| Signal family | Typical examples | Why it matters |
| --- | --- | --- |
| **Energy flow** | Active and reactive power, import, export, production, consumption, charge, and discharge. | Explains the current energy balance and whether assets follow their intended operating mode. |
| **Energy counters** | Imported, exported, generated, consumed, charged, and discharged energy. | Supports reporting, comparison, savings calculations, and long-term performance analysis. |
| **Electrical detail** | Voltage, current, frequency, power factor, insulation resistance, and phase values. | Helps distinguish an energy-performance issue from an electrical or connection issue. |
| **State and health** | State of charge, temperature, availability, operating state, communication quality, and device status. | Shows whether equipment is available, constrained, overheated, offline, or operating normally. |
| **Events and context** | Manufacturer alarms, SmartgridX alarms, irradiance, weather, energy prices, setpoints, and grid limits. | Provides the context needed to explain why behaviour changed and whether intervention is required. |

## How deep can you go?

Monitoring depth is determined by the complete data route:

1. The device or its gateway must expose the component and signal.
2. The selected protocol, cloud API, or local integration must transport it.
3. The object must be mapped to the correct installation hierarchy.
4. The stream must contain valid units, timestamps, and values.
5. The page configuration and user role must make the data visible.

<Callout type="info" title="String-level monitoring is not automatic">
  Some inverters expose only total AC power. Others also expose each MPPT or PV string. Battery systems can similarly range from one combined SoC value to rack-, module-, or cell-level telemetry. SmartgridX displays the detail supplied by the supported integration; it does not derive component measurements that the source does not provide.
</Callout>

## How the hierarchy looks in the portal

<ClickableImage src="/img/eniris/monitoring/screenshots/descendant-devices-menu.webp" alt="An anonymized SmartgridX device hierarchy showing how users navigate from an installation to descendant assets" maxWidth="1140px" />

*Use the descendant hierarchy to move from the installation overview to the device or component that explains the observed behaviour.*

## A practical investigation

Imagine that a solar portfolio produces less than expected:

1. **Portfolio:** identify the installation with the largest deviation.
2. **Installation:** compare total PV production with irradiance and grid exchange.
3. **Asset:** compare the inverters and find the unit producing less than its siblings.
4. **Subcomponent:** compare MPPT trackers or strings when those children are available.
5. **Signal:** review DC current, voltage, temperature, status, and alarms over the same period.

This same method applies to a battery that does not reach its target SoC, an EV charger that is unavailable, a meter with implausible values, or a controllable load that does not follow its setpoint.


# Portal styling and logos


# Portal styling and logos

The current white-label model supports dashboard logos, a dark-mode logo, a website URL, style configuration, and sidebar styling. Organisation-level logos can override environment defaults.

## Logo precedence

For SmartgridX Monitoring, the portal first checks the company device-forest settings for the light- or dark-mode logo. When absent, it can fall back to the white-label dashboard logo.

Use:

- an HTTPS URL reachable without authentication;
- SVG or a high-resolution transparent raster where supported;
- separate assets when one logo does not work in both themes;
- concise alternative text and adequate surrounding space.

![An example of portal white-label settings.](/img/generic/whitelabel.png)

## Custom styling

Custom styles can align colours and spacing with the organisation brand, but they should not override functional state colours blindly.

![An example of advanced white-label styling.](/img/generic/whitelabel-css.png)

<Callout type="warning" title="Test application states, not only the homepage">
  Check dialogs, validation errors, selected rows, charts, alarms, disabled buttons, focus outlines, mobile navigation, printing, and both colour themes. Preserve readable contrast and visible keyboard focus.
</Callout>


# White-label email


# White-label email

White-label email can affect invitations, password resets, alarm notifications, and report distribution. The sender setup is an operational integration and should be configured through the approved support process.

## Information to prepare

- sender display name and address;
- reply-to address;
- approved SMTP or mail-provider configuration;
- permitted sending domains;
- logo and brand colours;
- required languages;
- contact for delivery failures.

Share secrets only through the approved credential channel, not in a general support-ticket message.

## Validation

Test:

- new-user or access email;
- password reset;
- alarm activation and recovery;
- report attachment and subject;
- SPF, DKIM, and DMARC alignment where applicable;
- delivery to at least two external mail providers.

<Callout type="warning" title="Do not send passwords by email">
  Invite users to establish or reset their own password. Operational emails should identify the correct domain and never contain reusable credentials.
</Callout>


# Whitelabeling


import { FolderOverview } from '@/components/FolderOverview';

# Whitelabeling

Whitelabeling changes more than a logo. The current portal resolves branding from both organisation settings and the active white-label environment.

## What can be branded

- light- and dark-mode logos;
- login-page presentation;
- domain or subdomain;
- transactional email identity and content;
- colours and additional CSS where supported;
- product names and translated interface labels;
- environment-level feature flags, such as the optional **Advanced alarms** entry.

The company logo takes precedence when configured; otherwise the portal can fall back to the white-label dashboard logo. URLs are normalised before display, so use a publicly reachable HTTPS asset.

<Callout type="warning" title="Test both appearance and behaviour">
  Validate desktop and mobile layouts, light and dark mode, login and password-reset emails, public-display assets, and any feature flags. A valid colour or CSS rule can still reduce contrast or hide an interactive state.
</Callout>

## Whitelabel guides

<FolderOverview folder="Monitoring/Web portal/whitelabeling" />


# White-label login page


# White-label login page

The current login layout reads its presentation from the white-label configuration.

## Supported presentation settings

- login logo;
- background as a colour, image, or media object;
- WebM video background;
- fallback background colour;
- button colour;
- text colour;
- optional business-registration visibility.

When a background is a plain six-digit hexadecimal colour, the layout renders a colour. Other string values are treated as media URLs. A structured background can provide media plus a fallback colour.

## Video recommendations

- use WebM for the current video-rendering path;
- keep the file small enough for a fast first load;
- avoid rapid flashes or essential text in the video;
- provide a fallback colour;
- verify autoplay and reduced-motion behaviour in the target browsers.

<video controls muted style={{ maxWidth: '520px', width: '100%', borderRadius: '12px' }}>
  <source src="/img/generic/loginVideo.webm" type="video/webm" />
</video>

<Callout type="warning" title="Authentication must remain the focus">
  Branding must not obscure input labels, validation errors, password-reset links, policy messages, or keyboard focus. Test the complete sign-in and reset flow after every login-page change.
</Callout>


# White-label domain


# White-label domain

A custom monitoring domain provides a branded entry point for the login page and dashboard. Coordinate the exact DNS target with Eniris before creating the record, because infrastructure targets can change independently of the Insights application code.

## Recommended DNS pattern

Use a dedicated hostname such as `monitoring.example.com` and create the instructed CNAME record rather than pointing directly to an IP address.

## Deployment checklist

1. Agree the final hostname and responsible DNS administrator.
2. Obtain the current CNAME target from Eniris.
3. Create the DNS record with a temporary low TTL if a migration is planned.
4. Wait for DNS propagation.
5. Confirm HTTPS certificate issuance.
6. Configure login and dashboard branding.
7. Test sign-in, password reset, logout, policy acceptance, documentation links, and email URLs.
8. Increase the TTL after validation.

<Callout type="warning" title="Do not point to an undocumented IP address">
  Direct IP records make migrations and failover harder and can break TLS routing. Use the hostname supplied for the white-label environment.
</Callout>


# Start here


import { ChapterLanding } from '@/components/ChapterLanding';
import CustomerOnly from '@/components/CustomerOnly';
import { FolderOverview } from '@/components/FolderOverview';

<ChapterLanding
  chapter="simulations"
  introductionLabel="Chapter introduction"
  eyebrow="Energy-system modelling"
  title="Eniris Simulations"
  description="Explore technical and commercial energy choices before committing to them. Build a consistent starting point, compare scenarios, and use the results to support a well-founded project decision."
  highlightOne="Scenario comparison"
  highlightTwo="Transparent assumptions"
  highlightThree="Decision support"
/>

## From an energy question to a confident decision

Eniris Simulations helps structure an energy study around three simple questions: **what is the current situation, what could change, and what does that change mean?** A simulation connects site data and clearly documented assumptions to outcomes that can be compared on the same basis.

Use this chapter to prepare reliable inputs, understand how scenarios differ, and review results without losing sight of data quality, operational constraints, or the original project objective.

<Cards>
  <Card title="1. Frame the study" description="Define the question, reference situation, decision criteria, and boundaries before modelling starts." href="./getting-started" />
  <Card title="2. Prepare the inputs" description="Collect site, consumption, production, asset, tariff, and operational assumptions in a traceable way." href="./inputs-and-assumptions" />
  <Card title="3. Review the outcome" description="Compare scenarios, test sensitivities, and distinguish modelled results from measured performance." href="./reviewing-results" />
</Cards>

> [!IMPORTANT]
> The landing page is public. Detailed simulation guides can contain customer-specific methods and context, so every article in this chapter requires a customer sign-in. Selecting a guide while signed out opens the secure login page.



## What to prepare

Before starting a simulation project, gather the best available interval data, describe the existing installation and grid connection, and record the decisions the study needs to support. Missing values and uncertain assumptions are not a reason to stop, but they should always remain visible in the interpretation.

> [!NOTE]
> A simulation is a decision-support model. Its value depends on the quality of the input data and assumptions, and its results should not be presented as guaranteed measured performance.


# Connection architecture


import ClickableImage from '@/components/ClickableImage';

# Connection architecture

SmartgridX VPP can combine assets that use different connection routes. Select the route per site based on the existing infrastructure, the required response, and whether local control is needed.

<ClickableImage
  src="/img/vpp/connection-architecture.svg"
  alt="Different sites and energy assets connecting through the VPP API, SmartgridOne, or SmartgridOne Cloud into one SmartgridX VPP portfolio"
  maxWidth="900px"
/>

## Connection routes

| Connection | Best suited for | What it provides |
| --- | --- | --- |
| **VPP API** | Assets already connected to an EMS or cloud platform | Cloud-to-cloud onboarding without installing another controller, while the existing setup remains under your ownership. |
| **SmartgridOne** | Sites that benefit from reliable local control | Hardware-level control on site, local execution of commands, and compatibility with third-party EMS logic. |
| **SmartgridOne Cloud** | Assets that can be managed entirely through a cloud connection | Centralised asset control without a physical SmartgridOne controller at every site, where supported. |

A portfolio can use more than one route. For example, one group of sites can use local SmartgridOne controllers while another group connects through a manufacturer's platform or a third-party EMS.

## How to choose

Consider the following for every asset or site:

- whether a compatible controller or EMS is already installed;
- whether commands must continue locally during a cloud interruption;
- which protocols or APIs are available;
- the required command frequency and response time;
- network ownership, firewall restrictions, and security requirements; and
- who remains responsible for the local controls and equipment limits.

## Connection details to collect

- **Connection route:** SmartgridOne, customer EMS, VPP API, or manufacturer platform
- **Controller serial number** when SmartgridOne is already installed
- **Interface or protocol:** for example Modbus TCP/RTU, SunSpec, API, or MQTT
- **Network setup:** internet route, firewall restrictions, and responsible network contact
- **MQTT setup:** availability of ports `1883` or `8883`, plus the required TLS and authentication method
- **MQTT credentials:** credentials for the Eniris broker must be requested through the [Eniris webshop](https://webshop.eniris.com/); project onboarding does not create them automatically
- **Technical documentation:** device protocol or register documentation for custom integrations

> [!TIP]
> Use the [Controller documentation](/Controller/) for local SmartgridOne integrations. Use the [Eniris API documentation](../API/api) for cloud and data integrations.

When a device needs a custom integration, submit the specifications through the [Eniris integration request form](https://www.eniris.com/integration_request).


# Control and data


import ClickableImage from '@/components/ClickableImage';

# Control and data

VPP optimisation must stay within the technical boundaries of each asset, site, and grid connection. Define the control contract before market activation so that every command has an unambiguous meaning and a safe fallback.

<ClickableImage
  src="/img/vpp/control-and-data.svg"
  alt="VPP command path from dispatch through SmartgridX and the safety envelope to local control, with measurements and health data returning as feedback"
  maxWidth="900px"
/>

## Supported control patterns

Depending on the connected equipment and project setup, SmartgridX VPP can support:

- real-time import and export limits communicated over MQTT;
- control against quarter-hourly average set-points where enabled;
- automatic control modes that react to incoming grid signals;
- pre-configured fallback states when communication is interrupted; and
- handling of exceptional import or export limit signals.

## Define the command interface

Document the following for every controllable device or group:

- the device or group identifier;
- the agreed power and set-point convention, including sign and unit;
- command frequency and required response time;
- minimum and maximum allowed values;
- state-of-charge boundaries for batteries;
- timeout detection and the fallback behaviour after signal loss; and
- the party responsible for issuing, validating, and stopping commands.

## Feedback and historical data

The control loop should expose enough data to confirm whether a command was accepted and executed. Agree on:

- required real-time measurements and their update frequency;
- historical measurements and retention requirements;
- units, timestamps, and time zone conventions;
- command acknowledgement and actual-versus-requested power;
- availability and communication-health signals; and
- KPIs required per battery, site, and portfolio.

## Safety hierarchy

Local protection settings, device limits, and grid-connection constraints remain leading. A VPP command must never override equipment protection or an agreed site limit.

> [!WARNING]
> Define and test fallback behaviour before enabling external dispatch. A lost, delayed, or invalid signal must result in a known safe state.


# Start here


import { ChapterLanding } from '@/components/ChapterLanding';
import { FolderOverview } from '@/components/FolderOverview';
import ClickableImage from '@/components/ClickableImage';

<ChapterLanding
  chapter="vpp"
  introductionLabel="Chapter introduction"
  eyebrow="Virtual power plant"
  title="SmartgridX - VPP"
  description="Bring batteries, solar installations, heat pumps, and charging stations together in one flexible portfolio. Connect existing systems, choose the energy markets that fit your strategy, and retain control over how every asset is operated."
  highlightOne="Multi-asset portfolios"
  highlightTwo="Market participation"
  highlightThree="Grid control"
/>

## What SmartgridX VPP does

SmartgridX VPP connects distributed energy assets and makes their combined flexibility available as one controllable portfolio. Assets can run on [SmartgridOne](/Controller/), remain under a third-party energy management system, or connect cloud-to-cloud through an API.

The platform is designed for energy suppliers, traders, aggregators, balance responsible parties, balance service providers, and asset operators that want to coordinate many installations without giving up ownership of their setup or strategy.

<ClickableImage
  src="/img/vpp/portfolio-overview.svg"
  alt="Distributed energy assets aggregated into one SmartgridX VPP portfolio for market participation, coordinated control, and portfolio visibility"
  maxWidth="900px"
/>

At a high level, the VPP workflow is:

1. **Connect assets** such as batteries, PV installations, heat pumps, and EV chargers.
2. **Aggregate flexibility** across residential, commercial, or industrial sites.
3. **Choose a market strategy** for the portfolio or connect your own trading logic.
4. **Dispatch set-points** while respecting local limits, safety constraints, and fallback behaviour.
5. **Monitor the result** across the portfolio in SmartgridX.

## Explore SmartgridX VPP

<FolderOverview folder="VPP" columns={2} />

## Where to continue

- For SmartgridOne hardware, local integrations, and commissioning, use the [Controller documentation](/Controller/).
- For cloud and data integrations, use the [Eniris API documentation](../API/api).
- For dashboards, installation management, and portfolio visibility, continue to [SmartgridX - Monitoring](/Monitoring/).
- For the current commercial offering, read the [SmartgridX Virtual Power Plant overview](https://eniris.com/services/virtual-power-plant).

> [!NOTE]
> Feature availability depends on the connected assets, selected markets, contractual setup, and country-specific requirements.


# Markets and optimisation


import ClickableImage from '@/components/ClickableImage';

# Markets and optimisation

SmartgridX VPP does not require every portfolio to participate in the same markets. Select only the services that match the assets, commercial roles, and technical capabilities in scope.

<ClickableImage
  src="/img/vpp/markets-and-optimisation.svg"
  alt="Available portfolio flexibility optimised by SmartgridX VPP for energy markets and custom strategies while respecting technical priorities"
  maxWidth="900px"
/>

## Market options

| Market or service | Typical VPP activity |
| --- | --- |
| **Day-Ahead and Intraday** | Schedule charging, discharging, and flexible consumption against energy prices. |
| **Imbalance** | Curtail PV or steer batteries using local imbalance data, price signals, or third-party forecasts. |
| **Ancillary services** | Make qualified flexibility available through aggregators or in cooperation with balancing service providers. |
| **Forecasting and custom optimisation** | Forecast available flexibility per asset and translate your own prices, forecasts, or algorithms into actions. |

## Route to market

A portfolio can reach a market through:

- an aggregator;
- a direct connection as a balance responsible party (BRP) or balancing service provider (BSP), where applicable; or
- a trading desk connected to the SmartgridX VPP API.

Confirm the portfolio, balancing group, trader, BRP, BSP, and contractual responsibilities before activation.

## Portfolio strategy

Define which objective has priority when several opportunities compete for the same flexibility. Include:

- the participating assets and markets;
- reserved capacity and unavailable state-of-charge ranges;
- asset and site constraints;
- minimum expected value or activation rules;
- the forecasts and price signals that may be used; and
- how conflicts between market, site, and customer objectives are resolved.

Commercial access, qualification rules, and technical requirements vary by market and country. Confirm the applicable requirements before enabling a strategy.

## Portfolio visibility

Use SmartgridX to view the combined portfolio, follow production and market signals, and inspect how individual installations contribute to the aggregate result. For dashboards and installation management, continue to [SmartgridX - Monitoring](/Monitoring/).


# Onboarding checklist


import ClickableImage from '@/components/ClickableImage';

# VPP onboarding checklist

Use this checklist to collect the information required for technical intake and onboarding.

<ClickableImage
  src="/img/vpp/onboarding-checklist.svg"
  alt="Four-step VPP onboarding flow covering site and roles, assets, connectivity, and control and data"
  maxWidth="900px"
/>

## Site and commercial identification

- **Site name**
- **Requested go-live date**
- **Portfolio, balancing group, and trader/BRP/BSP assignment**, where applicable

## Assets and grid connection

- **Asset type:** PV, battery, EV charging, heat pump, or controllable load
- **Manufacturer, exact model, firmware version, and number of devices**
- **Nominal power in kW**; for batteries, also include usable capacity in kWh, minimum and maximum state of charge (SoC), and charge/discharge limits
- **Grid-meter make and model**, plus the maximum grid-connection power
- **Device protocol or register documentation** when a custom integration is required; also submit this information through the [Eniris integration request form](https://www.eniris.com/integration_request)

## Connectivity

- **Connection route:** a SmartgridOne controller, the customer's EMS, an API, or the manufacturer's platform
- **Controller serial number** if a controller is already installed
- **Available interface or protocol**, for example Modbus TCP/RTU, SunSpec, API, or MQTT
- **Internet and network setup**, including firewall restrictions and the responsible network contact
- **MQTT connectivity:** availability of ports `1883` or `8883` and the required TLS and security setup
- **MQTT credentials:** for connections to the Eniris MQTT broker, request the username and password through the [Eniris webshop](https://webshop.eniris.com/)

## VPP control and data

- **Controllable devices or groups** and the agreed power or set-point convention
- **Command frequency and required response time**
- **Fallback behaviour and timeout** if the external signal is lost
- **Required real-time feedback and historical data**, including units and timestamps
- **Availability and health signals**, including the KPIs required per battery or site

## What happens next

With this information, Eniris can determine the connection architecture, identify missing technical details, and agree on the onboarding route for the portfolio.

> [!NOTE]
> Feature availability depends on the connected assets, selected markets, contractual setup, and country-specific requirements.