Loxone Modbus Integration: Wiring Meters and Controllers into the Miniserver
The Loxone Miniserver can act as a Modbus client, polling third-party energy meters, heat pumps and controllers over TCP or RTU and mapping their registers as virtual inputs in Config — all running locally, without depending on Loxone's cloud services for core automation.
How the integration works
Identify the Modbus source
Confirm whether the meter, heat pump or controller speaks Modbus TCP or RTU, and pull its register map from the vendor's documentation.
Wire it into the panel
TCP devices join the automation network segment via a switch; RTU devices run on RS-485 back to a gateway or Modbus extension module.
Configure the Modbus client in Config
In Loxone Config, add the Modbus client and map the relevant registers to virtual inputs, ready to use like any native input.
Build the logic
Connect the virtual inputs to Config's function blocks for alarms, trending, and automation — the same workflow used for Tree, Link and Air devices.
What Modbus integration covers — and where it stops
Logic runs on the Miniserver
Automation, including Modbus polling, executes locally on the Miniserver — it doesn't depend on Loxone's cloud for core functions.
Modbus client mode
The Miniserver polls third-party meters and controllers as a Modbus client (master); results appear as virtual inputs in Config.
Local-first automation
Core logic runs on the Miniserver itself, so Modbus-based readings keep working without a live cloud connection.
Modbus vs. Loxone Tree
Tree is Loxone's own bus — one 4-wire cable carries power and data to native devices in a tree topology. Modbus is how you bring in equipment outside that ecosystem.
Link stays separate
Loxone Link connects extension modules internally to the Miniserver — keep it logically apart from the external Modbus/OT segment when planning your network.
Know the ceiling
Loxone is a closed, manufacturer-centric platform, unlike open standards such as KNX. For data-historian or SCADA-scale OT needs, Modbus polling into the Miniserver is often paired with a dedicated PLC/SCADA layer rather than replacing it.
What our engineers help with
From register mapping to DIN-rail hardware, planned with a certified Loxone Partner.
- Reviewing the Modbus register map with your automation team
- Selecting gateways, extension modules and SPDs for the DIN rail
- Setting up the Modbus client and virtual inputs in Config
- Basic OT/IT network segmentation guidance
- Coordination with certified Loxone Partner installers
Frequently asked questions
Can a Loxone Miniserver read a third-party energy meter over Modbus?
Yes. The Miniserver can act as a Modbus client (master), polling compatible meters over TCP or RTU and mapping their registers to virtual inputs inside Loxone Config.
What's the difference between Modbus and Loxone Tree?
Tree is Loxone's proprietary bus: a single 4-wire cable delivers power and data to native devices in a tree topology. Modbus is the protocol used to integrate third-party meters, heat pumps or controllers that aren't part of that ecosystem.
Does Modbus-based automation on the Miniserver need cloud access?
No. Core automation logic, including Modbus polling and the resulting logic, runs locally on the Miniserver and does not depend on Loxone's cloud services for basic operation.
Do I need Loxone Config to set up a Modbus integration?
Yes. Config, Loxone's free PC configuration software, is where you add the Modbus client, map registers to virtual inputs, and wire them into the same function-block logic used for Tree, Link and Air inputs.
When should I add a PLC or SCADA layer instead of relying on Loxone's Modbus client alone?
Loxone is a closed, manufacturer-centric platform rather than an open multi-vendor standard like KNX. For heavier OT data-historian or SCADA-scale requirements, integrators typically pair the Miniserver's Modbus polling with a dedicated PLC/SCADA layer, planned together with a certified Loxone Partner.
Planning a Modbus integration?
Talk to our engineers about register mapping, gateway selection and the DIN-rail components for your Loxone project — engineer to engineer.