When we test the matter, we sometimes will meet commissioning accessory fail and network dropping. In the worst case, we can't access the network for a long time after the network is dropped, and we can't access the network when we power on again.
Could you tell me whether this problem exists in the current matter itself or is introduced by Nordic's sdk? When is it expected to be solved?
Log description:
1/From 0 to 4336 lines, the log shows that you can use chip-tool-linux_X64 normally controls nrf52840DK switch led, that is, the equipment is on the network
2/From line 4431 to line 6816, the log shows that the control fails for more than 10 minutes, that is, the sed device is offline and cannot access the network for a long time
3/From line 6823 to line 7273, the log shows that after power failure and restart, the system still cannot be controlled, that is, after power failure and reset, the system still cannot be connected to the network
4/From line 7275 to line 12927, the log shows that the device cannot be connected to the network, and multiple devices cannot be connected to the network, that is, the device cannot be connected to the network even if it is paired again
5/From line 12927 to line 12943, the log shows that you can ping the OpenThread Border Router, that is, the IP network is normal
6/The log records that the connected devices are displayed on the web homepage of the OpenThread Border Router
7/The distance between the test OpenThread Border Router and the sed device is very close
8/Network topology: 4 sed devices are attached to one OpenThread Border Router
9/This log only records the phenomena of network loss and difficulty in accessing the network. There are many other times that we have encountered this kind of offline and difficult network access. The reason may be different from that shown in this log.
入网困难，掉网，最严重时掉网后长时间不能入网即便断电重启都不能入网
我们在测试matter时，时不时会遇到入网困难，异常掉网现象，最严重时，掉网后长时间不能入网，重新上电也不能入网。
请问这个问题，是当前matter本身存在的，还是nordic的sdk引入的，预期什么时候解决？
日志说明：
1/从0到4336行，日志显示能从chip_tool-linux_x64正常控制nrf52840DK开关led，即设备在网
2/从4431行到6816行，日志显示，10多分钟控制失败，即设备掉网，长时间不能入网
3/从6823行到7273行，日志显示，断电重启后仍不能控制，即断电复位后，仍不能入网
4/从7275行到12927行，日志显示，不能入网设备，多个设备都不能入网，即重新配对设备也不能入网
5/从12927行到12943行，日志显示，可以ping通边沿路由器，即ip网络正常
6/日志记录了，在边沿路由器web主页里，显示连接有设备
7/这个测试边沿路由器与设备间的距离很近
8/网络拓扑：一个边沿路由器上挂4个sed设备
9/这个日志只是记录一此掉网，入网困难现象。还有其他很多次遇见这种掉网，入网困难的情况，其原因可能跟这个日志显示的不一样。
距离-功耗-4sed-距离0-距离25的10分钟10次及10分钟在网待机功耗与时延，还有成功率，0距离掉网，0距离入网困难等.txt
