Connect a solar power plant

Choose the correct connector

Vega currently supports direct solar connections for SolarEdge and APsystems.

Before starting, select the correct workspace, identify the platform used by the plant, and obtain the appropriate credentials:

The installer, plant owner, or monitoring-platform administrator normally provides these values. If your manufacturer is not listed under Connect to…, contact Akkamind rather than selecting a different connector.

Treat API keys and secrets as credentials. Enter them only in the connection wizard.

Open the wizard

1. Confirm that the correct Vega account is active.
2. Open Inventory.
3. Select Connect to….
4. Choose SolarEdge or APsystems.

Both connectors use the same five wizard stages, but their credentials and component configuration differ.

Step 1: Enter credentials and scope

SolarEdge

1. Paste the monitoring key into API key.
2. Enter the SolarEdge Site IDs in Site IDs.
3. Put one Site ID on each line.
4. Select Next.

APsystems

1. Enter the APsystems App ID.
2. Enter the APsystems Secret.
3. Enter the System IDs in System IDs, one per line.
4. Select Next.

Do not enter a display name, inverter serial number, or ECU ID where the wizard asks for a Site ID or System ID.

Step 2: Test access and review detected systems

The Connection test validates the credentials and loads available systems.

1. Wait until testing and preparation finish.
2. Compare Detected sites with the systems you intended to connect.
3. Check each identifier, name, address, country, and connector details.
4. Review Verification errors.
5. If anything failed, select Back, correct the credentials or identifiers, and test again.
6. Continue after every required system is detected.

A detected system can still have incomplete address or equipment metadata. You can correct site details in the next stage.

Step 3: Link each system to a Vega site

For every detected solar system, apply the site and component model:

1. Review the detected name and address.
2. Correct the country or address if necessary.
3. Use geocoding or enter coordinates when the location is incomplete.
4. Choose the appropriate action:
   • Use suggested for a correct existing-site match.
   • Create new if Vega has no site for this facility.
   • Use new from wizard to attach another detected system to a site being created.
   • Choose other to select a different existing site.
   • Update existing meter if a matching component already exists without the connector.
5. Verify Selected site.
6. Repeat for all systems and select Next.

Avoid creating a duplicate site for a solar plant that belongs to an existing facility. Site-level comparisons work best when utility consumption and solar production are linked to the same site.

Step 4: Configure SolarEdge

For a SolarEdge system, review the PV configuration:

• Peak power (kWp) is the installed DC capacity.
• System loss (%) is the assumed total loss used in performance calculations.
• Tilt (deg) uses 0° for horizontal and 90° for vertical.
• Azimuth (deg) uses 0° north, 90° east, 180° south, and 270° west.

Use design or commissioning documents for these values. If the plant has multiple arrays with different orientations, configure the arrays separately when the detected structure supports them.

Review the history start setting. By default, SolarEdge synchronization begins from the installation date when available, otherwise from the earliest detected data date. Enable Custom start date only when you have a specific reason to limit or change the history.

Step 4: Configure APsystems

APsystems can expose a hierarchy containing a system, ECUs, inverters, panels, and batteries.

For each component level, choose:

• Exclude — do not create this component in Vega.
• Calculate — calculate its measurements from child components.
• Import — download measurements directly from that component.

Use Calculate for an aggregate when you want its total derived from imported children. Use Import when the device provides the authoritative series. Avoid importing and calculating overlapping totals without understanding the resulting hierarchy.

Then:

1. Review the component tree.
2. Rename components where a clearer operational name will help users.
3. Enter or verify peak power, tilt, and azimuth.
4. Use the component actions to apply an orientation to descendants or distribute peak power when appropriate.
5. Review detected batteries and exclude devices that should not appear.
6. Set System loss (%).
7. Review the history start date.

By default, APsystems uses a rolling three-month history window. Enable Custom start date if a different available history is needed.

Step 5: Review and finish

1. Check the totals for detected systems, selected existing sites, new sites, and components to update.
2. Review what will be created or extended under every site.
3. Confirm the selected APsystems import levels or SolarEdge PV settings.
4. Select Back to correct any mistake.
5. Select Finish when the summary is correct.
6. Wait for the wizard to complete.

Verify production data

Complete these checks and then work through the broader data-readiness guide:

1. Refresh Inventory.
2. Open the linked site and its Components tab.
3. Locate the SolarEdge or APsystems hierarchy.
4. Confirm names, identifiers, connector labels, and parent-child relationships.
5. Open Measurements and check recent production values.
6. Open PV Performance when available; Evaluate solar production and self-consumption explains how to continue the analysis.
7. Open PV Forecast when available and confirm that the current operational forecast loads. Use and interpret PV forecasts explains its prerequisites, horizon, and warnings.
8. Check site and component Health.
9. Review synchronization status and the imported history.
10. Compare one known day with the source monitoring platform.

If results are unexpectedly low or high, first check units, missing intervals, duplicated component totals, installed peak power, system loss, tilt, azimuth, and whether the selected series represents production or another quantity. Use Understand statistics and unusual patterns before treating an outlier as a performance issue.

Replace connector credentials

When a monitoring credential expires or is rotated, update it from an existing connected component:

1. Open the solar site in Inventory.
2. Open Components and select a connected SolarEdge or APsystems component.
3. Select Settings, then Edit credentials.
4. Review the message showing which components share the credentials.
5. For SolarEdge, enter the replacement API key. For APsystems, enter both the replacement App ID and Secret.
6. Select Verify and save.
7. Confirm the update, then inspect Sync, Health, and recent Measurements.

For APsystems, the credentials can be shared by many components across one or more systems. Vega tests access to all affected components and keeps the existing credentials if the replacement cannot access them. See the general credential-replacement workflow for more detail.