-
Notifications
You must be signed in to change notification settings - Fork 50
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
Cancel Observation Test case commands are not working in DEVKIT #7
Comments
Can you please provide the corresponding test case (version and best a copy or summary of what it does exactly)? At the moment, I do not know which cancellation you are using... |
I hit this issue today. I am cancelling an observation by setting cancel in "WriteAttributes". It keeps notifying after that. Cancel works fine only if I sent RST on a notification. |
How do you cancel with a WriteAttributes? Cancellation requires a CoAP GET request with Observe=1. |
Hi Matthias, My bad.. I got mislead by a cancel() method in writeattributes class in leshan. I will go and implement GET with observe=1. I hope devkit handles GET with observe=1. if that works, you should close this issue. |
I realized that older version of lwm2m spec had WriteAttributes with Cancel will actually cancel an observation. It has been changed to CoAP get with observe=1. I had this code working with a few clients in 2014/2015 Test Fests |
Steps to reproduce issue
1.Send Observation and Notification test command from server.
2.Observe that once the observation and notification commands are set on the DEVKIT
3. Try to send 'Cancel observation command'
Actual Result
Cancel observation is not working on DEVKIT client, still DEVKIT responds with notifications.
The text was updated successfully, but these errors were encountered: