Wilt u een slim huis/gebouw dat alles heeft?
KNX IoT producten en oplossingen evolueren 
slimmehuizen en gebouwen naar het volgende niveau.

Waarom KNX IoT?

  • Interoperabel & veilig: KNX is de referentie als het over interoperabiliteit gaat. Neem gewoon twee gecertificeerde apparaten van eender welke leverancier en ze zullen gewoon op een veilige manier samenwerken op applicatieniveau. Volgens deze filosofie is KNX IoT ontworpen om het hoogste veiligheidsniveau te behouden. KNX IoT busdeelnemers hebben beveiliging ingebouwd in het ontwerp. Met deze robuuste nieuwe KNX IoT technologie kunnen fabrikanten en ontwikkelaars de beste apparaten, oplossingen en diensten bouwen die geïnstalleerd zullen worden door professionals in de sector van slimme huizen en gebouwen.
  • Native KNX IoT apparaten (IPv6): KNX busdeelnemers gebruiken nu een nieuwe aanpak om in de IPv6 architectuur te passen. De nieuwe generatie KNX IoT busdeelnemers zal verbinding kunnen maken met IP netwerken (bekabeld en/of draadloos) om te communiceren met andere KNX IoT busdeelnemers en met klassieke KNX busdeelnemers die Twister Pair of Radio Frequency gebruiken.
  • Gestandaardiseerde API: Apparaten die in een KNX-netwerk moeten worden geïntegreerd, kunnen dat nu dankzij een gestandaardiseerde API die verbinding kan maken met KNX-installaties. Deze API is eenvoudig, veilig, ontdaan van KNX-specifieke kennis en toekomstbestendig.
  • Eén tool: ETS: Al deze mogelijkheden worden mogelijk gemaakt door het gebruik van ETS. Met ETS kunnen KNX busdeelnemers van meer dan 500 fabrikanten geconfigureerd worden, onafhankelijk van hun fysieke laag, en projectinformatie kan geëxporteerd worden naar om het even welke KNX IoT API Server met behulp van een verkopersonafhankelijke tool. ETS biedt kerninteroperabiliteit in een aantrekkelijke tool met een moderne gebruikersinterface.
  • KNX, het grootste ecosysteem in huis- en gebouwautomatisering: Deze nieuwe mogelijkheid om te communiceren met behulp van de KNX-technologie zorgt voor meer flexibiliteit. Fabrikanten kunnen nu gebruik maken van nieuwe ontwikkelingsmogelijkheden om innovatieve producten en oplossingen te creëren; en professionals hebben meer mogelijkheden om een groter KNX ecosysteem in hun projecten te creëren.
Aan de slag met KNX

Maak elk huis en gebouw slim met KNX IoT

Leer waarom KNX IoT een wereld van mogelijkheden opent voor slimme huizen en gebouwen in deze korte introductievideo.

Meer gedetailleerde video's en webinars over KNX IoT vindt u op ons YouTube kanaal.

KNX, het grootste ontwikkelingslandschap in zijn soort

Een baanbrekend ontwikkelingsplatform dat als basis dient voor opmerkelijke oplossingen is in 2023 aan de wereld gepresenteerd en maakt alle business cases in de smart home en building verticals mogelijk. Van enkelvoudige producten tot diensten, elke fabrikant of ontwikkelaar kan de nodige middelen vinden om unieke oplossingen te creëren.

Ontdek hoe het KNX Ecosysteem werkt door met de muis over de verschillende elementen in onderstaande afbeelding te gaan.

1
1
IP Wi-Fi Rounter IP Wi-Fi Access Point

A Wi-Fi Access Point is a topology element required by the Wi-Fi network. It allows Wi-Fi-based devices to communicate with the LAN and WAN.

2
2
KNX IoT Point API device Wi-Fi

A KNX IoT Point API device - Wi-Fi device is a certified device (Stack, Application) that uses Wi-Fi as its communication medium. Unlike KNX TP and KNX RF devices, the physical layer is not part of the KNX Specifications; instead, an IPv6-based communication medium is used.

3
3
KNX IP Interface/router

A KNX IP Interface connects KNX TP-based installations with IP (IPv4) using the KNXnet/IP protocol. It offers tunneling connections, which are used by clients to establish a connection with the downstream KNX installation. KNX IP Routers provide interface functionality as well as routing capabilities. A KNX IP Router can link several KNX TP sections using IP as a backbone.

4
4
Thread Border Router

A Thread Border Router is a topology element required by the Thread network. Similar to a Wi-Fi access point, it allows Thread-based devices to communicate with the LAN and WAN.

5
5
KNX IoT Point API device - Ethernet

 A KNX IoT Point API device - Ethernet device is a certified device (Stack, Application) that uses Ethernet as its communication medium. Unlike KNX TP and KNX RF devices, the physical layer is not part of the KNX Specifications; instead, an IPv6-based communication medium is used.

6
6
KNX IoT Point API device

A KNX IoT Point API device - Thread device is a certified device (Stack, Application) that uses Thread as its communication medium. Unlike KNX TP and KNX RF devices, the physical layer is not part of the KNX Specifications; instead, an IPv6-based communication medium is used.

7
7
KNX IoT Router (TP,RF,IPv4 & IPv6)

 A KNX IoT Router is a gateway between KNX TP, RF or IPv4 devices and KNX IoT devices. It can be a stand-alone device, but it can also be integrated into other network elements (e.g., Thread Border Router + KNX IoT Router).

8
8
KNX IoT API Client(application)

 The KNX IoT API Server uses the KNX Information Model, natively exported by ETS6, to expose a standardized API for third parties to communicate with KNX installations. A certified KNX IoT API Server has been tested against KNX specifications and is compliant with the standard API model. Third parties can develop clients that seamlessly work with KNX IoT API Servers, regardless of the manufacturer.

9
9
KNX IoT API Server

 The KNX IoT API Server uses the KNX Information Model, natively exported by ETS6, to expose a standardized API for third parties to communicate with KNX installations. A certified KNX IoT API Server has been tested against KNX specifications and is compliant with the standard API model. Third parties can develop clients that seamlessly work with KNX IoT API Servers, regardless of the manufacturer.

10
10
Media coupler TP/RF

 A TP/RF media coupler connects an RF segment with a TP line. It can be added as another 'line' or can extend an existing TP line with an RF sub-segment (in this case it is called Segment Coupler).

11
11
RF/Device

 A KNX RF device is a certified device (Physical Layer, Stack, Application) that uses a RF physical layer (RF) as its communication medium.

12
12
Line Coupler

 A Line Coupler is a topology element that connects a TP line with other TP lines via a TP backbone. A maximum of 15 lines can be coupled together, forming an area. Up to 15 areas can be coupled together using an Area Coupler.

13
13
Power Supply

 A KNX Power Supply is required to power the twisted pair (TP) cable that connects KNX TP devices.

14
14
TP device

 A KNX TP device is a certified device (Physical Layer, Stack, Application) that uses a twisted pair cable (TP) as its communication medium

15
15
Segment Proxy

 A Segment Proxy enables KNX Data Secure communication with plain KNX communication. This can help prevent easily accessible KNX TP Secure devices (e.g., thermostats) from communicating with back-end KNX TP devices that are not secure. The communication up to the Segment Proxy will be secure.

16
16
Segment Coupler

 A TP/RF media coupler connects an RF segment with a TP line. It can be added as another 'line' or can extend an existing TP line with an RF sub-segment (in this case it is called Segment Coupler).

17
17
RF/Device

A KNX RF device is a certified device (Physical Layer, Stack, Application) that uses a RF physical layer (RF) as its communication medium.

18
18
TP/Device

  A KNX TP device is a certified device (Physical Layer, Stack, Application) that uses a twisted pair cable (TP) as its communication medium

1
IP Wi-Fi Rounter IP Wi-Fi Access Point

A Wi-Fi Access Point is a topology element required by the Wi-Fi network. It allows Wi-Fi-based devices to communicate with the LAN and WAN.

2
KNX IoT Point API device Wi-Fi

A KNX IoT Point API device - Wi-Fi device is a certified device (Stack, Application) that uses Wi-Fi as its communication medium. Unlike KNX TP and KNX RF devices, the physical layer is not part of the KNX Specifications; instead, an IPv6-based communication medium is used.

3
KNX IP Interface/router

A KNX IP Interface connects KNX TP-based installations with IP (IPv4) using the KNXnet/IP protocol. It offers tunneling connections, which are used by clients to establish a connection with the downstream KNX installation. KNX IP Routers provide interface functionality as well as routing capabilities. A KNX IP Router can link several KNX TP sections using IP as a backbone.

4
Thread Border Router

A Thread Border Router is a topology element required by the Thread network. Similar to a Wi-Fi access point, it allows Thread-based devices to communicate with the LAN and WAN.

5
KNX IoT Point API device - Ethernet

 A KNX IoT Point API device - Ethernet device is a certified device (Stack, Application) that uses Ethernet as its communication medium. Unlike KNX TP and KNX RF devices, the physical layer is not part of the KNX Specifications; instead, an IPv6-based communication medium is used.

6
KNX IoT Point API device

A KNX IoT Point API device - Thread device is a certified device (Stack, Application) that uses Thread as its communication medium. Unlike KNX TP and KNX RF devices, the physical layer is not part of the KNX Specifications; instead, an IPv6-based communication medium is used.

7
KNX IoT Router (TP,RF,IPv4 & IPv6)

 A KNX IoT Router is a gateway between KNX TP, RF or IPv4 devices and KNX IoT devices. It can be a stand-alone device, but it can also be integrated into other network elements (e.g., Thread Border Router + KNX IoT Router).

8
KNX IoT API Client(application)

 The KNX IoT API Server uses the KNX Information Model, natively exported by ETS6, to expose a standardized API for third parties to communicate with KNX installations. A certified KNX IoT API Server has been tested against KNX specifications and is compliant with the standard API model. Third parties can develop clients that seamlessly work with KNX IoT API Servers, regardless of the manufacturer.

9
KNX IoT API Server

 The KNX IoT API Server uses the KNX Information Model, natively exported by ETS6, to expose a standardized API for third parties to communicate with KNX installations. A certified KNX IoT API Server has been tested against KNX specifications and is compliant with the standard API model. Third parties can develop clients that seamlessly work with KNX IoT API Servers, regardless of the manufacturer.

10
Media coupler TP/RF

 A TP/RF media coupler connects an RF segment with a TP line. It can be added as another 'line' or can extend an existing TP line with an RF sub-segment (in this case it is called Segment Coupler).

11
RF/Device

 A KNX RF device is a certified device (Physical Layer, Stack, Application) that uses a RF physical layer (RF) as its communication medium.

12
Line Coupler

 A Line Coupler is a topology element that connects a TP line with other TP lines via a TP backbone. A maximum of 15 lines can be coupled together, forming an area. Up to 15 areas can be coupled together using an Area Coupler.

13
Power Supply

 A KNX Power Supply is required to power the twisted pair (TP) cable that connects KNX TP devices.

14
TP device

 A KNX TP device is a certified device (Physical Layer, Stack, Application) that uses a twisted pair cable (TP) as its communication medium

15
Segment Proxy

 A Segment Proxy enables KNX Data Secure communication with plain KNX communication. This can help prevent easily accessible KNX TP Secure devices (e.g., thermostats) from communicating with back-end KNX TP devices that are not secure. The communication up to the Segment Proxy will be secure.

16
Segment Coupler

 A TP/RF media coupler connects an RF segment with a TP line. It can be added as another 'line' or can extend an existing TP line with an RF sub-segment (in this case it is called Segment Coupler).

17
RF/Device

A KNX RF device is a certified device (Physical Layer, Stack, Application) that uses a RF physical layer (RF) as its communication medium.

18
TP/Device

  A KNX TP device is a certified device (Physical Layer, Stack, Application) that uses a twisted pair cable (TP) as its communication medium

1
1
IP Wi-Fi Rounter IP Wi-Fi Access Point

A Wi-Fi Access Point is a topology element required by the Wi-Fi network. It allows Wi-Fi-based devices to communicate with the LAN and WAN.

2
2
KNX IoT Point API device Wi-Fi

A KNX IoT Point API device - Wi-Fi device is a certified device (Stack, Application) that uses Wi-Fi as its communication medium. Unlike KNX TP and KNX RF devices, the physical layer is not part of the KNX Specifications; instead, an IPv6-based communication medium is used.

3
3
KNX IP Interface/router

A KNX IP Interface connects KNX TP-based installations with IP (IPv4) using the KNXnet/IP protocol. It offers tunneling connections, which are used by clients to establish a connection with the downstream KNX installation. KNX IP Routers provide interface functionality as well as routing capabilities. A KNX IP Router can link several KNX TP sections using IP as a backbone.

