Nrf router and end device with Digi Xbee Coordinator

[Yash_2]

Hello,

I am using nrf sdk 1.5.1 and trying to connect the Nrf ZigBee router(light bulb example) with Digi Xbee Coordinator but it doesn't seem to connect. I observed the same when I tried to connect nrf end device(light switch example). 

Note - the digi xbee coordinator is tested and working with the digi end device and router

I have attached the sniffer log for more information.

IG_nrfRouter.pcapng

Any help on this is appreciated.

Thanks and Regards,

Yash.

[Yash_2]

Hello Jorgen,

While searching for API's to disable the n/w link key transfers I stumbled upon these API's -

ZBOSS - Compile-time configuration parameters
Link -developer.nordicsemi.com/.../group___z_b___c_o_n_f_i_g.html

#define ZB_ROUTER_SECURITY //Defines router security

And found these as well ->

Would either of those be used to disable the Transport key exchange step?

If not, can you please suggest what changes I can do to make it work?

Thanks and Regards,

Yash.

[run_ar]

Hi,
I am sorry, we are currently a little low on zigbee competence due to vacations (and will be for a couple of weeks). But I will try to forward your question to the developers to see if they can help answer your quesiton. I am sorry for the inconvenience.

[run_ar]

Hi,

Yash_2 said:

But considering that the coordinator will not send the Transport key, are there any changes(config or code changes) that I can make in the nrf_router/nrf_endDevice that will skip past those transport key steps?

Here is the answer I got from the zigbee team when forwarding your question:

I don't think so. First, make sure that Digi Xbee Coordinator is configured correctly so it can work with our Zigbee router.

For example, have the customer enabled securtiy at Xbee device? (Encryption Enable (EE) parameter must be set to 1)

[Smart.Enrg]

Thanks run_ar,

run_ar said:

Here is the answer I got from the zigbee team when forwarding your question:

I don't think so. First, make sure that Digi Xbee Coordinator is configured correctly so it can work with our Zigbee router.

For example, have the customer enabled securtiy at Xbee device? (Encryption Enable (EE) parameter must be set to 1)

I am working with Yash on this. Couple of follow-up questions for the team, if you will please: 
1) Digi Xbee based ZC is a 3rd party device already installed in the field, we are trying to connect 
     nRF52833 based ZED, ZR devices to it. As such, we've limited control over ZC's configuration.
     I mean - we can't change settings (like enable security), that will break things for other devices
     on this otherwise working, deployed network, right?

2) Like your recommendation to enable encryption on ZC side; which I agree with but not allowed
    to do:( - is there a way to disable encryption on our side? - i.e. in nRF52833 nRF Connect SDK
    (preferable), or nRF5 (if we must)?

Please advise. Thanks again.

[run_ar]

Hi,

I asked the ZB team, and here is what they say:

1. Most probably, according to XBee documentation:

Enable security

To enable security on a device, the Encryption Enable (EE) parameter must be set to 1. When the parameter value changes, the XBee module leaves the network (PAN ID and channel) it was operating on and attempt to form or join a new network. If you set EE to 1, all data transmissions are encrypted with the network key.

2. I don't think this is possible to completely disable encryption on our side - I am not aware of any API nor configuration option. Also, this is an unusual approach to completely disable security/encryption for the whole network.