WiFiManager VS esp-idf

Hello. Some time ago I' ve strugled with seting up wifi manager in esp_idf framework. Most popular wifi manager made by tzapu was not working on esp-idf framework inside PlatformIo. So I have found tonyp7. It started to work after many changes in library code and makefiles. I have some free time and I can make WifiManager suited to bare esp-idf and esp-idf inside PlatformIo. My question is- do somebody need this ? Maybe there are alternatives which i did not find and my work is pointless. Please share your opinion

Is that fork needed still? It seems like the main project claims support for esp32 now? https://github.com/tzapu/WiFiManager

I use WifiManager (https://github.com/tzapu/WiFiManager) .. it will setup the device as an access point you connect to and configure the wifi.

Reminds me of this. I will try it out.

WifiManager (https://github.com/tzapu/WiFiManager or https://registry.platformio.org/libraries/khoih-prog/ESP_WiFiManager_Lite):

If you have other code that does not rely on being connected to WiFi I would look into running WiFi manager in none blocking mode. There is an example here: https://github.com/tzapu/WiFiManager/blob/master/examples/NonBlocking/AutoConnectNonBlocking/AutoConnectNonBlocking.ino

// I won't hide these informations bellow because this is just a test. You can compile on your esp32 #define BLYNK_TEMPLATE_ID "TMPLc9VK-ym3" #define BLYNK_DEVICE_NAME "Wifi Bluetooth ESP32 DHT Station" #define BLYNK_AUTH_TOKEN "IzH-vvhVf0uLJaV54Ziero7kjUiFeq5g" #include // https://github.com/tzapu/WiFiManager #include #define TRIGGER_PIN 22 #define LED_PIN 23 TaskHandle_t Task1; int timeout = 120; unsigned long blink_timer; char auth[] = BLYNK_AUTH_TOKEN; WiFiManager wm; void wifi_stuff( void * pvParameters ){ Serial.print("wifi_stuff running on core "); Serial.println(xPortGetCoreID()); for(;;){ if(!Blynk.connected()){ wm.autoConnect(); Blynk.config(auth); Blynk.connect(5000); } if ( digitalRead(TRIGGER_PIN) == LOW) { WiFiManager wm; wm.resetSettings(); wm.setConfigPortalTimeout(timeout); if (!wm.startConfigPortal("OnDemandAP")) { Serial.println("failed to connect and hit timeout"); } wm.setEnableConfigPortal(false); } } } void setup() { WiFi.mode(WIFI_STA); // explicitly set mode, esp defaults to STA+AP Serial.begin(115200); Serial.println("\n Starting"); pinMode(TRIGGER_PIN, INPUT_PULLUP); pinMode(LED_PIN, OUTPUT); wm.setEnableConfigPortal(false); wm.autoConnect(); Blynk.config(auth); Blynk.connect(5000); //blynk connect timeout xTaskCreatePinnedToCore( wifi_stuff, /* Task function. */ "Task1", /* name of task. */ 10000, /* Stack size of task */ NULL, /* parameter of the task */ tskIDLE_PRIORITY, /* priority of the task */ &Task1, /* Task handle to keep track of created task */ 0); } void loop() { Blynk.run(); //bellow is for debug if (millis() - blink_timer > 300){ digitalWrite(LED_PIN, !digitalRead(LED_PIN)); blink_timer = millis(); Serial.println(Blynk.connected()); } }

Oh and if you're implementing it yourself and want a captive portal look into WifiManager. It's pretty much the standard ESP captive portal.

IDF contains stuff like https://github.com/espressif/esp-idf/blob/master/pytest.ini and https://github.com/espressif/esp-idf/blob/master/tools/ci/idf_pytest/constants.py which are not part of the pytest-embedded package.

ugh.. arduino.

Better to start with ESP-IDF, there's a pretty full featured well documented web server, and a lot more.

https://github.com/espressif/esp-idf/tree/master/examples/pr...

Hi, I have device ESP32-S3-DevKitM-1 and i want to catch keystrokes from keyboard. I tried using this https://github.com/tanakamasayuki/EspUsbHost and example from espressif https://github.com/espressif/esp-idf/tree/release/v5.1/examples/peripherals/usb/host/hid/main but when i connect keyboard it is just connecting and disconnecting. Can anyone help me with this?

According to this page, coexistence of WiFi and 802.15.4 is now supported. Thread is based on 802.15.4.

The example: https://github.com/espressif/esp-idf/tree/master/examples/openthread/ot_br "The example could also run on a single SoC which supports both Wi-Fi and Thread (e.g., ESP32-C6), but since there is only one RF path in ESP32-C6, which means Wi-Fi and Thread can't receive simultaneously, it has a significant impact on performance. Hence the two SoCs solution is recommended."

The latest, but it was a few months ago. The results were off by 400 meters, and many persons have the same problems : https://github.com/espressif/esp-idf/issues/8976

Use an official I2C example form the IDF. Like this: https://github.com/espressif/esp-idf/blob/master/examples/peripherals/i2c/i2c_simple/main/i2c_simple_main.c I’stand corrected with respect to the call order, it appears the driver install comes later. Your speed is unusually low, use the default speed of 400K. If you still get the error in the setup, use the source: the IDF is fully source distributed. Look into the implementation of the function, which errors occur form which code parts. Use ESP_LOGE or similar calls to get output messages on where you are getting to within the code. So that you learn where it’s expectations aren’t met.

You'll need the core dump and the ELF file, assuming you have them both, you will need espcoredump.py (Github), but it's easier to install the whole ESP-IDF (docs.esspressif.com) package as the coredump tool has dependencies.

I habe: https://github.com/espressif/esp-idf/tree/efe919275e8f4516ffd5f99f9a59e9d3efbae281/examples/peripherals/usb/host/msc