Required information, setup and verification for SMA (Sunny Portal API).
Collect SMA installation and device telemetry using the existing Sunny Portal connector. Its ongoing collection is paced by the dedicated SMA scheduler.
A reliable API connection combines the correct authorization method, an explicitly limited installation scope and a verified first retrieval.
Connection type: API and platform connection.
The fields here describe the deployed account-based connector. SMA also offers OAuth-based developer APIs; those credentials are not interchangeable. SMA API access control. Keep the managed SMA schedule selected during onboarding.
Provide your company and contact person, the intended Insights account, the source identifiers and explicit permission for the requested scope. Include a recent source example for verification.
| Information / setting | What is needed | Supplied or configured by |
|---|---|---|
| Account username (USERNAME) | Account name with access to the requested data. | Customer / installer |
| Account password (PASSWORD) | Share the source-account password through the secure channel agreed with Eniris. | Customer / installer |
| Installation scope (INSTALLATION_ID_ALLOW_LIST) | Exact installation IDs or numbers to include. Agree explicitly before including every installation. Optional for this connector. | Customer / installer |
Check that the first collection completed, then open the intended Insights account and verify the relevant measurements or metadata. Compare source IDs, timestamps and units with the original source. Check the next scheduled execution as well. An active schedule or a healthy job alone does not prove that every requested measurement was received.
For ordinary onboarding meters, creation requests an immediate first run and keeps recurring collection active. Source publication times, upload intervals and provider limits still apply; immediate collection cannot manufacture missing source data.
Provide Eniris with the connection name, account/site scope, time of the attempt and the exact error. Check source availability and access permissions before retrying. Share a source screenshot or sample without passwords or tokens.
Onboarding classifies this API route as paid. Confirm the applicable provider access and commercial agreement before activation.