Tian Sen Wen
Tian Sen Wen
The departure of a child node is not always intentional; it may result from unexpected events such as power outages or crashes. In such cases, the application layer often cannot...
Could you please provide the complete log files and operation steps? I tested LAN OTA using v5.5 without any issues.
命令中有一个 --channel 11，需要更换成设备当前所在的信道。
但确实存在接收 wireless debug log 失败的问题：https://github.com/tswen/esp-mesh-lite/commit/c4e40b86e742b5c2fd717895d5e49b2a0d2d8f2c 可以参考这个进行修改，后面会将该 fix 合入到 release/v1.0 分支上去。
In the current version, LAN OTA transmission fails when there is a mismatch between the OTA_DATA_LEN and OTA_WND_DEFAULT values on the firmware sender and receiver sides. Solution: Use an intermediate...
Apologies, I missed a point earlier. When upgrading from v1 to v2, the ESP32 should not restart after completing the upgrade (CONFIG_AUTO_RESTART should be disabled). Then, the next-layer device needs...
Yes, you are correct. The key point is to ensure that OTA_DATA_LEN and OTA_WND_DEFAULT remain consistent between all devices requesting firmware and those providing firmware during LAN OTA.
When calling the esp_wifi_sta_get_ap_info interface to retrieve AP information, if the device is not currently connected to an AP, this log message will appear. This log does not indicate an...
Could you enable logging by calling esp_mesh_lite_core_log_enable(true) right after esp_mesh_lite_init(), then provide the complete log file from power-on until the issue occurs?
Periodically print free heap size to check if there's sufficient available memory.