eco2lot feature · What would you like to connect?

Interfaces

Meters, machines, buildings, sensors, PV systems and software — eco2lot connects them via open industrial, IoT and software interfaces. This page shows which route fits your device: directly, via eco2node or via a manufacturer portal.

What are interfaces in eco2lot?

Interfaces are the connections through which data enters eco2lot and — where desired — leaves it again. On the plant side these are open industrial and IoT protocols such as MQTT, OPC UA, Modbus TCP and RTU, M-Bus, LoRaWAN and NB-IoT as well as access routes for smart meters. On the IT side they are the REST API and webhooks — plus MCP (Model Context Protocol), through which AI assistants evaluate and process values from eco2lot. Which interface fits depends on the device, the manufacturer and the existing infrastructure. That is why this page starts with the question of what you would like to connect — and then shows interface, solution and route to eco2lot.

How it works

The interface finder in one picture

The interface finder: six device types, their interfaces, the route to eco2lot and the benefit You choose what you would like to connect — the graphic shows the typical route of the data into eco2lot. Four steps: what would you like to connect, typical interface, route to eco2lot, arrival. Six lanes: meters for electricity, heat, water and gas speak Modbus, M-Bus or LoRaWAN and arrive directly or via a hardware gateway. Machines and PLCs speak OPC UA or Modbus TCP and arrive via eco2node or a hardware gateway. Building technology speaks Modbus, M-Bus or OPC UA and arrives via a gateway on site. Sensors speak LoRaWAN, NB-IoT or MQTT and arrive via radio network or gateway. PV, storage and charging points speak Modbus, OCPP or deliver via a manufacturer portal. Software such as ERP, MES, BI and data platforms uses REST API, webhooks or MQTT as software integration. All lanes end in eco2lot, the digital control center with one data foundation for everything. Step five, what you do with it afterwards: analyze, visualize, alert, report, get more from the data with the AI assistant via MCP, control processes within safety limits. You choose what you would like to connect — we show the typical route of the data into eco2lot. Different systems. One goal. Your data in eco2lot. 1 What would you like to connect? Your system or your plant 2 Typical interface How data is provided 3 Route to eco2lot How the data reaches us 4 Arrival One platform Meters Electricity · heat · water · gas Modbus M-Bus LoRaWAN Directly or via hardware gateway Machine · PLC Controller · plant · drive OPC UA Modbus TCP eco2node or hardware gateway Buildings · HVAC Heat pump · ventilation · BMS Modbus M-Bus OPC UA Gateway on site Sensor Climate · fill level · pulses LoRaWAN NB-IoT MQTT Radio network or gateway PV · storage · charging Inverter · charging point Modbus OCPP Portal Directly or manufacturer portal Software ERP · MES · BI · data platform REST API Webhooks MQTT Software integration eco2lot digital control center one data foundation for everything Connect once. Use together. Extend anytime. 5 What you do with it afterwards The same data — many possibilities. Analyze Recognize relationships Visualize Data clearly presented Alert Informed in time Report Reports automatically AI assistant · MCP More from your data Control Automate processes Every row shows a typical route: on the left the system, in the middle the usual interface, then the route into eco2lot. All routes end in the same data foundation — for analysis, visualization, alarms, reports, AI and control within safety limits. Hardware gateway = tested devices on site, e.g. InHand from eco2iot · eco2node = edge software on site · Portal = manufacturer connection · NB-IoT = mobile network sensors
Every row is a route: on the left the device — meter, machine with PLC, building technology, sensor, PV system or software —, then the typical interfaces, then the route to eco2lot: directly, via the edge software eco2node, via a hardware gateway (e.g. InHand) or via an integration. All routes end on the same data foundation; below it stands what you do with the data afterwards — up to evaluation by an AI assistant via MCP and to control within safety limits.
Level 1 · your starting point

What would you like to connect?

The first thought is rarely “I need Modbus TCP” but “I would like to connect my electricity meter”. That is why we start with your devices and systems. Depending on device, manufacturer and infrastructure, different connection options are available — the cards show the typical ones.

Meters & energy data

Bring consumption and energy data from existing or new metering into eco2lot.

  • Electricity meters and sub-meters
  • Heat, water and gas meters
  • Compressed air meters
  • Smart meters
Interfaces
Modbus TCP, Modbus RTU, M-Bus, LoRaWAN, MQTT, smart meter data access — depending on meter and manufacturer
Route to eco2lot
Network-capable meters directly; serial Modbus RTU and M-Bus meters via a hardware gateway (e.g. InHand) or eco2node; radio meters via a LoRaWAN network

