Supported recorders › Windows and macOS
Windows and macOS
A Windows or macOS computer works as the KNXSENSE bus recorder through an external KNX/IP gateway.

How the recorder works.
The KNXSENSE recorder is installed on the computer as a background service: a scheduled task on Windows and a LaunchDaemon on macOS. It starts with the computer and runs without anyone logging in, so you can keep using the computer normally for other work.
The recorder reads the bus and never writes to it. It opens the connection outbound from the site, so no open ports, VPN or static IP address are needed. It also works behind a shared carrier IP address.
Recording requires the computer to be powered on continuously and the site to have an internet connection.
- Specifications
- Connection to the KNX bus
- External KNX/IP gateway
- Operating system
- Windows 10 or 11 (64-bit)
macOS 11 or later - Installation
- Background service: scheduled task
or LaunchDaemon - Network interface
- Ethernet (recommended) or Wi-Fi
- ETS tunnel slots
- Only when tunnelling
KNXSENSE-compatible models
- Windows 10 (64-bit)
- Windows 11 (64-bit)
- macOS 11 or later
How telegrams reach the recording.
The computer 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 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 computer sees through the site’s KNX/IP gateways is recorded around the clock, to the millisecond, on our secure servers — even when you are not on site.
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.
Remote ETS access through the interface, no VPN.
The connection is ETS tunnelling that runs through KNXSENSE. You open it in the user interface, and ETS then connects to the site’s KNX bus.
The recorder never takes the interface’s last free tunnel. If the slots run out, it releases its own slot and reconnects as soon as one frees up.
When the interface offers multicast routing, the recorder uses it and reserves no tunnel slots at all.
Remote access is included in the KNXSENSE monthly fee. No separate portal, licence, port forwarding or VPN is needed.
Setting up your computer as the recorder.
You choose your operating system and get a ready-made command. On Windows you run it in PowerShell, on macOS in Terminal, in both cases with administrator rights. The command contains a one-time install code that is valid for one hour.
The installer downloads its own Python interpreter from python.org to the computer and verifies its checksum and the publisher’s signature. No inbound ports are opened on the computer.
The installer disables sleep mode on mains power so the recording has no gaps. The computer must be on the same local network as the KNX/IP gateway, preferably wired, and outbound HTTPS must be allowed.
- Import your ETS projectNames and structure from the project into KNXSENSE
- Choose your operating systemWindows or macOS
- Run the ready-made commandA one-time code, and the installer does the rest
- Recording is runningThe first telegram from the site’s bus confirms the connection
Setup is a one-off job. When updates to the recorder are released, they are installed on the computer automatically. Updating requires no action from you and no visit to the site.
Other supported recorders.
You can run KNXSENSE bus recording on these devices too. Compare all →