Austria · Est. 2009

Loxone

Austria's smart home platform — Miniserver Gen 2 with Tree bus and Air wireless for rapid residential commissioning without ETS6.

Loxone (Kollerschlag, Upper Austria, founded 2009) created a proprietary smart building ecosystem built around the Miniserver Gen 2 controller and the Tree bus (RS-485 derivative, 24V DC, star topology, 5A per channel, 50m per branch). Unlike KNX's decentralised peer-to-peer architecture, all Loxone intelligence resides in the Miniserver — programming is done via Loxone Config, a graphical drag-and-drop environment (Windows, free) that requires no formal ETS6 training. Loxone holds approximately 25-30% of the new-build residential automation market in Austria and Germany, with a strong installer network and rapid commissioning time advantage over KNX (typical 3-bedroom apartment: Loxone commissioning 2-3 days vs KNX 4-6 days). PanelCraft designs and builds both Loxone and KNX panels, selecting the platform that best matches the project specification, installer ecosystem, and client requirements.

Loxone compact smart-home controller with tree extension for panel-based building automation

Role in our panels

How we use Loxone

The Miniserver Gen 2 controller (ARM Cortex-A8, 512MB RAM, Linux OS) manages up to 50 Tree extensions on 2 Tree channels, plus 12 digital inputs (24V DC), 12 digital outputs (relay and transistor), and 8 analog inputs (0-10V). All extensions connect via Tree bus: 4-core cable (24V DC power + RS-485 data on same cable, max 5A per channel). The Tree Dimmer Extension provides 4x 0-10V dimmer channel pairs (8 circuits total) for KNX-style 0-10V LED drivers or DALI ballasts. The Tree Relay Extension provides 12x relay contacts (16A per relay, volt-free). Air wireless: 868MHz ISM band, 128-bit AES encryption, battery devices (NFC Code Touch, Smart Socket, Motion Sensor Air) communicate without wire runs — ideal for retrofit and Grade II listed buildings. Loxone Config programming: blocks (Timer, Gate, AND, OR, Clock, Staircase, Presence, Weather) connected by wires on a virtual canvas — no programming language required. Simulation mode allows full commissioning test before site visit. Remote access: Loxone Cloud (hosted by Loxone) or local access without Cloud.

KNX panel wiring notes for Loxone projects: In mixed KNX+Loxone projects, the Loxone KNX Extension (article 100362EXT, 750-point capacity) connects via KNX TP to an existing KNX bus — Loxone acts as KNX master, reading and writing group addresses from Loxone Config. Panel wiring: Miniserver Gen 2 + required Tree extensions on DIN-rail, Tree cable (4-core, min 0.75mm2 for 5A, max 50m per branch before extension required) wired in star from Miniserver. Power: Miniserver Gen 2 requires 24V DC 3A supply (Loxone 24V PSU or Phoenix Contact QUINT). All 24V DC from same panel PSU as Tree extensions. DIN-rail space: Miniserver Gen 2 = 12 DIN modules (216mm). For KNX projects: PanelCraft recommends KNX for commercial, multi-brand, and BMS-connected projects; Loxone for residential new-build where the client prefers graphical app control and the installer is Loxone-certified.

Used in these project types

Austrian new-build villa: Miniserver Gen 2 + 6x Tree extensions controlling lighting (Tree Dimmer), blinds (Tree Relay), floor heating (Tree extension + Uponor actuators), and access (NFC Code Touch at gate and front door)
German apartment building: Loxone per-apartment (each flat has own Miniserver Gen 2), centrally monitored via Loxone Cloud, Air wireless sensors for motion and windows in retrofit apartments
UK boutique hotel: Miniserver Gen 2 per room block, Air Motion Sensor in each room for presence-controlled HVAC, NFC Code Touch for keyless room entry, Sonos integration via local UDP for in-room music
Mixed KNX/Loxone commercial office: Loxone KNX Extension importing 200 KNX group addresses from existing MDT and Gira KNX installation — Loxone provides app visualisation and logic while KNX field devices remain unchanged
Passive house renovation: Loxone Air wireless (no new cable runs), Air Motion Sensors for presence detection, Tree Relay Extension controlling existing radiator thermostatic actuators, Fronius solar inverter integration via Modbus TCP

Loxone products

Key components we install

100362Central Controller (ARM Cortex-A8, Tree Bus, KNX-ready)

Loxone Miniserver Gen 2

Central automation controller: ARM Cortex-A8, 512MB RAM, Linux OS, CODESYS-free graphical programming via Loxone Config. 2x Tree channels (up to 50 extensions total), 12x digital inputs (24V DC), 12x digital outputs (relay and transistor), 8x analog inputs (0-10V), 2x RJ45 Ethernet. DIN-rail mount, 12 DIN modules (216mm). Powered by 24V DC 3A (Loxone 24V PSU or compatible). All automation logic resides in Miniserver — no separate PLC required. Remote access via Loxone Cloud or local network. Monthly config backup to microSD. Supports Tree, Air, and KNX (via KNX Extension) in a single project.

200450Dimmer Extension (4x 0-10V Output Pairs, Tree Bus)

Tree Dimmer Extension

