Need to connect KNX and OPC UA? The Weble WBox routes KNX OPC UA natively: one gateway speaks both protocols and maps data points in real time — no PC, no middleware, no cloud dependency.
The protocols
KNX
KNX is the worldwide standard for home and building control, running over twisted-pair, IP or RF.
KNX driver →OPC UA
OPC UA is the secure, platform-independent client/server standard for Industry 4.0 data exchange.
OPC UA driver →Typical use case
Industrial supervision, SCADA and MES platforms increasingly standardise on OPC UA, while the building's field level — lighting, blinds, HVAC room control — runs on KNX. Rather than a separate gateway per discipline, the WBox lifts KNX group objects straight into the OPC UA address space, so a central supervision reads and commands the building as native OPC UA nodes. On the Lombard Odier campus in Geneva, 50 WBox S485 KNX gateways route KNX — alongside BACnet and DALI — to exactly such a central OPC UA supervision.
In the field
Weble customers run this routing in production:
How the WBox bridges KNX and OPC UA
Enable the KNX and OPC UA drivers. Each KNX group object is mapped to a node in the WBox OPC UA server address space: measurements as Float nodes, switch and status objects as Boolean nodes. The supervision browses the namespace and subscribes to the values it needs; writes from OPC UA propagate back to the matching KNX group addresses. A JavaScript step can scale, clamp or combine values before they cross.
Step by step
- Connect KNX — TP via the WBox S485 KNX, or KNXnet/IP on an existing IP backbone.
- Enable the KNX and OPC UA drivers on the WBox.
- Map each KNX group object to an OPC UA node — measurements as Float, switch and status as Boolean — in the WBox server address space.
- Expose the OPC UA server endpoint
opc.tcp://wbox:4840with a security policy and certificate; your SCADA/MES browses the namespace. - Subscribe from the supervision; writes from OPC UA flow back to the KNX group addresses. Verify in the point monitor.
Example mapping
A worked example, all on one gateway:
- KNX group address
1/2/0zone temperature (DPT 9.001) → OPC UA nodens=4;s=Building.Zone2.Temp(Float) - KNX
0/1/5lighting on/off (DPT 1.001) → OPC UAns=4;s=Building.Zone2.Light(Boolean) - OPC UA write
ns=4;s=Building.Zone2.Setpoint→ KNX1/2/3setpoint
Capacity & limits
- KNX — KNX exposes the installation's group objects; a TP line carries up to 64 bus devices, extended through lines, areas and KNXnet/IP.
- OPC UA — OPC UA imposes no node limit — the address space scales with the server.
On the WBox, a driver licence enables the whole protocol — there is no artificial per-point tier to unlock. Capacity scales with the gateway model, from the compact S103 to the E413: you are bounded by the field bus, not by your licence.
Frequently asked questions
How do I connect KNX and OPC UA?
KNX is the building field bus (lighting, blinds, HVAC) and OPC UA is the industrial interoperability standard. A single WBox gateway runs the KNX and OPC UA drivers, speaks both protocols at once and maps the data points between them — no PC, no middleware, no cloud dependency.
Is the KNX ⇄ OPC UA bridge bidirectional?
Yes. The WBox reads and writes on both sides: a value or command on the KNX side propagates to OPC UA, and vice-versa.
Do I need a PC, a PLC or proprietary hardware?
No. The KNX and OPC UA drivers are licence-activated on one WBox — no gateway PC, no intermediate PLC and no proprietary hardware.
Which WBox model do I need?
Any WBox with the KNX and OPC UA driver licences. The online configurator recommends the right model from your interfaces and point count. For KNX TP, choose the WBox S485 KNX, which has the twisted-pair interface on board.
What you need
One WBox gateway with these two driver licences:
Route KNX OPC UA on your project
Find the right WBox gateway for your installation, or get in touch to validate your case.
Configure my gateway© 2026 Weble Sàrl. All rights reserved. General conditions