Today, we’re pleased to release a bunch of updates to the Afero Platform! We’re releasing new firmware for the Modulo board, a new Afero Profile Editor, and an updated afLib. Please see this forum post for a list of detailed changes to these components.
However, we do have one important message to convey – because of the number of components being upgraded, it’s important to upgrade your developer tools in a specific order for the most seamless upgrade. Please see the instructions below for the proper procedure. Getting these upgrades out of order will not cause any significant issues, but you may not be able to successfully publish profiles to your Afero devices until all the upgrade steps have been done.
IMPORTANT! PLEASE FOLLOW THESE UPGRADE STEPS IN ORDER!
More detailed steps are listed below, but in short, upgrading your devices and tools in the following order will make for the best upgrade experience:
- Make sure you have the latest Afero mobile app
- Let your Modulo devices download the new firmware over-the-air
- Reboot any microcontrollers attached to your Afero devices
- Upgrade Afero Profile Editor
- Republish your existing profiles to your devices
- Upgrade afLib
More detailed instructions on these steps are below.
1. Afero Mobile App
There are no specific changes to the Afero Mobile application for this upgrade, but do make sure you have the current update of the Afero app from the Google Play Store or the Apple App Store. Make sure your mobile device is awake and the app is running before completing step 2, since your devices need to be connected to the Afero Cloud to update.
The 1.2 release for Modulo will update the firmware on your Modulo. This is the first step and will be done in the background without you doing anything. Once the firmware has been upgraded, the Modulo will reboot.
The “Settings” menu of your device will show the following values for “1:” and “3:” when the OTA is complete:
1:6106 | 2:xxxxx | 3:14861 | 4:xxxxx
(the version numbers shown in “2:” and "4:"can be any value)
If you have a device that has not updated automatically, you can power-cycle your device to force the upgrade check. When they re-connect to the network they’ll download new firmware and will reboot. If you’re watching carefully, there will be two updates - a small one, and then a reboot, then a larger one, and another reboot.
At this point, your project will run just as it did before. If you want to continue using the same profile and MCU application, they will continue to work with no modifications.
3. MCU Reboot
If any of your Modulo devices are connected to an Arduino or other MCU, you must reboot the MCU after the Modulo update is complete. This problem is fixed in the 1.2 release, but to get this update you must manually reboot the MCU. We apologize for the inconvenience. It won’t happen again.
4. Afero Profile Editor
Once you have updated the firmware, you can continue using the version of the Profile Editor that you have. However, if you want to use the new features in 1.2, you will need to update to the latest Profile Editor to get them.
If you update to the latest Profile Editor before your device has received the 1.2 firmware, you will have to wait for the OTA or go back to the previous release of the Profile Editor.
5. Device Profile
The 1.2 release has added several new system attributes to the device profile. You will only get these attributes once you have published your profile using the latest version of the Profile Editor. So once you have the latest Profile Editor and Modulo firmware, load and re-publish your profile. You don’t need to make any changes to it; the Profile Editor will automatically add the new attributes and update your device-description.h file.
Once you have performed all these updates, you are now ready to update to the latest version of afLib from https://github.com/aferodeveloper/afLib
As always, if you have any questions or comments, please let us know on the forums, or at email@example.com.