Continuing the discussion from Issue with the new mobile cloud editor:
I have the same problem with the new web editor. Unfortunately when I clicked on "revert to old editor", nothing happens. It does not revert back to the old editor. The new editor seems like not able to recognize my device (or USB). The old editor was able to recognize my ESP32 Dev module almost immediately .
Any hint to solve this problem is appreciated!
Hi @thegreenfingers.
I tried it and it works fine for me. It might have been a temporary problem that was fixed since then.
Please note that the "old" editor will be shut down very soon so we should focus our attention on making sure you are able to use the "new" editor instead of any problems with reverting to the doomed "old" editor.
Do you still experience the problem if you try it again now? I just checked with my ESP32 Dev module board and everything works as expected.
If you are still experiencing the problem, please provide a detailed description of what you mean by "not able to recognize", including:
Make sure to include the full and exact text of any error or warning messages you might have encountered.
UPDATE: I just discovered that, although the "REVERT TO OLD EDITOR" link work as expected for me when I have a normal sketch open in Arduino Cloud Editor, nothing happens when I have an IoT Thing sketch open in the editor.
Are you using an Arduino Cloud IoT Thing sketch @thegreenfingers?
My web editor environment shows me this. Not sure if this is what you mean by "Arduino Cloud IoT Thing sketch" (I think so).
By the way, I tried connecting to my ESP32 device to my local Arduino IDE and i can compile and upload codes into it via the same com port. So I would say my connection was good. When I open up my IOT sketch, I do not see the connection to my device. Therefore I can't upload. I can compile codes with no error.
Yes, thanks for the clarification. I am able to reproduce the problem and have submitted a formal bug report to the Arduino Cloud developers. For now, please use Arduino IDE when you need to upload Arduino Cloud IoT Thing sketches to your ESP32 board.
You can use the Arduino Cloud sketchbook integration feature of Arduino IDE 2.x to get convenient access to all your Arduino Cloud sketches (including Thing sketches) for use in Arduino IDE:
https://docs.arduino.cc/software/ide-v2/tutorials/ide-v2-cloud-sketch-sync
Excellent! Thanks for the quick update.
Meanwhile, I will try to use the sketchbook integration feature of Arduino 2.0 that you recommended to compile and upload my code in my device.
Hopefully the Arduino cloud developers can resolve this quickly as the IOT cloud web editor is a convenient tool for me.
Thanks again!
Hello! I was also having this exact same problem, my ESP32 dev board is not being recognized. I followed this suggestion and once I had it done on the IDE, it became recognized as well with the cloud editor. Is this perhaps a system problem rather than on our boards? anyway, thank you for the help!
You make a very good point @eugil_v. The bug is specific to serial ports. Arduino Cloud also has an OTA (over-the-air) upload feature that allows you to uploading to boards via the Internet This feature is available if you have an "Entry" Arduino Cloud plan or higher. You must use the serial port to upload the IoT Thing sketch to a board for the first time, or if the board is no longer able to connect to the network using the credentials that were configured the last time the sketch was uploaded, but once an IoT Thing sketch is running on the ESP32 board with access to the Internet, it will produce an OTA port. You can then upload to that OTA port via Arduino Cloud. So the workaround of using Arduino IDE to upload the sketch is only required in cases where the board is not producing an OTA port.
Yes, the bug is in the code of the Arduino Cloud Editor website.
Earlier this week, the design of the Cloud Editor when using Arduino Cloud IoT Thing sketches was modified. The designers made the assumption that Cloud Editor would always be able to automagically identify which serial port was produced by the Arduino board being used as the IoT Device.
Such an automatic identification is possible with some boards because their serial port has a USB VID/PID identifier that is unique to that specific board model. This is the case with all of the official Arduino boards as well as certain models of 3rd party ESP32 boards.
However, many other ESP32 and ESP8266 board manufacturers use a general purpose USB to serial bridge chip (e.g., Silicon Labs CP210x, WCH CH340). These chips use the VID/PID provided by the chip manufacturer, meaning that any board (or even random consumer electronic device) that has that USB to serial bridge chip has the same VID/PID, and thus there is no way for Cloud Editor to conclusively identify the port of these boards. Prior to the Cloud Editor redesign, you could simply manually select the appropriate port (just as you can still do when using non-IoT sketches in Cloud Editor), so this lack of automatic port identification was only a minor inconvenience for the users of those boards.
I notice that, the new IOT cloud sketch editor no longer have "Revert to OLD editor" option anymore. So I would assume this is the latest upgrade of the IOT cloud editor. When I connect my device, the editor still could not recognize my ESP32 Dev board where in the very old editor it was working (as mentioned previously). I thought this problem was solved? I'm using Window 10.
That is correct. After giving access to both editors for some months in the interest of providing a smooth transition from the old editor to the completely rewritten new editor, the Arduino Cloud developers decided that the new editor had reached maturity and so the old editor was permanently removed. From now on, there is only one Cloud Editor.
No, it has not been solved.
The Arduino Cloud developers are aware of the bug and are already working on a fix. I will report back here if I have any news to share regarding a resolution.
Thank you for sharing.
Please keep us posted. I will wait for your update.
Good news, everyone! The bug that caused Cloud Editor to not recognize the serial ports of ESP32 and ESP8266 boards should now be fixed. I apologize for any inconvenience this has caused.
There is one remaining problem you should be aware of: if you have multiple Arduino boards (or other devices that produce serial ports) connected to your computer, Cloud Editor might pick the wrong port to use. I have submitted a report about this problem to the developers. For now, please disconnect any additional Arduino boards from your computer before opening an Arduino Cloud IoT Thing sketch in Cloud Editor when using a serial port to upload to the board.
Please give it a try and let us know if you still have any problems.
This topic was automatically closed 180 days after the last reply. New replies are no longer allowed.
