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

EnOcean⇄WBoxgateway⇄MQTTOne WBox gateway · native conversion · no PC

The protocols

EnOcean

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

EnOcean driver →

MQTT

MQTT is the lightweight publish/subscribe protocol used by IoT devices and cloud brokers.

MQTT driver →

Typical use case

Instrumenting a building — or a whole portfolio — with wireless comfort sensors that report to a cloud platform: EnOcean probes are installed without wiring or batteries to replace, and every reading lands as structured messages on your MQTT broker, ready for dashboards, analytics or an energy-management platform.

Example deployment

Typical scenario EnOcean sensor telemetry to the cloud EnOcean sensors (CO₂, temperature, humidity) equip meeting rooms with zero cabling. The WBox decodes the radio telegrams (EEP profiles) and publishes each reading as JSON to an MQTT broker — energy dashboard or IoT platform, on-site or in the cloud. Technical documentation →

How the WBox bridges EnOcean and MQTT

The WBox decodes incoming EnOcean telegrams by EEP profile and publishes each value as JSON on an MQTT topic of your naming — per site, per floor, per sensor. The connection to the broker is a standard client with TLS and QoS; on-gateway logic can filter or aggregate before publishing. Sensor profiles are transmit-only, so the pipeline is publish-oriented: from the radio sensors to your platform.

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).
  • MQTT — MQTT imposes no point limit — topics scale with your broker and network.

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 MQTT?

EnOcean is battery-free wireless (energy harvesting) and MQTT is the lightweight IoT publish/subscribe protocol. A single WBox gateway runs the EnOcean and MQTT drivers, speaks both protocols at once and maps the data points between them — no PC, no middleware, no cloud dependency.

Is the EnOcean ⇄ MQTT bridge bidirectional?

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

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

No. The EnOcean and MQTT 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 MQTT driver licences. The online configurator recommends the right model from your interfaces and point count.

What you need

One WBox gateway with these two driver licences:

EnOcean EnOcean Driver licence 100.00 CHF MQTT MQTT Driver licence 100.00 CHF

Route EnOcean MQTT on your project

Find the right WBox gateway for your installation, or get in touch to validate your case.

Configure my gateway

Related routes

← All routes