54  ::: {style=“overflow-x: auto;”}

title: “Z-Wave Routing & Healing” difficulty: advanced —

Key Concepts
  • Z-Wave Source Routing: The Z-Wave routing model where the controller specifies the complete route (list of intermediate node IDs) in each transmitted frame
  • Route Resolution: The process by which the controller selects the best route to a destination from its routing table
  • Routing Table: A table stored in the Z-Wave controller listing the available routes to each node, updated during route learning and network healing
  • Last Working Route (LWR): The most recently successful route to a node; the controller tries LWR first before attempting alternative routes
  • Route Healing: The automatic process of discovering new routes when the LWR fails; triggered by repeated delivery failures
  • Hop Count Limit: Z-Wave limits routes to a maximum of 4 hops (controller + 3 relay nodes + destination); limits network diameter
  • RSSI Threshold: The minimum signal strength for a Z-Wave link to be considered reliable and included in routing decisions

54.1 In 60 Seconds

Z-Wave source routing means the controller determines and stores complete message paths, with Explorer Frames automatically finding new routes when devices fail (self-healing). S2 security replaces the broken S0 framework with authenticated inclusion and per-device encryption keys. Compare Z-Wave (232 devices, sub-GHz, excellent interoperability) against Zigbee (65,000 devices, 2.4 GHz) and Thread (IP-native, open standard) for your use case.

54.2 Learning Objectives

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

  • Trace source routing paths: Diagram how Z-Wave controllers determine, store, and embed complete message paths in packet headers
  • Configure network healing: Schedule and troubleshoot Z-Wave network healing procedures after topology changes
  • Evaluate security frameworks: Differentiate S0 and S2 security levels and justify which framework to deploy for locks, sensors, and switches
  • Design secure networks: Assign S2 Access Control, Authenticated, and Unauthenticated levels to a multi-device floor plan
  • Contrast protocol trade-offs: Rank Z-Wave, Zigbee, and Thread against concrete project constraints such as device count, range, and IP requirements
  • Justify protocol selection: Defend a choice among Z-Wave Classic, Plus, and Long Range for a given deployment scenario
Connect with Learning Hubs

Explore Further:

54.3 Chapter Overview

Z-Wave’s source routing approach is fundamentally different from table-based routing used by Zigbee and Thread. In source routing, the controller determines the complete path before sending a message, embedding the route directly in the packet header. This chapter explores how source routing works, why network healing is essential, and how Z-Wave’s security has evolved to protect smart home communications.

Minimum Viable Understanding (MVU)

If you only have 5 minutes, understand these three concepts:

  1. Source Routing: Z-Wave controllers determine the complete message path upfront and embed it in the packet header. Every node in the path simply forwards to the next specified node - no routing decisions needed at intermediate nodes.

  2. Network Healing: When devices are added, moved, or removed, the controller must rediscover optimal routes. Trigger healing after topology changes; schedule nightly heals for large networks.

  3. S2 Security: Modern Z-Wave uses Elliptic Curve Diffie-Hellman (ECDH) key exchange with three security levels:

    • S2 Access Control: For locks and alarms (highest security, requires DSK + PIN)
    • S2 Authenticated: For most devices (requires DSK verification)
    • S2 Unauthenticated: For low-value devices (no verification)

Key decision point: Choose Z-Wave for guaranteed interoperability and sub-GHz range; choose Zigbee for massive scale (65,000 devices); choose Thread for Matter/IPv6 native support.

Imagine you’re sending a letter through a chain of friends to reach someone far away. With source routing, YOU write down the complete delivery path on the envelope: “Give to Alice, then Bob, then Carol, who will hand it to Dave.”

This is different from table routing (used by Zigbee), where each person decides who to pass the letter to next based on their own address book.

Source routing advantages:

  • The sender knows exactly how the message will travel
  • No confusion at intermediate nodes
  • Easier to troubleshoot when things go wrong

Source routing challenges:

  • The sender must know the network layout
  • If someone moves, the sender needs to update their directions
  • That’s why “network healing” exists - to rediscover optimal paths!

Real-world analogy: Source routing is like GPS turn-by-turn directions (complete path given upfront), while table routing is like asking locals for directions at each intersection (each node decides next step).

Hey there, future smart home engineer! Let’s learn how Z-Wave messages find their way through your house!

54.3.1 The Sensor Squad Adventure: Finding the Best Path

One day, Sammy the Smart Hub needed to send an urgent message to Lila the Lock on the front door: “Someone’s home - please unlock!”

But Lila was too far away to hear Sammy directly. What could they do?

Sammy had a special map! It showed all the Sensor Squad members and how they were connected:

Sammy (Hub) --> Max (Light) --> Bella (Dimmer) --> Lila (Lock)

“I know!” said Sammy. “I’ll write the directions RIGHT ON the message: Dear Max, please pass this to Bella, who should give it to Lila!”

Max received the message, saw the directions, and passed it to Bella. Bella read the directions and handed it to Lila. Click! The door unlocked!

But wait - what if Bella moves to a different room?

“Time for NETWORK HEALING!” announced Sammy. “Everyone, tell me who you can hear clearly!”

All the devices reported back, and Sammy drew a NEW map with the best paths. Now messages would flow smoothly again!

54.3.2 Key Words for Kids

Word What It Means
Source Routing Writing complete directions on a message before sending it
Network Healing Redrawing the map when devices move or connections change
Controller The smart hub that keeps the master map of all devices
Multi-hop When a message bounces through several friends to reach its destination

54.3.3 Fun Activity: Draw Your Own Network Map!

  1. Draw your house layout
  2. Mark where smart devices might be (lights, sensors, locks)
  3. Draw lines showing which devices can “hear” each other
  4. Pick any two devices - can you find a path between them?
  5. Now “move” one device - do you need to find a new path?

54.4 When to Heal Your Z-Wave Network

Network healing is the process of rediscovering optimal routes between devices. The controller sends test messages and updates its routing tables based on successful communication paths.

Z-Wave network healing process diagram showing controller initiating healing, devices reporting neighbors, and new optimal routes being established

Required After:

  • Adding new mains-powered devices (routing slaves)
  • Moving mains-powered devices
  • Removing devices from network
  • Persistent communication failures

Best Practices:

  • Schedule: Nightly healing during low-use hours (3-4 AM)
  • After Changes: Heal after adding/moving routers
  • Symptom: If devices become unreachable, heal network
  • Frequency: At least monthly for large networks

Healing Time:

Network Size Device Count Typical Duration
Small < 30 devices 5-10 minutes
Medium 30-100 devices 15-30 minutes
Large 100-232 devices 30-60 minutes

Network healing throughput: Each device queries its neighbors (~8 neighbors average) and reports back:

\[ T_{\text{heal}} = N \times (T_{\text{query}} + T_{\text{response}}) = N \times (30 + 15) = 45N \text{ seconds} \]

For a 100-device network:

\[ T_{\text{heal}} = 45 \times 100 = 4{,}500 \text{ seconds} \approx 75 \text{ minutes} \]

However, queries can overlap when devices don’t share neighbors, so actual time is typically 30-50% of this theoretical maximum: \(75 \times 0.4 \approx 30\) minutes (matches the table above).

Common Healing Mistakes
  1. Healing too often: Constant healing wastes battery on sleeping devices
  2. Healing during active use: Can cause temporary communication failures
  3. Not waiting for completion: Interrupted healing leaves inconsistent routes
  4. Forgetting after changes: New devices won’t have optimal routes without healing

54.5 Z-Wave Security

Z-Wave has evolved through multiple security frameworks:

54.5.1 Security Generations

Z-Wave security evolution timeline showing progression from no security in legacy devices through S0 security (2003-2016) with weak key exchange, to modern S2 security (2017+) with three levels

54.5.2 Security Framework Comparison

Feature No Security S0 Security S2 Unauthenticated S2 Authenticated S2 Access Control
Encryption None AES-128 AES-128 AES-128 AES-128
Authentication No Weak None DSK DSK + PIN
Key Exchange N/A Insecure ECDH ECDH ECDH
Replay Protection No Basic Nonce Nonce Nonce
Key Verification N/A No No Yes Yes
Use Case Legacy Legacy Basic devices Smart home Locks, alarms
Overhead 0% ~30% ~15% ~15% ~15%
Battery Impact Lowest High Medium Medium Medium

:::

54.6 Z-Wave Plus and Z-Wave Long Range

54.6.1 Z-Wave Plus (2013, updated 2020)

Z-Wave Plus is a certification program with enhanced features:

Key Improvements:

  • Better Range: ~30% longer range than Classic
  • More Battery Life: ~50% improvement
  • Better RF Performance: 500-series and 700-series chips
  • Self-Healing: Improved automatic route optimization
  • Over-The-Air Updates: Firmware updates via Z-Wave
  • Beaming: Wake battery devices for incoming commands
  • Network Wide Inclusion: Add devices from anywhere in network
  • S2 Security: Mandatory in Plus v2

54.6.2 Z-Wave Long Range (2020)

Z-Wave LR extends range dramatically for large properties:

Z-Wave Long Range (LR) architecture showing star topology with up to 1km range from controller to each device, compared to classic mesh topology with 100m range between hops

Z-Wave LR Features:

  • Range: Up to 1 km (vs ~100m for Classic)
  • Data Rate: 100 kbps (same as Classic)
  • Topology: Star (no mesh)
  • Use Case: Large properties, agriculture, industrial
  • Coexistence: Can run alongside classic Z-Wave

Comparison:

Feature Z-Wave Classic/Plus Z-Wave Long Range
Range 30-100m Up to 1 km
Topology Mesh Star (direct to controller)
Routing Multi-hop Single-hop only
Battery Life Years Years (similar)
Use Case Home automation Large areas, agriculture
Devices 232 per network 2000+ per controller

54.7 Z-Wave vs Zigbee vs Thread

The three main mesh protocols for home automation each have distinct characteristics:

Comparison radar chart showing Z-Wave, Zigbee, and Thread across dimensions of range, device capacity, cost, interoperability, and IP native support

Feature Z-Wave Zigbee Thread Wi-Fi
Frequency Sub-GHz (868/908 MHz) 2.4 GHz 2.4 GHz 2.4/5 GHz
Max Devices | 232 | 65,000 | 250 | ~250 |
Range (indoor) | 30-100m | 10-30m | 10-30m | 50-100m |
Data Rate | 100 kbps | 250 kbps | 250 kbps | 1-1000 Mbps |
Mesh Type | Source routing | Table routing | Table routing | No (standard) |
Native IP | No | No | IPv6 | Yes |
Power draw | Very low | Very low | Very low | High |
Interference risk | Low | High | High | High |
Interoperability | High | Medium | High | Very high |
Typical cost | High | Low | Low | Medium |

Quick read:

  • Z-Wave: best when you want sub-GHz range and strict interoperability.
  • Zigbee: best when you need large node counts at low device cost.
  • Thread: best when Matter and IP-native integration matter most.
  • Wi-Fi: best when bandwidth is critical and power draw is acceptable.

54.7.1 Protocol Strengths and Weaknesses

Z-Wave Strengths

Advantages:

  • Longer range (sub-GHz penetrates walls better)
  • Less interference (dedicated frequency band)
  • Guaranteed interoperability (strict certification)
  • Mature ecosystem (20+ years)
  • Single vendor consistency (Silicon Labs)

