This page descirbes the Cloud Integrations support for SolarEdge.

💡 Note this documentation is for the SolarEdge v2 API. The SolarEdge v1 page documents the legacy integration.

The SolarEdge integration service identifier is s10k.c2c.i9n.solaredge.v2. The following service properties are supported:

The SolarEdge integration supports the following Cloud Datum Stream Service implementations:

The SolarEdge datum stream service identifier is s10k.c2c.ds.solaredge.v2. The following service properties are supported:

The following placeholders are supported on the placeholders service property:

The following Data Filters are supported:

The SolarEdge integration uses the following data value cloud-speicifc metadata keys (refer to the SolarEdge API documentation for more information on possible values):

The SolarEdge cloud data value model is represented in 4 levels:

1. Site ID
2. Device Type -- one of inv, met, bat for inverter, meter, battery
3. Component ID
4. Measurement (property)

Value references are formed as:

/{siteId}/{deviceType}/{componentId}/{measurementName}

For example:

/610000/inv/7E130000-01/Pdel

The SolarEdge API returns data for all devices within a site, and as such the Datum Stream Service can generate SolarNetwork datum streams for multiple devices at once, if desired. To do so, the valueReference for a Datum Stream Mapping Property can use a * wildcard for the 3nd-level identifier. This can be combined with the {siteId} placeholder. SolarNetework will then take the sourceId defined on the Datum Stream and append /TYPE/X to each device in the site, where TYPE is a device type identifier like inv or met and X is the component identifier.

If the upperCaseSourceId service property is set to true, then the device type identifiers will be changed to upper case, like INV or MET in the generated source IDs.

If the indexBasedSourceId service property is set to true, then the position of the component within its device type in the site inventory will be used in the generated source IDs instead of the component identifier. The positions start at 1, like /inv/1, /inv/2, and so on.

Imagine the Data Values method returned an inverter 11111111 and meter Production for site 12345 like this:

{
  "success": true,
  "data": [
    {
      "name": "Inverters",
      "identifiers": [
        "12345",
        "inv"
      ],
      "children": [
        {
          "name": "Inverter 1",
          "identifiers": [
            "12345",
            "inv",
            "11111111"
          ],
          "metadata": {
            "serial": "11111111",
            "manufacturer": "SolarEdge",
            "model": "SE7600A-USS20NHY2",
            "firmwareVersion": "DSP1: 1.210.1623, DSP2: 1.210.1623, CPU: 3.2724.0"
          }
        }
      ]
    },
    {
      "name": "Meters",
      "identifiers": [
        "12345",
        "met"
      ],
      "children": [
        {
          "name": "Production Meter",
          "identifiers": [
            "12345",
            "met",
            "Production"
          ],
          "metadata": {
            "serial": "22222222",
            "manufacturer": "SolarEdge",
            "model": "SE-RGMTR-1D-240C-A",
            "connectedTo": "Inverter 1",
            "connectedToSerial": "11111111",
            "firmwareVersion": "62"
          }
        }
      ]
    }
  ]
}

Assuming your Datum Stream was configured with a sourceId of S01, you could configure mapping properties like this:

Then SolarNetwork would generate 2 datum streams, both with watts and wattHours properties, according to this table:

You can also define an explicit mapping of components to source IDs with a sourceIdMap service property on a Datum Stream. This can be specified as a map or comma-delimited mapping list of component IDs to associated source ID values. For example in JSON, the sourceIdMap service property could be specified as an object like:

{"/12345/inv/11111111":"S1/INV/01", "/12345/met/Production":"S1/MET/01"}

or a string like:

"/12345/inv/11111111=S1/INV/01, /12345/met/Production=S1/MET/01"

A complete example of the Datum Stream could look like this:

{
  "enabled": true,
  "name": "SolarEdge Example",
  "serviceIdentifier": "s10k.c2c.ds.solaredge.v1",
  "integrationId": 1,
  "schedule": "900",
  "kind": "n",
  "objectId": "123",
  "sourceId": "unused",
  "serviceProperties": {
	"resolution": "QUARTER_OF_AN_HOUR",
	"siteId": 12345,
	"sourceIdMap": {
	  "/12345/inv/11111111": "S1/INV/01",
	  "/12345/met/Production": "S1/MET/01",
	}
  }
}

Here the generated datum streams would be S1/INV/01 and S1/MET/01 because of the sourceIdMap setting. The unused sourceId setting would not be used.

☝️ When sourceIdMap is configured, only the devices explicitly included will be generated into datum streams, and all other devices will be ignored.

This service supports the Cloud Datum Stream import service.

The following validation types are supported, and can also be disabled by including on the validationIgnore service property: