Log in
EN
Start trial
How it worksRemote accessBenefitsMonitorAI integrationTimelineChartsProjectSupported loggersNewsPricingFAQLog in

KNXSENSE › Supported loggers

Supported loggers.

KNXSENSE is compatible with four different types of logger.

The service works the same way whichever device you choose.

A

logger in a KNX system component

For example a visualisation, logic or remote access device connected to the KNX bus.

The logger is installed on the device as separate software, and it has no effect on anything else the device does.

Telegrams from the bus are logged in the device’s own storage first and sent on to the KNXSENSE server from there. An outage between the logger and the server therefore leaves no gap in the recording.

B

logger on a computer

A Raspberry Pi, or a Windows or macOS computer, on the site’s local network.

The logger is installed on the computer as separate software, and it reads the telegram traffic on the bus through any external KNX/IP gateway.

Telegrams are logged in the computer’s own storage first and sent on to the KNXSENSE server from there. An outage between the logger and the server therefore leaves no gap in the recording.

C

the device’s own remote access

For example a Gira S1 or another device that is connected to the KNX bus and uses the manufacturer’s own secure remote access.

No logger is installed on the device; KNXSENSE reads the telegram traffic on the bus directly over that connection.

There is no local storage, so an outage between the site and the server leaves a gap that is documented in the recording.

D

the site’s VPN connection

The site’s router, working as an OpenVPN or WireGuard server.

No device, logger or software is installed on site. KNXSENSE connects to the VPN server on the router and reads the telegram traffic on the bus through any KNX/IP gateway.

There is no local storage, so an outage between the site and the server leaves a gap that is documented in the recording.

DeviceTypeBus connectionLogging coverageReserves a tunnel slot?Tunnel slots on the deviceRemote ETS accessLogger updates
Gira S1GiraCIntegrated KNX bus couplerOwn line and what is routed to itNone reserved3Via KNXSENSENothing to update
Wiser for KNXSchneider ElectricAIntegrated KNX bus couplerOwn line and what is routed to itNone reserved, Via KNXSENSEAutomatic
ABB APP-Control ServerABBAIntegrated KNX bus couplerOwn line and what is routed to itOne reserved10Via KNXSENSEAutomatic
Busch-Jaeger APP-Control ServerBusch-JaegerAIntegrated KNX bus couplerOwn line and what is routed to itOne reserved10Via KNXSENSEAutomatic
spaceLYnkSchneider ElectricAIntegrated KNX bus couplerOwn line and what is routed to itNone reserved, Via KNXSENSEAutomatic
LogicMachineEmbedded SystemsAIntegrated KNX bus couplerOwn line and what is routed to itNone reserved, Via KNXSENSEAutomatic
xxterxxter B.V.AIntegrated KNX bus couplerOwn line and what is routed to itOne reserved10Via KNXSENSEAutomatic
1Home Server KNX Pro1HomeAIntegrated KNX bus couplerOwn line and what is routed to itNone reserved4Via the device’s own channelManual, on the device
Elsner KNX Matter ServerElsner ElektronikAIntegrated KNX bus couplerOwn line and what is routed to itNone reserved4Via the device’s own channelManual, on the device
OpenVPN and WireGuard+ KNX/IP gatewayDExternal KNX/IP gatewayUp to 16 KNX/IP gatewaysOne reserved per gateway, Via KNXSENSENothing to update
Windows and macOS+ KNX/IP gatewayBExternal KNX/IP gatewayUp to 16 KNX/IP gatewaysOnly when tunnelling, Via KNXSENSEAutomatic
Raspberry Pi+ KNX/IP gatewayBExternal KNX/IP gatewayUp to 16 KNX/IP gatewaysOnly when tunnelling, Via KNXSENSEAutomatic