send resource value from msg.payload about node-red-contrib-lwm2m HOT 5 CLOSED

I misunderstood your question. I though this was just a default value issue but you're talking about writing object resource, aren't you?
If so, could you please post your flow JSON? Let me test it.

from node-red-contrib-lwm2m.

@dbaba Baba san, excuse me, it was misconfiguration in my Node-Red.
Yes, this issue is fixed: msg.payload from inject node is sent correctly as "value".
Thank you so much!

from node-red-contrib-lwm2m.

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.
I also introduced a new setting to change its behavior. The current behavior will be optional and can be enabled if necessary.

from node-red-contrib-lwm2m.

@dbaba I have upgraded to 2.1.0 - It is still not working for me.
I tried with both "Subscribe LwM2M object events" enabled and disabled (if it is correct option)
Debug of output:
{ "payload": [{ "uri": "/3303/0/5700", "value": { "type": "FLOAT", "acl": "R", "value": "" } }], "_msgid": "a72e7476.23f9c8" }

My guess would be I use double quotes "value": "", not single quotes for empty value in Config node - Objects.. Maybe that's the case?
Posting current Objects config - just in case:
{ "3303": { "0": { "5700": { "type": "FLOAT", "acl": "R", "value": "" } }, "1": { "5700": { "type": "FLOAT", "acl": "R", "value": "" }, "5701": { "type": "STRING", "acl": "R", "value": "" } }, "2": { "5700": { "type": "FLOAT", "acl": "R", "value": "" } }, "3": { "5700": { "type": "FLOAT", "acl": "R", "value": "" } } } }

from node-red-contrib-lwm2m.

@djDuff Got it, thanks.

from node-red-contrib-lwm2m.