espressif / esp-mdf

Espressif Mesh Development Framework, limited maintain, recommend to use https://github.com/espressif/esp-mesh-lite
Other
779 stars 253 forks source link

Parent is disconnected, reason: 106 #221

Open lcarnevale opened 3 years ago

lcarnevale commented 3 years ago

Environment

Problem Description

I am working with a single node configuration and ESP-MDF.

The node, which is of course the root node, connects to wifi and gets an IP address. It also connects to a public MQTT broker and sends messages.

After a while, the mesh breaks and the board enters a loop as shown in the Figure herein attached.

Expected Behavior

I expect the mesh network does not crash. In particular, I expect that after the parent is disconnected, it is able to reconnect again.

Actual Behavior

After a while, the mesh breaks and the board enters a loop as shown in the Figure herein attached.

Code to reproduce this issue

The code I am using to manage the MESH events is hosted on GitHub, on the following page: https://github.com/lcarnevale/esp32-mesh/blob/main/main/include/events.h

Debug Logs

...
I (172452) [mwifi, 187]: Parent is disconnected, reason: 106
I (172462) mesh: [wifi]disconnected reason:106(scan fail), continuous:10275/max:12, root, vote(,stopped)<><>
I (172452) [mwifi, 187]: Parent is disconnected, reason: 106
I (172462) mesh: [wifi]disconnected reason:106(scan fail), continuous:10276/max:12, root, vote(,stopped)<><>
I (172452) [mwifi, 187]: Parent is disconnected, reason: 106
I (172462) mesh: [wifi]disconnected reason:106(scan fail), continuous:10277/max:12, root, vote(,stopped)<><>
...
InfiniteYuan commented 3 years ago

Could this be reproduced on other development boards? And provide another log after the log level is set to Debug?