Disadvantages:

  • Proprietary (licensing fees, vendor lock-in)
  • Regional frequencies (devices not globally compatible)
  • Lower device limit (232 vs 65,000 Zigbee)
  • Higher cost (licensing fees passed to consumer)
  • No native IP (cannot connect directly to internet)
Zigbee Strengths

Advantages:

  • Open standard (no licensing fees)
  • Massive scale (65,000 devices)
  • Lower cost per device
  • Global frequency (2.4 GHz worldwide)

Disadvantages:

  • Shorter range (2.4 GHz)
  • 2.4 GHz interference (Wi-Fi, Bluetooth, microwaves)
  • Interoperability issues (Zigbee vs Zigbee 3.0, profiles)
  • No native IP support
Thread Strengths

Advantages:

  • Native IPv6 (direct internet connectivity)
  • Matter ecosystem (Apple, Google, Amazon support)
  • Open standard (no licensing)
  • Modern design (built for IoT from ground up)

Disadvantages:

  • Newer (less mature, smaller ecosystem)
  • Shorter range (2.4 GHz)
  • 2.4 GHz interference
  • Requires border router (gateway to internet)

54.8 Hands-On Lab: Z-Wave Network Design

Design a Z-Wave network for a two-story house with the following requirements:

54.8.1 Scenario

  • Floor 1: Living room, kitchen, garage, front door
  • Floor 2: 3 bedrooms, 2 bathrooms
  • Devices: Smart lock (front door), lights (all rooms), motion sensors (living room, hallways), thermostat, garage door opener

54.8.2 Design Exercise

  1. Identify device types: Which are mains-powered (routers) vs battery-powered (slaves)?
  2. Plan placement: Ensure mesh coverage with no “dead zones”
  3. Security levels: Assign appropriate S2 levels to each device
  4. Healing strategy: When should network healing occur?

Device Classification:

Device Power Type Z-Wave Role S2 Level
Smart Lock Battery Slave S2 Access Control
Lights (8) Mains Routing Slave S2 Authenticated
Motion Sensors (3) Battery Slave S2 Authenticated
Thermostat Mains Routing Slave S2 Authenticated
Garage Door Mains Routing Slave S2 Access Control

Mesh Coverage Strategy:

  • Place mains-powered lights strategically as repeaters
  • Ensure at least 2 routing slaves between controller and any slave
  • Living room light acts as central hub for Floor 1
  • Hallway light connects floors

Healing Schedule:

  • Daily at 3 AM (automatic)
  • Manual heal after adding/moving any mains-powered device
  • Monthly full network optimization

54.9 Common Pitfalls and Best Practices

Scenario: A homeowner moves a Z-Wave smart plug from hallway to basement after 6 months of operation. Battery-powered sensors in upstairs bedrooms start failing intermittently.

Initial Network (Working):

Controller (Living Room)
  ↓ 8m, -50 dBm
Kitchen Switch
  ↓ 10m, -55 dBm
Hallway Plug (WAS HERE)
  ↓ 6m, -48 dBm
Upstairs Motion Sensor (Bedroom 1)

Route stored in controller routing table:
Controller → Kitchen → Hallway Plug → Bedroom 1 Sensor
Total: 3 hops, 24m, weakest link -55 dBm

After Relocation (Broken):

Homeowner moves Hallway Plug to Basement (20m from Kitchen)

Controller tries stored route:
Controller → Kitchen → Hallway Plug (NOT THERE) → [TIMEOUT]

Kitchen Switch can't reach Hallway Plug at new basement location
Route fails, controller marks Bedroom 1 Sensor as "unreachable"

Step-by-Step Healing Process:

1. Controller Detects Route Failure

T=0s: Controller sends command to Bedroom 1 Sensor
T=0.15s: Kitchen forwards to old Hallway Plug location
T=0.50s: No ACK received (timeout after 300ms)
T=0.60s: Controller retries with backup route (if available)
T=1.20s: All backup routes fail
T=1.30s: Controller marks device as "unreachable"

