How many devices can a RapidConnect-based Coordinator support on one network?

Maximum network size is influenced by numerous factors, including the following:

• Overall network traffic

• Primary Network Function

  • For example, sensor devices typically don't generate much traffic. They mainly “report in” their data to the coordinator (aka Concentrator). There is rarely a need for the coordinator or other devices to control/configure sensors.

  • On the other hand, if there are many devices that require constant communication with the coordinator, then the network complexity rises and the number of devices which will reliably operate on the network is reduced. 

• Hardware that RapidConnect is running on

  • More RAM enables larger networks. Host applications can store more EUI - NodeID bindings. 

• Security policy of the network

  • Zigbee 3.0 requires unique link keys for every device, so all of these links keys must be stored in a table. We are working on enabling RapidConnect to offload that key storage to a Host MCU

• Neighbor Device Table: Neighbour device tables allow devices to store information on other Router devices on the network, allowing for a mesh network. In RapidHA/RapidConnect, the Neighbour Device Table can hold 16 router devices.

• Child Device Table: Child device tables hold entries for network End devices, which do not have message routing capabilities and have no child devices. In RapidHA/RapidConnect, the Child device Table can hold 6 end device entries.

Obviously, it is difficult to state an exact number of nodes that can be supported in all deployments. That said, MMB and our customers have built networks of 50+ nodes without seeing any issues.