search

atlewee / node-red-contrib-sacn

Simple sACN output for Node-RED
MIT License
1 stars 4 forks source link

Sacn flow doesnt work anymore after update node-red #7

Closed MikeJollie21 closed 4 years ago

MikeJollie21 commented 4 years ago

I was forced to reinstall node red , now i am on the latest version, but the Scan flow gives the following error, i filed in the right ip and port:

"RangeError: Port should be >= 0 and < 65536. Received [ '5568' ]."

Node-RED version: v1.0.6 Node.js version: v12.16.3 Knipsel

mylesie commented 4 years ago

I just came across this same issue tonight. Has there been any work around or fix found? I would love to implement this into my flow for sensors into a LX console SACN in view.

aroslanov commented 4 years ago

Just got the same error after moving to another server. Does anyone have any workarounds for this problem?

aroslanov commented 4 years ago

Got working solution from the Reddit user i8beef:

Just a guess, but he's turning the port into an array before sending it into the underlying client connection here, which looks like incorrect usage: https://github.com/atlewee/node-red-contrib-sacn/blob/master/sacn-config.js#L14 If you edit the node_modules/node-red-contrib-sacn/sacn-config.js and removed those brackets, restarted node-red, and then went and edited / resaved the server config, that might get you working, but that is just a temporary hack that'll be undone as soon as the node_modules is rebuilt, etc.

MikeJollie21 commented 4 years ago

@aroslanov Sorry for the late reply, You are right , i removed those brackets and it worked thank you very much, unless it's a temporary fix it will help me out, up to @atlewee to update this in his code.

atlewee commented 4 years ago

Thank you for creating the issue.. Fixed in v0.0.8 :)