Knowledge for Planning

Comparing Wireless Standards

Which wireless standard is right for which measurement task? This question is usually asked too soon. First, you need to determine what is being measured, how many measurement points there are, where they get their power from, and who will maintain the system in ten years—the standard follows from these factors, not the other way around.

How EnOcean Works in BuildingsWhich data path is best suited for this
868.3 MHzEnOcean in Europe
2.4 GHzZigbee and Bluetooth LE
1%Permitted transmission time per hour in the 868 MHz band
4 bytesTypical payload of a measurement telegram

An Overview of the Four

What Sets Them Apart

There are four wireless technologies used in building sensor systems: EnOcean, Zigbee, LoRaWAN, and Bluetooth Low Energy. They differ less in data rate than in three key aspects that are important for planning: where the device gets its power, how the network is structured, and what infrastructure is required within the building.

The following table lists only the characteristics specified in the respective standards and specifications. Range in meters and battery life in years are intentionally omitted: these depend on the individual device and the building’s construction, not on the standard.

StandardBand (Europe)Network ArchitecturePower at the SensorAdditional factors in the building
EnOcean868.3 MHzStar: Sensor transmits, receivers listenEnergy harvesting possible (light, motion, heat); each device also has a battery or power supplyOne receiver per zone, one gateway per floor
Zigbee2.4 GHz (sometimes 868 MHz)Mesh network; mains-powered devices act as relaysBattery; mains-powered nodes act as routersCoordinator, plus enough permanently powered nodes for the network
LoRaWAN868 MHzStar topology via gateways, large radio cellsBattery, very energy-efficientOne gateway per area and a network server that manages the devices
Bluetooth LE2.4 GHzStar or mesh network (Bluetooth Mesh)Battery, usually a coin cellAccess points or users’ phones as receivers
Two frequency bands, two environments. Below 1 GHz lies the SRD band from 863 to 870 MHz: it is shared with other building systems, and transmissions are permitted only a fraction of the time. At 2.4 GHz, the band shares space with Wi-Fi and Bluetooth—this is manageable but must be factored into channel planning, especially in densely equipped office spaces.

What the Decision Really Depends On

Three Questions to Ask Before Choosing a Standard

The choice is rarely based on radio technology. It comes down to three questions that can be answered before a single data sheet is even on the table.

1. EnergySpecify per device, not per standardEnergy-autonomous devices are not a feature of a wireless standard, but rather a feature of a device. Our own product line includes both types: sensors with a solar cell and a backup battery, devices powered solely by batteries, and those powered by an AC adapter or PoE. For planning purposes, it is therefore necessary to specify for each device group where the power comes from—and to include battery replacement as a maintenance service in the request for proposal.
2. TopologyStar or Mesh?A mesh network requires enough nodes with continuous power supply to relay data; if one fails, the network finds a new path—this is robust but harder to predict. A star network is less exciting but more predictable: You can calculate how many receivers a floor needs before making a purchase.
3. OperationWho manages the network?LoRaWAN requires a network server that manages devices, keys, and data rates—either in-house or as a service. Zigbee requires a coordinator and maintenance of the mesh. If you don’t want to operate either, you’re better off with one gateway per floor that transmits the data directly to the building automation system.

What Each Standard Is Designed For

Typical Applications

The four methods were designed for different tasks. This explains why they differ so significantly in terms of energy consumption, topology, and infrastructure—and it helps determine which method you’ll encounter in which project.

EnOcean is tailored for multiple measurement points within a single floor: short, infrequent telegrams, devices without their own network connection, and a design that can be calculated before purchase. Indoor air quality, occupancy, lighting, and windows in office, school, and administrative buildings are its core applications. The data is transmitted to the building management system via one gateway per floor.

LoRaWAN is used where measurement points are widely spaced: properties with multiple buildings, outdoor facilities, and meters in remote utility rooms. A single radio cell covers an entire area, but this requires a network server and its operation.

Zigbee is widely used in residential and small-scale properties, particularly for lighting and actuators, where there are already many devices with a constant power supply that support the mesh network. Bluetooth LE is ideal in scenarios where the user’s phone is part of the solution: reserving workstations via an app, indoor wayfinding, and devices that are set up on-site using a phone.

In large-scale projects, these worlds intersect anyway. The integration doesn’t happen over the radio link, but rather behind the scenes—in the MQTT broker or in the building automation system.

The standard is not the interface. The control system cannot see which wireless technology is used by the sensor. It sees what the gateway provides—MQTT, BACnet, KNX, or Modbus. This decision is independent of the wireless technology and is often the more important one.

What this means for your request for proposals

8 points
  • Specify the wireless standard, not the brand: “EnOcean according to ISO/IEC 14543-3-10” instead of a manufacturer’s name.
  • Specify the device profile as well (for EnOcean, this is the EEP); otherwise, interchangeability cannot be guaranteed.
  • Specify the frequency for the target market: 868.3 MHz applies to Europe; other markets require different variants.
  • Specify the power source for each device group: solar cell, battery, or power supply—and who is responsible for replacing it.
  • List the infrastructure as a separate item: receiver, gateway, network connection, and power supply.
  • For mesh networks, additionally specify how many permanently powered nodes are to be provided and who maintains the network.
  • For LoRaWAN, specify the network server: in-house operation or a service, and who owns the keys.
  • Describe the data transfer to the building automation system separately from the wireless standard.
One gateway per floorVL-700 BASEUp to 32 receivers and 500 sensors; data output in JSON, BACnet, KNX, or Modbus.View →The Wireless ReceiverEnoDisc®Monitors sensor telegrams; connects via RJ45 or LSA; powered via PoE.View →19 devices with filterAll SensorsMeasured variable, power supply, EEP, and part number side by side—as a list or as a CSV file.View →
Status and Sources

Information current as of September 16, 2026. Regulatory information has been compiled to the best of our knowledge and does not constitute legal advice. The text of the currently applicable version is always authoritative.

  • ISO/IEC 14543-3-10:2020, Information technology – Home electronic systems, Part 3-10: Wireless short-packet (WSP) protocol – the standard behind EnOcean.
  • ETSI EN 300 220, Short-Range Devices in the 863–870 MHz Band: Transmission Time Limits and Channel Access.
  • IEEE 802.15.4-2020: the wireless layer on which Zigbee and Thread are based.
  • LoRa Alliance, LoRaWAN Specification, and Regional Parameters: Network deployment via gateways and network servers.
  • Bluetooth SIG, Core Specification, and Mesh Profile: star and mesh operation at 2.4 GHz.
  • Our own planning parameters (one receiver per area, one gateway per floor) from our projects; these are detailed on the “Technical Information” page.

Would you like us to run the numbers for your building?

Send us the floor plan, dimensions, and target system. You’ll receive a recommendation for the number of units, a list of part numbers, and a quote.

Request a Quote Back to Technical Information