) or by selecting more than one Device ID Target from the Devices area. By effectively using Tags and/or Groups, a strategy can be developed to update as many or as few devices under your account as you choose.
Preface to OS Firmware Update Task guidance:
Scheduled Tasks are saved with an .xml filename extension (in the following tutorial, the file you downloaded within the zip file under Requirements is already created for you, and is called Update-Linux-OSFW.xml).
- Prior to running the procedure below, Update-Linux-OSFW.xml must be loaded into a standard text or XML editor.
- Within the editor, on line 38 of Update-Linux-OSFW.xml, replace the text [YOUR FIRMWARE FILENAME GOES HERE] with the filename of the .bin firmware image for your particular Gateway (Example: 82003150_C.bin) and save your file. This is a case sensitive entry, and if the filename is entered wrong, your Gateway OS Firmware Update Scheduled Task will fail.
Device Cloud/Remote Management Settings Update Task tutorial:
You should see the message Operation Submitted Successfully if your new task was successfully scheduled to run on the devices which you selected.
- Login to your Device Cloud or Remote Manager account
- Go to the Data Services --> Data Files area and open the my_tasks folder by double-clicking the folder:
- Create a directory under my_tasks, called Update-Linux-OSFW:
- Upload the Update-Linux-OSFW.xml file to your my_tasks folder:
- Double-click on the Update-Linux-OSFW folder you created in Step 2 to open the folder.
- Upload the the appropriate OS Firmware file for your XBee Gateway ZB or ConnectPort X2e for Smart Energy gateway (See the Requirements section above for file information):
- Go to the Device Management--> Schedules tab and press the New Schedule button:
- Select the My Tasks tab on the left, and select the Update-Linux-OSFW task listed (if you entered the filename of your firmware file correctly earlier, the task should load on the right as in the example):
- Select the Schedule >> button on the bottom right corner, to be taken to the second page of the Scheduler:
- At the second Scheduler page, various options are listed to run the Scheduled Task Immediately or to schedule for a time/date in the Future. You'll also need to select the Target(s) to run your Task on. You can select individual devices, by Group or by Tag:
Note on Disconnected Devices:
If scheduling a Task on a device, the Scheduled Task will time out (fail) after one week if the targetted Gateway(s) never attain a "Connected" state with Device Cloud to receive the OS Firmware update launched by the Task.
Once the Update Task has been tested and verified to work, it can be used to easily update multiple batches of devices via Digi Device Cloud.
Executing DBL-OS-update.xml on Gateways from Device Management --- Devices
- Log into your Device Cloud account
- Go to Device Management -> Devices
- Highlight, then right-click on any Gateway(s) you want to update
- Go to More -> Tasks -> DBL-OS-update.xml
- When prompted at the Scheduled Operations popup, click Yes.
How to check on Scheduled tasks which have run
- Browse to Device Management -> Operations
- Look for listed operations which are called "DBL OS Update":
- Double click on an operation to observe the details of the individual steps within the Scheduled Task
- Verify whether the Task was successful or failed.
Return to Device Management -- Devices to view the new Firmware version listed for your Gateway, and Gateway OS Update complete Description which the Scheduled Task writes to your Gateway:
The Description field of your Gateway is useful as an aid for you to see which Gateways under your inventory have been updated. You can edit this field to write a different "Success" message in the Description as preferred, in the same way you edited the Scheduled Task earlier to include the correct OS Firmware filename for your Gateways.
Keep in mind that a Scheduled Task operation can only have complete success, if all Gateway target(s) selected were successful in doing so. If a status of Failed is listed for your operation, it means that one of the steps which were part of your Scheduled Task failed, or that any of the device targets selected for the task weren't successful at connecting and receiving the update after a week (even though other device targets may have succeeded).
An operation with a status of Successful means that all commands within the Scheduled Task ran on all the device targets selected for update by the Task completed successfully, i.e. complete success for all devices, not partial.
Device Cloud Documentation page – Tech Support page for Device Cloud documentation
Device Cloud User Guide – see Operations and Schedules sections
Device Cloud Programming Guide – see Scheduled Operations
HOW TO: Example for Configuring a Device Cloud Task to Set a Gateway XBee PAN ID
HOW TO: Remove a Task listed under the My Tasks tab when creating a new Device Cloud Schedule
Aug 31, 2018