Zigbee Communication with Network Coordinator with Light Switch

RE: Zigbee Communication with Network Coordinator with Light Switch

Amanda Hsieh — Thu, 25 Apr 2024 14:30:05 GMT

Hi,

I tried with all the possible network keys I could find in all screenshots, both normal and reverse, but none of them worked. So the only suggestions I have are

If you can see the content of the packets, if you open the sniffer log in Wireshark or if it's only in Simplicity Studio
Verify that the screenshots showing the network key are from the same sniffer logs as you have uploaded. When the coordinator creates the network, it will generate a network key, so if the screenshots are from different tests with other networks, then the network key will not be the same.
Additionally, the network key should be part of the Zigbee Security Header in the Zigbee Network Layer, as in the following screenshot that I sent previously, so it would be nice to verify whether they see a Zigbee Security Header with a network key in your sniffer log

Collect new sniffer logs of the issue where you have manually set the network key. The network key must be set before the Zigbee stack is started. You can either set it in the code using zb_secur_setup_nwk_key() or if you are using Zigbee shell as coordinator you can set it with the shell command bdb nwkkey.
Then share the sniffer log and the network key you set manually in the ticket.

[quote user="NikhilVV"]I have followed the same steps which is mentioned in link to capture the sniffer log but when i starting wireshark it taking time to capture the packet and before that coordinator get start.[/quote]

You can just start the sniffer log earlier, no need to wait to start it until the coordinator starts up.

-Amanda H.

RE: Zigbee Communication with Network Coordinator with Light Switch

NikhilVV — Thu, 25 Apr 2024 07:14:40 GMT

Hi,

i did not get u what it mean by install codes.

How to differentiate it ?

Who will generate Transport key or who holds the key in zigbee network. does the coordinator or end device?

which feature u want to turn off and how.?

Can u tell the settings of wireshark which i need to config.

please find the transport key packet decrypted from other sniffer tool.

RE: Zigbee Communication with Network Coordinator with Light Switch

Amanda Hsieh — Wed, 24 Apr 2024 13:44:02 GMT

Hi,

The key doesn't work.

Are you using install codes? If you are using install code, the packets will be encrypted even if having the network key in Wireshark. Could you turn off the feature and provide the log again?

-Amanda H.

RE: Zigbee Communication with Network Coordinator with Light Switch

NikhilVV — Wed, 24 Apr 2024 09:19:38 GMT

hi,

I understand that zigbeeAlliance 09 key is exchanging at starting of network formation and TC Link key exchange for data exchange.

i captured the sniffer from before coordinator start but still i did not find the TC Link key exchange frame in Wireshark. attaching herewith the captured sniffer logs for reference.

devzone.nordicsemi.com/.../zigbee_5F00_ch16_5F00_Log.pcapng

devzone.nordicsemi.com/.../zigbee_5F00_APS.pcapng

please check the above logs and confirm.

RE: Zigbee Communication with Network Coordinator with Light Switch

Amanda Hsieh — Tue, 23 Apr 2024 14:32:56 GMT

Hi,

[quote user="NikhilVV"]we are not modified the Network key using default key "zigbee alliance 09 " .[/quote]

I have the Zigbee alliance 09 key in Wireshark, so your network is not using that as the Trust Center link key, as then I would be able to see the content of the packets.

The zigbee alliance 09 key is used for the first Transport Key packet, before the device has been commissioned to the network, like here (this is from a different sniffer log):

But this is not the actual network key, or Trust Center Link Key, as that will be one the ZC has randomly generated (unless you have specified one using e.g. shell commands).

After the device has been fully commissioned it will start using the actual network key, as you can see here (from the same sniffer log as the previous screenshot):

If you can see the actual frames, then it should be possible for you to get the network key from the Zigbee security header. It would be the same key as in my last screenshot.

Another option is to manually set a network key on the ZC before starting the network, using for example bdb nwkkey, and then share the network key so we can decrypt the packets. But then you have to collect new logs anyway.

-Amanda H.

RE: Zigbee Communication with Network Coordinator with Light Switch

NikhilVV — Tue, 23 Apr 2024 06:21:24 GMT

Hi,

I have followed the same steps which is mentioned in link to capture the sniffer log but when i starting wireshark it taking time to capture the packet and before that coordinator get start.

You can check the image which i uploaded in previous post in which all frames are clearly visible including the Data bytes in Hex.

we are not modified the Network key using default key "zigbee alliance 09 " .

if compare with Pcap log vs image you can see that all packet till APS Frame (Zigbee cluster Library) are same. ie IEEE 802.15.4 , zigbee network , zigbee network security and Zigbee application support are same. But due to encryption zigbee cluster library packets are not visible to compare in pcap. So we are using the Other platform sniffer to observe data.

Please find data bytes details of ZCL Frame.

ZCL Frame Control : 0x05

Manufacture Code : 0x1002

Sequence Number : 0x73

Command Identifier : 0x01

Application PayLoad :

0x00 0x00 0x00 0x02 0x14 0x00 0x03 0x01 0x4F 0x00 0x14 0x01 0xAD 0x1A

0xAC 0x40 0x05 0x2C 0x67 0xF2 0x40 0xA3 0x00 0x01 0x00 0x01 0x0A 0x4C

Hope these information helps you.

_Nikhil

RE: Zigbee Communication with Network Coordinator with Light Switch

Amanda Hsieh — Mon, 22 Apr 2024 16:23:11 GMT

Hi,

[quote user="NikhilVV"]I tried to capture the traffic using sniffer tool which is not working well.[/quote]

Here is the guide for nRF Sniffer for 802.15.4. Please create a new support case if it doesn't work.

[quote user="NikhilVV"]Please check the packet data and let me know how can i handle the packet in Shell or Coordinator sample.[/quote]

It's hard for us to analyze the issue without the proper sniffer log. Please share the network key or capture a new sniffer log where they start the sniffer before the coordinator starts the network.

-Amanda H.

RE: Zigbee Communication with Network Coordinator with Light Switch

NikhilVV — Mon, 22 Apr 2024 07:01:30 GMT

HI,

I tried to capture the traffic using sniffer tool which is not working well. Bit slow to start and capturing logs.

I have compared the previous captured pcap data which i uploaded in previous post with Captured data on Simplicity Studio which also posted in previous post as Image.

while comparing i have found that the zigbee packets are same as pcap. So i am posting here the full packet which i received on other device which act as sniffer for reference.

Please check the packet data and let me know how can i handle the packet in Shell or Coordinator sample.

_nikhil

RE: Zigbee Communication with Network Coordinator with Light Switch

Amanda Hsieh — Fri, 19 Apr 2024 12:41:17 GMT

Hi,

Q1a.
See the example here and here.

There is also some information about this in the documentation here: https://developer.nordicsemi.com/nRF_Connect_SDK/doc/zboss/3.11.3.0/using_zigbee__z_c_l.html#process_zcl_cmd

Q1b.

If you mean Zigbee packets in general then this is handled internally by the stack and is not visible to the application.

2) The packets in the sniffer log are encrypted. Please share the network key or capture a new sniffer log where they start the sniffer before the coordinator starts the network.

Q3a.

You should be able to handle this in the ZCL handler

RE: Zigbee Communication with Network Coordinator with Light Switch

NikhilVV — Wed, 17 Apr 2024 08:00:35 GMT

Hi,

coordinator Send : ZCL cmd 0x5df 2 0x0000 0x0104 0

uart:~$ zcl cmd 65df 2 0x0000 0x0104 0
Default Response received: Command: 4, Status: 129
Error: Command not successful
Done

Status 129 (0x81) is unsupported command or unsupported cluster command (zb_zcl_common.h#L371-L372).

They are trying to send command 0 to the Basic cluster on the device, which is "Reset to Factory Defaults":

Q1a : could you tell which handler or callback is processing the received ZCL generic command.

Q1b : Which function receives and process the incoming packets.

2)Please upload the sniffer log as a pcap file, and to clarify what command you are sending and which device you are sending it to/from.

Here follows the pcap file.

Also adding captured traffic image for reference.

devzone.nordicsemi.com/.../zigbeeROuter-traffic.pcapng

The End Device sending Customized manufacturing data in ZCL Generic Commands.

Here follows the details.

Profile : 0x0104

Cluster ID : 0xFF01

Manufacture ID : 0x1002

Q 3a: where can we receive the manufacture specific data ?

RE: Zigbee Communication with Network Coordinator with Light Switch

Amanda Hsieh — Tue, 16 Apr 2024 12:54:32 GMT

Hi,

[quote user="NikhilVV"]

coordinator Send : ZCL cmd 0x5df 2 0x0000 0x0104 0

uart:~$ zcl cmd 65df 2 0x0000 0x0104 0
Default Response received: Command: 4, Status: 129
Error: Command not successful
Done

[/quote]

Status 129 (0x81) is unsupported command or unsupported cluster command (zb_zcl_common.h#L371-L372).

You are trying to send command 0 to the Basic cluster on the device, which is "Reset to Factory Defaults":

This command is optional, so it could be that the device doesn't support it.

[quote user="NikhilVV"]3) End Device sending ZCL CMD in every seconds but not receiving at zigbee_logger_eprxzcl_ep_handler().[/quote]

Please upload the sniffer log as a pcap file, and to clarify what command you are sending and which device you are sending it to/from.

-Amanda H.

RE: Zigbee Communication with Network Coordinator with Light Switch

NikhilVV — Mon, 15 Apr 2024 14:24:18 GMT

HI,

I have tried following points in Shell Sample code which as working as Coordinator.

1) coordinator Send : ZCL attr read 0xA009 2 0x0000 0x0104 0

Responds Received from Node and printed on terminal.

2) Similarly

coordinator Send : ZCL cmd 0x5df 2 0x0000 0x0104 0

uart:~$ zcl cmd 65df 2 0x0000 0x0104 0
Default Response received: Command: 4, Status: 129
Error: Command not successful
Done
[00:15:45.006,256] <inf> zigbee_shell: RECEIVED CMD zbshellutil.c

[00:15:45.006,652] <inf> zigbee.eprxzcl: Received ZCL command (4): src_addr=0x65df(short) src_ep=2 dst_ep=64 cluster_id=0x0000 profile_id=0x0104 cmd_dir=1 common_cmd=1 cmd_id=0x0b cmd_seq=10 disable_def_resp=0 manuf_code=void payload=[0481] (4)

3) End Device sending ZCL CMD in every seconds but not receiving at zigbee_logger_eprxzcl_ep_handler().

Attached herewith the traffic captured for reference.

Kindly find the attachment and let me know why it is not receiving the ZCL generic command.

the only difference i found is manufacturing specific bit in ZCL Frame Control.

how to overcome this issue.

I also tried the following callback

1) ZB_ZCL_REGISTER_CALLBACK();

2) ZB_ZCL_SET_DISC_MANUFACTURE_COMMAND_CALLBACK();

3) ZB_AF_SET_ENDPOINT_HANDLER();

The incoming message is not hitting any of the above callback which i tried one by one.

i have observed that if i try ZCL on-off command from end device it is hitting at ZB_ZCL_Handler().

if i add a callback does the stack callback will disabled or not?

_nikhil

RE: Zigbee Communication with Network Coordinator with Light Switch

Amanda Hsieh — Fri, 12 Apr 2024 21:20:03 GMT

See this post.

[quote user="NikhilVV"]Is it possible the zigbee Shell example receive ZCL CMD not ZCL ATTR READ command from node without adding any other Cluster. [/quote]

Yes, it is possible for the Zigbee Shell example to receive ZCL (Zigbee Cluster Library) commands without adding any other cluster. The Zigbee Shell library implements a set of Zigbee shell commands that can be used for testing and debugging. These commands include zcl cmd for sending a generic ZCL command to a remote node and zcl attr read for retrieving the attribute value of a remote node.

[quote user="NikhilVV"]is it mandatory to add the cluster in coordinator side too to receive zcl cmd & zcl attr read commands.[/quote]

