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
It would be nice to have some tool/script which allows to kick some client from server (unregister).
At this moment I need to wait until instance of crashed client unregister due to timeout, which is little frustrating.
The text was updated successfully, but these errors were encountered:
This is how LWM2M works, because it needs to work with sleeping devices. Normally the server has no way of knowing whether the client has crashed or is just asleep. This is why the update time period is configurable on the client. If you want it to disappear sooner, then you'll want to reduce the update time on the client.
Are you having an issue with a crashed client being unable to re-register due to an existing record?
The way in which server works is fine in production state. However it will be useful for developer to instruct server that some client just expired. As you mentioned root cause of this request is restarted client can't re-register due to existing record, and in such situation send of "unregister" as a existing client will be useful.
It would be nice to have some tool/script which allows to kick some client from server (unregister).
At this moment I need to wait until instance of crashed client unregister due to timeout, which is little frustrating.
The text was updated successfully, but these errors were encountered: