Mistake on this page? Email us

Update your device's registration

When the device registers to the LwM2M server, it proposes a registration session lifetime using the configuration MBED_CLOUD_CLIENT_LIFETIME. That makes the registration valid before that "lifetime" expires.

Note: The server-side maximum registration period is 72 hours. On the client side you can set the limit higher, but the server overrides it.

Periodically, or in response to events within the client or as initiated by Device Management Connect, the client updates its registration information with Device Management Connect by sending it a Registration Update operation.

The client updates the registration automatically based on the lifetime, but if you want to explicitly renew the registration from the application, you can use this API:


If a device fails to send a registration update within the device lifetime, it will be deregistered by the server.

Note: Calling register_update() is a very resource-heavy operation and is not suitable for energy-efficient devices. For TCP-connected devices, it is better to use the TCP keepalive parameter. See Connection keepalive for TCP

Note: There is a registration rate limit, so do not call register_update in a loop too often. A client registering more that 10 times within 10 seconds will be blacklisted (all incoming traffic blocked) for 60 seconds.

Failure callback


If the update operation fails, you receive the result through your error callback: