Concept and Structure
Each function block has input terminals (left) and output terminals (right). A pushbutton input is connected to the Q input of a lighting block, whose output goes to a switching actuator output. What happens in between, switching, dimming, staircase lighting, is defined by the block type.
Function blocks are hierarchically organizable. Multiple blocks can be grouped inside a parent block, allowing recurring structures such as "standard room with lighting, blinds and temperature" to be created as templates.
Comparison with the KNX Concept
In KNX devices communicate peer-to-peer via group addresses: a pushbutton sends on GA 1/1/1, an actuator receives on GA 1/1/1. Logic resides in the device or is mapped through ETS bindings. Each device is autonomous.
In Loxone all logic resides centrally in the Miniserver. The pushbutton is just an input, the actuator just an output. The function block in the Miniserver decides what happens. This makes changes easier but creates a central dependency: if the Miniserver fails, nothing works.
Common Function Block Types
Lighting: pushbutton block (switching, dimming), presence detector block, twilight switch. Blinds: blind block with automatic shading, wind sensor stop, time schedule. Heating: room controller block with heating and cooling, time schedule, window contact.
For more complex logic there are analogue processing blocks (controllers, threshold switches), time blocks (weekly schedule, sun position calculation) and security blocks (alarm system, access control). All blocks are available directly in Loxone Config without additional licences.
Key Facts
- Logic resides centrally in the Miniserver, not in the field device
- Graphical linking: input left, output right
- No equivalent to KNX group address required
- Blocks nestable hierarchically (templates)
- Miniserver failure = failure of all logic