You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
I noticed that unregistering a device completely erases the information on that device in the database.
OMA LwM2m is a protocol that maintains the connection with the device through a keepalive mechanism with a timeout set by the lifetime parameter. If the device does not update its status within that lifetime the server unregisters the device. But there are also many other cases in which the device can be unregistered such as a failure, a reset, or a firmware update.
Thus, if provisioning is established using the Device API, each time the device goes into one of the cases where it must be unregistered its configuration will be completely removed from the database. Making the device completely unusable when it retrieves the connection and registers again.
Perhaps there is a way to avoid this behavior currently implemented that I have not been able to find. Any suggestions?
Thank you very much for your time and efforts,
Greetings
The text was updated successfully, but these errors were encountered:
Hi,
I noticed that unregistering a device completely erases the information on that device in the database.
OMA LwM2m is a protocol that maintains the connection with the device through a keepalive mechanism with a timeout set by the lifetime parameter. If the device does not update its status within that lifetime the server unregisters the device. But there are also many other cases in which the device can be unregistered such as a failure, a reset, or a firmware update.
Thus, if provisioning is established using the Device API, each time the device goes into one of the cases where it must be unregistered its configuration will be completely removed from the database. Making the device completely unusable when it retrieves the connection and registers again.
Perhaps there is a way to avoid this behavior currently implemented that I have not been able to find. Any suggestions?
Thank you very much for your time and efforts,
Greetings
The text was updated successfully, but these errors were encountered: