Remote access

With this function, devices in the network in which the controller is located can be addressed via a TCP tunnel. Using an external IP gateway located in the same network, KNX devices can be programmed via ETS. Communication takes place via the integrated VPN, no port forwarding is required.

Optionally, the controller's internal IP gateway can also be used (from image version 3.0 onwards).

Important: For programming KNX devices via the internal IP gateway with ETS 6.1 or newer, the image version of the controller must be at least 4.011. The internal IP gateway is third-party software, on whose development we have no influence. We also have no influence on software changes to the ETS programming software, so the function cannot be guaranteed with future updates of the ETS software.

In addition, the internal IP gateway only supports the standard APDU length of 15. Devices whose download requires longer telegrams — in particular the secure commissioning of KNX Data Secure devices — cannot be programmed via it; in this case the ETS reports "Insufficient APDU length (limited to 15 by the capabilities of the bus interface)". For such devices, either secure commissioning must be disabled in the ETS or an external IP gateway must be used.

Remote programming via VPN can be activated through the Controller - Remote programming menu.

In order to use remote programming, the connection to the controller must first be established via VPN; this is not possible over the local network.

With the option "Enable KNX remote access" and a click on Connect, remote programming is activated. Two interfaces can be used here:

Onboard: For this, the controller's IP gateway must be activated. See Web interface of the controller. Important: If the IP gateway has been activated, the KNX interface function block must also be switched to IP gateway.
External: An external IP gateway is used here. The IP address of the gateway must be specified; it must be located in the same network as the controller.

In order to establish a connection via ETS, a connection to the local computer must be created in ETS:

The IP address must be set to "127.0.0.1" and NAT mode must be activated. To prevent automatic switching between connections, the option "Use for this project" should be activated. KNX devices can now be programmed via this connection.

Important: For programming via the internal IP gateway (onboard), the image version of the controller must be at least 4.011. With older image versions, KNX devices can only be programmed via an external IP gateway.

Please note:

In the Studio, remote programming should be activated first before ETS is started or the interface is created. First select the VPN connection and connect to the controller. Then call up the Controller - Remote programming menu.
When remote programming is started, the main window is disabled. This is necessary because KNX remote programming is not possible in parallel with changes to the project.
This function should only be used when you are not in the same network as the controller.
If ETS displays a dialog for changing the physical address, it must be confirmed with "keep".
With a slow Internet connection, the ETS programming may abort. If ETS constantly aborts during the download, this may be due to the Internet connection. Connections over mobile networks (tethering/hotspot) in particular are not always stable. In rare cases, restarting ETS can help.

TCP Tunnel

With this function, a device in the remote network in which the controller is located is connected to the local network. A tunnel is established from the remote network to the local computer. For example, to access the web interface of a device, create a connection with the IP address and port 80.

The local port can be chosen freely; it just must not be occupied by another application. In the example above, local port 8080 is used instead of 80. Therefore, http://127.0.0.1:8080 must be entered in the browser because this does not correspond to the standard port for http.

Tip: Most browsers automatically switch to https if it has not been specified explicitly; if the device only supports http, the connection does not work. Therefore, http:// or https:// should always be specified in the browser.

For easier access, you can use the two buttons HTTP and HTTPS; these open the standard browser with the corresponding URLs.

Important: Please note the disclaimer when using the VPN service.