Sub-GHz Mesh Networks: When Do They Make Sense for Industrial IoT?

Table of contents Table of contents

Wireless range is rarely determined by transmitter power alone.

Frequency, antenna design, obstacles, interference, receiver sensitivity and network topology all influence whether an industrial IoT device can communicate reliably.

This is why engineering teams designing wireless products often face an important decision:

Should the network operate at 2.4 GHz or in a sub-GHz frequency band?

Sub-GHz mesh networks can provide better propagation, longer links and improved penetration through some materials. Combined with multi-hop routing, these characteristics make them useful in large buildings, industrial sites, outdoor infrastructure, tunnels, mines and other environments where direct gateway coverage is difficult.

However, sub-GHz is not automatically better than 2.4 GHz.

It comes with different antenna requirements, regional regulations, available bandwidth and hardware constraints.

This article explains how sub-GHz mesh networking works, where it provides the greatest value and what engineering teams should evaluate before selecting it for an industrial IoT system.

What is a sub-GHz mesh network?

A sub-GHz mesh network is a wireless network that operates below the 1 GHz frequency range and allows devices to forward data through other devices.

Typical sub-GHz frequency bands used by IoT systems include regional licence-free bands around:

  • 433 MHz,
  • 868 MHz,
  • 915 MHz,
  • and other locally permitted frequencies.

The exact frequencies and operating rules depend on the country and regulatory region.

In a mesh network, devices do not always need to communicate directly with a central gateway.

A packet may travel through several intermediate nodes:

device → mesh node → mesh node → gateway

This multi-hop communication can extend coverage beyond the range of a single radio link and provide alternative paths when individual links become unavailable.

A sub-GHz mesh network therefore combines two mechanisms:

  • the propagation advantages of a lower radio frequency,
  • and the extended coverage of multi-hop networking.

Why frequency matters in wireless IoT

Wireless signals lose strength as they travel.

The amount of loss depends on several factors:

  • distance,
  • frequency,
  • antenna characteristics,
  • walls and other obstacles,
  • reflections,
  • interference,
  • and the position of the transmitter and receiver.

Lower-frequency signals generally experience lower free-space path loss than higher-frequency signals under comparable conditions.

They can also penetrate certain obstacles more effectively.

This does not mean that a sub-GHz signal will always travel farther in every real installation. Antenna quality, transmit power, receiver sensitivity and the environment remain critical.

However, sub-GHz often offers a useful link-budget advantage in systems where coverage is more important than high data throughput.

Sub-GHz versus 2.4 GHz

The choice between sub-GHz and 2.4 GHz affects the entire product, not only the radio.

Propagation and range

Sub-GHz frequencies can provide longer communication distances under similar operating conditions.

This can be useful in:

  • large industrial halls,
  • warehouses,
  • multi-building sites,
  • outdoor infrastructure,
  • underground installations,
  • and widely distributed sensor networks.

Longer radio links may reduce the number of forwarding hops or gateways needed to cover the installation.

At 2.4 GHz, range may be shorter in the same environment, especially when walls, machinery or other structures attenuate the signal.

However, range should always be measured in the real deployment environment.

Material penetration

Lower-frequency signals can pass through some construction materials more effectively than 2.4 GHz signals.

This may improve communication through:

  • walls,
  • floors,
  • equipment enclosures,
  • vegetation,
  • and other physical obstructions.

The effect varies significantly by material.

Metal remains particularly challenging because it can block, reflect or redirect radio signals at both sub-GHz and 2.4 GHz frequencies.

A lower frequency cannot compensate for poor antenna placement inside a metal enclosure.

Interference

The 2.4 GHz band is widely used by:

  • Wi-Fi,
  • Bluetooth,
  • Zigbee,
  • Thread,
  • microwave ovens,
  • and many proprietary wireless systems.

In offices, factories and commercial buildings, this can create a busy radio environment.

Sub-GHz bands may be less crowded in some locations, but they are not interference-free.

Other systems may include:

  • alarms,
  • metering devices,
  • remote controls,
  • telemetry systems,
  • and long-range IoT networks.

The advantage depends on local spectrum usage, not simply on the nominal frequency.

Data rate

Sub-GHz networks are often designed for relatively small amounts of data.

