CC1352P: Disable Coordinator Default Responses

Hi Randy,

Please clarify, are you use a standalone Zigbee Coordinator or Zigbee Network Processor (ZNP) controlled by a Linux host application?  I'm also unsure as to what your use case intends to accomplish.  The Zstackapi_AfDataReq command contains parameter zstack_afDataReq_t -> zstack_TransOptions_t -> ackRequest which determines the APS ACK.  You can control the ZCL default response with AF_ACK_REQUEST from zcl_registerClusterOptionList, like in the Zigbee Fundamentals SLA.  Although one would typically want the "Disable Default Response" bit set in the ZCL of a Default Response message.

Regards,
Ryan

Hi Randy,

Thank you for providing more information.  Can you please provide a sniffer log that demonstrates the Read Attribute Request?  Have you added the necessary cluster attribute records to the endpoint on the host ZCL application?  Community members have also provided advice for implementing manufacturer-specific clusters/attributes/commands into Z-Stack.

Otherwise, it would be possible to modify zclProcessInReadCmd -> zcl_SendReadRsp -> zcl_SendCommand of zcl.c/h from your host application (I assume you've based from the ZIGBEE-LINUX-SENSOR-TO-CLOUD software solution) for your specific use.

Regards,
Ryan

Hi Ryan,

These are the logs Randy is referring to in his post.

ZigBee sniffer logs.zip

Hi Randy, Peter,

Thank you for providing the sniffer logs, however they only contain successful Read Attribute Responses.  Nevertheless my recommendation is to add your private cluster, attribute ID, and datatype to the gateway_config.tlg (please see the Z-Stack Linux Gateway Developer's Guide for more information) and use GW_WRITE_DEVICE_ATTRIBUTE_REQ from your host application to write the attribute value that you want to be read (refer to the Z-Stack Linux Gateway API document).

Regards,
Ryan

Hi Ryan,

I think there is some confusion as in the initial post Randy tried to combine two questions in one which did not really work out. So for the moment please ignore anything about "private clusters" and let us concentrate just on standard ZigBee. Actually the only packets of interesting are numbers 109 and 155 from "third party solution.cubx" which content I have also attached as a picture below.

Our challenge is that end end device does send a Basic: Read Attributes to the coordinator and not vice versa. So the end device asks the coordinator for Attribute [0x0005] Model Identifier and we need to reply to this message with a Basic: Read Attributes Response containing a string as model identifier. If the device gets the string it expects, it will be happy, if not it will refuse talking to us.

We have tried to work on that with gateway_config.tlg but, please correct me if wrong, in this we can configure the supported attributes which the coordinator uses for the gateway, not those which and end device can request from the gateway. If this also applies to the opposite direction: where I am supposed to configure the string which will be used for the answer?

Request send by the end device to the coordinator:

Desired answer from the coordinator to the end device:

I hope this is more clear now.

Regards
Peter

Hey Randy,

I'm glad to hear that you are making progress.  The Z-Stack Linux Gateway API document covers run-time attribute changes.  I am not too familiar with the .tlg file which determines the build-time configuration, but its attributes should be capable of configurating after being allocated after the EP is parsed by serverep.c

Regards,
Ryan

Dear YK,

Thank you so much for your great hint. However my problem is that I still get an empty string as response to the request. Maybe you have an idea what I could have done wrong.

@@ -309,6 +309,7 @@ CONST int giSrvNumNameValuePairs = sizeof(gaSrvNameValuePairs) / sizeof(srvNameV
 // ZCL Gateway Attributes
 uint8 srvAttrOnOff = 0;
 uint16 srvAttrIdentifyTime = 0;
+char srvAttrModelIdentifier[8] = "";

 

 char gszConfigTlgPath[MAX_CONFIG_STRING_LEN] = "";

 

@@ -335,6 +336,16 @@ zclAttrRec_t gsSrvDefaultZclAttrRecs[] =
       (ACCESS_CONTROL_READ | ACCESS_CONTROL_WRITE),
       NULL
     }
+  },
+
+  {
+    ZCL_CLUSTER_ID_GEN_BASIC,
+    {  // Attribute record
+      ATTRID_BASIC_MODEL_ID,
+      ZCL_DATATYPE_CHAR_STR,
+      (ACCESS_CONTROL_READ | ACCESS_CONTROL_WRITE),
+      "SAU2AG1"
+    }
   }
 };

 

@@ -343,7 +354,8 @@ zclAttrRec_t gsSrvDefaultZclAttrRecs[] =
 void * gsSrvDefaultAttrPtrs[] =
 {
   &srvAttrOnOff,
-  &srvAttrIdentifyTime
+  &srvAttrIdentifyTime,
+  &srvAttrModelIdentifier
 };

Thank you so much in advance.

Regards
Randy

Shouldn’t you give value in srvAttrModelIdentifier[8]?

Hi YK and Ryan, Thank you very much for the help, we were able to solve the problem by following your advice.

BR,

Randy