2. User Initiates Network Heal

# Home Assistant Z-Wave JS UI
Settings → Z-Wave → Actions → "Heal Network"

# SmartThings IDE
My Hubs → Z-Wave Utilities → "Repair Z-Wave Network"

# Homey Pro
Settings → Z-Wave → "Optimize Network"

3. Heal Sequence for 25-Device Network:

T=0min: Controller broadcasts "Neighbor Discovery Request"
T=1min: All routing slaves report their neighbors
  - Kitchen Switch reports: Controller (RSSI -50), Upstairs Switch (-62)
  - Basement Plug reports: Kitchen (-68), Laundry Light (-55)
  - No report of Kitchen → Hallway Plug link (too far now)

T=5min: Controller runs Dijkstra's algorithm to find new routes
  For Bedroom 1 Sensor:
    Old route (broken): Controller → Kitchen → Hallway Plug (X)
    New route candidate 1: Controller → Kitchen → Upstairs Switch → Sensor
      (3 hops, weakest -62 dBm)
    New route candidate 2: Controller → Living Room Dimmer → Upstairs → Sensor
      (3 hops, weakest -58 dBm) ← SELECTED (better weakest link)

T=8min: Controller tests new route by sending test frame
T=8.2s: ACK received, route validated
T=10min: Controller updates routing table for Bedroom 1 Sensor
T=15min: Healing complete (25 devices total)

4. Verification:

# Check new route
Device: Bedroom 1 Motion Sensor
Route: Controller → Living Room Dimmer → Upstairs Switch → Sensor
Hops: 3
Weakest Link: -58 dBm
Last Successful: Just now
Retry Count: 0
Status: Online ✓

Key Insights:

Metric Before Move After Move (Broken) After Heal
Route Kitchen → Hallway → Sensor Kitchen → Hallway (X) Living Room → Upstairs → Sensor
Hops 3 Failed 3
Weakest Link -55 dBm N/A -58 dBm
Success Rate 100% 0% 100%
Heal Time N/A N/A 15 minutes

Real Numbers from This Scenario:

  • 25 devices in network
  • 1 device relocated (Hallway Plug)
  • 3 devices affected (upstairs sensors using old route)
  • 15 minutes to complete full heal
  • 0 devices required re-inclusion

Why Automatic Healing Didn’t Work:

Z-Wave Plus has "background healing" but it only activates when:
1. Controller detects 3+ consecutive failed routes, AND
2. Device hasn't communicated in 24+ hours

In this case:
- Sensor is battery-powered (wakes every 240 seconds)
- Each wake attempt fails, but spread over time
- Automatic healing threshold not met fast enough
- Manual heal was faster (15 min vs waiting 24+ hours)

Prevention for Future:

  1. Run heal immediately after any device relocation
  2. Test affected devices before considering move permanent
  3. Document network topology to predict routing dependencies
  4. Use Z-Wave network health tools to identify weak links proactively
Pitfall Cards: Avoid These Mistakes

54.9.1 Pitfall 1: Mixing S0 and S2 Security

Problem: Including legacy S0 devices in an S2 network creates a security weakness - S0 key exchange is vulnerable to interception.

Solution: When possible, use S2-only networks. If S0 devices are required, segment them to non-critical functions (e.g., basic lighting, not locks).

54.9.2 Pitfall 2: Dead Zones from Poor Router Placement

Problem: Battery-powered devices (slaves) cannot relay messages. If all devices near a slave are also battery-powered, the slave becomes unreachable.

Solution: Ensure mains-powered devices (routing slaves) are placed strategically to provide mesh coverage. Rule of thumb: every slave should have at least 2 routing slaves within range.

54.9.3 Pitfall 3: Regional Frequency Mismatch

Problem: Z-Wave devices operate on region-specific frequencies (US: 908.42 MHz, EU: 868.42 MHz, AU: 921.42 MHz). Devices from one region won’t communicate with another.

