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:

            {
                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:

    //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.

[Marjeris Romero]

Hi Armand,

Did you check that the light switch is using the same Zigbee channel as the Smarthings hub? And can you attach the sniffer logs so I can see what is going on between the two?

And I just want to add that the main goal of the examples on the SDK is to demonstrate different features of the Zigbee stack, and unless it is explicitely said so on the testing instructions of the example, they are not intended for use with 3rd party devices such as Smarthings hub right out of the box. This doesn't mean there is an "issue" with the stack, you just have to modify the example for your intended purpose.

For instance, you should set the IEEE_CHANNEL_MASK (located in main.c) to cover multiple channels if you are not sure which channel your Smarthigns hub network is on (all of our examples use only Zigbee channel 16 as default). Set IEEE_CHANNEL_MASK to 0x07fff800U, in order to use all 802.15.4 defined channels as indicated here.

For the sleepy end device issue look inside sleepy_device_setup(). When putting the device into sleepy mode you need to press the SLEEPY_ON_BUTTON so zb_set_rx_on_when_idle is set to ZB_FALSE (RX off when idle, see here and here), in your code zb_set_rx_on_when_idle is set to  ZB_TRUE.

Best regards,

Marjeris

[Patrick]

What I have found, and I've only used SDK 3.2 long enough to discover this problem and do a little troubleshooting before abandoning it, is that application code that previously connected to a SmartThings hub and operated normally with SDK 3.1 now experiences an issue during the join process. Flash was completely erased, clearing any stored parameters from its previous pairing with the hub.

When attempting to pair with the SmartThings hub using SDK 3.2 the hub does not seem to detect the device in such a way that it is able to finish the pairing process. The end device does however get to a point where it receives a "Device Can Sleep" packet. The log output then indefinitely reports that the device can sleep for small intervals.

Obviously without logs this will be difficult to solve. If Armand is not able to provide wireshark captures and trace logs I can either do that here or in another ticket.

[Marjeris Romero]

Hi Patrick,

I think it's a good idea you make a ticket for this other issue so I can follow it more closely and don't mix it up here Also please mention which SDK example you are trying to connect (and do you have the same issue with the light_bulb example as well? is this happening with all SDK examples or just the one?) and also please attach the sniffer trace.

BR,

Marjeris

[Patrick]

I think the core issue is the same between what Armand is describing and what I have added. The difference is that Armand is experiencing this error with code based on the light switch example in SDK 3.2 and my application is a derivative of multi-sensor, originally compiled using SDK 3.1 that now does not connect to the hub when compiled using SDK 3.2.

I will make some time to try again with SDK 3.2 and get a sniffer trace and create a new ticket.

[Zigbee Team]

Which version of the SmartThings hub you have?

Kind regards,

Zigbee team

[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