A network failure occurs when multiple nodes are used (AEGHB-596) #72
Comments
github-actions
bot
changed the title
|
[*] Join Mesh without configured with information [*] Join Mesh no matter whether the node is connected to router I am using a plan with a router, do I need to check these two items? Can it bring better stability? There are about 100 devices. I don't actively specify the root node. I hope the device can automatically elect the root node. Is it right for me after checking |
|
I am currently trying to power on 15 esp32S3s synchronously. I am using a router solution. Normally, a root node should be elected after synchronously powering on. However, when I power on synchronously, 8 esp32S3s are all root. What is the reason? ? |
|
https://components.espressif.com/components/espressif/mesh_lite It seems that
|
|
In addition, I would like to ask, if I want to create two mutually isolated mesh networks in the same environment, how should I configure them? |
|
Hi I found a problem here. When I have multiple devices in the network and I power off an intermediate node, the downstream node connected to the node will trigger multiple times: |
Please kindly update to the latest commit on GitHub for testing. The latest version includes a fix for this issue. |
When is it expected to be updated here? |
"Join Mesh no matter whether the node is connected to router" - This option is not required to be selected. "Join Mesh without configured with information" - If this option is not selected, the device needs to be configured with network information before it can join the mesh network. If selected, the device can join the network even without network configuration. |
|
You need to set different mesh IDs for different networking configurations. |
From the perspective of mesh logic, everything appears normal. After disconnecting from the parent node, it will attempt to reconnect several times before seeking a new parent node. However, during this period, your application layer code experienced a crash. The backtrace indicates that you may have encountered an error caused by releasing a null pointer. Please review your application layer code again. |
You can first use the components in the master branch of the GitHub repository. We will soon update the new version to the package manager. Thank you for your support. |
|
I am setting up 5 esp32 to create a mesh network. first three worked fine.. when 4th is added ... 2 esp starts diconnecting and reconnecting again and again. All ESPs are working on mesh Level 1 only....
|
|
Hi, friend I want to confirm with you that I need to isolate two different meshes of devices in the same area. I only need to configure different Mesh IDs here so that they will not interfere with each other, right? I already have a group of devices using The other two parameters, |
|
Yes, different Mesh networks can be distinguished by different Mesh IDs. |
But now I have changed the |
|
Under the same router, devices with mesh id 78 will form a network, and devices with mesh id 77 will form a network, The similarity is that the root nodes of the two networks are connected to the same router, but they will not fusion one network because their mesh ids are different. |
If I modify the configuration directly, will it not take effect? I need to call it manually in the main method |
I modified the configuration file and re-burned it. By checking the serial port, I can see |
Can you provide the complete log file? |
When I was doing the actual deployment, if one of my nodes went offline, the following log would initially appear. I used 15 esp32S3 for testing, distributed in different places, and the initial one would be elected. A root node. When I let the root node go offline, some nodes can elect a new root node. However, a few two or three nodes will have the following logs, so the grid networking will never be carried out, resulting in the inability to It works normally, but it can be solved after restarting the device. I feel this is not reasonable. Please help me find out what the problem is?
The text was updated successfully, but these errors were encountered: