Tian Sen Wen

It seems that a network problem caused the component to be unable to be pulled from the package manager normally. Or you can try rolling back the `idf-component-manager` tool to...

目前层级最高可以支持到 16 层，我们会尝试支持更高的层级，但是有几个涉及到的点我们需要评估和验证下。

You can differentiate between different Mesh networks by setting different Mesh IDs. When the ESP32 undergoes an unexpected software reset, it will attempt to connect to the original parent node...

If you need to prevent the reconnection to the source parent node after a reset, you just need to execute `esp_mesh_lite_erase_rtc_store` before the esp_restart.

Hi @HWuest , I apologize for the delayed response. I will promptly work on providing you with a sample code to optimize the creation of a rootless mesh network and...

Yes, for a routerless network, it is essential to specify a root node. Otherwise, the devices that power on later will not know whom to connect to, and it can...

You can use this [branch](https://github.com/tswen/esp-mesh-lite/tree/examples/add_no_router_example/examples/no_router) to test the no_router scenario with some internal optimizations that have greatly reduced communication latency.

Hi, due to the use of UDP for internal communication, packet loss is possible, so we do not recommend using this kind of back-and-forth interactive message flow. If any packets...

You just need to replace the original mesh_lite component of your project with the latest mesh_lite component.

https://github.com/tswen/esp-mesh-lite/tree/examples/add_no_router_example/components/mesh_lite The component has been updated. Additionally, for the "no_router" scenario, the following configuration must be performed. ```c esp_mesh_lite_config_t mesh_lite_config = ESP_MESH_LITE_DEFAULT_INIT(); mesh_lite_config.join_mesh_ignore_router_status = true; #if CONFIG_MESH_ROOT mesh_lite_config.join_mesh_without_configured_wifi = false;...