Zigbee Cli Agent Router and Greenpower endpoint

[nicho2]

Hello,

I use zb_cli_wrapper.py and the Zigbee Cli Agent Router example.

I try to discover attributes from a GreenPower endpoint (242), the commande is :

communicator.py: DEBUG: CLI::UartConn: COM15@115200 TX: zcl cmd -w -d 0004740000CFFDA7 242 21 -p A1E0 C -l 0000ff
communicator.py: DEBUG: CLI::UartConn: COM15@115200 RX: zcl cmd -w -d 0004740000CFFDA7 242 21 -p A1E0 C -l 0000ff

profileId = 0xA1E0 ; Endpoint = 242 ; cluster = 0x21

On wireshark, le frame is correctly sending and i see also the answer:

but the answer frame is not received by the dongle. (function : cli_agent_ep_handler_generic_cmd)

Somebody has an idea?

of course this commande works with another endpoint as 

communicator.py: DEBUG: CLI::UartConn: COM15@115200 TX: zcl cmd -w -d 0004740000CFFDA7 1 3 -p 0104 C -l 0000ff
communicator.py: DEBUG: CLI::UartConn: COM15@115200 RX: zcl cmd -w -d 0004740000CFFDA7 1 3 -p 0104 C -l 0000ff
communicator.py: DEBUG: CLI::UartConn: COM15@115200 RX:
communicator.py: DEBUG: CLI::UartConn: COM15@115200 RX: Response received: generic
communicator.py: DEBUG: CLI::UartConn: COM15@115200 RX: List Attribute Response received:
communicator.py: DEBUG: CLI::UartConn: COM15@115200 RX: complete:1
communicator.py: DEBUG: CLI::UartConn: COM15@115200 RX: list attr,type:
communicator.py: DEBUG: CLI::UartConn: COM15@115200 RX: [(0,33),(65533,33),]
communicator.py: DEBUG: CLI::UartConn: COM15@115200 RX: Done

Version : 

['version', 'CLI: Apr 14 2021 08:31:54', 'ZBOSS: 3.3.0.4 ']

Thanks

[Marte Myrvold]

Hi,

It is possible that some functionality is not supported for Green Power in the SDK, but I am not certain. I will ask our Zigbee team about this and come back to you.

Best regards,

Marte 

[Marte Myrvold]

Hi,

I am sorry for the delay, but I am still waiting on a reply from our Zigbee team. There might be some extra delays due to summer holidays, but I have pinged them and hopefully I will get an answer regarding this soon. I will update you as soon as I hear from them.

Best regards,

Marte

[Marte Myrvold]

Hi Nicholas,

Could you please share the pcap file of the sniffer log so we can examine the packets more closely?

What does the flag "-w" do in your zcl cmd call? 

Best regards,

Marte

[nicho2]

Hello,

attached the file

and put this filter 

!(zbee_nwk.cmd.id == 0x08) && !(zbee_nwk.cmd.id == 0x01) && !(zbee_nwk.cmd.id == 0x05)  && (wpan.dst_pan == 0x79AA  || wpan.src_pan == 0x79AA)

wireshark_wireshark_extcap2972CSUI50.pcapng

I have add in the project the flag -w to send frame with the frame type : profile-wide

Best Regards

Nicolas

[Marte Myrvold]

Hi Nicholas,

Thank you for sharing the pcap file. It seems like the messages are encrypted. Can you either share the network key so that I can see the content of the packets, or can you start the sniffer before starting the network so the packets will not be encrypted in the sniffer log?

Best regards,

Marte

[nicho2]

the key is this, i thing

951da7958fdb0fee1df0050d9dd672f3

[Marte Myrvold]

Hi Nicholas,

They key was correct.

I forwarded your pcap file to the Zigbee team, and they could not find anything wrong there. They believe the response is received by the lower layers of the device, and then not handled properly, as it would be very strange if the frame is not received at all. 

From the logs it seems like you have made changes to both the CLI wrapper and the CLI agent. Would it be possible for you to provide your code so our developers can take a look at it? I can make the ticket private before you share the code if you do not want to upload it to a public ticket.

Best regards,

Marte

[nicho2]

Hello, below you found the CLI agent project with very few modifications

zigbee.cli_router_agent.zip

Best Regards

N.S

[Marte Myrvold]

Hi Nicholas,

Thank you for providing your project. I have forwarded it to the developers, and I will let you know when I hear from them.

Please be aware that due to summer vacations there might be longer response times.

Best regards,

Marte

[c.tessierpiart]

Hi Marte,

It has been a quite a while since your last reply. I am interested to know what could cause this issue and I hope your team can give us an answer.

Charles Tessier-Piart

[Marte Myrvold]

Hi,

This seams to be caused by a profile_id mismatch between the Discover Attribute Responses command and the endpoint used for receiving it. The command is filtered out by the stack, and it does not get to the endpoints device handler. 

Best regards,

Marte