Thanks Dave. 👍

Sure. You can serve static content, or integrate some functions into the server to serve dynamic content. The thing you have to contend with will be slower processing, a little slower transfer, and maybe adding an SD for storage space. You'll probably have to do some low-level http stuff, like sending the right headers, encoding changes, etc. I can't remember how much of that I did in the demo scripts.

I should set one up that folks could visit. Maybe. In my spare time.

Yes. The server script has a "client_timeout" variable. It is set at 10 seconds. The idea is that you don't want to keep a socket open if there is no communication (maybe the client quit and didn't tell you). So, after the timeout it closes the socket. Just send a byte of information from the client to the server every few seconds and it will stay open. You can also make the timeout longer. Or you could completely remove it if you want.

@@ClaytonDarwin Oh thanks for replying that fast ! And I think i understood that part, the problem I have is that in your video, when you run the script, both (server and client) are sending and receiving 'Data Line X'. In my case, server doesn't receive 'Data Line X' whereas connection between them is established. I apologize if it's something obvious, I've just started MicroPython like 2 days ago, thank you again for your help :)

Do you have both screens open so that you can see them connect? I mean, are you watching the ESP32 printout and the desktop printout?

Yes both are open, esp32's terminal shows me that my desktop managed to connect (it shows desktop's IP and other stuff about connection) but it doesn't receive data at all. That's why timeout appears and closes the socket, I watched all the video and did exactly what you did. If it's something you've never encounter, i'll keep trying, but i really have no clue about the problem :(

Okay, I just downloaded the script and tried them. Here is exactly what I did: 1) Edit "opensocket_server_example.py" and set the essid and password to your local values. 2) Load "main.py", "nettools.py", "opensocket_server.py" and "opensocket_server_example.py" onto the ESP32. 3) Reboot the ESP32 and watch that it connects to wifi. Also watch for the IP address. Watch for this line: "OpenSocket Server listening on addr ('0.0.0.0', 8888)." 4) Edit "opensocket_client.py" and add the IP address to the ESP32. 5) Run "opensocket_client.py". I recommend using the command line. 6) Watch for the following lines to show up: On ESP32: "Client 1 - OPEN - IP:192.168.254.10" # IP address will be different. On Desktop: "SOCKET CONNECTED" On ESP32: "APP LINEIN: b'_client:1'" On ESP32: "APP LINEIN: b'_ip:192.168.254.10'" # IP address will be different. On Desktop: "SENT: Data Line 1." On ESP32: "APP LINEIN: b'Data Line 1.'" On ESP32: "RETURN: b'BOUNCE Data Line 1.'" On Desktop: "GET: b'L1 BOUNCE Data Line 1.'" This works for me. If you aren't getting the same output, copy and paste the output you get.

I haven't done much with using an ESP as an access point, but the error might be related to the IP. The access point doesn't really have any real IP address. Instead they use 192.168.4.1 as the address to any sockets it runs. Are you using that?

And the access point server socket shouldn't be bound to an address: sock.bind('',80)

Here is a tutorial (not mine): randomnerdtutorials.com/micropython-esp32-esp8266-access-point-ap/

@@ClaytonDarwin Yes i am using 192.168.4.1 as the ip address. I am gonna quickly try out that tutorial. Thanks for answering ☺

@@ClaytonDarwin Omg cant believe it's actually working. Thank you so much!😀

Some call me... Tim!

You would have to devise your own handshake and error checking protocol if you wanted to be equally reliable to TCP, and at that point you would be reducing the speed advantage of UDP. So I stayed with TCP.

@@ClaytonDarwin OK，got it

@@ClaytonDarwin one more thing, how about OTA function for micropython ?

Not for the core OS. You can update application scripts.