Firmware Update — Remote via MQTT
This option is intended for customers who operate their own MQTT backend and do not use the Lobaro Platform. For updates via the Lobaro Platform, see Remote via CoAP.
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.
Firmware updates and configuration changes without the Lobaro Platform are performed using the MQTT device synchronization mechanism described in MQTT → Device Synchronization.
Any backend implementing this specification can manage devices via MQTT, including:
- Telemetry and device uplink handling
- Device state synchronization
- Configuration synchronization
- Chunked over-the-air firmware transfer (app and boot)
- Alternatively, the backend can point the device directly at an HTTP(S) URL serving the firmware file, letting the device download it as a single streamed request instead of chunk-by-chunk over MQTT (supported since firmware
v0.15.0) — see Firmware Download via HTTP(S).
A reference implementation is available upon request — contact support@lobaro.de. It can be used for evaluation, testing, or as a starting point for a custom backend implementation.