Part Number: LAUNCHXL-CC1352R1
Hello,
I successfully managed that the ZigBee Switch-example (simplelink_cc13x2_26x2_sdk_3_20_00_68\examples\rtos\CC1352R1_LAUNCHXL\zstack\zed_sw) running on a CC1352R1-Launchpad (Board #1) is detected by the zigbee2mqtt-gateway (www.zigbee2mqtt.io) , i got the message "interview successful" when subscribing to the MQTT broker. In the sniffer i see the exchange of three ZCL_CMD_READ commands with each 3 attributes and their corresponding ZCL_CMD_READ_RSP commands, where e.g. the attributes "ATTRID_BASIC_MODEL_ID", "ATTRID_BASIC_MANUFACTURER_NAME", "ATTRID_BASIC_POWER_SOURCE" etc. are requested from the zed_switch by the coordinator.
Now i want to "clone" the behaviour of the zed_sw_CC1352R1_LAUNCHXL_tirtos_ccs-project with a ZNP (running also on a CC1352 hardware, Board #2). I wrote a ZTool script that configure an endpoint with the same clusters like in the zed_sw-firmware.
Nevertheless, the coordinator of the zigbee2mqtt gateways behaves differently and terminates the communication after the first "read attribute" command, as i can see in the sniffer-logs. The result is an "interview failed" message of the mqtt gateway.
My questions:
1. Can anybody help me to figure out why my ZNP-node (Board #2) behaves differently than the board #1 programmed with the zed_sw program? Why is the coordinator not requesting the second and third "read attributes" command? Please see my both Ubiqua capture-files.
Because the coordinator is the same in both scenarious, i guess there is something i am missing in my ZNP script, making its behaviour not 100% equal to that of board #1. But i do not see any difference in the sniffer logs.
2. Does anybody know how the internal logic of the zigbee2mqtt "interview"-process works? Where is it programmed that the coordinator starts with asking for the e.g. Model-ID attribute? It would be nice if i could get out some more debug-info from the zigbee2mqtt-gateway, showing me why the interview-process actually failed.
Thanks a lot for every help,
best regards Albert
(Please visit the site to view this file)