sungrow-isolarcloud

A maintained fork of the pysolarcloud library for interacting with Sungrow's iSolarCloud API.

Install from PyPI:

pip install sungrow-isolarcloud

This fork adds:

• Support for requesting additional / custom measure points without modifying the upstream point map (useful for battery charge/discharge power fields that vary by inverter model).
• A best-effort per-device realtime helper for devices such as EV chargers (Plants.async_get_device_realtime), which can optionally fall back to a UserAuth session (pass user_auth=) when the OpenAPI per-device endpoint is unavailable for the account/region — returning the same {uuid: {code: {...}}} shape so callers need no changes.
• A heartbeat helper for External EMS dispatch mode (Control.async_heartbeat / Control.heartbeat_loop).
• Convenience constants for dispatch command value sets (Control.CHARGE_DISCHARGE_COMMANDS, Control.FORCED_CHARGING).

The package supports the following functionality:

• OAuth2 authentication
• Getting a list plants
• Getting details of a plant
• Getting devices of a plant
• Getting "real-time" data of a plant (Data is updated every 5 minutes according to Sungrow's documentation)
• Getting historical data
• Getting and updating grid control settings

Quirks

The iSolarCloud API is quite new and not very mature. Some tips:

• The authorisation flow is based on OAuth2 but doesn't work exactly as you would expect
• The state parameter is not passed back after to the authorisation step. This makes it more tricky to resume the flow in a client application.
• User is asked to approve the authorisation if the flow is invoked again, e.g. in case the tokens have expired - unlike many OAuth2 implementations who will perform a "silent" authorisation if the user has already approved the access.
• The API documentation lists a lot of data points which do not seem to be returned from my inverter, it probably varies between models.
• There are different iSolarCloud servers for different regions, see the pysolarcloud.Server enum
• API endpoints accept a language code but respond with Chinese text when when English is requested

Usage

Register your app

1. Create an account in the iSolarCloud Developer Portal
2. Create an app in the developer portal
   • Answer "Yes" to authorize with OAuth2.0
   • Enter a Redirect URL for your app (this can be changed later)
3. Wait for approval by Sungrow
4. Find the needed configuration details in the developer portal. You will need:
   • Appkey
   • Secret Key
   • Application Id (This is shown as a query parameter within the Authorize URL in the developer portal)

Example

from pysolarcloud import Auth, Server
from pysolarcloud.plants import Plants

app_key = "your app key"
secret_key = "your secret key"
app_id = "your app id"
redirect_uri = "your redirect uri"

auth = Auth(Server.Europe, app_key, secret_key, app_id)
url = auth.auth_url(redirect_uri)

1. Redirect user to url
2. User selects plant(s) and grants authorisation
3. iSolarCloud will redirect the user to redirect_uri with query parameter code

await auth.async_authorize(code, redirect_uri)
plants_api = Plants(auth)
plant_list = await plants_api.async_get_plants()
if plant_list:
   print(f"{len(plant_list)} plants found:")
   for plant in plant_list:
         print(f"Plant ID: {plant["ps_id"]}, Name: {plant["ps_name"]}")
else:
   print("No plants found.")
   return

print("\nFetching detailed information for each plant...\n")
plant_ids = [str(plant["ps_id"]) for plant in plant_list]
plant_details = await plants_api.async_get_plant_details(plant_ids)
for plant in plant_details:
   print(f"Details for Plant ID {plant["ps_id"]}: {plant}")

print("\nFetching real-time data for each plant...\n")
real_time_data = await plants_api.async_get_realtime_data(plant_ids)
for plant_id, data in real_time_data.items():
   # Print only the data points where value is not None
   data_values = {k: v for k, v in data.items() if v and v.get("value") is not None}
   print(f"Real-time data for Plant ID {plant_id}: {data_values}")

The Auth class keeps the access between calls and refreshes it when needed. If you prefer to manage this state yourself, you can create your own subclass of AbstractAuth.

Grid Control

The Control class enables retrieving and updating grid control settings. Parameters and value sets are documented in the iSolarCloud Developer portal.

Example

from pysolarcloud.control import Control
from pysolarcloud.plants import DeviceType

devices = await plants_api.async_get_plant_devices(plant_id, device_types=[DeviceType.ENERGY_STORAGE_SYSTEM])
device_uuid = devices[0]["uuid"]
control_api = Control(auth)
# Fetch current config
current_settings = await control_api.async_read_parameters(device_uuid)
print(current_settings)
# Make an update using the canonical command values.
# energy_management_mode (10003) must leave Self-consumption for charge/discharge to actuate:
# 0 self-consumption, 2 compulsory/forced, 3 external energy dispatch, 4 VPP.
await control_api.async_update_parameters(
    device_uuid,
    {
        "energy_management_mode": Control.encode_parameter("energy_management_mode", "compulsory"),
        "charge_discharge_command": Control.CHARGE_DISCHARGE_COMMANDS["charge"],
        "charge_discharge_power": "2500",
    },
)

# When using External EMS / forced dispatch, send a heartbeat periodically.
# 10017 = external_ems_heartbeat, value is the heartbeat interval in seconds (1-1000).
# Appendix 10: send the heartbeat when switching EMS modes through the API.
await control_api.async_heartbeat(device_uuid, interval_seconds=60)

User-account login (unofficial, experimental)

In addition to the official OpenAPI OAuth flow (Auth), this fork provides UserAuth, which logs in with a normal iSolarCloud user account (email + password) via the reverse-engineered app/web API — no developer application required.

from pysolarcloud import Server, UserAuth

async with UserAuth(Server.Europe, "you@example.com", "password") as auth:
    plants = await auth.async_get_plants()
    print(plants)

⚠️ Unofficial and experimental. This is not Sungrow's documented OpenAPI. It may change or break without notice and its use may be subject to Sungrow's terms of service. The protocol was reimplemented clean-room from the MIT-licensed homebridge-platform-isolarcloud (see NOTICE). Credentials are only sent to iSolarCloud over TLS and are never logged.

User-account read helpers

UserAuth mirrors the iSolarCloud app's read API. All of the following are read-only; endpoint paths and parameter names were verified against the app, but where the app uses undocumented enum values (e.g. date_type, query_type, fault type/share codes) those are left as caller-supplied optional arguments and documented as unverified against a live device.

⚠️ Breaking change in 0.16.0 — async_get_device_realtime now takes a device ps_key (from async_get_devices) as its single positional argument instead of (ps_id, device_sn), and returns data keyed by device uuid ({uuid: {point_id: {"id", "value", "unit", "name"}}}) instead of a flat {point_id: {"value", "unit"}} map. It now posts to queryDeviceRealTimeDataByPsKeys; the previous /v1/devService/queryDevice path did not exist in the app. Migrate by passing the device ps_key and reading points under each uuid.

Contributions

Ideas or contributions are welcome. I am not affiliated with Sungrow, I'm just another user of the API. My main use case will be a HomeAssistant integration based on this package.

See CONTRIBUTING.md for the development setup, the checks CI runs, and the rules that main enforces — notably that commits must be signed and that pull requests need the branch up to date with main.

Enjoy!