The new major release of the Arduino IDE is faster and even more powerful! In addition to a more modern editor and a more responsive interface it features autocompletion, code navigation, and even a live debugger.
For more details, please refer to the Arduino IDE 2.0 documentation.” –from arduino.cc website.
Thanks for sharing.
So, it means it’s no longer in the beta version?
Good Morning Sara,
Yes, Arduino IDE 2.0 has been officially released!
The “new” IDE 2.0 doesn’t support adding tools. So no uploading of data to LittleFS or other file systems.
Adding files to file system is easy; I use dplasa FTPClientServer library . only a few lines of code to add. I use Filezilla FTP Client for uploading, downloading, deleting. and creating directories.
Wow – thanks for that piece of information. These online forums are so often goldmines of info that would be really hard to find any other way.
Adding ftp capability to the ESP8266 code may allow me to now use Arduino UI 2.0. And as a bonus I will also be able to retrieve files (data) from the node using ftp, not just send files to the node. The downside of course is that it uses more of the code space in the ESP8266 memory.
Now I just have to figure out why OTA updates don’t work as well with 2.0. A brief look with Wireshark at the traffic on my LAN shows that 1.8 and 2.0 work differently and 2.0 is not very good at finding OTA nodes on my LAN.
Might try WiFiManager by Tzapu ; besides being a way to enter WiFi credentials, there is a option to update firmware.
Wow – WifiManger is slick. Thanks again.
In my case it might be a bit of overkill for my Arduino UI 2.0 issue. I’ve pretty much tracked that down to the way mDNS works and how 2.0 handles it for OTA updates. I think the easiest work around will be to use the OTA update python script directly – that seems to work with an IP address rather than mDNS names. My nodes are there, online, and responding. UI 2.0 is not catching their mDNS broadcasts for some reason.
Having said all that, my code always checks an otherwise unused GPIO and if it’s asserted then the code starts up in OTA mode only. That way if something I’m testing goes off the rails I have a way to recover then node via OTA and don’t need physical access to the node. WiFiManager provides a more rugged version of that, albeit at the expense of more code space again,