---
title: "Data Hub: Connectors"
url: "https://ensights.productfruits.help/en/article/data-hub-connectors"
language: "en"
last_updated: "2026-08-25T13:17:42.254Z"
---

# Data Hub: Connectors

The credentialed connections that pull production data out of monitoring vendors and into enSights.

## What this page is for

A connector is a credentialed connection to a monitoring vendor's cloud. Once configured, enSights signs in to that vendor on a schedule and pulls in the readings for the assets behind it. Everything you see in Monitoring & Control arrived through one of these.

This is the most consequential page in Data Hub: if a connector stops working, a site's data stops arriving, and every figure downstream goes quiet.

![The Connectors list: fifteen connectors with their ID, vendor logo, asset count, created and updated dates, sync and fetch columns and Active or Inactive status, with a help strip and add button above.](https://cdn-assets.productfruits.com/9ec2f919-e787-41d4-9419-e5c5ea94f46b)

## The list

| Column | Meaning |
| --- | --- |
| ID | The connector's internal identifier. Quote it when raising support. |
| Vendor | The monitoring platform, shown as its logo. Some rows also note the credential type used, for example Account Key. |
| #assets | How many assets this connector currently feeds. A connector showing 0 is either newly created or no longer mapped to anything. |
| Created At | When it was set up. |
| Updated At | When it was last changed. A date far in the past on an Active connector is normal; the timestamp tracks configuration, not the last data fetch. |
| Sync Inventory | The last inventory sync. |
| Fetch History | The last historical fetch. |
| Status | Active or Inactive. Inactive connectors are kept but no longer polled. |

Above the table: a search box, the connector count, and the **+** button. A help strip at the top offers **Contact us** and **Check out our guide**.

Accounts accumulate inactive connectors over the years — old vendors, migrated sites, abandoned trials. That is normal. What matters is that every connector marked Active has assets behind it and is actually returning data.

## Row actions

The three-dot menu on each row:

-   **View** — inspect the connector without editing it.
-   **Edit** — change credentials or polling configuration.
-   **Sync Systems** — re-read the asset list from the vendor. Run this after adding a site at the vendor end, so enSights picks it up.
-   **Fetch History** — pull historical data. Use it to backfill a gap, or after a site has been offline.
-   **Deactivate** — stop polling but keep the configuration. The reversible option.
-   **Delete** — remove it permanently.

## Adding a connector

The **+** button opens **Add Datapoint**, a grid of vendor tiles with a filter box above it. The supported list is long — SolarEdge, SMA, Enphase, Fronius, Sungrow, Growatt, Huawei NetEco, GoodWe, FusionSolar, Solis, SolaX, Hoymiles, Fimer, CPS, Locus Energy, AlsoEnergy, GreenPowerMonitor, Solar-Log, Solarman, Tigo, Tesla, Satec, Itron, eGauge, Nexalis, Contel, Kaco, Generac, Yaskawa Solectria, APsystems, Yotta, Smappee, N3uron, solarSCADA, Deye Cloud, Unity and more.

![The Add Datapoint vendor grid, showing tiles for the supported monitoring vendors with a filter box above them.](https://cdn-assets.productfruits.com/c85f120d-dc9c-4434-984a-c486ceb2e425)

Choosing a tile shows the credential form for that vendor. The fields differ — some want a username, password and server, others an account key or API token — but the structure is the same.

![A vendor credential form: an Enable Monthly Backfill toggle, required User Name, Password and Server fields, and Hourly, Daily and Monthly Resolution selectors above the collapsed API Call Estimator.](https://cdn-assets.productfruits.com/81fc826a-2e1e-4586-9d74-8c75f4c062dc)

### Common fields

| Field | What it does |
| --- | --- |
| Enable Monthly Backfill | Fetches historical months when the connector is first set up, so a new site arrives with a past rather than starting from today. |
| Credentials | Whatever the vendor requires — typically User Name, Password and Server. Required fields are marked. |
| Hourly Resolution | How finely intraday data is fetched, for example 15 minutes. |
| Daily Resolution | How often daily figures are refreshed, for example every 4 hours. |
| Monthly Resolution | How often monthly figures are refreshed, for example every 6 hours. |

### The API Call Estimator

A collapsible panel that turns a configuration into a number before you commit to it. Enter **Number of Systems**, **Inverters per System**, **Meters per System**, **Sensors per System** and **Resolution (minutes)**, then press **Calculate**.

![The API Call Estimator expanded, with inputs for number of systems, inverters, meters and sensors per system and the polling resolution in minutes, and a Calculate button.](https://cdn-assets.productfruits.com/c36cfb13-9ad0-4364-b717-e649329ed50d)

This matters because vendor APIs are rate-limited and most vendor contracts cap monthly calls. Finer resolution multiplies against every inverter, meter and sensor on every site — so the difference between 15-minute and 5-minute polling across a large fleet is not a small one. Estimate first, then choose the coarsest resolution that still answers the questions you actually ask.

### How to add one

1.  Go to **Data Hub → Connectors** and press the **+** button.
2.  Filter for your vendor and click its tile.
3.  Enter the credentials the vendor issued you. These are the vendor's own portal credentials, not your enSights login.
4.  Set the three resolutions. Open the **API Call Estimator** and check the implied volume against your vendor limit.
5.  Turn on **Enable Monthly Backfill** if you want history as well as live data.
6.  Press **Save**.
7.  Run **Sync Systems** from the row menu to pull in the asset list, then check the **#assets** column.

## When data stops arriving

1.  Find the connector for that site and check its **Status** is Active.
2.  Check **#assets** is not 0 — a site renamed or moved at the vendor end can fall out of the mapping. **Sync Systems** fixes that.
3.  Look at **Settings → Activity → Processes**, filtered to failures, for the import error and its message.
4.  The most common cause is a credential that has expired or been changed at the vendor. **Edit** the connector and re-enter it.
5.  Once it is working, use **Fetch History** to backfill the gap.

## Notes

-   **Connectors store vendor credentials.** Anyone who can open this page can change them. The permission is **Datapoints** in Roles & Permissions.
-   **Deactivate rather than delete** unless you are certain. Deleting loses the configuration and the mapping to assets.
-   **A password change at the vendor breaks the connector silently.** Data simply stops. This is worth telling whoever manages vendor accounts.
-   Backfill is heavy on API calls. Enable it deliberately, not by habit.
-   The URL for this page is `/portal/datapoints` — connectors are called datapoints internally, which is also the name of the permission.