Skip to main content

Firmware Update — Remote via CoAP

Update devices over-the-air via NB-IoT / LTE-M using the CoAP protocol. This is supported exclusively through the Lobaro IoT Platform — the CoAP implementation is not publicly disclosed and is intended for use with the Lobaro Platform only. Contact sales@lobaro.de for platform access.

info

Only Lobaro can upload firmware files to the platform. Contact support@lobaro.de to request the latest firmware for your device.

Downgrading below firmware 0.10.0 erases the configuration

The device configuration is stored encrypted (see Configuration Storage). Encrypted configuration storage was introduced in firmware version 0.10.0.

Firmware versions older than 0.10.0 (e.g. 0.9.x or earlier) cannot read the encrypted configuration. Downgrading a device to such a version discards the stored configuration (including LoRaWAN keys, APN credentials, SIM PINs, and MQTT credentials), and the device reverts to its defaults.

Before downgrading, back up all configuration values and be prepared to set the device up from scratch.

Prerequisites:

  • The device is connected via NB-IoT or LTE-M.
  • The firmware has been uploaded to your Lobaro Platform instance by Lobaro.

Create a firmware downlink (fw) in the Lobaro Platform (device → Downlinks) for the affected devices. Use the plain .hex file without ~boot suffix, e.g. app-nrf91-origin+0.14.0+hw4.hex for the Gateway V4.

Full remote update downlink (Gateway V4 example)
{
  "d": {
    "app": "app-nrf91-origin+0.14.0+hw4.hex",
    "boot": "app-nrf91-secure+0.5.0.hex"
  },
  "q": "fw"
}
Why app and boot are specified separately (vs. local USB)

The ~boot.hex file used for local USB updates is a bundle — application and secure firmware in one file. For remote updates, bundles cannot be used; both files are transferred individually over the air.

App-only update (advanced users only)
warning

Only use this if you are certain the installed secure firmware is already compatible. When in doubt, use the full update above.

App-only remote update downlink (Gateway V4 example)
{
  "d": {
    "app": "app-nrf91-origin+0.14.0+hw4.hex"
  },
  "q": "fw"
}
Older devices (V3 / Hybrid Gateway)

Older firmware generations distinguish between slot0 (local USB) and slot1 (remote) files. For remote updates, use the slot1 file for both app and secure firmware:

Hybrid Modbus DIN-Rail
{
  "d": {
    "app": "app-hybrid-modbus+0.14.1+dinrail+slot1.hex",
    "boot": "app-boot-nrf9160-sec-TZ2-1.8.2-mcuboot-slot1.hex"
  },
  "q": "fw"
}
Hybrid Modbus Battery (V3 + Modbus Add-On)
{
  "d": {
    "app": "app-hybrid-modbus+0.14.1+battery+slot1.hex",
    "boot": "app-boot-nrf9160-sec-TZ2-1.8.2-mcuboot-slot1.hex"
  },
  "q": "fw"
}
wM-Bus Gateway V3
{
  "d": {
    "app": "app-nrf9160-wmbus+0.28.1+hw3+slot1.hex",
    "boot": "app-boot-nrf9160-sec-TZ2-1.9.1-mcuboot-slot1.hex"
  },
  "q": "fw"
}

The variant part of the filename (e.g. dinrail, battery, hw3) identifies the hardware variant. Contact support@lobaro.de if unsure.

For details on HEX file naming and the secure firmware layer, see the Firmware Updates technical reference.

Last updated on