How to Compare Real-World Range Claims Against Your Floor Plan Materials

Main entity: Real-world RF range validation for local smart-home networks. Adjacent concepts include link budget, path loss, wall attenuation, receiver sensitivity, antenna gain, and site survey. For operators running Zigbee, Z-Wave, Thread, Wi-Fi, or LoRa devices in residential and small-office settings, the gap between a datasheet’s open-air range and what actually works through a finished floor plan is a reliability problem, not a marketing footnote. This article explains how to turn range claims into testable expectations using your own walls, floors, and materials.

Most range claims assume clear line of sight, ideal antenna orientation, low interference, and no obstructions. Your house or office is none of those things. Drywall, tile, concrete, low-E glass, metal studs, and even dense furniture change how far a signal travels. If you are maintaining a local-control system with no cloud dependency, you need a repeatable way to compare what a radio should do against what it actually does in your building.

Start With the Claim, Then Break It Into Parts

A typical product page might say “up to 100 m indoor range” or “400 m line of sight.” That number is not false, but it is incomplete. It usually comes from a controlled test with a specific transmit power, data rate, antenna, and packet size. To compare it against your floor plan, you need to know what the claim assumes.

Look for these details in the datasheet or certification filings:

• Transmit power: Usually in dBm. A 20 dBm radio will not behave like a 6 dBm radio.
• Receiver sensitivity: Usually in dBm at a given data rate. Lower is better, but only if the protocol and modulation match your use case.
• Antenna type and gain: A PCB trace antenna, a whip antenna, and a chip antenna have different radiation patterns.
• Test environment: Open field, anechoic chamber, or a specific indoor test house.
• Data rate and packet length: Higher data rates reduce range. Long packets are more likely to fail at the edge of coverage.

If the vendor does not publish these, treat the range claim as a rough ceiling, not a planning number. You can still compare it against your floor plan, but you will need to add more margin.

Build a Material Attenuation Table for Your Building

Every material between the transmitter and receiver adds loss, measured in decibels. The exact loss depends on frequency, thickness, moisture content, and construction details. For planning purposes, you can use conservative estimates and then verify with a site survey.

Common planning values for 2.4 GHz signals, which cover Wi-Fi, Zigbee, and Thread:

• Drywall or plaster wall: 3–5 dB per wall
• Solid wood door: 3–6 dB
• Hollow wood door: 2–4 dB
• Glass window, standard: 2–4 dB
• Low-E glass: 10–20 dB, sometimes more
• Brick wall: 6–12 dB
• Concrete wall or floor: 10–20 dB, depending on rebar and thickness
• Metal stud wall: 5–10 dB beyond the drywall loss
• Elevator shaft or metal-lined utility chase: 20–30 dB or complete blockage

For sub-GHz protocols such as Z-Wave, LoRa, or 433 MHz sensors, losses are often lower for the same material, but the exact difference depends on the material’s electrical properties. A concrete wall that costs 15 dB at 2.4 GHz might cost 8–10 dB at 900 MHz. Do not assume a simple linear scaling.

Create a simple table for your own building. Walk the floor plan and note every wall, floor, ceiling, door, and window between the proposed radio locations. Assign a loss value to each. Add 3–6 dB of fade margin for people moving, furniture, and humidity changes. That total is your expected path loss.

Turn the Range Claim Into a Link Budget

A link budget is the arithmetic of whether a signal will arrive with enough strength to be decoded. The basic form is:

Received power (dBm) = Transmit power (dBm) + Transmit antenna gain (dBi) + Receive antenna gain (dBi) − Path loss (dB) − Other losses (dB)

Compare the received power to the receiver sensitivity. If the received power is at least 10 dB above sensitivity, you have a workable margin. If it is within 3–5 dB, the link will be fragile. If it is below sensitivity, the link will not work reliably.

Example: A Zigbee sensor transmits at 8 dBm with a 0 dBi antenna. A hub receives with a 2 dBi antenna. The datasheet sensitivity is −100 dBm at the operating data rate. Your floor plan path loss estimate is 85 dB. Received power is 8 + 0 + 2 − 85 = −75 dBm. That is 25 dB above sensitivity, which is a solid margin.

