Integrations

What's live

Two inverter brands have full end-to-end integrations running on production sites today, plus one weather provider:

• SolarEdge — sites, equipment, telemetry and optimiser counts, through SolarEdge's monitoring API (V2) with an App API key your organisation creates at developer.solaredge.com. SolarEdge is polled regularly through your own SolarEdge App API key, but every call counts against your SolarEdge API plan's per-minute and monthly limits, which are shared across every site on the key — so a small plan can't refresh a large fleet as often as a bigger one. SolarEdge's own alerts are raised alongside SolarFleet's detections. Live power flow needs SolarEdge's Business Pro or Enterprise plan. V2 has no per-optimiser readings or panel layout on any plan — optimisers come through as a count per inverter. SolarEdge switches its old (V1) API and keys off on 3 November 2026, so connections made before then need a new App API key.
• Solis Cloud — sites, inverters, telemetry, alarms. Polled every 5 minutes. Authenticate with the API ID + secret from your Solis console.
• Open-Meteo — hourly irradiance, temperature, cloud cover. Used to build the weather-normalised expected generation curve and to gate the alert detections.

What's in beta

Sigenergy has an adapter shipped that's awaiting live-site verification. Hybrid inverter / per-MPPT / battery topology is built; we're pairing the adapter with a real mySigen account before flipping it to "live". If you've got Sigenergy hardware you'd like to be the first live customer on, get in touch.

What's on the roadmap

Every other major inverter brand is on the roadmap, demand-driven. Sungrow, Fronius, SMA, Enphase, Huawei, GoodWe, Growatt, FIMER. New adapters typically take around two weeks of work, and the first one is at cost for any customer who's making it possible.

If your portfolio runs a brand we don't have yet, tell us. We build to demand — a brand goes from "roadmap" to "live" when someone says they need it.

How to connect an integration

1. Settings → Integrations.
2. Click "Connect" next to the brand.
3. Paste the credentials — for SolarEdge, an App API key (Create Application → Monitoring API → Fleet Access → My Fleet at developer.solaredge.com) with its expiry date and your SolarEdge API plan; for Solis Cloud, the API ID + secret.
4. SolarFleet validates the credentials against the upstream API in real time. If they're wrong you'll know immediately.
5. Choose which sites to import from the ones the API exposes. For SolarEdge, SolarFleet also lists any of your sites the key can't see, and how the account that owns them can share them with yours (Associated Accounts).

Importing pulls equipment, recent telemetry (about two weeks by default), and any open alarms. Historical backfill runs in the background — typically three months of history is in place within an hour of connecting. For SolarEdge, how far back it goes depends on your SolarEdge API plan's monthly credits (up to 12 months).

Credential handling

Credentials are encrypted with AES-256-GCM at rest, keyed off a worker secret that isn't accessible from any app code path. We never log credentials to disk in cleartext. The decrypted value lives in memory only for the duration of each upstream API call.

If you rotate a credential upstream (you should, regularly), update it in Settings → Integrations and the next polling tick uses the new value. There's no downtime — we'll fall back to the previous credential for the in-flight tick and switch cleanly.

Manual sites

You can add sites for brands we don't yet integrate with. They won't auto-import telemetry, but everything else works the same — cases, maintenance visits, BS EN 62446-1 reports, client PDFs. When we ship the integration for that brand, you can flip the existing manual site to "connected" without losing any of its history.