¿Quiere una casa/edificio inteligente que lo tenga 
todo?Los dispositivos y soluciones IoT KNX llevan las viviendas y edificios inteligentes al siguiente nivel.

¿Por qué KNX IoT?

  • Interoperable y seguro: KNX ha sido la referencia cuando se habla de interoperabilidad. Basta con coger dos dispositivos certificados de cualquier proveedor, y simplemente trabajarán juntos a nivel de aplicación de forma segura. Siguiendo esta filosofía, KNX IoT ha sido diseñado para mantener el más alto nivel de seguridad. Los dispositivos KNX IoT vienen con seguridad integrada por diseño. Con esta nueva y robusta tecnología KNX IoT, los fabricantes y desarrolladores pueden construir los mejores dispositivos, soluciones y servicios que serán instalados por los profesionales de la industria de casas y edificios inteligentes.
  • Dispositivos KNX IoT Nativos (IPv6): Los dispositivos KNX utilizan ahora un nuevo enfoque para adaptarse a la arquitectura IPv6. La nueva generación de dispositivos KNX IoT será capaz de conectarse a redes IP (cableadas y/o inalámbricas) para tener comunicación con otros dispositivos KNX IoT así como con dispositivos KNX clásicos que usen Twister Pair o Radio Frecuencia.
  • API Estandarizada: Para Aquellos dispositivos que necesiten integrarse en una red KNX, ahora es posible gracias a una API estandarizada que puede conectar con instalaciones KNX. Esta API es simple, segura, abstraída del conocimiento específico KNX y a prueba de futuro.
  • Una Herramienta: ETS: Todas estas capacidades son posibles gracias al uso de ETS. Con ETS, los dispositivos KNX de más de 500 fabricantes pueden ser configurados independientemente de su capa física, y la información del proyecto puede ser exportada a cualquier KNX IoT API Server utilizando una herramienta independiente del proveedor. ETS proporciona interoperabilidad básica en una herramienta atractiva con una interfaz de usuario moderna.
  • KNX, el mayor ecosistema en automatización de viviendas y edificios: Con esta nueva posibilidad de comunicarse utilizando la Tecnología KNX, aporta más flexibilidad. Los fabricantes pueden ahora utilizar las nuevas posibilidades de desarrollo para crear productos y soluciones innovadoras; así como los profesionales tienen más posibilidades de crear un mayor ecosistema KNX en sus proyectos.
Comience con KNX

Convierta cualquier hogar y edificio en inteligente con KNX IoT

Descubra por qué KNX IoT abre un mundo de posibilidades para casas y edificios inteligentes en este breve vídeo de introducción.

Puede encontrar más vídeos detallados y webinars sobre KNX IoT en nuestro canal de YouTube.

KNX, el mayor entorno de desarrollo de su clase

En 2023 se ha presentado al mundo una innovadora plataforma de desarrollo que sirve de base para soluciones notables y que permite todos los casos de negocio en los verticales del hogar y la construcción inteligentes. Desde productos individuales a servicios, cualquier fabricante o desarrollador puede encontrar los recursos necesarios para crear soluciones únicas.

Descubra cómo funciona el Ecosistema KNX pasando el ratón por encima de los diferentes elementos en la siguiente imagen.

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

Desarrollo IoT KNX e Incubadora de Startups KNX

¿Está interesado en el desarrollo KNX IoT? Descubra más sobre KNX IoT y cómo puede desarrollar para KNX IoT, los beneficios y el apoyo que KNX ofrece a través de nuestra KNX Startup Incubator.

KNX IoT para desarrolladores

Acompáñenos en nuestro viaje

Crea una cuenta MyKNX para estar al día de lo último en KNX IoT, eventos tecnológicos, productos KNX innovadores y mucho más. Únase a nuestra comunidad para acceder a información exclusiva y formar parte del futuro de la energía sostenible. ¡Regístrese hoy y manténgase conectado!

Crear una cuenta MyKNX