← Back to the chapter · Previous detail
Technical detail · Z-Wave for Smart Homes
Read classic identifier fields
Classic network identity is equally concrete:
| Classic field | Width | Wire-level purpose | Operational meaning |
|---|---|---|---|
| Home ID | 4 bytes (32 bits) | separates frames belonging to different classic Z-Wave networks | shared network identifier assigned/managed by the primary controller |
| Node ID | 1 byte (8 bits) | identifies a classic node within that Home ID | device address; only the protocol-defined subset is assignable, giving the familiar 232-node classic limit |
| : Classic Z-Wave identifiers must be read together, not as globally unique device identity. |
A Node ID is meaningful only with its Home ID. It is not a serial number and it can be reused in another network. Security keys, command classes, controller records, and inclusion state remain separate fields. For packet logs and fleet records, capture at least Home ID, Node ID, controller, device identity, security class, route role, and observation time so “Node 7” cannot be confused across networks or after a controller migration.
Check three independent compatibility boundaries before inclusion with Figure 5.
The regional-SKU view separates EU 868.42 MHz from US 908.4 MHz hardware. The identity view separates the 4 B Home ID from the 1 B Node ID. The modulation view locates Gaussian filtering at the baseband-to-GFSK boundary.