nRF52 SDK 2.2.0 change default Zigbee channel and join existing non-nRF network

[dan.r]

Hi,

 While using either the Zigbee Light Bulb or the Zigbee Template examples from SDK V2.2.0 on an nRF52840 DK, it just keeps printing `I: Network steering was not successful (status: -1)`.

After a bit of searching, I found this "Nordic Devzone: Join existing Zigbee network with light bulb example" which leads me to believe that the default Zigbee channel is 16.

Is that still the case for the examples I'm using from SDK V2.2.0 ? If yes, then where is the `#define IEEE_CHANNEL_MASK` setting that this post mentions? I can't find it and would like to change it to either searching all channels or limiting it to channel 25.

If that doesn't work, I'll explore other options. For context, I'm using Zigbee2MQTT with a CC2652P2 coordinator. As far as I know, this is just using standard Zigbee.

Kind regards,

Dan

[Marte Myrvold]

Hi Dan,

Correct, the default channel in the Zigbee samples is 16. To change to a different (single) channel, you can set CONFIG_ZIGBEE_CHANNEL in prj.conf, for example:

CONFIG_ZIGBEE_CHANNEL=13

You can choose between two channel selection modes, single-channel mode, which is set by CONFIG_ZIGBEE_CHANNEL_SELECTION_MODE_SINGLE and enabled by default, and multi-channel mode, which can be enabled by setting CONFIG_ZIGBEE_CHANNEL_SELECTION_MODE_MULTI. When using the multi-channel mode, you can use CONFIG_ZIGBEE_CHANNEL_MASK to configure a custom set of channels or use the default 0x7FFF800.

Best regards,
Marte

[dan.r]

Hi Marte,

I just updated from SDK V2.2.0 to SDK 2.3.0 and the Zigbee channel setting reset back to 16. How can I make this and other settings permanent through SDK updates?

I used the kconfig menu to set the Zigbee channel.

How do I use the kconfig menu to set multi channel mode?

Kind regards,
Dan

[Marte Myrvold]

Hi Dan,

If you set it in the GUI menu, the configurations are set in configuration files inside the build directory. Thus, deleting the build directory will cause the configurations to no longer be set, and the same might be true for pristine builds. To ensure the configurations are permanent, you can configure them in prj.conf instead.

Best regards,
Marte