Loxone Config

In ETS each device is assigned a physical address and every function is linked via group addresses. Loxone Config works differently: all devices are inputs or outputs of the Miniserver. Connections are made graphically via drag-and-drop, not through address tables.

This makes the entry barrier lower for installers without bus experience, but has the drawback that the system is less open. All logic resides in the Miniserver; devices from other manufacturers are only integrable via extensions or third-party protocols.

A .loxone file is an XML document inside a ZIP container. It contains the complete system configuration: devices, function blocks, connections, visualisation objects and user rights. Backups are stored as .loxone files.

The format is proprietary, but the XML structure is readable and can be parsed by third-party applications such as venfree to extract project information or migrate between systems.

Create a project, define the Miniserver and extensions, name inputs (pushbuttons, sensors) and outputs (actuators, lights). Then place and connect function blocks. Final step: load the configuration onto the Miniserver via Ethernet and test.

Changes during operation are possible but usually require a brief Miniserver restart. Adjusting individual parameters without a full transfer is possible via the Loxone app or directly in the Miniserver web interface.