Skip to main content

wM-Bus/OMS Radio Protocol

As long as the Node is not paired with an energieleser.bridge, it sends each assigned port as its own wM-Bus meter: in C1 mode (frame format A) on 868.95 MHz, encrypted with OMS security mode 5 (AES-128-CBC). This page is for anyone adding the Node to their own wM-Bus receiver, for example another manufacturer's gateway. How to assign the ports with the button is described under Pairing with an External Device.

Applies to Node firmware 1.6.1.

When does the Node send wM-Bus?​

Node stateWhat it sends
No port assignedOnly a pairing signal for the Bridge, no wM-Bus telegram
Ports assigned with the button, not paired with the BridgeOne wM-Bus/OMS telegram per assigned port
Paired with the BridgeNo more wM-Bus, but the Bridge's proprietary telemetry protocol

As soon as the Node is paired with a Bridge, wM-Bus operation stops. To return to wM-Bus operation, reset the Node (hold the button for 10 seconds) and assign the ports again with the button.

Radio parameters​

PropertyValue
ModeC1 (meter → receiver), transmit only
Frame formatA
Frequency868.95 MHz
Data rate100 kcps, 2-FSK
Transmit powerup to +14 dBm
C field0x44 (SND-NR)
Transmit interval5 minutes on battery, 1 minute on USB-C power
Telegrams per interval1 per assigned port

The Node does not receive wM-Bus commands from external devices. Bidirectional modes (C2, T2, S2) and the T1 and S1 modes are not supported.

Addressing​

Each port appears as its own meter with its own address:

FieldContent
Manufacturer (M field)Bytes 0xAA 0x55 (provisional value, will change to a registered code)
Identification number (A field)8 BCD digits: the first 7 digits are the Node ID as a decimal number (its last 7 digits), the last digit is the port (1–4)
Version0x18
Device typeGas 0x03, water 0x07, electricity 0x02, heat 0x04

Example: the Node with ID DDA151 (decimal 14524753) sends port 3 under identification number 45247533.

Encryption​

PropertyValue
Security modeOMS mode 5, AES-128-CBC
KeyThe AES key on your Node, the same for all four ports
IVPer OMS mode 5: manufacturer, identification number, version, device type and 8 × access number
Check bytesThe decrypted content starts with 0x2F 0x2F
Additional layersNone (no ELL, no AFL, no key derivation)

The access number increases by one per port with every telegram.

Telegram structure and data records​

Gas, water and electricity via pulse send a short telegram (CI 0x7A, 31 bytes, one encrypted block). Electricity via TTL and heat send a long telegram (CI 0x72) containing only the values the meter actually provides.

Meter typeCIData records (DIF VIF)Content
Gas (pulse)0x7A0C 13Meter reading, 8 BCD digits
Water (pulse, sensor or TTL reading head)0x7A0C 13Meter reading, 8 BCD digits
Electricity (pulse)0x7A04 03Meter reading, 32 bit
Electricity (TTL)0x7204 03Import in Wh
04 81 3CExport in 0.01 Wh
04 2BPower in W
Heat (TTL, port 1 or 2)0x7204 03Energy in Wh
04 13Volume in l
04 2BPower in W
04 3BFlow in l/h
02 5AFlow temperature in 0.1 °C
02 5EReturn temperature in 0.1 °C

A port with a TTL reading head only sends after it has read the meter successfully once. A port without an assignment never sends.

Unit for pulse meters

Up to and including firmware 1.6.1, for gas, water and electricity via pulse the Node sends the reading in whole m³ or whole kWh, although the VIF states litres (0x13) or Wh (0x03). Multiply the value by 1000 in your receiver. Electricity via TTL and heat are not affected.

Compatibility​

The telegrams follow the simplified OMS structure above. Time stamps, status messages and due-date values are not included. The Node has not yet been officially tested with other manufacturers' receivers. If you have questions, write to info@energieleser.de.