//ESP_ERROR_CHECK(esp_event_loop_create_default()); // Create the default station interface esp_netif_create_default_wifi_sta(); // Initialize the Wi-Fi driver with default configuration wifi_init_config_t cfg = WIFI_INIT_CONFIG_DEFAULT(); ESP_ERROR_CHECK(esp_wifi_init(&cfg)); // ...
If I replace esp_event_loop_create_default with esp_event_loop_init(nullptr, nullptr), which I understand is deprecated, the error goes away and everything still works fine. The strangest thing is that when I created a new project to test this, neither esp_event_loop_create_default nor ...
(): esp_netif_init() returned \"%s\".",esp_err_to_name(err));continue; }// step 1.2// identify the event handler.err =esp_event_loop_create_default();if(err != ESP_OK) {ESP_LOGE(TAG,"wifiInit(): esp_event_loop_create_default() returned \"%s\".",esp_err_to_name(err))...
The problem I'm having is that theesp_event_loop_create_default()function seems to call only one of the event handlers (mqtt_event_handlerorevent_handlerfor Wi-fi). It is not clear for me how do I have to declare the event handlers so both of them are called after the program starts...
Hi everyone, in my project I'using the wifi example coupled with the Modbus Master (esp 32, v 4.2). Is possible that some bugs in esp_event_loop_create_default() function leads to the error showed on the screenshot? How this function work in detail?