Device Security Update Required

My NANO 33 IOT device is offline and has a yellow notice, 'Security update required'.
I have uploaded sketch from both cloud editor and offline editor. Uploads are done with no errors but the yellow flag on my device won't go away.
Need help here.

Same here using a Heltec ESP32S3. Have done multiple uploads as per instructions both OTA and via USB. The uploads are successful but the yellow "Security update required" alert does not go away.

Can we rely on the update being successful regardless of the alert status?

Finally got it working. The instructions are not ckear. I had to use the firmware upater on the IDE and then upload my sketch.
Device is now back onlie.

Thanks for taking the time to post an update @swordfish45! I'm glad you were able to complete the security update.

The approach you took of using the the "Firmware Updater" feature of Arduino IDE is completely valid. However, for the benefit of other Arduino Cloud users who might read this thread while researching the subject, I should state that you can also accomplish the security update using Arduino Cloud. Arduino Cloud also has the necessary firmware update capability. When you upload an Arduino Cloud IoT Thing sketch using Arduino Cloud, it will automatically perform the required firmware update.

I'm not sure why your Device remained in the "Security update required" state even after you uploaded a sketch using Cloud Editor. Since you already found a solution, I think it is best to just carry on instead of forming hypotheses about why that might have occurred (since it would be quite difficult to test those now that the problem has been resolved).

Hi @sciroccotorc. Are you still experiencing this problem? If so, I'm going to ask you to provide the full verbose output from a compilation.


:exclamation: This procedure is not intended to solve the problem. The purpose is to gather more information.


Please do this:

  1. Open your Thing sketch in Arduino Cloud Editor, as usual.
  2. Click the "Settings" icon at the bottom left corner of the page:

    The "Settings" panel will open.
  3. Select the "Verbose output" radio button under the "Console verbosity" section of the "Settings" panel.
  4. Click the button in the Cloud Editor toolbar.
  5. Wait for the compilation to finish.
  6. If the black "Console" panel at the bottom of the Cloud Editor page is minimized, click the ˄ icon at the right side of the "Console" toolbar to expand it.
  7. Click the icon in the top right corner of the black "Console" panel at the bottom of the Cloud Editor page that looks like two pieces of paper ("Copy Console Output"):
  8. Open a forum reply here by clicking the "Reply" button.
  9. 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 error messages are correctly formatted.
  10. Press the Ctrl+V keyboard shortcut (Command+V for macOS users).
    This will paste the compilation output into the code block.
  11. Move the cursor outside of the code block markup before you add any additional text to your reply.
  12. Click the "Reply" button to post the output.

In case the output is longer than the forum software will allow to be added to a post, you can instead save it to a .txt file and then attach that file to a reply here.

Click here for attachment instructions

  1. Open any text editor program.
  2. Paste the copied output into the text editor.
  3. Save the file in .txt format.
  4. Open a forum reply here by clicking the "Reply" button.
  5. Click the "Upload" icon (Upload icon) on the post composer toolbar:

    The "Open" dialog will open.
  6. Select the .txt file you saved from the "Open" dialog.
  7. Click the "Open" button.
    The dialog will close.
  8. Click the "Reply" button to publish the post.

Alternatively, instead of using the "Upload" icon on the post composer toolbar as described in steps (5) - (7) above, you can simply drag and drop the .txt file onto the post composer field to attach it.

Hi @ptillisch, thanks for helping with this. The dev board is still showing the yellow !UPDATE symbol despite numerous upload attempts. The console output is attached below in a .txt file. The sketch I'm uploading is just the basic one that is auto-populated when you create a new Thing. loop() is empty.
FQBN esp32esp32esp32s3.txt (374.4 KB)

Edit: The !UPDATE icon has gone. Not sure what I did.

Thanks! This was the information I was interested in:

I had a hypothesis that the problem might have been caused by your sketch being configured to use an older version of the "ArduinoIoTCloud" library. The security update requires the latest version of the library. However, I can see now that your sketch is correctly using the latest version of the library, so this information disproves my hypothesis.

Great news! Thanks for taking the time to post an update.

The alternative hypothesis I had was that the problem you experienced was caused by your Device not being able to connect to the Arduino Cloud servers for some reason. The "Security update required" marker will only be removed from the Device in the Arduino Cloud user interface after the first time the Device connects to Arduino Cloud after the Thing sketch compiled with the latest ArduinoIoTCloud library is uploaded.

Since the problem has now been resolved somehow, we don't have a way to know exactly what caused the problem, but we can be glad that it is fixed anyway.

Regards, Per

1 Like

I agree and I did try a number of uploads from Arduino cloud which did not make the security marker disappear.
My device happens to be in my garage so as a final atttemp I brought it in, whcih is a pain in the butt, and connected via USB. I then tried an upload and still the marker remained.
Finally I reverted to the firmware updater and it worked.
I have no idea why it would not work from the cloud editor but all is fine now.
Have a good day.

A post was split to a new topic: I'm giving up on Arduino Cloud

This topic was automatically closed 180 days after the last reply. New replies are no longer allowed.