node-red-contrib-buffer-parser icon indicating copy to clipboard operation
node-red-contrib-buffer-parser copied to clipboard

Dynamic spec returns 0 payload/value

Open Eze-DP opened this issue 3 years ago • 3 comments

When using dynamic specs, it only seems to work when the option type is set to string. All other types return 0, which is incorrect. This behavior can be seen in the buffer-parser examples provided by the package.

brokenbuffer

Eze-DP avatar May 16 '22 06:05 Eze-DP

I suggest to create a buffer node with same spec and debug whole msg (there's a msg.specification where you can check spec defined on that node) usually you are missing, offset, or any other non obvious parameter for that kind of parsing

albfan avatar Sep 17 '22 09:09 albfan

I have noticed this same behaviour and managed to get a working output when using 'mask': '' under the items properties.

woytekbode avatar Dec 28 '22 12:12 woytekbode

It works using 'mask': '' under the items properties. Thanks @woytekbode

FranPanadero avatar Apr 04 '23 07:04 FranPanadero