Other Parts Discussed in Thread: Z-STACK, CC2538
Several devices that were apparently joined with the ZNP were not reported in the device list.
9747 2020-11-08 18:06:19.582029 00:12:4b:00:10:22:82:77 → 00:0d:6f:00:12:a0:cc:f8 IEEE 802.15.4 27 Association Response, PAN: 0xeb67 Addr: 0x099f 9789 2020-11-08 18:06:36.820021 00:12:4b:00:01:dd:7a:d7 → 00:0d:6f:00:12:19:9e:48 IEEE 802.15.4 27 Association Response, PAN: 0xeb67 Addr: 0x9584 9947 2020-11-08 18:08:53.014896 00:12:4b:00:10:22:82:77 → 00:0d:6f:00:12:a0:cc:f8 IEEE 802.15.4 27 Association Response, PAN: 0xeb67 Addr: 0x099f 9989 2020-11-08 18:09:03.594017 00:12:4b:00:10:22:82:77 → 00:0d:6f:00:12:a0:cc:f8 IEEE 802.15.4 27 Association Response, PAN: 0xeb67 Addr: 0x099f
After checking the logs, I did further attempts to allow association did not seem to set "Association Permit: True".
However, I ended up noticing that I could not longer do onoff requests for the TI SampleLights neither.
In the attached zip files, you'll find the HEX file read back from the CC2530 after the Gateway/ZNP became in responsive as well as difKK.txt listing the differences with the loaded fw.
DbHistoryFull holds the versions of the csv files as the network was extended (it is now automatic), the timestamp in the name of the file should be close (less than a few seconds) to when the CSV file was updated.
pcap files are also included, 'lastkeys.log' has the network key, seriallog.txt.7 holds the serial communication with the CC250 .
Hopefully this helps to identify the cause for these two issues, and hopefully that leads to fixes.