Skip to content
Home Assistant TestFlight
Energy

Sungrow iSolarCloud

KRoperUK/sungrow-hass · vv6.6.0

HACSCloud polling

Home assistant integration for the Sungrow API

In Apple Home through HomeKit Bridge

What HomeKit Bridge makes of each kind of entity this integration creates, read from its source code. A device only gets the ones that apply to it.

EntityShows up asNote
binary_sensorSensor (motion, contact, leak, smoke…)
sensorSensor (temperature, humidity, air quality…)
selectMode picker (as switches)

What people report

Sungrow iSolarCloud integration with an optional local Modbus path via WiNet dongles. Local works well on SG-RS inverters; hybrid SH models are still being mapped.

  • Works1
  • Partly works1
DeviceIn Home AssistantIn Apple HomeWhat they saidSource
Sungrow SG3.6RS with WiNet-SWorks LocalLocal Modbus TCP validated on real hardware, discovered via mDNS
Saved copy
Discovery, it's zeroconf (mDNS), not DHCP Correction to earlier thinking: the WiNet-S MAC OUI is Espressif (its Wi-Fi chip), not Sungrow, so DHCP-by-OUI would false-match every ESP device on the network. Bad hook. But the WiNet-S advertises mDNS/zeroconf, which is clean and distinctive: - Service: `WiNet-WebServer`, `_http._tcp.local.`, port 80 - Hostname: `SUNGROW .local` - TXT records describe the whole rig: - `board=SUNGROW;1;WiNet-S; ;1;` - `inverter=1;9732; ;1;516;SG3.6RS;1;1;` ← type code + model (SG3.6RS) ### HA zeroconf discovery ```json "zeroconf": [{ "type": "_http._tcp.local.", …

Excerpt saved from GitHub on 2026-10-23.

Issue #159 · 2026-07
Sungrow SH10RS hybrid with SBH250 batteryPartly works LocalLive battery and grid power missing; local setup failed after upgrade to 5.6.0
Saved copy
Is your feature request related to a problem? Feature Request: Surface Live Battery and Grid Power for SH10RS / SBH Systems Hi Kieran, Firstly, thanks for the excellent work on the integration. I'm running: Home Assistant Container Sungrow iSolarCloud Integration v5.2.0 SH10RS Hybrid Inverter SBH250-V11 Battery WiNet-S2 Australia Gateway I'm currently building EV charging automation to replace Charge HQ and have run into a limitation with the available realtime entities. What I'm Missing For excess-solar EV charging, I need access to live power-flow measurements such as: Battery …

Excerpt saved from GitHub on 2026-10-23.

Issue #314 · 2026-07

Gathered from GitHub issues, pull requests, discussions and docs, and from r/homeassistant. These are individual reports, so check the linked thread and the date before you buy.

How it connects

Cloud polling

Goes through the maker’s cloud, asking it for updates every so often. Needs the internet and an account.

Found automatically over

  • Bonjour (zeroconf)

Details

Installs (analytics)726 (0.1%)
GitHub stars18
Latest versionv6.6.0 (2026-10-18)
Set up in the UIYes
Maintainers@KRoperUK
LicenseMIT

Devices listed in its README

  • Regions / gateways: Europe, International, China, Australia, and India. Pick the one matching the account you registered your developer application under.

Limitations from the README

  • Cloud-only. All data comes from the iSolarCloud cloud API, there is no local polling. If iSolarCloud is unreachable, or your account/plan loses API access, entities become unavailable.
  • API quota. The free developer plan allows ~2000 calls/hour; keep the polling interval sensible, especially with many sensors.
  • Dispatch needs compatible firmware and plan. External EMS / parameter setting requires an inverter and iSolarCloud plan that permit it. Where unsupported, dispatch entities may error on write.
  • Developer app approval. New iSolarCloud developer applications must be approved by Sungrow (with OAuth 2.0 enabled) before authorization works, this can take up to a week.

In ReReHome

Whatever HomeKit Bridge shares reaches Apple Home as normal HomeKit accessories behind your Home Assistant bridge, so ReReHome shows and controls them like any other.

Bridges get their own settings page listing the accessories behind them.