Now change the path. Add a concrete floor and a low-E window. Path loss rises to 105 dB. Received power becomes −95 dBm. That is only 5 dB above sensitivity. The link may work when the house is quiet and fail when a person stands in the wrong place or a door closes.

This is why two products with the same “100 m indoor range” claim can behave differently in your building. The claim does not account for your specific materials.

Measure Instead of Guessing

Planning tables are a starting point. A site survey gives you real numbers. You do not need expensive equipment. Many smart-home radios expose RSSI, LQI, or link quality metrics through their local API or debug interface.

For each candidate location:

1. Place the sensor or radio at its final mounting position.
2. Record RSSI at the hub or gateway over at least 24 hours.
3. Note the minimum, maximum, and typical values.
4. Trigger the device at different times of day, with doors open and closed, and with people moving through the space.
5. Repeat after any change to furniture, HVAC, or building materials.

RSSI is not a perfect proxy for link quality. A strong signal can still suffer from multipath interference or packet collisions. LQI, where available, is often more useful because it reflects chip-level error rates. Use both when the firmware exposes them.

If you are evaluating a product before purchase, ask the vendor for a test unit or a return window that allows a real site survey. A product that works in an open-plan showroom may fail in a 1950s house with plaster and metal lath.

Floor Plan Materials That Break Range Claims

Some materials deserve special attention because they are common in residential and small-office buildings but rarely reflected in marketing tests.

Low-E Glass

Low-emissivity coatings are designed to reflect infrared energy. They also reflect RF energy, especially at higher frequencies. A window that looks clear can be a 15 dB wall for a 2.4 GHz signal. If your floor plan has a sunroom, a glass-walled office, or a patio door between the hub and a sensor, do not trust a range claim that assumes ordinary glass.

Metal Lath and Plaster

Homes built before the 1960s often have plaster over metal lath. The metal mesh creates a partial Faraday cage. Signals may pass through one wall but fail after two. The effect is frequency-dependent and hard to predict from a visual inspection. A site survey is the only reliable way to map coverage in these buildings.

Radiant Floor Heating

Hydronic radiant systems are mostly RF-neutral, but electric radiant mats can create a ground plane that changes antenna behavior. If a sensor sits on a heated floor, its effective range may be shorter than the same sensor mounted on a wall. Test the device in its final orientation, not on a workbench.

Metal Studs and Foil-Backed Insulation

Commercial and newer residential construction often uses metal studs. Foil-backed rigid insulation is also common in basements and exterior walls. Both can add 5–15 dB of loss that a drywall-only estimate misses. If you are planning a basement sensor network, treat the ceiling and exterior walls as significant barriers.

Compare Products on Equal Terms

When two products claim similar range, compare them using the same floor plan, the same mounting locations, and the same test conditions. A product with a higher transmit power may look better on paper but have a poor antenna design that wastes that power in the wrong direction. A product with a lower transmit power but better receiver sensitivity may be more reliable in a noisy environment.

Ask these questions before choosing:

• Does the device let you adjust transmit power? Some firmware exposes this; some does not.
• Does the device report RSSI and LQI locally, or only through a cloud app?
• What antenna does it use? Is the antenna orientation fixed or adjustable?
• What data rate does the range claim assume? Does the device actually operate at that rate in your network?
• Does the protocol support mesh routing, and how does the device choose a parent or route?

For local-control operators, the ability to read link metrics without a cloud round-trip matters. If the only way to see RSSI is through a vendor app that requires an internet connection, you lose the diagnostic path when the network is degraded. That is a maintainability problem, not just a range problem.

Use a Margin Policy, Not a Best-Case Number

A practical rule for residential and small-office deployments is to plan for at least 10 dB of margin above receiver sensitivity. That margin absorbs:

• Seasonal humidity changes
• Furniture rearrangement
• People and pets moving through the space
• Interference from neighboring networks
• Battery voltage sag in sensors
• Aging components and antenna detuning

If your link budget shows less than 10 dB of margin, add a repeater, move the device, or choose a different product. Do not accept a link that works only when the door is open and the microwave is off.

This margin policy also helps when comparing range claims. A product that claims 100 m but leaves you 3 dB of margin in your floor plan is less useful than a product that claims 60 m but leaves 15 dB of margin. The claim is not the product. The margin is the product.

