BitCloud - ZigBee received payload too large, Coordinator just rejects it

[rfleming]

Hi Guys,

I have found a device that I have tried to integrate with my Coordinator and have found that when I read on its Manufacturer Name in the Basic Cluster, it returns a 57 character attribute that in turn creates a 107 character frame. This frame seems to be just rejected by the coordinator because it is simply "too large".

I have also seen this with another device when I did an attribute discovery for 20 attributes, the 20 attributes were too long in length for a frame so they were simply "rejected" but when I changed it to 5, it worked fine.

Any tips on how to read this long length would be awesome

Ryan.

[ataradov]

Coordinator should receive payloads like this without problems. It is likely that ZCL layer parser rejects this for some reason. I would look at APS_DataInd function in the ZCL to see if raw payload is received there.

Sorry for the delay, I was on vacation.

[DownTown]

I think from the spec *refer the picture attached* you cannot set the manufactures id above 32 byte! that could be the reason why the stack is rejecting it.
May be if you could find the the code where it actually checks for the length and increase it might work.