Light switch nRF5 on SDK for Thread and Zigbee v3.2 will not join network

[Ignacio]

Hi,

As simple as the title! I have tried to move my code from sdk v 3.1 to v3.2 but it will not join the network.

Back to basics and using off-the-box ligh switch example. Also, this example will not join the network (testing with a smartthings hub).

I have also detected a issue when setting the device as sleepy end device. I have changed the following on the example:

- On line 551:

Fullscreen

1

2

3

4

5

{

zb_zdo_signal_can_sleep_params_t *can_sleep_params = ZB_ZDO_SIGNAL_GET_PARAMS(p_sg_p, zb_zdo_signal_can_sleep_params_t);

NRF_LOG_INFO("Can sleep for %ld ms", can_sleep_params->sleep_tmo);

zb_sleep_now();

}

XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

            {
                zb_zdo_signal_can_sleep_params_t *can_sleep_params = ZB_ZDO_SIGNAL_GET_PARAMS(p_sg_p, zb_zdo_signal_can_sleep_params_t);
                NRF_LOG_INFO("Can sleep for %ld ms", can_sleep_params->sleep_tmo);
                zb_sleep_now();
            }

- On line 601:

Fullscreen

1

2

//sleepy_device_setup();

zb_set_rx_on_when_idle(ZB_TRUE);

XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

    //sleepy_device_setup();
    zb_set_rx_on_when_idle(ZB_TRUE);

Not sure if this related to the main issue, but the device will report a sleep time of 998ms but it will not sleep for that time. I will just keep reporting the sleep time but not going to sleep.

[Patrick]

Version 3.

As things usually go, once I moved my project back to SDK 3.2 to get some captures I was able to get the device connected and operating as expected (with exception to a random device lock-up after about a week, but that is an issue I'll have to investigate in another thread).

[Zigbee Team]

OK good to hear that it works. We were just about to get our SmartThings hub out of the closet ;)

Kind regards,

Zigbee team