Check which devices and cloud platforms support remote control or monitoring through Cloud controller.
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.
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 |
| 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.
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 once the combination is confirmed.