-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
esp_mesh_lite_get_level returns 0 (AEGHB-812) #123
Comments
Can you provide the log? esp_mesh_lite_get_level returns 0, which means WiFi is not connected properly. |
there is no more log.this happen in the code "uint8_t layer = esp_mesh_lite_get_level();". If I execute the function "esp_restart" and then restart, it's still the same. If I reset via hardware, the function "esp_mesh_lite_get_level" returns 1 or greater than 1 and then it works. |
|
The device is next to the router, and it doesn't feel like it's not connected to Wifi |
Please update mesh lite to the latest version and try again. |
Checklist
How often does this bug occurs?
rarely
Expected behavior
esp_mesh_lite_get_level should be return 1 or grater then 1
Actual behavior (suspected bug)
When the wifi mesh is networked, when the function esp_mesh_lite_get_level is called to obtain the level, 0 is returned. According to the code on GitHub, the function returns 1 to indicate that it is a router node. If the return value is greater than 1, it is a leaf node or an intermediate node. However, the return value is not defined as 0, and now 0 is returned, and the data is not processed, resulting in the module not being able to send the data to the route through the mesh.
Error logs or terminal output
Steps to reproduce the behavior
I used 15 modules to network, and after 7 days of operation, 2 modules had this situation
Project release version
mesh lite version:v0.9.0 - 2023-10-31
System architecture
ARM 64-bit (Apple M1/M2, Raspberry Pi 4/5)
Operating system
Windows
Operating system version
freeRTOS
Shell
other (details in Additional context)
Additional context
No response
The text was updated successfully, but these errors were encountered: