Operator · Fleet operator · EMSP

Inverter Hub Demo login

Solar-inverter clouds as a third data source — charging sessions reconstructed from the home PV system, even without a smart wallbox.

Wallbox-capable inverters are detected automatically — the driver simply enters their manufacturer API credentials in the driver portal. First charging sessions appear in the Fleet API within 60 minutes.

Enphasenative sessions
Huaweilive
Sungrowlive
EcoFlowlive
Froniuslive
+ 4 more
PATH 1 · ENPHASE
Native session import
/ev_charger/{serial}/sessions
PATH 2 · OTHER BRANDS
Snapshot worker + reconstructor
c4_pv_snapshots → pv_session_derive
FLEET API
op_charging_sessions
id_tag = pv-<brand>
reason = pv-native | pv-reconstructed
BETA · PHASE 1B
PV surplus charging
OCPP SetChargingProfile
wallbox follows solar surplus

Pipelet pulls charging data from three sources: OCPP wallboxes, OEM CarData (BMW · Tesla · Volvo · Audi · Ford), and since May 2026 also from the cloud APIs of solar-inverter manufacturers.

In practice: if a driver has an integrated wallbox attached to their own PV system (Enphase IQ EV Charger, Huawei Smart Charger, EcoFlow Power Charger, Sungrow iEnergyCharger), all that's needed is a sign-in at the manufacturer — a simple OAuth login for Enphase, an API key for the others. New since June 2026: native session import for the Enphase IQ EV Charger — Pipelet reads the charger's own pre-segmented charging history straight from the Enphase API (minute-accurate start/end times, energy from the charger meter, full history included on first import). For manufacturers without a session API, the reconstructor detects charges from the lifetime energy counter. Either way, a complete charging session lands in ``op_charging_sessions`` with markers ``id_tag = 'pv-<brand>'``, ``reason = 'pv-native'`` or ``'pv-reconstructed'`` and ``station_id = wallbox-serial``. Fleet managers and reimbursement workflows can recognise the PV source, reimburse it separately, or report it as the "solar share". Since June 2026, "PV Inverter" is selectable in the driver portal as the third data-source tile next to Wallbox and Digital Home Charging.

As of June 2026: nine manufacturers live (~68% market coverage) — Enphase, Solarwatt, SolarEdge, Fronius, SMA, Victron, Huawei FusionSolar, Sungrow iSolarCloud and EcoFlow PowerOcean. The reconstructor is brand-agnostic: a new manufacturer is three short files (adapter + worker branch + extractor). Solax and GoodWe (Phase 2) plus Kostal local (Phase 3) are on the roadmap.

What to expect

Native session import — Enphase IQ EV Charger

The charger reports its own charging history: minute-accurate sessions straight from the Enphase API, full history included on first import. Validated in production — 45 historical sessions of a pilot customer ingested in a single pass.

Third data-source tile in the driver portal

Drivers pick "PV Inverter" as a peer of Wallbox and Digital Home Charging. The choice auto-enables the PV module and leads straight to coupling — Enphase via OAuth sign-in, seven more manufacturers via API key.

9 manufacturers live, brand-agnostic reconstructor

Enphase, Solarwatt, SolarEdge, Fronius, SMA, Victron, Huawei FusionSolar, Sungrow iSolarCloud, EcoFlow PowerOcean. The reconstructor state machine is the same for every brand — adding a new manufacturer is about one workday.

Sessions with source markers in the Fleet API

Every PV session carries ``id_tag = pv-<brand>``, ``reason = pv-reconstructed``, ``station_id = wallbox-serial``. Partner portals tell wallbox vs. solar at a glance — and which brand.

Quota-aware polling (default 30 min)

Enphase free tier (1000 calls/month) and Huawei Northbound (login throttle) are respected. Configurable per brand — paid tiers can poll denser.

Idempotent UPSERT — replay-safe

Synthetic ``transaction_id`` is deterministic from ``(brand, system, start-edge-second)``. Reconstructor re-runs update the same session row instead of duplicating.

Driver self-service connect flow

Driver picks their manufacturer in the driver portal, enters OAuth code (Enphase) or service credentials (Huawei, Sungrow, EcoFlow). No operator-side intervention needed.

Fork-friendly for custom extensions

Three files per brand (adapter, worker branch, extractor). Fully documented at dev.pipelet.com — brand X takes one workday to add.

Common scenarios

1

Home charging without a smart wallbox

A driver charges at home on their own PV system with an Enphase IQ EVSE — no OCPP wallbox. Pipelet polls the EVSE every 30 min, recognises sessions and feeds them into the reimbursement workflow.

2

PV share in fleet reports

Fleet manager sees per driver: 320 kWh OCPP wallbox + 142 kWh PV wallbox + 89 kWh public charging. The solar share can be reimbursed, subsidised or reported separately.

3

Own-CPMS extension instead of aggregator lock-in

Instead of licensing an external aggregator, Pipelet talks to the manufacturer cloud directly. Aggregation value-add stays with the operator — no monthly per-driver fees to a third party.

4

One-day brand onboarding

A new manufacturer lands on the roadmap. Three files (adapter / worker branch / extractor) + i18n strings — done. State machine, UI badge, Fleet API surface come for free.

How Inverter Hub fits into the suite

Frequently asked questions

Is Pipelet available as source code?
Yes. Every module is available as a source-access package — complete with Docker Compose, documentation and an SLA support channel. You can audit, customize and self-host.
Which OCPP versions are supported?
Full OCPP 1.6 and 2.0.1 including Security Profiles, Smart Charging, and ISO 15118 Plug & Charge.
Can I use individual modules only?
Yes. Every module is standalone — you can deploy e.g. just the OCPP Broker as infrastructure and build your own CPMS on top.
What does onboarding look like?
We start with a 30-minute call to scope requirements. After that you get a concrete proposal with modules, timeline and price. Pilot typically live in 4–8 weeks.

Sounds like a fit?

Wallbox-capable inverters are detected automatically — the driver simply enters their manufacturer API credentials in the driver portal. First charging sessions appear in the Fleet API within 60 minutes.

You might also like

All products