Implementing over the air updates

over the air updates is a special kind of action read the sections on creating a new firmware version docid\ isaoic5 7ftnjttco55ih and triggering ota update docid\ adgo fn2yj0q5lptibrqo to learn how to upload a firmware file and push it to the device from the cloud the payload for the ota action update firmware is as below { "name" "update firmware", "id" "3620755", "payload" "{\\"content length\\" 304,\\"checksum\\"\ null,\\"status\\"\ false,\\"url\\" \\"https //firmware cloud bytebeam io/api/v1/firmwares/v3 0 0/artifact\\",\\"version\\" \\"v3 0 0\\"}", } notice that payload is json inside a string payload json has the following fields of interest content length the size of the firmware file url the url from which the firmware file needs to be downloaded version the version of the file being downloaded ignore the checksum and status fields these fields are not implemented on cloud bytebeam io and are used by some of our enterprise clients the client needs to download the file at the url extracted from the payload above using https mutual tls is implemented here as well i e both the server and the client authenticate each other the same certificates downloaded in the connect to bytebeam cloud docid\ jr6sxray6ci0j3yj9ihh section and used for settting up the mqtt connection need to be used here as well downloading the firmware file using curl we could not find a good gui tool that supports custom certificates to show how to download the above files however the curl command line tool is available for different platforms and can be used for this purpose once curl has been installed you can run the below command to download the firmware file curl cacert /ca certificate pem cert /device certificate pem key /device private key pem https //firmware cloud bytebeam io/api/v1/firmwares/v3 0 0/artifact o /file bin in the above command replace /ca certificate pem , /device certificate pem , /device private key pem and /file bin with the full paths of these files on your system implementing ota in your client you can implement otas in your client as follows as in the previous guide on receiving actions docid\ fecqp8yawwk1roks7a0aq subscribe to the actions topic when an action with name update firmware is received handle it as an ota action parse the payload as json extract the url field download the firmware using the certificates and private key from the json file downloaded earlier optionally send the download progress back to the cloud implement the actual update send progress back during the update and at the end it is useful to either have a factory version of the firmware or to store one previous version of the firmware to rollback in case the step 4 fails in this case it is usefult to send the status as "failed" and set the errors field to \["rolled back to version xyz"] to the cloud