Hi,
I tried the OTA again with the same result:
Jul 3, 2026, 10:06:20 AMOperation updated.service_lwm2m-agent
Operation updated: status: “PENDING”, description: “Update firmware to: “ADS700” (version: 0.0.4)”", device name: “ads700dev”.
Jul 3, 2026, 10:10:26 AMOperation updated.service_lwm2m-agent
Operation updated: status: “EXECUTING”, description: “Update firmware to: “ADS700” (version: 0.0.4)”", device name: “ads700dev”.
I never receive the execute command.
thanks
Hi Haris,
We have investigated the issue and identified the root cause.
During the process, the firmware update reached the triggering phase. However, because the registration lifetime expired in the meantime, the service assumed the device was offline and paused the process. Normally, the firmware update will automatically resume once the device reconnects with a new registration or a registration update.
Looking at the logs for the subsequent registration, it appears the operation was cancelled. We suspect this may have been done manually on your end, but please let us know if that wasn’t the case.
Currently, the registration lifetime is set to 300 seconds (5 minutes), while the firmware file delivery itself takes roughly 7 to 10 minutes. To resolve this moving forward, we recommend one of the following approaches:
Option 1: Allow the operation to proceed without cancelling it. The firmware update will automatically resume on its own once the device comes back with a new registration or a registration update.
Option 2: Increase the lifetimeInSec value to a duration longer than the firmware delivery process (e.g., 15 minutes). This will ensure the firmware process completes seamlessly in one go.
Hi Ozge,
I increased the registration lifetime and now I always get the Execute command.
I was under the impression that since we keep sending ACK messages back to the server, the device is supposed to be seen as active regardless of the timeout.
But anyway, happy to make it work and thank you for the valuable help.