EnOcean ⇄ KNX gateway

Need to connect EnOcean and KNX? The Weble WBox routes EnOcean KNX natively: one gateway speaks both protocols and maps data points in real time — no PC, no middleware, no cloud dependency.

The protocols

EnOcean

EnOcean connects self-powered radio sensors and switches (solar, motion) — ideal for retrofits, with no wiring and no batteries.

EnOcean driver →

KNX

KNX is the worldwide standard for home and building control, running over twisted-pair, IP or RF.

KNX driver →

Typical use case

Extending a KNX installation into rooms where cabling is impractical — a heritage façade, glass partitions, a rented floor: battery-free EnOcean sensors are placed in minutes. Window contacts, wall switches and temperature probes then feed the existing KNX heating and lighting logic as if they were wired bus devices.

Example deployment

Typical scenario Battery-free sensors in a KNX installation In a retrofit, pulling bus cable to every office is expensive. Self-powered EnOcean sensors (temperature, occupancy, window contacts, rocker switches) reach the WBox's USB receiver by radio, and the WBox publishes them on the KNX bus — the existing control logic uses them like any KNX point. Technical documentation →

How the WBox bridges EnOcean and KNX

An EnOcean USB gateway (USB 300, 868 MHz) on the WBox receives the radio telegrams; the driver decodes them by EEP profile — F6-02 rocker switches, D5-00 window contacts, A5-02 temperature probes. Each decoded value is routed to a KNX group address with the matching DPT, so a rocker press switches a KNX light and an open window lowers the heating setpoint. Sensor profiles are transmit-only: the main data flow runs from the radio sensors into the KNX bus.

Example mapping

Typical radio-to-bus bindings:

EEP A5-02-05 temperature probe → KNX 2/1/14 (DPT 9.001, °C)
EEP D5-00-01 window contact → KNX 3/0/1 (DPT 1.019)
EEP F6-02-01 rocker switch → KNX 1/0/3 (DPT 1.001)

Capacity & limits

EnOcean — EnOcean is radio — no bus limit; each device is identified by its unique ID and decoded via EEP profiles, through an EnOcean USB receiver (USB 300/310).
KNX — KNX exposes the installation's group objects; a TP line carries up to 64 bus devices, extended through lines, areas and KNXnet/IP.

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 EnOcean and KNX?

EnOcean is battery-free wireless (energy harvesting) and KNX is the building field bus (lighting, blinds, HVAC). A single WBox gateway runs the EnOcean and KNX drivers, speaks both protocols at once and maps the data points between them — no PC, no middleware, no cloud dependency.

Is the EnOcean ⇄ KNX bridge bidirectional?

Yes. The WBox reads and writes on both sides: a value or command on the EnOcean side propagates to KNX, and vice-versa.

Do I need a PC, a PLC or proprietary hardware?

No. The EnOcean and KNX 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 EnOcean and KNX 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.