This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

CC1352P: Zigbee 3.0 device joining a legacy network as a FFD

Part Number: CC1352P
Other Parts Discussed in Thread: Z-STACK

I'm looking for some feedback on whether a ZStack 3.0 FFD device can join a ZStack 1.2 network when security has been disabled.  

#define SECURE 0

#define ZG_SECURITY_MODE ZG_SECURITY_NONE

I saw this similar question on the forum: https://e2e.ti.com/support/wireless-connectivity/zigbee-and-thread/f/158/t/661590?CC2652R-Will-ZigBee-3-0-Be-Backwards-Compatible-

Also, per the Zigbee.org site, it states that: https://www.zigbee.org/zigbee-for-developers/zigbee-3-0/

It is interoperable

    • Certification ensures device-to-device interoperability
    • A single application language provides for multi-vendor ecosystems
    • Designed for forward and backward compatibility
      • Legacy devices may join a Zigbee 3.0 network
      • Zigbee 3.0 devices will join legacy networks

In my ZStack 3.0 device, I tried to simply set zgSecurityMode = ZG_SECURITY_NONE; before calling Zstackapi_bdbStartCommissioningReq().  With wireshark I see the beacon/association request/response, but I don't get a zstackmsg_CmdIDs_DEV_STATE_CHANGE_IND.  This causes our device to time-out and attempt to join again.

Is there something else that can be done?

Thanks,

- Bill