Integration (roadmap)

Sungrow monitoring integration

Architecture-ready Modbus/API ingest for Sungrow inverters and storage.

Quick answer

A Sungrow adapter is architecture-ready on NuraVolt’s ManufacturerAdapter framework — which already supports Modbus TCP, JSON API, SNMP, and SOAP — but is not yet shipped as a live, validated adapter. Live Sungrow ingest is delivered as part of an onboarding engagement against the target plant’s register map.

Supported protocols

  • Modbus TCP (planned)
  • iSolarCloud API (planned)
  • CSV export

Data points we ingest

  • Per-MPPT / per-string current and voltage (PV)
  • AC power, frequency, grid voltage (PV)
  • SoC, power, temperature (storage)
  • Device fault and alarm codes

Setup

NuraVolt’s base ManufacturerAdapter abstracts data format, field mapping, and unit conversion, so a Sungrow adapter is a configuration-and-validation task against the specific model’s register map rather than new framework code. We scope it during onboarding and validate against live plant data before relying on it.

Methodology & sources: nuravolt/bess/manufacturer_adapters/base.py

Frequently asked questions

See also

See this on your own plants

NuraVolt turns your SCADA and BMS data into early fault detection, degradation-aware BESS analytics, and audit-ready reporting. A fixed-scope audit shows you what we’d find on your portfolio.