FAQ - Frequently Asked Questions - How to choose the right wireless technology for an IoT device

Choosing the right wireless technology is one of the most important decisions in an IoT project. It affects range, battery lifetime, data rate, latency, antenna design, certification, network costs and long-term reliability.

A good connectivity choice starts with the application, not with the module. Before selecting NB-IoT, LTE-M, LoRaWAN, Wi-Fi, Bluetooth LE or UWB, define how the device will be used, where it will operate and how often it needs to communicate.

Key technical selection criteria

Before choosing a wireless technology, evaluate:
  • required data rate
  • message size
  • transmission interval
  • battery lifetime target
  • indoor or outdoor coverage
  • >fixed or mobile use
  • latency requirements
  • local, private or public network availability
  • antenna size and placement
  • enclosure material
  • target countries or regions
  • certification requirements
  • firmware update requirements
  • >expected production lifetime
  • module availability and lifecycle
The right choice is usually a balance between range, power consumption, infrastructure, cost and integration complexity.

 

Wireless technology comparison

Technology Range Data rate Power use Mobility Best fit
NB-IoT Long Low Very low Limited Fixed sensors, meters, remote monitoring
LTE-M Long Medium Low to medium Good Asset tracking, mobile IoT, alarms
LoRaWAN Long Low Very low Limited Private sensor networks, smart buildings, agriculture
Wi-Fi Short to medium High High Limited Local connected devices, gateways, powered equipment
Bluetooth LE Short Low to medium Very low Medium Wearables, sensors, mobile-connected devices
UWB Short Medium Medium Good Indoor positioning, distance measurement, asset location

This table gives a first direction. The final choice depends on the real application, environment, power budget and network situation.


When should you use NB-IoT?

NB-IoT is suitable for low-data IoT devices that need long battery life and cellular network coverage. It is often used for fixed or mostly stationary devices that send small data packets at intervals.

Use NB-IoT for:

  • smart meters
  • environmental sensors
  • parking sensors
  • utility monitoring
  • building sensors
  • remote industrial monitoring
  • devices installed in difficult indoor locations

NB-IoT can be a good choice when the device does not move much, sends limited data and needs reliable coverage through an operator network.

Technical considerations for NB-IoT

Check:

  • operator coverage in the target region
  • supported frequency bands
  • roaming requirements
  • data payload size
  • latency tolerance
  • power-saving modes
  • antenna integration
  • certification and operator requirements

NB-IoT is usually not the best choice for applications that need continuous mobility, low latency or frequent large data transfers.


When should you use LTE-M?

LTE-M is a cellular IoT technology for devices that need mobility, wider coverage and higher data rates than NB-IoT. It is often used when the device moves between locations or needs a more responsive connection.

Use LTE-M for:

  • asset tracking
  • fleet devices
  • mobile industrial equipment
  • alarm systems
  • connected products
  • wearable or portable devices
  • devices requiring firmware updates over the air

LTE-M is often a better choice than NB-IoT when handover, mobility or more frequent communication is required.

Technical considerations for LTE-M

Check:

  • cellular coverage in all target countries
  • roaming support
  • power consumption during network registration
  • peak current during transmission
  • antenna performance
  • data usage and subscription costs
  • firmware update requirements
  • module lifecycle

LTE-M can use more power than NB-IoT in some applications, but it offers more flexibility for mobile and data-rich IoT devices.


When should you use LoRaWAN?

LoRaWAN is suitable for long-range, low-power devices that send small amounts of data. It can be used with public networks, private networks or site-specific gateway infrastructure.

Use LoRaWAN for:

  • smart agriculture
  • building monitoring
  • industrial sensor networks
  • utility monitoring
  • environmental monitoring
  • large sites with many low-power sensors
  • private IoT networks

LoRaWAN is a good choice when you need long range, low power and control over the network infrastructure.

Technical considerations for LoRaWAN

Check:

  • public network availability
  • private gateway requirements
  • number of devices
  • message frequency
  • duty-cycle limitations
  • regional frequency plan
  • gateway placement
  • antenna height and orientation
  • indoor or outdoor range

LoRaWAN is usually not suitable for high data rates, frequent large messages or applications that need guaranteed low latency.


When should you use Wi-Fi?

Wi-Fi is suitable when the device needs high data throughput and has access to local network infrastructure. It is often used in products that are mains-powered or regularly charged.

Use Wi-Fi for:

  • gateways
  • cameras
  • smart building devices
  • industrial control panels
  • local monitoring systems
  • devices with regular power supply
  • products that need high data transfer

Wi-Fi is a practical choice when the user or installation site already has a local network.

Technical considerations for Wi-Fi

Check:

  • power budget
  • network setup process
  • security requirements
  • signal strength at installation location
  • antenna placement
  • data throughput
  • coexistence with Bluetooth or other radios
  • firmware update needs

Wi-Fi is usually less suitable for battery-powered field devices that need to operate for years without maintenance.


When should you use Bluetooth LE?

Bluetooth Low Energy is suitable for short-range, low-power communication. It is often used when an IoT device communicates with a smartphone, gateway or nearby device.

Use Bluetooth LE for:

  • wearable devices
  • handheld equipment
  • sensors
  • beacons
  • mobile-connected products
  • configuration interfaces
  • short-range monitoring

Bluetooth LE is useful when low power consumption and smartphone compatibility are important.

Technical considerations for Bluetooth LE

Check:

  • required range
  • smartphone or gateway availability
  • advertising interval
  • connection interval
  • battery lifetime
  • antenna placement
  • enclosure impact
  • coexistence with Wi-Fi
  • security and pairing method

Bluetooth LE is not the right choice for long-range communication without gateways or repeaters.


When should you use UWB?

