zigbee

HI 

After the connection between the light-bulb and the Zigbee-Coordinator is completed, it is observed from Sniffer that both parties will broadcast regularly (as shown in the screenshot below), and there are some questions:
1. Is there a way to describe the 5bytes payload?
2. What are the functions of the broadcast packets on both sides?

Parents
  • Hi,

    1. If you start the sniffer before the router is commissioned by the commissioner, the sniffer will capture the transport key that is exchanged on-air during commissioning process. You will then be able to see much more details about the packets and content in Wireshark. I have attached an example:

    2. The broadcast packets you see are "Link Status" messages sent by the stack with information about the node's neighbors and incoming/outgoing link cost. You can read more about this in the Zigbee Network specifications (Link Status Messages).

    Best regards,
    Jørgen

  • HI 

    Execute the following command in the console of ZC to toggle the LED light on the light-bulb
    zdo match_desc 0xfffd 0xfffd 0x0104 1 0 0
    zdo ieee_addr 0x5B28
    zcl cmd f4ce3682f9e8f132 10 0x0006 -p 0x0104 0x02


    1.How to interpret the content of this payload 13 bytes?
    2.where can it be seen that it is doing an on-off toggle command?

    3.Is there a packet for the light bulb to actively update the state?

     88.pcapng

  • It looks like your Wireshark is not properly setup to dissect the Zigbee protocol/packets.

    When I open your attached sniffer trace, I see this in Wireshark:

    Frame 46 is a "Extended address request".

    The state change command can be seen in frame 55/60: "ZCL OnOff Toggle".

    Please make sure you follow the instructions in Configuring Wireshark for Zigbee closely.

  • HI 

    I have a few questions about zigbee_cli_agent (PCA10056) clusters:
    1. In this example, where in the source code is the Zigbee (RF) packet received for parsing?
    2. In this example, when executing as Coordinator, what are the corresponding clusters that can be processed?
    3. In this example, where in the source code is the place to distinguish RF packet attributes (profile/cluster/attribute/command...)?

    Thanks.

  • Hi,

    SkyC said:
    1. In this example, where in the source code is the Zigbee (RF) packet received for parsing?

    This depends on the packet type. The reception of packets are handled inside the ZBOSS stack, which is only available as a linkable library. Relevant application packages are provided to the configured callbacks. The raw RF packages are not available to the application.

    SkyC said:
    2. In this example, when executing as Coordinator, what are the corresponding clusters that can be processed?

    Since the CLI agent example works with clusters through cluster IDs directly, it should be able to process any clusters defined in the ZCL specification.

    SkyC said:
    3. In this example, where in the source code is the place to distinguish RF packet attributes (profile/cluster/attribute/command...)?

    Not sure I understand this question. Like I said in 1., the packets are passed to the relevant callbacks in the application. Please have a look at the documentation in Zigbee stack API overview.

    Best regards,
    Jørgen

Reply
  • Hi,

    SkyC said:
    1. In this example, where in the source code is the Zigbee (RF) packet received for parsing?

    This depends on the packet type. The reception of packets are handled inside the ZBOSS stack, which is only available as a linkable library. Relevant application packages are provided to the configured callbacks. The raw RF packages are not available to the application.

    SkyC said:
    2. In this example, when executing as Coordinator, what are the corresponding clusters that can be processed?

    Since the CLI agent example works with clusters through cluster IDs directly, it should be able to process any clusters defined in the ZCL specification.

    SkyC said:
    3. In this example, where in the source code is the place to distinguish RF packet attributes (profile/cluster/attribute/command...)?

    Not sure I understand this question. Like I said in 1., the packets are passed to the relevant callbacks in the application. Please have a look at the documentation in Zigbee stack API overview.

    Best regards,
    Jørgen

Children
No Data
Related