Firmware updates

It is possible to inform a device that a new firmware is available in the platform by uploading a file and pushing its UUID to the device over the MQTT callback API. This way the device will get a message from the platform that a new firmware is ready to download. It will send the UUID to the device and upon the message is received in the device it can download the corresponding file by the setup download link that looks like:

https://<VANITY>.blpt.io/fw/<UUID>

WARNING

The device needs to be programmed in a way it will know what to do with the firmware file it has downloaded.

The Firmware over the air workflow is generic and usable for all sorts of devices and all sorts of file types. For example a bin, zip, csv for parameters or other file update the device can handle. As long as the device is able to download a file from a https link it will be possible to send files to the device with the firmware update fucntion.

After the firmware is uploaded to the portal you have to send it to the device. The device will then receive a message on the callback topic, so it will know it can download a the new firmware. At this point its not possible for the device to request if there is a new firmware available for download. So a device has to be listening on the callback topic and cant be asleep when sending the firmware to the device.