LTE vs Bluetooth vs LoRaWAN Concrete Sensors: A Fair Comparison

Wireless concrete sensors all do the same basic job: measure temperature inside the concrete and turn it into maturity and estimated strength. Where they differ is in how the readings leave the pour and reach the people making decisions. The three common approaches are direct cellular (LTE), BLE (Bluetooth Low Energy) read by a phone or hub, and low-power radio such as LoRaWAN through a site gateway. Each is a reasonable engineering choice in the right conditions. This article compares them on the points that matter on site.

Note that this is a different question from "embedded sensor or external logger". Many comparison guides sort products by whether the whole device is cast into the concrete or whether a probe on a cable connects to a logger outside. That is a form-factor choice, covered under cost drivers below. Here the question is how the data travels once it is measured.

How does each connectivity type work?

LTE sensors connect directly to the mobile network and upload to the cloud; BLE sensors wait to be read by a nearby device; LoRaWAN sensors transmit to a gateway that forwards the data over its own internet connection.

• LTE (cellular). The logger contains a cellular modem and a standard SIM card. It uploads readings at set intervals over the mobile network. No site infrastructure is needed, but the device depends on local network coverage and uses more power per transmission than short-range radios.
• BLE. The sensor stores readings and transfers them when a phone comes within range and connects. Short radio range and very low power are the main characteristics. Range in open air is typically tens of metres, but it drops sharply behind formwork and rebar and inside concrete. In our site experience, a BLE sensor embedded in fresh, wet concrete can be read only from about 20 cm away during the first hours, so the phone is held almost on the surface. Suppliers usually quote range at line of sight in ideal conditions, in cured concrete (water blocks the signal almost completely).
• LoRaWAN and other gateway systems. Sensors send small packets over a long-range, low-power radio link to a gateway. The gateway needs power and a backhaul connection (often cellular or wired internet) and must be positioned to cover the sensors. In our site experience, a LoRa sensor embedded in fresh, wet concrete reaches about 30 m during the first hours, so the gateway has to be close to the pour.

Connectivity does not change the underlying measurement. Strength estimates still come from the maturity method (ASTM C1074) and a mix-specific calibration, whichever radio is used.

How do LTE, BLE and LoRaWAN compare?

The table summarises typical characteristics; individual products vary, so check each supplier's specification.

Does someone need to visit the site to get the data?

The biggest practical difference is whether someone has to walk to the pour to get the data. With BLE, the answer is yes; with LTE and a working gateway system, it is no.

On a building site where a site engineer walks each deck every hour, collecting BLE readings adds little effort and the data is fresh enough for most stripping decisions. The picture changes when:

• pours happen at night or over weekends and the critical moment falls outside working hours;
• the project is spread over several sites or a long linear route, such as a highway, pipeline or rail job;
• access to the element is restricted, for example after backfilling, inside a cofferdam or at height, especially if BLE sensors are used.

In those cases every "can we strip yet?" or "what is the core temperature?" check becomes a trip, and a missed check can mean potential issues. Remote connectivity also allows threshold alerts, for example when an element reaches a target strength or when a temperature limit is approached, which matters for mass concrete temperature differentials where a late response can mean cracking.

What happens when the signal drops?

Every wireless system has gaps; what matters is whether readings are stored locally during the gap and uploaded later. A logger that buffers data produces a complete record even if delivery is delayed.

LTE

Cellular signal can be weak in basements, deep excavations, tunnels, inside heavily reinforced cores, and on remote desert sites. Signal also tends to change as the structure rises and floors are closed in. Before relying on LTE, check coverage at the actual logger positions rather than at the site office, and check it for the operator whose SIM you will use. Positioning the logger outside the formwork on a longer probe cable often solves marginal locations.

BLE

BLE gaps are gaps in collection rather than measurement: the sensor keeps logging, but no one sees the data until they come within range. The risk is that an alarm condition, such as a cold night or an overheating core, is discovered only after the event. Sensor memory capacity also matters on long pours between visits.

LoRaWAN

Gateway systems have a single point of failure. If the gateway loses power or its backhaul, or is moved, knocked or buried as work progresses, every sensor it serves goes silent at once. Radio paths also change as walls, slabs and equipment appear. A gateway needs an owner on site who keeps it powered and relocates it when needed.

How long do the batteries last?

Short-range radios generally use less power per transmission than cellular modems, but real battery life depends on sampling interval, temperature and signal quality for every technology. Compare stated figures only at the same sampling interval and conditions.

Cold weather reduces battery capacity, and cellular devices use more power when signal is weak because the modem works harder to connect. Hot sites raise different concerns: a device housing in direct sun can run well above the ambient temperature, so on Gulf sites in summer the logger should be shaded or mounted out of direct sun, with the probe cable doing the work of reaching the pour. Check the operating temperature range, the ingress protection rating (IP67 or IP68 is common for site loggers) and whether the battery is rechargeable or replaceable. For reusable loggers, recharging between pours is a normal part of the workflow.

What does each option really cost?

The sensor unit price is rarely the deciding cost. Total cost depends on staff time to collect data, infrastructure, subscriptions and how many pours each device is reused on.

• LTE: SIM data plan (local or roaming) and/or platform subscription per device; no gateway; minimal collection labour.
• BLE: often the lowest hardware cost per point; the hidden cost is the time spent walking to sensors, plus any delay in decisions when nobody is available.
• LoRaWAN: gateway purchase or hire, power supply, backhaul, and the labour of installing and relocating it; cost per sensor falls as sensor count on one site rises.
• All types: sacrificial probes or embedded sensors (some systems embed the whole device, others only a probe), calibration testing per mix, and data review time.

Embedded all-in-one sensors are lost with each pour, whereas systems with a sacrificial probe and an external logger allow the logger to be reused. That distinction can matter more to cost than the radio technology itself. An external logger also has a second advantage: it sits outside the concrete, where any radio, cellular included, has a far better signal than a device cast inside reinforced concrete.

Which option should you choose?

Choose BLE where staff are always on site. Choose a LoRaWAN gateway system for a large number of sensors on the same pour. Choose LTE where decisions are made remotely or out-of-hours alerts matter, and where you want to take data collection off the site team's hands.

Mixed approaches are also valid: some contractors use connected loggers on critical elements and simpler loggers on non-critical pours. Remember that connectivity is independent of acceptance testing; see concrete sensors vs test cylinders for how sensors fit alongside specimens.

How SHM360 helps

SHM360 uses direct LTE (cellular) connectivity: the SHM360-Node is an IP68 logger with three probe channels plus ambient temperature, operating from −40 °C to +85 °C, with no gateway, BLE pairing or QR scanning required. It stores readings locally and uploads them when signal returns; where there is no LTE at all, the stored data can also be read out on site over a USB cable. Its rechargeable battery lasts up to 6 months at a typical 15-minute sampling interval, less in cold conditions or weak signal. The node sits outside the concrete with SHM360-Probe cables of 1 to 30 m (up to 100 m on request), so only the probe is sacrificial, the node is reused across pours, and the node can be placed in shade and in signal rather than where the pour happens to be. Data appears in the SHM360 platform with live charts, threshold alerts, PDF reports, CSV export and a REST API. Where cellular coverage is genuinely unavailable, a gateway-based system may be the better fit.