KNOWLEDGE BASE · SMART HOME

Smart home remote access and security: KNX Secure, IP router, VPN

A KNX smart home is secure when the bus is physically protected, the network link is encrypted, remote access goes through a VPN, and the wall switches keep working without the internet. This article explains the difference between KNX Data Secure and KNX IP Secure, the role of the IP router and the IP interface, tunnelling versus routing, what to do with the device certificate, and what the EU Cyber Resilience Act means for manufacturers and owners.

In short

  • Two layers: KNX Data Secure encrypts and authenticates group telegrams end to end; KNX IP Secure protects KNX traffic on the IP network (routing, tunnelling, ETS connection). They can be combined.
  • Device certificate (FDSK): printed on the Secure device and usually on an enclosed card as a QR code; ETS starts from it and then assigns its own device keys. The project password and certificates must be handed over and stored safely.
  • Remote access: via VPN, not via a port opened to the internet. KNX IP should preferably run on a separate network.
  • Manual control: wall push-buttons control directly on the bus; a failure of the visualisation, the app or the internet must not stop lighting and blinds.

Author: Norbert Madarász, Managing Director and Partner · Updated: 10 November 2026

Where is a KNX smart home vulnerable?

A KNX system runs on a two-wire bus (TP) inside the house. Risk appears where the system leaves this closed loop:

  • Outdoor bus cable: door station, outdoor push-button, weather station – if the bus cable is accessible from outside, it needs physical protection or a secure device.
  • IP network: the IP router or IP interface sits on the home LAN; whatever can be reached from the network can also be reached by an infected computer or a poorly secured Wi-Fi.
  • Remote access: the biggest mistake is opening the KNX IP port directly to the internet.
  • Project file and passwords: anyone with the ETS project and its password can reprogram the whole system.

IP router or IP interface: tunnelling and routing

An IP interface provides a point-to-point connection (tunnelling) to the KNX bus: ETS connects through it for programming, and many visualisations use it too. One device can handle several tunnelling connections at once; the Siemens N 148/23 IP Interface Secure, for example, up to five.

A KNX IP router is also a line coupler (routing): it sends KNX telegrams as multicast onto the IP network (by default to 224.0.23.12, according to the ABB IPR/S 2.1 manual), so the IP network becomes the KNX backbone between lines or parts of a building.

AspectTunnelling (IP interface, IP router)Routing (IP router)
Connectionpoint to point, one client per connectionmulticast, every router listens
Typical useETS programming, visualisation, applinking lines or building parts over IP
SecurityIP Secure: password per tunnelling connectionIP Secure: encrypted backbone line
Network requirementsimpleswitches must handle multicast

KNX Data Secure vs KNX IP Secure: what is the difference?

KNX Data Secure encrypts and authenticates at the level of individual group objects, on every medium, based on AES-128. It only works when every object on a group address belongs to a Secure device; an older device does not understand the encrypted telegram. So it can be mixed within one house: critical functions (alarm, access control) encrypted, the rest conventional.

KNX IP Secure protects the IP segment: routing multicast, tunnelling connections and the ETS commissioning connection. According to the KNX Association, open internet access is an inherent risk and VPN already offers secure remote access; IP Secure also protects within the local network.

AspectKNX Data SecureKNX IP Secure
What does it protect?group telegrams end to endKNX traffic on the IP network
Where?every medium (TP, RF, IP)only the IP segment
Requirementevery participating object on a Secure deviceSecure IP router / interface and client
When?outdoor bus section, alarm, access control, metering datawhen KNX IP runs on the home LAN, or with routing

Device certificate (FDSK) and project password: what to keep?

Every KNX Secure device comes with a factory commissioning key (FDSK, Factory Default Setup Key), printed on the device and usually on an enclosed card as a QR code. ETS reads it and, during the first secure commissioning, issues its own device keys, known afterwards only to the device and ETS. With Secure devices, ETS requires a project password.

  1. Collect and keep the certificate cards (or receive them from us at handover) – they are needed again if a device is reset to factory state.
  2. Store the ETS project and the project password separately; without the password the project cannot be opened.
  3. After replacement or theft: according to Siemens, if a Secure-mode IP router or IP interface is stolen or replaced, secure commissioning must be repeated for the other devices on the network so that the old keys become worthless.

Remote access: VPN, not an open port

  • VPN on the router or the visualisation server: the phone or laptop joins the home network through an encrypted tunnel and only reaches KNX from there.
  • Manufacturer remote service: several visualisation servers offer their own encrypted cloud connection; updates and access management are what matter here.
  • No port forwarding: never open the KNX IP port (3671) to the internet.
  • Separate network: manufacturers recommend a separate network (or VLAN) for KNX IP communication, strong passwords, and documented network settings handed over by the installer.
Remote access has to be planned together with the home router and the internet provider. We set it up at commissioning and hand over the access rights in the owner’s name.

Secure KNX visualisation

KNX visualisation (wall panel, server and phone app) connects to the bus via tunnelling or routing. If the house uses Secure group addresses, the visualisation must know the keys as well; so we only choose visualisations that support KNX Secure, and pass on the keys from ETS the way the manufacturer specifies.

  • Users and rights: separate accounts for family members, read-only rights for guests or cleaners.
  • Updates: the visualisation server and the router software must be updated regularly.
  • Log: it helps if the server logs logins.

Keep manual control

One of KNX’s main strengths is that it has no central brain: the push-button sends its telegram directly to the switch actuator. This must be preserved in the design:

  • Wall push-buttons in every room – the app is a convenience, not the only user interface.
  • Logic on the bus: important functions (lighting, blinds, heating set points) should not run on the visualisation server or in the cloud.
  • Manual switching in the board: many actuators have manual controls to switch a circuit even when something fails.
  • Safety functions: wind alarm for blinds should come locally from the weather station, not from the internet.

If the internet goes down, at most remote access stops; the house keeps working. The same principle applies to alarms and cameras: see alarm systems and CCTV.

What do the Cyber Resilience Act and RED mean for KNX?

Regulation (EU) 2024/2847 (Cyber Resilience Act, CRA) places obligations on manufacturers of products with digital elements. It applies generally from 11 December 2027; manufacturers’ obligation to report actively exploited vulnerabilities (Article 14) applies from 11 September 2026, and Chapter IV on conformity assessment bodies from 11 June 2026 (Article 71).

  • Manufacturer requirements (Annex I): placed on the market without known exploitable vulnerabilities and with a secure-by-default configuration; with security updates, access protection, encryption and a reduced attack surface.
  • Support period: vulnerability handling for at least five years, unless the product is expected to be in use for less (Article 13(8)).
  • Important products: Annex III, Class I lists smart home products with security functionalities, such as smart door locks, security cameras and alarm systems.

The supplement to the Radio Equipment Directive (RED), Delegated Regulation (EU) 2022/30, makes network-protection, privacy and anti-fraud essential requirements mandatory for internet-connected radio equipment (for example Wi-Fi or RF devices); since the (EU) 2023/2444 amendment it applies from 1 August 2025. The references of the harmonised standards EN 18031-1, -2 and -3:2024 were published with restrictions by Implementing Decision (EU) 2025/138: for example, if the standard allows a user to operate a device without any password, this does not give presumption of conformity.

These rules bind manufacturers first of all. As an owner, ask the installer to fit devices for which the manufacturer commits to updates and a support period, and make sure updates are taken care of after handover. We speak English.

Related: KNX smart home · Smart home installation · KNX or a wireless smart home? · Low-voltage systems

Frequently asked questions

What is the difference between KNX Data Secure and KNX IP Secure?

Data Secure encrypts and authenticates group telegrams end to end, on every medium. IP Secure protects KNX traffic on the IP network (routing, tunnelling, ETS connection). The two can be used together.

Does a family house need KNX Secure?

It is recommended if KNX IP runs on the shared home network, there is an outdoor bus section, or alarm and access control are part of the system. For a small, closed TP system, physical protection and VPN remote access matter most.

How do I access KNX securely from outside?

Through a VPN to the router or the visualisation server, or with the manufacturer’s encrypted remote service. Never open the KNX IP port to the internet.

What is the FDSK?

The factory commissioning key (Factory Default Setup Key) of a KNX Secure device, printed as a QR code on the device and on a card. ETS uses it to start secure commissioning and then issues its own keys.

What is the difference between tunnelling and routing?

Tunnelling is a point-to-point connection between a client (ETS, visualisation) and the IP interface or router. Routing forwards KNX telegrams as multicast over the IP network, which IP routers use to link lines.

What does the Cyber Resilience Act mean for KNX devices?

From 11 December 2027 manufacturers must place products on the market that are secure by default, updatable and supported for at least five years. Installers and owners should choose supported devices and install updates.

Let’s talk about your project.

Tell us what you are planning and we will get back to you within a few days.

Get in touch

Cookie settings

Choose what you consent to. We remember your choice for 6 months; change it any time via “Cookie settings” in the footer.

Privacy notice