LP-CC2652RB: ZC Controller - get connection from third party end devices

Do you enable permit join on your coordinator to allow device to join?

If it is not the default setting, then no.

How can permit join added?

Try to refer to steps in dev.ti.com/.../node

This is what I get following the instructions - still could not connect and not sure how to allow device join. TI devices join in the first minute or after pushing a button, but ZTE does not seem to be able to connect to the LP.

Great help, thank you very much.

I have one question left - not sure if there should be a new topic, I just ask here and will open a new topic if required.

I just added a printf to zclSampleLight_processZStackMsgs and see the following messages coming:

0xC8 zstackmsg_CmdIDs_BDB_TC_LINK_KEY_EXCHANGE_NOTIFICATION_IND

0xE5 zstackmsg_CmdIDs_GP_CHECK_ANNCE

when pairing is done.  Excellent!

However, I see nothing when and actual door open/close is done - it looks like that is not making its way into zclSampleLight_processZStackMsgs.

0xC5 zstackmsg_CmdIDs_BDB_NOTIFICATION

0xC6 zstackmsg_CmdIDs_BDB_IDENTIFY_TIME_CB

are seen in zclSampleLight_processZStackMsgs after that. As far as I could find out in the docs, those are base device behavior notifications so not the open / close messages.

Is it possible that 0xC8 means TI only and there is some need to change the config to get open/close messages? Or do I need add a callback somewhere?

I must be doing something wrong. I imported zc_cie, added printf into zclSampleCIE_ProcessIncomingMsg and zclSampleCIE_processZStackMsgs but still nothing printed for open and close.

ZCL_ZONE is defined and also put a printf to zclSampleCIE_ChangeNotificationCB but that is not called either.

I also can see that 0x91 Discover zones are coming up and can be initiated from the example GUI but that is not implemented in there. Maybe if that would be handled and the button could be added to the zone then it should work?

zclSampleCIE_WriteIAS_CIE_Address is the only one what is called from #ifdef ZCL_ZONE part of code from the example, as far as I can see.

Sorry for the fragmented post in many parts.

So, when I click Discover Zone here then zclSampleCIE_ProcessIncomingMsg receives a 0x91 zstackmsg_CmdIDs_AF_DATA_CONFIRM_IND message what has no handler implemented.  That happens a couple of times during the pairing process, too.

Is it the case that this has to be implemented - or how do I add it to any zone so the door open / close would trigger something - because it is not now.

Hi Sandor,

Please read the zc_cie README to further understand how this example is intended to operate.  You can also find more information from a another recent E2E thread.  You should also consider implementing a Zigbee Packet Sniffer so that you can see what packets are actually occurring over-the-air.  Ultimately the third-party end device manufacturer should be able to explain what ZCL cluster/attribute environment is necessary for communication.

Regards,
Ryan

Hi Ryan,

I can do the sniffing... I read the documentation and not getting much closer.

I mean: probably a battery operated door switch and a wired controller is a very basic use case. So I was just hoping for a simple example. Just like like the zc_light + zed_switch. Is there actually a small example which is like zc_light + zed_door_switch (1 zc and 1 zed)? Or is it the case really that Zigbee is not a standard?

Thank you,

Sandor

TI provides multiple Z-Stack examples for various ZCL variations such as light or switch, temperature sensor and thermostat, doorlock and controller, or CIE and zone/warningdevice.  Developers are then allowed to modify any of these as necessary for the purposes of their specific use case.  This forum will be able to assist with any questions that arise during the further evaluation of these SDK projects.  I cannot comment further on the operation and usage requirements of a third-party device.

Regards,
Ryan

OK, thank you.

Is there a TI zed_door_switch example?

The Zigbee applications accomplish basic ZCL cluster/application functionality, specific application usage must be further created by developers.  SampleApp does include an Occupancy Sensor as one of its Application Builder Zigbee Device Types.

Regards,
Ryan

You can refer to zed_zone example at https://dev.ti.com/tirex/explore/node?node=A__ABHVGBLBILGlmwZg99QwVw__com.ti.SIMPLELINK_CC13XX_CC26XX_SDK_ZSTACK_MODULE__BSEc4rl__LATEST as code base for door sensor implementation.