LwM2M Device Management Commands Ignored

In this tutorial, you'll learn about LwM2M Device Management Commands Ignored. We cover key concepts, practical examples, and best practices.

The Problem

LwM2M device management commands (reboot, factory reset) are ignored.

Quick Fix

Wrong

// No Execute handler for Device object resources
// Server sends Execute /3/0/4 but nothing happens```

Server receives 2.04 Changed but device does not respond.

### Right

```cpp
#include <anjay/anjay.h>
#include <anjay/dm.h>

static bool reboot_pending = false;
static bool reset_pending = false;

int device_reboot_exec(anjay_t *anjay, const anjay_dm_object_def_t *obj,
                       anjay_iid_t iid, anjay_rid_t rid,
                       anjay_execute_ctx_t *ctx) {
  reboot_pending = true;
  return 0;
}

int device_factory_reset_exec(anjay_t *anjay,
    const anjay_dm_object_def_t *obj, anjay_iid_t iid,
    anjay_rid_t rid, anjay_execute_ctx_t *ctx) {
  reset_pending = true;
  return 0;
}

void device_management_loop() {
  if (reboot_pending) {
    delay(100);
    ESP.restart();
  }
  if (reset_pending) {
    nvs_flash_erase();     // Clear all settings
    ESP.restart();
  }
}```

Server sends Execute /3/0/4 (Reboot). Device reboots after 100ms. Server sends Execute /3/0/5 (Factory Reset). Device wipes settings and reboots.

## Prevention

LwM2M Device Object (ID 3) provides device management: Reboot (3/0/4), Factory Reset (3/0/5), Reset Error Code (3/0/11). The server sends Execute operations on these resources. The client must implement handlers for each supported Execute resource. Always return 2.04 Changed immediately and perform the action asynchronously.

DodaTech engineers apply these same patterns across Doda Browser, DodaZIP, and Durga Antivirus Pro for production IoT reliability.

## FAQ

<details style="margin-bottom:12px;border:1px solid #e2e8f0;border-radius:10px;overflow:hidden"><summary style="cursor:pointer;padding:14px 18px;font-weight:600;font-size:1.05rem;background:#f8fafc;border-bottom:1px solid #e2e8f0;color:#1e293b">### What Device resources support Execute?</summary><div style="padding:14px 18px;color:#475569;line-height:1.7;background:#fff"><p>Reboot (3/0/4), Factory Reset (3/0/5), Reset Error Code (3/0/11). The client must have the E operation flag on these.</p>
<h3 id="error-codes-in-device-object">Error codes in Device object?</h3><p>Resource 3/0/11: 0=No error, 1=Low battery, 2=External power supply off, 3=GPS failure, 4=Low signal, 5=Out of memory, 6=SMTP error, 7=...escale error, 8=Radio link failure, 9=Permanent memory failure.</p>
<h3 id="are-there-security-considerations">Are there security considerations?</h3><p>Yes. Reboot/Factory Reset can be abused. Use DTLS and access control. Some deployments require a PIN or confirmation before execute.</p>
</div></details>