Fading is what happens when multiple versions of the same radio signal arrive by different paths and partially cancel each other. Interference is different: the desired signal may still be strong, but other transmitters raise the noise and destroy SNR. For IoT, that distinction matters. A weak link budget fix will not solve a crowded 2.4 GHz channel, and a channel change will not solve a path with no fade margin. Reliable deployments need both: extra dB for fading and a coexistence plan for shared spectrum.
35.1 Learning Objectives
By the end of this chapter, you will be able to:
Explain how multipath propagation causes signal fading in IoT environments
Differentiate between Rayleigh fading (no line-of-sight) and Rician fading (dominant LOS path) and their impact on link reliability
Calculate appropriate fading margins using coherence bandwidth, delay spread, and reliability targets
Diagnose RF interference by distinguishing weak signal (low RSSI) from interference (good RSSI, poor SNR)
Implement interference mitigation strategies including channel selection, frequency hopping, and CCA/LBT protocols
Design a channel coexistence plan for mixed Wi-Fi/Zigbee/BLE deployments in the 2.4 GHz band
Key Concepts
Multipath creates fading because reflected copies arrive with different delays and phases.
Rayleigh fading describes non-line-of-sight links where no single path dominates; Rician fading applies when a strong LOS path is present.
Fade margin is budget reserve, not wasted power. It absorbs shadowing, motion, reflections, and installation variation.
Good RSSI with bad SNR usually means interference, not weak coverage.
2.4 GHz coexistence is a planning problem involving Wi-Fi, Zigbee, BLE, microwaves, and other uncoordinated transmitters.
Mitigation works at multiple levels: band choice, channel choice, antenna placement, protocol behavior, and physical separation.
For Beginners: Fading and RF Interference
When a radio signal travels from one IoT device to another, it does not just go in a straight line – it bounces off walls, floors, and objects, creating multiple copies that arrive at slightly different times. Sometimes these copies add together (stronger signal), and sometimes they cancel each other out (weak or dead spots). This is called fading, and it explains why your Wi-Fi works great in one spot but drops out when you move just a few feet. Understanding fading helps you design IoT systems that work reliably in the real world.
35.2 Prerequisites
Before diving into this chapter, you should be comfortable with:
Radio waves reflect off surfaces (walls, ground, buildings). The receiver sees multiple copies of the signal arriving at slightly different times:
35.3.1.1 One packet can arrive as several paths
Multipath fading is your own signal arriving by different routes and interfering with itself.
Propagation scene
Direct path: the shortest route from TX to RX.
Wall reflection: a delayed copy that arrives a few nanoseconds later.
Floor reflection: another delayed copy with different phase.
Blocked path: weak or badly delayed energy that can still distort the mix.
Receiver result
Constructive adding: delayed copies line up closely enough in phase to boost the received signal.
Destructive cancelling: a small movement changes the relative phase and causes a deep fade or packet loss.
Figure 35.1: Multipath overview showing direct, reflected, and blocked paths, plus the two receiver outcomes that matter in practice: signal boost or deep fade.
35.3.1.2 Alternative view: Multipath as time-delayed copies
The same packet reaches the receiver in a short sequence rather than as one clean impulse.
10 ns
Direct path
First copy arrives from the shortest route.
15 ns
Wall reflection
A +5 ns delayed copy reaches the receiver.
18 ns
Ground reflection
Another delayed copy arrives with different phase.
25 ns
Building reflection
A late copy stretches the channel response even further.
Figure 35.2: Time-domain view of multipath. The direct copy arrives first, followed by reflected copies whose delay and phase determine whether the packet is reinforced or weakened.
35.3.2 Types of Fading
Path loss: caused mainly by distance; it is comparatively static and is handled with antenna choices, geometry, and link budget.
Slow fading / shadowing: caused by obstacles and layout changes over seconds to minutes; it is handled with fade margin.
Fast fading / multipath: caused by reflections that change over milliseconds; it is handled with diversity, coding, and spread-spectrum behavior.
Frequency-selective fading: some parts of the channel fade more than others because different paths have different delays; it is handled with OFDM or wideband techniques.
35.3.3 Fading Models: Rayleigh vs. Rician
The statistical behaviour of fast fading depends on whether a direct line-of-sight (LOS) path exists between transmitter and receiver:
Rayleigh Fading: When there is no dominant LOS path (e.g., indoor office, dense urban canyon), the received signal is the sum of many reflected paths with similar power. The signal envelope follows a Rayleigh distribution. Deep fades of 20-30 dB below the mean can occur, and the probability of a fade depth \(F\) (in dB) is approximately \(P(\text{fade} > F) = 10^{-F/10}\). For example, a 20 dB fade occurs about 1% of the time.
Rician Fading: When a strong LOS path exists alongside weaker reflected paths (e.g., outdoor rural, rooftop-to-rooftop), the signal envelope follows a Rician distribution. The Rician K-factor measures the ratio of LOS power to scattered power: \(K = P_{\text{LOS}} / P_{\text{scattered}}\). When K = 0, Rician reduces to Rayleigh. Typical values: K = 6-10 dB for outdoor LOS, K = 0-3 dB for light indoor obstruction.
For Beginners: Rayleigh vs. Rician Fading
Think of Rayleigh fading like a room full of people all talking at the same volume – no single voice dominates, so the combined sound fluctuates wildly. This happens when your IoT device has no clear line of sight to the gateway. Rician fading is like that same room but with one person using a megaphone (the direct LOS path). The megaphone voice is always heard clearly, and the background chatter causes only small fluctuations. The stronger the megaphone (higher K-factor), the more stable and predictable the received signal.
35.3.4 Coherence Bandwidth and Coherence Time
Two parameters determine whether fading is “flat” (affects all frequencies equally) or “selective” (affects some frequencies more than others):
Coherence Bandwidth (\(B_c\)): The frequency range over which the channel response is approximately constant. Calculated from the RMS delay spread (\(\sigma_\tau\)) as \(B_c \approx 1 / (5 \sigma_\tau)\). If your signal bandwidth is less than\(B_c\), fading is flat (all frequencies fade together). If wider, fading is frequency-selective.
RMS delay spread: 1-5 us Coherence bandwidth: 40-200 kHz
Suburban
RMS delay spread: 0.2-2 us Coherence bandwidth: 100 kHz to 1 MHz
Mountainous
RMS delay spread: 5-20 us Coherence bandwidth: 10-40 kHz
Coherence Time (\(T_c\)): The time duration over which the channel remains approximately constant. Related to Doppler spread (\(f_d\)) as \(T_c \approx 1 / f_d\), where \(f_d = v \cdot f / c\) (v = device velocity, f = carrier frequency, c = speed of light). If your symbol period is less than\(T_c\), the channel appears static during one symbol.
Stationary sensor
Velocity: 0 m/s Doppler spread: ~0 Hz Coherence time: Very long (seconds+)
Walking pace
Velocity: 1.5 m/s Doppler spread: 12 Hz Coherence time: ~83 ms
Forklift in warehouse
Velocity: 5 m/s Doppler spread: 40 Hz Coherence time: ~25 ms
Vehicle-mounted
Velocity: 30 m/s Doppler spread: 240 Hz Coherence time: ~4 ms
35.3.5 Fading Margin
To account for unpredictable fading, we add a fading margin to the link budget:
Fading statistics (indoor warehouse with metal shelving): - Slow fading (shadowing): Log-normal with \(\sigma = 8\) dB - Fast fading (multipath): Rayleigh with 10 dB variance - Total fading: \(\sqrt{8^2 + 10^2} = 12.8\) dB standard deviation
For 99% reliability (2.33 standard deviations): \(12.8 \times 2.33 = 29.8\) dB fading margin needed
Our margin: 30 dB available vs 29.8 dB required → Success with 0.2 dB safety factor
What if we move 2× farther? Path loss increases by 6 dB → Margin drops to 24 dB → Fails (below 29.8 dB threshold). Reliability would drop to ~90%.
Core Concept: RF interference occurs when multiple signals occupy the same frequency band simultaneously, causing packet loss, reduced throughput, or complete communication failure - and the 2.4 GHz ISM band (used by Wi-Fi, Bluetooth, Zigbee, and microwave ovens) is the most crowded spectrum in IoT.
Why It Matters: Interference is the hidden cause of most “mysterious” IoT connectivity problems. A sensor network that works perfectly during testing may fail during business hours when Wi-Fi traffic peaks, or when the break room microwave runs. The 2.4 GHz band can see 40-60 overlapping networks in dense urban environments, while sub-GHz bands (868/915 MHz) typically have less than 5 competing signals.
Key Takeaway: Design for interference from day one using the “3C strategy”: Choose frequencies wisely (sub-GHz for critical sensors, avoid 2.4 GHz channels 1-6-11 overlap with Wi-Fi), use Clear Channel Assessment (listen-before-talk), and implement Channel hopping (frequency diversity). If your sensor node reports intermittent failures but RSSI looks good, suspect interference - measure SNR (signal-to-noise ratio) instead of just signal strength.
35.4.1 Choosing the Right Band for Your Application
35.4.1.1 Choose the band that matches the interference problem
Do not assume the fix lives inside 2.4 GHz. Sometimes the right answer is to change the band, not just the channel.
Sub-GHz
35.4.1.1.1 Best for hard coverage and crowded sites
Low crowding: usually far fewer competing transmitters than 2.4 GHz.
Good obstacle handling: longer wavelength helps range and penetration through clutter.
Best fit: agriculture, industrial sensors, city-scale telemetry, and large sites.
Watch out: lower throughput, regional regulations, and larger antennas.
2.4 GHz
35.4.1.1.2 Works when you actively manage coexistence
Highest crowding: Wi-Fi, BLE, Zigbee, microwaves, and consumer electronics all live here.
Moderate obstacle tolerance: good for building-scale networks if channels and placement are controlled.
Best fit: smart buildings, consumer devices, and common low-cost hardware ecosystems.
Watch out: never rely on defaults. Measure SNR and expect neighbors to change over time.
5 GHz
35.4.1.1.3 Good for short-range throughput, not hostile coverage
Cleaner than 2.4 GHz: often less crowded, but still not a cure for poor geometry.
Weak obstacle tolerance: coverage collapses faster through walls, shelving, and machinery.
Best fit: short-hop backhaul, video, and high-rate infrastructure with nearby access points.
Watch out: do not use it as a drop-in replacement for difficult LPWAN-style coverage problems.
Decision rule
If the deployment fails because the 2.4 GHz band is crowded, first ask whether the application truly belongs there at all. Channel tuning is not always enough.
Figure 35.3: Interference-first band selection guide comparing when to stay in 2.4 GHz, when to move to Sub-GHz, and when high-band throughput links are acceptable.
Practical shortcuts:
Choose Sub-GHz first when the site is large, obstacle-heavy, or already saturated with 2.4 GHz traffic.
Choose 2.4 GHz when ecosystem compatibility matters and you can actively manage channels and interference.
Choose 5 GHz only when you truly need throughput and can tolerate short-range, cleaner line-of-sight deployment.
35.5 RF Interference Analysis and Mitigation
Real-world IoT deployments rarely operate in isolation. Understanding and mitigating RF interference is essential for reliable wireless communication, especially in crowded ISM bands.
35.5.1 Sources of Interference
Co-Channel Interference (Same Frequency):
Wi-Fi networks: heavily affect BLE, Zigbee, and Thread in 2.4 GHz; usually high severity.
Microwave ovens: can disrupt almost any 2.4 GHz device nearby; very high local severity.
Other IoT networks: can still matter in Sub-GHz bands, but usually at lower density than 2.4 GHz systems.
Worked Example: Debugging Zigbee Network Interference
Scenario: An office building has 120 Zigbee smart lights. Lights on floor 3 randomly stop responding during lunch (12:00-13:00). Other floors work fine.
Step 1: Measure baseline signal quality
Use Zigbee sniffer to capture packets during failure
Key lesson: High RSSI does not guarantee reliable communication. Interference causes packet loss even with strong signals. Always measure SNR (Signal-to-Noise Ratio), not just RSSI.
Common Mistake: Ignoring Microwave Oven Interference
Problem: Smart home uses Zigbee sensors near kitchen. Sensors drop offline when cooking, return after ~2 minutes.
Why microwave ovens destroy 2.4 GHz:
Magnetron frequency: 2.45 GHz (center of 2.4 GHz ISM band)
Output power: 1000W (60 dBm!)
Zigbee transmit power: 0.01W (10 dBm)
Power ratio: 100,000:1 (50 dB stronger than Zigbee)
Even with microwave shielding (typically -30 dB attenuation), 30 dBm of microwave power leaks out - still 20 dB stronger than nearby Zigbee signals.
Fix options:
Move coordinator: Place Zigbee hub away from kitchen (>5 meters)
Switch bands: Use sub-GHz for kitchen sensors (868/915 MHz unaffected by microwaves)
Add redundancy: Multiple mesh router nodes so kitchen sensors can route around interference
Real-world data: Smart thermostat 2m from microwave: Packet loss increases from 0.5% → 98% when microwave operates. After moving hub to bedroom (8m away): Packet loss stays at 0.5% even during cooking.
What to observe: Correlation between interference and specific events. If failures cluster around meal times, suspect microwave. Use zigbee2mqtt or similar tools to log packet loss timestamps.
Non-Wi-Fi 2.4 GHz Interference:
Bluetooth audio
Affected technologies: BLE sensors Severity: Medium
Baby monitors
Affected technologies: 2.4 GHz mesh networks Severity: High
Adjacent-Channel Interference:
Channel allocation example (2.4 GHz)
Wi-Fi channel 1 overlaps with Zigbee channels 11-14.
Wi-Fi channel 6 creates another overlap zone through the middle of the Zigbee plan.
Planning implication: use the quieter gaps around channels 15, 20, 25, and 26 when strong Wi-Fi is present.
Knowledge Check: Fading and Interference
Q1: Your outdoor IoT sensor has good RSSI (-65 dBm) but is losing 30% of packets. What is the most likely cause?
The battery is low
The antenna is broken
RF interference is present (good RSSI but poor SNR) correct
The sensor firmware has a bug
Answer: C) RF interference. Good RSSI means the desired signal is still arriving. If packet loss is high anyway, the missing piece is usually poor SNR caused by competing transmitters or noise on the same band.
Q2: A Zigbee network in a hospital needs to coexist with heavy Wi-Fi traffic. Which Zigbee channels should you prefer?
Answer: B) Channels 15, 20, 25, 26. These channels sit in the quieter gaps around the common Wi-Fi plan. Channel 26 is the safest single answer, but the other listed channels are also useful when you need more deployment flexibility.
35.5.2 Interference Measurement Techniques
Spectrum Analysis:
# Pseudo-code for interference surveydef conduct_rf_survey(center_freq, bandwidth, duration_min):"""Measure RF environment over time""" samples = []for t inrange(duration_min *60): # Sample every second reading = spectrum_analyzer.measure( center_freq=center_freq, span=bandwidth, rbw=100000# 100 kHz resolution bandwidth ) samples.append({'timestamp': time.time(),'peak_power_dbm': reading.peak,'avg_power_dbm': reading.average,'channel_occupancy': reading.duty_cycle }) time.sleep(1)return analyze_interference(samples)def analyze_interference(samples):"""Classify interference patterns"""return {'avg_noise_floor': np.mean([s['avg_power_dbm'] for s in samples]),'peak_interference': max([s['peak_power_dbm'] for s in samples]),'duty_cycle': np.mean([s['channel_occupancy'] for s in samples]),'interference_events': count_peaks_above_threshold(samples, -60) }
Planning rule: avoid Zigbee channels 18-22 when Wi-Fi channel 6 is dominant because the overlap region becomes the busiest part of the band.
Sub-GHz Channel Selection (LoRa/Sigfox):
EU868
Frequency band: 868-868.6 MHz Duty-cycle limit: 1% Best channels: 868.1, 868.3, 868.5
US915
Frequency band: 902-928 MHz Duty-cycle limit: No limit (FCC) Best channels: Use all 64 uplink channels
AS923
Frequency band: 923-923.5 MHz Duty-cycle limit: Varies Best channels: 923.2, 923.4
35.5.4 Adaptive Frequency Hopping (AFH)
Bluetooth AFH Implementation:
Bluetooth AFH implementation
Standard hopping: 79 channels at 1600 hops per second.
Example AFH map: about 55 good channels remain when roughly 30% of the band is blocked.
Blocked set example: channels 3, 4, 10, 11, 40, 41, and 42 are blacklisted because they collide with persistent interferers.
Update cadence: refresh the map every 30 seconds using packet error rate, RSSI measurements, and the master’s blacklist.
Implementation Considerations:
Minimum channels: Bluetooth requires at least 20 good channels
Update latency: Changes propagate to all slaves within 6 slots
Hysteresis: Don’t thrash channels based on single errors
35.5.5 Physical Layer Mitigation
Antenna Techniques:
Directional antenna
Benefit: 6-15 dB rejection of off-axis interference Application: Fixed outdoor links
Antenna diversity
Benefit: 3-6 dB gain against multipath fading Application: Indoor gateways
Polarization isolation
Benefit: 20-30 dB between cross-polarized signals Application: Collocated systems
Spatial separation
Benefit: 6 dB per doubling of distance Application: Antenna placement
Power Control Strategy:
def adaptive_power_control(current_rssi, target_rssi, current_tx_power):"""Adjust transmit power to minimize interference contribution""" margin =6# dB safety marginif current_rssi > target_rssi + margin:# Signal too strong, reduce power new_power = current_tx_power - (current_rssi - target_rssi - margin)elif current_rssi < target_rssi - margin:# Signal too weak, increase power new_power = current_tx_power + (target_rssi - current_rssi)else: new_power = current_tx_power# Clamp to regulatory limitsreturnmax(min(new_power, MAX_TX_POWER), MIN_TX_POWER)
35.5.6 Protocol-Level Mitigation
Clear Channel Assessment (CCA):
Before transmit
Listen for energy on the channel (ED threshold about -62 dBm for 802.15.4).
If the channel is busy, defer and back off.
After the backoff window, check again.
Stop after the platform’s retry limit, typically 4-5 attempts.
Backoff rule:random(0, 2^BE - 1) × unit_period, where BE starts at 3 and increases up to 5 on repeated collisions.
Listen Before Talk (LBT) for Sub-GHz:
Required in EU868: - Minimum listen time: 5 ms - Threshold: -80 dBm (or technology-specific) - Penalty: Must wait 1 second if channel busy
35.5.7 Troubleshooting Interference Issues
Symptom: High Packet Error Rate
Measure RSSI and SNR (signal-to-noise ratio)
If RSSI good but SNR poor -> interference present
Conduct spectrum sweep during peak interference
Identify interferer by frequency, duty cycle, modulation
Symptom: Intermittent Connectivity
Log connection events with timestamps
Correlate with known interference sources (work schedules, microwave use)
Check for hidden node problem in mesh networks
Verify antenna orientation hasn’t changed
Symptom: Reduced Range
Verify transmit power setting
Check antenna connection (2 dB loss from poor SMA connection)
Measure noise floor vs. commissioning baseline
Look for new interference sources (new Wi-Fi APs, industrial equipment)
35.5.8 Site Survey Checklist
Pre-Deployment Survey:
35.6 Worked Example: Debugging a Warehouse Zigbee Deployment
A logistics company (DHL Supply Chain) deployed 200 Zigbee temperature sensors across a 50,000 sq ft cold storage warehouse to monitor pharmaceutical inventory. During commissioning, the network achieved 99.2% packet delivery. Three weeks after go-live, delivery dropped to 71% during weekday business hours (8 AM – 6 PM) but remained at 98% overnight and on weekends.
Step 1: Symptom Analysis
Commissioning
Packet delivery: 99.2%
Average RSSI: -62 dBm
Average SNR: 18 dB
Failed nodes: 0
Weekdays 8AM-6PM
Packet delivery: 71%
Average RSSI: -64 dBm
Average SNR: 4 dB
Failed nodes: 38 of 200
Nights/Weekends
Packet delivery: 98%
Average RSSI: -63 dBm
Average SNR: 16 dB
Failed nodes: 2 of 200
Key observation: RSSI was nearly unchanged (signal strength was fine), but SNR collapsed during business hours. This pointed to interference, not signal attenuation.
Step 2: RF Site Survey During Business Hours
Using a Wi-Spy spectrum analyser, the engineering team scanned the 2.4 GHz band across the warehouse floor during peak operations:
12 Wi-Fi access points active during business hours (for handheld barcode scanners). Only 4 were active during commissioning (the warehouse was empty).
8 forklift-mounted tablets with continuous Wi-Fi video streaming for inventory management.
3 microwave ovens in the break room (adjacent to the cold storage wall). Each microwave generated broadband interference across 2.40–2.48 GHz at up to -30 dBm within 5 metres.
The Zigbee network was configured on channel 15 (2.425 GHz), which overlapped with Wi-Fi channel 6 (centred at 2.437 GHz, extending from 2.426–2.448 GHz). During commissioning with light Wi-Fi traffic, the overlap was tolerable. During full operations with 20+ Wi-Fi clients streaming simultaneously, the interference overwhelmed the Zigbee receivers.
Step 3: Solution Implementation
Moved Zigbee to channel 26 (2.480 GHz) – this channel sits above all standard Wi-Fi channels (1, 6, 11) and avoids microwave interference (concentrated below 2.475 GHz). Packet delivery immediately improved to 94%.
Relocated 6 sensors that were within 3 metres of the break room wall. Microwave interference at -30 dBm was saturating their receivers regardless of channel. Moving sensors to the opposite side of the nearest shelf rack (adding 2 metres of metal shelving as a shield) reduced microwave interference by 22 dB. Delivery for those nodes improved from 58% to 97%.
Increased transmit power from 0 dBm to +8 dBm on the 38 affected nodes, improving SNR by 8 dB without exceeding the regulatory limit of +20 dBm for 802.15.4.
Final Results:
Packet delivery (business hours)
Before: 71% After: 98.7%
Average SNR (business hours)
Before: 4 dB After: 14 dB
Failed nodes (business hours)
Before: 38 After: 0
Cost of fix
Before: – After: $0 (software config plus physical relocation)
Lessons Learned:
Always commission during realistic operating conditions, not in an empty building. The 12 additional Wi-Fi APs and forklift tablets that appeared after go-live changed the RF environment completely.
Monitor SNR, not just RSSI. RSSI showed -64 dBm throughout (adequate signal), but SNR dropped from 18 dB to 4 dB (below the 8 dB minimum for reliable 802.15.4 reception). RSSI alone would not have identified the problem.
Zigbee channel 26 is the “safe harbour” in mixed Wi-Fi/Zigbee environments. It is the only Zigbee channel that does not overlap with any standard Wi-Fi channel, though it has slightly reduced range on some chipsets.
35.7 Concept Relationships
This chapter connects to other IoT topics:
Path Loss -> Path Loss and Link Budgets: fading is the extra uncertainty layered on top of the baseline attenuation calculation.
LoRaWAN -> LoRaWAN Overview: Sub-GHz links often avoid the worst 2.4 GHz coexistence problems altogether.
Zigbee Channels -> Zigbee Networks: channel planning is the concrete mechanism for surviving Wi-Fi overlap.
Challenge: Measure Interference in Your Environment
Objective: Use a Wi-Fi analyzer app to identify 2.4 GHz interference sources and plan optimal Zigbee channel placement.
Tools Needed:
Smartphone with Wi-Fi analyzer app (inSSIDer, WiFi Analyzer for Android, Network Analyzer for iOS)
Notebook for recording measurements
Steps:
Download a Wi-Fi analyzer app on your smartphone
Walk through your home/office recording all Wi-Fi networks and their channels
Note the RSSI of each network (strongest = most interference)
Identify “quiet zones” in the 2.4 GHz spectrum between Wi-Fi channels
Recommend 3 Zigbee channels that avoid overlapping with strong Wi-Fi signals
Solution Approach:
Wi-Fi channels 1, 6, 11 are non-overlapping (20 MHz each)
Zigbee channels 15, 20, 25, 26 fall between Wi-Fi channels
Choose Zigbee channel with lowest measured Wi-Fi power
Example: If Wi-Fi channel 6 (2.437 GHz) is strongest, avoid Zigbee channels 18-22 and use channel 25 (2.475 GHz)
Verify with “free space” measurement: -90 dBm or weaker = good channel
Expected Observation: In urban areas, you’ll see 10-40+ Wi-Fi networks. Zigbee channel 26 (highest frequency) typically has least overlap.
Common Pitfalls
1. Calling Every Packet Loss Problem “Weak Signal”
If RSSI looks healthy but retries explode, the problem is often interference or poor SNR, not transmit power. Treating every failure like a coverage problem wastes time and can make coexistence worse.
2. Forgetting Fade Margin After the Lab Demo Works
A link that works on an empty bench may collapse once people move, forklifts operate, doors close, or shelves fill. Fade margin is what keeps the deployment alive when the environment stops being ideal.
3. Using Busy 2.4 GHz Channels Just Because They Are the Default
Default Wi-Fi and Zigbee channel choices often collide with the noisiest part of the site. In shared bands, channel planning is a first-order design task, not a post-deployment cleanup step.
Label the Diagram
35.9 Summary
Multipath creates multiple delayed copies of the same packet, which can reinforce or cancel each other.
Rayleigh vs. Rician describes whether the channel has no dominant LOS path or a strong stabilizing LOS component.
Coherence bandwidth helps you decide whether fading is flat or frequency-selective.
Fade margin is the extra budget reserve that keeps links alive outside the lab.
RSSI and SNR answer different questions: RSSI says how strong the signal is; SNR says how usable it is.
2.4 GHz is crowded by default, so coexistence planning matters as much as signal strength.
Sub-GHz links often avoid the worst coexistence pain while gaining range and obstacle tolerance.
CCA/LBT and frequency hopping are protocol tools for reducing collisions and spreading interference risk.
Fading (signal strength variations from multipath reflections and shadowing) is the hidden enemy of wireless IoT reliability. Add 10-30 dB fading margin to your link budget depending on environment (10-15 dB rural, 25-30 dB safety-critical). For the crowded 2.4 GHz band, use the 3C strategy: Choose frequencies wisely (use Zigbee channels 15/20/25 to avoid Wi-Fi overlap), implement Clear Channel Assessment (listen-before-talk), and enable Channel hopping (frequency diversity). If RSSI looks good but packets are lost, suspect interference – measure SNR, not just signal strength.
For Kids: Meet the Sensor Squad!
Sammy the Sensor was trying to radio a message to the gateway, but the signal kept fading!
“Why does my signal keep getting weaker and stronger?” Sammy asked.
Max the Microcontroller drew a picture: “Your radio waves bounce off walls, the ground, and buildings. The gateway receives MULTIPLE copies of your message arriving at slightly different times. Sometimes they ADD together (strong signal!), sometimes they CANCEL each other out (fading!).”
Lila the LED blinked nervously: “That’s like two people talking at the same time – sometimes they agree and get louder, sometimes they disagree and you hear nothing!”
“And there’s another problem,” warned Bella the Battery. “The 2.4 GHz frequency band is like a crowded highway! Wi-Fi, Bluetooth, baby monitors, and even microwave ovens all share the same road. They cause interference – like trying to have a conversation in a noisy cafeteria.”
Max had solutions: “We add extra margin to our link budget – like speaking louder to be heard over noise. And we use frequency hopping – jumping between channels so interference on one channel doesn’t block us. It’s like switching lanes when traffic slows down!”
The lesson: Radio signals fade from reflections and face interference from other devices. Plan for both with extra margin and smart channel selection!
35.11 Knowledge Check
Quiz: Fading and RF Interference
35.12 What’s Next
With fading models and interference mitigation strategies in hand, explore these related topics:
Practical Wireless Lab: measure RSSI, packet loss, and interference effects with real devices.
Radio Wave Basics for IoT: revisit the band and wavelength choices that shape both fading and interference exposure.