KNX standard
KNX is a field bus for building automation . On the building automation market, KNX is the successor to the field buses European Installation Bus ( EIB ), BatiBus and European Home Systems (EHS). Technically, KNX is a further development of the EIB through the addition of configuration mechanisms and transmission media that were originally developed for BatiBus and EHS. KNX is compatible with EIB .
history
As early as the mid-1980s, the first considerations for the application of bus technologies for electrical installation technology and building technology were initiated by various companies in parallel. The market launch of manufacturer-specific systems would have stood in the way of broad market penetration and offered the client a wide variety of proprietary "standards" and "systems". As a result, leading manufacturers of electrical installation technology joined forces in 1990 within the framework of the European Installation Bus Association (EIBA) with the aim of introducing a standard onto the market. This standard guaranteed the compatibility and interoperability of the various devices and systems from different manufacturers from many areas, both electrical installation technology and other areas such as air conditioning & ventilation or household appliances.
The founding members were Berker , Jung , Gira , Merten and Siemens . The European installation bus ( EIB ), also Instabus , in the current version as a KNX standard.
- It describes how sensors and actuators in a house can be connected to one another during an installation ,
- It defines how sensors and actuators must communicate with each other (the protocol ).
In 1996 the three European organizations BatiBUS Club international (BCI), European Installation Bus Association (EIBA) and European Home System Association (EHSA) started the convergence process to find a common standard for applications in building automation in the commercial and residential construction market. In 1999 nine leading European companies from the electrical engineering and building management industries signed the statutes of the new organization. The founding members of the KNX Association (temporarily referred to as Konnex Association) are: Albrecht Jung , Gira , Bosch Telecom , Delta Dore , Électricité de France , Electrolux , Hager Group , Merten , Siemens ( AD ET division ), Siemens Building Technologies , Landis & Staefa Division.
The KNX specification was published in the spring of 2002, adopted in the European standard EN 50090 in November 2003 and this standard was accepted as the international standard ISO / IEC 14543-3 in November 2006.
The “Instabus” or KNX standard emerged from the KNX Association , with the official name being only KNX. The KNX standard is an open standard that more than 400 companies worldwide have now joined. The standard can be viewed as open, as everyone can access the relevant documents after registration.
execution
After the first products according to this standard were offered on the market in 1991, there have been almost 4000 product groups with a multiple of different products from over 200 companies. These products cover the various trades and applications in the building while maintaining the interchangeability of the products so that they can work together in a system designed with the KNX. KNX is now the first open world standard for home and building automation . This has been regulated in Europe since 1994 in EN 50090. Standardization by ISO has taken place as the ISO / IEC 14543-3 standard.
The KNX controls the lighting and blinds or shading devices , the building heating as well as the locking and alarm systems . Remote monitoring and control of a building is also possible using the EIB (KNX) . Control takes place via the user himself or via a computer equipped with appropriate software . Originally focused on commercial buildings, KNX is also increasingly being used in residential buildings and, in particular, in single-family buildings . KNX cannot follow the trend towards the transmission of more information from cameras, sensors, voice and media. These can and must only be transmitted via parallel networks.
While the strength of KNX in decentralized cabling is economically useful in commercial buildings, centralized cabling has prevailed in small buildings (routing of all sensor and actuator lines to one or two central points). The trend towards the all-IP solution in building construction ( VoIP ) changed the market permanently. The increasing tendency to use logic (server, visualization) is causing a strong increase in PLCs in building construction. Some PLC manufacturers offer gateways to KNX to connect both worlds. KNX is currently mainly installed in new residential and functional buildings, but can be retrofitted when modernizing old buildings. KNX networks are already integrated into the building as standard in inexpensive prefabricated houses.
Nevertheless, pioneers in the development of EIB / KNX have now formulated doubts about the future viability of KNX in the specialist literature. In the long term, KNX will not be able to escape the general trend towards networking at the IP level; the options of the competing systems are too versatile. Higher data rates, especially from the media sector ( multiroom ), require different networking concepts anyway. An essential feature and advantage of the technology is and will continue to be the very safe and open bus architecture of KNX.
technical basics
In conventional electrical installations, the control functions are permanently connected to the power distribution and are carried out using switch-off switches or simple push-button switches. Subsequent circuit changes are therefore difficult to implement. Even higher-level control functions such as central switching of all lighting circuits in a building can only be implemented with great effort.
KNX separates the device control and the power supply from one another on two networks, the power network for power supply with AC voltage and the control network (= KNX bus) with 30 V DC voltage . Both networks can be laid independently or in parallel in the house. There is also a Powernet version in which the control signals are sent via a phase-coupled power network. Powernet-KNX is primarily intended for subsequent installation. In general, all devices can be connected to one another via the bus and thus exchange data. The function of the individual bus participants is determined by their programming, which can be changed and adapted at any time.
The devices from different manufacturers can be used with one another in one system without restriction, provided they have the corresponding certification by the KNX Association .
Simple schematic representation
Technology of the KNX network
A control device, called an "actuator", is installed between the consumer (e.g. electrical device, lamp, window opener) and the mains voltage . The actuator is connected to the KNX bus and receives data from it in the form of telegrams . These telegrams come either directly from a sensor (e.g. switch, brightness, temperature or CO 2 concentration sensor) or indirectly from a computer, which controls time-controlled circuits and other evaluations of sensor data depending on the programming and actuators accordingly drives.
If an actuator receives the command to supply voltage to the consumer, it connects the mains voltage to the device.
The bus line (designation for example JY (St) Y 2x2x0.8 EIB or YCYM 2x2x0.8 ) usually consists of two wire pairs (red-black and white-yellow), of which only red-black is used. The bus line must at least comply with IEC 189-2 or the equivalent national regulation. The cables with the aforementioned designations are recommended in this regard. However, other cables such as JH (St) H 2x2x0.8 or A-2Y (L) 2Y 2x2x0.8 are also permitted. The cable diameter is generally 0.8 mm and may not exceed 1 mm. The laying instructions must be observed for all cables, whereby the so-called certified EIB (KNX) cable (YCYM) may also be laid directly next to 230 V and 400 V AC voltage cables.
The KNX system is supplied by a voltage supply via a choke with 30 V DC voltage. This voltage supplies the bus couplers, via which each KNX device communicates with the other networked KNX devices. The CSMA / CA principle (for radio transmissions) and the CSMA / CR principle (for wired transmissions) prevent telegram losses in the event of bus collisions. The KNX bus communicates at a transmission rate of 9.6 kbit / s, which is sufficient for several 10,000 devices if programmed correctly. Due to the spread of Ethernet, IP-KNX couplers were quickly developed, which allow higher-level lines (area lines) to communicate via significantly faster Ethernet connections and thus the bus can use the higher transmission speeds . As a result, the previously maximum size of 15 area lines with 15 lines and up to 255 bus users (actuators, sensors) has been expanded.
Advantages of KNX networks
With KNX technology, any type of electrical consumer can be operated easily and promptly. Each input (sensor) can be assigned to each output (actuator) by setting parameters using the engineering tool software (ETS, see control and programming ). This is done via group addresses. Devices with the same group address listen to each other and can, for example, be switched on or off at the same time. The bus participants also each have their own unique physical address. For example, a switch that was previously intended to switch on a ceiling light can be reprogrammed to switch on the garden irrigation within a short time. Every KNX installation can also request various sensor data. For example, the data from the anemometer can be used to retract blinds or awnings or to automatically close windows and doors at a certain wind strength. Which actions should take place can be flexibly determined by programming the system. Different trades can also be connected to one another. Heating, ventilation, alarm system, blinds or shading systems, lighting and weather station can communicate via a uniform network and react independently to changing environmental conditions. In addition, it is possible to integrate further trades via gateways. The fact that all switches and sensors are connected to one another via a looped bus cable simplifies the cabling effort. All feed lines of the consumers to be controlled, e.g. B. lights, blinds, motors, etc., are drawn directly to the electrical distribution.
Disadvantages of KNX
Compared to conventional electrical installation, the acquisition costs are higher due to the increased cabling requirement, which takes up more space in the installation zones. In addition, larger distributors are required to accommodate the couplers and the bus power supply. The actuators and sensors must also be placed and usually also covered. There can be cost advantages if different trades (heating, ventilation, plumbing, electrical, etc.) are combined with one another, since other regulations can be dispensed with. Signal transmission from cameras, intercoms, multi-room systems, etc. similar is not possible due to the low data rate of KNX. In the ideal case, each room has only one supply and bus line, and only then is it distributed to individual consumers in the room. The acquisition costs for KNX-compatible sensors (buttons, switches) are usually much higher than conventional switches that switch purely electrically. With regard to the cost structure and the distribution channel, the literature says: “ For example, devices of the KNX / EIB are often sold at the same price compared to different manufacturers, the costs of approx. 370 euros plus VAT for a power supply that only has a transformer and contains few electronic components, is much too high and hardly justifiable in view of a market availability of more than 20 years. ".
A possible energy saving through the central control is offset by the own power consumption of the KNX bus. A current requirement of 5 to 8 mA is to be expected per actuator or sensor. Actuators and sensors with the highest possible port density should therefore be used. This reduces the proportionate power consumption per switched or monitored function. At the same time, with a high port density, the proportional costs on the bus interface are lower, so the price per port is lower. With the spread of energy-saving lamps, the potential for energy savings through automatic light switching functions ( presence detectors ) is falling .
In the specialist literature, doubts about the future viability of the system are repeatedly voiced, whereby the author also sees low economic profit potential for the manufacturer. In addition, the author states that parallel bus systems ( DALI , DMX ) are developing parallel to the KNX bus , which can control subtasks (LED light, motors for shading, etc.) faster and more precisely using specialized protocols.
The data is transmitted unencrypted in the KNX bus. In particular, bus lines that lead out of the secured building envelope into the open (e.g. outside switches) pose a considerable security risk. The KNX Association has reacted to this, whereby appropriately equipped products are hardly available and the proportion of the installed components is below 0.1%.
Further development and future
Originally focused on commercial buildings, KNX is also increasingly being used in residential buildings and, in particular, in single-family buildings . This ensures an increased demand for components in this area, but also for a more focused development of devices and software for private end users. On the other hand, KNX loses out to other systems in property construction, e.g. B. EnOcean , ZigBee for simple switches that are assigned to a higher-level system (e.g. Bacnet , Modbus ).
While the strength of KNX in decentralized cabling is economically useful in commercial buildings, centralized cabling has prevailed in small buildings (routing all sensor and actuator lines to one or a few central points).
The trend towards the all-IP solution in building construction is changing the market permanently and is having an increasing impact on the private sector, as has already happened in the area of VoIP in particular . The increasing tendency to use logic (server, visualization) is causing a strong increase in PLCs in building construction. Some manufacturers of PLCs offer gateways to KNX in order to merge both worlds, whereby the KNX components are mainly used in the sense of input and output channels without using their own intelligence. KNX thus only corresponds to a cable-saving installation method . In addition, PLCs specially adapted for building technology appeared.
In the long term, KNX will not be able to escape the general trend of networking on the IP level (KNXnet), the options of the competing systems are too diverse. Higher data rates, especially from the media sector ( multiroom ), require different networking concepts anyway.
The attempt to use the KNX-RF + to serve the market of radio-based solutions, which are particularly required for the lucrative (and very large) retrofit market, consists ( as of 2016) in comparison to other radio-based systems ( Homematic , Qivicon ) cost and Functionally non-competitive push-button sensors and actuators.
Expansion into the USA is currently difficult, since many smart home systems traditionally work there using X10 ( Powerline ) and the successor technology (e.g. Insteon) is also powerline-based. The PLC bus (also powerline-based) is widespread in the Asian area , and there, too, places tight limits on the expansion of KNX (regardless of its limited technical possibilities).
Examples for the use of KNX
Example "Switching on a ceiling light"
As a rule, the command to switch on the ceiling light is given by a "normal" light switch. A person presses the switch and the light comes on. The switch-on command can, however, also be issued cumulatively via sensors. At dusk, for example, a light sensor measures that the light intensity in the room is decreasing. Therefore he gives the command to the ceiling light to switch on. However, it could also make the ceiling light continuously brighter at dusk. When the sun has completely set, the lamp shines with maximum brightness. With this continuous dimming, the room is kept constantly bright. If there are several ceiling lights in the room, different lighting scenarios can be programmed, provided that each individual ceiling light was connected separately via actuators. These can then also be switched on using a regular switch. Any type of lighting in the room can be programmed on this switch via a central computer, since each individual lamp can then be controlled.
Example "opening / closing windows"
There are three windows in one room. These have an automatic opening / closing mechanism. Any window or all of them can be opened at the touch of a button using a switch installed in the room. An air quality sensor can also be installed in the room. If there is bad / stuffy air in this room, one or all of the windows will be opened automatically and the room will be ventilated. The windows are then automatically closed again. This can also be combined with a rain sensor. If the rain sensor registers rain outside, the command can be issued via the EIB network to close all windows.
These functions can also be combined with other systems (= trades) without any problems. Coupling with the locking system is conceivable. If the front door is locked, all open windows in the house are automatically closed. A combination with a natural gas sensor is also conceivable. If natural gas escapes from a natural gas pipe and is concentrated in the room where the heating system is installed, a natural gas sensor can register this. All relevant windows are then automatically opened so that the natural gas evaporates. This prevents a gas explosion. In addition, an electrically controllable closure can close the main natural gas line so that no further gas flows into the room.
Summary
Using KNX,
- lighting
- Shading
- heater
- climate
- ventilation
- alarm
- information
- Remote access (via mobile phone, smartphone, telephone, internet)
- Central control of the house
interconnect integrated.
Structure of the KNX
Physical structure
The KNX is divided into 15 areas with 15 lines each and a maximum of 256 participants per line. Required active couplers count as participants and thus reduce the maximum number of participants. This means that up to ((256x15) +64) x15 + 63 = 58,623 bus users can be controlled individually. For example, the physical address 8.7.233 in area 8, line 7, designates subscriber 233. Couplers always receive subscriber number 0, e.g. B. the physical address 8.7.0.
Normally 64 bus subscribers (TLN) can be connected per line or if line repeaters are used up to 256 bus subscribers. The addresses xx64, xx128 and xx192 are reserved for these up to three possible line repeaters. Each segment of the line requires its own power supply, i.e. four power supplies when expanding to 256 subscribers.
In order to expand the structure of lines, they can be connected to the so-called main line via line couplers. The main line itself needs at least one power supply and can also contain a maximum of 63 TLN plus a line coupler. A main line connects a maximum of 15 lines with each other and forms an area.
A maximum of 15 areas can be connected to one another via an area line (backbone). The area line also needs at least its own power supply. A further 63 participants can also be integrated on the area line.
Devices that offer central functions are usually integrated on the higher-level lines, main lines and area lines. These are physical sensors, visualization, logic components and actuators in distributors that provide switching outputs for sensors from different lines.
Logical structure
Associated actuators and sensors are connected to a so-called group address, which can be easily programmed. This makes it possible to change the relationship between switches and lamps, for example, at any time without having to lay new cables.
The devices communicate with standardized commands. This ensures that devices from different manufacturers work together. This was the first time that a uniform standard was created that is open to all manufacturers of electrical devices and control components. Several hundred thousand buildings around the world have now been equipped with a KNX system. The variety of control units from the various manufacturers is correspondingly large.
KNX is an open standard, i. H. every manufacturer / developer has full access to all necessary technical information that he needs for further development. However, this requires membership in the KNX Association, which is subject to a fee. It is therefore criticized that this is not a really open standard, since membership generally incurs costs. Only when this membership is also free of charge can we speak of an “open standard”. However, it is not recognized that this is a common and, especially for smaller companies, very cheap way of obtaining the necessary patent rights.
Control and programming
The programming of the participants and the assignment of the group addresses is done with a special, but also standardized software, the engineering tool software (ETS). The ETS is provided by the umbrella organization KNX Association and ensures the problem-free cooperation of components from different manufacturers (now over 358 manufacturers worldwide). The ETS is software that is protected by licensing law and distributed by the KNX Association. In any case, an ETS installation is required to commission a KNX installation. The available versions differ in the number of controllable devices and thus also in their price: Demo (5 KNX devices, free of charge), Lite (20 KNX devices, € 200), Professional (unlimited, € 1000)
The KNX standard has now also been adopted by the USA and many Asian countries for house construction.
All major manufacturers of electrical installation products and heating equipment suppliers now offer KNX-compatible devices.
As the successor to EIB, the KNX standard was further developed in 2002 by the Konnex Association (then named) according to the EN50090 standard. KNX is downward compatible with the EIB, so that existing EIB systems can be expanded with KNX field modules.
Package structure
| Octet 0 | 1 | 2 | 3 | 4th | 5 | 6th | 7th | 8th | ... | N-1 | N <= 22 | ||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Control byte | Source address | Destination address | DRL | TPCI | APCI | Data / APCI | Data | Checksum | |||||
The control byte determines the packet priority and differentiates between a standard and an extended packet:
| 7th | 6th | 5 | 4th | 3 | 2 | 1 | 0 |
|---|---|---|---|---|---|---|---|
| 1 | 0 | R. | 1 | p1 | p0 | 0 | 0 |
The repeat bit R is 1 when the packet is sent for the first time, and 0 when it is repeated, so that participants who have already received the packet correctly can ignore the repetition.
The priority levels are divided into the bits:
| p1 | p0 | meaning |
|---|---|---|
| 0 | 0 | System function |
| 1 | 0 | Alarm function |
| 0 | 1 | high priority |
| 1 | 1 | normal priority |
The source address (typical notation <area>. <line>. <Subscriber>) consists of two bytes, whereby the MSB is transmitted first:
| 7th | 6th | 5 | 4th | 3 | 2 | 1 | 0 | 7th | 6th | 5 | 4th | 3 | 2 | 1 | 0 |
| B3 | B2 | B1 | B0 | L3 | L2 | L1 | L0 | T7 | T6 | T5 | T4 | T3 | T2 | T1 | T0 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Area | line | Attendees | |||||||||||||
The target address addresses either an individual recipient (uni-cast) or a group (multi-cast; typical notation: <main group> / <middle group> / <sub-group>); the type of the destination address is set in the DRL byte. With a physical address, the coding corresponds to the source address. A group address is coded differently:
| 7th | 6th | 5 | 4th | 3 | 2 | 1 | 0 | 7th | 6th | 5 | 4th | 3 | 2 | 1 | 0 |
| 0 | H3 | H2 | H1 | H0 | M2 | M1 | M0 | U7 | U6 | U5 | U4 | U3 | U2 | U1 | U0 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Main group | Middle group | Subgroup | |||||||||||||
The structure of the DRL byte (from D estination-adress-flag, R outing-counter, L ength) is
| 7th | 6th | 5 | 4th | 3 | 2 | 1 | 0 |
| D. | R2 | R1 | R0 | L3 | L2 | L1 | L0 |
|---|
| D. | Destination address |
|---|---|
| 0 | physical address |
| 1 | Group address |
The routing counter R0..R2 is initialized with 6 and decremented by each line and area coupler. A packet with the value 0 is discarded. A value of 7 prevents decrementation and allows the packet to be forwarded as often as required. The bits L0..L3 indicate the length of the following user data minus two, i.e. H. a length = 0 corresponds to 2 bytes, length = 15 corresponds to 17 bytes.
The Transport Layer Protocol Control Information (TPCI) describes the communication on the Transport Layer, e.g. B. to establish a point-to-point connection. The Application Layer Protocol Control Information (APCI) are responsible for the Application Layer Services (read, write, reply, ...). One possible variant of the user data is the standardized communication according to DPT (data point type), formerly EIS (EIB Interworking Standard). There are different DPT and EIS formats:
| DPT 1 | EIS 1 | Switching |
| DPT 3 | EIS 2 | Dimming |
| DPT 10 | EIS 3 | Time |
| DPT 11 | EIS 4 | date |
| DPT 9 | EIS 5 | Value, 16-bit floating point number, proprietary format |
| DPT 5 | EIS 6 | Relative value, 0 ... 100% |
| DPT 1 | EIS 7 | Drive control |
| DPT 2 | EIS 8 | Forced control |
| DPT 14 | EIS 9 | Floating-point number , 32 bit, IEEE 754 single |
| DPT 7/8 | EIS 10 | 16-bit value |
| DPT 12/13 | EIS 11 | 32-bit value |
| DPT 15 | EIS 12 | Access control |
| DPT 4 | EIS 13 | ASCII characters |
| DPT 5/6 | EIS 14 | 8-bit value |
| DPT 16 | EIS 15 | String |
The checksum is an inverted, bit-by-bit XOR link of all bytes previously sent in the packet.
With a long frame , even N> 255 octets are possible.
Software frameworks
Cross-platform
- OSGi - Middleware standard (Java framework) for the integration of EHS / CHAIN, EIB, Konnex, LON etc. in service gateways
- openHAB - Java / OSGi-based integration platform for using and networking KNX with other protocols such as HomeMatic , 1-Wire etc.
- MisterHouse - Perl-based framework for home automation (EIB, X10 etc.)
- ioBroker - Node.js-based IoT platform for networking between different protocols and IoT systems with a KNX system.
- SmartHomeNG - Open Source System, which acts as a metagateway between different "things". The programming of logics is done in the easy-to-learn programming language Python.
Windows
In the 1990s, OPC (OLE for Process Control) was developed as a standardized software interface for the Windows platform in order to facilitate the integration of various, until then mostly manufacturer-dependent and therefore proprietary, automation buses in one system. Originally at home in industrial automation, the possibility quickly emerged of being able to work in an interdisciplinary manner with other areas - such as building automation, for example - through OPC.
With the OPC server, the software tool came onto the market in 1998, which greatly simplified the integration of the EIB (KNX) into hybrid automation systems. In this way, software solutions can be created that include classic building functions, e.g. B. merge the heating and lighting control of a production facility using EIB as well as the visualization and automation of the industrial production process homogeneously via other bus systems. The coupling of different building buses, such as EIB and LON , to an integrated management system is also easily possible thanks to the existing OPC servers for KNX and LON.
Linux
The KNX daemon eibd and its fork knxd offer an interface to the EIB / KNX bus under Linux.
Variants of KNX networks
-
Cable-guided KNX : The architecture is to a limited extent comparable to an Ethernet . The transmission corresponds to UART with RZ coding of the zeros at 50% of the bit time.
- Type TP-0: transmission at 2400 baud. This variant comes from the BatiBUS standard.
- Type TP-1: transmission at 9600 baud. This variant comes from the EIB standard.
-
Powerline , also called Powernet (the phase-coupled power lines serve as the network medium, so no separate bus lines are required). The last remaining supplier discontinued the product range at the end of 2015.
- Type PL-110: transmission with 1200 baud on 110 kHz. This variant comes from the EIB standard.
- Type PL-132: transmission with 2400 baud on 132 kHz. This variant comes from the EHS standard.
- KNX-RF , radio transmission on 868 MHz (the components are controlled via radio).
- KNXnet (latest development: merging of the networks KNX and LAN . The entire building automation is controlled via a computer network (Ethernet).)
Networked home appliances
The renaissance of the KNX approaches reflects the trend in white goods towards “networked household appliances”. At the moment, this mostly involves Powerline solutions, where the EHS favored by the European umbrella association of household appliance manufacturers, CECED, has clearly established itself as the cross-manufacturer standard.
With regard to EHS, the focus is less on sensor / actuator technology than on the specified protocol frames ("objects") with which the individual functions of household appliances are controlled.
See also
- Smart living
- Complementary Technologies
Individual evidence
- ↑ KNX - the world's only open standard for home and building system technology. (PDF; 1.5 MB) (No longer available online.) KNX Germany in the ZVEI - Zentralverband Elektrotechnik- und Elektronikindustrie e. V., October 3, 2007, archived from the original on December 6, 2008 ; accessed on July 31, 2019 .
- ↑ Standardization . KNX Association. Archived from the original on June 20, 2009. Retrieved July 31, 2019.
- ↑ Published / in progress. (No longer available online.) CENELEC, formerly in the original ; Retrieved June 19, 2009 . ( Page no longer available , search in web archives )
- ↑ The restless flickering of Light & Building 2014. In: springerprofessional.de. April 7, 2014, accessed June 8, 2016 .
- ↑ E-Necker: 7 deadly sins in KNX planning. In: E-Necker. October 18, 2018, accessed June 7, 2020 (German).
- ↑ Bernd Aschendorf: Energy management through building automation . doi : 10.1007 / 978-3-8348-2032-7 ( springer.com [accessed July 14, 2016]). , P. 786
- ↑ a b The restless flickering of Light & Building 2014. In: springerprofessional.de. April 7, 2014, accessed June 8, 2016 .
- ↑ KNX security - position paper. (PDF) (No longer available online.) In: KNX.org. 2014, archived from the original on June 9, 2016 ; accessed on July 31, 2019 .
- ↑ KNX - MyKNX. Accessed July 31, 2019 .
- ↑ Interworking KNX. ( Memento of August 9, 2014 in the Internet Archive ) Retrieved July 31, 2019.
- ↑ openHAB website
- ↑ Web site MisterHouse
- ↑ KNX - ioBroker. Retrieved May 17, 2017 .
- ↑ EIB daemon (English)
- ↑ knxd / knxd. Retrieved April 25, 2015 .
literature
- Stefan Heinle: Home automation with KNX, DALI, 1-Wire and Co. - The comprehensive manual . Rheinwerk Verlag, Bonn 2015, ISBN 978-3-8362-3461-0 .
- Frank Völkel: Smart Home with KNX, plan and install it yourself . Franzis, Munich 2011, ISBN 978-3-7723-4387-2 .
- Rainer Scherg: EIB / KNX systems - plan, install and visualize . Vogel, Würzburg 2008, ISBN 978-3-8343-3125-0 .
- Willy Meyer: KNX / EIB Engineering Tool Software . Hüthig & Pflaum, Munich & Heidelberg 2007, ISBN 978-3-8101-0266-9 .
- Karlheinz Frank: EIB / KNX basics of building system technology . Huss, Berlin 2008, ISBN 978-3-341-01540-7 .
