Provider integration lifecycle
A provider integration brings plant and device data from an external monitoring platform into SolarSENS. A connection is not complete when an account is available: SolarSENS must also match the provider plant and devices, publish the reviewed configuration, and confirm that telemetry is arriving.
SolarSENS supports provider-specific workflows for Gelex, Huawei, Sungrow, and SolarEdge. The providers share the lifecycle below, but their account fields, discovery tools, device identities, and ingestion behavior differ. The providers available to you depend on your deployment.
How the lifecycle works
Section titled “How the lifecycle works”Connect account → Identify plant and devices → Assign external feed→ Review and publish → Normalize and ingest telemetry → Validate in monitoring| Stage | What happens | Expected result |
|---|---|---|
| 1. Connect an account | Record the provider credentials in Provider Accounts so SolarSENS can access the provider inventory. | The intended account is available for discovery and assignment. Credentials alone do not assign a provider plant or device to a SolarSENS plant. |
| 2. Identify the provider plant and devices | Match stable provider identities against the commissioning record. Huawei and Sungrow include dedicated plant explorers; other providers complete identity selection in Logger Setup. | Provider plant IDs, device IDs, and serial numbers are known before assignment. Display names are not used as the only match. |
| 3. Assign an external data feed | Make the provider feed the acquisition route for each planned device in Logger Setup. | Each selected device uses the intended provider account, plant, and device identity. A device uses either an AVA Logger connection or an external data feed, not both at the same time. |
| 4. Review and publish | Preview provider-specific additions, updates, removals, and device identities before publishing. | The downstream ingestion configuration is updated for the reviewed scope. A successful publication response does not by itself confirm that new telemetry has arrived. |
| 5. Normalize and ingest telemetry | Collect provider records and convert provider-specific measurements into the SolarSENS telemetry model. | Incoming records are associated with platform device identities. Measurements, update cadence, and historical coverage can vary by provider. |
| 6. Validate in monitoring | Check the intended plant and devices in monitoring after publication and ingestion. | Timestamps advance, expected measurements appear, and values are plausible for the operating state and time of day. |
What to check at each stage
Section titled “What to check at each stage”| Stage | What you verify |
|---|---|
| Account | The intended provider account is present and current |
| Identity | Provider plants and devices match the SolarSENS plan |
| Acquisition route | Each device uses the intended external feed |
| Publication | The preview contains only the expected changes |
| Ingestion | Provider records are associated with the right devices |
| Validation | Current, plausible telemetry is visible in monitoring |
When telemetry is missing
Section titled “When telemetry is missing”Start with the connection and identity mapping, then review the published preview, and finally check the latest telemetry. This sequence separates configuration issues from runtime issues.
Escalate persistent ingestion or provider-access failures through your support process.
To configure a connection, administrators can follow Set up a provider integration (sign-in required).