4x 0-10V dimmer channel pairs (8 circuits total), DIN-rail, powered directly from Tree bus (no separate 24V supply needed). Compatible with KNX-style 0-10V LED drivers and DALI ballasts without additional gateway. Each channel pair: one 0-10V output for dim level, one relay contact for on/off switching (DALI requires separate ballast wiring). Programmed in Loxone Config using Dimmer blocks with fade time, scenes, and presence-linked control. Up to 25 Tree Dimmer Extensions per Miniserver Gen 2 project (across 2 Tree channels). Used for lighting control in residential rooms, hotel corridors, and commercial office zones.

200463Relay Extension (12x Relay Output, Tree Bus)

Tree Relay Extension

12x relay output contacts, 16A per relay, volt-free contacts, DIN-rail, Tree bus powered. Used for blind and shutter motor control (Loxone Jalousie block), heating zone actuators (on/off type, e.g. Honeywell MT4 or Danfoss TWA), gate and garage door control, and general switching (pumps, fans, signal lights). Each relay pair can be configured in Loxone Config as a Jalousie block for up/down motor control with auto-stop. Up to 25 Tree Relay Extensions per Miniserver. For 16A loads (heating pumps, fan coil units), Loxone recommends wiring via external contactor triggered by Tree Relay contact.

100436Access Control Device (Air Wireless, NFC, PIN, IP55)

NFC Code Touch

NFC card and PIN code panel entry device. Air wireless (868MHz, 128-bit AES), battery life approximately 2 years (CR123A). IP55 outdoor rated — suitable for external gate pillars, main entrance, and plant room access. NFC RFID cards programmed directly in Loxone Config (no separate card management software). Supports up to 100 NFC cards per device. Also accepts 4-8 digit PIN codes (programmable per user in Config). Loxone Config integrates NFC Code Touch with access log, time-scheduled access (e.g. cleaner access Mon-Fri 08:00-12:00), and alarm system arm/disarm. Wall-mount bracket included; available in white and anthracite.

100362EXTKNX TP Interface for Miniserver Gen 2 (750 Group Addresses)

Loxone KNX Extension

Adds KNX TP (Twisted Pair) connection to Miniserver Gen 2 for hybrid Loxone+KNX installations. Imports up to 750 KNX group addresses from an ETS6 group address export file (ESF format) into Loxone Config — all imported group addresses appear as I/O points available to Loxone programming blocks. Loxone acts as KNX master: reads incoming KNX telegrams from KNX pushbuttons and sensors; writes to KNX group addresses to control KNX actuators, dimmer modules, and blind actuators. Used when an existing KNX installation is in place, when the project specifies designer KNX hardware (Gira, Basalte, Ekinex switches) alongside Loxone logic, or when a commercial project requires KNX field devices with Loxone visualisation and energy management.

Loxone FAQ

How does Loxone compare to KNX for a 4-bedroom residential project?

For a typical 4-bedroom house (200-300m2), Loxone delivers 15-25% lower hardware cost and significantly faster commissioning (2-3 days vs 4-6 days for KNX equivalent). Loxone Config graphical programming is accessible to electricians without ETS6 training — the installer ecosystem in Austria, Germany, and Switzerland is large and the training programme is free. However, KNX offers important advantages: 450+ certified manufacturers means true multi-brand hardware freedom (Gira, Basalte, Ekinex switches have no Loxone equivalent), and KNX is the required protocol for most commercial and hotel projects where BMS integration (BACnet, OPC UA) is specified. PanelCraft recommends Loxone for residential new-build where the client values ease of use, a modern app interface, and rapid setup; KNX for commercial, designer-specified, or multi-brand projects.

Can Loxone integrate with KNX devices in a hybrid project?

Yes — the Loxone KNX Extension (article 100362EXT) adds a KNX TP connection to the Miniserver Gen 2. You import an ETS6 group address export file (ESF format) into Loxone Config, which makes all KNX group addresses available as Loxone I/O points. Loxone then acts as a KNX master — it can read incoming KNX telegrams (from KNX pushbuttons, sensors) and write to KNX group addresses (to control KNX actuators, dimmer modules). The KNX Extension supports up to 750 group addresses. This approach is used when an existing KNX installation is in place and the client wants to add Loxone visualisation, or when the project specifies certain KNX hardware (e.g. Gira touchscreen) alongside Loxone control logic.

What are the main limitations of Loxone compared to KNX?

Three key limitations: (1) Single point of failure — all intelligence is in the Miniserver; if it fails, the building loses all automation (mitigated by Loxone's 2-hour replacement guarantee and monthly config backup to SD card). KNX is decentralised — individual actuators still function if the KNX power supply fails on other lines. (2) Proprietary ecosystem — Loxone hardware is only available from Loxone. No third-party Tree bus devices. This limits hardware competition and price pressure. KNX has 450+ certified manufacturers with a competitive market. (3) Programming dependency — the Config file lives on the Miniserver; if the installer's Config backup is lost and the Miniserver fails, reconstruction requires partial re-programming from scratch (though Loxone Config can read from Miniserver backup). ETS6 projects are portable between installers — any ETS6-trained engineer can modify the project.

Need a panel with Loxone components?

We select, procure, assemble and certify. Free initial consultation.

Request consultation →
Loading...
Back to top