Sungrow iSolarCloud provides extensive energy and system data. Terms like yield, self-consumption or autonomy seem clear at first, but often lead to misunderstandings in practice. This article explains the most important metrics in iSolarCloud and puts them into context.
For a general overview, see Sungrow iSolarCloud: Features, Login & Data Overview.
What data does Sungrow iSolarCloud display?
Depending on system configuration and installed measurement hardware, the following values may be shown:
- PV yield
- real-time power
- electricity consumption
- self-consumption rate
- grid import
- feed-in
- battery state of charge
- system status
Not every system automatically shows all values. Scope and accuracy depend on inverter type, meters and storage system.
Yield in iSolarCloud
Yield describes the energy generated by the photovoltaic system. It is measured in kilowatt-hours and typically shown as:
- daily yield
- monthly yield
- yearly yield
- total yield
Yield only indicates how much electricity was produced, not how it was used.
Power vs Yield: an important difference
A common misunderstanding is confusing power with yield.
- Power (kW) is the current electricity production
- Yield (kWh) is the amount of energy generated over time
Fluctuating power values are normal and depend on weather, time of day and consumption.
Understanding consumption and self-consumption
Consumption describes the total electricity demand of a household or business.
Self-consumption is the share of generated solar power that is used directly or later taken from the battery.
High yield does not automatically mean high self-consumption, since part of the energy may be fed into the grid.
Grid import and feed-in
Grid import
Grid import is the electricity drawn from the public grid when the PV system does not produce enough or the battery is empty.
Feed-in
Feed-in is the portion of solar energy that is not used on-site and is exported to the grid.
Simplified formula:
PV yield = self-consumption + feed-in
Small deviations due to measurement differences are possible.
Storage values in Sungrow iSolarCloud
For systems with battery storage, additional data is displayed:
- battery state of charge in percent
- charging power
- discharging power
The battery increases self-consumption by storing excess solar energy.
Why do values fluctuate during the day?
Fluctuations are technically normal and caused by:
- changing solar irradiation
- varying electricity demand
- internal energy management
- charge and discharge cycles
Single data points should not be evaluated in isolation.
Autonomy and self-consumption rate
iSolarCloud often shows metrics such as:
- autonomy level
- self-consumption rate
These values are useful for long-term analysis but should not be judged based on a single day.
Data delay in iSolarCloud
Displayed data is updated with a delay.
This means:
- no guaranteed real-time data
- updates typically occur every few minutes
- daily values are only complete at the end of the day
For reliable analysis, completed time periods should be used.
Common misunderstandings about iSolarCloud data
- high yield does not mean high autonomy
- low feed-in is not an error
- differences between app and web portal are normal
- short-term fluctuations are system-related
Data should always be interpreted in context.
When is the data sufficient and when not?
Sufficient for:
- single systems
- private use
- general overview of energy flows
- optimizing self-consumption
Limited for:
- multiple locations
- cross-manufacturer analysis
- precise billing
- external reporting
Frequently asked questions about Sungrow iSolarCloud data (FAQ)
Why do yield and consumption not match?
Yield describes generated energy, while consumption describes used electricity. Some energy is fed into the grid or stored.
Why does my electricity meter show different values?
Utility meters are legally relevant. iSolarCloud uses internal measurements that may differ.
Why don’t I see consumption data?
Without suitable measurement hardware, consumption cannot be displayed correctly.
Is the data real-time?
No. Data is updated with a delay and is intended for analysis, not second-by-second monitoring.
