Supported recorders › OpenVPN and WireGuard
OpenVPN and WireGuard
A VPN connection lets KNXSENSE work as a bus recorder through an external KNX/IP gateway.
How the recorder works.
KNXSENSE connects to the VPN server on the site's router, so no separate devices or software need to be installed.
This also makes recording possible when the site’s own visualisation server, for example a Basalte Core, Gira HomeServer or Jung Smart Visu Server, lacks the features to work as a recorder.
The recorder only reads bus traffic and never writes to the bus. KNXSENSE automatically restricts the connection to the site’s KNX/IP gateways, and it gives no access to other devices on the local network, such as servers, surveillance cameras or network drives. Every site has its own tunnel, and sites cannot see one another.
Recording requires the VPN connection to be up continuously and the site to have an internet connection.
- Specifications
- Remote ETS access
- Via KNXSENSE
- Connection
- OpenVPN or WireGuard
- Tunnelling
- Restricted to the site’s KNX/IP gateways
- Gateways per recorder
- Up to 16
- KNX port
- 3671 (UDP), another possible
- Installed on site
- Nothing
KNXSENSE-compatible models
- OpenVPN
- WireGuard
How telegrams reach the recording.
The recorder sees the bus traffic through the site’s KNX/IP gateways.
A single recorder reads up to 16 KNX/IP gateways at once and merges their traffic into a single recording. On a large site there may be, for example, one interface per line.
Telegrams are read in real time and there is no local storage on site: an outage leaves a gap that is documented in the recording.
Telegrams never have to be routed from one line to another for recording, so traffic between the lines does not grow at all. If the same telegram is seen through two interfaces at the same time, it is recorded only once.
KNXSENSE compares the addresses it sees against your ETS project and tells you straight away which lines and devices are in the recording and which are missing.
KNX bus monitoring in your browser.
Every telegram the recorder sees through the site’s KNX/IP gateways is recorded around the clock, with timestamps, to our secure servers — including when you are not there.
Telegram-level history reaches 400 days back on a rolling window. You can browse it in your browser, on any device, without the ETS software.
ETS tunnelling through KNXSENSE.
You open the connection from the interface, and from there you program the site in ETS as if you were on site.
Recording reserves one ETS tunnel slot on every gateway it reads and holds on to it. Leave one free slot on the gateway for remote ETS access.
Remote access is included in the KNXSENSE monthly fee. No separate portal, licence or port forwarding is needed.
Setting up bus recording over a VPN connection.
You add the site’s OpenVPN profile or WireGuard settings to KNXSENSE and enter the KNX/IP gateway address, or let KNXSENSE find it for you. Once the gateway is known, the connection is restricted to it.
The site needs a KNX/IP gateway and the router needs an OpenVPN or WireGuard server. Because KNXSENSE connects inward to the site, the server has to be reachable from the internet, and the site needs a static IP address or a DDNS name. Behind a shared carrier IP address this recorder does not work. The guided setup walks through the prerequisites and tells you at once if any of them is missing.
- Add the VPN profileOpenVPN profile or WireGuard settings
- Import your ETS projectNames and structure from the project into KNXSENSE
- Recording is runningThe first telegram from the site’s bus confirms the connection
Setup is a one-off job. No software is installed on site, so KNXSENSE updates require no action from you and no visit to the site.
Other supported recorders.
These devices are compatible with KNXSENSE too. Compare all →