This means that for mesh, we should lower the inactivity time, or delay more than 6s the mesh nodes to re-connect to the router. yes, this is the solution. To understand the behavior of your case, please provide the logs for the root and node with the absolute timestamps. like this: [01-19 14:36:26...

After the station connected to AP, it will continue to receive the beacon from the AP, if the station does not receive a beacon frame from the connected AP for 6s, it will disconnect from the AP. You can call the following API to set this inactive time. /** * @brief Set the inactive time of the STA ...

This API is using to set the block time of `esp_mesh_send()`, it means the `esp_mesh_send()` will return timeout error if the mesh packet has not been sent successfully after 5s.

`esp_err_t esp_mesh_set_rssi_threshold (const mesh_rssi_threshold_t *threshold)` is used to set the RSSI threshold of the current parent. And if the parent's rssi is lower than ` threshold->low ` for a period time of ` duration_ms `, then the mesh node will post ` MESH_WEAK_RSSI ` event. The ` thres...

建议可以设置 sniffer 的 filter 只抓管理包， filter = filter | WIFI_PROMIS_FILTER_MASK_MGMT; esp_wifi_set_promiscuous_filter(&filter); esp_wifi_set_promiscuous_rx_cb(wifi_sniffer_packet_handler); // 先设置 filter 和 rx cb 再启动 sniffer esp_wifi_set_promiscuous(true); esp_wifi_set_channel(sniffer->channel, WIFI_SECOND_C...

Hi, thanks for reporting this problem. This is a bug in wifi code, we will fix it ASAP.

I have tested locally, if you call `esp_wifi_config_espnow_rate(ESPNOW_WIFI_IF, WIFI_PHY_RATE_LORA_500K)` after `esp_now_init()`, it can work successfully.

will fix the log level to avoid misunderstanding (change W to I).

Please update the IDF branch and have a try.

@ ChrisAlfred ,
Please provide your commit ID on release/v4.2, thus we can figure out the specific code.

The root cause for the crash issue has been found, will merge it as soon as possible.