LAUNCHXL-CC1352R1: Z2M does not receive any reports

Hello Jan,

The zed_light project does not have BDB reporting enabled by default.  Please follow Task 2 of the Zigbee Fundamentals SLA and reference the default zed_temperaturesensor example to enable this functionality.

Regards,
Ryan

Your light project is a joiner device (ZED) and needs to create the bind locally.  Therefore you are correct that the light project will broadcast device announce messages and not receive them.  Thus you should be taking action after becoming a ZED joined to a network, so I recommend:

1. Checking if zstackmsg_devStateChangeInd_t -> zstack_devStateChangeInd_t -> zstack_DevState is zstack_DevState_DEV_END_DEVICE inside of the zstackmsg_CmdIDs_DEV_STATE_CHANGE_IND case.
2. Reading network information with Zstackapi_sysNwkInfoReadReq.
3. Create the manual bind with Zstackapi_ZdoBindReq where
   1. Destination address is the local device
   2. Source address is the Z2M device
   3. IEEE (i.e. long) addresses are used

        case zstackmsg_CmdIDs_DEV_STATE_CHANGE_IND:
        {
#if !defined(CUI_DISABLE) || defined(USE_DMM) && defined(BLE_START)
            // The ZStack Thread is indicating a State change
            zstackmsg_devStateChangeInd_t *pInd =
                (zstackmsg_devStateChangeInd_t *)pMsg;
#endif // !defined(CUI_DISABLE) || defined(USE_DMM) && defined(BLE_START)

#ifndef CUI_DISABLE
            UI_DeviceStateUpdated(&(pInd->req));
#endif
            if(pInd->req.state == zstack_DevState_DEV_END_DEVICE)
            {
                zstack_sysNwkInfoReadRsp_t pRsp;
                Zstackapi_sysNwkInfoReadReq(appServiceTaskId, &pRsp);
                
                zstack_zdoBindReq_t pReq;
                pReq.nwkAddr = pRsp.nwkAddr;
                pReq.bindInfo.clusterID = ZCL_CLUSTER_ID_GENERAL_ON_OFF;
                pReq.bindInfo.srcEndpoint = SAMPLELIGHT_ENDPOINT;
                pReq.bindInfo.dstAddr.addrMode = (zstack_AFAddrMode)Addr64Bit;
                pReq.bindInfo.dstAddr.endpoint = Z2M_ENDPOINT; // DEFINED AND KNOWN FROM Z2M
                OsalPort_memcpy(pReq.bindInfo.dstAddr.addr.extAddr, &(pRsp.parentExtAddr), Z_EXTADDR_LEN);  //ASSUMES Z2M IS THE PARENT
                OsalPort_memcpy(pReq.bindInfo.srcAddr, &(pRsp.ieeeAddr), Z_EXTADDR_LEN);

                Zstackapi_ZdoBindReq(appServiceTaskId, &pReq);
            }

This is untested pseudo-code which makes assumptions and should be thoroughly tested against your environment.  If the Z2M destination endpoint is unknown, or if the Z2M ZNP is not guaranteed to be the parent (assumed destination address bind address in the example), then further Zigbee messages will need to be transferred over-the-air to query the Z2M ZNP and obtain the correct bind information.

Regards,
Ryan