39  Wi-Fi Deployment Planning

In 60 Seconds

Wi-Fi IoT deployment requires careful planning to avoid common mistakes: using Wi-Fi for ultra-low-power sensors (consider LPWAN instead), ignoring channel congestion (survey before deploying), skipping network segmentation (use VLANs), and underestimating AP density needs (20-25m indoor range with obstacles). This chapter covers the top 10 deployment mistakes, AP capacity calculations, VLAN segmentation design, pre/post-deployment checklists, and a real-world case study of a 500-device industrial deployment.

  • Pre-Deployment Site Survey: RF measurement of an area before AP installation to identify interference, path loss, and optimal AP locations
  • AP Density Calculation: Number of APs needed = total devices / practical devices per AP (30-50) accounting for coverage area
  • Cell Overlap: 10-20% area overlap between adjacent APs for seamless roaming; excessive overlap increases co-channel interference
  • Channel Reuse Distance: Minimum physical separation between APs using the same channel to maintain acceptable SINR
  • Power over Ethernet (PoE): Delivering electrical power to APs via Ethernet cable; PoE+ (802.3at) provides 30W per port
  • RF Site Map: Floor plan annotated with predicted or measured RSSI contours, channel assignments, and AP locations
  • DHCP Scope Planning: IP address pool sizing for maximum expected device count with 20-30% growth headroom
  • Post-Deployment Validation: RF survey after AP installation to verify coverage meets design specifications

39.1 Sensor Squad: Wi-Fi Deployment Planning

Sammy the Sensor was learning about deployment mistakes the hard way!

Mistake #1: Sammy tried to run on batteries with Wi-Fi always connected. “I lasted only 3 days!” he said. Max the Microcontroller explained: “Wi-Fi uses a LOT of energy to stay connected. For battery sensors, either use deep sleep (wake up, send data, go back to sleep) or switch to LoRaWAN or Zigbee which sip energy like a hummingbird instead of gulping it like an elephant!”

Mistake #2: Lila the LED put all her IoT devices on the same network as the office computers. “A hacker got into a smart light bulb and then could see all the computers!” Max said: “Use VLANs – they are like separate neighborhoods in the same city. IoT devices live in one neighborhood, computers in another, and there is a security guard (firewall) at the gate between them.”

Mistake #3: Bella the Battery only put ONE access point in a huge warehouse. “Half the sensors cannot even reach it!” she said. “Indoor Wi-Fi only goes about 20-25 meters through walls. For a big building, you need multiple access points spread out like streetlights on a road – overlapping their coverage so there are no dark spots.”

Prerequisites: Wi-Fi Frequency Bands | Wi-Fi Power Consumption

This enables: Wi-Fi Architecture and Mesh | Network Design

39.2 Learning Objectives

By the end of this chapter, you should be able to:

  • Calculate access point capacity, coverage radius, and optimal placement for industrial IoT deployments
  • Diagnose the top 10 common Wi-Fi IoT deployment mistakes and prescribe corrective actions
  • Design VLAN segmentation architectures that isolate IoT traffic from corporate networks
  • Evaluate real-world case studies to justify technology selection decisions (Wi-Fi vs LPWAN)
  • Construct pre-deployment and post-deployment checklists tailored to specific deployment scenarios
  • Differentiate between coverage-limited and capacity-limited deployment constraints

Planning a Wi-Fi deployment means figuring out how many access points you need, where to place them, which channels to use, and how to handle interference. This chapter provides a systematic approach, like an architect’s planning guide for ensuring reliable wireless coverage throughout a building or campus.

39.3 Top 10 Wi-Fi IoT Deployment Mistakes

Common Mistakes and How to Avoid Them

39.3.1 Mistake 1: Using Wi-Fi for Battery-Powered Sensors

THE MISTAKE:
- Deploy Wi-Fi soil sensors expecting multi-year battery life
- Assume Wi-Fi power consumption is similar to Zigbee/BLE

THE REALITY:
- Wi-Fi connection overhead uses 10-20x more energy than LPWAN
- 3000 mAh battery: ~6 months (Wi-Fi) vs ~5 years (LoRaWAN)

THE FIX:
- Use LoRaWAN, Zigbee, or BLE for battery sensors
- Or redesign workflow: batch uploads, long sleep, TWT if available

39.3.2 Mistake 2: Deploying 100+ Devices to Consumer Router

THE MISTAKE:
- Smart home with 80 Wi-Fi bulbs + sensors on consumer router
- Assume "250 max devices" spec is realistic

THE REALITY:
- Consumer routers often struggle with 30-50 active clients
- CPU/memory limitations, not RF, cause issues
- Symptoms: intermittent drops, slow response

THE FIX:
- Use enterprise APs for 50+ devices
- Or migrate low-bandwidth devices to Zigbee/Thread
- Keep Wi-Fi for high-bandwidth devices only

39.3.3 Mistake 3: Using 5 GHz Through Multiple Walls

THE MISTAKE:
- Basement camera 20m away through 3 walls on 5 GHz
- Expect "5 GHz = better quality" always

THE REALITY:
- 5 GHz attenuates 2-3x more through walls than 2.4 GHz
- Concrete walls add 10-20 dB loss each
- Result: constant buffering, disconnects

THE FIX:
- Use 2.4 GHz for better penetration
- Or add closer APs/mesh nodes for 5 GHz
- Test before permanent installation

39.3.4 Mistake 4: No VLAN Segmentation for IoT

THE MISTAKE:
- IP cameras on same network as corporate laptops
- All devices can see each other

THE REALITY:
- Compromised camera = access to entire network
- IoT devices often have poor security, outdated firmware

THE FIX:
- VLAN 10: Corporate devices
- VLAN 20: IoT devices (firewalled)
- Block IoT-to-corporate traffic
- Allow IoT-to-internet only

39.3.5 Mistake 5: Ignoring 2.4 GHz Channel Congestion

THE MISTAKE:
- Router auto-selects channel 6
- 15 neighbor networks also on channel 6
- Accept default settings

THE REALITY:
- Collisions cause retransmissions
- Battery devices drain faster (more TX attempts)
- Throughput drops 50-80%

THE FIX:
- Use Wi-Fi analyzer to survey channels
- Manually select least congested (1, 6, or 11)
- Re-survey quarterly in dynamic environments

39.3.6 Mistake 6: Mixing Legacy Wi-Fi Standards

THE MISTAKE:
- New Wi-Fi 6 router with legacy mode enabled
- Allow 802.11b devices to connect
- "Compatibility is good, right?"

THE REALITY:
- Legacy protection mechanisms slow ALL devices
- One 802.11b device can reduce network to 11 Mbps
- Modern devices wait for slow devices

THE FIX:
- Disable 802.11b support (nobody uses it)
- Create separate 2.4 GHz SSID for legacy if needed
- Main network: Wi-Fi 4/5/6 only

39.3.7 Mistake 7: Undersized DHCP Scope

THE MISTAKE:
- DHCP pool: 192.168.1.100-199 (100 addresses)
- Deploy 80 IoT devices + 50 phones/laptops
- Don't plan for growth

THE REALITY:
- IoT devices often don't release leases properly
- Stale leases consume addresses
- New devices fail to connect

THE FIX:
- Expand to /22 (1000+ addresses) or larger
- Or use static IPs for IoT devices
- Monitor DHCP utilization (alert at 80% full)

39.3.8 Mistake 8: No Failover for Critical IoT

THE MISTAKE:
- Security system on single Wi-Fi AP
- No redundancy planned
- "Wi-Fi is reliable"

THE REALITY:
- AP failure = no alerts, no monitoring
- Power outage = complete loss
- No SLA like cellular

THE FIX:
- Deploy 2+ APs with overlapping coverage
- Critical devices: cellular backup (NB-IoT/LTE-M)
- Or use wired Ethernet for critical sensors

39.3.9 Mistake 9: Treating Wi-Fi 6 as Drop-In Replacement

THE MISTAKE:
- Buy Wi-Fi 6 router
- Expect automatic battery life improvement
- Don't verify device compatibility

THE REALITY:
- TWT requires BOTH router AND device to support Wi-Fi 6
- ESP32 (original) = Wi-Fi 4 (no TWT benefit)
- Even Wi-Fi 6 devices need TWT enabled in firmware

THE FIX:
- Verify IoT devices have Wi-Fi 6 chipsets
- Enable TWT in router AND device firmware
- Measure actual battery improvement

39.3.10 Mistake 10: Underestimating Video Bandwidth

THE MISTAKE:
- 10 security cameras on single AP
- Assume "1.3 Gbps AP" handles everything
- Don't account for overhead

THE REALITY:
- 10 cameras x 8 Mbps = 80 Mbps sustained
- Real throughput ~30% of theoretical
- AP serves 1.3 Gbps in bursts, not sustained

THE FIX:
- Budget 3x actual bandwidth needed
- Use multiple APs for cameras
- Prefer 5 GHz with 80 MHz channels
- Monitor AP utilization

Quick Check – Did You Catch the Pattern?

39.4 Pre-Deployment Checklist

Before deploying Wi-Fi IoT devices:

Pre-Deployment Checklist

Planning:

Infrastructure:

Security:

Documentation:

39.5 Post-Deployment Checklist

After deploying Wi-Fi IoT devices:

Post-Deployment Checklist

First Week:

Monthly:

Quarterly:

39.6 Case Study: TechCorp’s 500-Device Smart Office

Background: TechCorp retrofits their 50,000 sq ft office with smart devices: - 200 occupancy sensors (ceiling-mounted) - 100 smart lighting panels - 50 environmental sensors (temperature, humidity, CO2) - 100 smart power outlets - 50 conference room displays

Initial Decision: Wi-Fi for Everything

The facilities team chose Wi-Fi because: - Existing 12 access points (enterprise-grade) - IT team familiar with Wi-Fi management - No additional gateway hardware needed

Problems Discovered After Deployment:

Week 1 Issues:

- 30% of sensors intermittently offline
- Conference room displays showing "No Connection"
- Environmental sensors reporting only 2-3 times per day
  (expected: every 5 minutes)

Investigation Findings:

Finding 1: AP Overload

Before smart devices: 300 laptops/phones across 12 APs
- 25 clients per AP (comfortable)

After smart devices: 300 + 500 = 800 devices
- 67 clients per AP (overloaded!)
- Enterprise APs rated for 200 clients
- But IoT + laptops competing = poor performance

Finding 2: DHCP Scope Exhaustion

Original DHCP scope: 192.168.1.10 - 192.168.1.250
Available addresses: 240
Devices needing addresses: 800
Result: Devices failing to get IP addresses

Finding 3: Battery Drain on Sensors

Occupancy sensors (expected 5-year battery):
- Depleting in 3-4 months
- Cause: Wi-Fi connection overhead
- Each sensor waking frequently for beacon checks

Solution Implemented:

Phase 1: Network Segmentation

Created dedicated IoT VLAN:
- VLAN 100: Corporate (laptops, phones)
- VLAN 200: IoT devices (500 sensors)

New DHCP scopes:
- VLAN 100: 192.168.100.0/23 (500 addresses)
- VLAN 200: 192.168.200.0/22 (1000 addresses)

Phase 2: AP Expansion

Added 8 IoT-dedicated APs:
- Total APs: 20 (12 corporate + 8 IoT)
- IoT devices per AP: 63 (manageable)
- Different SSID: "TechCorp-IoT" vs "TechCorp-Corp"

Phase 3: Technology Reassessment

Devices kept on Wi-Fi (mains-powered):
- Smart lighting panels (PoE) - 100 devices
- Conference displays (wall power) - 50 devices
- Smart outlets (wall power) - 100 devices
Total: 250 Wi-Fi devices

Devices migrated to Zigbee (battery-powered):
- Occupancy sensors - 200 devices
- Environmental sensors - 50 devices
Total: 250 Zigbee devices

Added: 4 Zigbee coordinators

Results After Optimization:

Metric Before After
Device uptime 70% 99.2%
Sensor battery life 3-4 months 4-5 years (Zigbee)
Network incidents/week 12 <1
IT support tickets 40/week 3/week

Key Lessons Learned:

  1. Wi-Fi is not ideal for battery-powered IoT - Use Zigbee, Z-Wave, or Thread
  2. Always calculate total device count - Include IoT in capacity planning
  3. Segment IoT traffic - Dedicated VLAN prevents corporate interference
  4. Match technology to use case - Mains-powered = Wi-Fi OK; Battery = LPWAN
  5. Plan DHCP scope for 3x expected devices - IoT deployments grow unpredictably

39.7 Worked Example: AP Placement for Warehouse IoT

Scenario: Deploy Wi-Fi for 70 sensors in a 4,800 sqm warehouse with metal racking.

Given:

  • Floor area: 4,800 sqm with metal CNC machines
  • Sensors: 50 vibration + 20 environmental
  • Metal attenuation: 20 dB per large machine
  • Target RSSI: -70 dBm minimum

Why industrial environments need ~4× more APs than open offices:

Standard Wi-Fi AP coverage assumes free-space path loss (FSPL) plus wall/obstacle attenuation. The FSPL equation with distance in meters and frequency in MHz:

\[ \text{FSPL (dB)} = 20 \log_{10}(d) + 20 \log_{10}(f) + 32.45 \]

For \(d = 50\) m at \(f = 2400\) MHz (2.4 GHz): \[ \text{FSPL} = 20 \log_{10}(50) + 20 \log_{10}(2400) + 32.45 = 34.0 + 67.6 + 32.45 = 80.0 \text{ dB} \]

With AP TX power of +20 dBm and 2 dBi antenna gain, received signal at 50m (open space): \(20 + 2 - 80 = -58\) dBm (good).

But in a metal warehouse:

  • Each metal machine: +20 dB attenuation
  • Two machines between AP and sensor: +40 dB total loss
  • Received signal: \(-58 - 40 = -98\) dBm (well below -70 dBm threshold)

To maintain \(-70\) dBm minimum with obstacles, maximum practical distance shrinks to about 20-25m, reducing coverage area significantly. From standard 2,500 sqm per AP (open office) to roughly 1,000 sqm per AP in industrial environments with metal obstructions.

AP count: \[ N_{\text{APs}} = \frac{4800 \text{ sqm}}{1000 \text{ sqm/AP}} \times 1.3 \text{ (overlap)} = 6.24 \rightarrow 7 \text{ APs minimum} \]

Adding 30% margin for dead zones: \(7 \times 1.3 \approx 10\) APs deployed.

Step 1: Calculate Coverage per AP

Standard indoor: ~2,500 sqm per AP
Industrial derating:
- Metal equipment: 50% reduction
- High ceiling (8m): 20% reduction

Adjusted: 2,500 x 0.5 x 0.8 = 1,000 sqm per AP

Step 2: Calculate AP Quantity

Coverage-based: 4,800 / 1,000 = 4.8 → 5 APs minimum
Add 30% overlap for roaming: 5 x 1.3 = 6.5 → 7 APs

With additional margin for dead zones: 8-10 APs recommended

Step 3: Placement Strategy

Mount APs at 6-7m height (above machine tops)
Grid spacing: ~25m between APs
Stagger pattern (not aligned with aisles)
Focus on coverage overlap in work areas

Result:

  • 10 APs deployed (coverage-limited, not capacity-limited)
  • Mounted at 6.5m height
  • Checkerboard channel pattern (Ch 1, 6, 11 on 2.4 GHz)
  • 99.5% coverage verified by walk test

39.8 Worked Example: Smart Office Channel Planning

Scenario: 45 IoT devices in 500 sqm office with 3 APs and neighbor interference.

Given:

  • 10 security cameras (5 Mbps each)
  • 20 environmental sensors (10 kbps each)
  • 15 smart displays (2 Mbps each)
  • Neighbor networks: 2 on Ch 1, 4 on Ch 6, 1 on Ch 11

Step 1: Bandwidth Requirements

Cameras: 10 x 5 Mbps = 50 Mbps
Sensors: 20 x 0.01 Mbps = 0.2 Mbps
Displays: 15 x 2 Mbps = 30 Mbps
Total: 80.2 Mbps (with overhead: ~112 Mbps)

Step 2: Band Selection

5 GHz for cameras (high bandwidth):
- Channels 36-48 (UNII-1, no DFS)
- 80 MHz channel width
- Theoretical: 400+ Mbps

2.4 GHz for sensors (range/backup):
- Channel 11 (least congested - only 1 neighbor)
- 20 MHz channel width
- For fallback only

Step 3: Channel Assignment

AP1 (north): 5 GHz Ch 36, 2.4 GHz Ch 1
AP2 (center): 5 GHz Ch 149, 2.4 GHz Ch 11
AP3 (south): 5 GHz Ch 36, 2.4 GHz Ch 1

Load distribution:
- AP1: 4 cameras, 5 displays, 7 sensors (~31 Mbps)
- AP2: 4 cameras, 5 displays, 6 sensors (~30 Mbps)
- AP3: 2 cameras, 5 displays, 7 sensors (~20 Mbps)

Result:

  • Each AP at <10% utilization
  • 90%+ headroom for growth
  • Cameras on uncongested 5 GHz
  • Sensors can fall back to 2.4 GHz if needed

