Zigbee: Network coordinator
This Zigbee Network coordinator sample establishes the Zigbee network and commissions Zigbee devices that want to join the network.
The sample supports the following development kits:
You can use one of the development kits listed above.
Optionally, you can use this sample with one or both of the following samples:
The Zigbee Light bulb sample programmed on one or more separate devices.
The Zigbee Light switch sample programmed on one or more separate devices.
You can mix different development kits.
This Zigbee Network coordinator sample demonstrates the Zigbee Coordinator role and implements two clusters (Basic and Identify) that used to be required by the Zigbee Home Automation profile. It is a minimal implementation that supports only the network steering commissioning mechanism. The Basic cluster provides attributes and commands for determining basic information about the node. The Identify cluster allows to set the device into the identification mode, which provides a way to locate the device.
See Configuring your application for information about how to permanently or temporarily change the configuration.
You can add support for the nRF21540 front-end module to this sample by using one of the following options, depending on your hardware:
Build the sample for one board that contains the nRF21540 FEM, such as nrf21540dk_nrf52840.
Manually create a devicetree overlay file that describes how FEM is connected to the nRF5 SoC in your device. See Set devicetree overlays for different ways of adding the overlay file.
Provide nRF21540 FEM capabilities by using a shield, for example the nRF21540 EK shield that is available in the nRF Connect SDK. In this case, build the project for a board connected to the shield you are using with an appropriate variable included in the build command. This variable instructs the build system to append the appropriate devicetree overlay file. For example, to build the sample from the command line for an nRF52833 DK with the nRF21540 EK attached, use the following command within the sample directory:
west build -b nrf52833dk_nrf52833 -- -DSHIELD=nrf21540_ek
This command builds the application firmware. See Programming nRF21540 EK for information about how to program when you are using a board with a network core, for example nRF5340 DK.
Each of these options adds the description of the nRF21540 FEM to the devicetree. See Working with RF front-end modules for more information about FEM in the nRF Connect SDK.
To add support for other front-end modules, add the respective devicetree file entries to the board devicetree file or the devicetree overlay file.
- LED 1:
Blinks to indicate that the main application thread is running.
- LED 3:
Indicates whether the network is open or closed:
On - The network is open.
Off - The network is closed.
- LED 4:
Blinks when the Network coordinator is in Identify mode.
- Button 1:
Reopens the network for 180 seconds.
The network is also opened after startup.
- Button 4:
Depending on how long the button is pressed:
If pressed for less than five seconds, it starts or cancels the Identify mode.
If pressed for five seconds, it initiates the factory reset of the device. The length of the button press can be edited using the
CONFIG_FACTORY_RESET_PRESS_TIME_SECONDSKconfig option from Zigbee application utilities. Releasing the button within this time does not trigger the factory reset procedure.
Make sure to configure the Zigbee stack before building and testing this sample. See Configuring Zigbee in nRF Connect SDK for more information.
This sample can be found under
samples/zigbee/network_coordinator in the nRF Connect SDK folder structure.
To build the sample with Visual Studio Code, follow the steps listed on the How to build an application page in the nRF Connect for VS Code extension documentation. See Building and programming an application for other building and programming scenarios and Testing and debugging an application for general information about testing and debugging in the nRF Connect SDK.
After programming the sample to your development kit, complete the following steps to test it:
Turn on the development kit that runs the coordinator sample.
When LED 1 starts blinking, the main application thread has started.
When LED 3 turns on, this development kit has become the Coordinator of the Zigbee network and the network is established.
Turn on the other development kits that you programmed.
When LED 3 turns on the development kit that runs the Light bulb sample, it has become a Router inside the network.
When LED 3 turns on the development kit that runs the Light switch sample, it has become an End Device, connected directly to the Coordinator.
If LED 3 on the development kits does not turn on, press Button 1 on the Coordinator to reopen the network.
Optionally, if you are testing with both the Light bulb and the Light switch samples, complete the following additional steps:
Wait until LED 4 on the development kit that runs the Light switch sample turns on.
This LED indicates that the switch found a light bulb to control.
Use buttons on the development kit that runs the Light switch sample to control the light bulb, as described in the Light switch sample’s user interface section.
The result of using the buttons is reflected on the light bulb’s LED 4.
You can now use buttons on the light switch to control the light bulb, as described in the User interface section of the Light switch sample page.
This sample uses the following nRF Connect SDK libraries:
This sample uses the following sdk-nrfxlib libraries:
In addition, it uses the following Zephyr libraries: