This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Unhandled signal 17. Status: 0

Hello.

I'm working for a Zigbee networking project.I chose nRF52840 as the coordinator.The coordinator acts as a gateway to communicate with Zigbee 3.0 devices on the market that support HA 1.2.

I test the networking function through the nRF5SDKforThreadandZigbee20029775ac/examples/zigbee/experimental/cli/cli_agent_router.When nRF52840 accepted Micro Door Sensor 3323-C joined the network, the following problems arose:

<info> app: Unhandled signal 16. Status: 0
<info> app: Unhandled signal 2. Status: 0
<info> app: Unhandled signal 17. Status: 0

<info> app: Unhandled signal 16. Status: 0
<info> app: Unhandled signal 2. Status: 0
<info> app: Unhandled signal 17. Status: 0

It looks like the device has joined the network, but it will exit in a few seconds.

The state will continue to cycle like this.

I used the advice on the forum:

zb_bdb_set_legacy_device_support(1); // To support legacy Zigbee device

comm_status = bdb_start_top_level_commissioning(ZB_BDB_NETWORK_STEERING);

ZB_COMM_STATUS_CHECK(comm_status);

or

zb_bdb_set_legacy_device_support(0); // To support legacy Zigbee device

comm_status = bdb_start_top_level_commissioning(ZB_BDB_NETWORK_STEERING);

ZB_COMM_STATUS_CHECK(comm_status);

But I find that nothing seems to have changed.

I would like to ask the Nordic developer team what I should do to solve this problem?

Related