-
Notifications
You must be signed in to change notification settings - Fork 4
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
send resource value from msg.payload #9
Comments
Indeed, numeric types have now default 0. I thought numeric values didn't have NULL (empty byte array) but it seems to be my misunderstanding as OMA Spec doesn't mention it (probably because the empty string/null value handling is out of LwM2M spec scope and is implementation dependent). Will revert the default behaviors. |
@dbaba I have upgraded to 2.1.0 - It is still not working for me. My guess would be I use double quotes "value": "", not single quotes for empty value in Config node - Objects.. Maybe that's the case? |
I misunderstood your question. I though this was just a default value issue but you're talking about writing object resource, aren't you? |
@dbaba Baba san, excuse me, it was misconfiguration in my Node-Red. |
@djDuff Got it, thanks. |
@dbaba Daisuke Baba san,
I have found one more issue.
I want msg.payload to be send as resource value using lwm2m client node.
I added simple Inject node,
topic: /3303/0/5700,
payload: 20 (data type: number),
and wired it with ClientOut node.
ClientOut node successfully register on lwm2m server with this Objects defined in config node:
As you see, "value": "" is empty, so it should gather the value from msg.payload.
At least, it was working like this on my setup with 1.x version of your node.
Now, 0 is sent in this case.
If I change the "value" to exact value, for example:
value": "100",
100 will be sent to lwm2m server.
Kindly ask you to have a look at this issue, please.
Let me know if anything additional is needed.
My current config:
The text was updated successfully, but these errors were encountered: