Every common controller protocol, built in

Protocols

Seventeen protocols are part of the platform and not a project per customer: Modbus TCP, Modbus RTU, BACnet/IP, Climatix, M-Bus, OPC UA, KNX/IP, HTTP/JSON, MQTT, eBUS, CAN, CANopen, the Solar API, SunSpec Modbus, EEBUS, Zigbee and Matter.

eBUS is not there out of nostalgia. The two wire bus is old and sits, for that very reason, in a great many installed heating appliances. Whoever does not speak it cannot reach those plants.

EEBUS under VDE-AR-E 2829-6 is implemented, ahead of the July 2027 deadline from which the German subsidy requires it. What hangs on that is under Staying eligible.

CAN and CANopen are the bus of boiler and burner controls, and they sit in inverters as well. Both are listed separately because reading a manufacturer’s raw CAN frames is different work from serving a CANopen object dictionary.

MQTT is the way in for devices that push their data rather than being polled. It stands beside the controller buses and replaces none of them.

The Solar API sits on HTTP/JSON and reads inverters. SunSpec Modbus stands next to it and answers the other half of the same question: a common register model for inverters and batteries that bring no API of their own. Generation then sits in the same time series as consumption, instead of in a second portal. What that gives you is under Photovoltaics.

Zigbee and Matter are the room side. They come in through the panels: room sensors, thermostats and actuators that sit next to the plant rather than on its controller.

M-Bus is not in that list by accident. Heat and electricity meters speak it, and without meters there is no metered capture. What that has to do with remaining eligible for German subsidies is under Staying eligible.

That the protocol work is built in rather than bought in is the reason a new generation of equipment does not need weeks of lead time.

Which controllers this reaches

This is not a reference list. It says which controller families are reachable over the built in protocols, not who is a customer. What a given series speaks differs from device to device: what counts is what the controller offers on its interface.

Manufacturer	Typically connected over
Siemens, including Climatix	Climatix, Modbus TCP and RTU, BACnet/IP
Carel	Modbus RTU and TCP, BACnet/IP
Saia Burgess Controls	Modbus TCP and RTU, BACnet/IP
Sigmatek	Modbus TCP, OPC UA, CANopen
Beckhoff	Modbus TCP, OPC UA, BACnet/IP, CANopen
WAGO	Modbus TCP and RTU, BACnet/IP, OPC UA, CANopen
TEM	Modbus
Phoenix Contact	Modbus TCP, OPC UA
Schneider Electric, including Eliwell	Modbus, BACnet/IP
Honeywell, including Centraline	BACnet/IP, Modbus
Johnson Controls	BACnet/IP, Modbus
Sauter	BACnet/IP, Modbus
Kieback & Peter	BACnet/IP, Modbus
Regin	Modbus, BACnet/IP
LOYTEC	BACnet/IP, KNX/IP, OPC UA
Dixell and Emerson	Modbus RTU

Beyond that, without naming individual manufacturers: installed heating appliances over eBUS, boiler and burner controls over CAN and CANopen, inverters over the Solar API, SunSpec and Modbus TCP, heat and electricity meters over M-Bus and Modbus.

Your controller is not listed? That is not a reason to stop, it is the normal starting point. Where a fitting protocol layer exists, we map to it. Where none exists, we build the driver, and that includes proprietary interfaces. This works because the protocol integration is ours and not bought in.

Discovery instead of typing

The technician starts the scan, the client finds the reachable devices and reads out their data points. What it finds is a list, and all that remains is to map it.

The alternative most people know today is a spreadsheet of register addresses that somebody transfers by hand. That is exactly where the errors come from that nobody can trace later.

Template applications

An application describes a device type: which data points it has, what they are called, what unit they carry, what the interface around them looks like. It is built once and then applied to every plant of that type.

That moves the effort from the individual plant to the device type. For a manufacturer shipping a few thousand plants a year, this is the lever that matters.

Clients

The edge clients run on Android and on Linux. Which hardware may connect is your decision: only approved hardware connects, against documented criteria.