Existing meters stay in use — you add new metering only where transparency is missing.

Machines & production plants

Connect existing machines and controllers with eco2lot — the existing plant structure stays as it is.

  • PLC controllers and CNC machines
  • Production lines and production machines
  • Compressors, pumps, drives
  • Existing automation systems
Interfaces
OPC UA, Modbus TCP, Modbus RTU, MQTT — depending on controller and year of construction
Route to eco2lot
Via eco2node (edge software) or a hardware gateway such as InHand on site: reads the PLC via OPC UA or Modbus, buffers on connection loss and transfers encrypted

Machine data and energy data land on the same data foundation — energy per unit becomes calculable.

Buildings & building services

Bring building technology and energy consumption together on one platform — the building management system on site stays in operation.

  • Heat pumps, heating and cooling systems
  • Ventilation systems and building automation
  • Indoor climate sensors
  • Sub-distributions and energy metering
Interfaces
Modbus TCP and RTU, OPC UA, M-Bus, MQTT, LoRaWAN — depending on the system; BACnet building management via gateway components
Route to eco2lot
Controllers and BMS directly or via gateway; meter bus via M-Bus master; metering points in existing buildings via LoRaWAN radio

All buildings of a portfolio to one standard — independent of the technology manufacturer.

Sensors & remote measuring points

Connect measuring points even where classic cabling would be laborious or uneconomical.

  • Temperature, humidity, indoor climate
  • Fill levels and meter pulses
  • Outdoor areas and remote buildings
  • Measuring points that are hard to wire
Interfaces
LoRaWAN for long-range radio sensors, NB-IoT for sensors via the mobile network, MQTT for IoT sensors in the network
Route to eco2lot
LoRaWAN sensors register at a gateway, NB-IoT sensors send directly via the mobile network; the values reach eco2lot via the network or via eco2node

A radio sensor is often mounted within an hour — pulling a cable takes days.

PV, storage, generation & charging

Bring generation, storage, consumption and charging together in one shared data world.

  • PV systems and inverters
  • Battery storage and CHP units
  • Charging infrastructure
  • Existing energy management systems
Interfaces
Modbus TCP and MQTT at the device; manufacturer portals such as the SMA Sunny Portal as integration; OCPP for charging points in the charging park controller
Route to eco2lot
Inverters and storage directly or via eco2node; portal data via the integration — without intervention at the plant

A manufacturer portal is a data source, Modbus a field interface — eco2lot connects both.

IT systems & software

Integrate eco2lot into existing IT and software landscapes — read and write data, pass it on automatically and have AI assistants evaluate it.

  • ERP, MES and BI systems
  • Own applications and data platforms
  • Automation tools
  • AI assistants
Technical access
REST API with OAuth2/JWT (read and write), webhooks on events, MQTT — and MCP as the exit: AI assistants read values from eco2lot and analyze them further
Ready-made integrations
Grafana, Power BI, Node-RED, n8n and OPC Router — as a connection you set up instead of program

Your data stays openly usable — in the tools that have proven themselves in your operation.

In detail

What is behind the interfaces

Matching solutions per connection

Level 3: once device and interface are settled, the question of the route remains. Four building blocks cover most cases.

  • eco2node — industrial edge operating system on site: reads machines and meters, buffers, transfers encrypted (edge = computing power directly at the plant)
  • Tested hardware (eco2iot) — hardware gateways such as InHand, meters, sensors and control cabinet setups, preconfigured for eco2lot
  • Manufacturer integrations — portals such as the SMA Sunny Portal deliver data without intervention at the plant
  • Software integrations — Grafana, Power BI, Node-RED, n8n, OPC Router via REST API and MQTT

Your benefitYou get software and connection from one source — planned according to your plant, not according to a catalog.

eco2node — the edge platform on site

eco2node is an edge platform (industrial edge operating system) that works between plant and eco2lot — as a standalone product or in combination.

  • Reads OPC UA and MQTT from the start; Modbus TCP and Modbus RTU are in development
  • Stores values locally on connection loss and delivers them later (store & forward)
  • Plants stay unreachable from the internet — the connection runs encrypted from inside to outside
  • Writes back within safety limits down to the individual data point
  • Also starts standalone with its own database — eco2lot can be added later, same nodes and data points

Your benefitOne route for machine and meter alike: machine → OPC UA → eco2node → MQTT → eco2lot.

In both directions — within safety limits

eco2lot receives readings and states. If device, interface and configuration support it, eco2lot also sends values back.

  • To the platform: readings, states, consumption, meter readings
  • Back to the device: setpoints, parameters, releases, operating modes
  • Reading is the default — writing only to explicitly released data points
  • Every write access with value range, role, write-and-readback and audit trail

Your benefitObserving turns into acting — safety-critical control stays in the plant PLC.

Good to know

  • Manufacturer-independent: Janitza, Siemens, Wago, Beckhoff, SMA and many more
  • Existing plants from decades remain usable — on different routes depending on device, manufacturer and infrastructure
  • Interface = technical access (Modbus, OPC UA, REST) · integration = ready-made connection to a product (Grafana, SMA portal)
  • Several protocols run simultaneously in one eco2lot environment
Level 2 · you already know your interface?

Supported interfaces at a glance

Eight cards, one pattern: what is typically connected with it, and in which direction do the data flow? Technical details are in the linked pages.

Communication in both directions between device and eco2lot On the left a device or plant, on the right eco2lot. A blue arrow to the right carries readings, states, consumption and meter readings to the platform — that is the default. A green arrow to the left carries setpoints, parameters, releases and operating modes back to the device — only if device, interface and configuration support it. Below four protection rules: only released data points, value range per point, role and permission, write-and-readback with audit trail. Safety-critical control stays in the plant PLC. Device · plant Meter · PLC · heat pump Readings · states · consumption · meter readings Default: reading — via every interface Setpoints · parameters · releases · operating modes Writing — within safety limits, if device and interface allow it eco2lot reads · checks · writes within limits 4 Rules for every write access Only released points Value range per point Role and permission Readback + audit trail Safety-critical control stays in the plant PLC — eco2lot writes only what is explicitly released.
Readings and states flow to the platform. Setpoints, parameters and releases go back — within safety limits and only where device and interface support it.

MQTT

Lightweight messaging protocol for IoT, edge and cloud communication — many data points at small bandwidth.

Sensors · edge · gatewaysRead · write MQTT in the IoT platform

OPC UA

Standardized communication with machines, PLCs and modern automation systems — with information model and security.

Machines · PLC · plantsRead · write OPC UA via eco2node

Modbus TCP / RTU

The classic for energy meters, inverters, controllers and technical plants — TCP over Ethernet, RTU serial via gateway or eco2node.

Meters · inverters · controllersRead · write Modbus meters and gateways

M-Bus

Proven meter bus for heat, water and energy meters — as a second master next to an existing building management system.

Heat · water · consumption metersRead M-Bus and BMS integration

LoRaWAN & NB-IoT

Radio-based connection for sensors and remote measuring points — LoRaWAN via your own gateway, NB-IoT via the mobile network; long range, battery life of years.

Temperature · humidity · meters · outdoor areasRead Radio sensors (eco2iot)

Smart meter

Connection of smart metering systems for supply and feed-in data — the basis for load profile, cost centers and reports.

Grid supply · feed-inRead Smart meters in eco2lot Energy

REST API & webhooks

Data exchange with software and enterprise systems — read and write with OAuth2/JWT, webhooks actively report events.

ERP · MES · BI · own appsRead · write REST API and integrations

MCP

Model Context Protocol: your AI assistant reads values and KPIs from eco2lot and works with them — analyses, comparisons, summaries. In line with roles and traceable.

AI assistants · analysesExit · read Get to know MCP and Maja
How do the data get to eco2lot?

Three routes to eco2lot — this is how simple it works

Whether individual devices, complete machines or existing software — the data reach eco2lot on three routes. There they are collected centrally, evaluated and provided for your tasks. Which route fits depends on the device and the existing infrastructure; in practice several usually come together.

Three routes to eco2lot: directly from devices, via edge or gateway, via software and cloud Route A, directly from devices: meters, inverters, controllers and sensors speak MQTT, OPC UA, Modbus TCP or LoRaWAN and NB-IoT directly with eco2lot. Route B, via edge or gateway: machines and plants, buildings and infrastructure as well as process and utility data are read on site by eco2node, the industrial edge operating system, or a hardware gateway such as InHand via OPC UA, Modbus, M-Bus or serial interfaces, buffered and transferred securely and encrypted via LAN, mobile network or VPN using MQTT. Route C, via software and cloud: manufacturer portals such as the SMA Sunny Portal, cloud services for weather and power prices as well as software and tools such as Grafana, n8n or Node-RED deliver via REST API, webhooks, MQTT or file import. All three routes end in eco2lot, the digital control center: store data points centrally, analyze and visualize, alarms and notifications, reports and automation, collaborate with teams. Your benefit: all data in one place, manufacturer-independent, secure and reliable, scalable from the meter to the plant, more transparency and lower costs. A Directly from devices Fast and simple — straight from the plant. B Via edge or gateway For complex plants — collect data on site, buffer, transfer securely. C Via software and cloud Connect existing systems and keep using the data. Meters Electricity · heat · water Inverters PV · battery Controllers PLC · buildings Sensors Temperature · radio MQTT OPC UA Modbus TCP LoRaWAN · NB-IoT Manufacturer portals SMA Sunny Portal Cloud services Weather · power prices Software & Tools Grafana · n8n REST API Webhooks MQTT File import Machines & plants PLC · controllers · meters Buildings & infrastructure Heating · ventilation · HVAC Process & utility data Energy · water · gas eco2node · hardware gateway Industrial edge OS · e.g. InHand reads · buffers · encrypts OPC UA Modbus M-Bus serial Interfaces on site LAN · mobile network · VPN MQTT secure & encrypted · from inside to outside eco2lot Your digital control center Data points store centrally Analyze & visualize Alarms & notifications Reports & automation With teams collaborate Your benefit: All data in one place Manufacturer-independent Secure and reliable Scalable up to the plant Transparency & efficiency
Route A: network-capable devices talk directly to eco2lot. Route B: eco2node (edge software) or a hardware gateway such as InHand reads machines, PLCs and meters on site and transfers via MQTT securely and encrypted. Route C: manufacturer portals, cloud services and software deliver via REST API, webhooks, MQTT or file import. All routes end in the digital control center — with all data in one place, manufacturer-independent, secure and scalable.

A · Direct

Device → interface → eco2lot. For network-capable devices with MQTT, OPC UA or Modbus TCP that can reach eco2lot — for example in an on-premises environment or via secured network access.

B · Via eco2node or hardware gateway

Machine / PLC / meter → OPC UA / Modbus / M-Bus → eco2node or hardware gateway (e.g. InHand) → MQTT → eco2lot. The standard route for machines, serial meters and plants that should stay unreachable from the internet. eco2node is the edge software from BS-Systeme, the hardware gateway a tested component from eco2iot — both buffer and encrypt from inside to outside.

C · Via software and cloud

Manufacturer portal or software → API / integration → eco2lot. For inverter data from the SMA Sunny Portal, electricity market and weather data as well as tools such as Grafana, Node-RED or n8n.

From connecting to benefiting

Connecting is the beginning

The interface brings the value into the platform. The added value emerges afterwards: the value becomes a data point with history and quality, smartcalc calculates consumption and KPIs from it, dashboards show them, alarms report deviations and reports summarize everything — up to control within safety limits.

  1. Device
  2. Interface
  3. eco2lot
  4. Data point
  5. smartcalc
  6. Dashboard
  7. Alarm
  8. Report

The same chain applies to every category — from the electricity meter to the ERP system.

Connecting is the beginning: from device to report Eight stages in three rows: device, interface, eco2lot, data point, smartcalc, dashboard, alarm, report. The interface brings the value into the platform; afterwards the benefit emerges through history, calculation, visualization, alarm and report. A green return arrow shows: from the evaluation, setpoints go back to the device within safety limits. The interface is the entry — the benefit emerges afterwards Device Meter · machine · sensor Interface MQTT · OPC UA · Modbus eco2lot Control center Data point History · quality smartcalc Consumption · KPI Dashboard see · understand Alarm Report deviation Report report · send ↑ back to the device within safety limits: setpoints, releases
Your outcome

Afterwards you can …

  • Existing meters, machines and sensors deliver data — without hardware replacement.

  • New measuring points take the matching route: cable, bus, radio or portal.

  • Own applications and AI assistants access your data in a controlled way — and values go back within safety limits.

Frequently asked questions

What you should know about interfaces

Which devices can eco2lot connect?

Meters of all media, machines and controllers, building technology, radio sensors, PV systems, storage and charging infrastructure as well as IT systems. What matters is the interface of the device: MQTT, OPC UA, Modbus TCP and RTU, M-Bus, LoRaWAN or a manufacturer portal. Depending on device, manufacturer and infrastructure the route leads directly, via eco2node or via an integration to eco2lot.