Scenario: A 400-bed hospital needs to deploy 1,200 IoT devices across multiple VLANs with specific security requirements. The devices include medical monitors, smart beds, environmental sensors, guest Wi-Fi for patients, and visitor tracking.

Step 1 – Categorize devices by risk and requirements:

Device Type Count Risk Level Data Sensitivity Uptime Requirement
Patient monitors 450 Critical PHI (HIPAA) 99.99%
Smart infusion pumps 200 Critical PHI 99.99%
Environmental sensors 300 Low Non-PHI 95%
Asset tags (beds, wheelchairs) 150 Medium Location only 98%
Guest Wi-Fi (patients/visitors) ~500 concurrent Low None 99%
Staff tablets 100 High PHI 99.9%

Step 2 – Design VLAN architecture:

VLAN 10: Corporate (staff desktops, servers) - 10.10.0.0/16
VLAN 20: Critical Medical IoT - 10.20.0.0/16
VLAN 30: Non-Critical IoT - 10.30.0.0/16
VLAN 40: Guest (patients/visitors) - 10.40.0.0/16
VLAN 50: Staff Mobile (tablets, phones) - 10.50.0.0/16

Total address space: 5 × 65,534 = 327,670 addresses (sufficient for growth)

Step 3 – Define inter-VLAN firewall rules:

Source VLAN Destination VLAN Allowed Traffic Denied Traffic
VLAN 20 (Critical IoT) VLAN 10 (Corporate) HTTPS to specific medical record servers (IPs whitelisted) All other
VLAN 20 (Critical IoT) VLAN 30 (Non-Critical IoT) DENY ALL All
VLAN 20 (Critical IoT) VLAN 40 (Guest) DENY ALL All
VLAN 20 (Critical IoT) Internet HTTPS to FDA-approved cloud services (domain whitelist) All other ports/protocols
VLAN 30 (Non-Critical IoT) VLAN 10 (Corporate) DENY ALL All
VLAN 30 (Non-Critical IoT) VLAN 20 (Critical IoT) DENY ALL All
VLAN 30 (Non-Critical IoT) Internet HTTPS/MQTT to approved cloud platforms All other
VLAN 40 (Guest) All VLANs DENY ALL All (internet-only)
VLAN 40 (Guest) Internet HTTP/HTTPS only All other protocols
VLAN 50 (Staff Mobile) VLAN 10 (Corporate) 802.1X authenticated access All
VLAN 50 (Staff Mobile) VLAN 20 (Critical IoT) Read-only monitoring (specific ports) Write access

Step 4 – Calculate DHCP scope sizing:

VLAN 20 (Critical Medical):
  Current devices: 650 (monitors + pumps)
  Growth buffer (50%): 325
  Stale lease buffer (20%): 195
  Total addresses needed: 1,170
  DHCP scope: 10.20.1.1 - 10.20.9.254 (2,300 addresses) ✓

VLAN 30 (Non-Critical):
  Current devices: 450
  Growth buffer (100%): 450 (rapid expansion expected)
  Stale lease buffer (30%): 270
  Total addresses needed: 1,170
  DHCP scope: 10.30.1.1 - 10.30.9.254 (2,300 addresses) ✓

VLAN 40 (Guest):
  Peak concurrent: 500
  Turnover (patients discharged daily): 80
  Stale lease accumulation: 400
  Total addresses needed: 980
  DHCP scope: 10.40.1.1 - 10.40.7.254 (1,790 addresses) ✓

Step 5 – QoS prioritization:

VLAN Traffic Type 802.1p Priority DSCP Queue Assignment
VLAN 20 (Critical) Patient alarms 7 (highest) EF (46) Voice (expedited)
VLAN 20 (Critical) Monitor data streams 5 AF41 (34) Video
VLAN 30 (Non-Critical) Sensor telemetry 3 AF21 (18) Best effort+
VLAN 40 (Guest) Patient internet 1 BE (0) Best effort (lowest)
VLAN 50 (Staff) EMR access 4 AF31 (26) Business-critical

Step 6 – Security controls:

All VLANs:
  - WPA2-Enterprise (802.1X/RADIUS)
  - Per-device certificates (medical devices)
  - Username/password (staff devices)
  - PMF (Protected Management Frames) enabled
  - Disable legacy protocols (WEP, WPA, TKIP)

Critical Medical (VLAN 20):
  - MAC address whitelist (supplementary)
  - Hourly connection logs
  - Intrusion detection alerts
  - Isolated from all other VLANs
  - Encrypted backhaul to on-prem servers