4
4
Thread Border Router

A Thread Border Router is a topology element required by the Thread network. Similar to a Wi-Fi access point, it allows Thread-based devices to communicate with the LAN and WAN.

5
5
KNX IoT Point API device - Ethernet

 A KNX IoT Point API device - Ethernet device is a certified device (Stack, Application) that uses Ethernet as its communication medium. Unlike KNX TP and KNX RF devices, the physical layer is not part of the KNX Specifications; instead, an IPv6-based communication medium is used.

6
6
KNX IoT Point API device

A KNX IoT Point API device - Thread device is a certified device (Stack, Application) that uses Thread as its communication medium. Unlike KNX TP and KNX RF devices, the physical layer is not part of the KNX Specifications; instead, an IPv6-based communication medium is used.

7
7
KNX IoT Router (TP,RF,IPv4 & IPv6)

 A KNX IoT Router is a gateway between KNX TP, RF or IPv4 devices and KNX IoT devices. It can be a stand-alone device, but it can also be integrated into other network elements (e.g., Thread Border Router + KNX IoT Router).

8
8
KNX IoT API Client(application)

 The KNX IoT API Server uses the KNX Information Model, natively exported by ETS6, to expose a standardized API for third parties to communicate with KNX installations. A certified KNX IoT API Server has been tested against KNX specifications and is compliant with the standard API model. Third parties can develop clients that seamlessly work with KNX IoT API Servers, regardless of the manufacturer.

9
9
KNX IoT API Server

 The KNX IoT API Server uses the KNX Information Model, natively exported by ETS6, to expose a standardized API for third parties to communicate with KNX installations. A certified KNX IoT API Server has been tested against KNX specifications and is compliant with the standard API model. Third parties can develop clients that seamlessly work with KNX IoT API Servers, regardless of the manufacturer.

10
10
Media coupler TP/RF

 A TP/RF media coupler connects an RF segment with a TP line. It can be added as another 'line' or can extend an existing TP line with an RF sub-segment (in this case it is called Segment Coupler).

11
11
RF/Device

 A KNX RF device is a certified device (Physical Layer, Stack, Application) that uses a RF physical layer (RF) as its communication medium.

12
12
Line Coupler

 A Line Coupler is a topology element that connects a TP line with other TP lines via a TP backbone. A maximum of 15 lines can be coupled together, forming an area. Up to 15 areas can be coupled together using an Area Coupler.

13
13
Power Supply

 A KNX Power Supply is required to power the twisted pair (TP) cable that connects KNX TP devices.

14
14
TP device

 A KNX TP device is a certified device (Physical Layer, Stack, Application) that uses a twisted pair cable (TP) as its communication medium

15
15
Segment Proxy

 A Segment Proxy enables KNX Data Secure communication with plain KNX communication. This can help prevent easily accessible KNX TP Secure devices (e.g., thermostats) from communicating with back-end KNX TP devices that are not secure. The communication up to the Segment Proxy will be secure.

16
16
Segment Coupler

 A TP/RF media coupler connects an RF segment with a TP line. It can be added as another 'line' or can extend an existing TP line with an RF sub-segment (in this case it is called Segment Coupler).

17
17
RF/Device

A KNX RF device is a certified device (Physical Layer, Stack, Application) that uses a RF physical layer (RF) as its communication medium.

18
18
TP/Device

  A KNX TP device is a certified device (Physical Layer, Stack, Application) that uses a twisted pair cable (TP) as its communication medium

1
IP Wi-Fi Rounter IP Wi-Fi Access Point

A Wi-Fi Access Point is a topology element required by the Wi-Fi network. It allows Wi-Fi-based devices to communicate with the LAN and WAN.

2
KNX IoT Point API device Wi-Fi

A KNX IoT Point API device - Wi-Fi device is a certified device (Stack, Application) that uses Wi-Fi as its communication medium. Unlike KNX TP and KNX RF devices, the physical layer is not part of the KNX Specifications; instead, an IPv6-based communication medium is used.

3
KNX IP Interface/router

