Skip to content
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

Accept option (not Found) #365

Open
fernandesson opened this issue Jul 25, 2018 · 1 comment
Open

Accept option (not Found) #365

fernandesson opened this issue Jul 25, 2018 · 1 comment

Comments

@fernandesson
Copy link

Hi! I'm working on integration betwen a device using Awa Client and Ericsson Iot Accelerator.

During our tests we found that the gateway (one Leshan server) can do readings with the gateway diagnostic client, but the IOT Accelerator could not do readings internally.

Through traces we see that the only difference between the two requests is the presence of an option that specifies how the server wants to receive the message ("accept"). In the requests originated from the gateway (Leshan) this option is always sent, and we receive a response; in IOT Accelerator this option is not sent and the request fails.

This parameter is optional according to the specification, and in case it is not sent the client must respond with the format of preference. What happens in the case of the device we are testing is that we received an invalid response (not found):

On LWM2M specification, 8.1 Required Features, is possible verify the Accept option.

I'm using AwaLWM2M on orange pi zero plus, Linux 4.14.48-sunxi64

image001

Traces.zip

@boyvinall
Copy link
Contributor

Hi. This project is largely unmaintained at the moment, since founding members and companies have mostly left and shutdown. If you would like to submit a pull request, we'd be happy to consider it but otherwise this continues as-is at the current time.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants