To facilitate the deployment onto your production systems, we have set up the possibility to automatically update the HRE of your systems by uploading new installers from any Dev Station. This option is by default enabled, and if you wish to disable this functionnality, you can easily do so, see Configuration below.

​
Requirements

  • Any system you wish to OTA update needs to have the functionnality enabled (see Configuration below).
  • The installer that you upload needs to be built from the same operating system and architecture as the one you aim to update.

​
Configuration

The configuration of the OTA needs to be done before packaging your installer and installation onto the system. This means that once you have set your configuration and deployed the installer onto your system, you will not be able to modify it unless you re-install a new kernel. The settings can be found in the Core configuration file:
Open ~/Heex_SDK_<version>/kernel/Core.conf and look for the enableHreOtaUpdate setting: this is the switch to enable / disable to OTA feature. Setting it to 0 will disable it, by default it is set to 1.
📝 Note: The Core.conf file has another OTA related setting: hreOtaMaxWaitTimeMinutes. Changing this setting will allow more or less delay for the update to happen once a new installer has been uploaded, allowing the system to wait for a ‘not currently uploading’ moment before installing the new HRE. This is a more advanced feature, feel free to get in touch with our customer service if you want to know more about it.

​
Updating your system over the air

Once you have a HRE running on your system that allows OTA updates, you will be able to upload new installers from anywhere, and they will automatically be downloaded and installed onto the systems. To do so, simply add your new agents in the agents folder as described in the previous page, and from inside the Heex_SDK_<version> folder, upload the installer using following command: 
./heex hre release -c "full/path/to/your/systemConf.json" -e "ENV"
  • ENV being your heex server environment (ie: https://ENV.heex.io)

​
How it works ?

After you save configuration changes in the UI, they’ll be sent to the connected devices (agents) during the next data upload. After you upload the new installer from your dev station, it’ll be sent and installed to the connected devices (agents) during the next data upload. hre_ota_description