Reference / Hardware
Zigbee networks: plan devices, messages and maintenance
Zigbee combines radio networking with a shared application language for connected devices. A usable installation also needs defined device roles, commissioning, security, an application data model, a power budget and recovery after failure.
Choose by message and maintenance needs
Start with payload, reporting interval, latency tolerance, device count and battery-replacement plan. Occasional telemetry is different from a control loop or a device that must receive commands quickly.
A mesh can offer alternate paths, but it needs placement and powered routing participants. Test realistic walls, interference, firmware behaviour and loss of a mains-powered node.
Plan commissioning and interoperability
A radio module can simplify RF design but cannot automatically make applications interoperable. Define device types, joining, key protection and replacement of a lost controller.
Verify joining, normal reporting, power loss, reset and secure removal. Treat claimed range as a scenario to test, not as a substitute for an installed-site measurement.
Design the device lifecycle
Decide who owns a device after installation, how it receives updates and what happens when a tenant, battery or controller changes. Commissioning is only the beginning of operation.
Keep factory-reset behaviour controlled. A reset that silently rejoins a network or exposes an actuator can turn maintenance into a security event.