Supported wind, fleet-management and specialist monitoring data sources.
Use this list for wind assets, cross-site fleets and specialist platforms that supply monitoring data through an account, API, gateway, or file route.
Compatibility is verified per project
A listed integration means that a supported data route exists. It does not guarantee every model, firmware version, measurement, alarm, history interval, region, or control function. Eniris confirms the precise scope before commissioning.
| Integration | Typical monitoring scope | What Eniris needs |
|---|---|---|
| Enercon | Wind farms, turbines, production, status, and events where available | Dedicated platform access, farm/turbine identifiers, turbine serial numbers, and source time zone. |
| EWT DirectWind | Wind-farm and turbine data | Dedicated platform access, farm and turbine identifiers, serial numbers, and requested measurements. |
| Vensys | Wind farms, turbines, telemetry, and alarms where available | Vensys API key and the turbine TID list to include. |
| Windup | Wind farms and turbine telemetry | Dedicated API account and an allow-list of turbine IDs. |
| SynaptiQ API | Wind or renewable portfolio telemetry | Dedicated account, plant/turbine scope, time zone, and requested signals. |
| SynaptiQ file push | Recurring telemetry files | Delivery credentials, root asset IDs, address and tag configuration, sampling/interpolation interval, time zone, and sample files. |
| GreenPowerMonitor | Renewable plants, elements, inverters, and measurements where available | Dedicated API account, platform URL, plant scope, and element/device identifiers. |
| Dexter | Forecasts and actual energy measurements | Dedicated API account, environment, requested forecast queries, actuals source, asset identifiers, units, and time zone. |
| Hualogy export | Portfolio telemetry delivered through a supported export | Export access, plant list, device mapping, time zone, sample files, and delivery interval. |
| EMI | Supported installation telemetry | API key, time zone, installation allow-list, and source identifiers. |
| EPIAS | Supported energy-platform data | API username/password or approved service account, installation scope, and requested measurements. |
| OKTE | Supported market or energy data | Required area or asset scope, time range, units, and commissioning contact. |
| OREE | Supported structured energy data | Representative export, site/source mapping, timestamp and unit definitions, and delivery schedule. |
| WebdynSun manual/file routes | PV logger and fleet data | Logger identity, export route, representative files, site/inverter mapping, time zone, and schedule. |
Provide the exact manufacturer and model, firmware version, source account or installation identifiers, required measurements and alarms, expected interval, time zone, and a recent source screenshot or export. Never place passwords, API secrets, private keys, or refresh tokens in a support ticket.