Document Your Findings

Keep a simple site survey log for each building you maintain. Record the date, device, firmware version, mounting location, RSSI, LQI, and any notable conditions. Over time, this log becomes a reference for troubleshooting and for evaluating new devices.

A useful format:

• Location: Basement utility room, north wall, 1.2 m above floor
• Device: Temperature sensor, firmware 2.4.1
• Hub RSSI: −78 dBm typical, −84 dBm minimum
• LQI: 210 typical, 180 minimum
• Notes: Door closed, furnace running, two people in room

This log is also a natural companion to a broader audit of the small systems that quietly run your week. If you have not done that audit, it is a good next step after you finish mapping RF coverage. How to Audit the Small Systems That Quietly Run Your Week walks through the same kind of failure-mode thinking for the non-radio parts of a smart home.

When the Range Claim Is Not the Problem

Sometimes a device fails at short range for reasons that have nothing to do with path loss. Before blaming the range claim, check:

• Channel congestion: A 2.4 GHz network can be unusable even at 3 m if a neighbor’s Wi-Fi is saturating the band.
• Power supply noise: A poorly filtered USB adapter can raise the noise floor and reduce effective sensitivity.
• Antenna detuning: Mounting a device against a metal surface can shift its antenna resonance.
• Firmware bugs: Some devices report incorrect RSSI or fail to rejoin a network after a power cycle.
• Protocol overhead: A mesh network that routes through a weak intermediate node can appear to have a range problem when the real issue is routing.

Isolate the variable. Move the device to a known-good location. Swap the power supply. Change the channel. If the problem follows the device, it is the device. If it follows the location, it is the environment.

Practical Example: A Two-Story House With a Basement

Consider a 1960s two-story house with a finished basement. The hub sits in the first-floor living room. You want to add a water sensor in the basement mechanical room.

The path from the hub to the sensor crosses:

• One interior drywall wall: 4 dB
• One hardwood floor with plywood subfloor: 5 dB
• One basement ceiling with fiberglass insulation: 3 dB
• One concrete foundation wall section: 12 dB
• Fade margin: 6 dB

Total estimated path loss: 30 dB. If the sensor transmits at 0 dBm and the hub sensitivity is −95 dBm, the received power is −30 dBm. That is 65 dB above sensitivity. The link should be solid.

Now add a metal lath wall in the basement and a foil-backed insulation panel. Path loss rises by 15 dB. The link still works, but the margin drops. If the sensor is battery-powered and its transmit power sags as the battery ages, the margin shrinks further. A 10 dB margin policy would still pass, but a 3 dB policy would not.

This is the kind of arithmetic that turns a vague range claim into a decision you can defend.

Tools and Methods Worth Knowing

You do not need a spectrum analyzer to do useful work, but a few tools make the process faster and more repeatable.

• Local RSSI/LQI readouts: Check the device’s local API, MQTT output, or debug console before buying.
• Phone-based Wi-Fi scanners: Useful for mapping Wi-Fi coverage, but they do not measure Zigbee, Z-Wave, or Thread directly.
• USB radio dongles: A Zigbee or Z-Wave USB stick with a command-line tool can report link quality for individual devices.
• Floor plan software: A simple scaled drawing with material notes is enough. You do not need predictive RF modeling software for most homes.
• Attenuation reference tables: The National Institute of Standards and Technology publishes technical notes on building materials and RF propagation. These are useful for checking your assumptions, though they are written for engineering audiences.

For a deeper look at how building materials affect signal propagation, the NIST technical note on electromagnetic signal attenuation in construction materials is a credible reference. It is not light reading, but it is the kind of source that keeps your planning honest. NIST: Electromagnetic Signal Attenuation in Construction Materials

Common Mistakes When Comparing Range Claims

Most failed comparisons come from a few predictable errors.

Mistake 1: Comparing open-air range to indoor range. A 400 m line-of-sight claim does not mean 400 m through walls. It means 400 m with nothing in the way. Your floor plan is the thing in the way.

Mistake 2: Ignoring antenna orientation. A vertical whip antenna has a null directly above and below. A sensor mounted on a ceiling may be in the hub’s null. A PCB trace antenna may radiate mostly in one plane. Test the device in its final orientation.

