CC2652P: Zigbee 3.0 device interoperability with legacy HA,SE and ZLL devices

Hi Ryan/Chen,

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.

Thanks,

Vikas

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.

Thanks,

Vikas

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.

Regards,
Ryan

Hi Ryan,

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 ?

Thanks,

Vikas

YK Chen,

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.

Thanks,

Vikas