54 Wi-Fi Channel Analysis

In 60 Seconds

This review chapter applies Wi-Fi knowledge to a real deployment scenario: 50 sensors across a 5-floor office building. Site survey analysis shows channel 11 is optimal in 2.4 GHz (weakest interference at -73 dBm vs -45 dBm on channel 1). Path loss modeling at 25 meters yields -59 dBm RSSI (Good quality, 11 dB margin above -70 dBm threshold). Band selection favors 2.4 GHz for coverage-driven low-data-rate sensors (better wall penetration, 5.6 dB advantage over 5 GHz). Battery life calculation for ESP32 on 5 GHz with deep sleep shows 1.6 years on a CR123A (1500 mAh), where TX consumes 75% and deep sleep only 9.4% of daily energy. Critical insight: deep sleep (10 uA) provides 189x better battery life than modem sleep (20 mA).

Sensor Squad: Picking the Best Wi-Fi Channel

“We need to deploy sensors on ALL FIVE floors!” said Sammy the Sensor. “But which Wi-Fi channel should we use?”

“Let me check the site survey,” said Max the Microcontroller. “Channel 1 has a STRONG neighbor at -45 dBm – that will cause lots of interference. Channel 6 has two networks. But channel 11 only has a WEAK signal at -73 dBm. That is 630 times weaker than channel 1’s interference!”

“What about 2.4 GHz versus 5 GHz?” asked Lila the LED. “Our sensors only send 20 bytes every 30 seconds – that is just 5.3 bits per second!”

“For tiny data like that, use 2.4 GHz!” advised Bella the Battery. “It goes through walls better, giving us 5.6 dB more signal margin. We do not need 5 GHz speed for 20 bytes! And the most important trick: ALWAYS use deep sleep (10 uA) between readings, not modem sleep (20 mA). Deep sleep gives 189 times better battery life!”

54.1 Learning Objectives

By the end of this section, you will be able to:

Analyze Wi-Fi Site Surveys: Interpret RSSI measurements from a site survey table and rank channels by interference score to identify the optimal deployment channel
Calculate Path Loss: Apply the log-distance path loss model to compute RSSI at a given distance and determine whether the result exceeds the minimum -70 dBm threshold
Evaluate Band Trade-offs: Compare 2.4 GHz and 5 GHz propagation characteristics and justify band selection for a specific sensor deployment scenario
Assess Battery Life: Calculate daily energy consumption across TX, RX, and sleep states to predict battery life in days and years for a CR123A-powered ESP32 sensor
Distinguish Sleep Modes: Contrast deep sleep and modem sleep current draw to quantify the battery life improvement factor for duty-cycled IoT devices

For Beginners: Wi-Fi Channel Analysis

Wi-Fi channels are like lanes on a highway – using the right channel avoids traffic jams. This review covers how to analyze channel usage, detect interference, and select optimal channels for your IoT deployment. Good channel management is one of the simplest ways to improve Wi-Fi network performance.

54.2 Prerequisites

Before working through this analysis, ensure you understand:

Wi-Fi Fundamentals - Core 802.11 concepts
Wi-Fi Frequency Bands - 2.4 GHz vs 5 GHz characteristics
Networking Fundamentals - Basic RF concepts

Key Concepts

Channel Utilization Analysis: Measuring how much airtime is consumed by transmissions vs idle vs interference on a Wi-Fi channel
Co-Channel Interference (CCI): Interference from two APs using the same channel within reception range of each other
Adjacent Channel Interference (ACI): Signal leakage from channels that partially overlap (e.g., channels 1 and 2)
Channel Capacity Model: Theoretical maximum throughput considering overhead, retransmissions, and CSMA/CA contention
SINR vs RSSI: Signal-to-Interference-plus-Noise Ratio accounts for competing signals; RSSI alone misses interference effects
Airtime Fairness: Mechanism ensuring all clients receive equal airtime regardless of data rate; prevents slow clients from starving fast clients
Frequency Reuse: Using same channels at sufficient separation to minimize co-channel interference; requires channel planning
Channel Analysis Tools: Wireshark, Wi-Fi Analyzer, AirMagnet, Metageek Chanalyzer for spectrum and protocol analysis

54.3 Channel Selection and Signal Quality Analysis

Scenario:

You’re deploying a smart building system with 50 Wi-Fi-enabled temperature and humidity sensors across a 5-floor office building. Each sensor needs to report data every 30 seconds. You’ve performed a Wi-Fi site survey and obtained the following results:

Floor 3 Survey Results (where you plan to deploy 10 sensors):

Network SSID	Channel	RSSI (dBm)	Band
OfficeMain	1	-45	2.4 GHz
OfficeGuest	6	-52	2.4 GHz
Neighbor1	6	-68	2.4 GHz
Neighbor2	11	-73	2.4 GHz
OfficeMain-5G	36	-58	5 GHz
OfficeMain-5G	44	-61	5 GHz

Sensor Requirements:

Operating range: Up to 30 meters from access point
Minimum acceptable RSSI: -70 dBm for reliable operation
Data payload: 20 bytes every 30 seconds
Battery-powered (CR123A, 1500 mAh, 3V)
Module: ESP8266 (2.4 GHz only) or ESP32 (2.4 GHz + 5 GHz)

Analysis Questions:

Which channel(s) in the 2.4 GHz band would provide the best performance for your IoT deployment, and why?
Calculate the expected signal quality at 25 meters from the access point on channel 1 (assume TX power = 20 dBm, frequency = 2.412 GHz)
Should you use 2.4 GHz or 5 GHz for this deployment? Justify with specific calculations.
If you choose ESP32 with 5 GHz on channel 36, estimate the battery life assuming:
- Active TX (240 mA for 10 ms every 30 seconds)
- Active RX (100 mA for 5 ms every 30 seconds)
- Deep sleep (10 uA) for the rest of the time

54.4 Optimal 2.4 GHz Channel Selection

54.4.1 Channel Analysis

2.4 GHz channels are 20 MHz wide but only 5 MHz apart, causing significant overlap. Only channels 1, 6, and 11 are non-overlapping.

54.4.2 Interference Analysis

Channel	Interfering Networks	Interference Level	Score
Channel 1	OfficeMain (ch 1, -45 dBm)	Very High	31.6
Channel 6	OfficeGuest (ch 6, -52 dBm), Neighbor1 (ch 6, -68 dBm)	Medium	6.47
Channel 11	Neighbor2 (ch 11, -73 dBm)	Very Low	0.05

Channel overlap impact: Same channel = 100% interference, Adjacent (+/-1) = 83%, +/-2 = 58%, +/-3 = 33%, +/-4 = 17%, +/-5+ = 0%

Putting Numbers to It

2.4 GHz channels are 20 MHz wide but spaced only 5 MHz apart. Overlap formula: $\text{Overlap} = \max\left(0, 1 - \frac{|\Delta \text{ch}| \times 5}{20}\right)$. Worked example: Channel 1 vs channel 3 (Δch=2): $\text{Overlap} = 1 - \frac{2 \times 5}{20} = 1 - 0.5 = 0.5 = 50\%$. Channel 1 vs channel 6 (Δch=5): $\text{Overlap} = 1 - \frac{5 \times 5}{20} = 1 - 1.25 = -0.25 \to 0\%$ (no overlap). Only channels 1, 6, and 11 are truly non-overlapping in 2.4 GHz.

Recommendation: Channel 11

Lowest interference (only weak neighbor network at -73 dBm), provides cleanest spectrum.

Alternative: Channel 6 would also work well (only OfficeGuest and weak Neighbor1), but has more total interference than channel 11.

Avoid: Channel 1 - Strong OfficeMain network (-45 dBm) creates significant interference.

54.5 Signal Quality Calculation at 25 Meters

54.5.1 Path Loss Calculation

Using the Log-Distance Path Loss Model for indoor Wi-Fi environments:

Formula: PL(d) = PL(d0) + 10 x n x log10(d/d0)

Parameters:

Distance: 25 meters from AP
Frequency: 2,412 MHz (channel 1)
TX power: 20 dBm
Reference loss PL(d0): 40 dB at 1 meter (2.4 GHz)
Path loss exponent (n): 2.8 (typical office environment)

54.5.2 Calculation Results

Parameter	Value	Notes
Path loss at 25m	79.14 dB	Indoor office environment
TX power	+20 dBm	Typical Wi-Fi AP
Received signal (RSSI)	-59 dBm	20 - 79.14

Putting Numbers to It

Log-distance path loss model: $\text{PL}(d) = \text{PL}(d_0) + 10n \log_{10}\left(\frac{d}{d_0}\right)$ where $n$ is the path loss exponent. Worked example: At 25 meters with $\text{PL}(1m) = 40 \text{ dB}$, $n = 2.8$ (office): $\text{PL}(25) = 40 + 10 \times 2.8 \times \log_{10}(25) = 40 + 28 \times 1.398 = 40 + 39.14 = 79.14 \text{ dB}$. With TX power of 20 dBm: $\text{RSSI} = 20 - 79.14 = -59.14 \text{ dBm}$. This is “Good” quality, providing 11 dB margin above the -70 dBm minimum threshold.

54.5.3 Interactive Path Loss Calculator

Show code

viewof plDistance = Inputs.range([1, 100], {value: 25, step: 1, label: "Distance (meters)"})
viewof plExponent = Inputs.range([2.0, 4.0], {value: 2.8, step: 0.1, label: "Path loss exponent (n)"})
viewof plTxPower = Inputs.range([10, 30], {value: 20, step: 1, label: "TX power (dBm)"})
viewof plRefLoss = Inputs.range([30, 50], {value: 40, step: 1, label: "Reference loss at 1m (dB)"})

Show code

{
  const pathLoss = plRefLoss + 10 * plExponent * Math.log10(plDistance);
  const rssi = plTxPower - pathLoss;
  const margin = rssi - (-70);
  const quality = rssi > -50 ? "Excellent" : rssi > -60 ? "Good" : rssi > -70 ? "Fair" : rssi > -80 ? "Weak" : "Very Weak";
  const qualityColor = rssi > -60 ? "#16A085" : rssi > -70 ? "#E67E22" : "#E74C3C";

  return html`<div style="background: #f8f9fa; padding: 16px; border-radius: 8px; border-left: 4px solid ${qualityColor}; font-family: Arial, sans-serif;">
    <div style="display: grid; grid-template-columns: 1fr 1fr; gap: 12px;">
      <div><strong>Path Loss:</strong> ${pathLoss.toFixed(1)} dB</div>
      <div><strong>RSSI:</strong> ${rssi.toFixed(1)} dBm</div>
      <div><strong>Signal Quality:</strong> <span style="color: ${qualityColor}; font-weight: bold;">${quality}</span></div>
      <div><strong>Margin above -70 dBm:</strong> <span style="color: ${margin >= 0 ? '#16A085' : '#E74C3C'}; font-weight: bold;">${margin.toFixed(1)} dB</span></div>
    </div>
  </div>`
}

54.5.4 Signal Quality Assessment

RSSI Range	Quality	Status
-30 to -50 dBm	Excellent
-50 to -60 dBm	Good	Our result
-60 to -70 dBm	Fair
-70 to -80 dBm	Weak	Minimum threshold
Below -80 dBm	Very weak	Unreliable

Assessment Summary

Signal quality: GOOD (-59 dBm)
Above minimum requirement (-70 dBm)
Safety margin: 11 dB above threshold
Throughput headroom: far exceeds a low-rate sensor workload (actual throughput depends on PHY rate, contention, and retries)

54.6 2.4 GHz vs 5 GHz Decision

54.6.1 Comparison

