Configuration¶

Most options are reached from the integration entry: Settings → Devices & Services → Sungrow iSolarCloud → Configure.

Polling interval¶

The integration polls the iSolarCloud API on a fixed interval (default: 5 minutes). Lower it for fresher data or raise it to stay within the API's rate limits.

Custom measure points¶

The cloud returns a broad catalogue of measure points, but only the ones your hardware actually reports produce a value. If you need an additional point ID that isn't surfaced by default (for example a specific battery, meter, or EV-charger metric), add it under Custom measure points in the options — provide the numeric iSolarCloud point ID and it will appear as a sensor once it returns data.

Dispatch / control entities¶

For inverters that support it, the integration can expose number and select entities to control the battery and dispatch behaviour, such as:

• Charge / discharge command and power
• SOC upper / lower limits
• Forced charging schedules
• Energy-management / external-dispatch mode

When you set charge/discharge to Charge or Discharge, the integration switches Energy Management Mode to Compulsory (Forced) so the inverter actually follows the command, and sends the required EMS heartbeat so the setting is maintained. Stop restores Self-consumption mode.

Per-device sensors¶

Plant readings are already grouped under the physical device they come from — inverter, battery, meter or WiNet-S — nested beneath the plant (see Sensors → Device grouping). On top of that, you can optionally enable per-device sensors to fetch points reported only by an individual device (e.g. an EV charger or a second battery) and expose them under that device. Enabling this also surfaces the documented diagnostic points per device type — inverter temperature / MPPT voltages & currents, battery health (voltage, current, temperature, SOH), and WiNet-S WLAN/wireless signal strength.

Regardless of this option, every device gets a Fault (problem) and Connectivity (online/offline) binary sensor, and its device card is enriched with model, serial number and manufacturer. The Fault sensor exposes an operating_status attribute with a human-readable reason for inverter/ESS devices (e.g. Shut down due to faults, Low insulation resistance), and the Connectivity sensor exposes the commissioning date as an attribute.

Local Modbus (separate entry)¶

Local WiNet-S Modbus is a separate integration entry, not a field on the cloud options. Discover the dongle (or import a local entry) to get independent local sensors with their own poll interval. Cloud stays pure iSolarCloud. When serials match, the local inverter device is nested under the cloud plant in the device registry without merging values. See Local Modbus (WiNet-S).

Energy dashboard¶

Sensors are classified with the correct device_class / state_class, so energy points (Wh/kWh, device_class: energy) can be added directly to the Energy dashboard.