Model support matrix¶

Which sensors and controls you get depends on your inverter family. Sungrow expose different measure points (and different point IDs) per model, so this page shows what to expect for each family — and, when something is missing, whether that's a model limitation or something to report.

The integration resolves the family automatically from the device's model code (device_model_code, e.g. SG3.6RS, SH10RT-20), and uses it to request the right points — for example the MPPT voltage/current range differs between string inverters and hybrids. A model the resolver doesn't recognise still works: it falls back to the generic, device-type behaviour, so nothing is lost — you just won't get the family-specific tuning.

Families¶

Prefix SG = PV string inverter (no battery); SH = hybrid with a battery. Suffix RS = single-phase; RT / T / CX = three-phase.

What each family reports¶

✅ = available where the API/model reports it. Points a specific model or firmware doesn't return are simply skipped (no broken entities). Battery rows depend on a battery actually being present — the dispatch battery controls are hidden on PV-only plants for safety.

Data sources¶

Any model can be connected through one of several transports (see transport modes): the official developer Cloud (OAuth, full sensors + dispatch), an unofficial user-account Cloud login (email/password, plant sensors + experimental dispatch, details), and local Modbus. The matrix below describes what a model reports; which of those datapoints you actually get also depends on the transport.

Cloud vs local Modbus¶

Most points are available over both the cloud API and local Modbus (WiNet-S), but coverage differs by family. See Local Modbus for setup.

Local Modbus is currently read-only; dispatch/control still goes through the cloud (#220).

Known model-specific caveats¶

• SH20T — MPPT not exposed via cloud. On some firmware the SH20T doesn't return MPPT voltage/current over the iSolarCloud API even with per-device sensors enabled, so those sensors won't appear (reported in #189). This is a data limitation of the model/firmware, not a bug in the integration.
• SH10RT‑20 — battery charge/discharge power. Separate Battery Charging Power and Battery Discharging Power sensors are requested automatically for hybrid inverters (no manual configuration; #31).
• SG-RS — local daily_yield. The daily-yield register read over Modbus can diverge from the cloud value on some SG-RS firmware; the integration derives daily yield from the trustworthy lifetime total instead (#223).

Missing a sensor?¶

If a value you expect isn't appearing:

1. Check the table above — it may be a known limitation of your model.
2. Download a diagnostics dump from the device page. The points_catalog section lists every point your hardware actually reports (point ID, name, value, unit) per device — copy the IDs you want into Extra measure points (see Adding extra measure points).
3. If a point is reported but not surfaced — or your model isn't recognised as the right family — please open an issue with the redacted diagnostics so the model map can be extended.