-
Notifications
You must be signed in to change notification settings - Fork 44
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cannot handle update registration from a Wakaama client #106
Comments
I also tried Leshan demo client. Here are the logs.
Hope this helps! |
Hi, wakaama maintainer here, The registration update mapping was changed to a CoAP POST recently. Refer to chapter 8.2.3 of the latest LWM2M Technical Specification on the OMA FTP Regards |
dmoranj
added a commit
that referenced
this issue
Oct 6, 2016
FIX registration update. Resolves #106
@pasear this is already fixed in the development branch. |
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi,
I am using lwm2m-node-lib as a server and Wakaama as the client.
It seems that the two implementations are not compatible for update registration.
It seems that the Wakaama client only sends
/rd/1
and lacking parameters required by this library.The log at server looks like:
I do not know which implementation is correct, but I find a document here saying
and it does not mention endpoint name. So, maybe this behavior should be fixed here?
Thank you.
The text was updated successfully, but these errors were encountered: