Supported sources for metering, sensors, gateways, PLCs and building-management data.
Use this list for metering and operational data supplied by a meter platform, gateway, PLC, building-management system, API, or structured export.
The meter can reach SmartgridX through a controller, a supported platform or another documented data 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 |
|---|---|---|
| Fluvius API | Electricity and gas metering for authorized Flemish connection points | Customer authorization, B2B or B2C flow, reference number, EAN/GSRN context, and the connection points to include. |
| Fluvius NPS files | Recurring Fluvius meter files | Contract allow-list, supported file delivery route, time zone, and confirmation of EAN/GSRN and serial-number mapping. |
| Fudura | Utility-meter data available through the Fudura API | API key, EAN or meter scope, customer authorization, and time zone. |
| Innax | Metering and building-energy data | Client ID, client secret, refresh token or approved account connection, and the source IDs to include. |
| Opinum | Metering and energy-management data | Client ID and secret, dedicated account credentials, source IDs, and requested measurements. |
| Smappee API | Electricity, appliance, and site measurements where available | Client ID, client secret, dedicated account, installation allow-list, and service-location identifiers. |
| Smappee MQTT | Measurements published by a supported Smappee setup | Topic structure, payload sample, device identifiers, units, and publishing interval. MQTT credentials must be requested through the distributor. |
| Eniscope | Building and circuit-level energy measurements | Dedicated account, installation allow-list, and device or channel mapping. |
| Youless | Local electricity and gas readings from supported Youless devices | Exact model, local IP address, device access, meter mode, and site-network reachability. |
| Elgris / EmonCMS-compatible feed | Power-meter and energy-feed data | API key, feed identifiers, device/site mapping, units, and time zone. |
| E-alyzer | Meter data associated with EAN connection points | EAN identifiers, customer authorization, requested period, and site mapping. |
| Envitron | Metering platform data | Dedicated platform account, meter ID, approved API access, and site/time-zone mapping. |
| Efento | Environmental and temperature-sensor data | API key, sensor identifiers, installation mapping, units, and required interval. |
| Meterbeheer | Metering data from the Meterbeheer platform | API key, meter identifiers, installation mapping, and requested measurements. |
| EMB 2020 | Supported meter and building-energy data | Platform user or approved access, meter list, site mapping, and time zone. |
| Cast4All | Meter and telemetry data exposed by a Cast4All deployment | API base URL, client credentials, and an installation allow-list. |
| CADIS | Structured meter CSV data | Representative CADIS file, source folder/delivery route, time zone, device names, OBIS mapping, units, and interval. |
| CME 3100 | Supported recurring meter files | Representative file, delivery folders, time zone, meter serial numbers, and parameter/unit mapping. |
| CloudGate | Gateway CSV or FTP data | Gateway identity, supported file delivery route, time column and format, time zone, device-ID column, fields, tags, and sample file. |
| Moxa | CSV data from supported Moxa gateways | Representative file, delivery route, device/column mapping, units, timestamp definition, and error-file handling. |
| 2-Wire | Supported recurring meter CSV files | Representative file, delivery folders, time zone, device identifiers, units, and agreed schedule. |
| ProfiNrg | Supported meter CSV delivery | Representative file, delivery folders, time zone, device mapping, units, and schedule. |
| WAGO | Data exposed by a supported WAGO installation | Installation ID, endpoint or daily data URL, time zone, tag/register mapping, and network reachability. |
| Siemens S7-1200 | PLC tags and mapped energy signals | PLC name, reachable endpoint, tag mapping, time zone, network route, and an agreed sampling interval. |
| Siemens MQTT | PLC or gateway measurements published through MQTT | Broker route, topics, payload sample, device/tag mapping, units, timestamps, TLS setup, and publish interval. MQTT credentials must be requested through the distributor. |
| Ewon Talk2M | Data from supported Ewon gateways | Talk2M device ID and token, installation IDs, gateway access, and tag mapping. |
| Helexia | Supported project files containing inverter or meter data | Device name, source/delivery folders, inverter configuration, time zone, file sample, and units. |
| Qantum | Project metadata and supported platform data | Dedicated Qantum account, authorized Eniris integration access, installation mapping, and requested data scope. |
| Scipher | Supported platform data | Dedicated account, site/device identifiers, time zone, and requested measurements. |
| NEA | Data from a supported NEA endpoint | API base URL, site/source identifiers, expected fields, units, and time zone. |
| ElliTrack | Supported recurring tracker or asset files | Delivery route, time zone, asset identifiers, serial-number mapping, and representative files. |
| Generic CSV, Excel, JSON, XML, or TXT | Historical or recurring structured imports | Sample files, delivery method, timestamp column and format, time zone, decimal separator, device ID, tags, fields, units, retention rule, and update 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.