Another issue i am noticing is that when i install a node , it shows installing and after a few min it stops and the button reads "install" and not "installed" as usual. as if noting happened. regardless of the node i am trying to install .
2020-09-09T12:11:02.504Z Install : node-red-contrib-oled 0.1.0
2020-09-09T12:11:15.169Z [err] npm ERR! code ELIFECYCLE
2020-09-09T12:11:15.169Z [err] npm ERR! errno 1
2020-09-09T12:11:15.229Z [err] npm ERR! i2c-bus@1.2.5 install: `node-gyp rebuild`
2020-09-09T12:11:15.229Z [err] npm ERR!
2020-09-09T12:11:15.250Z [err] Exit status 1
2020-09-09T12:11:15.250Z [err] npm ERR!
2020-09-09T12:11:15.250Z [err] npm ERR! Failed at the i2c-bus@1.2.5 install script.
2020-09-09T12:11:15.250Z [err] npm
2020-09-09T12:11:15.259Z [err] ERR! This is probably not a problem with npm. There is likely additional logging output above.
2020-09-09T12:11:15.626Z [err]
2020-09-09T12:11:15.626Z [err] npm ERR! A complete log of this run can be found in:
2020-09-09T12:11:15.626Z [err] npm ERR! /home/pi/.npm/_logs/2020-09-09T12_11_15_510Z-debug.log
2020-09-09T12:11:15.685Z rc=1
OK, got it. the Sqlite is still busy installing ...will wait for it to complete, i know you said it will take at least 20min?
While I wait, do you have any advice on the Keypad / NFC / OLED that needs to be run by the same bus port? how does one go about this to make this work?
"The project I need to complete one's node-red is working again " below
Sorry - I'm not that familiar with i2c - the hardware usually a jumper or switch or something that allows you to select an alternate address if necessary. I thought different bus meant different pins at the Pi end. eg see pic here
npm i node-red-contrib-oled
npm ERR! code ETARGET
npm ERR! notarget No matching version found for oled-i2c-bus@^3.0.1.
npm ERR! notarget In most cases you or one of your dependencies are requesting
npm ERR! notarget a package version that doesn't exist.
npm ERR! notarget
npm ERR! notarget It was specified as a dependency of 'node-red-contrib-oled'
npm ERR! notarget
npm ERR! A complete log of this run can be found in:
npm ERR! /home/pi/.npm/_logs/2020-09-09T14_08_23_158Z-debug.log
I think we have been here before. There are already issues about that against the node but it appears the author has gone AWOL. There are suggested workarounds in the issues.