Solution: Always purchase devices certified for your region. Check the “Z-Wave Region” specification before buying.

54.9.4 Pitfall 4: Exceeding 4-Hop Limit

Problem: Z-Wave allows maximum 4 hops per message. Very large homes or buildings may exceed this, causing unreachable devices.

Solution:

  • Position the controller centrally
  • Use Z-Wave Long Range for large properties (single-hop, 1km range)
  • Add routing slaves to reduce hop count

54.9.5 Pitfall 5: Healing During Peak Usage

Problem: Network healing can cause brief communication disruptions. Triggering healing during active use (e.g., evening when automation is busy) frustrates users.

Solution: Schedule automatic healing for 2-4 AM when the home is typically inactive. Never heal during security system arming/disarming or other critical operations.

54.10 Summary and Key Takeaways

54.10.1 Core Concepts

Concept Key Point
Source Routing Controller determines complete path before sending; route embedded in packet header
Network Healing Rediscovers optimal routes; essential after network topology changes
S2 Security Modern ECDH-based security with three levels; mandatory for Z-Wave Plus v2
Z-Wave LR 1km range with star topology; ideal for large properties and agriculture

54.10.2 Decision Guide

Decision tree for choosing between Z-Wave, Zigbee, and Thread based on requirements like range, device count, and Matter support

54.10.3 Key Formulas and Numbers

Metric Value
Z-Wave Classic Range 30-100m indoor
Z-Wave LR Range Up to 1 km
Max Classic Devices 232 per network
Max LR Devices 2000+ per controller
S2 Overhead ~15% (vs 30% for S0)
Sub-GHz Advantage +8.4 dB vs 2.4 GHz path loss

Challenge: Design a Z-Wave network for a 3,000 sq ft two-story home with these requirements:

Devices to add:

  • 1 smart lock (front door, battery-powered)
  • 8 smart light switches (mains-powered)
  • 3 motion sensors (battery-powered)
  • 1 thermostat (mains-powered)
  • 1 garage door opener (mains-powered)

Tasks:

  1. Classify devices by role (controller, routing slave, battery slave)
  2. Draw a floor plan and mark device locations
  3. Identify routing paths - which devices will act as repeaters?
  4. Assign S2 security levels - which devices need Access Control vs Authenticated?
  5. Plan hop counts - is the smart lock within 4 hops of the controller?
  6. Schedule healing - when and how often should network healing run?

Expected outputs:

  • Floor plan diagram with Z-Wave mesh topology
  • Device classification table
  • Security level assignments with justifications
  • Healing schedule

What to observe:

  • Do battery devices have at least 2 routing slaves within range?
  • Are critical devices (lock, garage) within 3 hops of controller?
  • Is S2 Access Control used for entry points (lock, garage)?
  • Does healing schedule avoid disrupting daily routines?

Reflection questions:

  • What happens if you remove one mains-powered light switch from the hallway?
  • How would you extend coverage to a detached garage 25m away?
  • Why is it important to have multiple mains-powered devices on each floor?

54.11 What’s Next

Chapter Focus Link
Z-Wave Network Planning Hands-on device placement and mesh design exercises Open
Z-Wave Simulation and Assessment ESP32 Wokwi lab, production framework, and 30+ quiz questions Open
Zigbee Fundamentals Compare Z-Wave source routing with Zigbee AODV distributed routing Open
Thread Network Architecture IPv6-native mesh protocol and Matter ecosystem integration Open
IoT Security Fundamentals Broader security concepts beyond Z-Wave S2 Open
Practice Recommendations
  1. Hands-on: Set up a small Z-Wave network with a hub and 3-4 devices
  2. Experiment: Try network healing after moving a device
  3. Compare: If possible, test Z-Wave vs Zigbee range in your environment
  4. Simulate: Use the Protocol Comparison Tool to explore trade-offs