They are well suited to:

  • sensor measurements,
  • status messages,
  • control commands,
  • alarms,
  • configuration,
  • and diagnostics.

They are less suitable for:

  • video,
  • audio,
  • large continuous data streams,
  • or applications requiring high throughput.

The lower available bandwidth can also influence how long firmware updates take across a large network.

Antenna size

Lower frequencies generally require larger antennas.

This can affect:

  • enclosure size,
  • PCB layout,
  • product aesthetics,
  • manufacturing,
  • and installation.

Antenna efficiency can become difficult to achieve in compact devices.

At 2.4 GHz, antennas are smaller and easier to integrate into many consumer and compact embedded products.

The best radio architecture must therefore consider the physical product, not only network range.

Global availability

The 2.4 GHz band is available worldwide under broadly similar conditions.

This simplifies the development of products intended for global markets.

Sub-GHz frequency plans vary by region.

A product may need different:

  • radio settings,
  • channel plans,
  • transmit-power limits,
  • duty-cycle configurations,
  • certifications,
  • and potentially hardware variants.

For global products, regional compliance must be included in the architecture from the beginning.

When does a sub-GHz mesh network make sense?

Sub-GHz mesh networking is particularly useful when the application combines several of the following requirements.

Large physical coverage

A site may contain devices distributed across:

  • a large factory,
  • a warehouse complex,
  • an industrial campus,
  • agricultural land,
  • urban infrastructure,
  • or an exploration area.

Sub-GHz links can cover greater distances between nodes, while mesh routing extends coverage through intermediate devices.

This can reduce dependence on a large number of gateways.

Difficult-to-reach locations

Some devices may be installed:

  • behind walls,
  • underground,
  • inside technical spaces,
  • on multiple floors,
  • in tunnels,
  • or far from network infrastructure.

A mesh network can forward data around obstacles, while sub-GHz propagation may improve link stability.

Low or moderate data volume

Sub-GHz mesh is strongest when devices exchange relatively small packets.

Typical examples include:

  • temperature,
  • pressure,
  • occupancy,
  • vibration status,
  • energy usage,
  • equipment state,
  • lighting commands,
  • and alarms.

The network may still support firmware updates and diagnostics, but these operations must be designed around the available data rate.

Long product lifetime

Industrial systems often remain deployed for many years.

A sub-GHz mesh architecture may be attractive when the manufacturer wants:

  • local control of the network,
  • reduced dependence on operators,
  • support for multiple hardware generations,
  • and the ability to maintain devices remotely.

Infrastructure cost matters

A star network may require additional gateways whenever direct radio coverage is insufficient.

Mesh routing can allow devices to extend network coverage themselves.

This does not eliminate infrastructure requirements, but it may reduce:

  • gateway count,
  • cabling,
  • backhaul connections,
  • installation effort,
  • and maintenance points.

The final cost depends on network density and topology.

Applications for sub-GHz mesh networking

Industrial monitoring

Factories contain obstacles that create difficult radio conditions:

  • metal machinery,
  • moving equipment,
  • reinforced structures,
  • electrical interference,
  • and large physical distances.

A sub-GHz mesh network can connect distributed sensors monitoring:

  • temperature,
  • machine condition,
  • energy use,
  • pressure,
  • vibration,
  • and equipment status.

Mesh routing helps reach devices without direct gateway visibility, while lower-frequency communication may improve link robustness across the site.

Utilities and smart metering

Energy and utility networks often contain large numbers of devices distributed over wide areas.

Applications may include:

  • electricity meters,
  • water meters,
  • gas meters,
  • transformer monitoring,
  • grid sensors,
  • and infrastructure diagnostics.

Sub-GHz communication is commonly considered in these environments because it supports long-distance, low-data-rate connectivity.

Mesh networking can help devices reach gateways through neighbouring nodes, particularly in dense urban or residential deployments.

Smart cities

Smart-city infrastructure can include:

  • street lighting,
  • parking sensors,
  • traffic systems,
  • environmental monitoring,
  • waste-management sensors,
  • and public infrastructure.

Devices may be spread across streets, buildings and remote locations.

A sub-GHz mesh network can combine long links with multi-hop coverage to reach areas that would otherwise require additional gateways.

