Volete una casa/edificio intelligente che 
abbia tutto?I dispositivi e le soluzioni KNX IoT 
fanno evolvere le case e gli edifici intelligenti di
al livello successivo.

Perché KNX IoT?

  • Interoperabilità e sicurezza: KNX è stato il punto di riferimento quando si parla di interoperabilità. Basta prendere due dispositivi certificati di qualsiasi fornitore e questi lavoreranno insieme a livello di applicazione in modo sicuro. Seguendo questa filosofia, KNX IoT è stato progettato per mantenere il più alto livello di sicurezza. I dispositivi KNX IoT sono dotati di sicurezza incorporata per progettazione. Con questa nuova e robusta tecnologia KNX IoT, produttori e sviluppatori possono costruire i migliori dispositivi, soluzioni e servizi che saranno installati dai professionisti del settore delle case e degli edifici intelligenti.
  • Dispositivi IoT KNX nativi (IPv6): I dispositivi KNX utilizzano ora un nuovo approccio per adattarsi all'architettura IPv6. La nuova generazione di dispositivi KNX IoT sarà in grado di connettersi alle reti IP (via cavo e/o wireless) per comunicare con altri dispositivi KNX IoT e con i dispositivi KNX classici che utilizzano Twister Pair o Radio Frequenza.
  • API standardizzata: Per i dispositivi che devono essere integrati in una rete KNX, è ora possibile grazie a un'API standardizzata in grado di connettersi alle installazioni KNX. Questa API è semplice, sicura, astrae dalle conoscenze specifiche di KNX ed è a prova di futuro.
  • Uno strumento: ETS: Tutte queste funzionalità sono rese possibili dall'uso di ETS. Con ETS, i dispositivi KNX di oltre 500 produttori possono essere configurati indipendentemente dal loro livello fisico e le informazioni del progetto possono essere esportate a qualsiasi KNX IoT API Server utilizzando uno strumento indipendente dal fornitore. ETS fornisce l'interoperabilità di base in uno strumento attraente con un'interfaccia utente moderna.
  • KNX, il più grande ecosistema di automazione domestica e degli edifici: La nuova possibilità di comunicare utilizzando la tecnologia KNX offre una maggiore flessibilità. I produttori possono ora utilizzare le nuove possibilità di sviluppo per creare prodotti e soluzioni innovative, così come i professionisti hanno maggiori possibilità di creare un ecosistema KNX più ampio nei loro progetti.
Iniziare con KNX

Rendere intelligente qualsiasi casa ed edificio con KNX IoT

Scoprite perché KNX IoT apre un mondo di possibilità per case ed edifici intelligenti in questo breve video introduttivo.

Potete trovare video e webinar più dettagliati su KNX IoT sul nostro canale YouTube.

KNX, il più grande panorama di sviluppo del suo genere

Nel 2023 è stata presentata al mondo un'innovativa piattaforma di sviluppo che funge da base per soluzioni straordinarie , consentendo di risolvere tutti i casi aziendali nei settori verticali della casa intelligente e dell'edilizia. Dai singoli prodotti ai servizi, qualsiasi produttore o sviluppatore può trovare le risorse necessarie per creare soluzioni uniche.

Scoprite come funziona l'Ecosistema KNX passando il mouse sui diversi elementi nell'immagine sottostante.

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

Sviluppo KNX IoT e Incubatore KNX Startup

Interessato allo sviluppo KNX IoT? Scoprite di più su KNX IoT e su come sviluppare per KNX IoT, i benefici e il supporto che KNX offre attraverso il nostro KNX Startup Incubator.

KNX IoT per gli sviluppatori

Unisciti a noi nel nostro viaggio

Create un account MyKNX per rimanere aggiornati sulle ultime novità di KNX IoT, sugli eventi tecnologici, sui prodotti KNX innovativi e molto altro. Entrate a far parte della nostra comunità per accedere ad approfondimenti esclusivi ed essere parte del futuro dell'energia sostenibile. Iscriviti oggi stesso e rimani connesso!

Creare un account MyKNX