EnOcean is an energy harvesting wireless technology used primarily in building automation. EnOcean devices (sensors, switches, actuators) communicate using ultra-low power radio telegrams, often powered by solar cells, motion, or temperature differences — requiring no batteries. This makes EnOcean ideal for retrofitting buildings with wireless sensors and switches.
The Weble universal gateway EnOcean driver connects to an EnOcean USB receiver (e.g. USB 300/310) via serial port and listens for radio telegrams from nearby devices. Each device is identified by its unique EnOcean ID and its data is decoded using EEP (EnOcean Equipment Profiles) — a standardized set of profiles that define how each device type encodes its data.
The driver supports a large number of EEP profiles, covering:
- Temperature sensors (A5-02-xx)
- Humidity sensors (A5-04-xx)
- Light sensors (A5-06-xx)
- Occupancy / motion sensors (A5-07-xx, A5-08-xx)
- CO2 / VOC / air quality sensors (A5-09-xx)
- Room controllers / thermostats (A5-10-xx)
- HVAC valve actuators (A5-20-xx)
- Energy meters (A5-12-xx)
- Weather stations (A5-13-xx)
- Window/door contacts (D5-00-xx)
- Rocker switches (F6-02-xx, F6-03-xx)
- Electronic switches and dimmers (D2-01-xx)
- Smart plugs and metering plugs (D2-01-xx)
- And many more (D2-xx-xx series for VLD telegrams)
¶ 1. Getting started
¶ 1.1 Prerequisites
An EnOcean USB receiver must be connected to the gateway. Common receivers include the EnOcean USB 300 (868 MHz for Europe) or USB 310 (902 MHz for North America).
¶ 1.2 Gateway configuration
Create a new gateway and select the Enocean driver. Configure:
- Serial Port: select the EnOcean USB receiver from the auto-complete list. Using the unique ID is recommended.
- Only values: if enabled (default), the addresses only expose the decoded values. When disabled, additional raw telegram data is included.
¶ 1.3 Scanning for devices
Once the gateway is started, use the context menu and select Enocean methods > Scan devices to start listening for radio telegrams. The driver will discover any EnOcean device that transmits within range.
The scan shows progress and the number of devices found. Once complete, discovered devices are automatically created as addresses.
¶ 1.4 Device addresses
When a device is discovered, the driver creates a tree of addresses:
%enocean:<deviceId>— the main device address (EnOcean ID in hexadecimal)%enocean:<deviceId>/<eep>— the EEP profile node (e.g.a5-04-01for temperature/humidity)%enocean:<deviceId>/<eep>/<property>=<value>— decoded property values
For example, a temperature/humidity sensor might create:
%enocean:AABBCCDD
%enocean:AABBCCDD/a5-04-01
%enocean:AABBCCDD/a5-04-01/temperature
%enocean:AABBCCDD/a5-04-01/humidity
These addresses are routable and loggable like any other gateway address, so sensor data can be forwarded to BACnet, Modbus, MQTT, or any other protocol.
Note: Addresses are created automatically when devices are discovered. Manual address insertion is not available.
¶ 2. Gateway parameters
| Label | JSON Key | Description |
|---|---|---|
| Name | name | A descriptive name for this EnOcean gateway instance. |
| Cluster ID | cluster | Cluster identifier (integer). Use 0 for single-gateway setups. |
| Description | description | Optional description for this gateway. |
| Serial Port | serialPort | The serial interface of the EnOcean USB receiver. Auto-complete lists detected USB/serial interfaces. Use unique ID for stability. |
| Only values | onlyValues | If enabled (default), simplifies addresses to only expose decoded values. When disabled, raw telegram data is also available. |
¶ 2.1 Gateway JSON example
{
"serialPort": "/dev/serial/by-id/usb-EnOcean_GmbH_EnOcean_USB_300-if00",
"onlyValues": true
}
¶ 3. Addresses
¶ 3.1 Address format
EnOcean addresses use the prefix %enocean: followed by the device ID (hexadecimal) and the data path:
%enocean:AABBCCDD— main device address%enocean:AABBCCDD/a5-02-05— EEP profile (temperature sensor, range 0-40°C)%enocean:AABBCCDD/a5-02-05/temperature— decoded temperature value
¶ 3.2 Address parameters
| Label | JSON Key | Description |
|---|---|---|
| Name | name | The EnOcean address (auto-generated from device ID and EEP). |
| Description | description | Optional description. |
| Child paths | childPaths | Comma-separated list of property path names for organizing the address tree. Visible on device-level addresses only. Editable in the grid. |
¶ 3.3 EnOcean Equipment Profiles (EEP)
The EEP defines how a device's radio telegram is decoded. The format is RORG-FUNC-TYPE:
- RORG — radio telegram type:
F6(RPS, rocker switches),D5(1BS, single contact),A5(4BS, 4-byte sensors),D2(VLD, variable length) - FUNC — function group (e.g.
02= temperature,04= humidity,10= room controller) - TYPE — specific device type within the function group
Common EEP profiles:
| EEP | Device type |
|---|---|
| A5-02-xx | Temperature sensors (various ranges) |
| A5-04-01 | Temperature and humidity sensor (range 0-40°C, 0-100%) |
| A5-06-xx | Light sensors |
| A5-07-01 | Occupancy sensor |
| A5-08-01 | Light, temperature, and occupancy sensor |
| A5-09-04 | CO2 sensor |
| A5-09-05 | VOC sensor |
| A5-10-xx | Room controllers (temperature + setpoint + fan + occupancy) |
| A5-12-01 | Electricity meter |
| A5-13-01 | Weather station (temperature, wind, rain, sun) |
| A5-20-01 | HVAC valve actuator |
| D2-01-xx | Electronic switches and dimmers |
| D5-00-01 | Window/door contact |
| F6-02-01 | Rocker switch (2-channel) |
The full list of supported EEPs contains over 200 profiles covering virtually all EnOcean device types.
¶ 3.4 Address properties
| Property | Value |
|---|---|
| Readable | No (values are pushed by the device via radio) |
| Writable | Yes (for actuators that accept commands) |
| Routable | Yes |
| Loggable | Yes |