Professional outdoor lighting

Outdoor lighting networks may extend over:

  • streets,
  • industrial areas,
  • car parks,
  • campuses,
  • tunnels,
  • and public spaces.

A communication system may need to support:

  • switching,
  • dimming,
  • fault reporting,
  • energy monitoring,
  • configuration,
  • and group commands.

Sub-GHz mesh can provide greater spacing between devices while maintaining local network control.

Large commercial buildings

Large buildings often contain:

  • concrete walls,
  • technical rooms,
  • multiple floors,
  • underground areas,
  • and equipment that obstructs radio signals.

Sub-GHz can improve propagation in some of these conditions.

However, building layout and installation density may still make 2.4 GHz a strong alternative, especially when globally available hardware or compact antennas are more important.

Mining and underground environments

Underground communication is one of the most challenging wireless scenarios.

Tunnels, rock, machinery and irregular layouts create severe propagation constraints.

A mesh network can forward data along the physical structure of the mine, while sub-GHz links may provide better propagation in some locations.

Potential applications include:

  • environmental monitoring,
  • equipment status,
  • seismic sensing,
  • safety systems,
  • and distributed measurement.

Every underground deployment requires detailed radio testing. No frequency can guarantee coverage through rock or around every tunnel geometry.

Agriculture and environmental monitoring

Sensors may be distributed across fields, forests, water infrastructure or remote industrial sites.

Sub-GHz mesh can be useful when:

  • device density is sufficient to support forwarding,
  • small messages are transmitted,
  • cellular coverage is unavailable or undesirable,
  • and the operator wants to own the local network.

For very sparse networks, a star-based long-range technology may be more practical than mesh.

Sub-GHz mesh versus LoRaWAN

Sub-GHz mesh and LoRaWAN are sometimes considered for similar applications, but their architectures are different.

LoRaWAN generally uses a star-of-stars topology:

device → gateway → network server

End devices do not normally forward packets for one another.

A mesh network uses multi-hop communication:

device → device → device → gateway

LoRaWAN may be a better fit when:

  • devices are geographically dispersed,
  • each device can reach a gateway,
  • messages are small and infrequent,
  • long range is the main requirement,
  • and local device-to-device communication is not needed.

Sub-GHz mesh may be a better fit when:

  • devices form a sufficiently dense network,
  • some devices cannot reach the gateway directly,
  • local communication is useful,
  • traffic is more interactive,
  • group commands are required,
  • or coverage needs to extend through multiple hops.

Neither topology is universally better.

The decision depends on density, traffic, latency, maintenance and infrastructure requirements.

Sub-GHz mesh versus cellular IoT

Cellular IoT allows each device to connect through a mobile network.

This can simplify wide-area deployments, especially when devices are distributed across many unrelated locations.

Cellular connectivity may provide:

  • managed external infrastructure,
  • direct cloud access,
  • and broad geographical reach.

However, it can also introduce:

  • recurring service costs,
  • operator dependency,
  • SIM management,
  • variable indoor or underground coverage,
  • and higher complexity for local communication between devices.

A private sub-GHz mesh may be more attractive when many devices operate within one site and the owner wants local control of the network.

Sub-GHz mesh versus 2.4 GHz mesh

A 2.4 GHz mesh may be preferable when:

  • global frequency compatibility matters,
  • devices must be very compact,
  • the hardware ecosystem is important,
  • installation density is high,
  • and existing 2.4 GHz platforms are already part of the product.

A sub-GHz mesh may be preferable when:

  • communication distances are longer,
  • material penetration is challenging,
  • fewer hops or gateways are desirable,
  • the environment contains heavy 2.4 GHz usage,
  • or the product is intended for a known regional market.

The most reliable decision comes from testing both options in the target environment.

How mesh routing extends sub-GHz coverage

A long-range radio link is valuable, but it does not solve every coverage problem.

Signals may still be blocked by:

  • metal,
  • terrain,
  • building geometry,
  • underground structures,
  • or equipment enclosures.

Mesh routing allows a packet to use an indirect path.

For example:

sensor A → sensor B → controller C → gateway

This creates several potential benefits:

  • devices can reach beyond direct gateway range,
  • alternative routes may be available,
  • new devices can extend coverage,
  • and the network can adapt to some link failures.

