Know-how for integration · MQTT

EnOcean MQTT Gateway

The VL-700 BASE receives the radio telegrams of up to 500 EnOcean sensors, decodes the device profiles and publishes every reading as JSON to your MQTT broker – ready to read, with no EEP knowledge needed on the receiving side.

Request a quote See the JSON example

500sensors per gateway

32radio receivers per gateway

4MQTT brokers in parallel

AES-128with EnOcean Secure

0 €fee per sensor

How a reading gets to the broker

Four steps

1Measure and transmitThe sensor transmits according to EnOcean (ISO/IEC 14543-3-10) at 868.3 MHz, optionally encrypted with EnOcean Security.

2ReceiveAn EnoDisc® within range receives the telegram and forwards it via Ethernet, powered by PoE. Up to 32 receivers per gateway.

3DecodeThe VL-700 BASE decrypts Secure telegrams, reads the device profile (EEP) and converts the raw data into readings with units.

4PublishEvery telegram is sent as a JSON object to up to four MQTT brokers at the same time – on premises or in the cloud, optionally via TLS.

What is on the topic

JSON per telegram

One JSON object per radio telegram. If a device measures several values, they appear together in the “functions” list.

{
  "eepId": "47D10901",
  "deviceId": "0421A3F7",
  "friendlyId": "Room-201-CO2",
  "timestamp": 1790935200000,
  "dbm": -71,
  "functions": [
    { "key": "CO2",         "range": "0 to 5.000 ppm", "value": 612 },
    { "key": "Humidity",    "range": "0 to 100 %",     "value": 44 },
    { "key": "Temperature", "range": "+10 to +35 °C",  "value": 22.4 }
  ],
  "telegramInfo": { "dbm": -71 },
  "topic": "deuta/floor2"
}

Structure as sent by the device; device ID, name and values are example values.

Field	Content
eepId	Device profile of the sensor (EnOcean Equipment Profile)
deviceId	EnOcean ID of the sensor, eight hexadecimal digits
friendlyId	the plain name assigned during set-up
timestamp	Time of reception as Unix time in milliseconds
dbm	Received signal strength in dBm
functions	List of readings: name (key), measuring range with unit (range), value (value)
topic	the topic the message was published on

Topic form	Structure	When it makes sense
Static	one fixed topic for all devices of the gateway	the standard case: one subscription is enough, devices are distinguished in the payload
Dynamic	<prefix>/<device profile>/<device ID>	when the target system should filter by topic
Custom	exactly the agreed string	when an existing topic structure at the customer has to be respected

The topic form is defined during set-up. The full field description is in the VL-700 BASE manual.

A gateway instead of a USB stick

The comparison

For one room, a USB stick with an open-source script is enough. For a building, what counts is who takes care of radio coverage, device profiles and operation.

	USB stick + script	VL-700 BASE
Reception	one receiver on the computer	up to 32 EnoDisc® across the building, via PoE
Device profiles	assign and maintain yourself	decoded in the gateway, readings with units
EnOcean Secure	the computer has to handle decryption	decrypted in the gateway (AES-128, rolling code, CMAC)
Outputs	MQTT	MQTT to up to 4 brokers, plus BACnet, Modbus TCP, KNX, OPC UA in parallel
Operation	own script, own computer	DIN-rail device operated in the browser, remote support available
Cost per sensor	none	none

Where the values go

After the broker

Anything that understands MQTT and JSON can take over the values – for example Node-RED for your own flows, Home Assistant via its MQTT integration, InfluxDB with Grafana for history, or your own software. In parallel, the same gateway can serve the building automation via BACnet, Modbus TCP or KNX.

WorkflowsNode-REDYour own flows, alarms and forwarding based on the JSON messages.

Smart buildingHome AssistantVia the MQTT integration, one sensor per reading.

HistoryInfluxDB and GrafanaStore time series and show them as a dashboard.

Building automationBACnet, Modbus TCP, KNXIn parallel from the same gateway, independently of MQTT.

Frequently asked questions

7 questions

Do I need EEP knowledge?

No. The VL-700 BASE decodes the device profiles itself; the JSON contains readings with names and units.

Which broker can I use?

Your own, for example Mosquitto on premises, or a broker in the cloud. The connection can run via TLS.

Can the gateway send to several brokers at the same time?

Yes, to up to four MQTT brokers in parallel – for example to the on-site building automation and to an analytics platform.

Is the radio data encrypted?

With EnOcean Secure, yes: the VL-700 BASE decrypts AES-128-encrypted telegrams itself before passing them on as JSON. Encrypted and unencrypted sensors can be mixed.

Which sensors are supported?

Our own EnoSense sensors and EnOcean devices from other manufacturers with the common device profiles for room sensors. We check in advance which profiles your project needs.

Is there a REST interface?

Not today; it is in preparation. Today, the values go out via MQTT, BACnet, KNX or Modbus TCP.

Are there licence fees?

No. There is no fee per sensor and no recurring cost.

Order no. 11895VL-700 BASEThe gateway: 500 sensors, 32 receivers, DIN rail, 24 V DC.View →Software on the gatewayECSSpeaks MQTT, BACnet, KNX and Modbus TCP in parallel and shows alarms in the browser.View →Know-how for planningWhich data path fitsMQTT, BACnet, KNX and Modbus TCP side by side – and when each one makes sense.View →

Status

Information as of 2 October 2026. The VL-700 BASE manual in its current version is authoritative for the field structure.

Planning EnOcean over MQTT?

Send us your floor plan, sensor list and target system – you will receive a device list with order numbers and a quote.

Request a quote Go to the download center