Hi Sirs,
We are working on KW22. We set the Auto reporting of Humidity and Temperature every 1 minute by 4 steps, sending binding and the auto reporting timer value of Humidity and Temperature from ZC to ZED. After few hours testing, the ZED stop reporting. From the wireshark log, the wireshare log is in attachment, we found the short address - DCF3 sent the "permit join request" at 14:22:43.448 and successfully joined the network. After that, ZED keep sending Identify Query. Do you know why the ZED stop reporting?
220910 | 2016-03-04 14:22:43.448923 | 0xdcf3 | Broadcast | ZigBee ZDP | 62 | Permit Join Request |
220939 | 2016-03-04 14:22:43.928683 | 0x0000 | 0xdcf3 | ZigBee ZDP | 61 | Permit Join Response, Status: Success |
221034 | 2016-03-04 14:22:48.541803 | 0xdcf3 | Broadcast | ZigBee HA | 62 | ZCL Identify: Identify Query, Seq: 2 |
Platform: MKW24D512 Beekit: 3.0.2 Codebase: 4.0.1 Test Tool: 12.2.1
The Keys of this Zigbee network, FYI.
5A:69:67:42:65:65:41:6C:6C:69:61:6E:63:65:30:39 -Trust Center Link Key
b2:84:cf:69:b6:ba:dc:3b:f2:73:93:c6:97:31:49:26 -Network Key
Thanks,
Jake
Original Attachment has been moved to: BSP02.00stress-test_20160304.pcap.zip
One possibility (without seeing your over-the-air logs it's hard to tell) is that the EZ-Mode commissioning was unable to complete (hence the Identify Query). This could because you don't have matching clusters on the two nodes (that is and input cluster on the one node matching an output cluster on the other node). Reporting works through the binding table, which means it needs to complete that binding on the Reporting node.
Hello Jake, did you try the latest Kinetis BeeStack ZigBee Protocol Stack (REV 5.0.0) ?
Hi Juan,
We are upgrading the ZigBee Protocol Stack Rev 5.00. Is it a known issue of old ZigBee release?
If the issue still can be reproduced on V5.00, what kind of logs should I provide to you?
Thanks,
Jake
I'm glad that you are upgrading to latest revision. Basically some issues were solved there, I'm not aware if this is included but either way the previous version is no longer supported.
If the issue is still present, please provide all sniffer logs and application behavior for us to reproduce in our evaluation boards.
Hi Juan,
Thanks for your response. We will keep reproducing it in the new release.
Thanks,
Jake
Hi
Is there any response or information. we found 4 out of 12 devices have the behavior. ZEDs stop reporting attributes before send the "permit join request" to ZC.
Thanks,
Jake