It was a ton of fun to use the ESP32! Best of luck Chad!

Great! Make sure to take a close look at the comments, because you'll need to included the OTA code in every sketch.

@@programmingelectronics I figured it out after first selfoverwrite. Honestly it should be mentioned in the video that all setup and ArduinoOTA.handle(); in thel loop to be placed. It could be trap for many young players as I have read comments. What I'm actually working on is bitcoint ticker with nice VFD display. So I need Wi-Fi during program runtime. I plan to display also progress during OTA update as it is currently sent to serial.

Glad it helped - please take a close look at the comments here. One thing left out in this video is making sure that your update code also includes the OTA code, or else you won;t be able to perform the OTA more than once.

Thanks!!

Great to hear! There is also an updated video about this, you should be able to find linked in the comments that is definitely worth watching, as I left out something important in this lesson.

Not yet -> I need to do a follow up on this!

@@programmingelectronics Thanks I will be waiting

Great question! I'm not completely sure and it probably depends, but I think deep sleep usually implies that WiFi is off, which would rule out OTA. But perhaps, during its brief wakeup moments, you have it enable an OTA window for a short period?

You could potentially do it in reverse where it is checking a server for a new valid binary file to download and flash every time it wakes up, it wouldn’t be as quick or convenient but would do the trick.

Sorry for this, that was an oversight in this video! Please see the pinned comments. Here is the updated video: ukposts.info/have/v-deo/b4iVp5loqKeg06M.html

Not sure to be honest! There is this project on github: github.com/fabio-d/esp32-tuntap I think if you search for "esp32 as wifi dongle" you might be able to dig something up. Best of luck!

This is a great question! I just tested this with an ESP32 Wroom DA module, and yes, it shows up as a network port (with a WiFi symbol next to the board/port in Arduino IDE 2) in addition to it showing up as a serial port. Side Note: This video misses a key step, please watch our more thorough walk through of ESP32 OTA here: ukposts.info/have/v-deo/b4iVp5loqKeg06M.html

This is a great question! I am not sure to be honest, but I see if we can do try it on the channel! Thanks for the great question!

You would need to set up port forwarding on the router, otherwise a computer like a Pi on that same network would be needed to communicate with it for this method unless it were to check a server (potentially on your network) for the updated binary, there’s an example that uses Amazon AWS servers but it can be any server you can upload to.

Do you have a code for this? If you do, send the github

That is correct. What I should have done is include that OTA function again!

@@programmingelectronics Would be awesome if you could explain that in more detail in a pinned comment :)

Great!

I should have read deeper, just found my answer in other's comments.

Sorry about that Jim - this video could have been done much better!

Yes, that is correct.

FRG - what this video left out was making sure to include the OTA code in the new sketch you upload. There are a couple comments about that below. Sorry for leaving that out!

Thanks Dave! I need to release another video on this covering just that (and it's a shame I didn't in this video) It's pretty straightforward, for every new sketch (aka update) you upload, you include that ArduinoOTA.onStart function, and the ArduinoOTA.begin() function in setup, and then in the loop you make a call to ArduinoOTA.handle() I am not sure how often ArduinoOTA.handle() needs to be called, but I would imagine you do not want any delays inside your loop code else it would mess up the OTA I believe. I hope this helps some! Thanks again for watching!

@@programmingelectronics thanks for the reply, makes sense to me. I guess I was running before I could walk haha… shame as your video has to be the best out there for demonstrating how easy this is and I can’t understand why it’s taken me so long to come across your video. Thanks - Dave

Great question, but to be honest, I am not sure of the answer! Sorry I couldn't be of more help on this!

@@programmingelectronics 🙏🙋‍♂️

Thanks for the note! Maybe it's my router - the 2G always seems to connect quickly.

I assumed it meant 2.4GHz vs 5GHz, but also had a moment of pause when I heard it.

@@dieofthebeholder Makes sense now. Good call!

That 2G and 5G confused me too. I also didn't make the link between 2G and 2.4Ghz or 5G and 5 Ghz. Could be your 5Ghz is effected more by your walls and floors etc.

I have not tried this yet but in theory since this is an ESP32 and has RTOS you should be using RTOS tasks to avoid any interference with Wi-Fi and anything else.

It was my bad, if you read some other comments, you can see that you need to ket the OTA code in the sketch you upload, or you'll be out of luck.

Ive got this working fine now, i had changed the partition scheme so no OTA, its now at minimal spiffs and working OK, only issue now is it will only upload code once then i lose the ip port to send code again.....

My apologies for this issue Tony. Here is a video that more correctly covers this topic: ukposts.info/have/v-deo/b4iVp5loqKeg06M.html

Thanks for watching!

Hi Reno! OK, it probably shouldn't take more than 30-45 seconds to upload to your ESP32 board, so 3 hours is definitely an issue. I would attempt to uplug the board, and plug it back in, also perhaps try closing the Arduino IDE, and opening it again. You also might pressing the boot button on your board if it has one. Then try uploading again. Side note, is this an issue with every sketch you are trying to upload?

​@@programmingelectronics Yes, everytime I upload new code, I dont get message "uploading 100% done". always "uploading .............." the esp32 can work. but the process is not finished, always writing " uploading ..............." I have done to boot. but not working either. when I upload new code, the esp not responding.

Great question Amurao! Yes it is!

Programming and electronics ;)

I wasn't thinking when I said that - sorry about that!

@@programmingelectronics You must have been 'thinking' otherwise you would not have said that!

@@rodneytapit5636 I wasn't thinking clearly :)

You can, just take code you made for example a blink program then copy the 3 sections of the blink program (Global, setup, loop) and paste them in the 3 sections of the OTA program leaving the OTA stuff untouched and there you have it, now you can download and change your blink program as many times as you want with OTA.

​@@paulkoepnick7122 Callbacks have a loop which is usually blocking but some have nonblocking options, but if it works as you say, then it should be easy to run in the background of any program. Another option if blocking is an issue, as I have only worked with ROS and MQTT callbacks: ESP32S devices are dual core, so your second core can run the OTA server while the other runs your primary program. This is especially handy if you need to run multiple callbacks from different functions as the loops wont interfere and reduce chance of threading error due to improperly incorporated callback loops. If you want to always program this way, make a template to insert into all your other codes, the method requires no difference in setup between uploads. Also, you do not need to read your IP from the monitor (which comes from your wifi setup section using the localIP() constructor in the setup not the OTA callback section in the setup) I suggest always creating a static IP and knowing all devices on your network. Static, vs DHCP, significantly improves connection reliability and the amount of time it takes to connect to a network using general IoT devices. This may help a few of the people who may ask the same questions as Ive seen below get some ideas to try out.

Sorry about this issue. It is mentioned in the comments. Here is an updated video: ukposts.info/have/v-deo/b4iVp5loqKeg06M.html

You need to include the ota code for every update in addition to your regular code changes, not just the first time. It needs to be a part of your project permanently if you want to always be able to OTA update.