Connect, monitor and control compatible energy devices through manufacturer clouds and partner APIs — without requiring a local protocol connection to every asset.
SmartgridOne Cloud runs the 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.
No local device bus The device communicates through its existing vendor cloud or partner platform.
Portfolio-ready Multiple remote sites can be imported and managed from one environment.
Internet-dependent Availability, latency and fallback behaviour depend on both internet access and the vendor API.
The devices below can receive control actions through a cloud connection. A check in this table means that an Eniris integration already 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 |
| Battery / PV | Neovolt systems linked to a Neovolt account | Neovolt Cloud API | Monitoring and storage strategy control | Neovolt Cloud API |
| Battery | Greener / Alfen battery containers, 250 kWh–2 MWh | Greener API | Monitoring and constant-power setpoint | Greener / Alfen |
| PV | Huawei inverters and SmartLoggers managed by NetEco | Huawei NetEco | Site import and inverter or SmartLogger control | Huawei NetEco |
| PV | SMA inverters connected to an SMA Data Manager | SMA cloud API | Active-power and curtailment control | SMA cloud control |
| PV | SolarEdge inverters on one SolarEdge monitoring site | SolarEdge Grid Services API | Site-level monitoring and percentage power limitation | SolarEdge cloud control |
| PV / hybrid | Solis PV inverters and supported hybrid inverters | SolisCloud API V3 | Monitoring and device control; hybrid support is marked experimental | SolisCloud API V3 |
| PV | Sungrow inverters registered in iSolarCloud | iSolarCloud Open API | Monitoring and active-power limitation; firmware support can vary | Sungrow iSolarCloud |
| PV | Sparky-connected systems | Sparky Cloud API | Cloud site import and controller strategy integration | Sparky Cloud API |
| EV charging | Easee One, Up, Max, Pro, Charge and Core | Easee Cloud API | Charging-station communication and control | Easee |
| EV charging | Zaptec Go, Go 2 and Pro | Zaptec API | Charging-station communication and control | Zaptec |
| EV charging | Wallbox Pulsar Plus/Max/Pro, eM4, Quasar 2, Commander and Copper SB | Wallbox API | Charging-station communication and control | Wallbox |
| EV charging | OCPP chargers connected through Volt Time Cloud | Volt Time Cloud / OCPP | Cloud charging control | Volt Time |
| Flexible load | MyEnergi Eddi | MyEnergi API | Boost or Block control; no watt-level setpoint | MyEnergi Eddi |
SolarEdge currently does not accept onboarding of new sites through the API. Existing integrations remain documented, but verify availability before planning a new deployment.
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 |
| Cloud Meter Data | Cloud-delivered grid-meter measurements | Measurement input only | Cloud Meter Data |
| P1 API meter | Grid import and export measurements | Measurement input only | P1 API |
| Zeversolar inverter | Inverter data through the existing API integration | Curtailment is not supported | Zeversolar |
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.
SmartgridOne Cloud can also represent virtual sites whose measurements arrive from a partner platform and whose setpoints are returned to that platform.
| 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 for the topic structure, measurements, commands and partner-specific prerequisites.
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.
Compatibility can change when manufacturers update their APIs or firmware. Check the linked device page during engineering and again during commissioning.