CC2652P: reporting with Zstackapi_bdbRepChangedAttrValueReq() freezing the device

Hi Roberto,

Has your zcl_genericapp.c application used Zstackapi_bdbRepAddAttrCfgRecordDefaultToListReq to add default configuration values for the reportable attribute record and does both this function and bdb_ProcessInConfigReportCmd return successfully?  Are you stating that the Zstackapi_bdbRepChangedAttrValueReq API is not able to enter bdb_RepChangedAttrValue (followed by bdb_RepReport) for further debugging?  What is the call stack when you end inside sendReqDefaultRsp?

Regards,
Ryan

Hi Ryan, thank you.

I did not call Zstackapi_bdbRepAddAttrCfgRecordDefaultToListReq, which should not be useful for me if i send an explicit configure report message from the Z2M frontend with the correct parameters. Is it correct?

I just called Zstackapi_bdbRepChangedAttrValueReq alone in my routine and was freezing the device, it enters sendReqDefaultRsp, then OsalPort_msgSend and at that point debugging was very hard for some reason, (debug pointer jumping not linearly and finishing in disassembly), so i just knew it never sends that message to the bdb task.

So.. i changed the optimization level from z to 0 and it works perfectly, and debugging over there goes as expected and OsalPort_msgSend returns successfully. I double checked it returning to z and it freezes again, for now i'm not going to think about it.

Now, i do not want to have to send manually a configure report from the Z2M frontend page, so (if i understood well enough) i need to use Zstackapi_bdbRepAddAttrCfgRecordDefaultToListReq to send myself a configure report message to the zstack task, is it true?

If so, i'm using it in this way inside zclGenericApp_Init()

    //Make the attribute reportable
    uint8_t repChange[] = {0,0,0,0};
    OsalPort_memcpy(Req.reportableChange, repChange, BDBREPORTING_MAX_ANALOG_ATTR_SIZE /*4*/);
    Req.attrID = ATTRID_IOV_BASIC_PRESENT_VALUE;
    Req.cluster = ZCL_CLUSTER_ID_GENERAL_ANALOG_INPUT_BASIC;
    Req.endpoint = RFID_ENDPOINT;
    Req.maxReportInt = BDBREPORTING_NOPERIODIC;
    Req.minReportInt = BDBREPORTING_NOLIMIT;

    if (Zstackapi_bdbRepAddAttrCfgRecordDefaultToListReq(appServiceTaskId, &Req) != zstack_ZStatusValues_ZSuccess) {
        // Failed to make the attribute reportable
        LED_setOn(gRedLedHandle, LED_BRIGHTNESS_MAX);
    }

and it returns successfully, but still no report is sent when Zstackapi_bdbRepChangedAttrValueReq is called. Until i send again an explicit configure report message from the Zigbee2Mqtt instance, in that case it finally starts to send them.

I have put a breakpoint inside processBdbProcessInConfigReportReq which contains bdb_ProcessInConfigReportCmd, as i expected to enter there after Zstackapi_bdbRepAddAttrCfgRecordDefaultToListReq sent the message successfully to the zstack task.

What am i missing?

EDIT:

Zstackapi_bdbRepAddAttrCfgRecordDefaultToListReq sends a message to the zstack task which enters

processBdbRepAddAttrCfgRecordDefaultToListReq that enters

bdb_RepAddAttrCfgRecordDefaultToList

and that last function returns successfully, but still the reports are not sent until an explicit configure report from Z2M

EDIT 2:

debugging the Zstackapi_bdbRepChangedAttrValueReq called without effect, i see that it exits here inside bdb_RepChangedAttrValue

  if( bdb_reportingClusterEndpointArray[indexClusterEndpoint].consolidatedMaxReportInt == BDBREPORTING_REPORTOFF )
  {
    //reporting if off for this cluster
    return ZSuccess;
  }

that consolidatedMaxReportInt is 0xFFFF... But in the Zstackapi_bdbRepAddAttrCfgRecordDefaultToListReq request i have maxInterval to 0

Ok, thank you, could you please indicate the right Bind Request api to call to do such thing in order to avoid the need of zigbee2mqtt side configuration? I'm looking at this doc but it is not clear to me how to create the bind from my devices to the coordinator

Thank you Ryan, i solved this issue some minutes ago using the "configure" section of my Z2M custom converter configuration in order to send to the device the right configure report messages and bindings just after the pairing.

Now, an rfid tag is detected, the device sends an attribute report and Z2M convert it in an MQTT message containing a field like this { ...., "rfid":3.9265504009152834e-40}.

This is certainly not the most clean solution, ignoring the fact that presentValue attribute has float type.

Do you have any advice on a better cluster attribute in which i can pass my rfid code in order to notify it to the server?

This will depend on your attribute's data type and how Zigbee2MQTT processes messages from each attribute.  I suggest contacting the Zigbee2MQTT developers for further assistance.

Regards,
Ryan