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?

Parents
  • Hello,

    Can you try to add the ZB_ZDO_SIGNAL_DEVICE_ANNCE event to your zboss_signal_handler() in main.c and see if it hits? Just addNRF_LOG_INFO("ZB_ZDO_SIGNAL_DEVICE_ANNCE"); to the event, and you should see whether it happens or not.

    Best regards,

    Edvin

  • Yes, I've tried it. After adding ZB_ZDO_SIGNAL_DEVICE_ANNCE to Main.c,NRF_LOG_INFO ( "ZB_ZDO_SIGNAL_DEVICE_ANNCE") did happen.Because we see the "<info> app:unhandled signal 2."
    Status:0 "is actually ZB_ZDO_SIGNAL_DEVICE_ANNCE.

    I guess since we've seen ZB_ZDO_SIGNAL_DEVICE_ANNCE happen, is it possible to say that the Zigbee protocol version of the two devices is the same or compatible? The most important thing is that after a few seconds, we can see ZB_ZDO_SIGNAL_LEAVE_INDICATION, which is <info>app:unhandled SIGNAL 17. Status:0, this problem has prevented me from doing the next step.

  • Hello,

    I don't know if you saw, but we recently released SDK for Thread And Zigbee v 3.0.0.

    Can you (in your current implementation) please check the zb_zdo_signal_leave_indication_params_t.rejoin? Is it 0 or 1?

    What sort of device is your door sensor? Is it something that you have made? Does it require something specific that the CLI maybe haven't set up?

    BR,

    Edvin

Reply
  • Hello,

    I don't know if you saw, but we recently released SDK for Thread And Zigbee v 3.0.0.

    Can you (in your current implementation) please check the zb_zdo_signal_leave_indication_params_t.rejoin? Is it 0 or 1?

    What sort of device is your door sensor? Is it something that you have made? Does it require something specific that the CLI maybe haven't set up?

    BR,

    Edvin

Children
No Data
Related