Factor	2.4 GHz (Channel 11)	5 GHz (Channel 36)	Winner
Coverage	Better penetration through walls	Worse (higher frequency = more attenuation)	2.4 GHz
Interference	Often more crowded (Wi-Fi, Bluetooth, microwave)	Often more channel options (region/DFS dependent)	5 GHz
Range	Typically better penetration/coverage indoors	Often shorter in the same environment	2.4 GHz
Data Rate	Sufficient (only 20 bytes/30s = 5.3 bps)	Higher but unnecessary	Tie
Power	Lower (better for battery)	Higher (worse for battery)	2.4 GHz
Observed RSSI	-59 dBm (calculated)	-58 dBm (surveyed)	Tie

54.6.2 5 GHz Range Analysis

Using same log-distance model with n = 3.2 (higher path loss exponent for 5 GHz):

Parameter	2.4 GHz	5 GHz	Difference
Frequency	2,412 MHz	5,180 MHz	2.15x higher
Path loss at 25m	79.14 dB	84.74 dB	+5.6 dB
RSSI at 25m	-59 dBm	-65 dBm	5.6 dB worse

Both signals are acceptable (above -70 dBm threshold), but 2.4 GHz provides better margin.

Recommendation: Prefer 2.4 GHz for coverage-driven sensors

Validate with a site survey before final deployment.

Justification:

Coverage: Better penetration ensures all 50 sensors across 5 floors remain connected
Data rate: Both bands provide far more than the required 5.3 bps
Link margin: 2.4 GHz typically provides better margin at the same distance/obstacle layout

Only use 5 GHz if:

2.4 GHz is highly congested in your environment and 5 GHz is available/cleaner
You have higher per-device throughput needs (cameras, frequent uploads)
You can ensure coverage (placement/backhaul) despite higher path loss

54.7 Battery Life Calculation (ESP32, 5 GHz, Channel 36)

54.7.1 Given Parameters

Battery: CR123A, 1500 mAh, 3V
Transmission: 240 mA for 10 ms every 30 seconds
Reception: 100 mA for 5 ms every 30 seconds
Deep sleep: 10 uA for remaining time
Cycles per day: 2,880 (every 30 seconds)

54.7.2 Energy Consumption Breakdown

Activity	Current	Duration per cycle	Energy per day	Percentage
TX	240 mA	10 ms	1.92 mAh	75.0%
RX	100 mA	5 ms	0.40 mAh	15.6%
Deep sleep	10 uA	29.985 s	0.24 mAh	9.4%
Total		30 s	2.56 mAh/day	100%

54.7.3 Battery Life Calculation

Result: 1.6 years battery life (1500 mAh / 2.56 mAh/day = 586 days)

54.7.4 Optimization Opportunities

Optimization	Impact	New Battery Life
Increase interval to 5 min	10x fewer transmissions	16 years
Use 2.4 GHz instead of 5 GHz	15% power reduction	1.85 years
Combine both optimizations	10x + 15% improvement	18.4 years*

*Practical limit: CR123A self-discharge (~2%/year) caps real-world battery life at ~10 years.

54.7.5 Interactive Battery Life Calculator

Show code

viewof blBattery = Inputs.range([500, 5000], {value: 1500, step: 100, label: "Battery capacity (mAh)"})
viewof blTxCurrent = Inputs.range([100, 400], {value: 240, step: 10, label: "TX current (mA)"})
viewof blTxDuration = Inputs.range([1, 50], {value: 10, step: 1, label: "TX duration per cycle (ms)"})
viewof blInterval = Inputs.range([10, 600], {value: 30, step: 5, label: "Report interval (seconds)"})
viewof blSleepCurrent = Inputs.range([1, 100], {value: 10, step: 1, label: "Sleep current (uA)"})

Show code