Mistake 3: Assuming all walls are equal. Two walls that look identical can have very different RF loss. One may be drywall over wood studs. The other may be drywall over metal studs with foil-backed insulation. The only way to know is to test or to open the wall.

Mistake 4: Testing only at one time of day. Interference and humidity change. A link that works at 2 a.m. may fail at 7 p.m. when every neighbor is streaming video and the house is full of people.

Mistake 5: Trusting a single RSSI reading. RSSI fluctuates. A single reading of −70 dBm does not mean the link is stable. Collect data over time and look at the minimum, not the average.

What to Do When the Numbers Do Not Match the Claim

If a product’s real-world range falls far short of its claim, you have a few options.

• Return the product. If the vendor allows it, this is the cleanest path. A product that cannot meet your floor plan requirements is not a good fit, regardless of the datasheet.
• Add a repeater or router. For mesh protocols, a strategically placed repeater can close the gap. But each repeater adds a point of failure and a maintenance task.
• Move the hub or gateway. Sometimes the cheapest fix is to relocate the coordinator to a more central location, even if it means running a longer Ethernet cable.
• Change the protocol. If 2.4 GHz cannot penetrate your building, a sub-GHz protocol may work better. The tradeoff is usually lower data rate and a smaller device ecosystem.
• Accept the limitation and design around it. If a sensor only works in one corner of the basement, put it there and accept that the rest of the basement is uncovered.

The goal is not to make every product work everywhere. The goal is to know, before you commit, whether a product will work where you need it.

Build a Range Validation Habit

Range validation is not a one-time task. Buildings change. Furniture moves. Neighbors add Wi-Fi. Firmware updates change radio behavior. A link that was solid last year may be marginal this year.

Make a habit of re-checking critical links whenever you:

• Add or move furniture
• Replace windows or doors
• Renovate a room
• Change the hub or gateway location
• Update device firmware
• Notice intermittent sensor dropouts

This habit fits naturally into a broader reliability practice. The same discipline that makes you check battery levels and log file sizes should make you check link margins. A smart home that works only under ideal conditions is not reliable. It is a demo.

FAQ

Why does a product claim 100 m indoor range but fail 10 m from the hub in my house?

The claim usually assumes a specific test environment with minimal obstructions. Your house adds path loss from walls, floors, windows, and furniture. A 10 m path through a concrete wall and a low-E window can easily exceed the loss of a 100 m open-air path. The claim is not false; it is just not specific to your building.

What is a good RSSI value for a reliable smart-home link?

There is no universal number because receiver sensitivity varies by radio and data rate. A better approach is to compare RSSI to the device’s published sensitivity and keep at least 10 dB of margin. For many 2.4 GHz devices, an RSSI of −70 dBm or better is comfortable, while −85 dBm is marginal. But the margin above sensitivity matters more than the absolute number.

Do I need a spectrum analyzer to validate range claims?

No. For most residential and small-office deployments, a site survey using the device’s own RSSI and LQI metrics is enough. A spectrum analyzer helps when you suspect interference or antenna problems, but it is not required for basic range validation. Start with the tools the device already exposes.

How do I compare two products with different range claims?

Ignore the marketing numbers and compare them in your own building under the same conditions. Mount each device in the same location, record RSSI and LQI over the same period, and note the minimum values. The product with more margin above its sensitivity threshold is the better choice for your floor plan, regardless of the printed range.

What materials cause the most unexpected range loss?

Low-E glass, metal lath and plaster, foil-backed insulation, metal studs, and concrete with rebar are the usual surprises. They are common in residential and small-office construction but rarely reflected in open-air range tests. If your building has any of these, add extra margin to your link budget and verify with a site survey.

Next Step: Turn This Into a Standing Practice

Once you have mapped RF coverage for your building, the natural next step is to apply the same failure-mode thinking to the rest of your local-control stack. Power supplies, firmware update policies, backup paths, and logging all deserve the same scrutiny. How to Audit the Small Systems That Quietly Run Your Week is a practical starting point for that broader review.

If you maintain multiple buildings or help friends and family with their systems, keep a shared attenuation table and site survey log. Over time, you will build a reference library that makes every new device evaluation faster and more accurate. That is the difference between guessing and knowing.