Could not locate the bindings file

[harvspeedplumb-cell]

Hi,

Have just updated to Node Red 5.01 and the pallete has gone - have reinstalled follwing the instructions, but get the following error:-

Welcome to Node-RED
===================
9 Jul 15:36:24 - [info] Node-RED version: v5.0.1
9 Jul 15:36:24 - [info] Node.js  version: v24.18.0
9 Jul 15:36:24 - [info] Linux 6.12.93+rpt-rpi-v8 arm64 LE
9 Jul 15:36:24 - [info] Loading palette nodes
9 Jul 15:36:26 - [warn] ------------------------------------------------------
9 Jul 15:36:26 - [warn] [node-red-contrib-sm-16inpind/16inputs] Error: Could not locate the bindings file. Tried:
 → /home/hva/.node-red/node_modules/i2c-bus/build/i2c.node
 → /home/hva/.node-red/node_modules/i2c-bus/build/Debug/i2c.node
 → /home/hva/.node-red/node_modules/i2c-bus/build/Release/i2c.node
 → /home/hva/.node-red/node_modules/i2c-bus/out/Debug/i2c.node
 → /home/hva/.node-red/node_modules/i2c-bus/Debug/i2c.node
 → /home/hva/.node-red/node_modules/i2c-bus/out/Release/i2c.node
 → /home/hva/.node-red/node_modules/i2c-bus/Release/i2c.node
 → /home/hva/.node-red/node_modules/i2c-bus/build/default/i2c.node
 → /home/hva/.node-red/node_modules/i2c-bus/compiled/24.18.0/linux/arm64/i2c.node
 → /home/hva/.node-red/node_modules/i2c-bus/addon-build/release/install-root/i2c.node
 → /home/hva/.node-red/node_modules/i2c-bus/addon-build/debug/install-root/i2c.node
 → /home/hva/.node-red/node_modules/i2c-bus/addon-build/default/install-root/i2c.node
 → /home/hva/.node-red/node_modules/i2c-bus/lib/binding/node-v137-linux-arm64/i2c.node
9 Jul 15:36:26 - [warn] ------------------------------------------------------
9 Jul 15:36:26 - [info] Settings file  : /home/hva/.node-red/settings.js
9 Jul 15:36:26 - [info] Context store  : 'default' [module=memory]
9 Jul 15:36:26 - [info] User directory : /home/hva/.node-red
9 Jul 15:36:26 - [info] Projects directory: /home/hva/.node-red/projects
9 Jul 15:36:26 - [error] Unable to listen on http://127.0.0.1:1880/
9 Jul 15:36:26 - [error] Error: port in use
nodered.service: Main process exited, code=exited, status=1/FAILURE
nodered.service: Failed with result 'exit-code'.
nodered.service: Consumed 4.038s CPU time.

[alexburcea2877]

Hi,

We don't have an expert in Node-RED, but we will try to investigate on our end. Which installation method did you use the command line one or searching the node in the install menu?

[harvspeedplumb-cell]

I used the command line - couldn't find the node in the pallete.

There was an additional step for Node Red 5 - the scripst had to be approved using I think the following

npm approve-scripts --all

Many thanks

[alexburcea2877]

So, is it working now?

[harvspeedplumb-cell]

No.. that was just to do the install.

[alexburcea2877]

Please also install the I2C node: https://github.com/nielsnl68/node-red-contrib-i2c

[harvspeedplumb-cell]

Hi,

Have followed the instructions and installed this library - still not working - this is what is in the pallet menu:-

[koejok]

Hi, I don't want to interfere without being qualified. But I also use 16inpind and 16relind on my Raspberry Pi 5. Old and new generations. In my opinion, Sequent builds excellent hardware. I use node red in conjunction with Home Assistant. Formerly Home Assistant supervised, now Hass OS. Under supervised, the same thing happened to me when updating node red; the palette stopped working. That's after several years of use. Fortunately, I was able to recompile the Palette in the pi Linux shell. But I wanted to get away from this dependency. That's why I'm now using a modified Home Assistant integration from Alex. Node-RED communicates with Home Assistant, which manages the devices. Node-RED handles the logic. This way I have the administration in one place and can update node red at any time, without taking care of any special palette. Alex has built an excellent Python library for the sequent board. I was able to modify and implement this into the integration of hassos . So now for me the boards on pi5 working perfect. I reported this to Alex.
Best regards

[alexburcea2877]

Hi,

We are still not able to track this error, but in the meantime, you can use the exec node running the command line interface for the card.
Despite the fact that you need to play a little with the arguments, it actually runs faster than the native node itself (people gossip).