Architecture
The detail of how Quantum Domotics puts into practice its answer to the underlying problem with home automation today: hierarchical logic, software and hardware separated, and highly integrable devices.
Hierarchical logic
The system is made up of control devices arranged in a hierarchy, as in industrial control: the logic moves out of the field devices and into the controllers. In a home of ordinary size, a single central controller is usually enough. It is not the classic centralised architecture, where a controller failure brought everything to a halt.
- Three levels: operation (the application, to design, simulate and operate the home), control (the local controller, with the automation engine) and field (sensors, actuators and switches).
- Local fallback: switches are wired directly to their actuators; manual control always works, even without the controller.
- High-level logic: the automations live in the controller, independent of the hardware, and evolve without touching the physical installation.
- One engine: the same code runs in the simulation and, with Live, in the controller; what is designed and simulated is what gets installed.
- No cloud dependency: every home has its own controller; privacy, and it keeps working without an internet connection.
- Growth in levels: when a project needs it, several controllers with tiered responsibilities. Vision
Highly integrable devices
Interface and internal logic
A highly integrable field device needs a sufficient communication interface. And, as for its internal logic, it sits at one of two extremes:
- Complex devices with a high level of cooperation with the system's external control.
- Simple devices that do not interfere at all with the system's control.
The first option is the most efficient, because it shares responsibilities between the device and the controller, but also the hardest to achieve. Quantum Domotics analyses every level of device complexity to optimise its integration into the system.
In a complex device, what is essential is knowing what it does: its internal logic must be well documented so that the controller can synchronise with it. Being able to configure it as well helps, but is not essential. In a simple device, that knowledge hardly matters.
Internal logic is welcome when it cooperates: in KNX, the switch that acts directly on its actuator replicates the physical fallback of hierarchical logic. At the other extreme, a lamp with built-in light and presence sensors but no interface decides on its own when to switch on, and cannot be integrated.
Levels of integration
- Native devices: Quantum Domotics is formalising a catalogue, Quantum Domotics Open Infrastructure, that specifies, by type, their behaviour as well as their communication: what an LED driver does, what a blind controller does… With common, known behaviour, the controller governs them completely and with fewer distinct drivers: this is the highest control efficiency.
- Devices from other systems (KNX, DALI, Zigbee…): they are integrated through connectors and drivers, and keep at least the control efficiency they have in their original system. If a device becomes popular, it is integrated; and, where it makes sense, an equivalent native device that is simpler to integrate is specified.
- Equipment that only accepts its remote control, like many televisions: it is integrated through infrared or radio-frequency gateways, although usually without confirmation of its state.
- Not integrable: closed systems whose devices can only be reached through their own controller; the system would be subordinate to whatever that controller decided, which is unacceptable for Quantum Domotics.
Home automation built on industrial technology
Quantum Domotics brings the principles of industrial control to the home, with industrial controllers and open protocols.
- Controller: an industrial single-board computer (SBC) with embedded Linux, a reference model defined and documented by Quantum Domotics, which clients buy wherever they choose.
- Field devices widely used in industry, from any manufacturer.
- Open protocols: MQTT today, over Ethernet or Wi-Fi; industrial buses such as Modbus TCP or EtherCAT for the most demanding projects.
- Performance to match the project: the same software runs on a more powerful controller or a faster bus when the project calls for it.
Quantum Domotics Layer Model™
Two decoupled layers, inspired by the OSI model: the application layer, the software platform developed by Quantum Domotics, and the physical layer, the hardware, with a catalogue of native devices that is openly specified as Quantum Domotics Open Infrastructure™.
In the diagram, each layer is a column and each infrastructure a row: at the top, operation (what people use); at the bottom, control (what runs the home).
Application layer (software)
- Interface (Quantum Domotics Platform™): Designer and Simulator to design and simulate; Live to run the home. Built with Godot and C#.
- AI assistant: writes automations from plain language, with the user's own AI provider or a local model.
- Universal controller: the controller software, with Quantum Domotics Engine™, the automation engine: a C# (.NET) library, independent of the interface, with its own suite of automated tests. The same code runs in the simulation and, with Live, on the controller. Its drivers translate each physical device into logical devices (switch, dim, position…), so that the rules don't depend on the hardware underneath.
- Learning engine (Quantum Domotics Intelligence™): learns from how the home is used. Vision
- Inference engine (Quantum Domotics Intelligence™): applies what has been learnt on the controller, without the data leaving the home. Vision
Physical layer (interchangeable hardware)
- PC, tablet and mobile phone: where the interface (the application, for Windows and Linux) and the learning engine run.
- SBC: a reference industrial single-board computer with embedded Linux, which runs the universal controller.
- NPU (neural processing unit): an AI accelerator in the controller, for the inference engine. Vision
- Field devices: sensors, actuators and control equipment.
Topology of an installation
The controller runs the engine in the home; the application configures and operates it, locally or remotely. Devices communicate with the controller over MQTT, on Ethernet or Wi-Fi.
Elements of the diagram
- Controller (Engine): runs the automation engine in the home.
- Designer, Simulator and Terminal (Platform): the application. Designer and Simulator, on the computer, to design and simulate; Terminal, on a phone, a tablet or a computer, to monitor and control the home. Terminal talks to the controller over MQTT on IP, encrypted and only once paired.
- Switches: the Ethernet network that links the controller with the interfaces and the devices.
- Interfaces: modules that connect the devices to the network. The MQTT interfaces (for lights, for blinds) talk MQTT with the controller; the signal coupler gathers inputs and outputs onto an industrial bus.
- Drivers: power stages, such as the LED driver, that feed the load according to the command they receive.
- Devices: IP camera and smart TV (over TCP/IP), weather station, window contact, presence sensor, lights and roller blind.
- Control signals (green): commands and readings. Power signals (yellow): the energy that reaches the load.
- Industrial bus (*): Ethernet-based, such as Modbus TCP or EtherCAT.
- AI server (Quantum Domotics Intelligence): learning, outside the controller. Vision
- Licence server: issues and renews the application licences.
- Third-party services: external data, such as the weather or the news.
Quantum Domotics Open Infrastructure
The open definition of the physical layer: the catalogue of native devices, with their behaviour specified by type, and the communications it covers, from what already works to what is coming. It is Quantum Domotics' answer to a standard for communication that is not one for integration.
- Local IP network with MQTT Over Ethernet or Wi-Fi: quick to install and run locally. In the application: lighting, blinds, sockets (measuring what the appliances plugged into them draw), extractor fans and air conditioning; presence, light, temperature, humidity and contact sensors.
- Standards integration KNX first, and with it DALI lighting through KNX-DALI gateways; Zigbee, through MQTT; then direct DALI and others. With connectors that translate their devices into the engine's logical devices.
- Dedicated equipment IP devices (televisions, speakers, cameras) and climate and alarm control panels.
- Commercial and industrial Industrial fieldbuses (Modbus TCP, EtherCAT) for the most demanding projects.
- Domestic robotics Orchestration of autonomous maintenance robots.
Technical documentation
If you need more detail on the architecture to assess a project, just ask and we will send it to you.