A KNX IP Interface connects KNX TP-based installations with IP (IPv4) using the KNXnet/IP protocol. It offers tunneling connections, which are used by clients to establish a connection with the downstream KNX installation. KNX IP Routers provide interface functionality as well as routing capabilities. A KNX IP Router can link several KNX TP sections using IP as a backbone.

4
Thread Border Router

A Thread Border Router is a topology element required by the Thread network. Similar to a Wi-Fi access point, it allows Thread-based devices to communicate with the LAN and WAN.

5
KNX IoT Point API device - Ethernet

 A KNX IoT Point API device - Ethernet device is a certified device (Stack, Application) that uses Ethernet as its communication medium. Unlike KNX TP and KNX RF devices, the physical layer is not part of the KNX Specifications; instead, an IPv6-based communication medium is used.

6
KNX IoT Point API device

A KNX IoT Point API device - Thread device is a certified device (Stack, Application) that uses Thread as its communication medium. Unlike KNX TP and KNX RF devices, the physical layer is not part of the KNX Specifications; instead, an IPv6-based communication medium is used.

7
KNX IoT Router (TP,RF,IPv4 & IPv6)

 A KNX IoT Router is a gateway between KNX TP, RF or IPv4 devices and KNX IoT devices. It can be a stand-alone device, but it can also be integrated into other network elements (e.g., Thread Border Router + KNX IoT Router).

8
KNX IoT API Client(application)

 The KNX IoT API Server uses the KNX Information Model, natively exported by ETS6, to expose a standardized API for third parties to communicate with KNX installations. A certified KNX IoT API Server has been tested against KNX specifications and is compliant with the standard API model. Third parties can develop clients that seamlessly work with KNX IoT API Servers, regardless of the manufacturer.

9
KNX IoT API Server

 The KNX IoT API Server uses the KNX Information Model, natively exported by ETS6, to expose a standardized API for third parties to communicate with KNX installations. A certified KNX IoT API Server has been tested against KNX specifications and is compliant with the standard API model. Third parties can develop clients that seamlessly work with KNX IoT API Servers, regardless of the manufacturer.

10
Media coupler TP/RF

 A TP/RF media coupler connects an RF segment with a TP line. It can be added as another 'line' or can extend an existing TP line with an RF sub-segment (in this case it is called Segment Coupler).

11
RF/Device

 A KNX RF device is a certified device (Physical Layer, Stack, Application) that uses a RF physical layer (RF) as its communication medium.

12
Line Coupler

 A Line Coupler is a topology element that connects a TP line with other TP lines via a TP backbone. A maximum of 15 lines can be coupled together, forming an area. Up to 15 areas can be coupled together using an Area Coupler.

13
Power Supply

 A KNX Power Supply is required to power the twisted pair (TP) cable that connects KNX TP devices.

14
TP device

 A KNX TP device is a certified device (Physical Layer, Stack, Application) that uses a twisted pair cable (TP) as its communication medium

15
Segment Proxy

 A Segment Proxy enables KNX Data Secure communication with plain KNX communication. This can help prevent easily accessible KNX TP Secure devices (e.g., thermostats) from communicating with back-end KNX TP devices that are not secure. The communication up to the Segment Proxy will be secure.

16
Segment Coupler

 A TP/RF media coupler connects an RF segment with a TP line. It can be added as another 'line' or can extend an existing TP line with an RF sub-segment (in this case it is called Segment Coupler).

17
RF/Device

A KNX RF device is a certified device (Physical Layer, Stack, Application) that uses a RF physical layer (RF) as its communication medium.

18
TP/Device

  A KNX TP device is a certified device (Physical Layer, Stack, Application) that uses a twisted pair cable (TP) as its communication medium

KNX IoT Ontwikkeling en KNX Startup Incubator

Geïnteresseerd in KNX IoT ontwikkeling? Ontdek meer over KNX IoT en hoe u kan ontwikkelen voor KNX IoT, de voordelen en de ondersteuning die KNX biedt via onze KNX Startup Incubator.

KNX IoT voor ontwikkelaars

Reis met ons mee

Maak een MyKNX account aan om op de hoogte te blijven van het laatste nieuws in KNX IoT, technologische evenementen, innovatieve KNX producten en meer. Word lid van onze community voor toegang tot exclusieve inzichten en maak deel uit van de toekomst van duurzame energie. Meld u vandaag nog aan en blijf op de hoogte!

Maak een MyKNX account aan