Back to Protocols Overview
Protocol Blueprint

Z-Wave, ZWLR & Low-Power Automation Protocols

Standardized internationally as ITU-T G.9959, Z-Wave operates in dedicated sub-1GHz spectrum far below congested 2.4 GHz Wi-Fi. With Security 2 (S2) authenticated encryption and Z-Wave Long Range (ZWLR) star networking, it bridges home automation with mile-range commercial telemetry.

01 · ITU-T G.9959 Physical and MAC Architecture

Z-Wave defines three standardized data rates across its sub-1GHz channel allocations (908.4 MHz / 916.0 MHz in North America, 868.4 MHz in Europe):

  • R1 (9.6 kbps): Legacy 2-FSK with Manchester encoding. Retained for backwards compatibility with early 100/200-series nodes.
  • R2 (40 kbps): 2-FSK with NRZ encoding. Standard telemetry rate for 300/400-series nodes.
  • R3 (100 kbps): GFSK (BT=0.5BT = 0.5) with NRZ encoding. Standard high-speed channel for modern 500, 700, and 800-series hardware. Z-Wave Long Range does not use it: ZWLR has its own 100 kbps DSSS-OQPSK PHY.
PreambleSOF (1–2B)Home ID (4B)Source (1–2B)Frame Ctrl (1B)Length (1B)Dest (1–2B)Payload (Var)Checksum (1–2B)
0101 Sync0xF05532-bit Net IDTransmitterRouting FlagsByte CountRecipientCommand ClassXOR / CRC-16
Frame FieldField SizeFunctional Role & Wire Protocol Detail
Preamble10–24 BytesContinuous alternating 0101 bit sequence to allow receiver AGC settling and symbol clock recovery
SOF (Start of Frame)1 ByteHardware frame delimiter (0x0F for 9.6/40 kbps, 0xF055 for 100 kbps GFSK) signaling start of MAC data
Home ID4 Bytes32-bit unique network identifier assigned by the primary controller; separates adjacent neighboring networks
Source Node ID1 Byte (Classic) / 2 Bytes (LR)Node ID of the transmitting device (1–232 for Classic mesh, 1–4000 for Z-Wave Long Range)
Frame Control1–2 BytesFrame type (Singlecast, Broadcast, Multicast, ACK), routed hop flags, and header length options
Length1 ByteTotal length of the payload and subsequent header fields in bytes
Destination Node ID1 Byte (Classic) / 2 Bytes (LR)Node ID of target recipient or 0xFF for unencrypted network broadcast
Payload (Command Class)Var (up to 64B)Application layer command class, command byte, and structured parameter payload
Checksum / CRC-161–2 BytesXOR checksum (9.6/40 kbps) or CRC-16-CCITT (100 kbps and ZWLR). Errored packets dropped in hardware

02 · Command Classes (CC) & Application Layer

Z-Wave standardizes device behaviors using modular Command Classes. Every device exposes a Node Information Frame (NIF) listing supported classes so the hub controller knows exactly how to query and command it:

COMMAND_CLASS_BASIC (0x20)

The universal fallback class. A value of 0x00 turns off, while 0xFF turns on or opens to full scale.

COMMAND_CLASS_SWITCH_BINARY (0x25)

Controls physical relays, contactors, and smart wall switches with explicit Set, Get, and Report command frames.

COMMAND_CLASS_SENSOR_MULTILEVEL (0x31)

Encodes high-precision sensor telemetry (temperature, humidity, atmospheric pressure, power watts) with precision scales and signed byte encodings.

COMMAND_CLASS_DOOR_LOCK (0x62)

Electronic deadbolt and security actuator controls; strictly encapsulated within Security 2 (S2) Access Control encryption.


03 · Security 2 (S2) Cryptographic Architecture

Legacy Z-Wave Security 0 (S0) suffered from serious design flaws: it required three round-trip nonce handshakes for every single encrypted frame (destroying battery life and causing noticeable command lag) and exposed network keys during inclusion if an observer captured the plain-text exchange.

Security 2 (S2) replaced S0 with modern cryptographic primitives:

  • Key Exchange: Elliptic Curve Diffie-Hellman (ECDH) on Curve25519 ensures forward secrecy during secure inclusion.
  • Authenticated Encryption: AES-128-CCM (Counter with CBC-MAC) provides both confidential data encryption and 8-byte Message Authentication Code (MAC) integrity protection.
  • Single-Frame Delivery: S2 maintains synchronized pseudo-random sequence generators between nodes, allowing encrypted commands to be delivered in a single over-the-air frame with zero round-trip latency.
S2 Security ClassClass IdentifierKey Exchange Requirement & Target Devices
S2 Unauthenticated0x01No PIN/DSK verification during inclusion. Used for simple sensor devices lacking physical interfaces where rogue impersonation risk is low.
S2 Authenticated0x02Requires entering or scanning the 5-digit Device Specific Key (DSK) PIN printed on the device chassis. Prevents rogue node injection on wall switches and plugs.
S2 Access Control0x04Highest privilege tier. Reserved for electronic door deadbolts, garage door openers, and security barriers with strict authentication checks.

04 · Z-Wave Long Range (ZWLR): The Star Topology Shift

While classic Z-Wave connects devices through a repeating mesh limited to 4 hops and 232 nodes, Z-Wave Long Range (ZWLR) completely eliminates the mesh in favor of a direct point-to-point star topology:

4,000 Node Capacity

Node IDs expand from 8-bit (1–232) to 12-bit (1–4000), allowing massive commercial facilities, apartment complexes, and hotels to operate under a single controller.

1-Mile Line-of-Sight Range

Operating under FCC Part 15.247 rules on 912 MHz and 920 MHz with up to +30 dBm (1 W) conducted power, ZWLR communicates across outdoor properties and perimeter gates without relay nodes.

Dynamic Power Control (DPC)

The gateway measures link quality on every packet and instructs the battery node to throttle transmit power to the exact minimum needed. This prevents spectrum saturation and extends coin-cell battery life up to 10 years.


05 · Automation Protocol Comparison

How Z-Wave and ZWLR compare against competing smart home wireless protocols:

ProtocolRF BandTopologyMax NodesWi-Fi CoexistenceLine-of-Sight RangeSecurity StackIdeal Field Application
Z-Wave ClassicSub-1GHz (908/868 MHz)4-Hop Mesh232Zero Interference (Sub-1GHz)30–100 m / hopSecurity 2 (S2 AES-CCM)Whole-home reliable residential automation
Z-Wave Long RangeSub-1GHz (912/920 MHz)Star (Direct to AP)4,000Zero Interference (Sub-1GHz)1.6+ km (1 mile)Security 2 (S2 AES-CCM)Large estates, perimeter gates, commercial facilities
Zigbee / Thread2.4 GHz (802.15.4)Full MeshHundredsShares 2.4 GHz spectrum (needs Ch 15/20/25)10–30 m / hopAES-128-CCMSmart bulbs, sensors, Matter cross-vendor ecosystem
Bluetooth LE Mesh2.4 GHzManaged Flood Mesh32,767Heavy 2.4 GHz frequency hopping contention10–20 m / hopAES-128-CCM (Dual-layer)Commercial architectural lighting controls

Site search