Remote Manager doesn’t have a Bootrstrap Sever!

The Client Registration process differs based on whether the LwM2M client uses security mode or not. For LwM2M clients which do not use any security mode, the registration to Remote Manager happens without any human interaction.
For LwM2M clients which use one of the available security modes, the registration to Remote Manager requires a one-time setup from the user. For more information, check the Security page.

Initial Creation of Components upon Registration

When the LwM2M client sends a Register request, Remote Manager will make a couple of LwM2M Read requests based on the object link payload and the components will appear in the Management Console under the root node. Therefore, if a Resource in the Object Instance cannot be read, it will not be created in Remote Manager as a Resource Node.

As Executable nodes are not returned by a Read action, Remote Manager is unable to identify which executable resources are supported by the LwM2M client. That is why upon client registration, Remote Manager will create all executable resources (both mandatory and optional) in the given object model.

LwM2M Client's Registration requests will be rejected if their LwM2M version is superior to the version supported by Remote Manager.

Updating

When updates on the Lifetime parameter are sent periodically (to indicate that the client is still active and reachable), Remote Manager will update the client’s Root Node State Variables. Usually, only the "Last Update Time" State Variable will be updated.

Currently Remote Manager does not synchronize the object instances sent from update request, meaning that if new instances have occurred or an instance has been removed, Remote Manager will not read them from the client or remove them from the device. This is left as a future improvement.

De-registering, Expiration & Removing Devices

When a LwM2M client sends a De-register request, it is not removed from Remote Manager, only its state changes (to DE-REGISTERED). The client is not removed upon expiry of its lifetime either.
A LwM2M client can only be deleted by invoking its destructor (Delete action).

The delete action of the device is always an instant action! For more information about action execution, please refer to Queue Mode and Action Executions.

LwM2M Client's States

LwM2M clients have a "Client State" State Variable, which indicates their current state. It is computed on demand, meaning that the client's Root Node has to be refreshed in order to display the actual client state.

The possible client states are:

  • CREATED – this state applies when the LwM2M device root node is created for the first time but the device itself is not yet connected

  • REGISTERED – the LwM2M client registers to Remote Manager for the first time and the latter has not yet received any update from the client

  • UPDATED – the LwM2M client has sent an update(s) and is considered to be in active (reachable) state

  • EXPIRED – the lifetime period has passed without receiving an update from the LwM2M client. In that state it is considered that the request to the client will time out.

  • DE-REGISTERED – the LwM2M client has sent a de-register request, and it is no longer active (reachable)

  • AWAKE - (only in Queue Mode) the LwM2M client is awake

  • SLEEPING – (only in Queue Mode) the LwM2M client is considered to be sleeping state, which is its default state in queue mode