However, more hops can also increase:

  • latency,
  • traffic,
  • energy consumption,
  • and routing complexity.

The goal is not to maximize hop count. It is to create stable routes with sufficient link quality and controlled network load.

How network density affects sub-GHz mesh

Mesh requires enough devices or dedicated routers to create forwarding paths.

If devices are too far apart, there may be no viable route to the gateway.

This creates an important distinction.

Dense deployment

Examples include:

  • lighting,
  • metering,
  • building sensors,
  • factory monitoring,
  • and urban infrastructure.

Devices are close enough to create multiple possible routes.

Mesh can work well in these conditions.

Sparse deployment

Examples include isolated sensors placed many kilometres apart.

There may be no intermediate nodes available to forward packets.

A long-range star network, cellular connectivity or satellite communication may be more appropriate.

Sub-GHz does not automatically make a sparse deployment suitable for mesh.

The role of TSCH in sub-GHz mesh networking

As a network grows, long range alone is not enough.

Many devices may still compete for the same radio channel.

Contention can create:

  • collisions,
  • retransmissions,
  • unpredictable latency,
  • and unnecessary energy consumption.

Time-Slotted Channel Hopping, or TSCH, organizes communication into synchronized time slots.

Devices transmit and receive during defined opportunities rather than competing randomly for channel access.

Channel hopping allows successive transmissions to use different frequencies within the available channel plan.

This can help:

  • reduce collisions,
  • control network load,
  • limit the effect of interference,
  • improve timing predictability,
  • and support energy-efficient sleep schedules.

embeNET uses the TSCH mode of IEEE 802.15.4 within a 6TiSCH-compatible networking architecture. The platform supports both sub-GHz and 2.4 GHz radio hardware.

Regional regulations and compliance

Sub-GHz products must comply with local radio regulations.

Depending on the region, requirements may affect:

  • allowed frequency bands,
  • maximum transmit power,
  • duty cycle,
  • channel occupancy,
  • listen-before-talk mechanisms,
  • bandwidth,
  • and certification.

A product intended for Europe may not be able to use exactly the same configuration in North America or Asia.

Engineering teams should define target markets early and confirm:

  • supported channel plans,
  • regulatory limits,
  • radio hardware capabilities,
  • and certification requirements.

These constraints can affect network capacity and firmware-update performance.

Antenna design for sub-GHz devices

Antenna design is critical to the performance of any wireless product.

Sub-GHz antennas are physically larger than equivalent 2.4 GHz antennas.

In compact devices, designers may need to use:

  • electrically shortened antennas,
  • external antennas,
  • helical structures,
  • PCB antennas,
  • or custom antenna solutions.

Poor antenna efficiency can eliminate the expected range advantage of sub-GHz.

Performance can also be affected by:

  • the enclosure,
  • nearby batteries,
  • the PCB ground plane,
  • metal structures,
  • cables,
  • device orientation,
  • and installation height.

A strong networking stack cannot compensate for fundamentally poor RF hardware.

Sub-GHz mesh projects should therefore combine network planning with RF design, antenna testing and real-environment validation.

Data throughput and firmware updates

Sub-GHz mesh networks are generally optimized for relatively small application messages.

Firmware updates create a different traffic profile.

A firmware image may need to be distributed to hundreds or thousands of devices.

The network must control:

  • update scheduling,
  • fragment distribution,
  • retransmission of missing data,
  • traffic prioritization,
  • and update confirmation.

The available bandwidth and regulatory limits can significantly influence total update time.

A production-ready system should ensure that firmware distribution does not make normal application communication unusable.

embeNET includes automated firmware updates for large device fleets, together with built-in telemetry and diagnostics for monitoring deployed networks.

How to evaluate a sub-GHz mesh network

Test in the real environment

Do not rely only on theoretical range or open-field measurements.

Test around:

  • actual walls,
  • machinery,
  • underground structures,
  • vegetation,
  • vehicles,
  • equipment enclosures,
  • and installed antenna positions.

Measure link quality over time

Radio conditions change.

Measure:

  • packet-delivery ratio,
  • retransmissions,
  • signal strength,
  • route changes,
  • latency,
  • and performance at different times of day.

Test full network load

A successful point-to-point link does not prove that the complete mesh will scale.

Generate realistic:

  • sensor traffic,
  • group commands,
  • diagnostic traffic,
  • device joining,
  • route failures,
  • and firmware updates.

Evaluate the antenna as part of the product

Test the final enclosure and installation method.

A development board with an external antenna may perform very differently from the finished device.

Confirm regulatory assumptions

Make sure the planned traffic model is compatible with regional rules.

Duty-cycle or channel-occupancy restrictions may affect how frequently devices can communicate.

Test route recovery

Disable selected forwarding nodes and observe:

  • whether alternative routes are found,
  • how long recovery takes,
  • how many packets are lost,
  • and whether network congestion increases.

Common misconceptions about sub-GHz mesh

“Sub-GHz always provides better coverage”

It often improves the link budget, but antenna quality, obstacles, interference and installation still determine actual coverage.

“A longer radio range means mesh is unnecessary”

Even long-range links can be blocked.

Mesh can provide indirect paths and extend coverage around obstacles.

“Sub-GHz is always lower power”

A stronger link may reduce retransmissions, but total energy consumption depends on traffic, listening, routing and network maintenance.

“Sub-GHz is suitable for every country”

Frequency plans and operating rules vary by region.

Global products require careful regulatory planning.

“Mesh removes the need for gateways”

Mesh can reduce the number of gateways, but the network still needs one or more border routers or gateways to connect with external systems.

“More transmit power is the best way to increase range”

Higher power can help, but it may increase energy use, interference and regulatory complexity.

Antenna design, placement, routing and frequency selection can be equally important.

How embeNET supports sub-GHz mesh networking

embeNET is a wireless mesh networking platform designed for professional and industrial IoT applications.

It provides an embedded IPv6 and UDP networking stack based on a 6TiSCH-compatible architecture.

The platform combines:

  • IEEE 802.15.4 TSCH communication,
  • synchronized time slots,
  • channel hopping,
  • multi-hop routing,
  • telemetry,
  • network diagnostics,
  • automated firmware updates,
  • precise network-wide clock synchronization,
  • multicast communication,
  • and built-in security.

embeNET supports both 2.4 GHz and sub-GHz hardware platforms from multiple vendors.

This allows manufacturers to select radio hardware according to:

  • target market,
  • coverage,
  • power,
  • antenna,
  • cost,
  • component availability,
  • and product requirements.

The networking architecture can remain consistent across different supported hardware platforms, reducing dependence on a single semiconductor vendor.

When should you choose a sub-GHz mesh network?

A sub-GHz mesh network is worth evaluating when:

  • the installation covers a large area,
  • devices are located behind obstacles,
  • direct gateway coverage is difficult,
  • traffic consists mainly of small packets,
  • local multi-hop communication is valuable,
  • the deployment contains enough devices to form stable routes,
  • and the product can accommodate regional and antenna requirements.

A different architecture may be better when:

  • very high data rates are required,
  • devices are extremely small,
  • global frequency uniformity is critical,
  • devices are too geographically sparse to form a mesh,
  • or direct cellular or gateway connectivity already solves the problem.

The choice should be based on the complete system architecture rather than range alone.

Final checklist

Before selecting sub-GHz mesh networking, confirm:

  • target countries and frequency bands,
  • antenna size and performance,
  • required data rate,
  • network density,
  • expected hop count,
  • traffic frequency,
  • firmware update requirements,
  • latency expectations,
  • interference conditions,
  • power constraints,
  • gateway placement,
  • and device lifecycle requirements.

The strongest solution is not necessarily the radio with the longest theoretical range.

It is the architecture that provides reliable communication, manageable infrastructure and predictable performance across the full deployment.

Build a scalable sub-GHz mesh network with embeNET

embeNET provides a production-ready wireless mesh networking layer for industrial and professional IoT systems.

Deploy IPv6 mesh communication across supported sub-GHz and 2.4 GHz platforms, connect large device fleets and manage diagnostics, synchronization and firmware updates without developing the networking infrastructure from scratch.

Explore sub-GHz mesh networking with embeNET.

Contact us

Any question or remarks? Just write us a message!

Contact Information

Feel free to get in touch