Can I keep using existing electricity meters?

Usually yes. Meters with Modbus TCP are read directly, serial Modbus RTU and M-Bus meters via a gateway or eco2node. Meters without an interface you retrofit with a pulse or radio module or record them as manually entered values at the device.

Which interfaces does eco2lot support?

On the plant side MQTT, OPC UA, Modbus TCP, Modbus RTU, M-Bus, LoRaWAN, NB-IoT and smart meter access; as manufacturer integration the SMA Sunny Portal; on the IT side REST API with OAuth2/JWT and webhooks. Plus MCP, through which AI assistants evaluate values from eco2lot. Several protocols run simultaneously in one environment.

Can eco2lot do Modbus TCP and Modbus RTU?

Yes. Modbus TCP is the variant over Ethernet — typical for energy meters, inverters and controllers — and is connected directly. Modbus RTU is the serial variant for existing devices; it reaches eco2lot via a gateway. In eco2node both Modbus variants are in development.

Can eco2lot do OPC UA?

Yes. OPC UA is the standard for machines, PLCs and modern automation systems. The usual route leads via eco2node on site, which reads OPC UA servers, buffers values and transfers them encrypted to eco2lot via MQTT. Write access is possible if device and configuration allow it — within safety limits.

Can I connect LoRaWAN sensors?

Yes. LoRaWAN suits temperature, humidity, fill levels and meter pulses at measuring points that are far away or hard to wire. The sensors register at a LoRaWAN gateway; the values arrive in eco2lot via the network. Where no own radio network is desired, NB-IoT sensors send directly via the mobile network. Tested sensors and gateways can be found under eco2iot.

How are machines connected?

Via the interface of the controller — mostly OPC UA, for older plants Modbus TCP or RTU. eco2node reads the values on site, buffers them and transfers them via MQTT. The existing plant structure stays as it is; the controller stays unreachable from the internet.

What is eco2node?

eco2node is an industrial edge operating system — a software platform that runs on a computer at the plant. It reads machines and meters locally (OPC UA and MQTT from the start, Modbus in development), buffers values on connection loss and transfers them encrypted to eco2lot. eco2node also works standalone with its own database; eco2lot can be added later.

Do I always need a gateway?

Only where the plant requires it. Network-capable devices with MQTT, OPC UA or Modbus TCP reach eco2lot directly, for example in an on-premises environment. A hardware gateway (e.g. InHand from the tested eco2iot hardware) or the edge software eco2node comes into play when devices are connected serially, should stay unreachable from the internet or values must be buffered on connection loss.

Can eco2lot also send values back to devices?

Yes — if device, interface and configuration support it. Then setpoints, parameters, releases or operating modes go back. Every write access is within safety limits: only to explicitly released data points, with value range, role, write-and-readback and audit trail. Safety-critical control stays in the plant PLC.

How do I connect an ERP or MES system?

Via the REST API with OAuth2/JWT — reading and writing — as well as via webhooks that actively report events such as alarms to your system. For automations between the systems n8n, Node-RED and the OPC Router are available as ready-made integrations.

Can I connect manufacturer portals?

Yes, as an integration. The SMA Sunny Portal delivers PV and inverter data directly into eco2lot, without intervention at the plant. Further data sources such as SMARD electricity market prices and weather forecasts are also connected as integrations.

What is the difference between an interface and an integration?

An interface is the technical access — a protocol such as OPC UA, Modbus, MQTT or REST that many devices and systems speak. An integration is a ready-made connection to a specific product or portal — Grafana, n8n, OPC Router or the SMA portal. Interfaces are on this page, integrations on the integrations page.

What is the MCP interface for?

MCP (Model Context Protocol) is the exit towards AI: an AI assistant — Maja in eco2lot or your own assistant — reads values, KPIs and relationships from eco2lot and works with them: analyses, comparisons, root cause search, summaries. MCP therefore serves the evaluation of existing data; devices and systems are connected via the other interfaces. Access is read-only, in line with roles and traceable.

How secure is the connection of the plants?

On site eco2node takes over the connection: plants stay unreachable from the internet, communication runs encrypted from inside to outside, data are buffered locally on connection loss. On the IT side OAuth2/JWT, roles and an audit trail protect every access — including that of AI assistants via MCP.

Which connection fits your plant?

Describe your starting point and your goal — we get back to you with a concrete recommendation of matching features and solutions, plus a price indication.

Configure your solution