-
Notifications
You must be signed in to change notification settings - Fork 408
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
Leshan does not decode SenML-CBOR/JSON data value (vd/8) correctly #984
Comments
Thx a lot to reporting this 🙏 I will investigate this. For now it seems that we expect base64 string for SenML Data Value ( |
I confirm this is a bug in Leshan. LWM2M spec says :
SenML RFC says :
|
#985 should fix the issue. |
what branch is it on? |
nevermind |
you can see it in the PR below the title :
|
different error this time
|
Thx again I will look at this on Monday hoping I will be able to provide a fix quickly. |
thks. have a nice weekend :) |
I pushed a quick commit on |
Have a nice weekend too and thx again to report this kind of bug. |
failing compilation on integration tests
|
ok, we progressed. The bootstrap task on the server side completes without error, but afterwards the client then throws this:
|
At first sight, I guess this is a another issue not related to CBOR |
I looked at this a little and I'm not sure to understand what happened :/ |
I created a dedicated issue : #986 |
ok. I'll close this one |
Hi Leshan Team
I'm trying out the AVSystem's Coiote LwM2M stack (both bootstrap and device management) using Leshan client demo.
When I connect the client to the bootstrap server, I get this error when the server sends back the device manager info to connect to:
I asked about it and the guys at AV Systems say that it's probably a bug on Leshan's side as it is expecting text labels instead of numeric ones.
I've had the same result with master and demo_v2 branches and leshan-2.0.0-M2 tag
BR
Jacinto
The text was updated successfully, but these errors were encountered: