| Security |
Encryption and authentication |
Zigbee uses AES-128 encryption at the network and application security layers. Secure key establishment and authenticated joining help prevent unauthorized access. |
Confirm that commissioning uses authenticated joining, install codes, or an equivalent secure onboarding process. |
10% |
0–5 |
| Firmware maintenance |
Connected products require vulnerability fixes over time. Zigbee devices may support over-the-air firmware updates, but implementation depends on the device and controller. |
Look for signed firmware, encrypted update delivery, rollback protection, update history, and a published support policy. |
8% |
0–5 |
| Privacy and cloud dependency |
Zigbee communication is local radio communication, but a controller may still send data to cloud services for remote access, analytics, or integrations. |
Check local-control capabilities, data-retention terms, account security, remote-access settings, and whether essential automations work without the cloud. |
7% |
0–5 |
| Network access control |
A Zigbee network uses a network key, and joining devices must be admitted by the coordinator or an authorized process. |
Verify that joining can be closed after installation, unknown devices can be removed, and network credentials can be changed or restored securely. |
5% |
0–5 |
| Reliability |
Mesh routing and coverage |
Zigbee mesh networks can route traffic through powered devices. Battery-powered end devices normally rely on a parent device and do not act as routers while sleeping. |
Test the farthest rooms, thick walls, metal cabinets, and the recovery time after a router is unplugged. |
12% |
0–5 |
| Interference management |
Zigbee commonly operates in the 2.4 GHz band, which is shared with Wi-Fi and Bluetooth. Channel selection and physical placement affect performance. |
Check available channels, perform a radio-environment scan, and keep the coordinator away from Wi-Fi access points, USB 3.0 devices, and metal enclosures. |
8% |
0–5 |
| Power resilience |
Mains-powered Zigbee devices can extend a mesh, while battery devices depend on battery condition, sleep behavior, and parent connectivity. |
Check battery reporting, low-battery alerts, coordinator backup power options, and whether critical devices remain available during an internet outage. |
7% |
0–5 |
| Latency and recovery |
Local Zigbee control can reduce dependence on internet round trips, but response time varies with routing, congestion, sleeping devices, and controller software. |
Measure repeated commands, device rejoin behavior, automation execution during internet loss, and recovery after coordinator restart. |
8% |
0–5 |
| Scalability |
Device capacity |
The practical device limit is determined by the coordinator, routing table, memory, firmware, traffic patterns, and device types rather than by one universal Zigbee limit. |
Obtain the controller's documented supported-device range and test the planned number of routers, sensors, and frequent automations. |
10% |
0–5 |
| Interoperability |
Zigbee profiles and certified device behavior improve compatibility, but optional features, clusters, firmware, and controller support can still differ. |
Confirm the exact device model, supported clusters, certification status, binding support, and compatibility with the intended controller before purchase. |
8% |
0–5 |
| Expansion and migration |
A larger installation needs documented backups, network migration options, stable device identifiers, and a clear process for replacing the coordinator. |
Check backup and restore procedures, export options, coordinator replacement steps, and the availability of local APIs or standards-based integrations. |
7% |
0–5 |
| User Experience |
Setup and pairing |
Zigbee devices must join a coordinator-controlled network. Pairing quality depends on onboarding flow, reset instructions, signal conditions, and device support. |
Score the number of steps, clarity of instructions, failure messages, retry process, and time required to add and name a device. |
8% |
0–5 |
| Automation and control |
Smart-home automation may run locally or through cloud services. Local execution generally provides better resilience when internet access is unavailable. |
Test schedules, scenes, conditions, notifications, device-to-device binding, permissions, and behavior during internet and power interruptions. |
6% |
0–5 |
| Diagnostics and maintenance |
Mesh networks require practical visibility into signal quality, routing, battery levels, unavailable devices, and firmware status. |
Prefer dashboards with link-quality indicators, last-seen timestamps, route information, battery alerts, logs, and actionable troubleshooting guidance. |
4% |
0–5 |