• State Resolved
  • Locked Locked
  • Replies 16 replies
  • Subscribers 56 subscribers
  • Views 4026 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

How to implement ZCL Basic Message with manufacture code

Alexander Argollo
Genius 3370 points
Other Parts Discussed in Thread: Z-STACK

Hi Guys,

I´m working very well with my device (My Zstack is: Z-Stack Home 1.2.2a.44539) that Mr Yikai was helped me to build during this year. 

But during newest commercial gateway software version, one variable that I was found before and was not requested, is begin requested right now!

My manufacturer name variable in zclX_data is: 

const uint8 zclTeha0002_ManufacturerName[] = { 16, 'T','e','x','a','s','I','n','s','t','r','u','m','e','n','t','s' };

Somebody, please, would me help how to fix it?

The Message is ZCL Basic, that include the manufactured code (ZCL profile attribute). I seeing that this message is sent after the Device AnnCE sent by my device. As we can see below:

  • 0
    Guru 735685 points

    Can you attach your sniffer log and specify which line has this issue?

  • 0 in reply to YiKai Chen
    Genius 3370 points

    Hi Mr Yikai, nice to see you again.

    The PIC that i attched before is an example that working very well with ZCL Basic.

    I´ll attache two sniffer file, 1st as a reference and 2st from my device that is not send a ZCL Basic.

    As reference  (Azela Switch Commissioning Process GTW_20170928_a) - Azela switch (end Device) that sends ZCL basic in the line #104

    My device (My Device w Current ZBSERVER problem_2512_2017) - You can see that after Device_Annce #645 my device is not send ZCL basic message.

    Gtw addr: 00:0b:52:00:00:00:85:4e

    My device addr: 00:13:7a:00:00:01:b9:eb

    Reference device addr: 00:13:7a:00:00:01:b9:eb (you can see it in the 1st file).

    BR

    Alex

    Azela Switch Commissioning Process GTW_20170928_a.zip

    My Device w Current ZBSERVER problem_2512_2017.zip

  • 0 in reply to Alexander Argollo
    Guru 735685 points
    In your My Device w Current ZBSERVER problem_2512_2017.zip sniffer log, packet number 678 read attribute command is correct but packet number 686 is incorrect. You should refer to the code send read attribute command in packet number 678 to revise the one send as packet number 686.
  • 0 in reply to YiKai Chen
    Genius 3370 points

    Hi Mr Yikai,

    the ZCL read attributes message in the #686 was sent from another device, as you see it in the Destination Address is 0x19b3. My device short address is 0x4b30.  I ordered the messages by info. As you see in the PIC below:

    As i told you i think that it is occurred  by effect of not sent ZCL Basic. It is reflected in the message # 719 (Read Attributes Seq 171) sent by Gateway, in the parameter Manufacturer Code Unknown.

    You see it detailed in the messages #719 and #723 in the file  My Device w Current ZBSERVER problem_2512_2017.zip

    BR

    Alex

  • 0 in reply to Alexander Argollo
    Guru 735685 points
    How do you send package 719 from your code?
  • 0 in reply to YiKai Chen
    Genius 3370 points

    Hi Mr Yikai,

    About your question, the gateway is not mine, i using a commercial gateway to connect in my device. 

    I observed in the sniffer that i sent you the messages (Default Response) sent by my device in response to ZCL Attribute messages sent by Gateway. I explain those messages bellow:

     

    Seq. 167  – ZCL Command: Read Attributes, Model Identifier. ( my device was answer well and sent Read Attributes Response #682)

    Seq. 170  – ZCL Command: Read Attributes, Manufacturer Code: Unknown (0x0100) #686

    Seq. 171  – ZCL Command: Read Attributes, Manufacturer Code: Unknown (0x0105) #719

    Seq. 173  – ZCL Command: Read Attributes, Manufacturer Code: Unknown (0x0100) #705

    Default Response - # 692 (seq 170) , # 723 (seq. 171) , #707 (seq 173) , all those messages has a status: Unsupported Manufacturer General Command  and Manufacturer codes 0x0100 or 0x0105.

    My device reported via Default Response, in response to message Seq. 170 (ZCL Read Attributes w/ Cluster ID 0x0b04 - Electrical Measurement cluster), sent  Unsupported Manufacturer General Command (0x84). I think that after this response my device become silly. 

    Would you can help me please, how to implement the Cluster Id 0x0b04 in my Cluster Libary?

    Maybe we have a problem also in my device code to understand the manufacturer codes 0x100 and 0x0105. 

    BR

    Alex

  • 0 in reply to Alexander Argollo
    Guru 735685 points
    If you don’t design the GW, you should contact GW manufacturer to help you.
  • 0 in reply to YiKai Chen
    Genius 3370 points
    Mr Yikai,
    I received the answer from technical responsible to help customer and him advise me to implement ZCL Cluster 0x0b04 (Electrical Measurement ). Mr Yikai, please, would you can give me a way how to implement this ZCL Cluster definition?

    BR
    Alex
  • 0 in reply to Alexander Argollo
    Guru 735685 points
    You can add cluster support in simple descriptor define in zclXXx_data.c to implement it.
  • 0 in reply to Alexander Argollo
    Expert 2745 points
    I think zigbee Atrribute is not a part of ZCL ,do you think? attribute include manufacture human readable string name defined in zclTeha0002_ManufacturerName array, but attribute is interaction utilizing ZCL.

    In actuality,ZCL is a 'data packet format' that exchange data with zigbee mesh member each other, ZCL include ZCL header and body,header defined in struct zclFrameHdr_t,body will be store want to sent data over the air.
  • 0 in reply to behold li
    Genius 3370 points

    Mr. Yikai, thanks a lot!!!!!

    I´ll study more about the changes that gtw vendor made. Including I asked more about it to the technical support guy.

    I´ll let you know soon.

    BR

    Alex

  • 0 in reply to Alexander Argollo
    Genius 3370 points

    Mr Yikai,

    you´re always right!!!!

    I convince the technical guy from gateway vendor that the latest software version have a problem after understood how exactly the difference between the latest and penultimate version. 

    I observed that the 2st ZCL Read Attributes does not have command Attribute On/off, as you can see bellow on the left side of the figure. 

    BR

    Alex

     

  • 0 in reply to Alexander Argollo
    Guru 735685 points
    Cheers! May I know which GW you are testing?
  • 0 in reply to YiKai Chen
    Genius 3370 points

    Hi Mr. Yikai, i´m using to test a harmony gtw from Smartenit!

    BR

    Alex

  • 0 in reply to Alexander Argollo
    Guru 735685 points
    I see and Thanks for your information.
  • 0 in reply to YiKai Chen
    Genius 3370 points

    Hi Mr Yikai, 

    The gateway vendor was change something to interpret well the message ZCL Read attribute response in his code an right now my device is working well. After it I can saw that was not necessary to implement ZCL Basic as I was wrote in this post. 

    Thanks a lot again Mr Yikai.

    BR

    Alex