{
  const cyclesPerDay = 86400 / blInterval;
  const txEnergyPerDay = cyclesPerDay * blTxCurrent * (blTxDuration / 1000) / 3600;
  const sleepTimePerCycle = blInterval - (blTxDuration / 1000);
  const sleepEnergyPerDay = cyclesPerDay * (blSleepCurrent / 1000) * sleepTimePerCycle / 3600;
  const totalDaily = txEnergyPerDay + sleepEnergyPerDay;
  const batteryDays = blBattery / totalDaily;
  const batteryYears = (batteryDays / 365).toFixed(2);
  const txPercent = ((txEnergyPerDay / totalDaily) * 100).toFixed(1);

  return html`<div style="background: #f8f9fa; padding: 16px; border-radius: 8px; border-left: 4px solid #2C3E50; font-family: Arial, sans-serif;">
    <div style="display: grid; grid-template-columns: 1fr 1fr; gap: 12px;">
      <div><strong>Cycles/day:</strong> ${cyclesPerDay.toFixed(0)}</div>
      <div><strong>Daily energy:</strong> ${totalDaily.toFixed(2)} mAh</div>
      <div><strong>TX energy share:</strong> ${txPercent}%</div>
      <div><strong>Battery life:</strong> <span style="color: #2C3E50; font-weight: bold; font-size: 1.1em;">${Math.floor(batteryDays)} days (${batteryYears} years)</span></div>
    </div>
  </div>`
}

54.7.6 Critical Insight - Deep Sleep vs Modem Sleep

Sleep Mode	Current	Battery Life	Comparison
Deep sleep (recommended)	10 uA	1.6 years	Baseline
Modem sleep (NOT recommended)	20 mA	3.1 days	189x WORSE

Critical Power Design Decision

Deep sleep provides 189x improvement in battery life. Always use deep sleep for battery-powered Wi-Fi IoT devices when possible.

Decision Framework: Choosing 2.4 GHz vs 5 GHz for IoT Deployments

When deploying battery-powered sensors across a multi-floor facility, use this systematic framework to select the optimal Wi-Fi band.

Step 1: Calculate Required Throughput

Device Type	Count	Data Rate	Total Throughput
Your sensors	X	Y bytes/Ns	Z Mbps
Decision Rule	If < 10 Mbps: Both bands OK	If 10-50 Mbps: Check airtime	If > 50 Mbps: Consider 5 GHz

Step 2: Evaluate Coverage Requirements

Perform path loss calculation at maximum expected distance:

2.4 GHz (n=2.8):

PL(d) = 40 + 10 × 2.8 × log10(d)
RSSI = TX_power - PL(d)

5 GHz (n=3.2):

PL(d) = 40 + 10 × 3.2 × log10(d)
RSSI = TX_power - PL(d)

Decision Rule:

If both bands achieve RSSI > -70 dBm: Proceed to Step 3
If only 2.4 GHz meets threshold: Choose 2.4 GHz
If neither meets threshold: Add APs or consider mesh

Step 3: Assess Interference

Run site survey on both bands:

2.4 GHz scoring:

Interference_Score = Σ(10^((RSSI_neighbor - 70)/10))

5 GHz scoring:

Interference_Score = Σ(10^((RSSI_neighbor - 70)/10))

Decision Rule:

If 5_GHz_score < 2.4_GHz_score × 0.5: Choose 5 GHz (much cleaner)
If scores similar: Proceed to Step 4
If 2.4 GHz cleaner (rare): Choose 2.4 GHz

Step 4: Consider Device Constraints

Factor	2.4 GHz Advantage	5 GHz Advantage
Hardware cost	ESP8266: $2	ESP32: $4 (dual-band)
Power consumption	240 mA TX	260 mA TX (~8% more)
Battery life impact	Baseline	8% reduction
Module availability	Universal	ESP32, Raspberry Pi, not ESP8266

Decision Rule:

If cost-sensitive (>100 devices): 2.4 GHz if coverage adequate
If existing ESP8266 hardware: Must use 2.4 GHz
If neither constraint applies: Proceed to Step 5

Step 5: Evaluate Future Scalability

2.4 GHz: 3 non-overlapping channels (1, 6, 11) 5 GHz: 20+ non-overlapping channels (region-dependent)

Decision Rule:

If AP reuse factor > 0.3 (30% of channels occupied): 5 GHz provides better scaling
If deployment may double within 2 years: 5 GHz for headroom

Final Decision Matrix:

