SNMP node new version outputs buffer, old version outputs string

General
1

I'm trying to offload some SNMP calls to a new install, and the SNMP flows on the new install are all completely broken.
The flows are direct copy/paste from old machine to new one.

New SNMP node version is 2.0.0
Old version with all the flows is 0.0.25, installed in 2022 or 2023.

Old version returns this:

image
image298Ă—103 1.72 KB

Current version returns this:

image
image284Ă—201 3.07 KB

Is there a config setting I'm missing on the new one that maybe I forgot I'd made on the old one?
If not, is there a way to copy the old version of the node and install it on the new system?

2

Go read the notes about the node

3

That sucks for me...is there a way to save and reinstall the old version of a node? I probably have hundreds of flows with the old one, and will take a long time to figure out and implement a conversion. If my central system fails before then, and I import the flow backup to a rebuild, my stuff will grind to a halt.

Also, I thought I'd read the documentation...I didn't realize there was a more thorough library here. Thanks.

4

You can install an old version by going to your .node-red folder and running
npm install node-red-node-snmp@a.b.c
where a.b.c is the version you want, obviously. Then restart node-red and remember not to update it again at some point in the future.

1 Like
5

Awesome, thank you.

6

The reason for the change was that the underlying library returns an object that isn't a normal object so when I was trying to be helpful and sending a string - it wan't always successful and caused other problems for users so we changed it to just send the raw object so users could do what they wanted with it. In your case you can probably just .toString() the value property to convert it to a string.
Though indeed as Colin said you can re-install the old with something like npm i node-red-node-snmp@0.* which would get the last version 0 before we changed it over.

7

Does not @Rgrove want the latest 1.x?

8

Well he said originally he was using 0.0.25

9

That's true.

10

The old version was simpler form my perspective, but I see the rationale in making it consistent with it's packaged nodes, and outputting raw data.

I'll re-use the old version until I can update the flows with a way to string the output.

11

In case anyone runs across this in the future (or I forget what I did), the suggestion for .toString() got me in the right direction.

The text below, used in a function node, converted the buffer data to string for me.

var pl = msg.payload;

for (var i = 0; i < pl.length; i++) {
    var pli = msg.payload[i].value;  
    var converted = pli.toString();
    msg.payload[i].value = converted;
}

return msg;
1 Like
12

In case you are interested you should be able to replace that with this more concise code

msg.payload.forEach((element) => {
    element.value = element.value.toString()
})
return msg;
1 Like
13

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.