Hardware:
- Uno R4 WiFi;
- Linux Mint 21.3 (Virginia; completely up-to-date);
- up-to-date Cloud Agent;
- Arduino IDE 2.3.9
Problem(s):
I have looked for a 'structured' tutorial (etc) to introduce a relative newbie to the many extra layers of interaction that adding a WiFi link seems to add. But I have not found anything suitable. Any suggestions?
Lacking a structured approach, I have resorted to a hacking approach (or as a Swiss friend calls it, "learning by breaking"). Here are a few of my steps and stumbling blocks ⸺
- I managed to get the Cloud Agent installed and I am using the no-$ version for now (knowing that in this version, I cannot use the over-the-air [OTA] method of uploading sketches etc).
- I was able to 'Associate' my brand-new R4 WiFi 'Device' using the Cloud Agent
- I was able to create 'a Thing', and assign my R4 'Device' with that 'Thing'.
- I was able to associate a number of Variables to said Thing.
- I was also able to create a crude Dashboard, referencing the Variables associated with the Thing
- In the process of Associating a Device, the Cloud Agent seems to have created a bare-bones, device-specific Sketch (and named it "
untitled may28a.ino"); - ...After the Association of variables to the Thing, the Cloud Agent (automatically) modified the sketch so as to include 'triggers' which would cause changes to the Variables to be uploaded to the Cloud (and so made available to my remote Dashboard).
Up to this point, the hacking approach does reveal how the various elements of the WiFi / Cloud Agent system interact, and that feels "promising". However.... Here is where matters take a 'dark' turn:
If I upload any simple Arduino Example sketch to the R4 WiFi board (using a USB connection as I cannot use OTA method with the zero-cost Cloud service), that action immediate destroys any WiFi connectivity. Specifically, the board goes "dark", the on-board dancing LED display no longer functions, and I cannot find any method for re-establishing the online connection with the Device using the Cloud Agent. I even tried quitting the Agent, re-booting my desktop computer, and resetting the R4. Nothing.
In a desperate attempt to recover, I tried to "Update the Firmware" of the R4, via the Arduino IDE v2.3.9. That did not re-establish the WiFi connection, and I could NOT use the Cloud Agent to detect the R4 board.
I then deleted the Device (within the Cloud Agent), and tried to re-Add the Device, but that also did NOT work (Adding the device seems to have stalled-out completely, and it could not link to the R4 WiFi board).
After concluding that I had somehow "smoked" my R4 ⸺ and had nothing to lose by further experimentation ⸺ I followed the method outlined at Arduino Support: Re-Install ESP32 Firmware . After a bit of further fussing around with the Cloud Agent, that seems to have got me back to a functioning R4 board: I was able to get the Cloud Agent to recognize and Add the Device and to re-associate the Device with my Thing, and I now have an active cloud connection to my R4.
Interesting observation: having re-installed the ESP32 Firmware, and even after the Cloud Agent "updated" the R4 firmware during the process of Adding a Device....the dancing LED cloud image is definitely different after the re-installation of firmware. Specifically, the original dancing-LED 'cloud' stayed in one place on the LED matrix with the exception of a wiggling internal loop (or internal 'tail', supposedly to emulate how the data "cloud" was active in the way that an atmospheric cloud changes shape); but NOW, the LED 'cloud' outline does not change shape but rather shifts from left-to-right, and then back again. I include this observation because, for a person with intimate knowledge of the R4, it might indicate which version of the Firmware(s) are currently running on my R4.
2nd Interesting Observation: I keep getting pop-ups ⸺ WITHIN the Cloud Agent itself (!!!) ⸺ telling me that I must install the Cloud Agent. What kind of weird gaslighting is that? What does it possibly mean?
So after a full day of frustration, I have what is (essentially, seemingly...) an out-of-the-box R4 with basic connectivity via the Cloud.
Clearly, I do not understand how to craft a Sketch that will upload (via USB connection) to the R4 and not destroy the WiFi connectivity.
I believe that the untitled may28a.ino , automatically created by the Cloud Agent when I first established my connection with this particular R4 board, holds the key.....particularly, the fact that this automatically generated Sketch includes the helper file #include "thingProperties.h"
Pointers? Suggestions? Major themes that I am missing here?






