How to Make nRF52840 as Zigbee HA1.2 Coordinator

RE: How to Make nRF52840 as Zigbee HA1.2 Coordinator

uldara — Sun, 10 Mar 2019 10:50:02 GMT

Dear tomchy

i can add zigbee devices to Coordinator, but i didn't see and traffic from device.

i'm sure device connected with coordinator how to enable traffic log ?

Thanks

RE: How to Make nRF52840 as Zigbee HA1.2 Coordinator

tomchy — Sat, 09 Mar 2019 18:51:53 GMT

Hi UL Dara,

There should be no need to register a key. It should just work You code looks fine.

I would put the "zb_bdb_set_legacy_device_support(0);" a couple of lines further, after checking status to be RET_OK. That way, this code will be executed only if the coordinator is able to create a new Zigbee network.

What is the current status of your interoperability test? Were you able to add new devices using my advices?

RE: How to Make nRF52840 as Zigbee HA1.2 Coordinator

bjorn-spockeli — Thu, 21 Feb 2019 14:57:41 GMT

The key you posted appears to be the same used in the example, i.e. the one found in nRF5_SDK_for_Thread_and_Zigbee_v2.0.0\external\zboss\include\zb_config.h , on line 161.

/* 5.1.2.3.2 test specification - The default value for DUT-GPP being a Basic Combo pr a Basic Proxy
* is "ZigBeeAlliance09", i.e. {0x5A 0x69 0x67 0x42 0x65 0x65 0x41 0x6C 0x6C 0x69 0x61 0x6E
* 0x63 0x65 0x30 0x39}. */
#define ZB_ZGP_DEFAULT_LINK_KEY "ZigBeeAlliance09"

RE: How to Make nRF52840 as Zigbee HA1.2 Coordinator

uldara — Mon, 11 Feb 2019 04:31:45 GMT

Dear tomchy

Tanke for your reply

The code put like this right ?

and how to put requited key

void zboss_signal_handler(zb_uint8_t param)
{
    /* Read signal description out of memory buffer. */
    zb_zdo_app_signal_type_t sig = zb_get_app_signal(param, NULL);
    zb_ret_t                 status = ZB_GET_APP_SIGNAL_STATUS(param);
    zb_ret_t                 zb_err_code;
    zb_bool_t                comm_status;

    switch(sig)
    {
        case ZB_BDB_SIGNAL_DEVICE_FIRST_START: // Device started and commissioned first time after NVRAM erase.
        case ZB_BDB_SIGNAL_DEVICE_REBOOT:      // BDB initialization completed after device reboot, use NVRAM contents during initialization. Device joined/rejoined and started.
           
            zb_bdb_set_legacy_device_support(0);
            if (status == RET_OK)
            {
                NRF_LOG_INFO("Device started OK. Start network steering.");
                bsp_board_led_on(ZIGBEE_NETWORK_STATE_LED);
                comm_status = bdb_start_top_level_commissioning(ZB_BDB_NETWORK_STEERING);
                ZB_COMM_STATUS_CHECK(comm_status);
            }
            else
            {
                NRF_LOG_ERROR("Device startup failed. Status: %d. Retry network formation after 1 second.", status);
                bsp_board_led_off(ZIGBEE_NETWORK_STATE_LED);
                zb_err_code = ZB_SCHEDULE_ALARM(bdb_restart_top_level_commissioning, 0, ZB_TIME_ONE_SECOND);
                ZB_ERROR_CHECK(zb_err_code);
            }
            break;

        case ZB_BDB_SIGNAL_STEERING:
            if (status == RET_OK)
            {
                /* Schedule an alarm to notify about the end of steering period */
                NRF_LOG_INFO("Network steering started");
                zb_err_code = ZB_SCHEDULE_ALARM(steering_finished, 0, ZB_TIME_ONE_SECOND * ZB_ZGP_DEFAULT_COMMISSIONING_WINDOW);
                ZB_ERROR_CHECK(zb_err_code);
            }
            else
            {
                NRF_LOG_INFO("Network steering failed to start. Status: %d. Retry network formation after 1 second.", status);
                bsp_board_led_off(ZIGBEE_NETWORK_STATE_LED);
                zb_err_code = ZB_SCHEDULE_ALARM(bdb_restart_top_level_commissioning, 0, ZB_TIME_ONE_SECOND);
                ZB_ERROR_CHECK(zb_err_code);
            }
            break;

        case ZB_ZDO_SIGNAL_PRODUCTION_CONFIG_READY:
            if (status != RET_OK)
            {
                NRF_LOG_WARNING("Production config is not present or invalid");
            }
            break;

        default:
            /* Unhandled signal. For more information see: zb_zdo_app_signal_type_e and zb_ret_e */
            NRF_LOG_INFO("Unhandled signal %d. Status: %d", sig, status);
            break;
    }

    /* All callbacks should either reuse or free passed buffers. If param == 0, the buffer is invalid (not passed) */
    if (param)
    {
        ZB_FREE_BUF_BY_REF(param);
    }
}

Thank

RE: How to Make nRF52840 as Zigbee HA1.2 Coordinator

tomchy — Fri, 08 Feb 2019 21:50:41 GMT

Hi UL Dara,

there is one, ultimately important point mentioned by Bjørn:

A Zigbee Home Automation device can join a Zigbee 3.0 Centralized Network that does not require a key exchange.

The key exchange is required in Nordic's coordinator example by default. I know this causes a lot of headaches, when you try to do some interoperability tests, but consider it as a security precaution.

There is an API to disable/enable this so-called compatibility mode. It can be called after ZB_BDB_SIGNAL_DEVICE_FISRT_START/REBOOT signals. For debug purposes, it may be wise to just call it inside zboss_signal_handler, upon reception of those signals.

I hope this helps 🙂. For further investigation of your case, you may try to post traffic dump from the failed attempt. There is a nrf52840-based sniffer available on github to do so.

RE: How to Make nRF52840 as Zigbee HA1.2 Coordinator

bjorn-spockeli — Thu, 07 Feb 2019 16:15:19 GMT

Hi UL Dara,

you can try taking a look at the this thread:

https://devzone.nordicsemi.com/f/nordic-q-a/33683/zigbee-coordinator-with-xiaomi-devices

It goes through some of the steps on how to swap the key.

RE: How to Make nRF52840 as Zigbee HA1.2 Coordinator

uldara — Wed, 06 Feb 2019 05:04:23 GMT

Dear bjorn-spockeli

secret key required for Zigbee authentication is "5A:69:67:42:65:65:41:6C:6C:69:61:6E:63:65:30:39"

faire-ca-soi-meme.fr/.../

RE: How to Make nRF52840 as Zigbee HA1.2 Coordinator

bjorn-spockeli — Tue, 05 Feb 2019 10:00:17 GMT

No, I do not think we have any example where a nRF52840 communicates with a HA1.2 device out of the box. The examples we have in the SDK doesn't contain the secret key required for Zigbee authentication. You would need to be a Zigbee alliance member to acquire the key.

RE: How to Make nRF52840 as Zigbee HA1.2 Coordinator

uldara — Tue, 05 Feb 2019 09:11:40 GMT

Thank you bjorn-spockeli

i just start up on ZigBee

do you have sample code for this option ?

Thank

RE: How to Make nRF52840 as Zigbee HA1.2 Coordinator

bjorn-spockeli — Tue, 05 Feb 2019 08:33:51 GMT

The Zigbee 3.0 specification is backwards compatible with the Zigbee Home Automation 1.2 profile, as long as the Zigbee 3.0 device is configured as such. So our Zigbee 3.0 stack should be backwards compatible with Zigbee Home Automation (HA) 1.2 devices. The limitations are listed below

A Zigbee Home Automation device can join a Zigbee 3.0 Centralized Network that does not require a key exchange.
A Zigbee Home Automation device can NOT join a Zigbee 3.0 distributed network.
A Zigbee 3.0 device can join either a Zigbee Light Link or a Zigbee Home Automation network using classical commissioning.

RE: How to Make nRF52840 as Zigbee HA1.2 Coordinator

uldara — Tue, 05 Feb 2019 03:47:58 GMT

HIbjorn-spockeli

I bought some modules from market that support ZigBee HA1.2

and i want to use nRF52840 as ZigBee Coordinator,

I tested example Light coordinator but Sensor module not joint to this coordinator

and I see nRF52840 running on ZigBee 3.0 that why i don't know how to make it work with Zigbee HA1.2

Thank

RE: How to Make nRF52840 as Zigbee HA1.2 Coordinator

bjorn-spockeli — Mon, 04 Feb 2019 13:36:31 GMT

Hi UL Dara,

the nRF52840 comes with a Zigbee PRO stack, see Zigbee stack features and you can find examples in the nRF5 SDK for Thread and Zigbee . I suggest taking a look at the Zigbee Light Control example, it provides a minimal implementation of the following devices:

Light coordinator - demonstrates the Zigbee Coordinator role, which supports only the network steering commissioning mechanism.
Light switch - demonstrates the Zigbee End Device role, implementing the Dimmable Light Switch profile.
Light bulb - demonstrates the Zigbee Router role, implementing the Dimmable Light profile.

Best regards

Bjørn