esp | Extensible Service Proxy

WiFi channels 12-14 are not used in some countries (e.g. US). Perhaps the ESP32 AP picked one of those channels, and ESP8266 is configured by default with settings from a country which doesn't allow them. Set the AP channel to some reasonably safe value in range 1-11.

I can see that the default channel should be 1, but I'd suggest experimenting with it, perhaps setting it to 6:

You need to parse the incoming url, depending on the request you are sending with your form. The most common is a POST request, regarding to HTML forms.

If you send a POST request to your ESP, then your data will be in the body and you should parse in there. You will get a request like this (Reference: https://developer.mozilla.org/en-US/docs/Web/HTTP/Methods/POST)

My supervising professor had a look at the problem and found the solution. Here are the changes that were needed to be made:

Include the following line in the sdkconfig file: CONFIG_ESP_HTTPS_SERVER_ENABLE=y

“config” instead of “conf” in the file file_server.c and the configuration for the http server is a subcomponent of the https configuration and needs a "httpd.” after the “config.”:

I'm still not at all sure what you're confused about... ... but this pseudo-code might help:

CALLER:

update_FILES("../File/accounts.dat","../Files/movements.txt", key);

P-CODE:

The root cause of this error is that the struct esp_netif_t is a private type in the netif implementation. You're not supposed to create any objects of this type, only pass around handles (pointers) to it.

I suspect you've misunderstood what esp_netif_get_netif_impl_name() does. According to the API doc it takes a handle to a esp_netif_t and returns the name corresponding to this interface.

What you seem to be after is retrieving the handle to your interface in the first place. For this the (rather terse) API doc suggest a few other functions, e.g. esp_netif_get_handle_from_ifkey(...) for searching for interfaces using something called interface key (no idea, sorry, but google helps there) or esp_netif_next(...) for iterating over interfaces.

According to this forum post you might want to try something like this:

I call checkValue function on load to check the current value and then on change to check the new value and perform the action to the selected value type

I fixed this by adding

display.setPanelsWidth(2);

display.setMuxPattern(SHIFTREG_ABC_BIN_DE);

because my led is combined by 2 matrix 32x16.

It's quite likely the IP addresses that you use and possibly your current network setup. If you run Flask locally, by default it will use 127.0.0.1 (localhost) and the application can only be reached from your own computer. Other hosts on the network cannot. So your intuition is correct, you need to run it on 0.0.0.0 so that the application becomes accessible on any interface, not just localhost but also the LAN IP address and WAN IP address (provided you have got one).

Now the remaining question is, is 10.104.2.114 is the correct address for your PC where the Flask application is running ? Assuming that you use DHCP, the IP address is subject to change. From what you are saying your ESP8266 is on the same network but I think the connection sharing applies some form of isolation between guests (possibly by VLAN). So, for that reason, the guests on that network may not be able to see each other and this is by design. It is normal for wifi hotspots to segregate traffic per client.

Putting all your devices on the same router/switch could work. Note that you can still use your home router/switch to connect devices, even if Internet access is out of service. This is something you could try, as long as your hardware is in good condition.

While creating the task iot_thread (presumably by calling xTaskCreate() or xTaskCreatePinnedToCore()) you've allocated insufficient stack space. Since you haven't posted the code where you create it, I can't be more specific. Start by increasing your current stack 2 times, see if it still crashes. If that doesn't help, repeat.

The usual approach for determining a task's stack size is to set the stack very large (perhaps 8-16 KiB) and let the task run its more stack-intensive stuff for a while. Then use the task monitoring functionality in vTaskGetInfo() to see how much unused stack it has. Finally you can reduce the stack size to the actually used amount plus a sufficient reserve. I tend to keep 1-2 KiB of stack in reserve.