Hey Matt,
Any SIMPLELINK-CC13XX-CC26XX-SDK device which supports Z-Stack (those listed included) uses the Zigbee 3.0 Specification which is backwards compatible with legacy Zigbee Home Automation and Zigbee Light Link Specifications.
A ZigBee Light Link…
Hello Halil,
If using a Z-Stack 3.0 coordinator then please make sure that BDB_DEFAULT_TC_REQUIRE_KEY_EXCHANGE is set to FALSE in the bdb_interface.h file. You could also reference the older Z-STACK-ARCHIVE solutions if necessary, however the CC2530 is not…
Hi Krishna,
Limiting ZDSECMGR_TC_DEVICE_MAX will work only if Zigbee 3.0 devices are joining, however it will not apply for Zigbee HA 1.2 nodes or other legacy specifications which join. You could set BDB_DEFAULT_TC_REQUIRE_KEY_EXCHANGE to TRUE but this…
If the Leave Request now occurs about five seconds after association and there is no TCLK Update Request, you will need to make sure that BDB_DEFAULT_TC_REQUIRE_KEY_EXCHANGE on the ZC is FALSE.
Regards, Ryan
Hi Shuyang,
The SimpleLink SDK has BDB_DEFAULT_TC_REQUIRE_KEY_EXCHANGE set to FALSE by default. It is not possible to send the NWK Key without encryption. I understand that the global TCLK is used to transport the Network Key but you can set a pre-confi…
Z-Stack 3.0 is interoperable with Z-Stack HA 1.2.2a so long as BDB_DEFAULT_TC_REQUIRE_KEY_EXCHANGE is set to FALSE (i.e. define TP2_LEGACY_ZC)
Regards, Ryan
BDB_DEFAULT_TC_REQUIRE_KEY_EXCHANGE = FALSE means using Zigbee HA 1.2 security to encrypt network key with TC link key and don’t do TC link key exchange defined in Zigbee 3.0 spec.
Hello YiKai Chen ,
I am not able to understand your point, will you please eloborate your question?.
I am using default version of all type of software applications.
I found that,
In CC1352 znp application BDB_DEFAULT_TC_REQUIRE_KEY_EXCHANGE is set FALSE…