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.
Part Number: CC2652P
I am planning to create a zigbee coordinator on CC2652P using SIMPELINK-CC13X2-26X2-SDK Z-Stack with ZigBee 3.0 support.
I would like to know if the device will be interoperable with legacy ZigBee PRO HA,SE and ZLL devices. my network has some old sensors and lights and meters based on legacy HA,SE and ZLL on ZigBee PRO.
I wanted to understand if its possible to join the legacy devices to the ZigBee 3.0 based coordinator and retrieve data from the legacy devices.
Is there any documentation present for interoperability between zigbee 3.0 and legacy devices?
SIMPLELINK-CC13X2-26X2-SDK v4.30 Z-Stack 3.0 Coordinators will allow legacy devices to join if BDB_DEFAULT_TC_REQUIRE_KEY_EXCHANGE is FALSE (default). There are several relevant E2E threads which can be referenced.
To better aid the community, please click on the "This Resolved my issue" button whenever a post answers your question!
We are glad that we were able to resolve this issue, and will now proceed to close this thread.
If you have further questions related to this thread, you may click "Ask a related question" below. The newly created question will be automatically linked to this question.
For HA and ZLL devices, it's interoperable as Ryan mentioned to set BDB_DEFAULT_TC_REQUIRE_KEY_EXCHANGE to FALSE but SE profile device is usually another story which is not compatible to Zigbee 3.0.
If my post answers your question, please click on "This Resolved my issue" button to benefit others who have the same issue.
Comparision on Zigbee, Z-Wave, and Z-Wave Long range.
Build OpenThread Sleepy End Device doorlock prototype to test with Rasperry Pi OpenThread Border Router
How to use two UARTs in CC26x2 and CC13x2
SwitchBot DIY using LPSTK-CC1352R , SG90 servo motor, and ProjectZero to away from COVID-19.
How to use two endpoints in SIMPLELINK-CC13X2-26X2-SDK Z-Stack.
How to create a periodic event to toggle BLE Advertising in CC26xx simple_peripheral example
How to use indication in simple_peripheral example and use Btool to enable indication
How to detect button hold in CC26x2, CC13x0, CC13x2 SDK.
660 Zigbee devices in the same Zigbee network!
In reply to Ryan Brown1:
Thanks for the response.
what does BDB_DEFAULT_TC_REQUIRE_KEY_EXCHANGE = FALSE means? There will not be any security enabled for the network?
I am expecting my coordinator centralized to be trust center and have install codes and dynamic key change functionality.
In reply to vikas k:
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.
In reply to YiKai Chen:
Hi YK Chen,
So it is not possible to join the legacy SE devices to ZigBee 3.0 coordinator.
My customer has a requirement to join legacy SE devices to ZigBee 3.0 coordinator and gather information from SE devices.
As YK mentioned previously, Zigbee 3.0 is not backwards compatible with legacy SE. Your customer will need to consider updating their legacy solution or seek alternative devices to join the 3.0 network. Removing the security features necessary to allow SE devices to join is not an option in the SIMPLELINK-CC13X2-26X2-SDK.
They have smart meters based on SE profile.When you say "updating their solution" what does that mean ? upgrade to zigbee 3.0 ? Does TI support that ?
" seek alternative devices to join the 3.0 network" - Does this mean that use some other devices which support ZigBee 3.0 ?
it is not possible to join the legacy SE devices to ZigBee 3.0 coordinator.
My requirement is as below :
The coordinator is based on ZigBee 3.0 specification.The network will containZigBee3.0 coordinator, zigbee 3.0 routers, legacy HA and ZLL devices. The ZigBee 3.0 coordinator should be able to join zigbee3.0 routers ,legacy HA and ZLL devices.
Based on your repose above in order for legacy HA and ZLL device to join ZigBee 3.0 coordinator BDB_DEFAULT_TC_REQUIRE_KEY_EXCHANGE should be set to FALSE. Will there be an issue for joining another ZigBee 3.0 device to the coordinator while the macro is set to false ?
Also I would like to know if the ZigBee 3.0 coordinator support touch link commissioning for ZLL devices.
Other than coordinator all other devices used in the network will be off the shelf devices available in market.
vikas kWill there be an issue for joining another ZigBee 3.0 device to the coordinator while the macro is set to false ?
vikas kAlso I would like to know if the ZigBee 3.0 coordinator support touch link commissioning for ZLL devices.
All content and materials on this site are provided "as is". TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with regard to these materials, including but not limited to all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement of any third party intellectual property right. No license, either express or implied, by estoppel or otherwise, is granted by TI. Use of the information on this site may require a license from a third party, or a license from TI.
TI is a global semiconductor design and manufacturing company. Innovate with 100,000+ analog ICs andembedded processors, along with software, tools and the industry’s largest sales/support staff.