Today, I accidentally had my Arduino IDE software open while I was trying to work through the Arduino Cloud. This caused an error on my Arduino Uno R4 WiFi board.
However, the problem is that I can no longer reset the board that got messed up.
I’ve already tried the following steps without success:
Pressed the reset button twice
Unplugged and reconnected the Arduino
Restarted the computer
Tried using a different laptop
Overwrote the program with a simple “blink” sketch (the Arduinos still work fine through the IDE)
Performed a firmware update to version 0.6.0
Uploaded SSL root certificates (I don’t even know what that means)
In the Arduino IDE, the board works perfectly. However, in the Arduino Cloud, I can no longer connect to it — even though the device still appears there.
Does anyone have any idea what I’m doing wrong or how I could fix this?
Hmmmm . . . . . Sounds like a strange problem. If you had another Arduino maybe flashing the bootloader would work? I'm not sure as this as has never happened to me. Maybe clearing your browsers cache and if all else fails, contacting Arduino Support.
I'm not sure I understand what you mean by this. Please provide a detailed description of what you mean by "can no longer connect to it" in a reply here on this forum topic.
Do you maybe mean that you see the icon on the Cloud Editor toolbar?:
Hi @hastttt and @lodsam. Please clarify the relation between the two accounts. It is a bit confusing that @lodsam requested support, but then when asked for clarification @hastttt responded.
Is this one person using two different accounts? Or is it instead two different people? If the latter, are you working together on a project, or are simple two independent members of the community who are both experiencing problems using the UNO R4 WiFi with Arduino Cloud?
Understanding this will allow the forum helpers to most effectively assist you.
The suggestions I received on the last screen I have tried them all, both with different Arduinos and on different laptops. I have also uninstalled and reinstalled the Arduino software and Cloud Agent, but unfortunately without success.
Thanks to everyone who is willing to help me with this!
Click on the icon in the Windows notification area.
A menu will open.
Select "Open Debug Console" from the menu.
The "Arduino Cloud Agent Debug Console" page will open in your browser.
Click the third button from the right in the toolbar at the bottom of the "Arduino Cloud Agent Debug Console" page.
A menu will open.
Select "SHOW 'LIST' COMMANDS INLINE" from the menu.
Click the "CLEAR LOG" button that is located near the bottom right corner of the "Arduino Cloud Agent Debug Console" window.
Leaving the "Arduino Cloud Agent Debug Console" browser tab open, make another attempt at setting up the Arduino Cloud IoT Device, just as you did before when you encountered the problem.
Once the process fails, switch to the "Arduino Cloud Agent Debug Console" browser tab.
Click the "EXPORT LOG" button in the bottom right corner of the "Arduino Cloud Agent Debug Console" window.
A download of a file named agent-log.txt will start.
Open the downloaded "agent-log.txt" file in any text editor.
Press the Ctrl+A keyboard shortcut to select all the text.
Press the Ctrl+C keyboard shortcut.
This will copy the selected text to the clipboard.
Open a reply here on this forum topic by clicking the "Reply" button.
Click the <CODE/> icon on the post composer toolbar. This will add the forum's code block markup (```) to your reply to make sure the output is correctly formatted.
hello this problem happens when you have the IDE running at the same time. just quit the IDE and it will work. (at least that is the cause of this exact problem on my Mac) and I just spent a day trying to figure out what it was
That’s indeed how the problem started. The issue is that when I close the IDE, the problem doesn’t go away anymore. Even after restarting everything (including the computer), the problem still persists. When I use a different Arduino, the issue disappears. However, I would still like to be able to use the Arduinos that were affected. I did this with a class, so I now have this problem with eight Arduinos.