No, it is not mandatory to add the cluster on the coordinator side to receive ZCL commands and ZCL attribute read commands. The Zigbee Shell in the coordinator can issue commands to any device in the network, regardless of the clusters implemented on the coordinator side.

[quote user="NikhilVV"]

When the i try to read the added cluster (Basic) info from node am able get the responds.

can i use the same zigbee_logger_eprxzcl_ep_handler() to receive ZCL CMD from router Node.

[/quote]

Yes, you can use the zigbee_logger_eprxzcl_ep_handler() function to receive ZCL commands from a router node. This function is part of the Zigbee endpoint logger library and is used for parsing incoming ZCL frames and logging their fields and command payload.

For more information, you can refer to the Zigbee endpoint logger documentation and the Configuring Zigbee endpoint logger documentation.

RE: Zigbee Communication with Network Coordinator with Light Switch

NikhilVV — Fri, 12 Apr 2024 09:00:58 GMT

HI,

https://docs.nordicsemi.com/bundle/ncs-latest/page/nrf/protocols/zigbee/adding_clusters.html

By referring above the link i added temperature Sensor in zigbee template example. when building it is failed due to errors.

warning: data definition has no type or storage class
   86 | ZB_HA_DECLARE_TEMPERATURE_SENSOR_CLUSTER_LIST(
      | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
../src/main.c:86:1: error: type defaults to 'int' in declaration of 'ZB_HA_DECLARE_TEMPERATURE_SENSOR_CLUSTER_LIST' [-Werror=implicit-int]
../src/main.c:90:9: warning: parameter names (without types) in function declaration
   90 |         temp_measurement_attr_list);
      |         ^~~~~~~~~~~~~~~~~~~~~~~~~~
../src/main.c:99:31: error: expected ')' before numeric constant
   99 |         temperature_sensor_ep,
      |                               ^
      |                               )
../src/main.c:110:1: warning: data definition has no type or storage class
  110 | ZB_DECLARE_DEVICE_CTX_2_EP(
      | ^~~~~~~~~~~~~~~~~~~~~~~~~~
../src/main.c:110:1: error: type defaults to 'int' in declaration of 'ZB_DECLARE_DEVICE_CTX_2_EP' [-Werror=implicit-int]
../src/main.c:113:9: warning: parameter names (without types) in function declaration
  113 |         temperature_sensor_ep);
      |         ^~~~~~~~~~~~~~~~~~~~~
In file included from C:/ncs/v2.5.2/nrfxlib/zboss/production/include/zboss_api.h:52,
                 from ../src/main.c:16:
../src/main.c: In function 'main':
../src/main.c:270:36: error: 'app_template_ctx' undeclared (first use in this function)
  270 |         ZB_AF_REGISTER_DEVICE_CTX(&app_template_ctx);
      |                                    ^~~~~~~~~~~~~~~~
C:/ncs/v2.5.2/nrfxlib/zboss/production/include/zboss_api_af.h:657:74: note: in definition of macro 'ZB_AF_REGISTER_DEVICE_CTX'
  657 | #define ZB_AF_REGISTER_DEVICE_CTX(_device_ctx) zb_af_register_device_ctx(_device_ctx)
      |                                                                          ^~~~~~~~~~~
../src/main.c:270:36: note: each undeclared identifier is reported only once for each function it appears in
  270 |         ZB_AF_REGISTER_DEVICE_CTX(&app_template_ctx);
      |                                    ^~~~~~~~~~~~~~~~
C:/ncs/v2.5.2/nrfxlib/zboss/production/include/zboss_api_af.h:657:74: note: in definition of macro 'ZB_AF_REGISTER_DEVICE_CTX'
  657 | #define ZB_AF_REGISTER_DEVICE_CTX(_device_ctx) zb_af_register_device_ctx(_device_ctx)
      |                                                                          ^~~~~~~~~~~
cc1.exe: some warnings being treated as errors
[109/316] Building C object zephyr/CMakeFiles/zephyr.dir/lib/os/heap.c.obj
ninja: build stopped: subcommand failed.

In my project Zigbee Node which sends data is sending data in customised manufacture cluster.

Is it possible the zigbee Shell example receive ZCL CMD not ZCL ATTR READ command from node without adding any other Cluster.

is it mandatory to add the cluster in coordinator side too to receive zcl cmd & zcl attr read commands.

When the i try to read the added cluster (Basic) info from node am able get the responds.

can i use the same zigbee_logger_eprxzcl_ep_handler() to receive ZCL CMD from router Node.

if the zigbee_logger_eprxzcl_ep_handler() doent work to receive ZCL CMD how to add a handler or call back to receive ZCL CMD.

-Nikhil

RE: Zigbee Communication with Network Coordinator with Light Switch

NikhilVV — Wed, 10 Apr 2024 13:42:17 GMT

hi Amanda,

the link which you shared describes how to add a preconfigured cluster.

Where am looking for how to add a custom cluster in coordinator. In my application coordinator continuously receive data from node. The endnode is using some custom profile.

kindly guide me to how to add custom cluster in coordinator.

_nikhil

RE: Zigbee Communication with Network Coordinator with Light Switch

NikhilVV — Wed, 10 Apr 2024 06:02:47 GMT

hi,

Thanks for the response.

I will check the same and let you the result.

-nikhil

RE: Zigbee Communication with Network Coordinator with Light Switch

Amanda Hsieh — Mon, 08 Apr 2024 20:09:59 GMT

Hi,

[quote user="NikhilVV"]In Shell sample code which network is used ?[/quote]

See https://docs.nordicsemi.com/bundle/ncs-latest/page/nrf/protocols/zigbee/commissioning.html#centralized_security_network and https://github.com/nrfconnect/sdk-nrfxlib/blob/v2.6.0/zboss/production/include/zb_config.h#L158

[quote user="NikhilVV"]C) Can i add custom cluster shell sample or should i use template sample?[/quote]

You can refer to https://docs.nordicsemi.com/bundle/ncs-latest/page/nrf/protocols/zigbee/adding_clusters.html

-Amanda H.

RE: Zigbee Communication with Network Coordinator with Light Switch

NikhilVV — Mon, 08 Apr 2024 13:20:58 GMT

hi Amanda,

A) Currently am able to read basic attribute from zigbee device using shell sample.

Thank you for your guidance.

Later i will reuse the payload read from Zigbee device to pass to uart buffer.

B) Regarding KEY.

The KEY i mentioned in previous post is Network Key.

In Shell sample code which network is used ?

C) Can i add custom cluster shell sample or should i use template sample?

kindly provide the guidance to add cluster in coordinator side.

Am referring following Link to declare cluster.

https://infocenter.nordicsemi.com/index.jsp?topic=%2Fcom.nordic.infocenter.thread_zigbee.v3.0.0%2Fusing_zigbee__z_c_l.html&anchor=att_declaration

thanks,

Nikhil

RE: Zigbee Communication with Network Coordinator with Light Switch

NikhilVV — Fri, 05 Apr 2024 06:51:59 GMT

Hi Amanda,

Thank you for quick response.

In shell Sample code i did the same but End Device is not joining to the network.

following the steps i did.

1. In proj.config changed

//CONFIG_ZIGBEE_ROLE_ROUTER = y

CONFIG_ZIGBEE_ROLE_COORDINATOR = y

2. builded and flashed the code.

3. changed role to ZC .. bdb role zc

4. bdb start ..

Started coordinator
Done

(Extended PAN ID: f4ce365044756cb7, PAN ID: 0x1205)

5. bdb legacy enable.

6. waited for joining device.

7. after steering finished tried again bdb start.

8 bdb short

0000

done.

9. ping 0000 10

Ping time: 3 ms
Done
[00:01:59.551,086] <inf> zigbee.eprxzcl: Received ZCL command (0): src_addr=0x0000(short) src_ep=10 dst_ep=10 cluster_id=0xbeef profile_id=0x0104 cmd_dir=0 common_cmd=0 cmd_id=0x02 cmd_seq=0 disable_def_resp=1 manuf_code=void payload=[abababababababababab] (0)
[00:01:59.552,734] <inf> zigbee.eprxzcl: Received ZCL command (1): src_addr=0x0000(short) src_ep=10 dst_ep=10 cluster_id=0xbeef profile_id=0x0104 cmd_dir=0 common_cmd=0 cmd_id=0x01 cmd_seq=0 disable_def_resp=1 manuf_code=void payload=[cdcdcdcdcdcdcdcdcdcd] (1)

b) In Network coordinator we Enabled Shell and tried same and end device is connecting to coordinator and binded cluster 0x0000. but when we tried

zcl attr read 9153 1 0x0000 0x0104 0

Error: Request timed out

c) Also tried with Network Coordinator (Shell Enabled) with another( Custom Made , NOT NRF) device which is configured as router.

That moment also Router joined and Binded with coordinator.

we tried zcl attr read and still getting time out. (In shell)

We monitored the traffic between coordinator and router we noticed that when NRF request for reading attribute , Router sends read response and NRF not showing the response data.

is coordinator sample enabled read response printing ? if not how to get and print the data.

Please refer attached screen shot.

d) Regarding KEY.

The KEY i mentioned in previous post is Network Key.

In coordinator sample code which network is used ?

E) Can i add cluster in coodinator / shell sample or should i use template sample?

kindly provide the guidance to add cluster in coordinator side.

zigbee SDK 2.5.2

Toolchain 2.5.2

VSCode

thanks,

Nikhil

RE: Zigbee Communication with Network Coordinator with Light Switch

Amanda Hsieh — Wed, 03 Apr 2024 14:50:49 GMT

Hi,

[quote user="NikhilVV"]Does i need to modify anything else in source code ?[/quote]

No. See the Testing

[quote user="NikhilVV"]2. Can u tell by default which key it is using in Network Coordinator Sample?[/quote]

What do you mean by the "key"? Could you elaborate in more detail?

[quote user="NikhilVV"]

3. I like to ask regarding Attribute Type and Attribute ID .

is it generating dynamically or pre-configured?

when coordinator generate or receive or know attribute id and type of end device cluster.

how can i know attribute id and type of end device ?

[/quote]

Zigbee Attribute Types and Attribute IDs are pre-configured and not generated dynamically. They are defined in the Zigbee Cluster Library (ZCL) and are used to identify specific attributes within a cluster. For example, in the Zigbee dimmable light level control attribute reporting, the Attribute ID for the On/Off cluster is ZB_ZCL_ATTR_ON_OFF_ON_OFF_ID and for the Level Control cluster, it's ZB_ZCL_ATTR_LEVEL_CONTROL_CURRENT_LEVEL_ID. These are predefined in the ZCL and used to set or get the attribute values.

Here is an example of setting the attribute values:

https://github.com/nrfconnect/sdk-nrf/blob/v2.6.0/samples/zigbee/light_bulb/src/main.c#L412-L426

In the above code, ZB_ZCL_SET_ATTRIBUTE is a macro used to set the attribute value. The parameters include the endpoint, cluster ID, role, attribute ID, attribute value, and a flag to indicate if the attribute is reportable.

-Amanda H.

RE: Zigbee Communication with Network Coordinator with Light Switch

NikhilVV — Wed, 03 Apr 2024 07:09:21 GMT

hi,

Thank you for your feedback.

1. I configured Zigbee Shell example Proj.conf as follows.

//CONFIG_ZIGBEE_ROLE_ROUTER = y

CONFIG_ZIGBEE_ROLE_COORDINATOR = y

Does i need to modify anything else in source code ?

Because i tried to steering and device is not connecting with it.

2. Can u tell by default which key it is using in Network Coordinator Sample?

3. I like to ask regarding Attribute Type and Attribute ID .

is it generating dynamically or pre-configured?

when coordinator generate or receive or know attribute id and type of end device cluster.

how can i know attribute id and type of end device ?

Regards,

Nikhil.

RE: Zigbee Communication with Network Coordinator with Light Switch

Amanda Hsieh — Tue, 02 Apr 2024 20:33:38 GMT

Hi,

1. Could you use Zigbee: Shell to run as coordinator to test?

2. See this post.

Regards,
Amanda H.