Guest (VLAN 40):
  - Captive portal with terms acceptance
  - Bandwidth throttling (5 Mbps per device)
  - Session timeout (24 hours)
  - Zero access to internal VLANs

Step 7 – Deployment validation:

Pre-deployment testing:
  - Simulate 500 concurrent guest connections
  - Verify VLAN isolation (scan from guest, attempt access to medical)
  - Test patient monitor failover (unplug AP, monitor reconnects <5s)
  - Load test DHCP (1,000 simultaneous requests)
  - Penetration test from guest VLAN

Post-deployment monitoring:
  - Alert on any cross-VLAN traffic attempts
  - Alert on >80% DHCP pool utilization
  - Daily audit of new MAC addresses
  - Weekly security scan
  - Monthly firewall rule review

Result: Zero HIPAA violations in 18 months. One compromised guest device (malware) isolated to guest VLAN - no lateral movement. Medical device uptime: 99.97%.

39.9 Knowledge Check

39.9.1 Match the Deployment Mistake to Its Root Cause

39.9.2 Order the Steps: Wi-Fi IoT Deployment Planning

39.10 Quick Reference: Deployment Sizing

Deployment Size Consumer Router Enterprise AP APs Needed
Small home (<20 devices) OK Overkill 1
Medium home (20-50) Borderline Recommended 1-2
Smart home (50-100) No Required 2-3
Small office (100-200) No Required 4-6
Large office (200-500) No Required 10-15
Enterprise (500+) No Controller-based 20+

Concept Relates To Why It Matters
AP Capacity Planning Device count, Channel utilization, Interference Determines how many access points needed for coverage and capacity
VLAN Segmentation Network security, IoT isolation, Firewall rules Prevents compromised IoT devices from accessing corporate resources
Channel Planning 1-6-11 rule, Interference, Site survey Avoids overlapping channels that cause hidden-node problems
Battery vs Mains Power Technology selection, Wi-Fi vs Zigbee Battery-powered sensors often better suited to LPWAN protocols
Site Survey RSSI measurement, Coverage verification, AP placement Validates theoretical planning with real-world RF measurements

39.11 See Also

Common Pitfalls

Predictive planning tools produce estimates based on floor plan and propagation models. Real RF environments differ due to furniture, equipment, glass partitions, and construction materials not in the floor plan. Always conduct a post-deployment RF survey to validate coverage.

Even AP spacing provides uniform coverage but ignores where clients actually are. If 80% of IoT sensors are in one wing of a building, that wing needs more APs for capacity even if coverage is already adequate. Deploy APs where the devices are, not where the floor plan looks symmetric.

PoE switches have limited total power budgets (e.g., 370W for a 24-port switch). High-density deployments with many PoE+ APs (25-30W each) can exceed the switch power budget. Calculate total PoE power consumption before ordering switching infrastructure.

APs should have their management traffic on a dedicated management VLAN separate from client traffic. Without this separation, security incidents on client VLANs can disrupt AP management access. Plan the management network as a separate, secured network segment.

39.12 Summary

This chapter covered Wi-Fi IoT deployment planning:

  • Top 10 Mistakes: Battery drain without deep sleep, channel congestion, missing VLANs, insufficient AP density, ignoring firmware updates, weak passwords, no monitoring, poor antenna placement, missing redundancy, skipping site surveys
  • AP Capacity Planning: Indoor range 20-25m through obstacles; plan 4-6 APs for warehouse-scale deployments
  • VLAN Segmentation: Separate IoT devices from corporate networks with firewall rules between VLANs
  • Case Study: 500-device industrial deployment with channel planning, VLAN isolation, and monitoring
  • Checklists: Pre-deployment (site survey, channel plan, VLAN design) and post-deployment (RSSI verification, roaming test, security audit)

39.13 What’s Next

Chapter Focus
Wi-Fi Certification Reference Wi-Fi Alliance certifications, regional regulatory requirements, and testing procedures for IoT products
Wi-Fi Security and Provisioning WPA3 configuration, device onboarding, and zero-trust network access for IoT fleets
Wi-Fi Architecture and Mesh Mesh topologies, roaming protocols, and controller-based vs autonomous AP architectures
Wi-Fi Power Consumption TWT scheduling, deep sleep strategies, and battery life calculations for Wi-Fi IoT devices
Wi-Fi Frequency Bands 2.4/5/6 GHz band selection, channel bonding, and interference mitigation techniques