UWB is used mainly for accurate distance measurement and indoor positioning. It is not typically selected for general IoT data communication, but for location, ranging and proximity applications.

Use UWB for:

  • indoor asset tracking
  • real-time location systems
  • access control
  • distance measurement
  • positioning in warehouses
  • proximity detection
  • robotics and automation support

UWB is useful when location accuracy is more important than long communication range.

Technical considerations for UWB

Check:

  • required positioning accuracy
  • anchor infrastructure
  • tag power consumption
  • update rate
  • antenna placement
  • enclosure impact
  • coexistence with other radios
  • regulatory requirements

UWB usually requires more system planning than simple point-to-point communication, especially when anchors, tags and positioning software are involved.


Network and infrastructure requirements

Wireless technology selection is not only a hardware decision. The network model also matters.

Ask:

  • Does the device need an operator network?
  • Is a private network preferred?
  • Is local Wi-Fi available?
  • Is a gateway required?
  • Does the device need smartphone connectivity?
  • Will the product be used in multiple countries?
  • Who manages the network?
  • What are the recurring connectivity costs?
  • What happens if the network is unavailable?

Public networks

NB-IoT and LTE-M usually depend on mobile network operators. This can reduce infrastructure work, but introduces subscription costs, coverage dependencies and operator certification requirements.

Private or site networks

LoRaWAN can be deployed as a private network. This gives more control, but requires gateway planning, network management and coverage testing.

Local networks

Wi-Fi and Bluetooth LE depend on local infrastructure. They can be cost-effective, but range, setup and reliability depend on the installation environment.


Antenna and enclosure considerations

Antenna performance has a major impact on wireless reliability. The same module can perform very differently depending on the antenna, PCB layout and enclosure.

Check:

  • frequency band
  • antenna type
  • antenna size
  • ground plane requirements
  • keep-out area
  • cable losses
  • enclosure material
  • distance from batteries, displays and metal parts
  • final mounting orientation
  • indoor or outdoor installation

Metal enclosures, compact PCBs and poor antenna placement can reduce range and signal quality. For industrial or outdoor devices, an external antenna may be required.

For best results, test RF performance in the final enclosure and in the real installation environment.


Power budget and duty cycle

Power consumption depends on more than the wireless technology. Firmware behavior, signal quality and transmission pattern also matter.

Evaluate:

  • sleep current
  • active current
  • radio startup time
  • network registration time
  • message size
  • transmission frequency
  • retry behavior
  • signal strength
  • peak current
  • battery chemistry
  • low-temperature performance

A device that transmits once per day has a very different power profile from a device that sends data every minute. Poor signal conditions can also increase power consumption because the radio may transmit longer or retry more often.

For battery-powered devices, calculate energy per communication cycle instead of only comparing datasheet current values.


Latency and update frequency

Some IoT devices can tolerate delayed communication. Others need fast response.

Low latency may be important for:

  • alarms
  • control systems
  • mobile equipment
  • user interaction
  • access systems
  • safety-related monitoring

Low latency is usually less important for:

  • periodic environmental sensing
  • smart metering
  • slow-changing measurements
  • daily asset status updates

In general, technologies optimized for very low power may have higher latency or lower data rates. Define the required response time before selecting the wireless technology.


Firmware updates and data volume

Firmware updates are often forgotten during wireless technology selection. A device may send only small sensor values during normal use, but still need larger data transfers for maintenance.

Check:

  • will the device need over-the-air updates?
  • how large are firmware files?
  • how often will updates happen?
  • is the connection stable enough?
  • are data costs acceptable?
  • can updates be done locally by Bluetooth or Wi-Fi?
  • is a fallback update method needed?

For devices that require regular remote updates, LTE-M or Wi-Fi may be more suitable than ultra-low-data technologies.


Certification and regional deployment

Wireless products must comply with regional radio and safety requirements. Certification can affect module choice, antenna choice and product design.

Check:

  • CE, UKCA, FCC or other regional requirements
  • cellular operator certification
  • module certification status
  • approved antenna types
  • regional frequency bands
  • LoRaWAN regional frequency plans
  • target market restrictions
  • documentation from the module manufacturer

Changing the antenna, enclosure or RF layout can affect certification. Consider certification early, not after the final prototype.


Common wireless technology selection mistakes

Avoid these common mistakes:

  • choosing based only on range
  • selecting Wi-Fi for long-life battery devices
  • choosing NB-IoT for applications that need continuous mobility
  • choosing LoRaWAN without checking gateway coverage
  • ignoring antenna size and placement
  • forgetting regional frequency bands
  • underestimating network registration power
  • ignoring firmware update requirements
  • not checking operator coverage
  • assuming datasheet range equals real-world range
  • testing without the final enclosure
  • selecting a module without checking lifecycle and availability

Most wireless problems are caused by system-level choices, not by the radio module alone.


Decision checklist

Before selecting a wireless technology, define:

  • What data does the device send?
  • How large is each message?
  • How often does it transmit?
  • Is the device battery-powered?
  • What battery lifetime is required?
  • Is the device fixed or mobile?
  • Does it operate indoors, outdoors or both?
  • Which countries or regions are targeted?
  • Is public network coverage available?
  • Is a private network possible?
  • Is a gateway required?
  • Does the device need smartphone connectivity?
  • Are firmware updates needed?
  • What antenna space is available?
  • What enclosure material is used?
  • What certifications are required?
  • What production lifetime is expected?

If these questions are answered before module selection, the chance of choosing the right technology increases significantly.


Need help selecting the right wireless technology?

The best wireless technology depends on your application, power budget, antenna design, network model and certification requirements.

TOP-electronics supports engineers with component selection, technical advice and supply chain support for IoT and connectivity projects.

Need help selecting the right wireless module, antenna or connectivity technology? Contact our technical support team.

Back