Scenario	Optimal Choice	Reason
Low data rate + multi-floor + battery	2.4 GHz	Better penetration, adequate throughput
Low data rate + clean 5 GHz + adequate coverage	5 GHz	Future-proof, less interference
High data rate (>10 Mbps/device)	5 GHz	Avoid 2.4 GHz airtime saturation
ESP8266 hardware	2.4 GHz	No choice
Dense deployment (>50 devices per AP)	5 GHz	More channels for AP reuse

Example Application (from this chapter):

50 sensors, 20 bytes/30s = 5.3 bps (LOW data rate)
5 floors, concrete walls (CHALLENGING propagation)
Battery-powered (POWER sensitive)
Site survey: 2.4 GHz RSSI -59 dBm, 5 GHz -65 dBm (both OK)
Interference: 2.4 GHz moderate, 5 GHz light

Decision: 2.4 GHz - The 5.6 dB better penetration provides superior link margin for a multi-floor deployment where throughput is not a constraint. 5 GHz advantage (less interference) does not offset propagation disadvantage for battery sensors requiring maximum range.

54.8 Concept Relationships

Understanding how channel analysis concepts relate:

Concept	Depends On	Enables	Trade-off
Channel Selection	Site survey, interference scan	Optimal throughput	Planning time vs performance
Path Loss Model	Distance, environment type	Coverage prediction	Accuracy vs complexity
2.4 GHz Band	Wavelength physics	Better penetration	Speed vs range
RSSI Threshold	Link budget analysis	Reliable connections	Margin vs coverage area
Deep Sleep	Wake source configuration	Battery life extension	Latency vs power consumption

Common Pitfalls

1. Analyzing Only a Single Channel in a Multi-AP Deployment

Channel analysis must examine all channels used in the deployment simultaneously. An AP on channel 1 that appears clear may be suffering from hidden-node collisions with another channel-1 AP not visible from the analysis point. Use multiple capture points or tools that analyze all channels simultaneously.

2. Confusing Airtime Fairness With Throughput Fairness

Airtime fairness gives each client equal airtime. But a 1 Mbps legacy client consumes 10x more airtime than a 10 Mbps client to send the same data. Throughput fairness would give both clients equal bytes per second. In IoT mixed with high-speed clients, disable airtime fairness to prevent slow IoT devices from consuming excessive channel time.

3. Not Accounting for Management Frame Overhead in Channel Utilization

Beacons, probe responses, and association frames consume channel airtime but are not data traffic. In dense deployments with many SSIDs and high client churn, management frame overhead can reach 10-30% of channel utilization. Include management frame analysis in channel utilization assessments.

4. Optimizing Channel Assignment Without Considering AP Topology

Channel assignment depends on physical AP locations. An optimal channel plan for current AP positions becomes sub-optimal if APs are moved. Always re-run channel analysis after any AP relocation or power level change.

🏷️ Label the Diagram

💻 Code Challenge

54.9 Summary

This analysis demonstrated a systematic approach to Wi-Fi deployment decisions:

Channel Selection: Analyze site survey data to choose channels with lowest interference (channel 11 in this case)
Path Loss Modeling: Apply log-distance models to predict signal quality at deployment distances
Band Selection: Choose 2.4 GHz for coverage-critical, low-data-rate sensor deployments
Power Budgeting: Calculate expected battery life and identify optimization opportunities
Sleep Mode Selection: Always use deep sleep (10 uA) instead of modem sleep (20 mA) for battery-powered devices

Interactive Quiz: Match Concepts

Interactive Quiz: Sequence the Steps

54.10 See Also

For deeper exploration of related topics:

Wi-Fi Frequency Bands - Detailed 2.4/5/6 GHz channel planning
Wi-Fi Power Consumption - Battery life calculations and optimization
Wi-Fi Deployment Planning - Capacity planning and case studies
Wi-Fi Fundamentals - Path loss equations and RF modeling

54.11 What’s Next

Chapter	Focus
Wi-Fi Review: Power Optimization	Detailed power optimization strategies for battery-powered Wi-Fi IoT devices, including connection reuse and transmission interval optimization