BR-Coding-cmd

For those that want to look through the logs, I've popped them below. [orphaned_node.txt](https://github.com/user-attachments/files/19892352/orphaned_node.txt) [meshed_node_layer-1.txt](https://github.com/user-attachments/files/19892350/meshed_node_layer-1.txt) [meshed_node_layer-2.txt](https://github.com/user-attachments/files/19892351/meshed_node_layer-2.txt) [meshed_node_layer-2-2.txt](https://github.com/user-attachments/files/19892349/meshed_node_layer-2-2.txt)

I wouldn't have expected the necessity to alter the task stack size in basic example, but I have since changed the stack and, you're correct, I haven't seen that error....

> Is the SSID hidden for the device in orphaned_node.txt? Only in the text file, the SSID and password are the same across all 4 devices. The SSID is not...

> Can this issue be stably reproduced? I've not been able to reproduce recently or gathered Thread now stale, to be revisited when Logs can be gathered

For those, who may be looking for info about this. I've found this document/white paper, which discusses the increase of the LWIP stack and params (see fig 19) https://dspace.ut.ee/server/api/core/bitstreams/a548d8b3-f4c7-461c-906a-f6f493a47f5d/content Hope...

Okay, thanks. I'll close issue if by removing the unnecessary function call of 'esp_wifi_sta_get_ap_info' solves this issue or the real issues presents itself and I'll update the name of the...

After investigating the code, I will still get the above issue as there are no uses of that function outside of the tasks that are sleeping until there is a...

I'll update this thread with logs once captured.

Below is what I expect to see if the device disconnects from the MQTT broker due to the mesh. [Successful rejoin.txt](https://github.com/user-attachments/files/20566116/Successful.rejoin.txt) Within logs below I've been a little confused with...

As an add-on to the above post, the final message that is then sent to the serial regarding any connection events can be seen captures in the below log. [last...